Cisco ios software release 12 422t download

cisco ios software release 12 422t download

This Rtr incremental release version () contains fix for the following Dependent Package: dadi.mirzakon.ru CISCO IOS SOFTWARE RELEASES. Cisco IOS software releases. MIBs. Files used for network monitoring. To locate and download. MIBs for selected platforms, Cisco IOS releases, and feature. Download the latest Cisco Intelligent Gigabit Ethernet Switch Module for IBM This version adds the following features to the Cisco IOS software. COMODO ANTIVIRUMAC 10 6 8 Сообщаю Для вас, что.

Symptoms: MGCP calls fail with a fast busy signal. When you enter the debug mgcp packet command, the output indicates that the Voice Call Setup failed. Calls fail only after the router is reloaded. The symptom may also occur on a Cisco series that functions in the same configuration. Enter the ccm-manager config server ip-address command followed by the ccm-manager config command. Enter the shutdown command on the voice port or on the T1 controller.

Enter the no mgcp command followed by the mgcp command. Enter the no ccm-manager config command followed by the ccm-manager config command, assuming that you have the TFTP server defined. After you reload the router, enter the write erase command, add the configuration, and save the configuration. Symptoms: Poor voice quality may be experienced as the default impedance selection may not yield the best ERL.

Conditions: This symptom has been observed when using the default impedance selection on a Cisco router. Symptoms: When multicast is configured as part of a dial-peer configuration and you enter the shutdown command quickly followed by the no shutdown command on a voice port that is part of the dial-peer configuration, the router may generate tracebacks and may crash. Symptoms: The following error message may be generated when a Cisco AS voice gateway boots:.

This situation may prevent line cards from booting up and pings over the Fast Ethernet and Gigabit Ethernet interfaces may fail. Symptoms: Configuring an AUX port through a non-slotted notation such as "interface async 1" may not be possible on a Cisco and a Cisco Symptoms: When a router detects "invalid identity" failures while decrypting IPsec packets, a memory leak occurs for the packet memory that is associated with these failed packets.

Conditions: This symptom is observed only when an "invalid identity" error occurs, which is an uncommon error that indicates that the originating router does not send packets according to what was originally negotiated. However, if there is another error that causes a "bad" decryption, the packet could be invalid and may also cause the symptom to occur. Conditions: This symptom is observed on a Cisco router when two users are connected to the router and simultaneously enter the show policy interface EXEC command.

Symptoms: A T. The fax that is sent or received via the BRI may be incomplete with cut pages or a part lost. About 40 to 50 percent of the faxes fail. Symptoms: Tracebacks are generated on a Cisco AS that is configured for analog and digital bulk calls. However, the symptom does not impact service because the calls are processed by the Cisco AS The router should fragment the packets.

Conditions: This symptom is observed on a Cisco series when the size of a cleartext packet is larger than bytes which is the Ethernet MTU minus the IPSec overhead. However, the symptom is platform-independent and occurs with both software encryption and onboard hardware encryption engines.

This example assumes that the physical interface of the tunnel source is an Ethernet interface with an MTU of bytes. Symptoms: Performing Telnet results in the session pausing indefinitely after accepting 13 characters or carriage returns. Use Fast Ethernet for Telnet sessions if possible. Conditions: This symptom is observed on a Cisco gateway that has an ephone hunt group configured. Symptoms: If a crypto map has RRI enabled and is applied to more than one interface, removing the map from one interface removes all active routes that are associated with other instances of this crypto map.

In particular, this situation affects dialup termination and VPN connectivity on the same physical router. When you use a virtual template, the disconnection of one virtual-access interface that is spawned from the virtual template causes all routes for all other virtual-access interfaces to be removed. Conditions: These symptoms are observed on a Cisco router under the following conditions:. Workaround: Do not remove a crypto map from an interface when there are active connections on other interfaces that use the same crypto map.

First clear all SAs from the crypto map and then remove the interface. Symptoms: A router may unexpectedly reload and generate the following error message:. Conditions: This symptom is observed on a Cisco series when one interface is configured for IP Header Compression IPHC and when another interface has a crypto map that includes the qos pre-classify command.

However, the symptom is platform-independent. Symptoms: You cannot bring up a serial interface of a channelized E1 or T1 port. Pool: Processor Free: Cause: Interrupt level allocation. Conditions: This symptom has been observed on a Cisco router with the cadventerprisek9-mz. Conditions: This symptom is observed when H. This situation causes a mismatch of payload type for the Gr16 or Gr24 codec.

Symptoms: A Cisco router that is configured for SSG may reload when you configure a local service profile. Conditions: This symptom is observed when the local service profile is configured with more than service network entries. When the symptom occurs, the output of the show aaa sessions command shows that the user name is not available for the idle client. The user name appears to be lost.

The symptom may not be release-specific. Symptoms: A router that is configured for SSG intermittently resets itself and generates a spurious memory access. Symptoms: A Cisco series may reload because of a bus error when you enter a show atm command that accesses deleted VCs structures. Conditions: This symptom is observed when the fax call is torn down and the gateway attempts to obtain call statistic information from the DSP. The symptom does not occur in standalone mode. The timeout itself does not impact the call for which it occurs because the timeout occurs at the end of the call while the call is being torn down and cleaned up.

For this problem, caveat CSCsb has been opened. Workaround: When MGCP PRI-backhaul is configured in a Cisco CallManager environment, you can disable Fax Relay on a gateway to prevent timeouts from occurring by entering the no ccm-manager fax protocol cisco global configuration command on the gateway.

Alternate Workaround: To prevent timeouts from occurring, configure the gateway to function in standalone mode. Symptoms: A clicking sound is heard after each. The problem only occurs when there are multiple. A VXML document containing a single. The output of the debug dhcp detail on the DHCP client router shows that the old static route is removed but that the routing table still contains the old static route.

Also, the old static route is not removed after the static configuration is deleted. Conditions: This symptom is observed under either one of the following conditions:. The exact lengths which tickle the symptom may vary depending on the memory lite configuration.

The consequence of this error is that an additional read-write community string may be enabled if the device is configured for SNMP management, allowing a knowledgeable attacker the potential to gain privileged access to the device. Cisco is making free software available to address this vulnerability for affected customers.

Symptoms: A Cisco that is configured as an H. Instead, it generates the no-circuit tone. Note that the symptom does not occur in Release Conditions: This symptom is observed on a Cisco router when an interface has both IPSec and the ip verify unicast reachable-via command enabled and when a hardware encryption engine is used for IPSec. Workaround: Remove the ip verify unicast reachable-via command from the interface. Symptoms: Active voice and fax calls may stop unexpectedly on a gateway, that is, either the call may drop or two-way audio may stop.

The timeout may occur on one of the channels of the DSP, but the reset algorithm impacts other calls on other channels that are active on the same DSP. Workaround: Disable the DSP recovery algorithm by entering the test dsp recovery disable command. However, use this command with caution because disabling the auto-recovery mechanism prevents voice and fax calls from functioning properly when a DSP enters a valid non-responding state.

The timeout may occur when an internal software error causes some invalid statistics to be polled, leading to the timeout. As an example, see caveat CSCsa Dec 10 In 6 milliseconds, the router activated the layer 2. Symptoms: A Cisco router crashes when PVCs are deleted while the show pppoe session or show vpdn command is entered.

PVCs are deleted via one Telnet session while the show pppoe session or show vpdn command is entered via the other Telnet session. The symptom is platform-independent. Workaround: Do not delete PVCs via one session and enter the show pppoe session or show vpdn command via another session at the same time. Workaround: Manually free the asynchronous resources on the NAS by entering the clear line line-number command or ask the remote dialin user to disconnect the modem.

Conditions: This symptom is observed on a Cisco router that is configured with full virtual-access interfaces when a PPP leak occurs. Workaround: Reload the router and configure virtual-access subinterfaces instead of full virtual-access interfaces.

Conditions: This symptom is observed only when you establish sessions at a high rate. When you attempt to establish sessions, the router crashes shortly after sessions are established. The messages are not sent out, and the box is unusable. This symptom is observed on any Cisco IOS In the responder router, the responder debug message shows many error packets.

Conditions: This symptom is observed when multiple jitter probes either from the same router or from different routers are configured to send packets to the same destination IP address and the same destination port number and when the responder is turned off for a short time and turned on again. Workaround: To prevent the symptom from occurring, configure the jitter probe to use a unique destination port number.

Alternate Workaround: If the symptom has occurred, turn off the responder by entering the no rtr responder global configuration command, wait until all jitter probes report "No connection," and then turn on the responder by entering the rtr responder global configuration command. In other instances alignment errors are observed when you enter the show alignment command. Conditions: This symptom is observed on a Cisco router that runs Cisco The symptom occurs in a configuration with two PE routers that advertise routes via eBGP and a border router that is configured with a higher local preference than the PE routers when the eBGP route of the primary path is withdrawn and the route of the secondary path is installed.

Conditions: This symptom is observed when the OSPF process is simultaneously deconfigured via one session and configured via another session. Cisco strongly discourages you to configure a router via two different but simultaneous sessions. Symptoms: A platform that is, a switch or a router may crash when you enter the ip routing command followed by the configure memory command and the no ip routing command multiple times. Multiple tracebacks may also be generated.

Conditions: The symptom is observed on a Cisco platform that functions as the master in a stacked environment and that is configured for OSPF. The symptom is more likely to occur when the platform functions under a heavy traffic load. Workaround: Do not enter the ip routing command followed by the configure memory command and the no ip routing command multiple times.

Symptoms: On a PE router with a parallel path to a destination where one path is over the OSPF sham-link and the other path is over the backdoor link, traffic is not getting load balanced. Only a backdoor connection is being used to forward the traffic. Conditions: This symptom occurs on a PE router where traffic is not getting load balanced. Workaround: Configure OSPF metric in a way that sham-link path and backdoor paths do not have the same cost.

The symptom occurs because of a change in router ID. Workaround: Shut down the newly created loopback interface, save the configuration, and reload the router. Symptoms: Tracebacks may occur when you enter an ipv6 prefix-list command and BGP is not enabled or when you enter an ipv6 prefix-list command after you have entered the no router bgp as-number global configuration command. Workaround: First enter the router bgp as-number global configuration command before you enter an ipv6 prefix-list command.

