Using the shelf manager CLI
Using the shelf manager system event log (SEL)
FortiGate-5140B Chassis Guide
01-500-156415-20151104
73
Where:
0x018D
The event ID, every new event increments by 1h. So the next event in the log
file will be tagged with
0x018E
. You can use this to keep track of what line you are on
in the file.
Event: at Jan 1 00:02:15 1970;
The date and time that the event occurred.
f
rom:(0x10,0,0);
In this string,
0x10
is the IPMC controller to which the sensor is
attached. In this message its referencing an event monitored by the shelf manager in
slot #1.
sensor:(0x04,10);
The first part
0x04
can be ignored, the
10
shows the ID of the
Sensor that generated the alarm.
event:0x1(asserted):
Sensors show when an event is triggered because of
something going wrong, but also when they return to normal. In this case,
asserted
is the key point, meaning that the sensor has observed that the device has gone
outside the bounds or thresholds that have been set for it. Had this contained
deasserted
it would mean the device has returned to its normal operating mode.
Upper Critical", Threshold:
ss a reference to the specific threshold level that
the device exceeded. Some events like thermal events could have multiple threshold
levels. The first event could simply notify the shelf manager that it’s getting too hot, to
which the shelf manager would then notify the fans in the system to speed up to help
cool the board better, at which point the sensor would
deassert
the event. Another,
higher level thermal event could notify the shelf manager that the board has now
exceeded its maximum thermal operating limit, to which the shelf manager would tell
it to deactivate and shut down.
Reading: 0xff
represents a raw value sent with the event, typically for more
technical troubleshooting review by the manufacturer. Data is rarely published for
these values.
Reviewing the SEL messages from the IPMC, FRU and Sensor commands will show you
exactly what devices are in your chassis, what the FRU IDs are for the devices that
connect to them, and all the sensor numbers that each of these devices contain. You
should be able to no identify the vast majority of both good and bad events that have
happened to your chassis and blades.
For more advanced users you can try using “–v” after many of the Shelf Manager
commands or running the “Sensordata”, “Threshold”, and “Fruinfo” commands to get
more detailed information on each sensor and FRU device.
Clearing SEL logs
Use the following command to clear SEL logs:
# clia sel clear
Example IPMC log output
# clia IPMC
Pigeon Point Shelf Manager Command Line Interpreter
10: FRU # 0
Entity: (0xf0, 0x60)
Hot Swap State: M4 (Active), Previous: M3 (Activation In
Process), Last State Change Cause: Normal State Change (0x0)
Device ID String: "ShMM-500"