Changes to these options are activated immediatly:
Scan for MicroTCA resources after connect
After NATview has established a valid RMCP connection it tries to scan the
resources of the MicroTCA system.
Send CLOSE_SESSION_REQ on session shutdown
If activated NATview tries to shutdown the RMCP session with a CLOSE_SESSION_REQ
(as it is required by the IPMI specification). This feature may be disabled
if this leads to timeout problems.
Dump IPMI message to logfile/console
Displayes a simple dump of all IPMI messages being sent resp. received by NATview
to the console or to the logfile (if one has been specified on the register Debug).
Do not complain about old/incompatible MCH firmware
Shows no warnings for MCH firmware versions before 2.6.
Show "images not found" warnings
Display further information about missing AMC resp. chassis image files
and how to solve this. This option offers also further information in this
online help about creating new image file in case your new hardware is not
supported by NATview yet.
Changes to these options are activated after the MicroTCA system has been rescanned:
Carrier Manager ID
In a MicroTCA system every carrier must have a system wide unique ID.
Valid IDs range between 1 and 16. This option determines how the ID for the
curretly conntected carrier is configured: either from the backplane FRU data
or by static configuration in NATview. It is important that NATview and the
NAT MCH use the same carrier ID source - otherwise bridged message communication
will fail (e.g. with the AMCs).
If usure use the default (which is "from Backplane FRU")!
Limit sensor history size
Determines the number of sensor history values NATview will save for every
sensor.
Hot swap sensor type
This setting is important for proper hot swap detection. The hot swap sensor type
(and the value it stored) has changed in MCH firmware development history:
0xf2 | |
Depends on the sub version; release 2.17.14 started to use sensor type 0xf0. |
|
0xf0 |
Changes to these options become active only after a complete restart of the application:
Send poll messages to shelf manager
Used to prevent an idle disconnect from the system software.
Periodically scna the carrier manager
Starts a thread that periodically scans the carrier manahger repository to detect
changes in the system setup, e.g. whenever a hot swap handle has been pulled or pushed
back in or whenever a FRU device has been completely removed from the system.
BACKGROUND INFO:Pulling the hot swap handle on an AMC causes the board's M-state to transition from M4 through the M-states M5,M6 to M1: Payload power is being switched off, only management power is active. Unfortunately boards in M1 are no longer visible in the Shelf Manager Repository. By periodically scanning the Carrier Manager Repository NATview can detect when the board has been physically removed from the system.
Clear SEL after system scan
Default behaviour is that an SEL events is being removed/deleted after it has been
read by NATview. Therefore it is possible that the SEL still contains "old" events
being more or less meaningless after NATview has been connected to the system. (One
result for this could be that the AMCs toggle enabled/disabled state after the connection
has been established because of earlier hardware changes.)
Enabling this option removes all SEL events after the connection has been established and ensures that all SEL events are recent.