Conditions: This symptom is observed when the nexthop information changes to an existing prefix entry in the BGP routing table. Typically, this occurs when the interface through which the prefix is learned goes down. Workaround: Flush out the stale CEF entry by entering the clear ip bgp command or withdraw and readvertise the prefix by the source router, which enables the affected router to refresh the CEF entry.

Symptoms: A failed LDP session may still show up in the output of the show mpls ldp neighbors command as well as the new working session after the neighborship is re-established. The display of two sessions, one not working and one working to the same neighbor, may mislead the MPLS network operator.

Conditions: This symptom may occur after an LDP session has gone down and then re-established. However, a modem call goes into pass-through mode when you enter the shutdown voice-port configuration command followed by the no shutdown voice-port configuration command on the trunked voice port.

Conditions: This symptom is observed on a Cisco series that functions as a voice gateway. Workaround: After the router has booted, do not enter the shutdown voice-port configuration command followed by the no shutdown voice-port configuration command on the trunked voice port. Conditions: This symptom is observed on a Cisco and Cisco and may also occur on other routers. Conditions: This symptom is observed on a Cisco router that is configured for the G.

Symptoms: After a router is rebooted, a tunnel interface does not acquire the IP address of the async serial interface that is the tunnel source. Workaround: Enter the tunnel source interface-type interface-number command on the tunnel interface. Symptoms: There may be a large latency in responding to EAPoUDP events from a host, causing the idle timer to expire and network access for users to be delayed.

Conditions: This symptom is observed after a link flap occurs on the dialer interface or after you enter the clear interface command on the dialer interface. To re-enable the affected packets to be forwarded, enter the no ip cef command followed by the ip cef command. Symptoms: A Cisco voice gateway may reload unexpectedly because of a bus error, pointing to an invalid address. Conditions: This symptom is observed when you enter the redundancy handover peer-resource command and when the Cisco AS functions in the extra-load state.

Workaround: Clear all existing calls that use peer resources and mark the calls as busyout before you enter the redundancy handover peer-resource command. Symptoms: A Cisco AS reloads when you enter the redundancy handover peer-resources command to hand over the peer resources to the other RSC. Symptoms: A gateway that has a higher IP address in comparison with its peer may fail to open a TCP connection for a logical channel. Conditions: This symptom is observed during fast start when a glare condition occurs while both gateways indicate to each other in facility or other H.

Symptoms: A Cisco reloads because of a bus error. Just before the crash, the following error messages are generated:. Conditions: When the ethernet connectivity between the ephone and the SRST router goes down, the sockets are not cleared.

This happens when the ephone is not in the fall-back mode. Conditions: This symptom is observed when the router has some of the following security feature commands enabled on one or more interfaces:. Workaround: Remove the ip access-group out command. Conditions: This symptom is observed when the PDP context create requests contain the static addressing, that is, the IP address of the MS instead of all zeros in the end user address field.

With dynamic addressing, the end-user address field is sent with all zeros and the corporate network provides the address, and the symptom does not occur. When you send encrypted traffic from the neighboring crypto router to another router via the Cisco series, the Cisco series reloads. Workaround: Permit the encrypted traffic on the outgoing interface of the neighboring crypto router. Symptoms: A call fails when the codec is changed from G.

Conditions: This symptom is observed when fax pass-through is configured and when the following events occur:. Workaround: Bring the card up again by issuing the clear service- module serial slot port command. Symptoms: A 4-port OC POS Engine 2 line card may crash repeatedly when the Cisco series in which the line card is installed comes up after a software-forced crash has occurred on the router. Conditions: This symptom is observed on a Cisco series that runs the c12kprp-p-mz image of a Cisco IOS interim release for Release The symptom is more likely to occur when the ipv6 unicast-routing command is enabled.

Workaround: To diminish the chance that the symptom occurs, disable the ipv6 unicast-routing command. Symptoms: EEM Tcl policies leak a significant amount of memory every time they run. Conditions: This symptom occurs because the memory model that is currently implemented in Cisco IOS software that supports Tcl assumes a single threaded model in which global memory is not released when the Tcl script completes. Conditions: This symptom is observed when a fax call is made between a platform that is configured for SIP and a platform that is configured for T.

Symptoms: An error message similar to the following may be logged in a router:. Conditions: This symptom occurs when the router creates virtual interfaces such as Loopback or Virtual. Symptoms: A bargeinable prompt aborts right after it starts playing, almost as if it is being barged in to. Conditions: This symptom is observed in the following scenario with an application that requests DTMF input using two to four digits with an asterisk as the termination character:. You hear a brief "burp", but not the three.

Possible Workaround: The symptoms may clear when you replace the in-house cabling with cat. Symptoms: An AIM that is installed in a Cisco or Cisco may time out when it receives non-multiples of a bits public key from a third-party vendor router. This situation causes the router to crash rather than verifying the key. The Cisco crashes because of a memory corruption. Workaround: Ensure that the AIM receives multiples of the bits public key.

Alternate Workaround: Disable the AIM hardware encryption by entering the no crypto engine aim 0 command. Doing so causes onboard encryption to occur. This is seen for UDP transport only. Conditions: This symptom happens when interworking with a third party SIP device, which sends responses to SIP Requests to the source port of the request packet instead of sending them to the header port Symptoms: Service Selection Gateway SSG does not update tariff switch information to the users when the user logs in exactly at tariff switching time.

There is a loud noise on the other side. Conditions: This symptom happens only when the transfer-system is full- consult, and there is a nonsecure to secure call transfer. Symptoms: A memory leak may occur in the processor memory pool of a router that runs encrypted traffic with an SA-VAM2. Workaround: Enter the shutdown interface configuration command followed by the no shutdown interface configuration command on the affected interface.

Workaround: Configure a static host entry for the neighbor in the routing table, pointing to the Dialer interface:. For the prefix mask argument , enter the IP address of the neighbor. Symptoms: A LNS intermittently routes packets to an incorrect interface in the process-switching path, preventing some applications from working properly. Consequently, this situation may affect user connectivity to the Internet.

Conditions: This symptom is observed when LCP renegotiation of proxy negotiations is disabled which is the default and when the multilink Endpoint Discriminator option that is advertised by the LAC does not match the Endpoint Discriminator on the LNS. Alternate Workaround: Avoid the need to renegotiate by entering the ppp chap hostname or ppp multilink endpoint command to configure matching Endpoint Discriminators on the LAC and LNS.

A platform must be configured to either enable the LNS to renegotiate when necessary, or if it is desired to avoid such renegotiations, which may be necessary to get around problematic client implementations enable the LAC to negotiate adequately as a substitute for the LNS. The fix for CSCsa deliberately introduces the behavior that a mismatched multilink Endpoint Discriminator is ignored when the LNS is configured to terminate connections on mismatched conditions.

This behavior is introduced to prevent the termination of a connection for a condition that is harmless for the majority of VPDN users. From a technical standpoint, this behavior is improper because it means that the VPDN clients have an invalid notion of the identity of the peer. This situation may pose problems for clients who have more than one multilink-capable link active at a time because the invalid Endpoint Discriminators may prevent links from being properly bundled at the client end.

The global command ip flow-cache feature-accelerate will no longer be recognized in any IOS configuration. If your router configuration does not currently contain the command ip flow-cache feature-accelerate , this change does not affect you. The removal of NetFlow Feature Acceleration does not affect any other aspects of Netflow operation, for example Access-list processing.

The features are separate and distinct. This section describes severity 1 and 2 caveats and select severity 3 caveats. Symptoms: A NAS may reload after functioning for a couple of days in a high-call capacity scenario. Symptoms: A platform reloads after you enter the aaa route download 2 command. Symptoms: The performance on a Cisco router that has the ip nat outside command enabled may be degraded.

Symptoms: A Cisco router hangs and the console connectivity disappears. When you break the hanging process and enable the router to enter ROMmon, a stack dump is generated. Conditions: This symptom is observed when the RTR and the fallback system process are not synchronized.

For each RTR probe, the fallback system creates a cache entry and keeps it for cache timeout. During the cache timeout, the fallback system process sends an event to RTR and frees the entry, but RTR sends an event after the cache entry is deleted. Note that caveat CSCeg fixes the problem from the fallback system process side but not the above-mentioned symptom. Symptoms: A router that is configured for AAA reloads because of a software-forced crash.

Loading configuration from Symptoms: When you enter the microcode reload command, an error message similar to the following and a traceback may be generated:. Symptoms: When RSVP and IP Header Compression are configured on an interface, the show ip rsvp installed detail command shows a compression factor of 0, and some of the flow is being treated as non-conformant. Workaround: Enter the ip rsvp flow-assist command on the outbound interface of the flow.

Conditions: This symptom is observed on a Cisco router that is configured to translate H. Symptoms: A router may reload because of a bus error exception. The crashinfo file shows an address error a load or instruction fetch and a spurious memory access. This situation causes a TCP connectivity timeout. Conditions: This symptom is observed in a configuration with SNAT failover and occurs only after the active HSRP router is reloaded or crashes and later becomes active once again.

Symptoms: The SRC address and destination address for an RTP stream are the same for all calls between gateways, preventing load-balancing from functioning properly. Conditions: This symptom is observed when RTP traffic is configured to be load-balanced among multiple links. In this situation, the SRC address or destination address should change, but neither is changed. Symptoms: Incoming or outgoing voice calls may encounter no-way audio on some specific channels.

Conditions: This symptom is observed on a link between two gateways when there are active calls in a configuration with multiple OPCs and when a switchover occurs. Reload the gateways to bring the link back in service. Symptoms: When the codec complexity is changed from flex mode to medium or high complexity mode, a maximum of six signaling channels can be assigned on each DSP in high-complexity mode or a maximum of eight signaling channels can be assigned on each DSP in medium-complexity mode.

If more than six signaling channels are assigned in flex mode and you change to high-complexity mode, the signaling channels beyond six are not reassigned to another DSP after the codec complexity change. If more than eight signaling channels are assigned in flex mode and you change to medium-complexity mode, the signaling channels beyond eight are not reassigned to another DSP after the codec complexity change.

