management Messages

management Messages

This chapter describes messages generated by the management subsystem.

Critical
Message: Failed to get buffer, in function rmonAlarmSend line <line>
Meaning: The system has run out of memory.

Action: Save your system log to a file and contact Avici Customer Support.
Message: ModuleFSM: Configuration Error; Incorrect fabric version <major>.<minor> in bay <area>, slot <slot>
Meaning: The specified Line Card Module is of an unsupported version

Action: Check the module type and verify supported version number. If the problem persists, save your system log to a file and contact Avici Customer Support.
Message: ModuleFSM: Configuration error; Discovered <type> module in bay <area>, slot <slot> configured for <module type>
Meaning: The specified Line Card Module is not properly configured. The module type in the config file does not match the module discovered.

Action: Verify Module type and system running configuration. If the problem persists, save your system log to a file and contact Avici Customer Support.
Message: ModuleFSM: Discarded unknown event <number> for module in bay <area>, slot <slot>
Meaning: The Route Server received an unknown event from the Line Card Module.

Action: This can occur infrequently and should not have an operational effect. If the problem persists save your system log to a file and contact Avici Customer Support.
Message: ModuleFSM: Failed to configure <type> module in bay <area>, slot <slot>
Meaning: The specified Line Card Module is not properly configured.

Action: Check the running configuration. If the problem persists, save your system log to a file and contact Avici Customer Support.
Message: ModuleFSM: Failed to create context for module in bay <area>, slot <slot>; error <number>
Meaning: The Bay Controller is unable to monitor the specified Line Card Module.

Action: Save your system log to a file and contact Avici Customer Support.
Message: ModuleFSM: Failed to initialize <type> module in bay <area>, slot <slot>
Meaning: The specified Line Card Module failed to initialize.

Action: Save your system log to a file and contact Avici Customer Support.
Message: ModuleFSM: Unknown alarm message <id>, code <value>
Meaning: The Route Server received an unknown alarm from a Line Card Module.

Action: Check module configuration. If situation persists, call customer service
Message: RPC: system error, in function moduleConfigTask(), <name>
Meaning: The Route Server to Line Card Module communication was not properly initialized.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Task tBaySpoof taskSpawn error <number>
Meaning: A system software component failed during initialization.

Action: Save your system log to a file and contact Avici Customer Support.
Message: aviciInit4(): moduleFsmMsgSend failed for module in bay <number>
Meaning: The Bay Controller failed to communicate with a Line Card Module.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bad value, in function bayLeaveActive, status
Meaning: A bad status message was received from a Bay Controller.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bayCallbacks(): Timeout while waiting for callback lock! <number>
Meaning: The Route Server to Bay Controller communication has failed.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bayFsm(): No memory for operation
Meaning: The system has run out of memory.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bayFsmCallbackDereg(): Timeout while waiting for callback lock! <number>
Meaning: The Route Server to Bay Controller communication has failed.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bayFsmCallbackReg(): No memory for operation
Meaning: The system has run out of memory.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bayFsmCallbackRegTimeout(): Timeout while waiting for callback lock! <number>
Meaning: The Route Server to Bay Controller communication has failed.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bayFsmInit(): Unable to create callback lock! <number>
Meaning: The Route Server to Bay Controller communication has failed during initialization.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bayFsmTask(): pipe open of <name> failed! <number>
Meaning: The Route Server to Bay Controller communication has failed.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bayFsmTask(): select failed! <number>
Meaning: The Route Server to Bay Controller communication has failed.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bayFsmTask(): select failed! <number>
Meaning: The Composite-Link software component failed.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bayFsmTaskInit(): taskSpawn failed! <number>
Meaning: The Route Server to Bay Controller communication has failed during initialization.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bayMonFlipInterfaces(): Failed to bind monitoring socket! <number>
Meaning: The Route Server was unable to monitor a secondary Bay Controller.

Action: Verify that bay controllers are installed in both slots. If the problem persists, save your system log to a file and contact Avici Customer Support.
Message: bayMonFlipInterfaces(): Failed to get monitoring socket! <number>
Meaning: The Route Server was unable to monitor a secondary Bay Controller.

