Cisco Cisco IOS Software Release 12.4(4)T

<snip>

IF-MIB1.3.6.1.2.1.2.2.1.2.5ifDescr.5T1 0/0/1

IF-MIB1.3.6.1.2.1.2.2.1.2.7ifDescr.7Async0/1/0

<snip>

So the interface is indexed on the router but the snmpwalk/snmpget does not seem to return the 
value.

Test was run with snmpv2 whereas the customer was running snmpv3. This test was run with and 
without the CME configuration. Both do not return Async18 interface ifIndex 6.

Conditions: This symptom is observed on a Cisco 3825 router that is running Cisco IOS 
Release 12.4(4)XC5.

Workaround: There is no workaround. 

CSCsh20336

Symptoms: A spoke may be unable to connect or reconnect to a hub because there may not be a 
crypto socket.

Conditions: This symptom is observed in a DMVPN Hub-to-Spoke environment.

Workaround: Remove the static NHRP entry from the tunnel interface that connects the spoke to the 
hub, and reapply the static NHRP entry. 

CSCsh31605

Symptoms: In a dial backup scenario with backup EzVPN over an asynchronous or dialer interface, 
EzVPN fails to kickoff the asynchronous or dialer interface intermittently. Dial backup EzVPN 
cannot be brought up always. It works intermittently.

IKE request packet in failure cases is dropped with the following error:

*Oct  5 07:39:22.187: EZVPN(backup): New State: READY

*Oct  5 07:39:22.187: EZVPN(backup): Current State: READY

*Oct  5 07:39:22.187: EZVPN(backup): Event: CONNECT

*Oct  5 07:39:22.187: EZVPN(backup): No state change

*Oct  5 07:39:22.187: ISAKMP:(0):receive null address from sa_req (local 

0.0.0.0, remote 10.175.161.41)

*Oct  5 07:39:22.191: ISAKMP: Error while processing SA request: Failed to 

initialize SA

*Oct  5 07:39:22.191: ISAKMP: Error while processing KMI message 0, error 2.

*Oct  5 07:40:03.551: ISAKMP:(2018):purging SA., sa=841CC6D0, delme=841CC6D0

Conditions: This symptom occurs in a dial backup scenario with backup EzVPN over an 
asynchronous or dialer interface

Workaround: There is no workaround. 

CSCsh37414

Symptoms: EzVPN leaks some memory with the fix of CSCsg94570. It can take a long time for the 
box to run out of memory causing a reload.

Conditions: This symptom is observed when EzVPN leaks memory.

Workaround: There is no workaround.