The MPLS-OPS Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] Re: MPLS over ISDN PRI
Hi, Couple of things i'm not clear about in your config. you don't use a dialer interface ? how is the bri associated with the virtual template ? Regards Amos ----- Original Message ----- From: "Stefan Oettl" <soettl@freenet.de> To: "alok" <alok.dube@apara.com>; "Saifulazza" <Saifulazza@vads.com>; <mpls-ops@mplsrc.com> Sent: Wednesday, September 11, 2002 11:44 AM Subject: Re: [MPLS-OPS]: MPLS over ISDN PRI > setup looks like this: > > PE3 <- eth link -> P3 > > eth link is backed up using 'backup interface' on PE3. > P3 is used as NAS and tunnel endpoint in this setup (must support MPLS then). > Authentication / Authorization is done via Radius. IP address of the NAS > virtual-access int. is set via AAA per-user attributes > > relevant parts of the config: > > ############# > PE3: > > interface Tunnel0 > description Backup Tunnel to P3 > ip unnumbered Loopback0 > ip router isis > tag-switching ip > isis metric 50 > tunnel source 10.15.1.2 > tunnel destination 10.15.1.1 > ! > interface FastEthernet0/0 > backup delay 0 30 > backup interface Tunnel0 > ip address 10.3.3.2 255.255.255.252 > ip router isis > speed 10 > half-duplex > tag-switching mtu 1520 > tag-switching ip > ! > interface BRI1/0 > no ip address > dialer pool-member 1 > isdn switch-type basic-net3 > isdn answer1 21 > ! > interface Dialer1 > ip address 10.15.1.2 255.255.255.252 > encapsulation ppp > dialer pool 1 > dialer remote-name _P_3_ > dialer string 11 > dialer-group 1 > ppp authentication pap callin > ppp pap sent-username pe3 password 0 pe3 > ! > router isis > net 49.0100.0500.0003.00 > passive-interface Loopback0 > is-type level-2-only > metric-style wide > log-adjacency-changes > ! > > ######## > > P3: > ######### > > aaa new-model > ! > aaa authentication ppp default local group radius > aaa authorization network default group radius > aaa accounting network default start-stop group radius > ! > virtual-profile virtual-template 1 > ! > interface Tunnel0 > description Backup Tunnel to PE3 > ip unnumbered Loopback0 > ip router isis > tag-switching ip > isis metric 50 > tunnel source 10.15.1.1 > tunnel destination 10.15.1.2 > ! > interface Ethernet0/0 > ip address 10.3.3.1 255.255.255.252 > ip router isis > half-duplex > tag-switching mtu 1520 > tag-switching ip > ! > interface BRI1/0 > no ip address > encapsulation ppp > isdn switch-type basic-net3 > isdn answer1 11 > isdn answer2 11 > ppp authentication pap callin > ! > interface Virtual-Template1 > description Template for PE backup > no ip address > ppp authentication pap callin > ! > router isis > passive-interface Loopback0 > net 49.0100.0500.0013.00 > is-type level-2-only > metric-style wide > ! > radius-server host 10.0.1.254 auth-port 1812 acct-port 1813 key cisco > ! > > #### > > Radius profile: > ####### > > pe3 Password = "pe3" > Service-Type = Framed-User, > Framed-Protocol = PPP, > Framed-IP-Address = "10.15.1.2", > Cisco-AVPair = "lcp:interface-config=ip address > 10.15.1.1 255.255.255.252" > > #### > > hope that helps, > Stefan > > > On Wednesday 11 September 2002 08:11, alok wrote: > > canu send me your config? > > show runn i mean > > with some small explanation of the setup? > > > > -rgds > > Alok > > ----- Original Message ----- > > From: Saifulazza <Saifulazza@vads.com> > > To: alok <alok.dube@apara.com>; Stefan Oettl <soettl@freenet.de>; > > <mpls-ops@mplsrc.com> > > Sent: Wednesday, September 11, 2002 7:30 AM > > Subject: RE: [MPLS-OPS]: MPLS over ISDN PRI > > > > > > > > hi ; > > > > PE-CE , isdn backup was not an issue , as a matter of fact , I am using it > > currently , and it works fine if u used radius server instead of tacacs > > server . > > > > But what if PE-PE backup ? > > > > > > -----Original Message----- > > From: alok [mailto:alok.dube@apara.com] > > Sent: Tuesday, September 10, 2002 8:50 PM > > To: Stefan Oettl; mpls-ops@mplsrc.com > > Subject: Re: [MPLS-OPS]: MPLS over ISDN PRI > > > > > > i think Amos made a good point on my last mail....its a PE -CE > > connection..so no need to support MPLS over that. > > > > what you cud do is this: > > is ur calling end have a fixed ip address or a pool (shud be)... > > > > assuming u have a seperate ISDN RAS....u wud have some connectivity b/w the > > PE and the RAS, u cud use acls on the ethernet connecting to the RAS and > > put it into the right vrf...or mpls VPN... > > > > similarly...if the call terminates on the PE.. and ISDN interfaces cant be > > directly put onto the vrf, u cud use acls to filter traffic based on source > > ip and put it into the vrf for that mpls vpn... > > > > i know that filters to vrf mapping seems to work on some routers..not sure > > abt cisco though.... > > > > -rgds > > A > > ----- Original Message ----- > > From: Stefan Oettl <soettl@freenet.de> > > To: Saifulazza <Saifulazza@vads.com>; <mpls-ops@mplsrc.com> > > Sent: Tuesday, September 10, 2002 5:12 PM > > Subject: Re: [MPLS-OPS]: MPLS over ISDN PRI > > > > > > what kind of PE boxes do you use ? > > in case of Cisco's you could configure a backup PE-PE or PE-NAS (NAS will > > need > > MPLS then) GRE tunnel for label switching. > > As far as I know MPLS forwarding on (DDR) ISDN / Dialer interfaces isn't > > supported directly in IOS up to know. Please someone correct me if I'm > > wrong here ... > > So you could use GRE encapsulation to tunnel the MPLS frames over the > > non-supported circuit. > > > > cheers, > > Stefan > > > > On Tuesday 10 September 2002 11:08, Saifulazza wrote: > > > Hi > > > > > > Has anybody out have implemented the PE-PE connection being backup by > > > ISDN PRI ? . I experienced very unstable connection with the OSPF > > > > adjacency > > > > > flapping most of the time and the VPN can never be developed . > > > > > > Cheers > > > > > > > > > > > > -----Original Message----- > > > From: fraanro [mailto:fraanro@arrakis.es] > > > Sent: Tuesday, September 10, 2002 4:02 PM > > > To: Enrique Torres > > > Cc: mpls-ops@mplsrc.com > > > Subject: Re: [MPLS-OPS]: tag-switching MTU on c7206 and c3640 > > > > > > > > > You should configure the tagswitching MTU in the Fast Ethernet > > > interfaces to be able to hold the MPLS frame with as many shim headers > > > as you need. for example 1508 if you want to labels. > > > > > > mpls mtu 1508 > > > > > > under the interface configuration. > > > > > > Rgds. > > > Javier. > > > > > > ----- Mensaje Original ----- > > > Remitente: Enrique Torres <entorresa@yahoo.com> > > > Fecha: Lunes, Septiembre 9, 2002 8:28 pm > > > Asunto: [MPLS-OPS]: tag-switching MTU on c7206 and c3640 > > > > > > > Hi all > > > > > > > > I started tag-switching between 2 nodes of my network > > > > but there is a problem with the MTU and the packet > > > > size after tag imposition. > > > > > > > > My configuration in each node is it > > > > > > > > I have a Cisco7206 (IOS 12.1(1)E), it is connected > > > > with 6 Cisco 3640 (remote cells) through E1 circuits. > > > > Between the C3640 and C7206 I run tag switching > > > > because I have configured VPN's. In all these routers > > > > is configured "Path MTU Discovery" and our MTU between > > > > the c3640 and c7206 is 1530. > > > > > > > > In this configuration I dont have any problem to send > > > > information between clients connected in our c3640's. > > > > > > > > But when I connect this node with a second node, I > > > > must connect the c7206 through a fast ethernet port > > > > and run tag-switching over these ports. In this > > > > situation I started to have problems with http, ftp or > > > > any kind of traffic with large size of packet (greater > > > > than 1500bytes). > > > > > > > > I believe that I have a problem with the MTU after > > > > second tag imposition (the impositon between c7206's) > > > > > > > > Please, could you help me to solve this. > > > > > > > > Thanks, > > > > Enrique. > > > > > > > > > > > > > > > > ===== > > > > Saludos, > > > > Enrique > > > > > > > > __________________________________________________ > > > > Do You Yahoo!? > > > > Yahoo! Finance - Get real-time stock quotes > > > > http://finance.yahoo.com > > > > > > > > ------- > > > > The MPLS-OPS Mailing List > > > > Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml > > > > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml > > > > > > ------- > > > The MPLS-OPS Mailing List > > > Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml > > > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml > > > > > > ------- > > > The MPLS-OPS Mailing List > > > Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml > > > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml > > > > ------- > > The MPLS-OPS Mailing List > > Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml > > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml > > > > > > > > ------- > > The MPLS-OPS Mailing List > > Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml > > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml > > > > ------- > > The MPLS-OPS Mailing List > > Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml > > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml > > > > > > > > ------- > > The MPLS-OPS Mailing List > > Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml > > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml > > ------- > The MPLS-OPS Mailing List > Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml > Archive: http://www.mplsrc.com/mpls-ops_archive.shtml ------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
|
|