From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Thu Oct 21 2004 - 11:49:06 GMT-3
This is not necessarily true. While it is typically common that
NI switches have two SPIDs, it's completely determined by how the ISDN
network is configured. NI switches can have setups of 2 SPIDs, 1 SPID,
or no SPIDs.
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
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> robbie
> Sent: Wednesday, October 20, 2004 11:55 PM
> To: Cisco Net
> Cc: Group Study
> Subject: Re: PPP multilink - not getting the second BRI [IE lab 7]
>
> For Custom (5ESS/DMS100) or NI switches, both SPIDs are required, as
> each BRI channel requires a SPID so it can register with the switch,
get
> assigned a TEI, and place outbound/receive inbound calls with its own
> specific TEI on the ISDN switch. The TEI is a layer 2 address, but to
> have one assigned, you must have a SPID for each channel if using
NI-1.
> I'm not sure if this is a requirement on other switchtypes (NET3,
etc).
>
> robbie
>
>
> Cisco Net wrote:
> > Thanks guys...
> > Actually adding 2 spids helped in getting the second channel as
well.
> > Good to know...
> > I think as earleir mentioned it could be switch specific.
> >
> > Thank you all.
> > Cert.
> >
> >
> > On Wed, 20 Oct 2004 18:37:04 -0700, Larry Metzger
> > <larrymetzger@sbcglobal.net> wrote:
> >
> >>This sounds very familiar. I believe if you'll read the isdn spid1
> >>command reference
>
>>http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgc
r/
> >>fdial_r/drfisl2.htm#wp1077028
> >>You'll find that you can only bring up one B channel if you only
have 1
> >>spid and no LDN (for some isdn switches). If you'll add the LDN to
the
> >>isdn spid1 command, both channels will be able to come up.
> >>
> >>Larry
> >>
> >>
> >>
> >>-----Original Message-----
> >>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> >>Cisco Net
> >>Sent: Wednesday, October 20, 2004 6:05 PM
> >>To: Group Study
> >>Subject: PPP multilink - not getting the second BRI [IE lab 7]
> >>
> >>Hi
> >>Part of the question is to get both BRI channels together.
> >>And i have the following configurations,
> >>
> >>Rack4R5:
> >>interface BRI2/0
> >>ip address 163.4.45.5 255.255.255.248
> >>ip router isis
> >>encapsulation ppp
> >>dialer map clns 33.0004.0004.0004.00 name Rack4R4 broadcast 2436155
> >>dialer map ip 163.4.45.4 name Rack4R4 broadcast 2436155
> >>dialer-group 1
> >>isdn switch-type basic-ni
> >>isdn spid1 4084370443
> >>ppp authentication chap
> >>ppp multilink --> Multilink is enabled
> >>ppp multilink links minimum 2 -->so that both channels should come
up
> >>isis circuit-type level-2-only
> >>
> >>dialer-list 1 protocol ip permit
> >>dialer-list 1 protocol clns_is permit
> >>
> >>Rack4R4:
> >>
> >>interface BRI3/0
> >>ip address 163.4.45.4 255.255.255.248
> >>ip router isis
> >>encapsulation ppp
> >>dialer idle-timeout 0
> >>dialer map clns 33.0005.0005.0004.00 name Rack4R5 broadcast 4370443
> >>dialer map ip 163.4.45.5 name Rack4R5 broadcast 4370443
> >>isdn switch-type basic-ni
> >>isdn spid1 4082436155
> >>ppp authentication chap
> >>ppp multilink --------> mullink enabled
> >>isis circuit-type level-2-only
> >>
> >>Only R5 have the " ppp multilink links minimum 2" and that is
beacuse
> >>only R5 is allowed to dial and establish. There is no DDR on R4.
> >>
> >>R5:
> >>Sh ip in brief shows second channel is still down.
> >>BRI2/0 163.4.45.5 YES NVRAM up
> >> up
> >>BRI2/0:1 unassigned YES unset up
> >> up
> >>BRI2/0:2 unassigned YES unset down
> >> down
> >>
> >>Any inputs are appreciated
> >>Regards
> >>Cert
> >>
>
>>______________________________________________________________________
_
> >>Subscription information may be found at:
> >>http://www.groupstudy.com/list/CCIELab.html
> >
> >
> >
This archive was generated by hypermail 2.1.4 : Sat Nov 06 2004 - 17:11:51 GMT-3