Action: Verify that bay controllers are installed in both slots. If the problem persists, save your system log to a file and contact Avici Customer Support.
Message: bayMonFlipInterfaces(): Failed to join multicast group! <number>
Meaning: The Route Server to Bay Controller communication has failed.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bayMonMain(): Failed to bind monitoring socket! <number>
Meaning: The Route Server was unable to monitor a secondary Bay Controller.

Action: Verify that bay controllers are installed in both slots. If the problem persists, save your system log to a file and contact Avici Customer Support.
Message: bayMonMain(): Failed to connect bay monitor timer! <number>
Meaning: The Route Server to Bay Controller communication has failed.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bayMonMain(): Failed to create bay monitor timer! <number>
Meaning: The Route Server to Bay Controller communication has failed.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bayMonMain(): Failed to get monitoring socket! <number>
Meaning: The Route Server was unable to monitor a secondary Bay Controller.

Action: Verify that bay controllers are installed in both slots. If the problem persists, save your system log to a file and contact Avici Customer Support.
Message: bayMonMain(): Failed to join multicast group! <number>
Meaning: The Route Server to Bay Controller communication has failed.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bayMonMain(): Failed to set bay monitor timer! <number>
Meaning: The Route Server to Bay Controller communication has failed.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bayMonMain(): Too many errors in recvfrom(), exiting task
Meaning: The Route Server to Bay Controller communication has failed.

Action: Save your system log to a file and contact Avici Customer Support.
Message: baySendFsmMsg(): pipe error! <number>
Meaning: The Route Server to Bay Controller communication has failed.

Action: Save your system log to a file and contact Avici Customer Support.
Message: baySendFsmMsg(): pipe write error! <number>
Meaning: The Route Server to Bay Controller communication has failed.

Action: Save your system log to a file and contact Avici Customer Support.
Message: bayServerRegister(): No memory for operation
Meaning: The Bay Controller has run out of memory.

Action: Save your system log to a file and contact Avici Customer Support.
Message: m2mCmdTaskInit taskSpawn error <number>
Meaning: The Line Card Module to Line Card Module communication failed.

Action: Save your system log to a file and contact Avici Customer Support.
Message: m2mCmdTaskMain: Failed to create BamBamSr msg queue
Meaning: The Line Card Module to Line Card Module communication failed.

Action: Save your system log to a file and contact Avici Customer Support.
Message: moduleCompLnkTaskInit(): taskSpawn failed! <number>
Meaning: The Composite-Link software component failed during initialization.

Action: Save your system log to a file and contact Avici Customer Support.
Message: moduleFsmTask(): select failed! <number>
Meaning: The Route Server to Line Card Module communication has failed.

Action: Save your system log to a file and contact Avici Customer Support.
Message: moduleFsmTaskInit(): taskSpawn failed! <number>
Meaning: The Route Server to Line Card Module communication has failed during initialization.

Action: Save your system log to a file and contact Avici Customer Support.
Message: rmonAlarmSvcLoop(): select failed! <number>
Meaning: The RMON software service has failed

Action: Save your system log to a file and contact Avici Customer Support.

Major
Message: <function> : bad message to transport. ClassId <number>, qos <value>
Meaning: The message transport detected a bad message.

Action: Save your system log to a file and contact Avici Customer Support.
Message: <registration> registration late for bay controller ID <number> (previous <time>, current <time>)
Meaning: The server is not registering often enough with the specified bay controller, either itself or for slot ownership.

Action: This message usually indicates a transient condition and provides debugging information. If this message repeats frequently, save the log files and contact Avici customer support.
Message: <task>(): BayController ID <number> is timing out, lifetime = <number>
Meaning: Bay controller is timing out.

Action: Check the status of the bay controller and verify the cables between the bay controller and the server are properly connected.
Message: <function>(): Successfully changed bay interface, current interface is eth<number>
Meaning: The server has changed the interface over which it attempts to communicate with bay controllers.

