
This chapter describes messages generated by the switch-mapping subsystem.
Critical
Message: <function>: Failed to find DLC for ifIndex <index>Meaning: Invalid Data Access in Link-Layer.
Action: Report this to Avici Customer Support. This is a critical memory/software error.
Message: Ether WKP initialization failedMeaning: This system software component failed during initialization.
Action: Save your system log to a file and contact Avici Customer Support.
Message: LDP WKP initialization failedMeaning: This system software component failed during initialization.
Action: Save your system log to a file and contact Avici Customer Support.
Message: MPLS StatC WKP initialization failedMeaning: This system software component failed during initialization.
Action: Save your system log to a file and contact Avici Customer Support.
Message: NETJOB-SWMAP WKP initialization failedMeaning: This system software component failed during initialization.
Action: Save your system log to a file and contact Avici Customer Support.
Message: PATHMGR WKP initialization failedMeaning: This system software component failed during initialization.
Action: Save your system log to a file and contact Avici Customer Support.
Message: QOS WKP initialization failedMeaning: This system software component failed during initialization.
Action: Save your system log to a file and contact Avici Customer Support.
Message: RTM WKP initialization failedMeaning: This system software component failed during initialization.
Action: Save your system log to a file and contact Avici Customer Support.
Message: STATICMPLS WKP initialization failedMeaning: This system software component failed during initialization.
Action: Save your system log to a file and contact Avici Customer Support.
Message: SWMAP-ARPCM WKP initialization failedMeaning: This system software component failed during initialization.
Action: Save your system log to a file and contact Avici Customer Support.
Message: Swmap Lnk WKP initialization failedMeaning: This system software component failed during initialization.
Action: Save your system log to a file and contact Avici Customer Support.
Message: memory allocation for counter header failedMeaning: An internal software component failed to allocate memory.
Action: Save your system log to a file and contact Avici Customer Support.
Message: memory allocation for counterId failedMeaning: An internal software component failed to allocate memory.
Action: Save your system log to a file and contact Avici Customer Support.
Message: memory allocation for mod_counters_reqT failedMeaning: An internal software component failed to allocate memory.
Action: Save your system log to a file and contact Avici Customer Support.
Message: memory allocation for segment tree failedMeaning: An internal software component failed to allocate memory.
Action: Save your system log to a file and contact Avici Customer Support.
Message: memory allocation for segment work item request failedMeaning: An internal software component failed to allocate memory.
Action: Save your system log to a file and contact Avici Customer Support.
Message: module task initialization failed, <message>Meaning: A Line Card Module software component failed during initialization.
Action: No action required - this is a normal initialization event.
Message: pointer to <address> is not setMeaning: An invalid memory address was detected in the Route Server software.
Action: Report this to Avici Customer Support. This is a critical memory/software error.
Message: server task initialization failed, <message = {mSwMap taskSpawn failed | csm init | events init | tunnel mapping tree resources | ether init | mSwMap taskSpawn failed}>Meaning: A Route Server software component failed during initialization.
Action: No action required - this is a normal initialization event.
Major
Message: <function> <number> num_ofi_entries <number> ofint_tbl_index <number>Meaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: <function> 0x<hexadecimal> already allocated for ifIndex 0x<hexadecimal>Meaning: The specified insegment already exists and we are trying to create it again.
Action: Save your system log to a file and contact Avici Customer Support.
Message: <function>: mtMsgSend failed, ipAddr=<address>Meaning: Inter process communication failed.
Action: Save your system log to a file and contact Avici Customer Support.
Message: Did not find label <number> for inIfindex <number> while deleting insegment.Meaning: An internal software component failed to delete an LSP corresponding to the given insegment.
Action: Save your system log to a file and contact Avici Customer Support.
Message: Registration with FPH failed. STATUS = <number>, RXSTATE = <number>Meaning: An internal software component failed to initialize properly.
Action: Save your system log to a file and contact Avici Customer Support.
Message: SwMap QoS: memory failure during member link downMeaning: Memory Allocation failed in an internal software component
Action: Save your system log to a file and contact Avici Customer Support.
Message: SwMap QoS: memory failure for mod msg in qossm_assignTraffic_handler.Meaning: Memory Allocation failed in an internal software component
Action: Save your system log to a file and contact Avici Customer Support.
Message: SwMap QoS: memory failure for module msg in qossm_getStats_handlerMeaning: Memory Allocation failed in an internal software component
Action: Save your system log to a file and contact Avici Customer Support.
Message: SwMap QoS: memory failure for response in qossm_getStats_handlerMeaning: Memory Allocation failed in an internal software component
Action: Save your system log to a file and contact Avici Customer Support.
Message: SwMap QoS: memory failure when adding member linkMeaning: Memory Allocation failed in an internal software component
Action: Save your system log to a file and contact Avici Customer Support.
Message: SwMap QoS: memory failure when changing buffer ratioMeaning: Memory Allocation failed in an internal software component
Action: Save your system log to a file and contact Avici Customer Support.
Message: SwMap QoS: memory failure when deleting member linkMeaning: Memory Allocation failed in an internal software component
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager Backup inuse notify request has unexpected argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager LDP tunnel notify request has unexpected argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager RRO notify request has unexpected argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager RRO notify request has unexpected argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager TE ADVERTISE notify request has unexpected argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager TE ADVERTISE notify request has unexpected argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager TE ROUTE notify request has unexpected argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager TE ROUTE notify request has unexpected argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager TE STATS notify request has unexpected argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager TE-LSDB message has no argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager TE-LSDB message has no argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager backup inuse notify: socket <number> arg type <number> expected <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager midpoint setup with no argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager midpoint setup with no argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager midpoint setup: socket <number> arg type <number> expected <number>Meaning: An internal software component detected an invalid message
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager midpoint setup: socket <socket> arg type <n> expected <n>Meaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager update rro notify: socket <number> arg type <number> expected <number>Meaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API Path Manager update rro notify: socket <socket> arg type <n> expected <n>Meaning: An internal software component detected an invalid message
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API TE-LSDB: advertisement header damaged, size= <number>Meaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API TE-LSDB: expected type <number> got type <number> size <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API TE-LSDB: expected type <number>got type <number> size <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API TE-LSDB: message too smallMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API TE-LSDB: network adjacency damaged, size= <number>Meaning: An internal message is corrupted
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API TE-LSDB: router adjacency damaged, size= <number>Meaning: An internal message is corrupted
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API TE-LSDB: router adv header damaged, size= <number>Meaning: An internal message is corrupted
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API TE-LSDB: router advertisement damaged, size= <number>Meaning: An internal message is corrupted
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API TE-LSDB: socket <number> identity type <number> expected <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API TE-LSDB: too few argumentsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API TE-LSDB: unknown advertisement type <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API TE-LSDB: unknown argument type <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API bad interface notify argument type <number>Meaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API interface notify with no argumentsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API midpoint teardown with no argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API midpoint teardown: socket <number> arg type <number> expected <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API tunnel state init: socket <number> arg size <number> expected <number>Meaning: An internal message is corrupted.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API tunnel state init: socket <number> arg type <number> expected <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API tunnel state init: socket <number> message type <number> expected <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API tunnel state init: socket <number> size <number> expected <number>Meaning: An internal message is corrupted.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API tunnel state update: socket <number> arg size <number> expected <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API tunnel state update: socket <number> arg type <number> expected <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API tunnel state update: socket <number> message type <number> expected <number>Meaning: An internal software component detected an invalid message
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API tunnel state update: socket <number> size <number> expected <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: ADVERTISE notification has no argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: ADVERTISE notify args: socket <number> identity type <number> expected <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: Backup inuse notify has no argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: Connect to Path Manager failedMeaning: An internal software component failed to initialize properly
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: Create LSP first arg: expected type <number> got type <number> size <number>Meaning: An internal software component has encountered an error due to incorrect arguments.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: Create LSP path arg: expected type <number> got type <number> size <number>Meaning: An internal software component has encountered an error due to incorrect arguments.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: Create LSP request arg damaged, size <number>Meaning: An internal message is corrupted
Action: Contact Avici Customer Support
Message: TE API: Create LSP request has no argsMeaning: An internal software component failed while creating an LSP due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: Create Tunnel request has no argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: Delete LSP arg: expected type <number> got type <number> size <number>Meaning: An internal software component has encountered an error due to incorrect arguments
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: Delete LSP request has no argsMeaning: An internal software component failed while deleting an LSP due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: LDP tunnel notify has no argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: LDP tunnel notify: error <number>Meaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: LDP tunnel notify: expected type <hexadecimal> got type <hexadecimal> size <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: ROUTE notification has no argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: ROUTE notify args: expected type <number> got type <number> size <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: RRO notify has no argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: TE STAT notification has no argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: TE STAT notify arg: expected type <number> got type <number> size <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: TE enable arg: expected type <number> got type <number> size <number>Meaning: An internal software component has encountered an error due to incorrect arguments.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: TE-LSDB notify request has unexpected argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: Tunnel DSCP map expected a compound argMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: Tunnel DSCP map: expected type <number> got type <number> size <number>Meaning: An internal software component has encountered an error due to incorrect arguments.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: Tunnel has wrong DSCP map arg count <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: Tunnel header: expected type <number> got type <number> size <number>Meaning: An internal software component has encountered an error due to incorrect arguments.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: Tunnel member: expected type <number> got type <number> size <number>Meaning: An internal software component has encountered an error due to incorrect arguments.
Action: Contact Avici Customer SupportMinor
Message: TE API: delet LSP message has no argsMeaning: An internal software component failed while deleting an LSP due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: deleting LSP: expected arg type <number> got type <number> size <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: handle_associate_backup: expected size <number> got <number>Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: handle_associate_backup: wrong number of args, got <number>, expected 1Meaning: An internal software component detected an invalid message.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: midpoint response has no argsMeaning: An internal software component failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: midpoint response: expected type <number> got type <number> size <number>Meaning: An internal software component has encountered an error due to incorrect arguments.
Action: Save your system log to a file and contact Avici Customer Support.
Message: TE API: open failed, errno <number>Meaning: An internal software component failed to initialize properly.
Action: Save your system log to a file and contact Avici Customer Support.
Message: Unable to apply <name> ACL on interface <interface>, memory fullMeaning: ACL processing failed for the particular interface
Action: Save your system log to a file and contact Avici Customer Support.
Message: swmap_ipc_read_swmap_dispatcher: got = <number> bytes on socket = <number>, port = <number>, request = <number>Meaning: Inter process communication failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Message: te_ipc_read_swmap_dispatcher: got = <number> bytes on socket = <number>, request = <number>, peer status = <number>, peer port = <number>, my status = <number>, my port = <number>Meaning: Inter process communication failed due to incorrect parameters.
Action: Save your system log to a file and contact Avici Customer Support.
Minor
Message: <string>: hash table for moduleID <number> does not existMeaning: A module table was not found during an attempt to access it.
Action: No action required.
Message: APS: CommMsgDispatcher[<line number>] Receive APS clear DB server messageMeaning: The module has received a clear APS database message from the server. This message is normal even if there is no APS configuration, and can occur when the module has just come up or after an NSR® failover.
Action: If this message occurs when the module is not coming up and the system is not undergoing an NSR® failover, contact Avici Customer Support.
Message: APS: SendDB[<line>] APS init module <module>: Total APS Handles <handles>, downloaded <downloaded handles>Meaning: The server is sending a message to the specified module to initialize its APS database. This message is normal even if there is no APS configuration, and can occur when a module has just come up or after an NSR® failover.
Action: If this message occurs when the specified module is not coming up and the system is not undergoing an NSR® failover, contact Avici Customer Support.
Warning
Message: <Function Name>: hash table for moduleID <Module Id> does not existMeaning: On module down, module hash table to be freed was not found
Action: No action required.
Message: Sending cleanup to module, ModuleId= <Mod_ID>Meaning: A cleanup request is being sent to the specified module.
Action: No action required.
Message: Sending failover command to module, ModuleId= <Mod_ID> flag= <Flag>Meaning: The module is being signaled that NSR® failover has started.
Action: No action required.
Message: SwMap QoS: incorrect <Mod_ID> Id <Num> received in qossm_dscp_mapping_handler.Meaning: The QoS Manager has passed a mapping with an invalid Module ID
Action: Save your system log to a file and contact Avici Customer Support.
Message: mod_req_mpls_failover_state: no-op <Flag>Meaning: An NSR® Fail-over request was received for a non-NSR® capable or a non-MPLS capable module. A flag value of 2 indicates the end of transition.
Action: No action required.
Message: mod_req_set_result_records: module <Mod_ID> init mapping tree doneMeaning: The RSVP Ingress forwarding initialization programming for the module has been completed.
Action: No action required.
Message: swmap_mod_cleanup_interface_mpls_states: Cleaning up interface mpls states for failover.Meaning: Stale MPLS Interface state is being cleaned up upon completion of an NSR® failover.
Action: No action required.
Message: swmap_mod_cleanup_interface_mpls_states: Resetting mplsFailoverState = DONEMeaning: MPLS NSR® failover flags are being reset to default values as normal cleanup upon the completion of an NSR® failover.
Action: No action required.
Message: swmap_mod_cleanup_stale_asic_entries: Cleaning up stale ASIC entries after fail-over.Meaning: Stale Module ASIC entries are being cleaned up upon the completion of an NSR® failover.
Action: No action required.
Message: swmap_remove_old_handles: Removed <Num> old handles and reset <Num> valid handles after HA transitionMeaning: Old handles are being removed from the RRI tree upon completion of an NSR® failover.
Action: No action required.
Message: swmap_rri_alloc: Bad type <Type#> for handle 0d<Handle#>, caller <Caller_ID>Meaning: Module received a Forwarding data (RRI) alloc request for a route with the wrong type.
Action: No action required.
Message: swmap_send_tunnel_mapping_tree: module <Mod_ID> done sending init mapping treeMeaning: The Server has finished sending the RSVP Ingress forwarding initialization programming.
Action: No action required.
Copyright © 2006
Avici Systems Inc.
Avici® and TSR®
is a registered trademark of Avici Systems Inc.
IPriori, Composite Links, SSR, QSR, and NSR® are
trademarks of Avici Systems Inc.
Source
File Name: switch-mapping.fm
HTML File Name: switch-mapping.html
Last Updated: 09/26/06 at 14:21:59