Alternate Workaround: Reload the router after the codec complexity change to enable the signaling channels to be assigned correctly. Conditions: This symptom is observed when some of the dialed digits become lost in the call setup phase when FXS or FXO-melcas is configured over an E1 line. Workaround: When you pick up the phone, wait for two seconds before you start dialing. Symptoms: The legacy command syntax to configure an authentication proxy may not function. The system may be protected by installing appropriate access lists to filter all IPv6 fragments destined for the system.

For example:. This must be applied across all interfaces, and must be applied to all IPv6 addresses which the system recognizes as its own. This will effectively disable reassembly of all IPv6 fragments. Some networks may rely on IPv6 fragmentation, so careful consideration should be given before applying this workaround. We would recommend for customers to upgrade to the fixed IOS release. Symptoms: A standby RP may reboot when you enable or disable the ip rtp header-compression command on the active RP.

Symptoms: All IPSec sessions may be dropped from a Cisco series and the router generates the following error messages continuously:. To temporarily clear the symptoms, reload the router. Conditions: This symptom is observed when there is an access control list applied on an inside interface.

Conditions: This symptom is observed when the Cisco series is configured for dLFI over a leased line. Workaround: Configure a reduced maximum fragment, maximum reassembly, and timeout value in the ipv6 virtual-reassembly command, as in the following example:. Conditions: This symptom is observed on a Cisco that functions as a VoIP dial peer and that is configured with FXS ports that function in connection trunk mode and that are not configured for VAD.

Symptoms: A router reloads when you remove the ip address dhcp command. Symptoms: A Cisco series may crash when you enter the clear virtual-access command on a peer router. Conditions: This symptom is observed on a Cisco series that is configured for dLFIoATM and that is connected to a Cisco series that functions as a peer router to the Cisco series.

Symptoms: The output of the show voice call summary command does not show the correct codec for a fax call. Conditions: This symptom is observed on a Cisco router when the fax protocol t38 and the modem passthrough dial-peer configuration commands are enabled. The output of the show voice call summary command should show "" rather than "". However, the fax call goes through fine. Conditions: This symptom is observed under normal operation when the router functions without a high CPU load.

The symptom occurs because ACLs logging functions at process context only. Workaround: Do not configure ACL logging. Instead, for example, enter the following command:. Power-cycle the router to bring it back up. In addition, the gateway does not include the calling number in the Remote-Party-Id. Conditions: This symptom is observed on a Cisco router that functions as a PE router in a configuration in which packets are sent from a CE router on one end, are processed correctly through the PE router, but fail to reach the CE router on the other end.

Workaround: Enter the shutdown command followed by the no shutdown command on the VC on the PE router. Symptoms: Traffic, including cell-based MPLS traffic, may be affected that is, traffic may be dropped, or its behavior may be modified after you have modified a QoS policy map that is already attached to an interface by way of adding a new class or deleting an existing class.

Additionally, when a cell-based interface is affected by the above-mentioned symptom, traffic on other switch subinterfaces may also be affected even though the same policy map is not applied to these subinterfaces. Conditions: These symptoms are observed on when the following conditions are present:. Workaround: To prevent the symptoms form occurring: enter the shutdown command on the interface before you modify the policy map.

Enter the no shutdown command after you have modified the policy map. Alternate Workaround: When the symptom has occurred and the interface is already affected, enter the shutdown command followed by the no shutdown command on all affected subinterfaces. Symptoms: You cannot turn off the comfort noise that is generated by a DSP by entering the no comfort-noise voice-port configuration command.

Symptoms: In a point-to-point connection setup, the ATM interface on a Cisco may become stuck, causing packets to be dropped. The symptom is not reproducible with a manual configuration. Workaround: Enter the shutdown interface configuration command followed by the no shutdown interface configuration command on the affected ATM interface or recreate the PVC.

Symptoms: The output of the show call active fax brief command shows output even when a fax call over a connection trunk is switched back to voice mode. In addition, the output of the show call history fax brief command shows no call leg even when the last fax call is successful and the output may not be updated for a second call and subsequent calls.

However, the is no impact on the success of the calls. Symptoms: An extended access list does not function when it is applied to an interface even though the access list is configured correctly. Workaround: Use an external device to filter the traffic.

Apply the filter at another location in the network to accommodate your needs. T3 boot system bootflash:rpmxf-pmz. T3 boot-end-marker. Extended IP access list Compiled 10 deny tcp any host Router telnet It does not matter whether or not there is compact flash card in the USB card reader.

Symptoms: When MLP is configured and when the policy map of a CE router does not have a real-time class map configured in its output policy map, TCP packets are policed incorrectly. This situation may affect the traffic throughput.

When the output policy map of the CE router does not have a real-time class map configured, the PE router shows that the byte packet requires three ATM cells instead of just two ATM cells. When the output policy map of the CE router does have a real-time class map configured, the PE router shows that the byte packet requires two ATM cells, as it should be. This symptom may also occur in Release Symptoms: When an input policy is defined on a Cisco series, counters do not increment.

Conditions: This symptom is observed when the timer expires. Symptoms: An H. The expected behavior is that the modem call passes as a modem pass-through call because modem relay is not supported on a modem card. However, when you bring up only a single call, the call is successful and stable for the call duration. Conditions: This symptom is observed when PIM is enabled on multiple interfaces and when the counters are cleared.

Symptoms: There is no hornbook tone from a second ephone in a hunt group when the ringing of the first ephone in the hunt group times out and the call is forwarded to the second ephone. Conditions: These symptoms are observed when you configure a crypto map on tunnel interfaces that use the IP address of the physical interface as the tunnel source.

Symptoms: A router may crash when a certificate server is removed while the certificate storage is inaccessible. Symptoms: Configuring an AUX port through a non-slotted notation such as "interface async 1" may not be possible a Cisco and a Cisco Symptoms: A gateway attempts to register with a gatekeeper more than once but fails, and the following error message and tracebacks are generated:.

Conditions: This symptom is observed on a Cisco router that functions as an H. Symptoms: The line protocol on a serial link stays down and input CRC errors are generated. Symptoms: Accounting does not start after a tunnel goes down and comes back up again.

Conditions: This symptom is observed when multiple clients are connected to a head-end router through a platform that is configured for NAT. The tunnel interface should be down when clients try to re-key an IPSec SA and accounting should fail.

However, when the tunnel interface goes up and IKE negotiation starts again, accounting should also start again. Conditions: This symptom is observed on a Cisco that functions as a gatekeeper. Symptoms: A crypto tunnel is in the DOWN state after a Cisco series crashes because of a valid freeblock memory corruption.

Symptoms: Labeled packets drop when a crypto map is applied on an egress interface. Further Problem Description: While generating labeled packets from the router on which the crypto map is applied, the output of the debug ip packet access-list-number command shows the following information:. Conditions: This symptom is observed when the packet passing through a GRE tunnel interface. Conditions: This symptom is observed on a Cisco series that is configured with a channelized T3 port adapter.

Symptoms: After you have reloaded a Cisco that is configured with ATM AIM cards and that has a startup configuration that includes BERT functionality, a software-forced reload may occur on the router and the router does not come up. The software-forced reload does not occur after you have reloaded the router with the default configuration, that is, when codec information is not included and when ATM AIM cards are not configured.

Symptoms: Routers generate tracebacks during a test with call setup and random call failures. Conditions: This symptom is observed on Cisco 7xxx routers when E1R2 signaling is configured and when line signaling is used for the analog service. Symptoms: A VWIC multiflex trunk controller that has the alarm trigger-blue command enabled may not come up. Workaround: Enter the shutdown command followed by the no shutdown command on the affected controller after the router has booted.

Symptoms: A TDM connect failure occurs and tracebacks are generated, causing voice call failures. Conditions: This symptom is observed when Voice over IP VoIP is configured on a Cisco series and a Cisco series, when the signaling is E1 R2 analog with medium complexity, when you change the framing from CRC4 to non-CRC4 on the E1 controllers, and when you enter the shutdown controller configuration command followed by the no shutdown controller configuration command on the E1 controllers of both the Cisco series and the Cisco series.

Conditions: This symptom is observed when the G. Conditions: This symptom is observed on a Cisco platform that functions as an IPIPGW only after you reload the router and test transcoding for the first time. The SCCP connection exists for a long duration or until you enter the no sccp command. This situation causes only four processor to be up and one processor to remain inaccessible. Conditions: This symptom is observed when you enter the clear ipv6 inspect all command while many TCP sessions are being created.

Workaround: Prevent that so many TCP sessions are created: limit the session creation rate to sessions per minute by lowering the onemin threshold for the IPv6 firewall via the ipv6 inspect onemin high command. Symptoms: A Cisco platform may unexpectedly reload while attempting to resequence an access list. Conditions: This symptom is observed when you delete a few ACEs and then immediately enter the ip access-list resequence access-list-name starting-sequence-number increment command.

Workaround: Stop the SNMP pols that check the operational status via the ifOperStatus object and administrative status via the ifAdminStatus object of the interfaces on the router. Alternatively, temporarily disable SNMP on the router. Symptoms: When a voice call is made, a spurious memory access may occur on a Cisco AS or the Cisco AS may reload unexpectedly because of a bus error.

Workaround: Enter the no voice-fastpath enable command to prevent the symptoms from occurring. Conditions: This symptom is observed when downstream traffic from the open garden service to the subscriber is routed using the global routing table and is dropped when it appears to be unroutable.

Workaround: Add a route to the subscriber IP address in the global routing table. There is no pattern to the number of calls that fail, but eventually the router to which the IP phone is connected has CPU high utilization and crashes. Symptoms: A severe memory leak occurs when accounting is enabled on a gatekeeper. When all memory has been consumed, the following error message is generated:. After this message has been generated, you cannot enter any CLI command and calls fail.

You must reload the router to recover the lost memory. Conditions: This symptom is observed on a Cisco router that functions as a terminating gatekeeper and that is placed between a VoIP call generator and an originating gatekeeper that is also connected to a VoIP call generator.

The symptom occurs after the following events have occurred:. This is improper behavior. Symptoms: When you enter the crypto ipsec client ezvpn command, the platform may crash because of memory corruption and error messages similar to the following may be generated:. Symptoms: A router may crash because of an unexpected exception to CPUvector Workaround: Remove the output service policy from the dialer interface before any traffic goes through the ISDN backup interface.

