 | Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
This chapter describes messages with the CHASSISD prefix. They are generated by the chassis process (chassisd), which controls hardware components on the routing platform.
PIM pim-slot failed anti-counterfeit check
The indicated Physical Interface Module (PIM) failed the anti-counterfeit check performed by the chassis process (chassisd).
Error: An error occurred
error
Routing Engine failed anti-counterfeit check
The Routing Engine failed the anti-counterfeit check performed by the chassis process (chassisd).
Error: An error occurred
error
Unable to read serial number from anti-counterfeit device for Routing Engine
The chassis process (chassisd) could not read the serial number recorded in the ROM of the anti-counterfeit device for the Routing Engine.
Error: An error occurred
error
Contact your technical support representative.
Unable to read SHA output from anti-counterfeit device for Routing Engine
The chassis process (chassisd) could not read Secure Hash Algorithm (SHA) information from the anti-counterfeit device for the Routing Engine.
Error: An error occurred
error
Contact your technical support representative.
Unable to read serial number from anti-counterfeit device for PIM pim-slot
The chassis process (chassisd) could not read the serial number recorded in the ROM of the anti-counterfeit device for the indicated Physical Interface Module.
Error: An error occurred
error
Contact your technical support representative.
Unable to read SHA output from anti-counterfeit device for PIM pim-slot
The chassis process (chassisd) could not read Secure Hash Algorithm (SHA) information from the anti-counterfeit device for the indicated Physical Interface Module (PIM).
Error: An error occurred
error
Contact your technical support representative.
Unknown option option
The indicated option, provided on the 'chassisd' command line, is invalid. The chassis process (chassisd) initialized but ignored the invalid option.
Error: An error occurred
error
Contact your technical support representative.
Fans and impellers are now running at normal speed
The fans (and impellers, if applicable) were running at the normal speed.
Event: This message reports an event, not an error
notice
Fans and impellers being set to full speed [reason]
For the indicated reason, the chassis process (chassisd) increased the speed of fans (and impellers, if applicable) to the maximum.
Event: This message reports an event, not an error
notice
Fans and impellers being set to intermediate speed
The chassis process (chassisd) increased the speed of fans (and impellers, if applicable) to the intermediate level because of a temperature increase in the chassis.
Event: This message reports an event, not an error
notice
Unable to open 'bus-type' bus device, error error-message (error-code)
The chassis process (chassisd) could not open the indicated bus device for the indicated reason.
Error: An error occurred
error
Contact your technical support representative.
Clock module on M120 CB had configuration data checksum error
The chassis process (chassisd) detected a checksum error for the clock module on an M120 Control Board (CB).
Error: An error occurred
error
Press of online/offline button ignored for master fru-name fru-slot
The online/offline button for the indicated control board was pressed, but the chassis process (chassisd) ignored the request. The control board for M40e and M160 routers is the Miscellaneous Control Subsystem (MCS). The control board for M320, T320, and T640 routing platforms is the Control Board (CB).
Event: This message reports an event, not an error
error
The control board was acting as master.
Switch mastership to the other control board before taking the control board offline.
Error reading midplane ID EEPROM, errno error-code
The chassis process (chassisd) could not read the EEPROM on the midplane.
Error: An error occurred
error
Contact your technical support representative.
Unable to take fru-name fru-slot offline because paired Routing Engine is online
The online/offline button for the indicated control board was pressed, but the chassis process (chassisd) ignored the request. The control board for M40e and M160 routers is the Miscellaneous Control Subsystem (MCS). The control board for M320, T320, and T640 routing platforms is the Control Board (CB).
Event: This message reports an event, not an error
error
The Routing Engine paired with the indicated control board is still online.
Take the Routing Engine offline before taking the control board offline.
function-name: unable to turn state power for CFEB cfeb-slot
The chassis process (chassisd) could not turn on or turn off the power to the indicated Compact Forwarding Engine Board (CFEB).
Error: An error occurred
error
Contact your technical support representative.
function-name: status
The chassis process (chassisd) encountered an error while trying to clear the state information associated with a copy of the management process (mgd) that it spawned to commit the rescue configuration. The commit operation succeeded or failed as indicated.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
function-name: fru-name error-message
The chassis process (chassisd) determined that the indicated clock source failed in the indicated way.
Error: An error occurred
error
Contact your technical support representative.
fru-name: message
The clock-synchronization status of the indicated component (field-replaceable unit, or FRU) changed as indicated.
Event: This message reports an event, not an error
notice
Readback error from chassis management bus for fru-name fru-slot ([0xaddress, 0xoffset] -> 0xerror-code)
The chassis process (chassisd) could not read back information from the Chassis Management Bus (CMB) about the indicated component (field-replaceable unit, or FRU).
Error: An error occurred
error
The probable cause is hardware error.
Contact your technical support representative.
Error occurred when fru-name fru-slot reported its online status: error-message (error code error-code)
The chassis process requested that the indicated component (field-replaceable unit, or FRU) confirm that it was online. The indicated error occurred when the FRU sent its response. In the normal case, the chassis process performed any additional action necessary to guarantee that the FRU came online.
Error: An error occurred
error
Contact your technical support representative.
function-name: SFM sfm-slot did not acknowledge FPC fpc-slot: error error-message (code error-code)
The chassis process (chassisd) requires an acknowledgment from each Switching and Forwarding Module (SFM) before it registers a Flexible PIC Controller (FPC) as online. The acknowledgment message from the indicated SFM failed for the indicated FPC.
Error: An error occurred
error
Contact your technical support representative.
Cannot set no-concatenated mode for FPC fpc-slot PIC pic-slot
The chassis process (chassisd) could not set channelized mode for the indicated SONET/SDH Physical Interface Card (PIC). Channelized mode is configured by including the no-concatenate statement at the [edit chassis fpc 'slot' pic 'slot'] hierarchy level.
Event: This message reports an event, not an error
warning
function-name: error-message
The chassis process (chassisd) experienced the indicated problem while attempting to parse the configuration database.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
Unable to parse configuration; using defaults
The chassis process (chassisd) could not parse the configuration, and used default values while initializing.
Error: An error occurred
error
Contact your technical support representative.
function-name: warning-message, FPC fpc-slot PIC pic-slot
The configuration that was specified for the indicated Physical Interface Card (PIC) is invalid for that type of PIC.
Event: This message reports an event, not an error
warning
Unable to open device-name device file (errno error-code)
The chassis process (chassisd) could not open the device file for the indicated device.
Error: An error occurred
error
Contact your technical support representative.
function-name: error-message
While trying to commit the rescue configuration, the chassis process (chassisd) encountered an error.
Error: An error occurred
error
An internal software failure occurred.
Contact your technical support representative.
chassisd already running; exiting
The chassis process (chassisd) exited because it discovered that another chassisd process was already running.
Event: This message reports an event, not an error
error
Killing existing chassisd and exiting
The chassis process (chassisd) discovered that another chassisd process was already running. It terminated the other process and exited.
Event: This message reports an event, not an error
error
fru-name in slot fru-slot failed
The indicated fan or impeller failed. The chassis process (chassisd) raised an alarm and increased the speed of the remaining fans (and impellers, if applicable) to full speed.
Error: An error occurred
error
Contact your technical support representative.
Fchip: configuration already completed
The chassis process (chassisd) detected an attempt to configure an F chip on a Control Board (CB) when configuration was already complete.
Error: An error occurred
error
Fchip (CB control-board-slot, ID fchip-id): ftoken overflow/underflow set (data) at address
The chassis process (chassisd) detected an underflow or overflow error on the indicated F chip on the indicated Control Board (CB).
Error: An error occurred
error
Contact your technical support representative.
Fchip (CB control-board-slot, ID fchip-id): f8chip_ftoken_init() stuck in ftoken loop, addr=address, data=data
The chassis process (chassisd) encountered an error while initializing memory at the indicated address for the indicated F chip on the indicated Control Board (CB).
Error: An error occurred
error
Contact your technical support representative.
Fchip (CB control-board-slot, ID fchip-id): HSL configuration failed (error error-message)
The chassis process (chassisd) could not configure high speed links (HSL) for the indicated F chip on the indicated Control Board (CB).
Error: An error occurred
error
Fchip (CB control-board-slot, ID fchip-id): link link-id failed because of error-message
The chassis process (chassisd) detected an error for the indicated high speed link (HSL) for the indicated F chip on the indicated Control Board (CB).
Error: An error occurred
error
Contact your technical support representative.
Fchips were not configured yet
The chassis process (chassisd) detected that F chips were not yet initialized on the Control Board (CB).
Error: An error occurred
error
Fchip (CB control-board-slot, ID fchip-id): dropped drop-rate cells per second coming from Packet Forwarding Engine pfe on FPC fpc-slot
The Packet Forwarding Engine divides packets into smaller units called cells for more efficient processing. As the indicated F chip on the indicated Control Board (CB) processed data that was received from the indicated Packet Forwarding Engine on the indicated Flexible PIC Concentrator (FPC), it dropped the indicated number of cells per second.
Error: An error occurred
error
Contact your technical support representative.
Fchip (CB control-board-slot, ID fchip-id): dropped drop-rate cells per second destined for Packet Forwarding Engine pfe on FPC fpc-slot
The Packet Forwarding Engine divides packets into smaller units called cells for more efficient processing. As the indicated F chip on the indicated Control Board (CB) processed data before sending it to the indicated Packet Forwarding Engine on the indicated Flexible Port Concentrator (FPC) for outgoing transmission, it dropped the indicated number of cells per second.
Error: An error occurred
error
Contact your technical support representative.
Fchip (CB control-board-slot, ID fchip-id): read error in function-name() for link#link-id at address address in register register
The indicated routine failed with a read error at the indicated address and register for the indicated F chip and link on the indicated Control Board (CB).
Error: An error occurred
error
Fchip (CB control-board-slot, ID fchip-id): write error in function-name() for link#link-id at address address in register register
The indicated routine failed with a write error at the indicated address and register for the indicated F chip and link on the indicated Control Board (CB).
Error: An error occurred
error
Fchip (CB control-board-slot, ID fchip-id): unable to lock PLL
The chassis process (chassisd) could not lock a phased-lock loop (PLL) for the indicated F chip on the indicated Control Board (CB).
Error: An error occurred
error
Contact your technical support representative.
Fchip (CB control-board-slot, ID fchip-id): reset failed
The chassis process (chassisd) could not reset the indicated F chip on the indicated Control Board (CB).
Error: An error occurred
error
Contact your technical support representative.
Fchip (CB control-board-slot, ID fchip-id): SRAM fuse did not initialize
The chassis process (chassisd) detected that static RAM (SRAM) did not initialize properly for the indicated F chip on the indicated Control Board (CB).
Error: An error occurred
error
Fchip (CB control-board-slot, ID fchip-id): part number part-number and version version were invalid
The indicated part number and version detected for the indicated F chip on the indicated Control Board (CB) were not valid values.
Error: An error occurred
error
Fchip: configuration already completed
The chassis process (chassisd) detected an attempt to configure an F chip when configuration was already complete.
Error: An error occurred
error
Fchip fchip-id: invalid number of Md chips (count) for Packet Forwarding Engine pfe on FPC fpc-slot
The chassis process (chassisd) detected an invalid number of Md chips for the indicated F chip, Packet Forwarding Engine and Flexible PIC Concentrator (FPC).
Error: An error occurred
error
Fchip fchip-id: unable to set rate limit on port port
The chassis process (chassisd) could not set the rate limit for the indicated F chip and port.
Error: An error occurred
error
Fchip fchip-id: unable to read configuration register
The chassis process (chassisd) could not read a configuration register on the indicated F chip.
Error: An error occurred
error
Fchip fchip-id: Ftoken overflow/underflow set (data) at address
The chassis process (chassisd) detected an underflow or overflow error on the indicated F chip.
Error: An error occurred
error
Contact your technical support representative.
Fchip fchip-id: fchip_ftoken_init() stuck in ftoken loop, addr=address, data=data
The chassis process (chassisd) encountered an error while initializing memory at the indicated address for the indicated F chip.
Error: An error occurred
error
Contact your technical support representative.
Fchip high-speed receiver (HSR) error: error-message
The chassis process (chassisd) detected an error in the high-speed receiver (HSR) subsystem for the F chip with the indicated characteristics.
Error: An error occurred
error
HSR: No vectors supplied
The chassis process (chassisd) could not initialize the high-speed receiver (HSR) subsystem for an F chip.
Error: An error occurred
error
Fchip fchip-id: unable to initialize HSR link link-id
The chassis process (chassisd) could not initialize the indicated high-speed receiver (HSR) link for the indicated F chip.
Error: An error occurred
error
Fchip fchip-id: hsr_reset error in fchip_init() on link link-id
A high-speed receiver (HSR) reset error occurred during initialization of the indicated F chip and link.
Error: An error occurred
error
Fchip high-speed transmitter (HST) error: error-message
The chassis process (chassisd) detected an error in the high-speed transmitter (HST) subsystem for the F chip with the indicated characteristics.
Error: An error occurred
error
HST: No vectors supplied
The chassis process (chassisd) could not initialize the high-speed transmitter (HST) subsystem for an F chip.
Error: An error occurred
error
Fchip fchip-id: unable to initialize HST link link-id
The chassis process (chassisd) could not initialize the indicated high-speed transmitter (HST) link for the indicated F chip.
Error: An error occurred
error
Fchip fchip-id: hst_reset error in fchip_init() on link link-id
A high-speed transmitter (HST) reset error occurred during initialization of the indicated F chip and link.
Error: An error occurred
error
Fchips were not configured yet
The chassis process (chassisd) detected that F chips were not yet initialized.
Error: An error occurred
error
SIBsib-slot_F0: link-type link link-id was bad
The chassis process (chassisd) detected an error for the indicated high-speed receiver (HSR) or high-speed transmitter (HST) link for an F chip on the indicated Switch Interface Board (SIB).
Error: An error occurred
error
Contact your technical support representative.
F chip module was invalid
The chassis process (chassisd) detected an invalid F-chip module while enabling or disabling the monitoring of F-chip functional blocks.
Error: An error occurred
error
Contact your technical support representative.
Fchip fchip-id: read error in function-name() for link#link-id, at address address in register register
The indicated routine failed with a read error at the indicated address and register for the indicated F chip and link.
Error: An error occurred
error
Fchip fchip-id: write error in function-name() for link#link-id, at address address in register register
The indicated routine failed with a write error at the indicated address and register for the indicated F chip and link.
Error: An error occurred
error
Fchip fchip-id: link-type link-id poll returned error error-code
An error with the indicated error number occurred during polling of the indicated high-speed receiver (HSR) or high-speed transmitter (HST) link for the indicated F chip.
Error: An error occurred
error
Contact your technical support representative.
Fchip fchip-id: per-port rate limit was not enabled
The chassis process (chassisd) detected that per-port rate limiting was not enabled when it attempted to set the rate limit on an individual port for the indicated F chip.
Error: An error occurred
error
Contact your technical support representative.
Unable to start fru-name fru-slot because F chips were not initialized
The indicated Switch Interface Board (SIB) did not start because the F chips on it were not initialized.
Error: An error occurred
error
Contact your technical support representative.
F chip fchip-id: part number (part-number) and version (version) were invalid
The indicated part number and version detected for the indicated F chip were not valid values.
Error: An error occurred
error
Fchip: fhsr_read() failed at address address
The high-speed receiver (HSR) read routine failed at the indicated address on an F-chip register.
Error: An error occurred
error
Contact your technical support representative.
Fchip: fhsr_write() of value value failed at address address
The high-speed receiver (HSR) write routine could not record the indicated value at the indicated address on an F-chip register.
Error: An error occurred
error
Fchip: fhst_read() failed at address address
The high-speed transmitter (HST) read routine failed at the indicated address on an F-chip register.
Error: An error occurred
error
Contact your technical support representative.
Fchip: fhst_write() of value value failed at address address
The high-speed transmitter (HST) write routine could not record the indicated value at the indicated address on an F-chip register.
Error: An error occurred
error
File open: filename, error: error-code -- error-message
The chassis process (chassisd) could not open the indicated file for the indicated reason.
Error: An error occurred
critical
File stat: filename, error: error-code -- error-message
The chassis process (chassisd) could not open the indicated file because it could not obtain its status.
Error: An error occurred
error
function-name: unexpected state statetype for SIB#sib-slot
The indicated function failed because it encountered the indicated type of unexpected internal state with respect to the indicated Switch Interface Board (SIB).
Error: An error occurred
error
Contact your technical support representative.
function-name: error-message (SIB#sib-slot, Packet Forwarding Engine pfe on FPC fpc-slot)
During execution of the indicated fabric management routine, the indicated error occurred between the indicated Switch Interface Board (SIB) and the indicated Packet Forwarding Engine on the indicated Flexible PIC Concentrator (FPC).
Error: An error occurred
error
Contact your technical support representative.
FM: HSR error occurred on link from SIB-S port F(s-row,s-port) to SIB-L#sib-slot port F(l-row,l-port)
In a routing matrix, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the T640 routing nodes (called SIB-Ls) and the SIBs in the TX Matrix platform (called SIB-Ss). The chassis process (chassisd) on the routing node that houses the indicated SIB-L detected an error in the electrical path between the indicated ports on the SIB-L and the corresponding SIB-S.
Error: An error occurred
error
Contact your technical support representative.
FM: error-message error occurred on link to-from-sib SIB-L#sib-slot to-from-scc SCC
In a routing matrix, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the TX Matrix platform (the switch-card chassis, or SCC) and the SIBs in the T640 routing nodes (called SIB-Ls). The chassis process (chassisd) on the routing node that houses the indicated SIB-L detected the indicated error as packets that were traveling in the indicated direction were translated between electrical and optical media.
Error: An error occurred
error
Contact your technical support representative.
FM: fiber cable from SIB-L#sib-slot possibly connected to wrong SIB-S
In a routing matrix, the fiber-optic cable between each Switch Interface Board in a T640 routing node (called a SIB-L) must connect to a specific SIB port on the TX Matrix platform (called a SIB-S). The cable originating at the indicated SIB-L was possibly plugged into the wrong SIB-S port or wrong SIB-S.
Error: An error occurred
error
Contact your technical support representative.
FM: HSR error occurred on link from LCClcc SIB-L port F(l-row,l-port) to SIB-S#sib-slot port F(s-row,s-port)
In a routing matrix, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the TX Matrix platform (called SIB-Ss) and the SIBs in the T640 routing nodes (called SIB-Ls). The chassis process (chassisd) on the TX Matrix platform detected an error in the electrical path between the indicated port on the indicated SIB-S and the indicated port on a SIB-L installed in the indicated routing node (line-card chassis, or LCC).
Error: An error occurred
error
Contact your technical support representative.
FM: error-message error occurred on link to-from-sib-s SIB-S#sib-slot to-from-lcc LCClcc
In a routing matrix, packets traverse both electrical and optical media as they travel between the Switch Interface Boards (SIBs) in the TX Matrix platform (called SIB-Ss) and the SIBs in the T640 routing nodes (line-card chassis, or LCCs). The chassis process (chassisd) on the TX Matrix platform detected the indicated error as packets that were traveling to or from the indicated LCC were translated between electrical and optical media.
Error: An error occurred
error
Contact your technical support representative.
function-name: unable to allocate memory; error-message
The chassis process (chassisd) could not allocate memory for a fabric operation.
Error: An error occurred
warning
Contact your technical support representative.
Fabric management error for SIB sib-slot: error-message
The chassis process (chassisd) detected the indicated type of error on the indicated Switch Interface Board (SIB) and performed the indicated action.
Error: An error occurred
error
Contact your technical support representative.
SIB sib-slot does not support features required for FPC Type 4
The indicated Switch Interface Board (SIB) does not support features required by the Flexible PIC Concentrator (FPC) Type 4.
Error: An error occurred
error
Contact your technical support representative.
function-name: SIB sib-slot does not support configured features. But six_slot state configured. Correct the configuration and restart chassisd.
The configuration that was specified for the indicated Switch Interface Board (SIB) is not supported.
Error: An error occurred
error
Change the configuration and restart the chassis process (chassisd).
function-name: unable to find FPC for PIC attachment operation
The chassis process (chassisd) attempted to bring a Physical Interface Card (PIC) online, but could not find the Flexible PIC Concentrator (FPC) that houses it.
Error: An error occurred
warning
Contact your technical support representative.
function-name: PIC detection on FPC fpc-slot timed out
The chassis process (chassisd) expects to receive notification within a timeout period that each Flexible PIC Concentrator (FPC) has attached the Physical Interface Cards (PICs) that it houses. It did not receive notification from the indicated FPC.
Error: An error occurred
error
Contact your technical support representative.
Installed SIB type (SIB-I8-F16) does not support features required by FPC fpc-slot
The indicated Flexible PIC Concentrator (FPC) is Type 4, which is not supported by Switch Interface Board (SIB) type SIB-I8-F16.
Error: An error occurred
error
Contact your technical support representative.
fru-name fru-slot already offline
The chassis process (chassisd) received a request to take the indicated component (field-replaceable unit, or FRU) offline, but the FRU was already offline.
Event: This message reports an event, not an error
error
Received request to bring fru-name fru-slot online; it was already online
The chassis process (chassisd) received a request to bring the indicated component (field-replaceable unit, or FRU) online, but the FRU was already online.
Event: This message reports an event, not an error
warning
function-name: state fru-name fru-slot
The state of the indicated component (field-replaceable unit, or FRU) changed as indicated.
Event: This message reports an event, not an error
notice
FRU fru-name is not supported in current slot
The chassis process (chassisd) detected that the indicated hardware component (field-replaceable unit, or FRU) was inserted in a slot that is not valid for that component type.
Error: An error occurred
critical
Contact your technical support representative.
function-name: fru-name operation error: reason (error-message)
The chassis process (chassisd) could not perform the indicated I/O operation on the indicated component (field-replaceable unit, or FRU).
Error: An error occurred
error
Contact your technical support representative.
function-name: fru-name operation error: reason 0xoffset (error-message)
The chassis process (chassisd) could not perform the indicated I/O operation at the indicated byte offset.
Error: An error occurred
error
Contact your technical support representative.
function-name: FRU fru-name, errno error-code, error-message
The chassis process (chassisd) could not send an interprocess communication (IPC) message to the indicated component (field-replaceable unit, or FRU) because of the indicated error.
Error: An error occurred
warning
Unable to take fru-name fru-slot offline because FRU sequencer is active: reason
The chassis process (chassisd) could not take the indicated component (field-replaceable unit, or FRU) offline for the indicated reason.
Event: This message reports an event, not an error
notice
Taking fru-name fru-slot offline: reason
The chassis process (chassisd) took the indicated component (field-replaceable unit, or FRU) offline for the indicated reason.
Event: This message reports an event, not an error
notice
Offline request timed out; fru-name fru-slot restarted
The indicated component (field-replaceable unit, or FRU) did not go offline within the time period that is normally sufficient for synchronized shutdown. After generating this message, the chassis process (chassisd) tried several times to take the FRU offline and powered it down if all attempts failed.
Event: This message reports an event, not an error
warning
function-name: attempt to bring fru-name fru-slot online timed out
The indicated component (field-replaceable unit, or FRU) did not come online within the time that is normally sufficient. After generating this message, the chassis process (chassisd) tried to bring the FRU online several more times. If all attempts failed, the chassisd process raised an alarm and left the FRU offline.
Event: This message reports an event, not an error
error
fru-name fru-slot at step step-number
The power-on sequence for the indicated component (field-replaceable unit, or FRU) failed at the indicated point.
Error: An error occurred
error
Error for fru-name fru-slot: error-message; action
The chassis process (chassisd) tried to bring the indicated component (field-replaceable unit, or FRU) online, but the attempt failed in the indicated way. As a result, the chassisd process performed the indicated action.
Event: This message reports an event, not an error
error
Attempt count to power on fru-name fru-slot timed out; restarted it
The chassis process (chassisd) tried the indicated number of times to bring the indicated component (field-replaceable unit, or FRU) online, but the attempts failed. In another attempt to bring the FRU online, the chassisd process issued the restart command for the FRU.
Event: This message reports an event, not an error
error
chassisd invalidated support for fru-name fru-slot
The chassis process (chassisd) invalidated support for the indicated component (field-replaceable unit, or FRU) during initialization.
Error: An error occurred
warning
component version mismatch for fru-name -- expected expected-value, got received-value
The chassis process (chassisd) verifies that it supports the revision level or version of a component (field-replaceable unit, or FRU). The revision level for the indicated FRU was unsupported or otherwise invalid.
Event: This message reports an event, not an error
error
Upgrade the FRU.
Fchip: invalid SIB slot
A routine tried to determine the identifier for an application-specific integrated circuit (ASIC) on a Switch Interface Board (SIB). The attempt failed, because the supplied SIB slot number was invalid.
Error: An error occurred
error
Contact your technical support representative.
function-name: fru-name not ready for power up (RTIME_PWR_COND = 0xvalue)
The GBUS was not ready when the chassis process (chassisd) first tried to power it on, and the power-up operation timed out.
Error: An error occurred
error
The probable cause is hardware error.
Contact your technical support representative.
Readback error from GBUS for fru-name fru-slot ([0xgbus-address, 0xgbus-registers] -> 0xreturn-value)
There was an error when the chassis process (chassisd) tried to read back information from the GBUS on the indicated component (field-replaceable unit, or FRU).
Error: An error occurred
error
The probable cause is hardware error.
Contact your technical support representative.
fru-name#fru-slot - command
The chassis process (chassisd) reset the GBUS for the indicated component (field-replaceable unit, or FRU). This is a normal part of startup.
Event: This message reports an event, not an error
warning
function-name: fru-name fru-slot -- management bus failed sanity test
The chassis process (chassisd) checks its management GBUS with a set of test operations when it is started. The tests failed.
Error: An error occurred
error
Contact your technical support representative.
function-name: error-message
The chassis process (chassisd) detected the indicated error.
Error: An error occurred
error
Perform any corrective actions mentioned in the error message.
function-name: error-message
The chassis process (chassisd) generated the indicated warning message.
Error: An error occurred
notice
Unexpected error from gettimeofday: error-code -- error-message
The chassis process (chassisd) could not obtain the time of day because of the indicated error.
Error: An error occurred
warning
Unable to enable graceful Routing Engine switchover; interface interface-name does not support it
The chassis process (chassisd) could not enable graceful Routing Engine switchover because the indicated interface does not support it.
Error: An error occurred
error
Unable to enable graceful Routing Engine switchover; PIC does not support it
The chassis process (chassisd) could not enable graceful Routing Engine switchover because an installed Physical Interface Card (PIC) does not support it.
Error: An error occurred
error
Chassis temperature over temperature degrees C (message)
The temperature of one or more components (field-replaceable units, or FRUs) exceeded the indicated temperature, which is the lower of two thresholds. The fans (and impellers, if applicable) were in the indicated state. The chassis process (chassisd) increased the speed of all functioning fans and impellers to full speed.
Event: This message reports an event, not an error
warning
Increase cooling in the area around the chassis.
Error reading host temperature sensor
The chassis process (chassisd) could not read the temperature sensors on the routing platform.
Error: An error occurred
notice
function-name: unable to read configuration for HSR identifier
The indicated function could not read the configuration for the indicated high-speed receiver (HSR).
Error: An error occurred
error
function-name: unable to write configuration for HSR identifier
The indicated routine could not write to the configuration for the indicated high-speed receiver (HSR).
Error: An error occurred
error
Provided number of HSR elements (count) was invalid
The indicated routine for processing a certain number of high-speed receiver (HSR) elements failed, because the supplied number of elements was invalid.
Error: An error occurred
error
function-name: FIFO read failed for HSR identifier
A first in, first out (FIFO) read error occurred during execution of the indicated routine on the indicated high-speed receiver (HSR).
Error: An error occurred
error
Readback error from I2C slave for fru-name fru-slot ([0xi2cs-address, 0xoffset] -> 0xerror-code)
The chassis process (chassisd) could not read back information from the I2C slave (I2CS) about the indicated component (field-replaceable unit, or FRU).
Error: An error occurred
error
The probable cause is hardware error.
Contact your technical support representative.
Invalid IDEEPROM format for fru-name
The chassis process (chassisd) determined that the ID EEPROM format specified for the indicated type of hardware component (field-replaceable unit, or FRU) is not valid for it.
Error: An error occurred
critical
Contact your technical support representative.
function-name: fru-name unable to get presence masks (error-message)
The chassis process (chassisd) could not read I2C data with presence information about the indicated component (field-replaceable unit, or FRU).
Error: An error occurred
error
Contact your technical support representative.
function-name: error-message
The indicated error occurred during an I2C access library operation.
Error: An error occurred
error
Contact your technical support representative.
'0xassembly-id' is invalid value for fru-name assembly ID
The assembly ID for the indicated component (field-replaceable unit, or FRU) was not valid for its type.
Error: An error occurred
error
Contact your technical support representative.
function-name: operation ioctl failure for group group-id at address 0xaddress (errno error-code)
The chassis process (chassisd) could not perform the indicated ioctl() operation on the I2C data for the indicated component (field-replaceable unit, or FRU).
Error: An error occurred
error
Contact your technical support representative.
function-name: fru-name operation failed for group group-id at address 0xaddress
The chassis process (chassisd) could not perform the indicated I/O operation on the I2C data for the indicated component (field-replaceable unit, or FRU).
Error: An error occurred
error
Contact your technical support representative.
Corruption on midplane ID EEPROM (ID: 0xassembly-id, MAC address: 0xmac-address, 0xversion)
The chassis process (chassisd) found corrupted information when it tried to verify the parameters of the midplane's I2C ID EEPROM.
Error: An error occurred
error
Contact your technical support representative.
function-name: requested offset was out of range (offset offset + nbytes count > 256)
The indicated offset, which is greater than 256, was specified in a read request for an I2C device.
Error: An error occurred
error
No I2C device uses or has storage above an offset of 256.
Contact your technical support representative.
function-name: read error for group group-id at address 0xaddress, offset offset
The chassis process (chassisd) could not read I2C data from the indicated device.
Error: An error occurred
error
Contact your technical support representative.
function-name: write error for group group-id at address 0xaddress, offset offset
The chassis process (chassisd) could not write I2C data to the indicated device.
Error: An error occurred
error
Contact your technical support representative.
Unable to read fru-name ID EEPROM
The chassis process (chassisd) could not read the I2C ID EEPROM of the indicated component (field-replaceable unit, or FRU).
Error: An error occurred
error
Contact your technical support representative.
function-name: unable to create interface device for interface-name (error-message)
The chassis process (chassisd) creates initial interface devices for newly installed Physical Interface Cards (PICs) and pseudodevices. It could not create a device for the indicated PIC or pseudodevice.
Error: An error occurred
error
Necessary resources might have been unavailable.
Contact your technical support representative.
function-name: created device-name for interface-name
The chassis process (chassisd) created the initial interface device for the indicated newly installed Physical Interface Card (PIC) or pseudodevice.
Event: This message reports an event, not an error
notice
ifdev_detach(pseudo devices: all)
The chassis process (chassisd) detached the interface devices for all pseudodevices.
Event: This message reports an event, not an error
notice
ifdev_detach(fpc-slot)
The chassis process (chassisd) detached the interface devices for all Physical Interface Cards (PICs) installed in the indicated Flexible PIC Concentrator (FPC).
Event: This message reports an event, not an error
notice
ifdev_detach_pic(fpc-slot/pic-slot)
The chassis process (chassisd) detached the interface devices for the indicated Physical Interface Card (PIC).
Event: This message reports an event, not an error
notice
ifdev_detach(pseudo devices: porttype port-type, sdev=sdev-number, edev=edev-number)
The chassis process (chassisd) detached the interface devices for the indicated pseudodevices.
Event: This message reports an event, not an error
notice
ifdev_detach: rtslib_ifdm_change_tlvs failed for slot fpc-slot dev idx device-id error-message
The chassis process (chassisd) asked the kernel to remove the indicated interface from the kernel interface table. The request failed.
Error: An error occurred
error
function-name: ifdm get_by_name failed for interface-type interface device interface-name (error-message)
The chassis process (chassisd) failed to find the indicated interface device, even though it just created it.
Event: This message reports an event, not an error
warning
There was a problem with interface state creation.
Contact your technical support representative.
function-name: rtslib_ifdm_get_by_index failed: error-code - error-message
The chassis process (chassisd) could not obtain information about an interface device.
Error: An error occurred
error
Unable to retrieve information for interface device interface-name: error-message
The chassis process (chassisd) could not obtain information about the indicated interface device.
Error: An error occurred
error
function-name: unable to allocate memory for interface-type interface
The chassis process (chassisd) could not allocate memory when creating an interface device for the indicated interface type.
Error: An error occurred
error
Resources on the system are extremely limited.
Eliminate the resource limitations and restart the Physical Interface Card (PIC) that houses the interface for which the interface device could not be created.
function-name: attempt count to add interface device interface-name failed (error-message)
The chassis process (chassisd) tried the indicated number of times to create the indicated interface device, but the attempts failed. After generating this message, the chassisd process waited a while for resources to free up and tried again.
Event: This message reports an event, not an error
warning
Necessary resources might have been unavailable. They should become available soon.
function-name: library-function-name failed (error-message)
The chassis process (chassisd) could not create an interface device because an error occurred during the indicated call to the routing socket library.
Error: An error occurred
error
Contact your technical support representative.
function-name: reason for fru-name (error-message)
The chassis process (chassisd) could not perform the indicated ioctl() operation on the indicated component (field-replaceable unit, or FRU).
Error: An error occurred
error
Contact your technical support representative.
function-name: no ack received from fru-type for fru-name fru-slot state change (0xsent-mask, acks 0xack-mask)
The chassis process (chassisd) notified the indicated components (field-replaceable units, or FRUs) that the component in the indicated slot was changing state. It did not receive the expected acknowledgment.
Error: An error occurred
error
Contact your technical support representative.
Dropped IPC connection for fru-name fru-slot
The chassis process (chassisd) dropped its interprocess communication (IPC) connection to the indicated component (field-replaceable unit, or FRU).
Event: This message reports an event, not an error
warning
pipe_write failure for connection-id; connection error: error-message (errno error-code)
The chassis process (chassisd) could not write to a socket, because of the indicated error. The socket is for a connection to another process that runs on the Routing Engine and helps manage the chassis.
Error: An error occurred
error
Contact your technical support representative.
function-name: error-message
An error occurred when the chassis process (chassisd) received an interprocess communication (IPC) message.
Error: An error occurred
error
Contact your technical support representative.
function-name: flush operation failed for fru-name fru-slot
The chassis process (chassisd) could not write to a socket that it was using to communicate with the indicated component (field-replaceable unit, or FRU).
Error: An error occurred
warning
Contact your technical support representative.
Dropping message from connection queue: type = message-type, subtype = message-subtype
The chassis process (chassisd) dropped an interprocess communication (IPC) message because the message queue had already reached maximum capacity.
Error: An error occurred
error
The connection to a component (field-replaceable unit, or FRU) no longer exists, so the chassisd process cannot send all messages immediately as it usually does.
Contact your technical support representative.
function-name: error code error-code, type message-type, subtype message-subtype, opcode message-opcode
The chassis process (chassisd) detected an error in an interprocess communication (IPC) message with the indicated characteristics.
Error: An error occurred
error
Contact your technical support representative.
function-name: unable to locate FRU for message with type message-type, subtype message-subtype, opcode message-opcode
The chassis process (chassisd) could not locate a component (field-replaceable unit, or FRU) to handle the interprocess communication (IPC) message with the indicated characteristics that it received. The message was ignored.
Error: An error occurred
error
Contact your technical support representative.
Dropping message from connection queue: type = message-type, subtype = message-subtype
The chassis process (chassisd) had to discard a message because the queue of messages waiting for a connection was already full.
Error: An error occurred
error
function-name: unable to handle fru-name message with type message-type, subtype message-subtype, length length, opcode message-opcode, error error-code
The chassis process (chassisd) received an interprocess communication (IPC) message about the indicated FRU. The message had the indicated characteristics. The chassisd process could not handle the message.
Error: An error occurred
error
Contact your technical support representative.
function-name: invalid message received: message (message type message-type, subtype message-subtype)
The chassis process (chassisd) received a unexpected message with the indicated characteristics.
Error: An error occurred
error
Contact your technical support representative.
Received unexpected message from connection-id: type = message-type, subtype = message-subtype
The chassis process (chassisd) received an unexpected message from a peer connection.
Error: An error occurred
error
function-name: pipe_write failure for SCC connection with error error-code (error-message)
A line-card chassis in a routing matrix attempted to send data to the TX Matrix platform (switch-card chassis, or SCC) over a pipe. The attempt failed with the indicated error.
Error: An error occurred
warning
FRU has no connection pipe function-name fru-name
The chassis process (chassisd) could not send a message to the indicated component (field-replaceable unit, or FRU) because the interprocess communication (IPC) pipe to the FRU no longer existed.
Error: An error occurred
warning
FRU has no connection arguments function-name fru-name
The chassis process (chassisd) could not send a message to the indicated component (field-replaceable unit, or FRU) because one or more required parameters had a null value.
Error: An error occurred
warning
fru-name: error-message
The chassisd process (chassisd) detected the indicated error while handling blobs (opaque information) for the indicated field replaceable unit (fru). The blobs are used by the fru to store state information across in service software upgrade(issu) reboot.
Error: An error occurred
notice
Daemon [process-name] state:<state> error:<error-message>
The chassisd process (chassisd) encountered the indicated error in the indicated in service software upgrade (issu) state for the indicated daemon.
Error: An error occurred
notice
action error-code(error-message)
The chassisd process (chassisd) encountered the indicated error for the indicated in service software upgrade process (issu) action.
Error: An error occurred
notice
fru-name: state:[state] error-message
The chassisd process (chassisd) encoutered the indicated error during the in service software upgrade for the indicated field replaceable unit (fru).
Error: An error occurred
notice
fru-name: state:[state] error:[message] reason:[error-message]
The chassisd process (chassisd) detected the indicated error for the indicated field replaceable unit (fru) during in service software upgrade (issu).
Error: An error occurred
notice
jtree terminate operation returned error-code
The chassis process (chassisd) received the indicated error when executing the JUNOS system call that terminates the jtree.
Event: This message reports an event, not an error
warning
Backup Routing Engine became master, because JUNOS version of former master did not match SCC master
The chassis process (chassisd) running on the master Routing Engine on a T640 routing node (line-card chassis, or LCC, in a routing matrix) relinquished mastership to the backup Routing Engine in the LCC.
Event: This message reports an event, not an error
notice
The version of the JUNOS software on the master Routing Engine did not match the version on the TX Matrix platform's master Routing Engine. The version on the backup Routing Engine did match the TX Matrix platform.
Routing Engine lost mastership; exiting
The chassis process (chassisd) running on the master Routing Engine exited, because mastership switched to the other Routing Engine.
Error: An error occurred
error
Contact your technical support representative.
chassisd MAC address allocation error for aedevice-id
The chassis process (chassisd) could not obtain a media access control (MAC) address for the indicated aggregated Ethernet interface because of an internal error.
Error: An error occurred
error
chassisd MAC address allocation exceed error for FPC fpc-slot, PIC pic-slot, port port
The chassis process (chassisd) could not obtain a media access control (MAC) address for the indicated interface because of an internal error.
Error: An error occurred
error
Unable to allocate MAC address for fabric interface device-id
The chassis process (chassisd) could not obtain a media access control (MAC) address for the indicated fabric interface because of an internal error.
Error: An error occurred
error
chassisd MAC address allocation error for IRB
The chassis process (chassisd) could not obtain a media access control (MAC) address for an integrated routing and bridging interface because of an internal error.
Error: An error occurred
error
chassisd MAC address allocation error for VLAN
The chassis process (chassisd) could not obtain a media access control (MAC) address for a vlan interface because of an internal error.
Error: An error occurred
error
Using default MAC address base
The chassis process (chassisd) used the default base media access control (MAC) address.
Event: This message reports an event, not an error
info
function-name: chassisd malloc failed, aborting
The chassis process (chassisd) could not allocate memory. The chassisd process tried to continue functioning, but the lack of memory usually causes the process to fail. An administrator needs to restart it at some point.
Error: An error occurred
error
Contact your technical support representative.
Master PCG (slot pcg-slot) removed; powering down Packet Forwarding Engine complex
The master Packet Forwarding Engine Clock Generator (PCG) was removed. The PCG provides the system clock for all application-specific integrated circuits (ASICs) in the routing platform, so packet forwarding halts until the Packet Forwarding Engine is restarted and a PCG is functioning as master.
Error: An error occurred
critical
Master SCG (slot fru-slot) removed; powering it down
The master SONET Clock Generator (SCG) was removed. The SCG provides the clock for SONET/SDH interface timing, so those interfaces might drop packets and experience other errors until a new clock source is established.
Error: An error occurred
critical
fru-name fru-slot: management bus failed sanity test
Startup tests on the indicated FRU's management bus failed.
Error: An error occurred
error
Contact your technical support representative.
CB settings on chassis-type old-index changed: switch is now 'value', chassis index is now 0xnew-index
A toggle switch on the back of the Control Board on each platform in a routing matrix is set to 'M' (multichassis) on the T640 routing nodes and to 'S' (single-chassis) on the TX Matrix platform. On a T640 routing node, the adjacent dial is set to the node's index number in the routing matrix (0 through 3); on the TX Matrix platform it is set to 0. The setting of the toggle switch, the dial, or both, changed to the indicated values on the indicated platform. The new settings take effect when the routing matrix next reboots.
Event: This message reports an event, not an error
warning
If the changes were accidental, return the toggle and dial to the correct settings before the next reboot. If the changes were intended, disconnect and move the cables on the TX Matrix platform Switch Interface Board (SIB) to the row that corresponds to the T640 routing node's new index number.
Received SIGUSR2 without any interrupts pending
The chassis process (chassisd) received the indicated interrupt signal. The signal normally indicates that an event on the Miscellaneous Control Subsystem (MCS) requires servicing. However, the chassisd process did not find such an event pending. This error does not usually cause component failure.
Error: An error occurred
error
Contact your technical support representative.
function-name evSelectFD: initial pipe create aborted (errno error-code)
The chassis process (chassisd) could not to open a pipe for interprocess communication (IPC) to a component (field-replaceable unit, or FRU).
Error: An error occurred
error
Contact your technical support representative.
Unable to set multilink Frame Relay UNI NNI bundles for PIC pic-slot in FPC fpc-slot
The chassis process (chassisd) could not create multilink Frame Relay user-to-network interface and network-to-network interface (MLFR UNI NNI [FRF.16]) bundles for the indicated Physical Interface Card (PIC).
Error: An error occurred
warning
Contact your technical support representative.
No PCG status
The chassis process (chassisd) could not find an operational Packet Forwarding Engine Clock Generator (PCG). Packet forwarding is halted until a PCG becomes operational.
Error: An error occurred
error
Contact your technical support representative.
No SCG state
The chassis process (chassisd) could not find an operational SONET Clock Generator (SCG). To continue functioning correctly, SONET/SDH interfaces that use an SCG as their clock source must find another source.
Error: An error occurred
error
Contact your technical support representative.
Routing Engine offline: message
The chassis process (chassisd) took the Routing Engine offline.
Event: This message reports an event, not an error
critical
Unable to generate OID: oid (error-message)
The chassis process (chassisd) could not generate an object identifier (OID) for the indicated object.
Error: An error occurred
error
Contact your technical support representative.
Chassis temperature over temperature degrees C (message); routing platform will shutdown in duration seconds if condition persists
The temperature of one or more components (field-replaceable units, or FRUs) exceeded the indicated temperature, which is the upper of two thresholds. The fans (and impellers, if applicable) were in the indicated state. If the temperature does not go below the threshold within four minutes after the chassis process (chassisd) detects this condition, the chassisd process shuts down the routing platform. When this message was logged, the indicated number of seconds remained before shutdown.
Error: An error occurred
error
Increase cooling in the area around the chassis.
Chassis temperature above temperature degrees C description (> duration seconds); powering down all FRUs
The chassis process (chassisd) shut down the routing platform because the temperature of one or more components exceeded the indicated threshold temperature for the indicated amount of time. Continued operation at the excessive temperature could damage the routing platform.
Error: An error occurred
critical
Increase cooling in the area around the chassis.
Using new configuration
The chassis process (chassisd) successfully parsed its configuration file.
Event: This message reports an event, not an error
info
function-name: error-message
While performing an operation on the PCI bus, the chassis process (chassisd) encountered the indicated error.
Error: An error occurred
error
A software or a hardware problem occurred.
Contact your technical support representative.
function-name: peer not connected
The chassis process (chassisd) processed a packet for a peer with an invalid or missing connection.
Event: This message reports an event, not an error
error
In most cases, this error is caused by peers transitioning up and down unexpectedly. The error is usually transient and nonfatal.
Circuit breaker tripped for power supply pem-slot
The circuit breaker was tripped for the indicated power entry module (PEM).
Event: This message reports an event, not an error
warning
Turn on the affected PEM manually.
error-message for power supply pem-slot (status bits: 0xstatus-code); check circuit breaker
The chassis process (chassisd) detected the indicated error condition for the indicated power entry module (PEM).
Event: This message reports an event, not an error
warning
Check the status of the circuit breaker and the input connections.
Unable to power up FPC fpc-slot, because no three-input 240-A power supply is installed
On the T1600 router, the T1600-FPC4 ES Flexible PIC Concentrator (FPC) requires that at least one three-input 240-A power supply be installed. The chassis process (chassisd) did not power on the T1600-FPC4 ES in the indicated slot because the required power supply is not installed.
Error: An error occurred
error
Install at least one three-input 240-A power supply.
Overload condition for power supply pem-slot (status bits: 0xstatus-code);
The indicated power entry module (PEM) reported an output voltage overload condition.
Event: This message reports an event, not an error
warning
There might have been excessive load on the PEM.
Temperature check bit set for power supply pem-slot; airflow might be inadequate
The chassis process (chassisd) detected that the 'temperature check bit' was set in the status bit mask for the indicated power entry module (PEM).
Event: This message reports an event, not an error
warning
The PEM might have exceeded its temperature threshold, possibly because the airflow through it was inadequate.
Power supply pem-slot reports problem; check output voltage
The indicated power entry module (PEM) reported a problem with its output voltage.
Event: This message reports an event, not an error
warning
There might have been excessive load on the PEM.
function-name: fpc-slot
The chassis process (chassisd) detected an FPC in an unsupported slot with six-slot configuration set.
Error: An error occurred
error
function-name: attempt fpc-slot to bring PIC pic-slot in FPC count online timed out; stopped trying
The chassis process (chassisd) tried the indicated number of times to bring the indicated Physical Interface Card (PIC) online, but stopped trying after all attempts failed.
Error: An error occurred
error
Contact your technical support representative.
function-name: attempt to bring PIC pic-slot in FPC fpc-slot online timed out
The chassis process (chassisd) tried to bring the indicated Physical Interface Card (PIC) online. The attempt took longer than the standard time allotted for that operation.
Error: An error occurred
error
Contact your technical support representative.
Unable to create interface devices during attachment of PIC pic-slot in FPC fpc-slot: graceful switchover not supported
The chassis process (chassisd) did not create an interface device for the indicated Physical Interface Card (PIC), because graceful switchover was enabled but is not supported in combination with that PIC type. A PIC must have an interface device to come online, so it remained offline.
Error: An error occurred
error
Remove the PIC or upgrade the JUNOS software.
PIC pic-slot in FPC fpc-slot (PIC type pic-type, version version) had hardware error
The indicated Physical Interface Card (PIC) experienced a hardware error. The chassis process (chassisd) did not bring the PIC online.
Event: This message reports an event, not an error
warning
Contact your technical support representative.
Taking PIC pic-slot in FPC fpc-slot offline: reason
The chassis process (chassisd) took the indicated Physical Interface Card (PIC) offline, for the indicated reason.
Event: This message reports an event, not an error
notice
Unable to generate OID for PIC: pic-name (error-message)
The chassis process (chassisd) could not generate an object identifier (OID) for the indicated Physical Interface Card (PIC).
Error: An error occurred
error
Contact your technical support representative.
Unable to find OID for PIC: i2c-id
The chassis process (chassisd) could not determine the object identifier (OID) for the Physical Interface Card (PIC) with the indicated identifier.
Error: An error occurred
error
Contact your technical support representative.
PIC pic-slot in FPC fpc-slot (type pic-type, version version) will be reset on switchover
The chassis process (chassisd) noted that the Physical Interface Card (PIC) with the indicated characteristics needs to be reset when a graceful switchover occurs.
Event: This message reports an event, not an error
warning
Set speed for so-fpc-slot/pic-slot/port to default-value because configured value current-value is invalid
The chassis process (chassisd) set the speed for the indicated Physical Interface Card (PIC) to the indicated value, because the configured value is either higher than the maximum valid value or lower than the minimum valid value.
Error: An error occurred
error
Reconfigure the PIC with a valid speed.
Hardware version (pic-slot) of PIC fpc-slot in FPC pic-type (PIC type version) is not supported
The chassis process (chassisd) did not bring the indicated Physical Interface Card (PIC) online, because its hardware version is not supported.
Error: An error occurred
warning
The PIC requires a hardware upgrade.
Contact your technical support representative.
Unable to open PID file 'filename': errno error-code
The chassis process (chassisd) could not open the file where it stores its process ID (PID).
Error: An error occurred
error
The chassisd process might have detected that another chassisd process was running and tried to read the file so that it could use the PID recorded there when terminating the other process.
Pipe write error: error-message
The chassis process (chassisd) experienced a fatal error while writing to a pipe.
Error: An error occurred
error
There was no reader for the pipe.
fru-name fru-slot not powering up
The chassis process (chassisd) could not power up the indicated component (field-replaceable unit, or FRU), because the FRU did not respond.
Error: An error occurred
error
Unable to turn off power to fru-name fru-slot; a stand-alone test jumper might be installed
The chassis process (chassisd) could not turn off power to the indicated component (field-replaceable unit, or FRU).
Event: This message reports an event, not an error
warning
A common reason is that a standalone test jumper is installed.
PIM/module in slot fru-slot left offline to avoid exceeding chassis power ratings
The chassis process (chassisd) did not bring online the component (field-replaceable unit, or FRU) in the indicated slot, because doing so causes the total power demand of components in the chassis to exceed the chassis' power ratings. On a J-series Services Router, the component is a Physical Interface Module (PIM) or other module that installs in a PIM slot.
Error: An error occurred
error
Backup Routing Engine became master, because JUNOS version of former master did not match RSD master
The chassis process (chassisd) running on the master Routing Engine on a System-Domain routing node relinquished mastership to the backup Routing Engine in the PSD.
Event: This message reports an event, not an error
notice
The version of the JUNOS software on the master Routing Engine did not match the version on the RSD platform's master Routing Engine. The version on the backup Routing Engine did match the RSD platform.
error-message power supply pem-slot (status bits: 0xstatus-code); status failure
The chassis process (chassisd) detected the indicated error condition for the indicated power supply unit (PSU).
Event: This message reports an event, not an error
warning
Fan Fail for power supply pem-slot
PSU Fan fail bit is set in the status for the indicated power supply unit (PSU)
Error: An error occurred
warning
error-message power supply pem-slot (status bits: 0xstatus-code); Input failure
The chassis process (chassisd) detected the input voltage/warning fault condition for the indicated power supply unit (PSU).
Event: This message reports an event, not an error
warning
Overload condition for power supply pem-slot (status bits: 0xstatus-code);
The indicated power supply unit (PSU) reported an output voltage overload condition.
This message reports an event, not an error
warning
There might have been excessive load on the PSU.
Temperature check bit set for power supply pem-slot; airflow might be inadequate
The chassis process (chassisd) detected that the 'temperature check bit' was set in the status bit mask for the indicated power supply unit (PSU).
Event: This message reports an event, not an error
warning
The PSU might have exceeded its temperature threshold, possibly because the airflow through it was inadequate.
Power supply pem-slot reports problem; check output voltage
The indicated power supply unit (PSU) reported a problem with its output voltage.
Event: This message reports an event, not an error
warning
There might have been excessive load on the PSU.
function-name: '0xvalue' is invalid value for object-name (out of range)
The indicated value was outside the valid range of values for the indicated object.
Error: An error occurred
error
Contact your technical support representative.
Successfully reconnected on soft restart
The chassis process (chassisd) successfully reconnected with each Packet Forwarding Engine after a soft restart.
Event: This message reports an event, not an error
notice
Release mastership notification
The chassis process (chassisd) running on the master Routing Engine received a request to release mastership.
Event: This message reports an event, not an error
info
The Routing Engine was probably rebooting and graceful Routing Engine switchover is configured.
re_init: re routing-engine-slot, out of range
The chassis process (chassisd) could not initialize a Routing Engine because the slot number specified for it was invalid.
Error: An error occurred
error
Routing Engine routing-engine-slot temperature (temperature C) over threshold degrees C
The temperature of the indicated Routing Engine exceeded the indicated temperature, which is the upper of two thresholds.
Error: An error occurred
error
Increase cooling in the area around the chassis.
Routing Engine routing-engine-slot temperature above threshold degrees C for too long; action
The chassis process (chassisd) performed the indicated action because the temperature of the indicated Routing Engine exceeded the maximum threshold for more than four minutes. Continued operation at the excessive temperature could damage routing platform components.
Error: An error occurred
critical
Increase cooling in the area around the chassis.
Routing Engine routing-engine-slot temperature (temperature C) over threshold degrees C, component will shutdown in duration seconds if condition persists
The temperature of the indicated Routing Engine exceeded the indicated temperature, which is the upper of two thresholds. If the temperature does not go below the threshold within four minutes after the chassis process (chassisd) detects this condition, the chassisd process shuts down the indicated component. When this message was logged, the indicated number of seconds remained before shutdown.
Error: An error occurred
error
Increase cooling in the area around the chassis.
Routing Engine routing-engine-slot temperature (temperature C) is above warm temperature limit (threshold C)
The temperature of the indicated Routing Engine exceeded the indicated temperature, which is the lower of two thresholds.
Event: This message reports an event, not an error
error
Increase cooling in the area around the chassis.
Unable to determine the mount point for root directory: error-message
The chassis process (chassisd) could not determine the mount point for the root file system.
Error: An error occurred
error
ifmsg sequence gap expected-value - received-value
The chassis process (chassisd) received a routing socket message out of order.
Event: This message reports an event, not an error
warning
A routing socket message was lost because of excessive load or lack of memory.
Version mismatch: chassisd message version expected-value fru-name message version received-value local IPC version local-ipc-version remote IPC version remote-ipc-version
The chassis process (chassisd) verifies that it supports the revision level or version of a component (field-replaceable unit, or FRU). The revision level for the indicated FRU was unsupported or otherwise invalid.
Error: An error occurred
error
Either a previous software upgrade did not complete successfully, or the chassisd process or FRU did not restart after a successful software upgrade.
Upgrade the software and reboot the routing platform.
fru-name fru-slot temperature is temperature degrees C, which is outside operating range
The temperature sensor on the indicated component (field-replaceable unit, or FRU) reported the indicated temperature, which is outside the acceptable operating range.
Event: This message reports an event, not an error
warning
Some sensors generate erroneous readings when a FRU starts up. When this happens, the chassis process (chassisd) rereads the sensor at a later time.
Serial ID read error: error-code -- error-message
The chassis process (chassisd) could not obtain the Routing Engine's serial number from the kernel because of the indicated error.
Error: An error occurred
warning
function-name: error-message
The chassis process could not configure a requested operational mode for a Switching and Forwarding Module (SFM), for the indicated reason.
Error: An error occurred
info
Possible reasons include (a) the requested mode is available only with certain versions of an application-specific integrated circuit (ASIC) (b) not all SFMs are online as required by the requested mode (c) cross-connect mode cannot be configured if an OC-192c Physical Interface Card (PIC) is installed.
function-name: SFM sfm-slot not online
The indicated Switching and Forwarding Module (SFM) was offline.
Error: An error occurred
error
Contact your technical support representative.
Shutdown reason: reason
Although the chassis process (chassisd) normally does not exit or shut down except when the Routing Engine reboots, it shut down for the indicated reason.
Event: This message reports an event, not an error
warning
SIGPIPE received
The chassis process (chassisd) received a signal indicating that its attempt to write to a pipe failed because the reader (which could be another process or thread) did not exist.
Event: This message reports an event, not an error
error
The entity at the other end of the pipe exited or closed the connection.
smb_read: fpga download not complete: val return-value, action
The system management bus (SMB) could not download field-programmable gate array (FPGA) information and returned the indicated status code. The chassis process (chassisd) took the indicated action.
Error: An error occurred
error
function-name: invalid power supply status code (0xstatus-code)
The chassis process (chassisd) could not set the status (enabled or disabled) for a power supply, because it received the indicated power supply status code, which is invalid.
Error: An error occurred
critical
Contact your technical support representative.
function-name: 'operation' ioctl failed on system management bus (address 0xmemory-address, cmd 0xcommand)
The indicated ioctl() operation failed at the indicated address on the system management bus (SMB).
Error: An error occurred
critical
Contact your technical support representative.
function-name: read() failed on system management bus (address 0xmemory-address)
A read() operation failed at the indicated address on the system management bus (SMB).
Error: An error occurred
critical
Contact your technical support representative.
SNMP trap generated: trap (argument1 value1)
The chassisd process (chassisd) generated the indicated simple network management protocol (snmp) trap with the indicated value.
Event: This message reports an event, not an error
notice
SNMP trap generated: trap (argument1 value1, argument2 value2, argument3 value3, argument4 value4, argument5 value5, argument6 value6, argument7 value7, argument8 value8, argument9 value9, argument10 value10)
The chassis process (chassisd) generated a Simple Network Management Protocol (SNMP) trap with the ten indicated argument-value pairs.
Event: This message reports an event, not an error
notice
SNMP trap generated: trap (argument1 value1, argument2 value2, argument3 value3, argument4 value4, argument5 value5, argument6 value6)
The chassis process (chassisd) generated a Simple Network Management Protocol (SNMP) trap with the six indicated argument-value pairs.
Event: This message reports an event, not an error
notice
SNMP trap generated: trap (argument1 value1, argument2 value2, argument3 value3, argument4 value4, argument5 value5, argument6 value6, argument7 value7)
The chassis process (chassisd) generated a Simple Network Management Protocol (SNMP) trap with the seven indicated argument-value pairs.
Event: This message reports an event, not an error
notice
SPMB slot restarted
The indicated Switch Processor Mezzanine Board (SPMB) restarted.
Event: This message reports an event, not an error
info
Attempt count to restart SPMB slot timed out; action
The chassis process (chassisd) tried the indicated number of times to bring the indicated Switch Processor Mezzanine Board (SPMB) online. The chassisd process performed the indicated action as a result of the failure.
Event: This message reports an event, not an error
error
fru-name failover occurred count times
The indicated packet-switching component or control board failed over to a redundant neighbor the indicated number of times, which exceeds the maximum limit.
Event: This message reports an event, not an error
warning
There is probably a system error.
Contact your technical support representative.
chassisd running in standalone FPC mode mode
The chassis process (chassisd) was running in the indicated standalone Flexible PIC Concentrator (FPC) mode. This message was logged in case the administrator wants it to run in a different mode.
Event: This message reports an event, not an error
warning
function-name: sysctl-error error from sysctl-function-name: error-message (errno error-code)
The chassis process (chassisd) received the indicated error from the indicated sysctl() operation.
Error: An error occurred
error
fru-name temperature of temperature degrees C is above limit (threshold degrees)
The temperature of the chassis, or of the indicated component (field-replaceable unit, or FRU), exceeded the lower of two thresholds. The chassis process (chassisd) increased the speed of all functioning fans (and impellers, if applicable) to full speed. If the temperature did not decrease below the threshold within 4 minutes after this message was logged, the chassisd process shut down the routing platform.
Event: This message reports an event, not an error
error
Increase cooling in the area around the chassis.
function-name: unable to read temperature sensor for fru-name
The temperature sensor for the indicated component (field-replaceable unit, or FRU) either did not respond to a request from the chassis process (chassisd) for a temperature reading or sent a value that is outside the normal operating range.
Error: An error occurred
error
Contact your technical support representative.
Received SIGTERM request, shutting down
The chassis process (chassisd) received the SIGTERM signal, indicating that it should terminate. It began the procedure for clean shutdown and exit, but possibly restarted automatically after exiting.
Event: This message reports an event, not an error
info
function-name: message
The chassis process (chassisd) could not clear the state of the timer it had set to track the timeout period for an event.
Error: An error occurred
error
Unable to schedule timeout for description
The chassis process (chassisd) could not start a timer to track the timeout period for the indicated event. The seriousness of this error depends on the event.
Error: An error occurred
error
Contact your technical support representative.
Null timer ID
The chassis process (chassisd) started a timer to track the timeout period for an event. The timer returned a null identifier, so the chassisd process could not clear the timer.
Error: An error occurred
error
evMainLoop returned return-value (errno error-code)
The chassis process (chassisd) exited unexpectedly and reported the indicated error.
Error: An error occurred
error
function-name: 'value' is invalid value for object-name
The indicated value was specified for the indicated object in a message received by the chassis process (chassisd). The value is invalid for that type of object.
Error: An error occurred
warning
Contact your technical support representative.
FPC with I2C ID of 0xi2c-id is not supported
A Flexible PIC Concentrator (FPC) of the indicated type was installed in the routing platform. The software does not support that FPC type on this platform.
Error: An error occurred
error
Contact your technical support representative.
Model model unsupported with this version of chassisd
The version of the chassis process (chassisd) software that is installed on the routing platform does not support this type of chassis.
Error: An error occurred
warning
Contact your technical support representative.
PIC pic-slot in FPC fpc-slot (type pic-type, version version) is not supported
The indicated Physical Interface Card (PIC) is either not supported on this routing platform or is not supported by the installed version of the chassis process (chassisd) software. The chassisd process did not bring the PIC online.
Error: An error occurred
warning
Contact your technical support representative.
Application mode mode is not supported for PIC pic-slot in FPC fpc-slot
The indicated Physical Interface Card (PIC) does not support the indicated application mode configured for it.
Event: This message reports an event, not an error
warning
Check which application modes are supported for the PIC.
SIB with assembly ID assembly-id is not supported
The chassis process (chassisd) detected the presence of a new Switch Interface Board (SIB) with the indicated assembly ID. The SIB remains offline, because it is not a supported type.
Error: An error occurred
error
Contact your technical support representative.
Version mismatch: chassisd message version expected-value fru-name fru-slot message version received-value local IPC version local-ipc-version remote IPC version remote-ipc-version
As a component (field-replaceable unit, or FRU) comes online, the chassis process (chassisd) verifies that the FRU's revision level or version is supported. The revision level of the indicated FRU was unsupported or otherwise invalid.
Error: An error occurred
error
Either a previous software upgrade did not complete successfully, or the chassisd process or FRU did not restart after a successful software upgrade.
Upgrade the software and reboot the routing platform.
Unable to read voltage from fru-name (group group-id, address address, channel voltage-channel)
The chassis process (chassisd) could not read voltage data from the indicated component (field-replaceable unit, or FRU).
Error: An error occurred
error
Contact your technical support representative.
Unable to initialize voltage sensor for fru-name (group group-id, address address)
The chassis process (chassisd) could not initialize the voltage sensor for the indicated component (field-replaceable unit, for FRU).
Error: An error occurred
error
Contact your technical support representative.
| Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |