Cisco Cisco IOS Software Release 12.4(4)T

Cisco IOS Release 12.4(11)T3 is a rebuild release for Cisco IOS Release 12.4(11)T. The caveats in this 
section are resolved in Cisco IOS Release 12.4(11)T3 but may be open in previous Cisco IOS releases. 

The following information is provided for each caveat:

Symptoms—A description of what is observed when the caveat occurs.

Conditions—The conditions under which the caveat has been known to occur.

Workaround—Solutions, if available, to counteract the caveat.

CSCsg63809

Symptoms: Cisco IOS CLI commands that contain the slash character (/) are not interpreted 
correctly when executed over HTTP using HTTP POST.

Conditions: This symptom is observed when the HTTP POST method is used to configure 
commands such as the interface GigabitEthernet0/1 command.

Workaround: Execute Cisco IOS CLI commands that contain the slash character over SSH or Telnet. 

CSCek47667

Symptoms: A router may not clear BGP routes when you enter the clear bgp ipv6 unicast * 
command.

Conditions: This symptom is observed on a Cisco router that runs Cisco IOS Release 12.2SXF but 
is not release-specific.

Workaround: There is no workaround. 

CSCsg76408

Symptoms: Multicast traffic from a DMVPN spoke is dropped by a hub when CEF is enabled on the 
tunnel interface of the hub. This situation causes the spoke to remain in registering mode and the 
hub to forward the decapsulated data.

Conditions: This symptom is observed on a Cisco router that runs Cisco IOS Release 12.4(9)T1 or 
an earlier release in a DMVPN environment when the mGRE tunnel interfaces are within a VRF.

Workaround: Disable CEF on the tunnel interface of the hub. Doing so enables the hub to receive 
the multicast traffic, although the traffic is then process-switched. 

CSCsh84102

Symptoms: The following symptoms may occur:

Some DMVPN spokes become unreachable and a loop appears in a traceroute.

When you enter the show adjacency details command on the hub, the output shows that the 
adjacency rewrite information for a problematic spoke is the same as for another spoke.

There is an inconsistency between the NHRP cache and the adjacency for the problematic 
spoke.