SBC_MPS through SENSORMGR
SBC_MPS
%SBC_MPS-3-INTERNAL : An internal IOSd SBC error has been encountered[chars]. | |
---|---|
Explanation | An internal error has been encountered. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SBC_MPS-3-INITFAIL : SBC module initialisation failure: [chars]. | |
---|---|
Explanation | An unexpected condition has occurred which resulted in the module being unable to initialise. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SBC_MPS-3-MAX_RESOURCES : The maximum resource limit has been reached. | |
---|---|
Explanation | The system was asked to allocate more resources, but the maximum resource limit had already been reached |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SBC_MPS-3-ENQUEFAIL : Enqueue of TDL message failed ([chars]). | |
---|---|
Explanation | An unexpected condition has occurred which resulted in configuration or event details not being forwarded. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SBC_MPS-6-UNEXPECTED_TDL : An unexpected message ([chars]) has been received by SBC while in the [chars] state. | |
---|---|
Explanation | An internal message has been received by SBC, but it was not expecting that message at that particular time. The system will ignore the message and continue operation. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SBC_MPS-4-UNEXPECTED_PKT : An unexpected packet for call [dec] has been received by SBC. | |
---|---|
Explanation | A packet been received by SBC for the noted call, but the call was not in a correct state to handle it. The system will ignore the packet and continue operating. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SBC_MPS-3-UNEXPECTED_TIMOUT : An unexpected timeout has been encountered by SBC ([chars]). | |
---|---|
Explanation | A timeout was experienced by the IOSd SBC subsystem, but no such timeout should have occurred. The system will ignore the timeout and continue operating. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SBC_MPS-6-DEACTIVATE_NO_RSP : SBC deactivate response is considered lost. | |
---|---|
Explanation | The response for SBC deactivate can get lost due to FP startup or switchover while deactivation is in progress. |
Recommended Action | SBC can be activated now if needed. |
%SBC_MPS-6-DEACTIVATE_RESPONSE : SBC deactivate is complete. | |
---|---|
Explanation | SBC deactivation can take a while. This happens when SBC deactivation is done in the presence of a lot calls with deactivation-mode set to abort. SBC deactivate is now complete. |
Recommended Action | SBC can be safely activated now if needed. |
%SBC_MPS-4-NEW_MPF_CAPABILITIES : New SBC MPF Capabilities handling failure. | |
---|---|
Explanation | SBC has received a new set of Media Packet Forwarding capabilities from the associated Forwarding Processor that are inconsistent with those already in use. SBC was unable to process these new capabilities online, and will automatically restart. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SBC_MPS-4-TRANSCODE_MPF_CAPABILITIES : Transcoding SBC MPF Capabilities handling failure. | |
---|---|
Explanation | SBC has been unable to prepare a transcoding supported Media Packet Forwarding capabilities message. SBC will not be able to support transcoding functionality. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SBC_MPS-4-MPF_SRTP_CAPABILITIES : Unable to set SRTP capabilities | |
---|---|
Explanation | SBC made an attempt to set the platform capabilities with respect to its handling of SRTP streams and was not successful. SRTP streams will not be handled through the SBC. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SBC_MPS-4-MPF_CAPABILITIES : SBC MPF Capabilities handling failure. | |
---|---|
Explanation | SBC has been unable to properly prepare a Media Packet Forwarding capabilities message. SBC may not be able to support select functionality such as transcoding or SRTP. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
SBC_SPF
%SBC_SPF-3-INTERNAL : An internal IOSd SBC error has been encountered[chars]. | |
---|---|
Explanation | An internal error has been encountered. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SBC_SPF-3-NOT_FOUND : An unsolicited message has been received by SBC ([chars] [int]) | |
---|---|
Explanation | An internal message has been received by SBC, but it was not expecting that message at that particular time. The system will ignore the message and continue operation. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SBC_SPF-3-ENQUEFAIL : Enqueue of TDL message failed ([chars]). | |
---|---|
Explanation | An unexpected condition has occurred which resulted in configuration or event details not being forwarded. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
SCHED_TEST
%SCHED_TEST-6-ERRMSG : This errmsg should print correctly. | |
---|---|
Explanation | |
Recommended Action |
%SCHED_TEST-2-EXITHOOK : Exit routine invoked for process [chars]. | |
---|---|
Explanation | |
Recommended Action |
SCOOBY
%SCOOBY-5-SERIAL_BRIDGE_BLOCK_EVENT : Block [chars]/[dec] of serial bridge [dec] had I/O event [hex] | |
---|---|
Explanation | A serial bridge I/O event has occurred. This event is not serious but is logged for diagnostic purposes. |
Recommended Action | No user action is required. |
%SCOOBY-0-SERIAL_BRIDGE_CRITICAL_ERROR : Reloading [chars] due critical event [hex] in block [chars]/[dec] of serial bridge [dec] | |
---|---|
Explanation | A critical serial bridge I/O event has occurred. |
Recommended Action | The system automatically reloads the hardware component experiencing the error. If the problem persists, copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. |
%SCOOBY-5-SERIAL_BRIDGE_EVENT_RATE : The [chars] event rate of [int] has exceeded the threshold of [int] on serial bridge [dec] interconnect [dec] | |
---|---|
Explanation | A Serial Bridge has experienced a high event rate. This condition is not considered serious, but is logged for diagnostic purposes. This could be due to a hardware or software driver defect. |
Recommended Action | No user action is required. If this message persists, a serial bridge critical message that needs to be addressed will appear. |
%SCOOBY-0-SERIAL_BRIDGE_CRITICAL_ERROR_RATE : Reloading [chars] due to critically high serial bridge error rate. | |
---|---|
Explanation | A Serial Bridge has experienced a persistently high error rate. The condition is serious and the card must be reloaded. This could be due to a hardware or software driver defect. |
Recommended Action | Copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. |
SDFLASH
%SDFLASH-6-DEVICE_ENABLED : SDFlash device enabled | |
---|---|
Explanation | SDFlash device is enabled in the system. |
Recommended Action | No action is required. |
%SDFLASH-1-DEVICE_DISABLED : SDFlash device disabled | |
---|---|
Explanation | SDFlash device is disabled from the system. Please enable it for correct operation of the switch. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
SDLC
%SDLC-4-DROPPED : Dropped SDLC packet from SDLC hold queue | |
---|---|
Explanation | An SDLC frame had to be dropped from the output hold queue, usually because of excessive congestion on the output link. |
Recommended Action | If this message occurs frequently, determine why your SDLC link is being overloaded with data and resolve the cause (typically by either increasing bandwidth to your SDLC line or reducing the load on your link). |
%SDLC-3-NULLPAK : Interface [chars], NULL packet ptr, rvr [dec], vs [dec], vr [dec] | |
---|---|
Explanation | An internal software error occurred in the router's SDLC processing system. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SDLC-3-NOINPIDB : Input idb not set | |
---|---|
Explanation | This is a software error. A frame was given to the SDLC handler to process, but the interface on which the frame arrived is not known. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SDLC-4-FRAMEERR : Interface [chars], Frame error: CF [hex], VS [dec] %c VR [dec], Reason [hex] | |
---|---|
Explanation | A FRMR frame was received. This can be due to a noisy serial line, an overloaded SDLC device, or corrupted data. |
Recommended Action | If this message recurs, service the serial line and the devices attached to it. |
%SDLC-4-INFOBAD : Interface [chars], Info field not permitted | |
---|---|
Explanation | A bad SDLC frame was received. |
Recommended Action | If this message recurs, check the SDLC serial line and the devices attached to it. |
%SDLC-4-CTRLBAD : Interface [chars], Invalid control field | |
---|---|
Explanation | A bad SDLC frame was received. |
Recommended Action | If this message recurs, check the SDLC serial line and the devices attached to it. |
%SDLC-4-N1TOOBIG : Interface [chars], N1 too large | |
---|---|
Explanation | An information frame was received from the other end of the SDLC link that was larger than allowed with the N1 parameter on this link. |
Recommended Action | Either increase the value of the N1 parameter for this interface on the router or reduce the size of the maximum information frame sent by the other end of the link. |
%SDLC-4-INVNR : Interface [chars], Invalid NR value | |
---|---|
Explanation | A bad SDLC frame was received. |
Recommended Action | If this message recurs, check the SDLC serial line and the devices attached to it. |
%SDLC-4-SDLC_ERR : SDLC_ERROR with no poll | |
---|---|
Explanation | A protocol error was detected on a secondary station, but FRMR could not be sent because the station did not own the poll bit. This message indicates either poor line conditions or a faulty SDLC implementation. |
Recommended Action | If this message recurs, run traces on the SDLC line. Copy the error message exactly as it appears, and report it to your technical support representative. |
%SDLC-2-ILLEGSTATE : [chars], illegal state for addr [hex], [chars]([dec]) | |
---|---|
Explanation | An internal SDLC state violation was detected. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SDLC-2-NOPOINTER : AW_SDLC_SEC with no sdllc_llc pointer. | |
---|---|
Explanation | An error condition occurred during SDLLC initiation. |
Recommended Action | No action is required. The SDLLC session will restart without operator intervention. |
%SDLC-3-CONFIGERR : [chars], addr [hex], Sent SNRM, received SNRM. Check link station roles. | |
---|---|
Explanation | A hardware or software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SDLC-4-NOUA : [chars], addr [hex] received command [hex] in response to SNRM, expected UA | |
---|---|
Explanation | The router received a frame other than a UA in response to a SNRM. |
Recommended Action | Check the end station to see if the SNA stack is up and running. |
%SDLC-5-INVLDGRPPOLL : Interface [chars], not configured for group-poll frame, received [hex] | |
---|---|
Explanation | An unnumbered poll (UP) was received with the wrong group poll address. |
Recommended Action | Make sure the group poll address configured on the router matches the one configured in the physical unit macro (GP3174=XX) in the Network Control Program (NCP) generate file. |
%SDLC-4-INVLDGRPCFG : Interface [chars], ignoring group-poll mismatch, UPOLL [hex] | |
---|---|
Explanation | A hardware or software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SDLC-4-BADFRAME : [chars], Received bad SDLC [chars]frame, address [hex], control [hex] | |
---|---|
Explanation | A hardware or software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SDLC-2-NOMEMORY : No memory available: [chars] | |
---|---|
Explanation | The requested operation failed because of a low memory condition. |
Recommended Action | Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. |
%SDLC-3-DLU_ERROR : [chars], DLU failed to close station [hex] before re-opening, [chars]/[chars] | |
---|---|
Explanation | A hardware or software error occurred. |
Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SDLC-4-XID_NOMATCH : [chars], XID mismatch for [hex]. CONNECTION REJECTED | |
---|---|
Explanation | An inbound exchange identification (XID) from a PU 2.0/PU 2.1 node was rejected. The targeted SDLC address is displayed. The XID information is displayed in a subsequent message = SDLLC-6-XID_DISPLAY or SDLLC-6-FORMAT. |
Recommended Action | This is a security feature. Additional information is displayed to help trace the source of the rejected XID. If the message is undesirable, simply remove the XID statement from the router configuration. |
%SDLC-6-XID_DISPLAY : sa [enet] da [enet] ss [hex] ds [hex] [[hex][hex][hex][hex]] | |
---|---|
Explanation | This message supplies the information for the received and rejected XID. |
Recommended Action | See the SDLC-6-XID_NOMATCH error message. |
%SDLC-6-XID_FORMAT : Unsupported XID format received, format [dec] | |
---|---|
Explanation | An inappropriate exchange identification (XID) format was received for this mode of SDLLC operation. Review the type of devices you are connecting with SDLLC to make sure they are supported. |
Recommended Action | See the SDLLC-6-XID_NOMATCH error message. |
SDLLC
%SDLLC-5-ACT_LINK : SDLLC: [chars] LINK address [hex] ACTIVATED: [chars] | |
---|---|
Explanation | An SDLLC media conversion session was activated. |
Recommended Action | No action is required. |
%SDLLC-5-DACT_LINK : SDLLC: [chars] LINK address [hex] DEACTIVATED: [chars] | |
---|---|
Explanation | An SDLLC media conversion session was deactivated. If deactivation is a result of an error condition, this message will include a reason. |
Recommended Action | If the message does not include a description of an error, the deactivation was normal and the message is for information only. If the message does include a description of an error, begin problem analysis. Determine whether session loss is related to LLC2 timers by issuing the debug llc2-err command. If the problem is related to LLC2 timers, consider using SDLLC with the local acknowledgment feature. Copy the error message exactly as it appears, and report it to your technical support representative. |
SEC
%SEC-4-TOOMANY : Box secured, too many options on internal packet | |
---|---|
Explanation | No room for all desired IP header options. Packet discarded. |
Recommended Action | Configure for fewer IP header options. |
%SEC-2-NOOPT : Box secured, no option on internal packet | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SEC-2-NOTSEC : First opt in tcb not BASIC security | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If this message recurs, contact your technical support representative. |
%SEC-2-SECINS : Security opt in tcb not SECINSERT | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SEC-3-NOMAX : No default for NLESO defined | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If this message recurs, copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
%SEC-6-IPACCESSLOGNP : list [chars] [chars] [dec] [IP_address] [chars]-> [IP_address], [dec] packet[chars] [chars] | |
---|---|
Explanation | A packet matching the log criteria for the given access list was detected. |
Recommended Action | No action is required. |
%SEC-6-IPACCESSLOGDP : list [chars] [chars] [chars] [IP_address] [chars]-> [IP_address] ([dec]/[dec]), [dec] packet[chars] [chars] | |
---|---|
Explanation | A packet matching the log criteria for the given access list was detected. |
Recommended Action | No action is required. |
%SEC-6-IPACCESSLOGP : list [chars] [chars] [chars] [IP_address]([dec]) [chars]-> [IP_address]([dec]), [dec] packet[chars] [chars] | |
---|---|
Explanation | A packet matching the log criteria for the given access list was detected. |
Recommended Action | No action is required. |
%SEC-6-IPACCESSLOGRP : list [chars] [chars] [chars] [IP_address] [chars]-> [IP_address], [dec] packet[chars] [chars] | |
---|---|
Explanation | A packet matching the log criteria for the given access list wasdetected. |
Recommended Action | No action is required. |
%SEC-6-IPACCESSLOGS : list [chars] [chars] [IP_address] [dec] packet[chars] [chars] | |
---|---|
Explanation | A packet matching the log criteria for the given access list was detected. |
Recommended Action | No action is required. |
%SEC-6-IPACCESSLOGRL : access-list logging rate-limited or missed [dec] packet[chars] | |
---|---|
Explanation | Some packet matching logs were missed because the access list log messages were rate-limited or no access list log buffers were available. |
Recommended Action | No action is required. |
%SEC-4-SHELFCTLRTELOPT : malformed option on vty%t %c%c%c[dec] len [dec] [chars] | |
---|---|
Explanation | A packet containing shelf controller telnet options was malformed. Options were ignored or truncated. |
Recommended Action | No action is required. |
SEC_LOGIN
%SEC_LOGIN-1-QUIET_MODE_ON : Still timeleft for watching failures is [int] secs, [user: [chars]] [Source: [chars]] [localport: [int]] [Reason: [chars]] [ACL: [chars]] at [chars] | |
---|---|
Explanation | Quiet Mode is ON. No request for connection is accepted other than allowed by the Access List, if configured for the blocking period. Else an implicity *deny all* login's will be in force |
Recommended Action | As all the requests from other sources are blocked check ACL and add any source addr. if needed. |
%SEC_LOGIN-5-QUIET_MODE_OFF : Quiet Mode is OFF, because [chars] at [chars] | |
---|---|
Explanation | Quiet Mode is OFF. Router now operates in normal connection processing mode |
Recommended Action | A notification that the device now operates in normal connection processing mode and the reason why it switched mode is also indicated with the notification. |
%SEC_LOGIN-4-LOGIN_FAILED : Login failed [user: [chars]] [Source: [chars]] [localport: [int]] [Reason: [chars]] at [chars] | |
---|---|
Explanation | Invalid User Name or Password is given from terminal. |
Recommended Action | A notification to indicate that login failed |
%SEC_LOGIN-5-LOGIN_SUCCESS : Login Success [user: [chars]] [Source: [chars]] [localport: [int]] at [chars] | |
---|---|
Explanation | A successful login happened with the device. |
Recommended Action | A notification that login succeeded. |
%SEC_LOGIN-3-INIT_FAILED : Secure Login Initialization failed. [chars] | |
---|---|
Explanation | Initialization of Secure Login Subsystem failed |
Recommended Action | Copy the error message exactly as it appears; include the stack trace; and report it to your technical support representative. |
SENSORMGR
%SENSORMGR-3-NOMEM : Sensor manger failed to allocate memory : [chars] | |
---|---|
Explanation | The sensor manager was not able to add a new threshold node to its database. |
Recommended Action | TBD |