I have a 3825 router with a NM-8T1-IMA NM module configured as follows:
interface ATM1/0 no ip address ip pim sparse-mode no scrambling-payload ima-group 0 no atm ilmi-keepalive clock source line
interface ATM1/1 no ip address ip pim sparse-mode no scrambling-payload ima-group 0 no atm ilmi-keepalive clock source line
interface ATM1/2 no ip address ip pim sparse-mode no scrambling-payload ima-group 0 no atm ilmi-keepalive clock source line
interface ATM1/3 no ip address ip pim sparse-mode no scrambling-payload ima-group 0 no atm ilmi-keepalive clock source line
interface ATM1/4 no ip address ip pim sparse-mode no scrambling-payload ima-group 0 no atm ilmi-keepalive clock source line
interface ATM1/5 no ip address ip pim sparse-mode no scrambling-payload ima-group 0 no atm ilmi-keepalive clock source line
interface ATM1/IMA0 no ip address ip pim sparse-mode
ima clock common 0 no atm ilmi-keepalive
interface ATM1/IMA0.32 point-to-point description PVC to Grand River Hospital ip address x.x.x.x 255.255.255.252 ip pim sparse-mode ip igmp version 3 pvc 1/32 vbr-nrt 4000 4000 encapsulation aal5snap
The ATM interfaces will show a status of Receive "FailedNoReason" after applying a shut, no shut. It appears that the interfaces flap when attempting to join the IMA group. I am sure I am missing something simple since I'm tired and have a migraine at the moment.
The 3825 is replacing a 2821 with the ATM bundle and 3 vwics. I am currently working on upgrading from 3 T1s to 5 T1s at this site, and that is why we went with the 3825 and the NM-8T1-IMA. The T1s on the carrier side are up with no error, and are working flawlessly on the 2821 at the moment (I had to cut back over to it for business today).
On the 3825/NM-8T1-IMA if I remove one of the ATM interfaces from the IMA group it will come up, but if it assigned to the IMA group it will initially come up, and then go down after about 10 seconds. I had ATM and IMA error debuging on and I did not see any errors.
I'm not on my work laptop so I will have to see if I saved the captures from the sh ima interface etc. I believe the Rx was going into a unusable failed state.
My first thought was that I have the clock source setup wrong on the IMA group?
Took another stab at trying to get this to work last night and was not able to get the ATM interfaces to come up/up. If I removed the ATM interface from the IMA group it did go up/up, so it appears to be that the framing, etc on the T1 is correct. It appears to be failing in the startup of the IMA group and bouncing the T1s. Here is what I was seeing on the router last night:
Just a quick update on this. Worked on the issue some more tonight. I am able to get this to work back to back between a Cisco 3640 and the Cisco 3825. I was able to replicate the same issue with a Cisco 3640 onsite as well. After speaking with Qwest who provides our circuits it seems almost like an IMA version mismatch. I am still showing a los of delay on the NE, although one of the ATM links did come up for a few seconds after they changed the IMA version to 1.0. Version was changed back to IMA 1.1 and I'm back with the same 5 links all in fault with a LODfailure. I plan on talking to Qwest again tomorrow, but if anyone can think of a config change I can do on our end that would be great. I don't see any mention of the IMA version so I assume it is on 1.0, where as the 2821 would be at 1.1.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...