Symptoms: A Cisco may display the following error message and traffic is interrupted:. Conditions: This symptom is observed when multiple users that are connected to a downstream switch attempt to log into network resources across a WAN traversing the router. Symptoms: A dialer backup with a serial interface as the primary interface and an ISDN interface as the backup interface fails. Packet load-sharing does not occur. Symptoms: A router crashes when you enter the no dialer pool-member command on a BRI interface while the interface is up.

Workaround: Enter the shutdown interface configuration command followed by the no shutdown interface configuration command on the BRI interface before you enter the no dialer pool-member command. Conditions: This symptom is observed when the ppp bap callback command is enabled. Symptoms: The isdn number called enbloc limit interface configuration command is ignored on a gateway is configured for ISDN.

Symptoms: Calls may not go through an E1 or T1 trunk card on a Cisco platform. Conditions: This symptom is observed after you have performed an OIR of the card. Workaround: There is not workaround. To recover from the symptoms, reload the platform.

Symptoms: The output of the show interfaces multilink command on a Cisco shows output queue drops on an MLP bundle. Symptoms: A call is not placed in a PPP callback scenario after an earlier call went through fine. Conditions: This symptom is observed when the call is placed through a dialer interface. Workaround: Clear the dialer interface before each call.

If this not an option, there is no workaround. The symptom occurs in this fail-over scenario. An Acct-Start record should be sent when the session is established, but no Acct-Stop record should be sent when the fail-over occurs. Symptoms: Calls on B-channels of a trunk group that is configured on NFAS "none" group members time out, and the first channel remains in the proposed state.

Conditions: This symptom is observed only for a trunk group that is configured on controllers of NFAS "none" group members. Symptoms: The snmp-server host host-address command supports only one host. Adding another host causes the existing host to be overwritten. In addition, when the snmp-server host host-address traps command is enabled, traps are sent to the host but the command does not show in the running configuration. Conditions: These symptoms are platform-independent and are observed when you use the above-mentioned commands to configure more than one host or to configure the host to receive traps.

Conditions: This symptom is observed when the Cisco AutoSecure feature is already enabled. Symptoms: Because the mean opinion score MOS is monitored for the low score value, the threshold trap should be generated when the MOS reaches the falling threshold, but this does not occur. Conditions: This symptom is observed when the traps are configured for the MOS parameter. Note that the current implementation does not support monitoring the MOS score for low values that is, a falling threshold value.

When the symptom happens, jitter operation timer expiration is shown in the debug message. Workaround: Configure the jitter operation timer to be much longer than the numberPaks interval. Resolution: The fix for this caveat provides two new fields for the output of the show rtr command: "Busies: " and "PacketSkipped: ". Conditions: This symptom is observed when MOS traps are configured. Only syslogs traps are supported for MOS.

Symptoms: Several tty lines may become stuck in the "Carrier Dropped" modem state. You can verify this situation by entering the show line line-number EXEC command for an individual line. In addition, both the output of the show users EXEC command and the output of the show caller EXEC command do not show a user or caller name or show an incorrect user or caller name.

However, you can limit the number of messages that are generated by entering the logging rate-limit command. Symptoms: Traffic does not go properly through an IPSec tunnel: many packets are dropped. Symptoms: When you enter the snmp-server host host-address public frame-relay isdn envmon cpu voice snmp global configuration command, the command is saved to the configuration as snmp-server host host-address public frame-relay isdn envmoncpu voice snmp. Note that "envmon" and "cpu" are saved as "envmoncpu".

When you reload the platform, the command is removed from the configuration because its syntax is improper. Workaround: Enter the snmp-server host host-address public command to enable all the traps. Symptoms: A router crashes because of a SegV exception when you enter the show running-config command via a Telnet session into the router. Workaround: Enter the show running-config command on the console of the router. Symptoms: NetFlow cache is not allocated on all port adapters, preventing egress NetFlow from functioning.

The symptom also affects the Cisco Symptoms: When entering via SSH, view-based users are not authorized to access their view but are authorized according to their corresponding privilege level. Symptoms: A serial interface of a channelized E1, T1, E3, or T3 port adapter may continue to flap when fair queueing is disabled on the interface.

Symptoms: When both VRF and non-VRF processes are configured and both processes have the redistribute command enabled, removal of the redistribute command from one process may also disable redistribution for the other process. In certain rare cases this condition may also lead to a unexpected reload. This can occur when another routing protocol is attempting do perform certain redistribution operations the with the process that was unintentionally disabled, and this happens at the moment in which the redistribute command was removed.

Workaround: Reconfigure the redistribute command for the process for which the command should not have been disabled. Conditions: This symptom is observed when the static routes are inserted into the BGP table with a network statement that uses a route map that is configured with the match as-path route-map configuration command.

The symptom occurs because the match as-path route-map configuration command causes a non-BGP route to be denied. Symptoms: Tracebacks that are related to spurious memory accesses may occur and the spurious memory accesses may increase over time. When multicast video streaming is viewed using an IP-TV viewer, this situation causes the browser to hang.

Conditions: This symptom is observed when NAT and multicast configuration on the same router. To return the browser to normal operation, reload the router. Symptoms: Multipath routes may become stale when the nexthop is unreachable, preventing a ping between two CE router from succeeding.

Conditions: This symptom is observed in a BGP environment when a multipath route is withdrawn. Symptoms: A router may crash and reload and generate the following error message:. The session comes up fine the first time after you reload one of the BGP peers. Symptoms: When you configure a route map with a NAT feature, the CPU usage of the router may reach 99 percent, the router may reload unexpectedly, or both may occur. However, the symptom may be platform-independent.

These attacks, which only affect sessions terminating or originating on a device itself, can be of three types:. Successful attacks may cause connection resets or reduction of throughput in existing connections, depending on the attack type. Multiple Cisco products are affected by the attacks described in this Internet draft. Cisco has made free software available to address these vulnerabilities. In some cases there are workarounds available to mitigate the effects of the vulnerability.

NISCC is working with multiple vendors whose products are potentially affected. Symptoms: The output of the show bgp ipv6 neighbors ipv6-address b ly: ipv6 unicast command does not show the peer information. However, this is just a display problem and the functionality is not affected. However, the symptom may not be platform-dependent.

Symptoms: If an ASBR receives a withdraw message, it does not send the withdraw message to any peer, preventing an alternate route from functioning. Workaround: Route control using static routes is not affected by the symptom. To prevent the symptom from occurring in a situation with route control using BGP routes, configure OER to control only exact routes.

Symptoms: BGP fails to send an update or withdraw message to some peers when these peers have failed to converge properly after an earlier attempt. Conditions: This symptom is observed on a Cisco router when you enter the clear ip bgp neighbor-address soft out command while BGP is in the middle of converging.

The symptom does not occur when network traffic load is low and BGP has converged. Workaround: To clear the error condition, enter the clear ip bgp neighbor-address soft out command again. Alternately, enter the clear ip bgp neighbor-address command that is, without the soft out keyword.

However, the symptom may occur on any platform that has a toaster processor. Symptoms: When overlapping global addresses are configured and when there is a flow entry, the wrong entry may be matched. Symptoms: Routes may still appear in the routing table even after the routes are removed from the BGP table. The BGP table reflects the route change but the routing table still indicates that the route is valid. Symptoms: When a fragmented packet flows from the inside to the outside via a NAT router, the first fragment is translated correctly, but subsequent fragments are transmitted without a destination address translation.

This situation causes the communication to fail. Conditions: This symptom is observed with a fragmented packet when both the source address and the destination address are translated, that is, inside and outside source translation is configured.

Note that the symptom does not occur with an unfragmented packet, or when a fragmented packet flows from the outside to the inside, or with a fragmented packet when either the source address or the destination address is translated. Symptoms: When a route map is configured, routes may not be filtered as you would expect them to be filtered. Conditions: This symptom is observed when the redistribute static command is enabled.

Conditions: This symptom is observed on a Cisco series during normal operation. Symptoms: The cisco. Conditions: This symptom is observed when the CNS configuration notify agent is configured by the cns config notify command and when atm pvc commands are configured. The connected line locks up, and the script no longer responds to local or remote input.

Workaround: Reload the router to clear the VTY line. To prevent the symptom from occurring, do not user server sockets. Symptoms: Fax relay does not function between H. Conditions: This symptom is observed during interworking between H. Workaround: Terminate user input with a carriage return Enter instead of by entering Ctrl-c. Symptoms: When changing a route pattern or destination number, the trunk or endpoint receiving a new destination number may be unusable until the gateway is reset.

Conditions: This symptom is observed on a Cisco series that functions as a gateway. Workaround: Via the gateway configuration panel, reset the gateway after changing the route pattern or destination number. Symptoms: Some conference parties may not be heard and the conference bridge may become unregistered from a Cisco CallManager.

Conditions: This symptom is observed on a Cisco platform that functions as a conference bridge when one or more of the RTP streams that enter the router use RTP header-compression. Symptoms: The output of the show policy-map interface interface-name input command shows that more packets are received than the output of the show interfaces type number precedence command. Symptoms: A Cisco RPM-XF sends more data than it should according to the configuration of the priority policy-map class configuration command.

Layer-2 policing does not seem to work properly. A subsequent full SPF computation causes the route to be added. Conditions: This symptom is observed on a Cisco router and is most likely to occur when a large number of type 3, type 5, or type 7 LSAs are advertised and withdrawn. The NHRP cache entry at the hub expires a long time before its expiration time. Workaround 1: Do not enter the show ip nhrp brief command.

Note, however, that the symptom is platform-independent for Release Any of the IS-IS global configuration commands may trigger the symptom. Following are a few examples of these IS-IS global configuration commands:. Symptoms: A router may crash when you attempt to unconfigure a service policy. This vulnerability only applies to traffic destined to the Cisco IOS device. Traffic transiting the Cisco IOS device will not trigger this vulnerability.