Action: Check the status of the bay controllers and verify the cables between each bay controller and the server(s) are properly connected. If the bay controllers appear to be working, but the problem persists, save your system log to a file and contact Avici customer support.
Message: Bay <area>, controller <slot> - detected an invalid action in state <number>
Meaning: An invalid action had been detected by Bay controller in a certain state.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Bay <area>, controller <slot> - detected an invalid event in bay status message in state <number>
Meaning: The bay controller detected an invalid event in bay status message.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Bay <area>, controller <slot> - failed in registration in slot <slot>
Meaning: The bay failed to register for a slot.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Bay <area>, controller <slot> - received an invalid event in state <number>
Meaning: An invalid event had been received by Bay controller in a certain state.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Bay <area>, controller <slot> in state <number> - is about going down
Meaning: The bay is going down.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Bay Controller ID <number> was in state <state> ... going down
Meaning: The specified bay controller is starting to reboot.

Action: No action required if expected. If this message repeats frequently or the bay controller reboot was not expected, save the log files and contact Avici customer support.
Message: Callback failed in function <function>
Meaning: The bay failed to register an event.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Config task Unexpectedly failed to get module context for module in bay <area>, slot <slot> in function <function>
Meaning: Module software component failed to get module context for module in the bay controller.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Failed to send module start msg in function <function> for module in bay <number>, slot <slot>
Meaning: The specifiled line Card Module failed during the initialization.

Action: Check configuration and specifiled module. If the problem persists, contact Avici Customer Support.
Message: In function <function> : bad message to transport (unknown clas id) with ClassId <class id> and qos <QoS>
Meaning: The message transport detected an unknown class id message.

Action: Save your system log to a file and contact Avici Customer Support.
Message: In function <function>: message transport detected an unknown QOS with classId <number>, qos <value>
Meaning: The message transport detected an unknown QOS with class id and qos.

Action: Save your system log to a file and contact Avici Customer Support.
Message: In function <function>: message transport detected bad message length <length>
Meaning: The message transport detected bad message length.

Action: Save your system log to a file and contact Avici Customer Support.
Message: In function <function>: message transport failed to free msg. classId <number>, qos <value>
Meaning: The message transport failed to free msg with the class id and the qos.

Action: Save your system log to a file and contact Avici Customer Support.
Message: In funtion <function>: message transport detected a class which was not created yet for classId <number>
Meaning: The message transport detected a class which was not created yet.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Invalid bay <area>, controller <slot> detected by the bay controller in function <function>
Meaning: The bay controller detected an invalid bay ID

Action: Save your system log to a file and contact Avici Customer Support.
Message: Invalid message in function <function>
Meaning: Invalid message received in Bay controller.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Module software component: Discard event <event> (in state <name>) for module in bay <area>, slot <slot>
Meaning: Module software component discarded event in a state in the bay controller.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Module software component: Discarded invalid event for unknown module in bay <area>, slot <slot>
Meaning: Module software component discarded invalid event message for unknown module in the bay controller.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Module software component: Discarded message containing invalid version: <major>, <minor>
Meaning: Module software component discarded message containing invalid version.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Module software component: Error configuring module <name> in bay <area>, slot <slot>
Meaning: Module software component was error in configuring module in the bay controller.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Module software component: Error configuring module <name> in bay <area>, slot <slot>
Meaning: Module software component encountered error while attempting to auto-upgrade module in the bay operational image to the release.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Module software component: Error occurred while attempting to auto-upgrade module in bay <area>, slot <slot> Switch Card FPGA image successfully auto-upgraded to Release <number>.
Meaning: Module software component encountered error while attempting to auto-upgrade module in the bay Switch Card FPGA image successfully auto-upgraded to the release.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Module software component: Failed to configure module in bay <area>, slot <slot> due to incompatible image <name>
Meaning: Module software component failed to configure module in the bay due to incompatible image.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Module software component: Keepalive Down in bay <area>, slot <slot>
Meaning: Module software component: keepalive down in the bay.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Module software component: Module in bay <area>, slot <slot> has not been rebooted because a module's romburn has failed
Meaning: Module software component failed to reboot the module in the bay because a module's romburn has failed

