ATM IMA Configuration Problem

Unanswered Question

I have a 2600 with at NM-4T1-IMA. I am trying to bond 2 t1's from Qwest for our DSL hosting. I have the 2600 configured like Qwest's sample config for my router but we cannot get the ATM interfaces to come up. If qwest loops my t1s they come up. What is strange is the moment we remove ima-group command from the ATM interface the t1s come up.

We are running 12.3 (26) and we have atm ATM-IMA card installed as well. Qwest is configured for ima 1.0. I have tried different clock modes on the ima interface and on the ATM interfaces. Qwest is saying they are configured for EFS/B8ZS.

Here are the relevent parts of the router:

interface ATM1/0

no ip address

no atm ilmi-keepalive

ima-group 0

no scrambling-payload

!

interface ATM1/1

no ip address

no atm ilmi-keepalive

ima-group 0

no scrambling-payload

!

interface ATM1/IMA0

no ip address

no atm ilmi-keepalive

!

interface ATM1/IMA0.132 point-to-point

bandwidth 3072

ip address 10.10.10.41 255.255.255.252

ip nbar protocol-discovery

no ip mroute-cache

atm route-bridged ip

no snmp trap link-status

pvc 1/32

ubr 3072

encapsulation aal5snap

!

!

VRC_E29_32_C2611_xxx_123_CORE#sh atm interface atM 1/0

Interface ATM1/0:

AAL enabled: AAL5 , Maximum VCs: 255, Current VCCs: 0

Maximum Transmit Channels: 0

VCIs per VPI: 1024,

Max. Datagram Size: 4528

PLIM Type: DS1, TX clocking: LINE

Cell-payload scrambling: OFF

0 input, 0 output, 0 IN fast, 0 OUT fast, 0 out drop

Avail bw = 1536

Config. is ACTIVE

VRC_E29_32_C2611_xxx_123_CORE#sh atm interface atM 1/ima0

Interface ATM1/IMA0:

AAL enabled: AAL5 , Maximum VCs: 255, Current VCCs: 0

Maximum Transmit Channels: 0

VCIs per VPI: 1024,

Max. Datagram Size: 4528

PLIM Type: DS1 IMA, TX clocking: IMA ITC

0 input, 0 output, 0 IN fast, 0 OUT fast, 0 out drop

Avail bw = 3072

Config. is ACTIVE

VRC_E29_32_C2611_xxx_123_CORE#sh atm interface atM 1/ima0

Interface ATM1/IMA0:

AAL enabled: AAL5 , Maximum VCs: 255, Current VCCs: 0

Maximum Transmit Channels: 0

VCIs per VPI: 1024,

Max. Datagram Size: 4528

PLIM Type: DS1 IMA, TX clocking: IMA ITC

0 input, 0 output, 0 IN fast, 0 OUT fast, 0 out drop

Avail bw = 3072

Config. is ACTIVE

VRC_E29_32_C2611_xxx_123_CORE# sh ima interface

Interface ATM1/IMA0 is down

Group index is 26

Ne state is startUp, failure status is startUpNe

Active links bitmap 0x0

IMA Group Current Configuration:

Tx/Rx configured links bitmap 0x3/0x3

Tx/Rx minimum required links 1/1

Maximum allowed diff delay is 25ms, Tx frame length 128

Ne Tx clock mode ITC

Test pattern procedure is disabled

IMA Group Current Counters (time elapsed 368 seconds):

0 Ne Failures, 0 Fe Failures, 476 Unavail Secs

IMA Group Total Counters (last 0 15 minute intervals):

0 Ne Failures, 0 Fe Failures, 0 Unavail Secs

IMA link Information:

Link Physical Status NearEnd Rx Status Test Status

---- --------------- ----------------- -----------

ATM1/0 down unusableFailed disabled

ATM1/1 down unusableFailed disabled

Interface ATM1/IMA1 is down

Group index is 45

Ne state is notConfigured, failure status is noFailure

Active links bitmap 0x0

IMA Group Current Configuration:

Tx/Rx configured links bitmap 0x0/0x0

Tx/Rx minimum required links 1/1

Maximum allowed diff delay is 25ms, Tx frame length 128

Ne Tx clock mode CTC, configured timing reference link ATM1/0

Test pattern procedure is disabled

IMA link Information:

Link Physical Status NearEnd Rx Status Test Status

---- --------------- ----------------- -----------

VRC_E29_32_C2611_xxx_123_CORE#

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Giuseppe Larosa Sun, 11/01/2009 - 01:10

Hello Dylan,

sorry for that, but providing links is the first line of help.

I think something is going wrong with IMA negotiation messages, the fact that each link in stand-alone mode goes up means that encoding and clock are fine.

You may be facing a bug that affects ATM IMA in your device.

I would give a try to another IOS image.

If I remember correctly in another thread the solution was an IOS change.

Hope to help

Giuseppe

Giuseppe-

I was thinking that as well. But that that turned out not to be the problem. We had Qwest send a tech to check the NIU. They said the NIU was fine, but ever since the tech touched the circuit it has been running clean. I wonder if the NIU wasn't seated right or something.

Thanks for your help though,

Dylan

Giuseppe Larosa Mon, 11/02/2009 - 01:30

Hello Dylan,

thanks for reporting the solution of your issue.

this can help somebody else.

So the issue was on the service provider side.

I suppose the NIU is a device provided by provider to your premises.

Best Regards

Giuseppe

Actions

This Discussion