From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Fri Apr 09 2004 - 20:43:32 GMT-3
Richard,
No, because LMI is only locally significant. That's why Frame Relay EEK is needed. You typically don't notice this in the lab because there is only one frame-relay switch.
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
________________________________________
From: Richard Dumoulin [mailto:richard.dumoulin@vanco.es]
Sent: Friday, April 09, 2004 6:07 PM
To: Brian McGahan; ccie2002@bellsouth.net; ccielab@groupstudy.com
Subject: RE: RE: Internetworkexpert Lab 2
Even if there are multiple switches in between, the pvc on R5 should show inactive right ?
-----Original Message-----
From: Brian McGahan [mailto:bmcgahan@internetworkexpert.com]
Sent: sabado, 10 de abril de 2004 0:58
To: ccie2002@bellsouth.net; ccielab@groupstudy.com
Subject: RE: RE: Internetworkexpert Lab 2
Do you have multiple frame-relay switches in the transit path? The problem is that the VC status on R4 is not affecting the VC status on R5. Enable Frame Relay end to end Keepalives on R4 and R5.
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> ccie2002@bellsouth.net
> Sent: Friday, April 09, 2004 5:27 PM
> To: Brian McGahan; ccielab@groupstudy.com
> Subject: RE: RE: Internetworkexpert Lab 2
>
> Brian:
>
>
> Per your request I have admin down serial 0. For grins, I went to the
> remote router (R5) and had Debug isdn q931 and ppp auth and nothing
> showed up when I shut down ser 0. My interesting traffic statement on
> R5 is permit ip. I even tried permit clns_is. Any help would be great.
>
>
> Cisco2504_R4#show ip int brief
> Interface IP-Address OK? Method Status
> Prot
> ocol
> BRI0 132.1.45.4 YES NVRAM up
> up
>
> BRI0:1 unassigned YES unset down
> down
>
> BRI0:2 unassigned YES unset down
> down
>
> Loopback0 150.1.4.4 YES NVRAM up
> up
>
> Serial0 132.1.0.4 YES NVRAM administratively
> down down
>
> Serial1 unassigned YES NVRAM administratively
> down down
>
> TokenRing0 unassigned YES NVRAM administratively
> down down
>
> Virtual-Access1 unassigned YES TFTP down
> down
>
> Cisco2504_R4#
>
>
>
>
> >
> > From: "Brian McGahan" <bmcgahan@internetworkexpert.com>
> > Date: 2004/04/09 Fri PM 05:58:28 EDT
> > To: <ccie2002@bellsouth.net>,
> > <ccielab@groupstudy.com>
> > Subject: RE: RE: Internetworkexpert Lab 2
> >
> > Shut the interface S0 down on R4 and repaste the sh ip int brief.
> >
> > Brian McGahan, CCIE #8593
> > bmcgahan@internetworkexpert.com
> >
> > Internetwork Expert, Inc.
> > http://www.InternetworkExpert.com
> > Toll Free: 877-224-8987 x 705
> > Outside US: 775-826-4344 x 705
> >
> > > -----Original Message-----
> > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
Behalf
> > Of
> > > ccie2002@bellsouth.net
> > > Sent: Friday, April 09, 2004 3:54 PM
> > > To: Brian McGahan; ccielab@groupstudy.com
> > > Subject: Re: RE: Internetworkexpert Lab 2
> > >
> > > All thank for responding..So many good ideas.
> > >
> > > Below is the info you requested..
> > >
> > >
> > > Router 3 below
> > >
> > > ^
> > >
> > > Cisco2502_R3#show ip int brief
> > > Interface IP-Address OK? Method Status
> > > Prol
> > > Async1 132.1.23.3 YES NVRAM up
> > > up
> > > Loopback0 150.1.3.3 YES NVRAM up
> > > up
> > > Loopback1 132.1.33.3 YES NVRAM up
> > > up
> > > Serial0 132.1.0.3 YES NVRAM up
> > > up
> > > Serial1 unassigned YES NVRAM up
> > > up
> > > Serial1.1 132.1.35.3 YES manual up
> > > up
> > > TokenRing0 132.1.3.3 YES NVRAM up
> > > up
> > > Cisco2502_R3#
> > >
> > >
> > >
> > > router 4 below
> > >
> > >
> > >
> > > Cisco2504_R4#show ip int brief
> > > Interface IP-Address OK? Method Status
> > > Prol
> > > BRI0 132.1.45.4 YES NVRAM up
> > > up
> > > BRI0:1 unassigned YES unset down
> > > dow
> > > BRI0:2 unassigned YES unset down
> > > dow
> > > Loopback0 150.1.4.4 YES NVRAM up
> > > up
> > > Serial0 132.1.0.4 YES NVRAM up
> > > up
> > > Serial1 unassigned YES NVRAM
administratively
> > > down dow
> > > TokenRing0 unassigned YES NVRAM
administratively
> > > down dow
> > > Virtual-Access1 unassigned YES TFTP down
> > > dow
> > > Cisco2504_R4#
> > >
> > > Route 5 below
> > >
> > >
> > >
> > > Cisco2503_R5#show ip int brief
> > > Interface IP-Address OK? Method Status
> > > Prol
> > > BRI0 132.1.45.5 YES NVRAM standby mode
> > > dow
> > > BRI0:1 unassigned YES unset
administratively
> > > down dow
> > > BRI0:2 unassigned YES unset
administratively
> > > down dow
> > > Ethernet0 192.10.1.5 YES NVRAM up
> > > up
> > > Loopback0 150.1.5.5 YES NVRAM up
> > > up
> > > Loopback1 132.1.5.5 YES NVRAM up
> > > up
> > > Serial0 unassigned YES TFTP up
> > > up
> > > Serial0.1 132.1.35.5 YES manual up
> > > up
> > > Serial1 unassigned YES TFTP
administratively
> > > down dow
> > > Virtual-Access1 unassigned YES TFTP down
> > > dow
> > > Cisco2503_R5#
> > >
> > >
> > >
> > >
> > > >
> > > > From: "Brian McGahan" <bmcgahan@internetworkexpert.com>
> > > > Date: 2004/04/09 Fri AM 10:54:04 EDT
> > > > To: <ccie2002@bellsouth.net>, <ccielab@groupstudy.com>
> > > > Subject: RE: Internetworkexpert Lab 2
> > > >
> > > > What is the line protocol status of the subinterface
where the
> > > > "backup interface" command is configured? Unless the line
protocol
> > is
> > > > down the interface in standby mode will remain so. Paste a
"show ip
> > int
> > > > brief" from R3, R4, and R5.
> > > >
> > > >
> > > > HTH,
> > > >
> > > > Brian McGahan, CCIE #8593 bmcgahan@internetworkexpert.com
> > > >
> > > > Internetwork Expert, Inc. http://www.InternetworkExpert.com
> > > > Toll Free: 877-224-8987 x 705
> > > > Outside US: 775-826-4344 x 705
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
> > Behalf
> > > > Of
> > > > > ccie2002@bellsouth.net
> > > > > Sent: Thursday, April 08, 2004 9:37 PM
> > > > > To: ccielab@groupstudy.com
> > > > > Subject: Internetworkexpert Lab 2
> > > > >
> > > > > All:
> > > > >
> > > > > I am working on the internetwork lab and I am having problems
> > > > > with my isdn. The goal is go have the frame relay go down.
Once
> > > > > the frame relay goes down, the isdn should kick in with
> > > > > PPP callback. The isdn is a backup interface. To try to
> > > > > jump start the isdn, I went to the remote side and downed
> > > > > the frame relay link. However, my isdn would not kick in.
> > > > > Any suggestions on why it is not working.
> > > > >
> > > > > ****************************** Router 5 *********************
> > > > >
> > > > > Cisco2503_R5#show isdn status
> > > > > Global ISDN Switchtype = basic-ni
> > > > > ISDN BRI0 interface
> > > > > dsl 0, interface ISDN Switchtype = basic-ni
> > > > > Layer 1 Status:
> > > > > DEACTIVATED
> > > > > Layer 2 Status:
> > > > > Layer 2 NOT Activated
> > > > > TEI Not Assigned, ces = 1, state = 3(await
establishment)
> > > > > spid1 configured, spid1 NOT sent, spid1 NOT valid
> > > > > Layer 3 Status:
> > > > > 0 Active Layer 3 Call(s)
> > > > > Active dsl 0 CCBs = 0
> > > > > The Free Channel Mask: 0x00000000
> > > > > --More--
> > > > >
> > > > >
> > > > >
> > > > > username ROUTER4 password 0 cisco
> > > > >
> > > > > interface BRI0
> > > > > description port B s1 40822222221 s2 40822222222
> > > > > ip address 132.1.45.5 255.255.255.248
> > > > > ip router isis
> > > > > encapsulation ppp
> > > > > dialer map clns 49.0035.0006.0006.00 name ROUTER4 broadcast
> > > > 4082222222
> > > > > dialer map ip 132.1.45.4 name ROUTER4 broadcast 4082222222
> > > > > dialer-group 1
> > > > > isdn switch-type basic-ni
> > > > > isdn spid1 40811111111 4081111111
> > > > > ppp callback request
> > > > > ppp authentication chap callout
> > > > > ppp chap hostname ROUTER5
> > > > > ppp multilink
> > > > > isis circuit-type level-2-only
> > > > > end
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Cisco2503_R5#
> > > > > Cisco2503_R5#sh run int s0.1
> > > > > Building configuration...
> > > > >
> > > > > Current configuration : 186 bytes
> > > > > !
> > > > > interface Serial0.1 point-to-point
> > > > > backup interface BRI0
> > > > > ip address 132.1.35.5 255.255.255.0
> > > > > ip router isis
> > > > > frame-relay interface-dlci 513
> > > > > isis circuit-type level-2-only
> > > > > end
> > > > >
> > > > > Cisco2503_R5#
> > > > >
> > > > >
> > > > >
> > > > > **************************** Router 4 configs below
> > > > **********************
> > > > > username ROUTER5 password 0 cisco
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > interface BRI0
> > > > > description port A s1 40811111111 s2 40811111112
> > > > > ip address 132.1.45.4 255.255.255.248
> > > > > ip router isis
> > > > > encapsulation ppp
> > > > > dialer idle-timeout 0
> > > > > dialer map clns 49.0035.0005.0005.00 name ROUTER5 broadcast
> > > > 4081111111
> > > > > dialer map ip 132.1.45.5 name ROUTER5 class CALLBACK
4081111111
> > > > > dialer-group 1
> > > > > isdn switch-type basic-ni
> > > > > isdn spid1 40822222222 4082222222
> > > > > cdapi buffers regular 0
> > > > > cdapi buffers raw 0
> > > > > cdapi buffers large 0
> > > > > ppp callback accept
> > > > > ppp authentication chap callin
> > > > > ppp chap hostname ROUTER4
> > > > > ppp multilink
> > > > >
> > > > >
> > > > >
> > > > > dialer-list 1 protocol ip permit
> > > > >
> > > > >
> > > > > map-class dialer CALLBACK
> > > > > dialer callback-server username
> > > > >
> > > > >
> > > >
> >
This archive was generated by hypermail 2.1.4 : Mon May 03 2004 - 19:48:45 GMT-3