Action: Save your system log to a file and contact Avici Customer Support.
Message: Module software component: Reboot of module in bay <area>, slot <slot>
Meaning: Module software component started reboot module.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Module software component: Slot Authorization failed (<number>) for module in bay <area>, slot <slot> in function <function>
Meaning: Module software component failed in slot authorization for a module in the bay controller.

Action: Save your system log to a file and contact Avici Customer Support.
Message: ModuleFSM: Discarded invalid Rediscovered event for unknown module in bay <area>, slot <slot>
Meaning: IPriori cannot properly determine the state of this module.

Action: When this happens, the module is persisting even though it is no longer in communication with the server. The module should be rebooted by physically removing and reinserting it.
Message: ModuleFSM: Discarded message containing invalid module ID <module>
Meaning: Module software component discarded message containing invalid module ID.

Action: Save your system log to a file and contact Avici Customer Support.
Message: ModuleFSM: Error occurred while attempting to auto-upgrade module in bay <area>, slot <slot> LineCard FPGA image to Release <major>.<minor>.<build>.<patch>.
Meaning: Module software component encountered error while attempting to auto-upgrade module in the bay LineCard FPGA image to the release.

Action: Save your system log to a file and contact Avici Customer Support.
Message: ModuleFSM: Error occurred while attempting to auto-upgrade module in bay <area>, slot <slot> POST image to Release <major>.<minor>.<build>.<patch>.
Meaning: Module software component encountered error owhile attempting to auto-upgrade module in the bay <bay_number> POST image to the release.

Action: Save your system log to a file and contact Avici Customer Support.
Message: ModuleFSM: Failed to configure module in bay <number>, slot <slot> due to incompatible <module> image
Meaning: Module's image is not compatible with server's image.

Action: Check the specific image of the module which is incompatible
Message: ModuleFSM: Keepalive Down in bay <area>, slot <slot>
Meaning: This message indicates that the server can no longer communicate with this module.

Action: Save Your System Log To A File, And Contact Avici Customer Support unless the module is down for administrative
Message: Recv failed on moduleCompLnkSocket
Meaning: Composite link task failed to read from socket.

Action: Save your system log to a file and contact Avici Customer Support.
Message: Recv failed on moduleFsm_socket
Meaning: Module software component failed to receive data from socket.

Action: Save your system log to a file and contact Avici Customer Support.
Message: The bay controller detected an invalid state <state> in bay status message in function <function>
Meaning: The bay controller detected an invalid state in bay status message.

Action: Save your system log to a file and contact Avici Customer Support.
Message: The bay controller received a message from an invalid bay <slot> in function <function>
Meaning: The bay controller received a message from an invalid bay.

Action: Save your system log to a file and contact Avici Customer Support.
Message: The bay failed to received message in function <function> with error number <number>
Meaning: The bay failed to received message.

Action: Save your system log to a file and contact Avici Customer Support.
Message: The bay successfully changed the ethernet interface to a new interface <address> in function <function>
Meaning: The bay successfully changed ethernet interface to a backup link

Action: Check the state of the original link to figure out why it went down in the first place. If problem persists, Save your system log to a file and contact Avici Customer Support.
Message: no transport to NE <IP> in function <function>
Meaning: Server failed to send message to the network entity.

Action: Check iIF configure. Contact Avici Customer Support if it persists.
Message: operation not allowed, in function <function>, <event>
Meaning: An enexpected transient condition occurred. Debug will provide information.

Action: Save the log files and contact Avici customer support.
Message: ran out of memory, in function <function>, <string>
Meaning: Server ran out of memory.

Action: Save your system log to a file and contact Avici Customer Support.

Minor
Message: <task>(): BayController ID <number> is timing out, lifetime = <number>
Meaning: Bay controller is timing out.

Action: Check the status of the bay controller and verify the cables between the bay controller and the server are properly connected.
Message: <function>(): Server registration failed for Bay Controller ID <number> (<error>)
Meaning: The server failed to register with a bay controller for ownership of slots within a bay.

Action: Usually indicates a transient condition and provides debugging information. If this message repeats frequently, save the log files and contact Avici customer support.
Message: <function>(): detected two active bay controllers in bay <number>
Meaning: This is a normal message generated when bayFSM detects two active bay controllers in the same bay.

