snmp-traps Messages

snmp-traps Messages

This chapter describes messages generated by the snmp-traps subsystem.

Minor
Message: <composite link> <composite link> bandwidth increased by <number> mbit/s
Meaning: The bandwidth of the specified composite link has been increased.

Action: No action required.
Message: <primary> Server <number> in bay <number> slot <slot> is in Admin mode of <admin status> and hot standby mode of <standby mode>, but failed to detect a BackUp Server.
Meaning: The specified primary server lost communication with a backup server. The backup server may be down.

Action: Verify the primary server's standby mode and the backup server's admin status.
Message: <primary> Server <number> in bay <number> slot <number> is in Admin mode of <admin status> and hot standby mode of <standby mode>, has successfully detected a BackUp Server.
Meaning: The specified primary server determined that a backup server has comes up.

Action: No action required.
Message: <primary | backup> server <number> in bay <number> slot <number> down
Meaning: A server module went down.

Action: No action required.
Message: A module has been discovered in bay <number> slot <number> of type <module type>.
Meaning: A module has been discovered by a server or communication with the module is up.

Action: No action required.
Message: BGP has entered the established state with peer <address>, with last error <number> and peer state <number>.
Meaning: BGP has entered the established state with the specified peer.

Action: No action required.
Message: BGP has transitioned from higher state to lower state with peer <address>, with last error <error> and peer state <state>.
Meaning: BGP has transitioned from a higher state to a lower state.

Action: Verify the peer's status, if possible.
Message: Bay Controller communications link in bay <number> slot <number> interface <number> is down.
Meaning: A communications link between the specified bay controller and the other bay controller for this bay has gone down.

Action: Remove and re-insert the two bay controllers within the specified bay. If this message repeats frequently, save the log files and contact Avici customer support.
Message: Bay Controller communications link in bay <number> slot <number> interface <number> is up.
Meaning: A communications link between the specified bay controller and the other bay controller for this bay is now up.

Action: No action required since this message represents the expected behavior. If this message repeats frequently, save the log files and contact Avici customer support.
Message: Bay Controller in bay <number> slot <number> is powered up.
Meaning: The specified bay controller was just powered on.

Action: No action required if the bay controller's behavior was expected. If this message repeats frequently or the power cycle was not expected, save the log files and contact Avici customer support.
Message: Bay Controller in bay <number> slot <number> is restarted.
Meaning: The specified bay controller was just rebooted.

Action: No action required if the bay controller's behavior was expected. If this message repeats frequently or the bay controller reboot was not expected, save the log files and contact Avici customer support.
Message: Bay Controller in bay <number> slot <number> no longer communicating.
Meaning: The specified bay controller has stopped communicating with the rest of the system. This could be caused by either an unexpected restart or a hardware failure.

Action: Verify that all cables between the bay controller and the server are properly connected, then reboot the bay controller. If this condition persists after the reboot, save the log files and contact Avici customer support.
Message: Cooling module <number> in bay <number> (fan <number>) has a communication failure. Last five error codes: <number>,<number>,<number>,<number>,<number>.
Meaning: A fan controller has stopped communicating with the bay controller.

Action: Remove and re-insert the specified blower assembly. If this message repeats frequently, save the log files and contact Avici customer support.
Message: LDP entity with LDP ID: <address>:<label> and entity index <ldp entity> having a path vector limit of <number> does not match the path vector limit of its peer with LDP ID: <address>:<label> which has a path vector limit of <number>
Meaning: A specified LDP entity's path vector limit does not match its peer's path vector limit.

Action: Verify LDP configuration.
Message: Link Status of <interface>f is <status>
Meaning: the GBE link status has changed.

Action: Assure that the change is an expected behavior. If not administratively down, check for alarms on the gbe interface.
Message: Link down on interface with ifIndex <interface> and ifAdminStatus <status>, ifOperStatus <status>.
Meaning: An event triggered the link to an operational DOWN state.