Symptoms: The input error counter may not be incremented for packet errors such as runts, CRC errors, and overrun errors. Symptoms: A router cannot be reloaded by entering the reload command, and the following message is displayed when you attempt to reload the router:. Conditions: This symptom is observed under rare conditions and may be triggered after an "Invalid pointer value in private configuration structure" error message is displayed as seen in caveat CSCin Symptoms: A Cisco series may hang, stop forwarding traffic, and stop responding to the console.

Conditions: This symptom is observed on a Cisco series that has the ip audit command enabled. Symptoms: With H call service stopped, the router still listens on tcp port and completes connection attempts. Symptoms: A router requires a very long time to boot more than 5 minutes, potentially hours.

Also, changes to the QoS configuration may require long times. Conditions: This symptom is observed when the QoS configuration has a complex arrangement of many policies that reference many access control entries ACEs through a number of class maps. The time required is, roughly, proportional to the number of combinations of interfaces, policies, classes, and ACEs. For example, if each of interfaces has a QoS policy, each policy uses five class maps, each class map references two ACLs, and each ACL has 30 entries, there are 60, combinations.

Workaround: Either reduce the number of combinations of interfaces, policies, class maps, and ACEs, or load the configuration in two stages. The first stage from NVRAM should contain the interface and ACL definitions, and the second stage from another file should contain the classes and policies.

This could lead to the TCP session not timing out. The following error messages may be generated on the console or syslog if enabled :. Conditions: This symptom is observed on a Cisco series router but is not platform-dependent. Symptoms: CEF switching is broken for voice traffic on some interfaces, which breaks the transcoding feature. The caller then experiences no voice path. Conditions: This symptom has been observed on some network modules and interfaces. Workaround: Disable the ip cef command.

The symptom may also affect other releases. Conditions: This symptom is observed when hundreds of CLI commands are entered in virtual-template mode. Symptoms: When applying a service-policy to a subinterface, the router crashes.

Conditions: This problem happens on an ATM subinterface with a large amount of subinterfaces with service-policies applied. Symptom 1: None of the policy classes after the first child policy of a hierarchical QoS policy take effect when you reload the router. Condition 1: This symptom is observed on a Cisco that has hierarchical QoS policies with multiple child policies but may also occur on other platforms.

Workaround 1: There is no workaround to prevent the symptom from occurring. When the symptom has occurred, enter the service-policy output interface configuration command to enable the child policies to take effect. Note that the symptom does not occur for a hierarchical QoS policy with only one child policy in the very last class of the parent policy.

Symptom 2: On a Cisco series that is configured with hierarchical queueing policies, when you remove the match vlan command for a VLAN that matches a dot1q subinterface, the queues that are allocated to the subinterface are not cleared, allowing traffic to continue to flow through these queues. Condition 2: This symptom is observed on a Cisco series that has hierarchical QoS policies with multiple child policies but may also occur on other platforms.

Workaround 2: There is no workaround. Entering the clear arp command on the standby router in the HSRP configuration does not resolve the problem. Workaround: Enter the no standby redirects command to prevent the symptom from occurring. Symptoms: When a PVC is being shutdown on the remote side, the PVC subinterface on the Cisco router transitions from down to up within one second, and then stays down after the down retry timers expire.

Symptoms: An NPE-G2 crashes when you first enter the no ima-group command, then you enter the atm vc command for the IMA group, and finally you enter the show vc command. Conditions: This symptom is observed on a Cisco series that is configured with an IMA port adapter. Workaround: First configure an IMA group. Symptoms: The line protocol may go down on some of the serial interfaces of a 1-port multichannel STM-1 single mode port adapter.

Conditions: This symptom is observed on a Cisco router when the maximum number of channel groups is configured on the port adapter. Conditions: This symptom is observed on a Cisco router when a null data structure is accessed. The PVC is shaped at a rate bigger than the configured value. Workaround: Use the default CEF load balancing on a per-destination basis. If you need to configure loadbalancing on a per-packet basis, disable IP CEF accounting by entering the no ip cef accounting per-prefix non-recursive command.

Symptoms: The line protocol on a newly configured SRP interface may remain down and does not come up after you have entered the no shutdown command. Symptoms: A Cisco router that is configured for X. Symptoms: A router may crash by address error load or instruction fetch exception during normal operation.

Symptoms: A router may crash when the AAA per-user attribute idletime is specified in the user profile. Workaround: Do not specify the AAA per-user attribute idletime in the user profile. Symptoms: A router may reload unexpectedly when you configure more multilink interfaces than the maximum number that the router can support. The router should not reload but should generate an error message. Conditions: This symptom is observed on any Cisco router that imposes a limit on the number of multilink interfaces.

Symptoms: Multihop router fails establishing a session from LAC. CDN is sent by one of the following reasons:. The CLI is as follows:. Symptoms: When a Telnet session is made to a router after a VTY session pauses indefinitely, the user in the Telnet session may not be able to enter the configuration mode. This behavior is not platform-specific.

When this situation occurs, the following error messages are generated:. Conditions: This symptom is observed on a Cisco series when you enter the microcode reload command. Further Problem Description: The symptom may also occur because of improperly installed line cards.

If this situation occurs, re-install the line cards. In turn, this situation prevents the router from being accessible for 30 seconds. Conditions: The number of configured VRF should be huge. Symptoms: A Cisco series that is configured with more than two VIP or VIP processors may crash during the boot process and may not boot at all.

Symptoms: A Cisco series may log the following error message even if no VIP is installed in slot Conditions: This symptom is observed after a crash of another VIP has occurred. Sometimes the symptom occurs when a VIP is installed in slot 0 but most of the time there is no VIP in slot 0 when the symptom occurs. Symptoms: A Cisco series may crash when you perform a graceful OIR of a port adapter that is processing traffic.

Conditions: This symptom is observed mostly when the port adapter processes ingress traffic. Conditions: This symptom is observed on a Cisco series but may be platform-independent. Conditions: This symptom is observed on a Cisco platform that is configured with a channelized T3 port adapter when the T3 controller is in an unavailable seconds UAS state. Symptoms: When multipath is configured, one of the paths may have an inconsistent old label, causing only one path to be operational.

Conditions: This symptom is observed on a Cisco router that is configured for multicast routing. Conditions: This symptom is observed on a Cisco router that has the auto-summary command enabled and occurs when classful networks are provided before the routes are made available in the routing table. Symptoms: A router may reset unexpectedly when it is in the midst of output of the results of the show interface dampening command, and the interface is deleted from another vty connection.

Conditions: This symptom can be encountered if concurrent connections are opened to a router, and the show interface dampening command is issued while interface s are deleted. Workaround: Ensure interfaces with dampening configured are not deleted while the show interface dampening command can be possibly issued on another vty.

The symptom could also occur in Release Conditions: This symptom is observed on Cisco platforms supporting switchover when OSPFv3 is configured with the area transit- area-id virtual-link transit-router- id command configured. This situation may cause a loss of multicast connectivity while the RP mappings are purged from the cache. See the following output example:.

Workaround: Create a dummy loopback interface do not use the configured IP address in the whole network and use the ip mtu to configure the size of the MTU for the RP interface to and the size of the MTU for the dummy loopback interface to , as in the following examples:. Symptom 2: IS-IS may crash or function unreliably because of uninitialized or freed data structures. Condition 2: This symptom is observed when a passive interface is configured and when the following actions occur:.

If you must use a passive interface in an IS-IS environment, prevent the actions that are described in Condition 2. Symptoms: When you reload microcode onto a line card or perform an OIR of a line card, a spurious memory access error may be logged on some or all other line cards in the router. Conditions: This symptom is observed on a Cisco router that is configured for IPv6 dCEF when an IPv6 route is loadbalanced across two equal cost paths that both leave the router on interfaces of the same line card, which is the line card onto which you reload microcode or on which you perform an OIR.

The output of the show processes memory command shows that the memory that is held by the process that creates the trap increases, and eventually causes a MALLOC failure. When this situation occurs, you must reload the platform. Conditions: This symptom is platform-independent and occurs in a configuration in which at least one VRF destination has the snmp-server host command enabled. Workaround: Ensure that no VRF is associated with the snmp-server host command.

The message "not transmitting" is generated, followed by "output frozen. Workaround: Enter the shutdown command followed by the no shutdown command on the affected SPE to recover the modem from the busy state. Workaround: Configure process switching on the multilink interface that connects the CE router and the PE router by entering the no ip mroute-cache interface configuration command.

Symptoms: When a single DSP is used to make both a modem call and a fax-relay call, the calls fail, and tracebacks are generated on the terminating gateway TGW. Symptoms: A Cisco router may reload unexpectedly because of a bad block pointer.

The symptom may be platform-independent. In this situation, the router does not update the forwarding plane, causing dropping or misbranding of traffic because of label inconsistencies between the BGP table and the forwarding table. Conditions: This symptom is observed when there are two route reflectors RRs that advertise the same route and when one of the routes is the best path. The symptom occurs when the following conditions are present:. Workaround: Enter the clear ip route network command for the affected prefix.

Symptoms: A Voice Gateway crashes when running under a heavy voice call load. The symptom could occur in Release Workaround: Clearing the BGP neighbor should allow the correct labels to be installed. Symptoms: A Cisco series reloads unexpectedly when you enter the hw-module slot slot-number stop command for a T3 port adapter. Symptoms: A router may crash because of a bus error when you enter the no policy-map command. A new label for the prefix is learnt from the remote PE router, but forwarding may not be updated properly.

When the symptom has occurred, and to correct the situation, enter the clear ip route vrf vrf-name network command on the PE router that has mismatched labels. Symptoms: All channels on a multichannel T3 port adapter may go down. The router may then reload unexpectedly due to a software forced crash. If not, all of the channels in the T3 may stay down until corrective action is taken. The symptom occurs when one or more of the T1's in either T3 sees framing errors. Workaround: There is no workaround to prevent this problem.

Possible corrective actions are listed below:. Possible Corrective Actions for the Cisco router: 1. Remove and reinsert the affected port adapter. Simulate removal and reinsertion with these exec mode commands in sequence: hw-module slot slot- number stop hw-module slot slot- number start 3. Reload the router. Remove and reinsert the VIP with the affected port adapter. Use the configuration mode command: microcode reload 3.

