TN through TUN
TN
%TN-3-READLINE : Unknown return code [dec] from telnet_readline() | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If any message recurs, call your technical support representative for assistance. |
%TN-3-BADSTATE : Illegal state [dec] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If any message recurs, call your technical support representative for assistance. |
%TN-2-BADLOGIN : Bad login string pointer [hex] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If any message recurs, call your technical support representative for assistance. |
%TN-2-BADCONN : Bad conn pointer [hex] closing all connections on terminal line [dec] | |
---|---|
Explanation | An internal software error occurred. |
Recommended Action | If any message recurs, call your technical support representative for assistance. |
TN3270
%TN3270-2-INP_OVF1 : Input Buffer overflow | |
---|---|
Explanation | A problem in TN3270 protocol was detected. Eight KB (8192) bytes of data were received without a TN3270 end-of-packet indicator. The TN3270 buffer overflowed. |
Recommended Action | Copy this error message exactly as it appears, and contact your technical support representative for assistance. |
TPLUS
%TPLUS-3-FORKFAIL : Failed to fork process for [chars]. | |
---|---|
Explanation | Quite likely, we ran out of memory. Other explanations are possible. |
Recommended Action | If this message recurs, call your technical support representative for assistance. |
%TPLUS-3-UNKNOWNTYPE : TPLUS: [hex] Unknown Request type [int]. | |
---|---|
Explanation | Unknown request type in client request |
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. |
TR
%TR-2-PANICTYPE : Unit [dec], [chars] error | |
---|---|
Explanation | This message is similar to the %TR-3-PANIC error message, but indicates a nonfatal error. This message appears in very unusual situations that should not arise in normal operation. |
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. |
%TR-2-PANIC : Unit [dec], panic %-08x %-08x %-08x | |
---|---|
Explanation | The Token Ring monitor firmware detected a fatal error that indicates an impending interface failure. |
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. |
%TR-2-PANICINF : Unit [dec], PI %-08x %-08x %-08x %-08x %-08x %-08x | |
---|---|
Explanation | This message is similar to the %TR-3-PANIC error message, but indicates a nonfatal error. This message appears in very unusual situations that should not arise in normal operation. |
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. |
%TR-3-BADMUL : [chars]: Can't set address to a multicast ([enet]) | |
---|---|
Explanation | An attempt was made to set the Token Ring interface MAC address to a reserved multicast address. |
Recommended Action | Check your configuration. Make sure that your XNS and/or Novell Token Ring addresses have not inadvertently been set to reserved multicast addresses. |
%TR-3-BADSTART : Unit [dec], Start completion and wrong idb state - state= [dec] | |
---|---|
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. |
%TR-3-RESETFAIL : Unit [dec], reset failed, error code %-08x. | |
---|---|
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. |
%TR-6-STATE : [chars]: Ring Status: [chars] | |
---|---|
Explanation | This message is displayed when the Token Ring's status changed as determined by the chipset. This information also is used to automatically determine whether the interface is still usable to propagate network traffic. |
Recommended Action | No action is required. |
%TR-6-STATRING : TR[dec]: Ring Status: [chars] [chars] | |
---|---|
Explanation | This message is displayed when the Token Ring's status changed as determined by the chipset. This information also is used to automatically determine whether the interface is still usable to propagate network traffic. The meaning of each status code is shown in the Token Ring Status Codes Table. Code Explanation Fatal 0x8000 Signal loss Yes 0x4000 Hard error Yes 0x2000 Soft error No 0x1000 Transmit beacon Yes 0x0800 Lobe wire fault Yes 0x0400 Auto removal error Yes 0x0100 Receive request removed Yes 0x0080 Counter overflow No 0x0040 Single station No 0x0020 Ring recovery No |
Recommended Action | Check the Token Ring for the indicated condition. |
%TR-3-INTFAIL : Unit [dec] interface failure: [hex] [hex] [hex], idb state [dec] | |
---|---|
Explanation | The Token Ring Monitor firmware detected a fatal error due either to an internal software problem or to a hardware failure. |
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. |
%TR-3-BADRNGNUM : Unit [dec], ring number ([dec]) doesn't match established number ([dec]). | |
---|---|
Explanation | The number you have configured for the local ring does not match the value currently in use on the ring. |
Recommended Action | Check the configuration to make sure you used the correct ring number. If it is correct, confirm the configuration of all other bridges on the ring to make sure they are using the same ring number. |
%TR-3-WIREFAULT : Unit [dec], wire fault: check the lobe cable MAU connection. | |
---|---|
Explanation | The Token Ring hardware is reporting a wire fault condition. |
Recommended Action | Check the cable connecting the router to the Token Ring media attachment unit (MAU). |
%TR-3-OPENFAIL : Unit [dec], open failed: [chars], [chars] | |
---|---|
Explanation | The Token Ring interface was unable to insert itself into the ring. This is an indication of a busy or broken ring. The first character string in this error message indicates the stage of initialization at which the error occurred, and the second describes the error. |
Recommended Action | Try to open the interface again. This generally can be accomplished by issuing the clear interface tokenring command. If the error message recurs, call your Cisco technical support representative for assistance. |
%TR-3-OPENFAIL2 : Unit [dec], open failed: check the lobe cable DB-9 connection. | |
---|---|
Explanation | The Token Ring interface was unable to insert itself into the ring, and the error code returned indicates a wiring problem. |
Recommended Action | Check the cable connecting the router to the Token Ring MAU, and try to open the interface again. This generally can be accomplished by issuing the clear interface tokenring command. LOG_STD_RECUR_ACTION |
%TR-3-SETGRPFAIL : Unit [dec], set group address failed (code [hex]). | |
---|---|
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. |
%TR-3-SETFUNFAIL : Unit [dec], set functional address failed (code [hex]). | |
---|---|
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. |
%TR-3-SETBRIDGEFAIL : Unit [dec], set bridge failed (code [hex]). | |
---|---|
Explanation | A hardware error occurred. The source routing accelerator (SRA) chip on the Token Ring card could not be initialized. |
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. |
%TR-3-BADUNIT : Bad unit number [dec] | |
---|---|
Explanation | This error message pertains only to the IGS. When displayed, it indicates that the system cannot find the chipset registers where it expects them to be. This is most likely a hardware error. |
Recommended Action | If this message recurs, call your technical support representative for assistance. It will be necessary to determine the hardware unit configuration. |
%TR-3-BADBUFFSIZE : Unit [dec], bad buffersize = [dec] | |
---|---|
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. |
%TR-3-BADFUNC : Unit [dec], bad functional address=[hex], ring mode=[hex] | |
---|---|
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. |
%TR-3-BADBRDGPARMS : Unit [dec], bad bridge parameters: bridge_num=[dec], max_rd=[dec]thisring=[dec], targetring=[dec] | |
---|---|
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. |
%TR-3-INITFAIL : Unit [dec], init failed. result code=[hex], error code=[hex] | |
---|---|
Explanation | The Token Ring hardware failed to initialize properly. |
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. |
%TR-3-MODEFAIL : Unit [dec], change mode failed. result code=[hex], error code=[hex] | |
---|---|
Explanation | An internal hardware or software error occurred. |
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. |
%TR-3-NOFIRM : Unit [dec], no TMS380 firmware present. eagle=[hex], magic=[hex] | |
---|---|
Explanation | An internal hardware or software error occurred. |
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. |
%TR-3-BADFIRMTYPE : Unit [dec], bad firmware type code during [chars]. type=[hex], fw=[hex] | |
---|---|
Explanation | An internal software error occurred. |
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. |
%TR-3-BADFIRM : Unit [dec], Tokenring firmware download failed got [hex], expected [hex], at address [hex].[hex] | |
---|---|
Explanation | An internal software error occurred. |
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. |
%TR-2-NOMEMORY : Unit [dec], no memory for [chars] | |
---|---|
Explanation | The requested operation could not be accomplished 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. |
%TR-3-DIAGFAIL : Interface [chars] failed init diags ([hex]), [chars] | |
---|---|
Explanation | The microcode attempted to run its diagnostics on the chip and failed. |
Recommended Action | Issue a clear interface command. LOG_STD_RECUR_ACTION |
%TR-3-ADPCHK : Interface [chars], adapter check error (non-fatal)([hex] [hex] [hex] [hex]) | |
---|---|
Explanation | The Token Ring monitor firmware detected a non-fatal error on the interface card. |
Recommended Action | Issue a clear interface command. If this message recurs, call your technical support representative for assistance. |
%TR-3-ADPCHKFATAL : Interface [chars], adapter check error (fatal) ([hex] [hex] [hex] [hex]) | |
---|---|
Explanation | The Token Ring monitor firmware detected a fatal error on the interface card. |
Recommended Action | Issue a clear interface command. If this message recurs, call your technical support representative for assistance. You may need to replace the interface card |
TRACK
%TRACK-3-ERROR : Internal error, [chars] | |
---|---|
Explanation | An internal 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. |
%TRACK-4-WARN : Internal warning, [chars] | |
---|---|
Explanation | An internal software warning 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. |
%TRACK-6-STATE : [chars] | |
---|---|
Explanation | The Tracked object has changed state. |
Recommended Action | No action is required. |
%TRACK-6-INFO : Internal info, [chars] | |
---|---|
Explanation | An internal software information message 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. |
TRCCFG
%TRCCFG-3-INVALID_BOOT_TRACE_CFG : Boottime trace configuration string [chars] invalid | |
---|---|
Explanation | The value is not accepted by flash library due to an error. The result is that the boottime trace configuration settings are not successfully saved for use across re-boots. |
Recommended Action | Check that the boot trace configuration is valid. If valid, try saving configuration again. |
%TRCCFG-3-ROMMON_OUT_OF_SPACE_TRACE_CFG : No space in rommon for boot trace configuration | |
---|---|
Explanation | Rommon is full and does not have room to save boot trace configuration. |
Recommended Action | Remove any unnecessary rommon variables to free up space and retry. |
TSP
%TSP-3-NOEVENT : no free event structure available from [chars] for DSP message | |
---|---|
Explanation | There were no event structures remaining in the system pools to alert the router of a voice or signaling event. |
Recommended Action | Check that the voice port for which the event was reported is still operational. If not, clear the voice port. |
%TSP-3-CAPABILITYMISMATCH : voice port [chars]: call connection id [[hex] [hex] [hex] [hex]] | |
---|---|
Explanation | There was a capabilities mismatch between the two call legs. capabilities are negotiated between call legs for CODEC, VAD and FAX rate. |
Recommended Action | Check that the dial peer configuration is appropriate for the interface in question. Also check that and configuration on the interface is correct. |
%TSP-3-DSPALARM : voice port [chars]: status=[hex] message=[hex] | |
---|---|
Explanation | The DSP reported a fatal error. All calls on the DSP were dropped and a DSP reload was attempted. |
Recommended Action | Verify that the DSP reloaded properly by attempting to place a call on the affected voice port. Contact your technical support representative, include the full text of the error message. |
%TSP-5-PRI : [chars] at slot [dec], unit [dec], channel [dec] | |
---|---|
Explanation | A PRI signalling channel is added/deleted to TSP's inventory of signalling channels. |
Recommended Action | This is a notification message only. No action is required. |
%TSP-3-FSM_ERROR : [chars] | |
---|---|
Explanation | Internal Finite State Machine Error. |
Recommended Action | Contact your technical support representative, include the full text of the error message. |
TTY
%TTY-3-AUTOCONFIG : TTY%t: Modem auto-configuration failed | |
---|---|
Explanation | Modem auto-configuration failed either because the modem rejected the configuration string or because of a timeout. An attempt should be made to apply the configuration string mannually. |
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. |
%TTY-3-NOPROCESS : Cannot create [chars] process | |
---|---|
Explanation | Failed creating the process. |
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. |
TTYMON
%TTYMON-3-INIT : The software which monitors ownership of the console port cannot be initialized correctly | |
---|---|
Explanation | The Host Manager process on the Route Processor, and only the Route Processor, is responsible for determining which process has control of the console port, either IOSd or an IOSXE process. A user can initiate a switch in ownership by by entering the 'send break' command at a telnet prompt to switch from IOSd to a shell instance. Control is returned to IOSd by exiting the shell instance. The component within the Host Manager responsible for this has encountered an initialization error and console monitoring is no longer available. |
Recommended Action | Check the status of the Host Manager process. Check the Host Manager log files for further indications as to why the initialization failed and if necessary restart the machine. |
%TTYMON-3-CHASFS : The software which monitors ownership of the console port cannot [chars] a filesystem configuration value. | |
---|---|
Explanation | The Host Manager process on the Route Processor, and only the Route Processor, is responsible for determining which process has control of the console port, either IOSd or an IOSXE process. A user can initiate a switch in ownership by by entering the 'send break' command at a telnet prompt to switch from IOSd to a shell instance. Control is returned to IOSd by exiting the shell instance. The component within the Host Manager responsible for monitoring a change of console ownership uses the filesystem to store various settings. This error indicates that the daemon encountered a problem either reading or writing a value from/to the filesystem. |
Recommended Action | Check the log files for the Host Manager and search for entries related to 'ttymon' and 'chasfs' and this should give an indication as to why the operation failed. Check available resources and see if other daemons are also experiencing problems with the chassis filesystem since this may indicate a more pervasive problem. If so the reboot the box. |
%TTYMON-3-AGETTY : Cannot initiate a switch in console ownership. A required program could not be launched successfully. | |
---|---|
Explanation | The Host Manager process on the Route Processor, and only the Route Processor, is responsible for determining which process has control of the console port, either IOSd or an IOSXE process. A user can initiate a switch in ownership by by entering the 'send break' command at a telnet prompt to switch from IOSd to a shell instance. Control is returned to IOSd by exiting the shell instance. Switching ownership of the console port is initiated by the user entering a 'send break' command at a telnet prompt. The Host Manager launches one or more programs to authenticate users and to provide a shell instance. One or more of these programs has not been configured correctly. |
Recommended Action | Some required programs are either not available or not configured correctly or are failing for some reason. If this occurs after a recent upgrade it is possible that the upgrade has corrupted the current installation. |
TUN
%TUN-3-API_ARGS : unexpected arguments: [chars], [chars] | |
---|---|
Explanation | A public tunnel component api was driven with arguments outside the expected boundaries. |
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. |
%TUN-5-TUN_DB_IF : Operation on tunnel interface table failed for [chars] - [chars] | |
---|---|
Explanation | Manipulation of the tunnel interface table failed. |
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. |
%TUN-5-RECURDOWN : [chars] temporarily disabled due to recursive routing | |
---|---|
Explanation | When routing the same payload protocol over a carrier protocol (tunneling IP over IP, for example), it is possible to misconfigure your network so that you will try to route to the tunnel destination address via the tunnel. This is usually caused by a misconfiguration of the tunnel or a temporary instability due to route flapping elsewhere in your network. It is important to take steps to ensure that routing information between the carrier networks and the payload networks is not allowed to mix. If the router discovers a recursive routing problem, it will temporarily shut down the tunnel interface for a few minutes so that the situation that is causing this problem can resolve itself as routing protocols converge. If the problem is caused by misconfiguration, the link may oscillate indefinitely. |
Recommended Action | No action is required. |
%TUN-5-RECURDOWN_SRC : [chars] linestate down, recursive source interface, next output [chars] | |
---|---|
Explanation | Whilst evaluating tunnel linestate we revisted a source interface. |
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. |
%TUN-3-ENDPOINT_STORE : Operation [chars] failed for [chars] | |
---|---|
Explanation | Manipulation of the tunnel endpoint store failed. |
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. |
%TUN-3-MULTI_KEYS_INFO : [chars] [chars] | |
---|---|
Explanation | Manipulation of the tunnel keys database failed. |
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. |
%TUN-3-MULTI_KEYS_INFO_ERROR : [chars] [dec] | |
---|---|
Explanation | Manipulation of the tunnel keys database failed because of incorrect idb_index. |
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. |
%TUN-4-UDLR_IDB_ERROR : UDLR [chars] - [chars] | |
---|---|
Explanation | An error was encountered on a udlr interface |
Recommended Action | No action is required. |
%TUN-3-ENDPOINT_ERROR : [chars] [chars] | |
---|---|
Explanation | An internal software error occurred when manipulating the tunnel endpoint database |
Recommended Action | No action is required. |
%TUN-5-IGNOREICMPMTU : [chars] ignoring received ICMP Type 3 Code 4, due to pmtud min-mtu setting | |
---|---|
Explanation | An ICMP Type 3 Code 4 (fragmentation needed and DF set) packet has been received. This packet has specified a Next-Hop MTU smaller than the tunnel current minimum path mtu discovery mtu value. The ICMP packet has been ignored and the MTU of the tunnel has not been changed. |
Recommended Action | If you want the ICMP packet to be accepted and to be used to decrease the tunnel MTU then use the tunnel path-mtu-discovery min-mtu command to decrease the minimum mtu allowed. The min-mtu specified is the minimum tunnel payload mtu allowed. Use the show interface tunnel command to view the current path mtu discovery settings. |
%TUN-5-IGNOREICMP6MTU : [chars] ignoring received ICMP6 Type 2 Code 0 , due to pmtud min-mtu setting | |
---|---|
Explanation | An ICMP6 Type 2 Code 0 (ICMP6 Packet Too Big message) packet has been received. This packet has specified a Next-Hop MTU smaller than the tunnel current minimum path mtu discovery mtu value. The ICMP6 packet has been ignored and the MTU of the tunnel has not been changed. |
Recommended Action | If you want the ICMP6 packet to be accepted and to be used to decrease the tunnel MTU then use the tunnel path-mtu-discovery min-mtu command to decrease the minimum mtu allowed. The min-mtu specified is the minimum tunnel payload mtu allowed. Use the show interface tunnel command to view the current path mtu discovery settings. |
%TUN-3-MTUCONFIGEXCEEDSL2MTU_IPV4 : [chars] IPv4 MTU configured [int] exceeds tunnel maximum MTU [int] | |
---|---|
Explanation | An IPv4 MTU value is configured on the tunnel interface and this value exceeds the tunnel's maximum MTU. This message is typically observed when the tunnel header size changes or when the MTU of the underlying exit interface changes. As a result of either, the tunnel maximum MTU can change. This message can also be observed when using an IPv6 tunnel to carry IPv4 since IPv4 MTU config in this case allows for a value to be configured that is greater than the tunnel's maximum MTU. As a result of any of these conditions, packets may be dropped. |
Recommended Action | If a specific IPv4 MTU value is not required, it is recommended that you leave the value at the default by typing no ip mtu on the tunnel interface. If a specific value is required, it is recommended that you check the interface MTU value from the show interface tunnel command and adjust ip mtu on the tunnel interface to be lower than or equal to this. |
%TUN-3-MTUCONFIGEXCEEDSL2MTU_IPV6 : [chars] IPv6 MTU configured [int] exceeds tunnel maximum MTU [int] | |
---|---|
Explanation | An IPv6 MTU value is configured on the tunnel interface and this value exceeds the tunnel's maximum MTU. This message is typically observed when the tunnel header size changes or when the MTU of the underlying exit interface changes. As a result of either, the tunnel maximum MTU can change. This message can also be observed when using an IPv6 tunnel to carry IPv6 since IPv6 MTU config in this case allows for a value to be configured that is greater than the tunnel's maximum MTU. As a result of any of these conditions, packets may be dropped. |
Recommended Action | If a specific IPv6 MTU value is not required, it is recommended that you leave the value at the default by typing no ipv6 mtu on the tunnel interface. If a specific value is required, it is recommended that you check the interface MTU value from the show interface tunnel command and adjust ipv6 mtu on the tunnel interface to be lower than or equal to this. |
%TUN-4-MTUCONFIGLESSTHAN_MINIPV4MTU : [chars] IPv4 MTU [int] is lesser than the minimum IP MTU [int], fragmentation may occur | |
---|---|
Explanation | The IPv4 MTU value calculated on the tunnel interface is less than the minimum IP MTU. The MTU of the underlying exit interface of the tunnel is too small. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface. |
Recommended Action | If a specific MTU value is not required for the exit interface, it is recommended that you leave the value at the default by typing no mtu on the exit interface. If a specific value is required, it is recommended that you check the MTU value from the show interface command for the exit interface and adjust mtu on the tunnel exit to be higher than this. |
%TUN-4-MTUCONFIGEXCEEDSTRMTU_IPV4 : [chars] IPv4 MTU configured [int] exceeds tunnel transport MTU [int] | |
---|---|
Explanation | An IPv4 MTU value has been configured on the tunnel interface and this value exceeds the tunnel's transport (default) MTU. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface. |
Recommended Action | If a specific IPv4 MTU value is not required, it is recommended that you leave the value at the default by typing no ip mtu on the tunnel interface. If a specific value is required, it is recommended that you check the tunnel transport MTU value from the show interface tunnel command and adjust ip mtu on the tunnel interface to be lower than or equal to this. |
%TUN-4-MTUCONFIGEXCEEDSTRMTU_IPV6 : [chars] IPv6 MTU configured [int] exceeds tunnel transport MTU [int] | |
---|---|
Explanation | An IPv6 MTU value has been configured on the tunnel interface and this value exceeds the tunnel's transport (default) MTU. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface. |
Recommended Action | If a specific IPv6 MTU value is not required, it is recommended that you leave the value at the default by typing no ipv6 mtu on the tunnel interface. If a specific value is required, it is recommended that you check the tunnel transport MTU value from the show interface tunnel command and adjust ipv6 mtu on the tunnel interface to be lower than or equal to this. |
%TUN-4-MTUDEFAULTEXCEEDSL2MTU_IPV4 : [chars] transport MTU [int] exceeds [chars] configured IPv4 MTU [int], fragmentation may occur | |
---|---|
Explanation | A default MTU value has been configured on the tunnel and this value exceeds the underlying physical interface MTU. As a result, fragmentation of the transport packet may occur before this goes out of the underlying exit interface. |
Recommended Action | If possible, increase the size of the IPv4 MTU on the underlying physical interface using ip mtu. |
%TUN-5-TUN_TABLE : Operation [chars] on tunnel table failed for [chars] - [chars] | |
---|---|
Explanation | Manipulation of the tunnel table failed. |
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. |
%TUN-3-DECAP_OCE : [chars] [chars] | |
---|---|
Explanation | An internal software error occurred in the tunnel subsystem which is responsible for building forwarding for the purposes of decapsulation |
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. |
%TUN-3-DECAP_TINFO : [chars] [chars] | |
---|---|
Explanation | An internal software error occurred in the tunnel subsystem which is responsible for driving forwarding based on the tinfo configuration |
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. |
%TUN-3-ILLEGAL_ARGS : Illegal arguments - [chars] | |
---|---|
Explanation | An internal 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. |
%TUN-5-TUN_HWIDB_RECYCLE : Failed to recycle hwidb for Tunnel [dec] index [dec] | |
---|---|
Explanation | Recycling of tunnnel interface failed. |
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. |
%TUN-5-TUN_SWIDB_RECYCLE : Failed to recycle swidb for Tunnel [dec] index [dec] | |
---|---|
Explanation | Recycling of tunnnel interface failed. |
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. |
%TUN-5-TUN_HWIDB_DELETE : Failed to delete hwidb for Tunnel [dec] index [dec] | |
---|---|
Explanation | Deletion of tunnnel interface failed. |
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. |
%TUN-5-TUN_SWIDB_DELETE : Failed to delete swidb for Tunnel [dec] index [dec] | |
---|---|
Explanation | Deletion of tunnnel interface failed. |
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. |
%TUN-5-TUN_INTF_STATE_RESET : Failed to reset tunnel interface state for [chars] | |
---|---|
Explanation | Reset of tunnnel interface failed. |
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. |
%TUN-5-TUN_UNIT_LIST_INSERT : Failed to add entry unit [dec] to tunnel unit list | |
---|---|
Explanation | Insertion of tunnnel unit failed. |
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. |
%TUN-5-TUN_HWIDB_LIST_INSERT : Failed to add [chars] to tunnel hwidb list | |
---|---|
Explanation | Insertion of tunnnel to hwidb list failed. |
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. |
%TUN-5-TUN_UNIT_LIST_DELETE : Failed to delete entry unit [dec] to tunnel unit list | |
---|---|
Explanation | Deletion from tunnnel unit failed. |
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. |
%TUN-5-TUN_HWIDB_LIST_DELETE : Failed to delete [chars] from tunnel hwidb list | |
---|---|
Explanation | Deletion of tunnnel from hwidb list failed. |
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. |
%TUN-5-TUN_LIST_CREATE : Failed to create tunnel list [chars] | |
---|---|
Explanation | Creation of tunnel list failed. |
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. |
%TUN-5-HW_IF_INDEX_ILLEGAL : Attempt to create tunnel interface for [chars] with illegal index: [dec] | |
---|---|
Explanation | Creation of tunnel interface failed. |
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. |
%TUN-5-INIT_ERROR : A critical error [chars]occurred during initialization | |
---|---|
Explanation | Creation of tunnel subsystem failed. |
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. |
%TUN-3-TUN_SIDB2TUNS : [chars]: [chars] | |
---|---|
Explanation | An internal 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. |
%TUN-3-TUN_SB : TUN_SB: [chars][chars][chars] | |
---|---|
Explanation | An internal 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. |
%TUN-3-TUN_DBG : TUN_DBG: [chars] [chars] | |
---|---|
Explanation | An internal 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. |
%TUN-3-TUN_HA : Tunnel HA: [chars] | |
---|---|
Explanation | Tunnel HA encountered an internal software error |
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. |
%TUN-3-GROUPS : Tunnel Groups: [chars]: [chars] | |
---|---|
Explanation | The tunnel group component encountered an internal software error |
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. |
%TUN-3-WCCP_GROUP : Tunnel WCCP Groups: [chars]: [chars] | |
---|---|
Explanation | The tunnel group component encountered an internal software error |
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. |
%TUN-3-OTV_GROUP : Tunnel OTV Groups: [chars]: [chars] | |
---|---|
Explanation | The tunnel group component encountered an internal software error |
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. |
%TUN-3-L3VPN_GROUP : Tunnel L3VPN Groups: [chars]: [chars] | |
---|---|
Explanation | The tunnel group component encountered an internal software error |
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. |
%TUN-3-L3VPN_ENCAP_IP_PROFILE : L3VPN Encap IP : [chars]: [chars] | |
---|---|
Explanation | The L3VPN Encap IP component encountered an internal software error |
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. |
%TUN-4-L3VPN_ENCAP_IP_SRC_DEL : L3VPN Encap IP : [chars]: [chars] | |
---|---|
Explanation | The user configuration change results in a warning. This message is typically printed when the user tries to delete a loopback interface, and the loopback interface is configured as the source interface of the L3VPN encap IP profile |
Recommended Action | It is recommended that the user removes the loopback interface as the source interface of the L3vpn encap ip profile, before deleting the loopback interface. |
%TUN-3-SIA_GROUP : Tunnel SIA Groups: [chars]: [chars] | |
---|---|
Explanation | The tunnel group component encountered an internal software error |
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. |
%TUN-3-6RD : [chars]: [chars] | |
---|---|
Explanation | The tunnel 6RD feature encountered an internal software error |
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. |
%TUN-5-6RD_INFO : [chars]: [chars] | |
---|---|
Explanation | 6RD configuration has been removed as it is not compatible with the new sub-mode |
Recommended Action | No action is required. |
%TUN-3-CM1 : [chars] | |
---|---|
Explanation | The tunnel classification module encountered an internal software error |
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. |
%TUN-3-CM2 : [chars] [dec] | |
---|---|
Explanation | The tunnel classification module encountered an internal software error |
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. |
%TUN-3-TUNTO : Operation: [chars], Action: [chars], Reason: [chars] | |
---|---|
Explanation | The tunnel-to module encountered an internal software error |
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. |
%TUN-5-L3VPN_IP_PROFILE_DELETE : l3vpn encap ip profile [chars] deleted | |
---|---|
Explanation | l3vpn encap ip profile is deleted |
Recommended Action | No action is required. |