Action: Save your system log to a file and contact Avici Customer Support.
Message: BayController ID <n> going active
Meaning: This is a normal message generated when one bay controller does not detect another active bay controller, so it becomes the active bay controller

Action: None
Message: ModuleFSM: Automatically generated default configuration for <module> module in bay <area>, slot <slot>
Meaning: This is a normal message indicating that the server has detected this module and given it the default configuration.

Action: Finish configuring the module
Message: ModuleFSM: Module in bay <number>, slot <slot> successfully completed the server initiated reboot
Meaning: Module is succesfully rebooting. The module's bootrom image is not compatible with the server and module. Bootrom upgrade has failed.

Action: Module bootrom image needs to be changed.
Message: ModuleFSM: Received <event> event (in state <state>) for module in bay <number>, slot <slot>
Meaning: Module FSM received the specified event while in the valid specified state.

Action: Actions taken based on event and state of Module FSM as specified in Module FSM table.

Warning
Message: <task>(): BayController ID <number> is timing out, lifetime = <number>
Meaning: Bay controller is timing out. Lifetime is greater than 16, less than 24

Action: Check Status of bay controller
Message: <function>(): Server registration failed for Bay Controller ID <number> (<error>)
Meaning: An unexpected transient condition occurred and prdebugging information is provided. If this message repeats frequently, save the log files and notify Avici Customer Support.

Action: If this message repeats frequently, save the log files and contact Avici customer support.
Message: [<message>:<interface> <string>] <string>
Meaning: A generic warning in LME sub-system, e.g., indicating invalid interface or interface information cannot be found.

Action: Save your system log to a file and contact Avici customer support.
Message: no client, in function set_logging, serverId <n>
Meaning: This message indicates a problem with the logging system.

Action: Configure a logging client
Message: operation not allowed, in function <function>, <event>
Meaning: An enexpected transient condition occurred. Debug will provide information.

Action: Save the log files and contact Avici customer support.

Information
Message: ModuleFSM: Authorized module in bay <area>, slot <slot>
Meaning: This is a normal message indicating that the bay controller has authorized this module to boot.

Action: None.
Message: ModuleFSM: Configuring <module> module in bay <area>, slot <slot>
Meaning: This is a normal message indicating that the server has finished configuring this module.

Action: None.
Message: ModuleFSM: Discarded invalid Unreachable event for unknown module in bay <area>, slot <slot>
Meaning: This message indicates that a module that was not previously configured, is no longer reachable via the bay controller.

Action: None.
Message: ModuleFSM: Discovered module in bay <area>, slot <slot>
Meaning: This is a normal message indicating that the bay controller has detected a module in this slot.

Action: None.
Message: ModuleFSM: Keepalive Up in bay <area>, slot <slot>
Meaning: This is a normal message indicating that the module is now up and ready to be configured by the server.

Action: None.
Message: ModuleFSM: Successfully configured <module> module in bay <area>, slot <slot>
Meaning: Module configuration has been successful loaded into a module.

Action: None.
Message: RPC: can't send, in function get_afviciBayCoAlarmEntry, in bay <area> index <n>
Meaning: This message indicates that IPriori had an error processing an internal communications request.

Action: Excessive instances of this message could indicate a configuration problem. Save Your System Log To A File, And Contact Avici Customer Support if you see this message more than ten (10) times a day.
Message: RPC: can't send, in function set_logging, in bayController <n>/<n>
Meaning: This message indicates that IPriori had an error processing an internal communications request.

Action: Excessive instances of this message could indicate a configuration problem. Save Your System Log To A File, And Contact Avici Customer Support if you see this message more than ten (10) times a day.
Message: RPC: timeout, in function set_ppp_interfaceEntry, bay <area> slot <slot> port <number>
Meaning: This message indicates that IPriori had an error processing an internal communications request.

Action: Excessive instances of this message could indicate a configuration problem. Save Your System Log To A File, And Contact Avici Customer Support if you see this message more than ten (10) times a day.

   Source File Name: management.fm
    HTML File Name: management.html
    Last Updated: 09/26/06 at 14:21:24

management Messages

Critical

Major

Minor

Warning

Information

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