From: Lupi, Guy (Guy.Lupi@xxxxxxxxxxxxx)
Date: Mon Apr 15 2002 - 21:54:39 GMT-3
I know this is often considered a cop out, but what IOS version are you
using? I had a problem similar to this with anything below 12.1(12). My
issue was that only one bri would come up, and it was always the opposite
bri on each router. So if router 1 had bri0/0:1 up, router 2 would have
bri0/0:2 up. Couldn't get it to work for the life of me, upgraded to
12.1(12) and haven't had a problem since.
-----Original Message-----
From: Jaspreet Bhatia
To: dmadlan@qwest.com
Cc: Ali; Jeffery S Kimes; ccielab@groupstudy.com; nobody@groupstudy.com
Sent: 4/15/2002 7:56 PM
Subject: Re: Second BRI channel does not come up
Ok I have removed the second dialer map command and also used 3 as the
value for dialer load-threshold command now .
GreenBay#sh int bri1/0:1
BRI1/0:1 is up, line protocol is up
Hardware is BRI
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
reliability 255/255, txload 83/255, rxload 83/255
Encapsulation PPP, loopback not set
Keepalive set (10 sec)
LCP Open, multilink Open
Last input 00:00:02, output 00:00:02, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 53 drops; input queue 0/75, 13 drops
5 minute input rate 21000 bits/sec, 4 packets/sec
5 minute output rate 21000 bits/sec, 4 packets/sec
3694 packets input, 529811 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
13 input errors, 0 CRC, 13 frame, 0 overrun, 0 ignored, 13 abort
3875 packets output, 542905 bytes, 1 underruns
1 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
805 carrier transitions
GreenBay#sh dialer
BRI1/0 - dialer type = ISDN
Dial String Successes Failures Last DNIS Last status
8995101 7 44 00:00:19 failed
4 incoming call(s) have been screened.
0 incoming call(s) rejected for callback.
BRI1/0:1 - dialer type = ISDN
Idle timer (300 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is multilink member
Dial reason: ip (s=172.10.129.1, d=172.10.129.2)
Connected to 8995101 (SanDiego)
BRI1/0:2 - dialer type = ISDN
Idle timer (300 secs), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is idle
As you can see gentlemen that the load on the first BRI channel has gone
all the way upto 83/255 due to the extended pings that I am generating
from
the other side .but still the second BRI channel does not come up . ANy
ideas ?
Jaspreet
At 06:34 PM 4/15/2002 -0500, MADMAN wrote:
> I agree with Ali, personally I simply use dialer string xxxxxxx.
Also
>I was told some time ago by a TAC engineer that the lowest dialer
>threshold was 3. You could configure 1 or 2 butg 3 was more effective.
>I wish I could remeber why but it is what I have done since
succesfully.
>
> Dave
>
>Ali wrote:
> >
> > Why are you using two dialer map statements?? try with out the
second
> one...
> > Also send output of SHOW ISDN STATUS
> >
> > ----- Original Message -----
> > From: "Jaspreet Bhatia" <jasbhati@cisco.com>
> > To: "Jeffery S Kimes" <kimes@us.ibm.com>
> > Cc: <ccielab@groupstudy.com>; <nobody@groupstudy.com>
> > Sent: Monday, April 15, 2002 3:23 PM
> > Subject: Re: Second BRI channel does not come up
> >
> > > Hello,
> > >
> > > I am using two dialer map statements pointing to the remote
router's two
> > LDNs
> > >
> > > Current configuration:
> > > !
> > > version 12.1
> > > service timestamps debug uptime
> > > service timestamps log uptime
> > > no service password-encryption
> > > !
> > > hostname GreenBay
> > > !
> > > !
> > > username SanDiego password 0 cisco
> > > !
> > > !
> > > !
> > > !
> > > ip subnet-zero
> > > no ip domain-lookup
> > > !
> > > isdn switch-type basic-ni
> > > cns event-service server
> > > !
> > > !
> > > !
> > > !
> > > !
> > > !
> > > !
> > > !
> > > !
> > > interface Ethernet0/0
> > > ip address 170.10.22.1 255.255.255.0
> > > no keepalive
> > > !
> > > interface Ethernet0/1
> > > no ip address
> > > shutdown
> > > !
> > > interface BRI1/0
> > > ip address 172.10.129.1 255.255.255.252
> > > encapsulation ppp
> > > ip ospf cost 9999
> > > ip ospf demand-circuit
> > > dialer idle-timeout 300
> > > dialer map ip 172.10.129.2 name SanDiego broadcast 8995101
> > > dialer map ip 172.10.129.2 name SanDiego broadcast 8995102
> > > dialer load-threshold 1 either
> > > dialer-group 1
> > > isdn switch-type basic-ni
> > > isdn spid1 5401 8995401
> > > isdn spid2 5402 8995402
> > > ppp authentication chap
> > > ppp multilink
> > > !
> > > interface BRI1/1
> > > no ip address
> > > shutdown
> > > isdn switch-type basic-ni
> > > !
> > > interface BRI1/2
> > > no ip address
> > > shutdown
> > > isdn switch-type basic-ni
> > > !
> > > interface BRI1/3
> > > no ip address
> > > shutdown
> > > isdn switch-type basic-ni
> > > !
> > > interface BRI1/4
> > > no ip address
> > > shutdown
> > > isdn switch-type basic-ni
> > > !
> > > interface BRI1/5
> > > no ip address
> > > shutdown
> > > isdn switch-type basic-ni
> > > !
> > > interface BRI1/6
> > > no ip address
> > > shutdown
> > > isdn switch-type basic-ni
> > > !
> > > interface BRI1/7
> > > no ip address
> > > shutdown
> > > isdn switch-type basic-ni
> > > !
> > > interface Ethernet2/0
> > > no ip address
> > > shutdown
> > > !
> > > interface Ethernet2/1
> > > no ip address
> > > shutdown
> > > !
> > > interface Ethernet2/2
> > > no ip address
> > > shutdown
> > > !
> > > interface Ethernet2/3
> > > no ip address
> > > shutdown
> > > !
> > > interface Serial3/0
> > > bandwidth 56000
> > > no ip address
> > > encapsulation frame-relay
> > > no fair-queue
> > > !
> > > interface Serial3/0.1 point-to-point
> > > bandwidth 56
> > > ip address 172.10.29.1 255.255.255.252
> > > frame-relay interface-dlci 201
> > > !
> > > interface Serial3/1
> > > bandwidth 64
> > > ip address 170.10.23.1 255.255.255.252
> > > clockrate 64000
> > > !
> > > interface Serial3/2
> > > no ip address
> > > shutdown
> > > !
> > > interface Serial3/3
> > > no ip address
> > > shutdown
> > > !
> > > interface Serial3/4
> > > no ip address
> > > shutdown
> > > !
> > > interface Serial3/5
> > > no ip address
> > > shutdown
> > > !
> > > interface Serial3/6
> > > no ip address
> > > shutdown
> > > !
> > > interface Serial3/7
> > > no ip address
> > > shutdown
> > > !
> > > router eigrp 1
> > > redistribute ospf 1 metric 10000 100 100 1 1500
> > > passive-interface BRI1/0
> > > passive-interface Serial3/0
> > > network 170.10.0.0
> > > no auto-summary
> > > no eigrp log-neighbor-changes
> > > !
> > > router ospf 1
> > > log-adjacency-changes
> > > redistribute eigrp 1 subnets route-map eigrp-to-ospf
> > > passive-interface Serial3/1
> > > network 172.10.29.1 0.0.0.0 area 0
> > > network 172.10.129.1 0.0.0.0 area 0
> > > !
> > > ip classless
> > > no ip http server
> > > !
> > > !
> > > map-class dialer myclass
> > > dialer callback-server username
> > > !
> > > map-class dialer class
> > > access-list 1 permit 170.10.129.0 0.0.0.3
> > > dialer watch-list 2 ip 170.10.49.0 255.255.255.0
> > > dialer-list 1 protocol ip permit
> > > route-map eigrp-to-ospf deny 10
> > > match ip address 1
> > > !
> > > route-map eigrp-to-ospf permit 20
> > > !
> > > !
> > > !
> > > !
> > > alias exec s show ip int brief
> > > !
> > > line con 0
> > > transport input none
> > > line aux 0
> > > line vty 0 4
> > > !
> > > end
> > >
> > > As you can see the interface BRI 1/0:1 is being shown as a
multilink
> > > member . but the second BRI channel does not come up .
> > >
> > >
> > >
> > >
> > > GreenBay#sh dialer
> > >
> > > BRI1/0 - dialer type = ISDN
> > >
> > > Dial String Successes Failures Last DNIS Last status
> > > 8995102 0 17 00:00:08 failed
> > > 8995101 3 18 00:00:08 failed
> > > 4 incoming call(s) have been screened.
> > > 0 incoming call(s) rejected for callback.
> > >
> > > BRI1/0:1 - dialer type = ISDN
> > > Idle timer (300 secs), Fast idle timer (20 secs)
> > > Wait for carrier (30 secs), Re-enable (15 secs)
> > > Dialer state is multilink member
> > > Dial reason: ip (s=172.10.129.1, d=172.10.129.2)
> > > Connected to 8995101 (SanDiego)
> > >
> > > BRI1/0:2 - dialer type = ISDN
> > > Idle timer (300 secs), Fast idle timer (20 secs)
> > > Wait for carrier (30 secs), Re-enable (15 secs)
> > > Dialer state is idle
> > >
> > > BRI1/1 - dialer type = ISDN
> > >
> > > --More--
> > >
> > >
> > > Thanks
> > >
> > > Jaspreet
> > >
> > > At 02:25 PM 4/15/2002 -0700, Jeffery S Kimes wrote:
> > >
> > > >Let's look at the config of the dialing router.
> > > >
> > > >I would pay particular attention to see if you had two dialer
maps...
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Jaspreet
> > > > Bhatia
> > > >
> > > > <jasbhati@cisco.c To:
> > > > ccielab@groupstudy.com
> > > > om> cc:
> > > >
> > > > Sent by: Subject: Second
BRI
> > > > channel does not come up
> > > > nobody@groupstudy
> > > >
> > > > .com
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > 04/15/2002
> > > > 01:59
> > > >
> > > > PM
> > > >
> > > > Please respond
> > > > to
> > > >
> > > > Jaspreet
> > > > Bhatia
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >Guys,
> > > > I have never been able to get my second BRI
> channel up
> > > >and running .Here is what I am doing
> > > >1) dialer load-threshold 1 either
> > > >
> > > >2) encap ppp
> > > >
> > > >3) ppp auth chap
> > > >
> > > >4) ppp multilink
> > > >
> > > >5) Gave two spids and two LDN's
> > > >
> > > >
> > > > I am running the BRI circuit between two 3600 routers running
on 12.1
> > > >code Enterprise .
> > > >
> > > >Am I missing something here ?
> > > >
> > > >TIA
> > > >
> > > >Jaspreet
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:08 GMT-3