cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
554
Views
0
Helpful
5
Replies

Bond two T1s with VWIC 2MFT-T1 over ATM - Need Assistance Please

adam.miller
Level 1
Level 1

I've found some multilink ppp configs that look great, but it doesn't look like it will work with my hardware setup. We are currently running a T1, and need to upgrade to a bonded 3meg connection. I'd really appreciate some suggestions. Here's some output.

OS (tm) C2600 Software (C2600-IS-M), Version 12.3(3g), RELEASE SOFTWARE (fc1)

cisco 2650XM (MPC860P) processor (revision 0x300) with 124928K/6144K bytes of memory.

Primary Rate ISDN software, Version 1.1.

1 FastEthernet/IEEE 802.3 interface(s)

2 ATM network interface(s)

2 Channelized T1/PRI port(s)

1 ATM AIM(s)

32K bytes of non-volatile configuration memory.

49152K bytes of processor board System flash (Read/Write)

controller T1 0/0

mode atm aim 0

framing esf

linecode b8zs

cablelength short 133

!

controller T1 0/1

mode atm aim 0

framing esf

linecode b8zs

!

!

!

interface ATM0/0

no ip address

ip pim sparse-dense-mode

no scrambling-payload

atm uni-version 3.1

no atm ilmi-keepalive

!

interface ATM0/0.101 point-to-point

ip address x.x.x.x 255.255.255.252

ip access-group xxxx in

ip pim sparse-dense-mode

pvc xxx 1/101

protocol ip x.x.x.x broadcast

broadcast

encapsulation aal5snap

5 Replies 5

wochanda
Level 4
Level 4

Sounds like you're going to want to look at ATM IMA. It'll let you bond both of your T1's into 1 logical ATM interface, much like multilink PPP. The difference is IMA is terminated by the provider, while Multilink PPP is terminated by the other end. Here is more info:

http://www.cisco.com/en/US/tech/tk39/tk356/technologies_configuration_example09186a0080174992.shtml

http://www.cisco.com/en/US/tech/tk39/tk356/technologies_q_and_a_item09186a0080111162.shtml

I've input the config just like the sample shows, but my IMA interface and subinterface remains at down/down.. Any tips? I've called the service provider and they tell me their IMA group is correct. I currently only have one interface in the ima group so I can continue to use the old circuit for internet. You'll probably also notice I have no IP address on the IMA sub interface. That's also so I can use the internet to post this message. EVen with an IP, my IMA interfaces do not come up.

controller T1 0/1

mode atm aim 0

framing esf

linecode b8zs

interface ATM0/1

no ip address

no scrambling-payload

ima-group 0

no atm ilmi-keepalive

!

interface ATM0/IMA0

no ip address

no atm ilmi-keepalive

!

interface ATM0/IMA0.1 point-to-point

pvc 1/100

encapsulation aal5snap

Taylorsville#show ima int

Interface ATM0/IMA0 is down

Group index is 9

Ne state is insufficientLinks, failure status is insufficientLinksNe

IMA Group Current Configuration:

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 ATM0/1

Test pattern procedure is disabled

IMA Group Total Counters (time elapsed 0 seconds):

0 Tx cells, 0 Rx cells

2 Ne Failures, 3 Fe Failures, 543 Unavail Secs

IMA link Information:

Link Physical Status NearEnd Rx Status Test Status

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

ATM0/1 up usable disabled

Taylorsville#show atm pvc

VCD / Peak Avg/Min Burst

Interface Name VPI VCI Type Encaps SC Kbps Kbps Cells Sts

0/0.101 Dist-155 1 101 PVC SNAP UBR 1536 UP

0/IMA0.1 1 1 100 PVC SNAP UBR 1536 INAC

Taylorsville#

Taylorsville#

Just to update... I updated to IOS to 12.4 release and my IMA interfaces came up like they should. I'm wondering why I still don't have end to end connectivity. I am unable to even ping the IP of the local sub interface, although it is up/up.

Could be a problem with the way the PVC is provisioned in the telco, or a problem with the remote end.

When you ping the IP of your subinterface, the ping packet is sent out the PVC to the remote end, which is supposed to send it back to you. If the other end doesn't get your ping, or it isn't configured correctly pings to your own interface will fail.

My best suggestion will be to do the following:

Insert T1 loopback plugs into both T1's on your router and ping again.

If successful, put a T1 loopback plug on the opposite end. If this is successful there is a problem with remote router, if it fails there is a problem with the telco.

Also,

Make sure the following is in your config:

network-clock-participate aim 0

network-clock-participate wic 0

network-clock-select 1 t1 0/1

If the WIC isn't in slot 0, change the 0 to whichever slot it is in.

If T1 0/1 isn't the lowest numbered T1 coming into the router, change the command to reflect that too.

Review Cisco Networking products for a $25 gift card