[Contents] [Prev] [Next] [Index] [Report an Error]


Step 2: Display CIP Error Messages in the System Log File

Action

To display the CIP error messages in the system log file, use the following CLI command:

user@host> show log messages

Sample Output

user@host> show log messages
Jun 11 20:45:07 hissy-re0 /kernel: fxp0: link media DOWN 10Mb / half-duplex
Jun 11 20:45:07 hissy-re0 craftd[556]:  Major alarm set, fxp0: ethernet link 
down
Jun 11 20:45:07 hissy-re0 alarmd[555]: Alarm set: fxp0 color=RED, class=ETHER, 
reason=fxp0: ethernet link down 
Jun 11 20:45:07 hissy-re0 mib2d[560]: SNMP_TRAP_LINK_DOWN: ifIndex 1, 
ifAdminStatus up(1), ifOperStatus down(2), ifName fxp0
Jun 11 20:45:08 hissy-re0 craftd[556]:  Major alarm set, Connector Interface 
Panel Missing
Jun 11 20:45:08 hissy-re0 alarmd[555]: Alarm set: CIP color=RED, class=CHASSIS, 
reason=Connector Interface Panel Missing 

What It Means

The messages system log file records the time the failure or event occurred, the severity level, a code, and a message description. You can also use the show log messages | match cip command to see specific error messages that are generated when a CIP fails or is offline. Use this information to diagnose a power supply problem and to let the Juniper Networks Technical Assistance Center (JTAC) know what error messages were generated and the router events that occurred before and after the problem. For more information about system log messages, see the JUNOS System Log Messages Reference.


[Contents] [Prev] [Next] [Index] [Report an Error]