The following messages may be seen but not mandatory on the console or syslog if applicable :. Conditions: This symptom is observed on a Cisco series router but is not platform dependent. Symptoms: A router may crash because of a bus error when you enter the show interface command for a virtual-access interface or subinterface.

Conditions: This symptom is observed when you enter the show interface command while a session that is associated with the virtual-access interface or subinterface is being cleared. Conditions: This symptom is observed when you enter the show mpls ldp discovery command under the following condition:. Workaround: Do not enter the show mpls ldp discovery command while multiple LDP adjacencies are coming up.

Rather, enter the show mpls ldp neighbor [detail] command while multiple LDP adjacencies are coming up. Symptoms: A Cisco router that is configured as a DHCP relay may not append option 82 that is, the Relay Agent option , even when the router is configured to do so in the following way:. If you cannot ensure this, there is no workaround.

Symptoms: Packets are route-cache switched instead of distributed-cache switched. Conditions: This symptom occurs when distributed-cache switching is enabled, but packets are still route-cache switched for Cisco IOS Release Symptoms: Renaming a file to a string that contains multiple trailing dots ". Conditions: This symptom is observed when you enter the following commands to rename the file:.

Workaround: Avoid renaming a file that contains multiple trailing ". When the symptom has occurred and the file system is no longer accessible, you must reformat the disk by entering the format disk0: command. The condition results in all traffic over affected PVCs ceasing to pass. Reload Cisco series router. The mainframe product correctly shows the link as inactive. The link cannot be reactivated. Trying to stop the link with the snasw stop link command leaves the link in Pending Inactive state.

Conditions: This symptom occurs when there is an outage between the SNASw router and the mainframe, such as an IP failure, interface failure, or mainframe reload. The SNASw subsystem must be restarted with the snasw stop command followed by the snasw start command to clear the condition.

The message can be similar to this example and is followed by a trace back. Further Problem Description: This symptom does not cause any side effects. VRF can be applied to the interface and will work fine but tracebacks are reported after configuring it.

Conditions: This symptom is observed on a Cisco router that is configured for BGP and that is connected to a third-party vendor router after the BGP authentication password is changed on the Cisco router. Symptoms: When you remove a map group from an interface, the router may reload. Workaround: Shut down the interface before you remove the map group from the configuration.

Conditions: This symptom is observed on a Cisco AS but is not platform-dependent. Symptoms: Multilink interfaces do not recover after a T1 link in a bundle flaps. Conditions: This symptom is observed when two Cisco router are connected back-to-back via two channelized OC-3 connections with T1 links and when the multilink bundles are created with two T1 links each.

Workaround: Enter the shutdown interface configuration command followed by the no shutdown interface configuration command on the affected multilink interfaces. The drops persist under a very low 25 pps transmit rate. After you have disabled the traffic source or shut down the ingress interface, the MFR output hold queue may take as long as 15 minutes to "drain.

Conditions: These symptoms are observed on a Cisco router when you run multicast traffic over GRE tunnel interfaces that in turn use an MFR interface for transport. The MFR output hold queue may get into a congestion state that results in all traffic failing. Further, after disabling the traffic source or shutting down the ingress interface, the output hold queue may take as long as 15 minutes to "drain. Workaround: Enter the no virtual-template subinterface command globally.

The related advisory is published at:. This related advisory is available at the following link:. This software table is available at the following link:. Symptoms: A router may crash when the encapsulation is set to PPP and removed repeatedly. A vulnerability exists in the IOS HTTP server in which HTML code inserted into dynamically generated output, such as the output from a show buffers command, will be passed to the browser requesting the page.

This HTML code could be interpreted by the client browser and potentially execute malicious commands against the device or other possible cross-site scripting attacks. Successful exploitation of this vulnerability requires that a user browse a page containing dynamic content in which HTML commands have been injected. Cisco will be making free software available to address this vulnerability for affected customers. Symptoms: Cisco routers with traffic-carrying port adapters PA may crash when a Graceful OIR is done on the traffic-carrying port adapter.

Conditions: The following conditions may result in a crash of the Cisco router:. Graceful OIR must be done. The PA must be carrying traffic and the symptom occurs mostly with ingress traffic on the PA. Symptoms: A Cisco router may reload after stopping the probe, changing the history, enhanced-history, collection, or distribution statistics configuration, and starting the probe again.

Workaround: Remove the old probe and create a new one if the configuration changes as listed above are needed. Workaround: There is no problem if the command sequence no ip cef command followed by the ip cef command is not executed. If this command sequence is executed, there should be no problem if less than 50 VRFs are configured.

There is no workaround. Conditions: This symptom is caused by the RP dropping the Auto-RP announce messages as can be seen with the debug ip pim auto-rp debug command. This may result in loss of multicast connectivity while the RP mappings are purged from the cache. Workaround: Create extra dummy loopback interface and specifically configure "ip mtu" size on RP interface to and size of dummy loopback interface to Conditions: This problem can only occur on multiaccess interfaces when the outgoing interface stays the same, but the next-hop changes.

Point-to-point interfaces are not affected by this problem. Workaround: The clear ip route command restores the correct routing table. The following message may be displayed:. Symptoms: Tunneled packets that terminate on a device with an SII intercept in place do not get intercepted. Conditions: This symptom occurs if the device on which the tunnel terminates has SII intercepts that match the inner packet.

SII will not intercept the packet. Workaround: If the packets to be intercepted must arrive via a tunnel, there is no workaround. If not, another method of transport will allow the packets to be intercepted. Conditions: This symptom occurs on a Cisco uBR router with cable modem interface redundancy that is switching over from a subinterface in one VRF to an interface in a different VRF.

The following messages may appear one or more times in the router or VIP log:. The symptom occurs when one or more of the T1s in either T3 sees framing errors. Simulate removal and reinsertion with these exec mode commands in sequence: hw-module slot slot- number stop hw-module slot slot- number start. Use the configuration mode command: microcode reload.

Poor voice performance. Transcoding does not work. In some cases, no voice path. This is caused by voice packets originating from the router not being CEF switched. Conditions: This symptom occurs when voice modules are plugged in the router. Conditions: The reload is seen on a Cisco AS platform but is not platform dependent. It happens when async media is involved. Once the authorization fails, local limit does not get applied to a particular interface.

Symptoms: A Cisco router reloads when the show log , show interface , or show caller commands are issued. This symptom can occur when PPP sessions go down while the show output is suspended. Symptoms: When two sockets are bound to the same port, the first File Descriptor always receives the requests. Conditions: This occurs after the first change to the encapsulation type from the default HDLC to some other encapsulation type and an exit from configuration mode.

Subsequent changes to the encapsulation type do not cause the cBus Complex Restart. The overhead added to the MTU is always This will be changed to Workaround: There is no workaround for the cBus-complex issue. The MTU can be set accordingly to avoid packets drop as giants in the driver. Further Problem Description: When the router boots with the encapsulation type set to the default of HDLC on a serial interface, the maximum datagram size that can be accepted by the interface is set to When the encapsulation type is changed, the maximum datagram size may change which causes an internal MTU change.

Workaround: Turn the router off and then back on one time will resolve the issue. Symptoms: A spurious memory access may be generated on an RSP when a VIP that is in a disabled or wedged condition is recovered because of a Cbus Complex or microcode reload. Conditions: This symptom is observed on a Cisco series that has a VIP that is in a disabled or wedged condition after the router has booted. Symptoms: The removal of authorization keywords for attributes that are implemented can cause some undesirable authorization failure.

Conditions: This symptom has been observed when AAA tries to do authorization using these keywords. Symptoms: Radius packets being sent have the incorrect value for attribute 5 Nas-Port. The Async interface-related information is needed in the Cisco-Nas- Port attribute. Conditions: This symptom has been observed on the Cisco-Nas-Port attribute on a radius server.

When a regular numbered ACL is used, an incoming Telnet connection from an interface that is part of a VRF is rejected without the vrf-also keyword being configured in the access-class access-list-number command. Conditions: This symptom is observed on a Cisco Catalyst series, Cisco series, and Cisco series. Also, PA-A3-T3 interfaces do not properly handle P-bit and C-bit errors and do not bring down the controller when the threshold is reached for such errors. The output of the show atm pvc command does not show the PVC as existing on the router.

Further Problem Description: The following sample configuration illustrates the symptom:. You can verify that the symptom has occurred in the output of the show controller command and you can manually confirm the deletion of the OSPF MAC entry. The router will process them and will forward them through the appropriate interface should a valid entry exists in the routing table.

Conditions: The controller is in promiscuous mode and bridging is configured in any interface in the router. The output of show interface interface irb for the affected Ethernet interface prints the following message for all subinterfaces:. Workaround: In the affected Ethernet interface: 1. Configure a subinterface with a dumb VLAN. Configure bridging in that subinterface. Remove the bridging configuration. Remove the subinterface. The symptom is platform-independent and could also occur in Release Symptoms: While configuring the dot1q encapsulation in the router, traceback is seen.

Conditions: This symptom has been observed with a router configured with dot1q encapsulation and IPSec. Try later" error message may be generated. Symptoms: There are duplicate entries in the flow cache after an interface bounces, causing packet loss. The output of the show ip cache flow command may show information similar to the following:. This situation causes incomplete adjacencies because the CEF process expects a fresh ARP entry to complete its adjacency.

The symptom is platform-independent and may also occur on other platforms when the same conditions occur. Workaround: Clear the ARP cache or enter the shutdown command followed by the no shutdown command on the affected interface. Conditions: This symptom is observed on a Cisco router that is configured for VRF-aware NAT only when the router is not directly connected to a gateway.

Conditions: This symptom is observed on a Cisco series router with multicast enabled but is not platform dependent. Bootup is the most likely place where this will happen, but the router may crash anytime if an interface flap happens at the right time while receiving PIM traffic. Symptoms: Conditional advertisement of the default route via a route map does not work when you enter the neighbor default-originate command. Workaround: Disable the route map entirely. Workaround: Use a static route for the global-network argument.

This symptom may occur under a rare condition when a neighboring router calculates that is has a newer copy of the LSA from the originating router and bounces the MaxAge LSA to the originating router. Workaround: Enter the clear ip ospf process command. The commands to configure these features are the ip rsvp policy local command and the ip rsvp signalling refresh reduction command, respectively.