Action: No action required.
Message: Link up on interface with ifIndex <interface> and ifAdminStatus <admin status>, ifOperStatus <status>.
Meaning: An event has triggered the link to operational UP state

Action: No action required.
Message: Module in bay <number> slot <number> is powered up.
Meaning: The specified routing module was just powered on.

Action: No action required if the routing module's behavior was expected. If this message repeats frequently or the power cycle was not expected, save the log files and contact Avici customer support.
Message: Module in bay <number> slot <number> is restarted.
Meaning: The specified routing module was just rebooted.

Action: No action required if the routing module's behavior was expected. If this message repeats frequently or the routing module reboot was not expected, save the log files and contact Avici customer support.
Message: Module in bay <number> slot <number> of type <module type> has lost communication.
Meaning: A module has lost his communication or it is down.

Action: No action required if the behavior is expected. Otherwise, verify communication line with server.
Message: Module in bay <number> slot <number> with admin status <status> is no longer communicating.
Meaning: A specified module has lost communication with the server

Action: No action required if the module's behavior was expected. Otherwise, verify the module admin status.
Message: OSPF with routerId <router> had interface state change on non-virtual interface <interface> (address less <index>) to state <new state>.
Meaning: Log message for the IntfStateChange Trap indicating an interface state change. The new interface state is as per the ospfIfState object of the OSPF-Mib

Action: Verify the connection with the peer router.
Message: OSPF with routerId <router> had interface state change on virtual interface area <number>, neighbor <number> to state <state>.
Meaning: Log message for the VirtualIntfStateChange Trap indicating a virtual interface state change. The virtual interface new state is as per the ospfVirtIfState object from the OSPF-Mib.

Action: Verify the connection with the virtual router.
Message: OSPF with routerId <router> had non-virtual neighbor state change with neighbor <neighbor> (address less <address>) (router id <number>) to state <state>.
Meaning: Log message for the NbrStateChange Trap indicating a neighbor state change. The new neighbor state is as per the ospfNbrState object from the OSPF-Mib.

Action: No action required.
Message: OSPF with routerId <router> had virtual neighbor state change with neighbor in area <area> (router id <number>) to state <state>.
Meaning: Log message for the VirtNbrStateChange Trap indicating a neighbor state change. The new neighbor state is as per the ospfVirtNbrState object of the OSPF-Mib.

Action: No action required.
Message: OSPF with routerId <router> received a bad packet on non-virtual interface <address> (address less <index>). It came from <address> with a packet type <number>. Error code <number>
Meaning: Log for ospfIfRxBadPacket trap signifies that an OSPF packet has been received on a non-virtual interface that cannot be parsed.

Action: No action require.
Message: OSPF with routerId <router> received a bad packet on virtual interface area <area>. It came from <address> with a packet type <number>. Error code <number>
Meaning: Log for ospfVirtIfRxBadPacket trap signifies that an OSPF packet has been received on a virtual interface that cannot be parsed.

Action: No action required.
Message: Power rail <number> in bay <number> used for discovery of slots <number> to <number> has a major voltage problem (<number> Volts).
Meaning: The voltage measured on the specified power rail is not normal (too low).

Action: Check the incoming voltage levels and reboot the bay controller. If this condition persists after the reboot, save the log files and contact Avici customer support.
Message: Power rail <number> in bay <number> used for discovery of slots <number> to <number> has a normal voltage (<number> Volts).
Meaning: The voltage measured on the specified power rail is at a normal level.

Action: No action required since this message represents the expected behavior. If this message repeats frequently, save the log files and contact Avici customer support.
Message: Power supply rail <number> in bay <number> has a normal voltage reading. (<number> Volts).
Meaning: The incoming voltage measured on the specified power supply is at a normal level.

Action: No action required since this message represents the expected behavior. If this message repeats frequently, save the log files and contact Avici customer support.
Message: Power supply rail <number> in bay <number> has a voltage problem. (<number> Volts).
Meaning: The incoming voltage measured on the specified power supply is outside normal limits (too high or too low).