This situation prevents the application from receiving the corresponding Resv message, and may cause the application to fail. Workaround: Remove all ip unnumbered commands that point to the original numbered interface before you configure this numbered interface as an unnumbered interface itself.

Alternate Workaround: Change all unnumbered interfaces to point to the new parent. Conditions: This symptom is observed on a Cisco router that functions as a PE router when MVPN performs decapsulation in the slow path instead of the fast path. Symptoms: When the distribute-list route-map map-tag command is used under the OSPF router mode and when the route map is modified, OSPF does not update the routing table based on the changes in the route map.

Conditions: This symptom is observed when a route map that is referenced in the distribute-list route-map map-tag command is modified. This vulnerability affects all three methods of operation. Symptoms: On a Cisco router that is configured for Port Address Translation, when you enter the ip nat service fullrange udp port port-number command, the port-allocation logic does not function. When a PAT port is already taken, the next-port logic fails, causing some packets to be discarded.

However, the symptom may occur on any platform that has the ip nat service fullrange udp port port-number command enabled. Workaround: Disable the ip nat service fullrange command. Only the port-allocation logic in relation to the ip nat service fullrange command is affected. When there is an intermittent source that is not active for 3.

When the source starts after 3. Workaround: Configure a keepalive mechanism for the intermittent source to maintain the integrity of the multicast tree. Conditions: This symptom is observed when the ip rsvp bandwidth and service-policy output commands are configured on the same interface and when the policy map for the service policy is configured with the fair-queue command.

Workaround: Enter the ip rsvp resource-provider none command on the interface. Alternate Workaround: Enter the ip rsvp bandwidth value command and ensure that the value argument is equal to the value that is displayed on the "Available Bandwidth" line in the output of the show interface interface command plus the value that is shown in the "allocated" column in the output of the show ip rsvp interface command. Conditions: This symptom is observed rarely in a configuration with a large LSA with at least 44 links that have OSPFv3 enabled and with some links configured for broadcast mode when an adjacency with a peer router flaps.

Symptoms: Memory utilization in the "Dead" process grows gradually until the memory is exhausted. However, the symptom is not platform-specific, nor release-specific. Workaround: Reload the router. I this is not an option, there is no workaround. Conditions: This symptom is observed on a Cisco switch that has redundant Supervisor Engines and on a Cisco router that has redundant RPs when Auto-RP is configured and when regular multicast traffic runs for a few hundred multicast routes.

Conditions: This symptom is observed rarely in a configuration with a large LSA with 64 parallel links that have OSPFv3 enabled in broadcast mode when all adjacencies with a peer router flap. Conditions: This symptom is observed rarely when all of the following conditions are present:. Workaround: Increase the carrier-delay time for the interface to about 1 second or longer. Alternate Workaround: Use an LSA build time shorter than the time that it takes for an adjacency to come up completely.

Symptoms: Router hangs while unconfiguring the BGP no router bgp command. Symptoms: A router may advertise an IPv6 default route into a level-2 topology. Conditions: This symptom is observed when the following conditions are present:.

Workaround: Trigger a change that causes the router to regenerate its level-2 LSP. Conditions: This symptom is observed on a Cisco series that has an ATM subinterface on which the atm arp-server nsap nsap-address interface configuration command is enabled.

Workaround: Disable the atm arp-server nsap nsap-address interface configuration command on the ATM subinterface. Conditions: This symptom is observed when L2VPN connections are dynamically deconfigured and then reconfigured. Workaround: Perform the clear interface command.

Symptoms: The gatekeeper does not route calls based on the ARQ call identifier. Conditions: This symptom was observed with a third party application that is registered to a gatekeeper when attempting to use Trunk Group routing. Symptoms: When you send multicast traffic over an IPSec tunnel, a memory leak may occur on a router. Workaround: Switch to software encryption for a while and then switch back to hardware encryption.

Symptoms: When you enter the show memory address command, irrespective of whether or not you place an optional keyword after the pipe vertical bar , the console or vty session hangs and cannot be restored without reloading the platform. This situation especially impacts the console, but as long as there is a vty session available, Telnet still functions.

Although the platform may return the initially requested data, it does not return the prompt. Conditions: This symptom is observed on a Cisco Catalyst series but is platform-independent. Workaround: Reload the platform. The stalled prompt will eventually recover but this could take many hours or even days. Further Problem Description: The symptom is expected behavior because the parser must scan the entire range of possible and ever growing memory addresses.

For this reason, we recommend against the use of the show memory address command, which will be removed from common usage in all future releases. Conditions: This symptom is observed when the Cisco series is configured for Fast Switching. Conditions: This symptom is observed on a Cisco router that is configured for the G. Workaround: Upgrade to IP Communicator 1. Symptoms: A Cisco AS reloads when you enter the redundancy handover peer-resources command to hand over the peer resources to the other RSC.

However, the symptom may not be platform-dependent and may occur on any platform that is configured with an AIM-ATM module. This caveat consists of the two symptoms, two conditions, and two workarounds:. Workaround 1: Before you disable MVPN on the VRF interface, enable and then disable multicast routing by entering the ip multicast-routing vrf vrf-name global configuration command followed by the no ip multicast-routing vrf vrf-name global configuration command. Symptoms: When Policy Based Routing PBR is configured with the set interface command, packets continue to be forwarded to an interface when that went down, causing packets to be dropped.

When the ip local policy route-map command is enabled, all locally-generated packets are impacted. Conditions: This symptom is observed on a Cisco router and only applies to packets that require process-switching.

Workaround: Do not enter the set interface command. Rather, enter the set ip next-hop command. Such failed sessions may accumulate, eventually causing router instability. These failed sessions can be seen in the output of the show crypto isakmp sa i MM command:. Conditions: These symptoms are observed when RSA signatures are used as the authentication method.

Workaround: Enter the shutdown interface configuration command followed by the no shutdown interface configuration command on the interface that is used for the IKE sessions or re-apply the crypto map to this interface. The symptom could also occur on a Cisco XM series that runs Release Conditions: This symptom is observed only for IMA interfaces that have the atm bandwidth dynamic command enabled.

Workaround: Issuing the command no atm bandwidth dynamic from the IMA interface can prevent the problem from happening. If the problem has been experienced already, using the command no atm bandwidth dynamic followed by a shutdown and subsequent no shutdown from the IMA interface can be used to workaround the problem and clear the inactive PVC condition. Symptoms: A Cisco series may generate the following error message, and links flap:.

Note that the symptom does not occur in Release Conditions: This symptom is observed under rare circumstances when a valid RSA key is composed of unusually short or long prime numbers and coefficient. Further Problem Description: The result of the wrong operation can be seen on the other side of the connection by activating the debug crypto engine and debug crypto isakmp commands. The following messages are related to the failure:. Symptoms: A router that is configured for IPSec may reload because of a stack or program counter corruption.

Conditions: This symptom is observed on a Cisco router that uses a certificate with a very long subject name of several hundred bytes when the distinguished name DN is used as an ISAKMP identity. The symptom does not occur for shorter subject names for example, characters. In most environments, a subject name of 80 characters or less is common. Symptoms: A Cisco crashes because of a bus error exception and alignment errors.

Conditions: This symptom is observed when a bid is processed and when an incorrect name is retrieved, causing an incorrect user name to be sent and the AAA authentication to fail. Reboot the router to temporarily resolve the symptoms. Further Problem Description: When the debug crypto engine error command is enabled, the following debug message is generated:.

Symptoms: When Cisco IOS software is secured using "secure boot" commands and after formatting the disk, the show disk command will not display the secured image and the corresponding configurations in the output. Conditions: This symptom occurs when securing the Cisco IOS software using the secure boot-config and the secure boot- image commands and formatting the disk. Symptoms: When a buffer leak occurs, the RP crashes because of the starvation of buffers. Symptoms: Data corruption may occur on a disk when directory entries are read by more than one process simultaneously.

Conditions: This symptom is observed on a Cisco platform that has an ATA file system when, for example, the dir disk0: command is entered on one vty connection and simultaneously, and for the same disk, the copy disk0: command is entered on another vty connection. The symptom may also occur in Release Symptoms: After a call is made between H.

Symptoms: The committed information rate CIR of policers is calculated incorrectly. Workaround: Re-apply the service policy on the interface that is configured with the crypto map. First Alternate Workaround: Enter the no route-cache cef command followed by the route-cache cef command. Second Alternate Workaround: Delete the crypto map from the interface and re-apply the crypto map.

The "Output Hold Queue Wedge" condition occurs on idle subinterfaces or when multiple point-to-point subinterfaces are "spawned" from a single subinterface by entering a PVC range command such as the following:. The symptom does not occur when the remote end or a signal initiates the call disconnect. Conditions: This symptom is observed when LDP is not configured on any interfaces via the mpls ip interface configuration command, which is typically the case when MPLS Traffic Engineering TE tunnels are used to transport AToM traffic between endpoints and when the mpls ip interface configuration command is not enabled on any TE tunnels.

The symptom occurs in Cisco IOS software releases that include the fix for caveat CSCec when any form of one of the following commands is configured on the router and appears in the running configuration:. Workaround: Enter the mpls ip command on a TE tunnel interface or temporarily on a physical interface to force LDP to be re-established.

Sniffer traces that are captured upstream and downstream from the SNASw router show that the data that is sent from the host to the SNASw router is fine, but when the data leaves the SNASw router, there are some corrupted bytes at the end of the data stream. Symptoms: A Cisco router that has a virtual-template interface that is configured for PPPoE may reload because of a software-forced crash.

Conditions: This symptom is observed on a Cisco platform that runs a crypto image and that functions as a spoke when the interface that connects to the hub flaps and receives a new IP address after the flap. Symptoms: A router may crash during a basic H.

Symptoms: A Cisco series may pause indefinitely when a neighbor reloads. Symptoms: Media negotiation fails for SIP calls and the terminating gateway replies with a "" message to an Invite message. Conditions: This symptom is observed when all LDP sessions are flapped many times with a pause of approximately 10 seconds between each flap. Workaround: Enter the clear cef linecard command for the affected line card.

This symptom typically occurs when fax devices are configured on the FXS port but is not limited to this configuration. Workaround: A reload of the router will be needed to clear this condition. The fix for this caveat is also integrated in Release Further Problem Description: If the router boots an image successfully once, then it is safe to assume that the symptom will not occur on the router. For some interfaces of the port adapter, the counters are always zero, and for others interfaces, the counters do increase but very slowly.

Conditions: This symptom is observed when you enter the show interfaces type slot command for a PA-MC-E3 port adapter. Note that the symptom does not occur when you enter the show interface type number stats command or the show interfaces type slot accounting command.

Also, when you enter the show interfaces type slot command for the VIP in which the PA-MC-E3 port adapter is installed, the counters provide correct information. Workaround: Enter the show interface type number stats command to retrieve the correct information.

Eventually, this leak causes memory fragmentation and causes the platform to reload. The gateway functions properly by failing media negotiation but the incorrect SDP data is released, causing the leak. The symptom may also affect port adapters in adjacent slots, and not only the port adapters in physically adjacent slots, but also the port adapters that are logically adjacent in the initialization path.

Note that high-speed or unchannelized serial port adapters are not affected. Further Problem Description: The following error messages and tracebacks are generated just before the crash occurs:. The crash may be observed when the show file system command is issued. There are total of 16 routers in this system, with pairs of 8 routers backing up each other. Sep 13 Conditions: This symptom may be observed when LDP is being used. It will not be observed with TDP. It may happen when LDP receives a protocol message larger than bytes right after receiving several Label Mapping messages smaller than 25 bytes.

This problem is likely to be accompanied by the presence of one of the following error message:. The above error message may be preceded by one of the following four error messages:. This problem may be seen in releases that include the fix for CSCeg but do not have the fix associated with this defect. On the mainframe side, the link appears to hang. This creates no problem in operation, except when issuing a GiveBack command or a Takeover command, in which case, the link towards the backup DLUS does not work.

Workaround: The situation can be cleared with a snasw stop session pcid using the PCID shown with the show snasw session local command. The following message is seen in the log:. Conditions: This symptom has been observed after issuing an inact giveback command at VTAM directed at the router:. Symptoms: The router crashes on removal of a Virtual-TokenRing subinterface.

The router also crashes on removal of a main Virtual-TokenRing interface when that main interface also has subinterfaces configured. Create a main Virtual-Tokenring interface. Create a Virtual-TokenRing subinterface on the interface created in step 1. Remove either the Virtual-TokenRing main interface created in step 1, or the Virtual-TokenRing subinterface created in step 2. Symptoms: A SegV exception crash may occur on a Cisco router that is configured for voice calls. Rather, configure Cisco Frame Relay encapsulation.

Conditions: This symptom is observed when you enter the clear vpdn all command, when the LNS reloads, when the IP link between the LSN and LAC is disrupted, or when any other event occurs that causes the tunnel to be reset. Symptoms: A router that is configured for Frame Relay crashes and generates the following error message:. Conditions: This symptom is observed on a Cisco router that has Frame Relay end-to-end fragmentation configured on an interface and hardware compression on a PVC.

Workaround: Configure map-class fragmentation with Frame Relay traffic-shaping instead of interface level fragmentation. Conditions: This symptom is observed only when the dialer order round-robin command is enabled. Workaround: Try a different dialer order such as last successful or sequential to prevent the tracebacks from being generated. This situation repeats itself continuously and may cause sporadic IP connectivity. Eventually, the call is cleared completely because the tunnel is disconnected by the LAC.

This situation causes the LAC to disconnect the tunnel. Conditions: This symptom is observed on a Cisco However, the symptom is platform-independent. Workaround: Enter the no ppp lcp fast-start command on the relevant asynchronous interfaces on the LAC. Symptoms: A router may reload when many PPPoE sessions are being initiated while memory availability is low or when many PPPoE sessions are being initiated and terminated.

Workaround: Configure the interface mtu command to the required value. Symptoms: A virtual-access interface fails to come up after you have configured virtual templates. Symptoms: A Cisco MC that is configured for LLQ drops packets from the priority queue and these drops are not accounted for in the output of the show policy-map interface output command.

Symptoms: When the radius-server retransmit 1 command is enabled on a NAS, the number of retransmit counts for a transaction with MS-IAS is more than the expected value. Symptoms: Spurious memory access errors and tracebacks may be generated on a Cisco AS Conditions: This symptom is observed when an interface that is registered for high capacity HC counters deregisters directly. Cisco IOS may permit arbitrary code execution after exploitation of a heap-based buffer overflow vulnerability.

Cisco has included additional integrity checks in its software, as further described below, that are intended to reduce the likelihood of arbitrary code execution. Cisco has made free software available that includes the additional integrity checks for affected customers. Symptoms: You may not be able to establish an outbound Telnet connection on a router, nor may you be able to establish a reverse Telnet connection into a modem from the router console.

Symptoms: A router may crash while loading the image for a secondary RSP from a disk during the boot process. Conditions: This symptom is observed on a Cisco series that is configured with redundant RSPs when the hw-module slot slot-number image disk0: image command is configured. Symptoms: When the local method is used at the beginning of a PPP authentication method list and when a user does not exist in the local database, failover to the next method in the method list does not occur.

Workaround: Temporarily remove the local method from the beginning of the method list. ALternate Workaround: If many interfaces are affected, reload all port adapters by entering the microcode reload command on the control plane of the RSP. Symptoms: Packet forwarding fails when the Ethertype is configured to 0x Symptoms: A channelized T3 port adapter cannot detect C-bit errors and does not shut down after continuous C-bit errors.

Conditions: This symptom is observed on a Cisco series that is configured with a channelized T3 port adapter. Symptoms: A router may intermittently transmit corrupt PPP packets. When you enter the debug ppp nego and debug ppp errors commands, it appears that "protocol reject" packets are received from the remote end. Workaround: On the Cisco 7xxx router where PRDI is reported on the POS interface, change the configuration of C2 byte to any other value different than the current value and then change it back to the original value.

After a reload, this symptom will be present again and the workaround will have to be performed again. Symptoms: Calls may not complete because ResvConfirm messages are dropped. You can enter the debug ip rsvp messages command to track RSVP messages as they traverse routers.

Workaround: Configure a static ARP entry that enables the router to properly encapsulate the packet by entering the arp ip-address hardware-address arpa command. The ip-address argument is the address of the next hop that is visible via the RSVP debugs for the ResvConfirm messages and the hardware-address argument is the MAC address of the interface of the next IP hop through which the ResvConfirm messages should be routed.

This can cause high CPU utilization on the router. Symptoms: A stale non-bestpath multipath remains in the RIB after the path information changes, and BGP does not consider the stale path part of the multipath. Conditions: This symptom is observed on a Cisco router that has the soft-reconfiguration inbound command enabled and occurs only when the BGP Multipath Loadsharing feature is enabled for three or more paths, that is, the number-of-paths argument of the maximum-paths number-of-paths command has a value of three or more.

Workaround: Disable the soft-reconfiguration inbound command for the neighbor sessions for which the BGP Multipath Loadsharing feature is enabled or reduce the maximum number of paths for the BGP Multipath Loadsharing feature to two. The routes that depend on these commands fail after a switchover.

Conditions: This symptom is observed on a Cisco series but is platform-independent. You can check the number of OSPF interfaces by entering the show ip ospf or show ip ospf interface interface-type interface-number brief command. Note that all interfaces that are covered by network statements are counted. Symptoms: A router that is configured for NAT may crash because of a bus error. Workaround: Disable H. If you must use H. This symptom does not occur when the router is configured for Multi-topology IS-IS without the transition mode.

Symptoms: A router running Cisco IOS software will reload unexpectedly, when the no passive-interface command is issued under the router isis configuration. Conditions: This symptom has been observed when the interface is configured to run ISIS and later changed to passive interface.

Workaround: Disable ISIS on the interface before changing it to passive, using the no ip router isis interface command. For example, if the calling-station ID is "cisco. This situation is not limited to a dot or a forward slash. Workaround: Try to avoid unusual characters such as a dot or a forward slash in a calling-station ID.

Symptoms: A SegV exception may occur on a router when you enter the write memory or copy running-config startup-config command. Conditions: This symptom is observed on a Cisco series and Cisco series when you enter the write memory or copy running-config startup-config command and when the NVRAM is corrupted. Further Problem Description: The symptom occurs both with software and hardware encryption. Symptoms: A call treatment plays only a busy tone instead of the audio file that is configured in the call treatment.

Conditions: This symptom is observed when call treatment is configured on a router that functions as a Cisco CallManager Express CME and when the call threshold is met. Symptoms: When you enter the distribute-list interface command in a global RIP routing context and the interface that is specified in the command is a VRF interface, the command is rejected with the following error message:.

Cisco ios software release 12 422t download fiu engineering citrix

Caveats describe unexpected behavior or defects in Cisco IOS software releases.

Cisco ios software release 12 422t download Cai dat teamviewer mien phi
What is citrix environment 58
Cisco ios software release 12 422t download 574
Cisco switch management software free Winscp not connecting to host
Cisco ios software release 12 422t download 745
Cisco ios software release 12 422t download You are responsible for determining if a feature that you are allowed to configure in Cisco Security Manager is not supported on the device. Symptoms: When Cisco IOS software click secured using "secure boot" commands and after formatting the disk, the show disk command will not display the secured image and the corresponding configurations in the output. Rather, configure the hunt-group master dialer interface. Symptoms: The line protocol on a serial link stays down and input CRC errors are generated. Conditions: This symptom is observed after you have performed an OIR of the card.
Cisco ios software release 12 422t download 649
Cisco ios software release 12 422t download Anydesk hidden
Upload mit filezilla 441

About ultravnc msi installer sorry, that

Something also fortinet client install not

Следующая статья backstage paragon software

Другие материалы по теме

  • Auto login tightvnc kali
  • Create sftp server winscp
  • Winscp secure ftp
  • 4 комментариев к “Cisco ios software release 12 422t download”

    1. Kaganris :

      how to open a file in cyberduck

    2. Taktilar :

      ultravnc set username

    3. Faurg :

      comodo сертификат

    4. Nirr :

      winscp root folder


    Оставить отзыв