Action: Correct any problems with the incoming power supplies and reboot the bay controller. If the incoming power supplies appear to be within normal limits and this condition persists after the reboot, save the log files and contact Avici customer support.
Message: Primary server <n> in bay <area> slot <slot> heartbeat down
Meaning: This message indicates that the warm stand-by server has lost save your system log to a file, and contact with the primary server.

Action: Check server to server connection.
Message: SNMP agent restarted, and configuration may have changed.
Meaning: This is a normal message indicating that the SNMP agent has just started (cold start).

Action: None.
Message: SNMP authentication error from IP address <address>.
Meaning: SNMP failed to authenticate access from the remote host.

Action: Verify the User ID and password.
Message: Secondary server <n> in bay <area> slot <slot> down
Meaning: This message indicates that the warm standby server has stopped responding to the primary server.

Action: If the warm standby server was removed or turned administratively off, then this is a normal message. Otherwise, save your system log to a file, and contact Avici Customer Support.
Message: Server <number> in bay <number> slot <number> is running an incompatible software image. <incompatibility>
Meaning: A specified Server is running an incompatible package file software image.

Action: Verify software versions of ALL components and modules.
Message: Server <number> in bay <number> slot <number>: Configuration changed by <user name>.
Meaning: The router's default configuration file has been changed.

Action: If the configuration file should not have been changed, restore the original configuration file before the router is rebooted. Otherwise, no action required.
Message: Server <number> in bay <number> slot <slot>: User <user name> - Authentication Failure.
Meaning: An attempt to log in to the server failed due to an authentication failure

Action: None or attempt to loggin again.
Message: Server access module to bay <number> slot <number> up (<primary | backup> connected to server interface <ethernet>).
Meaning: The specified server access module (SAM) is UP

Action: No action required.
Message: Server attached module to bay <number> slot <number> down (<server type> connected to server interface <interface>).
Meaning: This message indicates that the server attached module (SAM) in slot <slot_number> has stopped communicating with the server.

Action: If the module that was the server attached module has been removed or placed administratively down, this is an expected message. Otherwise, save your system log to a file and contact Avici Customer Support.
Message: Sonet event on link <interface>f: <path layer/threshold event>1
Meaning: The specified path layer SONET alarm has been received, or threshold event has occurred, on the indicated link.

Action: Check the link in accordance the specific alarm or threshold.
Message: Sonet link POS <bay>/<slot>/<port> has new adminStatus up and operStatus down
Meaning: Change in operational state of a particular POS interface.

Action: None.
Message: Sonet link POS <bay>/<slot>/<port> has new adminStatus up and operStatus up
Meaning: Change in operational state of a particular POS interface.

Action: None.
Message: Two or more fans failed in bay <number>.
Meaning: Two or more fans in the specified bay have reported errors. This may result in an insufficient flow of cooling air.

Action: See other messages for the cause(s) of the primary failures. Resolve those failures so fans return to working order. If unable to resolve this issue, contact Avici customer support.
Message: [index <number>] <composite link> link up, member interface <number> is now up
Meaning: A composite link is up and the specified member interface are up.

Action: No action required.

Information
Message: Primary server <n> in bay <area> slot <slot> heartbeat up
Meaning: This message indicates that the warm stand-by server has established communication with the primary server.

Action: None.
Message: Sonet event on link POS <bay>/<slot>/<port>: Loss Of Frame (LOF) Failure
Meaning: SONET has lost frame synchronization.

Action: Check signal types and clocking on both sides of link.
Message: Sonet event on link POS <bay>/<slot>/<port>: Loss Of Signal (LOS) Failure
Meaning: The optical SONET signal has been lost.

Action: Check interface cables and connections.

   Source File Name: snmp-traps.fm
    HTML File Name: snmp-traps.html
    Last Updated: 09/26/06 at 14:21:56

snmp-traps Messages

Minor

Information

Please email suggestions and comments to: doc@avici.com