From: Brian Lodwick (xpranax@xxxxxxxxxxx)
Date: Fri Oct 05 2001 - 16:56:22 GMT-3
I havent tried that. I kindof was hoping to get this scenario to work. In
the ECP class I just went to, we setup a very similar schenario, but instead
of using ATM we were using Frame-Relay, and everything worked great. I will
try your recommendation though here in a second if I can't get this scenario
to work once I get tired of researching. I am going to check Cisco technotes
now and see if they have anything similar.
Thanks!
>>>Brian
>From: "rsevier" <rsevier@zealousolutions.com>
>To: "Brian Lodwick" <xpranax@hotmail.com>
>Subject: RE: IS-IS problems on an ATM multipoint config
>Date: Fri, 5 Oct 2001 12:56:36 -0700
>
>Have you tried to put the pvc's on separate subinterfaces. I remember when
>I used to do DSL and a customer that wanted to see their other locations,
>we
>would have to separate the pvc's.
>
>Raymond
>
>-----Original Message-----
>From: Brian Lodwick [mailto:xpranax@hotmail.com]
>Sent: Friday, October 05, 2001 12:35 PM
>To: rsevier@zealousolutions.com
>Cc: ccielab@groupstudy.com
>Subject: RE: IS-IS problems on an ATM multipoint config
>
>
>The reason I do not believe it is an issue with having a Level-1 interface
>is primarily because r2 is sending the routing update to r8 about it's
>ethernet segment (the level-1 only interface). The link between r2 and r8
>is
>the ATM pvc. r8 receives this route and puts it into the routing table:
>r8#ip
>Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
> D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
> N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
> E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
> i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter
>area
> * - candidate default, U - per-user static route, o - ODR
> P - periodic downloaded static route
>
>Gateway of last resort is not set
>
> 172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks
>i L2 172.16.20.0/28 [115/20] via 172.16.70.3, ATM2/0.1
>C 172.16.70.0/24 is directly connected, ATM2/0.1
>
>But it doesn't forward the update to r7. I know r8 is the DR because in the
>sh clns is-neighbor output the spokes are acnowledged as priority 0 and the
>hub is acknowledged as priority 127:
>
>r7#sh clns is-neighbors
>
>System Id Interface State Type Priority Circuit Id Format
>r8 AT0/0 Up L2 127 r8.01 Phase V
>
>r8#sh clns is-neighbors
>
>System Id Interface State Type Priority Circuit Id Format
>r2 AT2/0.1 Up L2 0 r8.01 Phase V
>r7 AT2/0.1 Up L2 0 r8.01 Phase V
>
>Also when debugging isis adj-packets then clearing isis * on r8 during the
>adjacency it shows the DR is us:
>03:39:57: ISIS-Adj: Run level-2 DR election for ATM2/0.1
>03:39:57: ISIS-Adj: No change (it's us)
>
>But the main reason I don't think this is the issue is because I changed
>the
>ethernet on r2 to level-2 wrote and then rebooted and the same thing
>happened.
>
> >>>Brian
>
>
>
> >From: "rsevier" <rsevier@zealousolutions.com>
> >To: "Brian Lodwick" <xpranax@hotmail.com>
> >Subject: RE: IS-IS problems on an ATM multipoint config
> >Date: Fri, 5 Oct 2001 12:21:09 -0700
> >
> >B- Are sure it has nothing to do with that you have level-2-only on the
> >ATM
> >interfaces and level-1 on the 20.1 interface? Post some routing tables.
> >
> >Raymond
> >
> >-----Original Message-----
> >From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> >Brian Lodwick
> >Sent: Friday, October 05, 2001 11:40 AM
> >To: jcarnevale@gnilink.net
> >Cc: ccielab@groupstudy.com
> >Subject: RE: IS-IS problems on an ATM multipoint config
> >
> >
> >None of these interfaces are configured with point-to-point
>sub-interfaces.
> >There is only one multipoint sub-interface and the others are physical
> >interfaces. I know there is an issue with using point-to-point
> >sub-interfaces with either physical or multipoint sub-interfaces, but I
> >believe physical and multipoint sub-interfaces are compatible. Also if
>this
> >was the issue it would be an adjacency issue, and all adjacencies are
>full.
> >Also if you notice I have manually configured the Hello/Dead intervals
>and
> >priorities to assure the Hub is elected the DR.
> >
> >r8#sh clns is-neighbors
> >
> >System Id Interface State Type Priority Circuit Id
>Format
> >r2 AT2/0.1 Up L2 0 r8.01 Phase
>V
> >r7 AT2/0.1 Up L2 0 r8.01 Phase
>V
> >
> >
> >r2#sh clns is-neighbors
> >
> >System Id Interface State Type Priority Circuit Id
>Format
> >r8 AT1/0 Up L2 127 r8.01 Phase
>V
> >
> >r7#sh clns is-neighbors
> >
> >System Id Interface State Type Priority Circuit Id
>Format
> >r8 AT0/0 Up L2 127 r8.01 Phase
>V
> >
> >
> > >From: "Carnevale, Jason" <jcarnevale@gnilink.net>
> > >Reply-To: "Carnevale, Jason" <jcarnevale@gnilink.net>
> > >To: "'Brian Lodwick '" <xpranax@hotmail.com>
> > >CC: "'ccielab@groupstudy.com'" <ccielab@groupstudy.com>
> > >Subject: RE: IS-IS problems on an ATM multipoint config
> > >Date: Fri, 5 Oct 2001 14:19:26 -0400
> > >
> > >The problem is that isis has the same type mismatch problems as ospf.
>The
> > >difference is that ospf has a command to manually set the network type,
> > >isis
> > >does not. Since ATM is an NBMA network and one interface is point to
> >point
> > >and the others are main interfaces this is not going to work. The
> >solution
> > >is to create point-to-point tunnels between each router running isis.
> > >
> > >-jason
> > >
> > >-----Original Message-----
> > >From: Brian Lodwick
> > >To: ccielab@groupstudy.com
> > >Sent: 10/5/2001 1:51 PM
> > >Subject: IS-IS problems on an ATM multipoint config
> > >
> > >I am getting frustrated with this IGP. I have decided to make up this
> > >crazy
> > >lab to key in on my difficult areas and one part of it is causing me
> > >difficulties. It is a hub spoke topology with ATM PVC's running IS-IS
> > >over
> > >them. The routers are r7, r8, and r2. r8 is the hub and has a
>multipoint
> > >
> > >sub-interface to the spokes r2, and r7. r2's ethernet 0/1/0
> > >(172.16.20.0/24)is participating in IS-IS. What I end up getting is on
> > >r8 I
> > >receive the route for 172.16.20.1/24, but not on r7. When I debug isis
> > >update-packets and isis spf-events on r7 I don't get anything at all,
>so
> > >I
> > >know it is not getting the update and rejecting it, it just isn't
> > >receiving
> > >it at all for some reason. Can anyone figure out what I am doing wrong?
> > >I
> > >have added the configs below for analysis.
> > >Thanks in advance!
> > > >>>Brian
> > >
> > >Hub:
> > >r8#sh run
> > >Building configuration...
> > >
> > >Current configuration : 1305 bytes
> > >!
> > >version 12.1
> > >no service single-slot-reload-enable
> > >service timestamps debug uptime
> > >service timestamps log uptime
> > >no service password-encryption
> > >!
> > >hostname r8
> > >!
> > >logging rate-limit console 10 except errors
> > >!
> > >!
> > >!
> > >ip subnet-zero
> > >!
> > >!
> > >no ip finger
> > >no ip domain-lookup
> > >!
> > >no mgcp timer receive-rtcp
> > >!
> > >!
> > >call rsvp-sync
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >interface ATM2/0
> > >no ip address
> > >no atm scrambling cell-payload
> > >atm uni-version 3.1
> > >no atm ilmi-keepalive
> > >!
> > >interface ATM2/0.1 multipoint
> > >ip address 172.16.70.2 255.255.255.0
> > >ip router isis
> > >pvc 7/15
> > > protocol ip 172.16.70.1 broadcast
> > > protocol clns 49.0000.0007.0007.0007.00 broadcast
> > > broadcast
> > > encapsulation aal5snap
> > >!
> > >pvc 8/15
> > > protocol ip 172.16.70.3 broadcast
> > > protocol clns 49.0000.0002.0002.0002.00 broadcast
> > > broadcast
> > > encapsulation aal5snap
> > >!
> > >isis circuit-type level-2-only
> > >isis priority 127 level-2
> > >isis hello-multiplier 120
> > >isis hello-interval 40
> > >!
> > >!
> > >router isis
> > >net 49.0000.0008.0008.0008.00
> > >!
> > >ip kerberos source-interface any
> > >ip classless
> > >no ip http server
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >snmp-server engineID local 80000009FF0000A100E4E5B4
> > >snmp-server manager
> > >!
> > >dial-peer cor custom
> > >!
> > >!
> > >!
> > >!
> > >alias exec ip sh ip route
> > >alias exec int sh ip int brief
> > >alias exec ipx sh ipx route
> > >!
> > >line con 0
> > >transport input none
> > >line aux 0
> > >line vty 0 4
> > >login
> > >!
> > >end
> > >
> > >Spoke:
> > >r7#sh run
> > >Building configuration...
> > >
> > >Current configuration : 2003 bytes
> > >!
> > >version 12.1
> > >no service single-slot-reload-enable
> > >service timestamps debug uptime
> > >service timestamps log uptime
> > >no service password-encryption
> > >!
> > >hostname r7
> > >!
> > >logging rate-limit console 10 except errors
> > >!
> > >!
> > >!
> > >ip subnet-zero
> > >!
> > >!
> > >no ip finger
> > >no ip domain-lookup
> > >!
> > >no mgcp timer receive-rtcp
> > >!
> > >!
> > >call rsvp-sync
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >controller T1 1/0
> > >framing esf
> > >linecode b8zs
> > >channel-group 0 timeslots 1-24
> > >!
> > >controller T1 1/1
> > >!
> > >!
> > >interface ATM0/0
> > >ip address 172.16.70.1 255.255.255.0
> > >ip router isis
> > >no atm scrambling cell-payload
> > >no atm ilmi-keepalive
> > >pvc 5/15
> > > protocol ip 172.16.70.2 broadcast
> > > protocol ip 172.16.70.3 broadcast
> > > protocol clns 49.0000.0002.0002.0002.00 broadcast
> > > protocol clns 49.0000.0008.0008.0008.00 broadcast
> > > broadcast
> > > encapsulation aal5snap
> > >!
> > >isis circuit-type level-2-only
> > >isis priority 0 level-2
> > >isis hello-multiplier 120
> > >isis hello-interval 40
> > >!
> > >interface Serial1/0:0
> > >no ip address
> > >encapsulation frame-relay
> > >frame-relay traffic-shaping
> > >!
> > >interface Serial1/0:0.1 point-to-point
> > >ip address 172.16.30.1 255.255.255.0
> > >ip ospf network point-to-multipoint
> > >frame-relay interface-dlci 701
> > > class vofr
> > > vofr cisco
> > >!
> > >!
> > >router ospf 100
> > >log-adjacency-changes
> > >network 172.16.30.1 0.0.0.0 area 0
> > >!
> > >router isis
> > >net 49.0000.0007.0007.0007.00
> > >!
> > >ip kerberos source-interface any
> > >ip classless
> > >no ip http server
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >map-class frame-relay vofr
> > >no frame-relay adaptive-shaping
> > >frame-relay fair-queue
> > >frame-relay voice bandwidth 32000
> > >frame-relay fragment 80
> > >!
> > >snmp-server engineID local 80000009FF0000A1012D34BF
> > >snmp-server manager
> > >!
> > >voice-port 3/0/0
> > >!
> > >voice-port 3/0/1
> > >!
> > >voice-port 3/1/0
> > >!
> > >voice-port 3/1/1
> > >!
> > >dial-peer cor custom
> > >!
> > >!
> > >!
> > >dial-peer voice 777 pots
> > >destination-pattern 777
> > >port 3/1/0
> > >!
> > >dial-peer voice 111 vofr
> > >destination-pattern 111
> > >session target Serial1/0:0 701
> > >!
> > >!
> > >alias exec ip sh ip route
> > >alias exec int sh ip int brief
> > >alias exec ipx sh ipx route
> > >!
> > >line con 0
> > >transport input none
> > >line aux 0
> > >line vty 0 4
> > >login
> > >!
> > >end
> > >
> > >
> > >Spoke:
> > >r2#sh run
> > >Building configuration...
> > >
> > >Current configuration : 2663 bytes
> > >!
> > >version 12.2
> > >no service single-slot-reload-enable
> > >service timestamps debug uptime
> > >service timestamps log uptime
> > >no service password-encryption
> > >!
> > >hostname r2
> > >!
> > >logging rate-limit console 10 except errors
> > >!
> > >ip subnet-zero
> > >no ip finger
> > >no ip domain-lookup
> > >!
> > >ip cef
> > >no ip dhcp-client network-discovery
> > >frame-relay switching
> > >call rsvp-sync
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >!
> > >controller T1 0/0/0
> > >framing esf
> > >clock source internal
> > >linecode b8zs
> > >channel-group 0 timeslots 1-24 speed 56
> > >!
> > >controller T1 0/0/1
> > >framing esf
> > >linecode b8zs
> > >!
> > >controller T1 0/0/2
> > >framing esf
> > >linecode b8zs
> > >!
> > >controller T1 0/0/3
> > >framing esf
> > >linecode b8zs
> > >!
> > >!
> > >interface Serial0/0/0:0
> > >no ip address
> > >encapsulation frame-relay
> > >no ip route-cache distributed
> > >frame-relay intf-type dce
> > >frame-relay route 701 interface Serial3/1 107
> > >!
> > >interface Ethernet0/1/0
> > >ip address 172.16.20.1 255.255.255.240
> > >ip router isis
> > >no ip route-cache distributed
> > >no keepalive
> > >isis circuit-type level-1
> > >isis hello-multiplier 1000
> > >isis hello-interval 300
> > >!
> > >interface Ethernet0/1/1
> > >no ip address
> > >no ip route-cache distributed
> > >shutdown
> > >!
> > >interface Ethernet0/1/2
> > >no ip address
> > >no ip route-cache distributed
> > >shutdown
> > >!
> > >interface Ethernet0/1/3
> > >no ip address
> > >no ip route-cache distributed
> > >shutdown
> > >!
> > >interface ATM1/0
> > >ip address 172.16.70.3 255.255.255.0
> > >ip router isis
> > >no atm ilmi-keepalive
> > >pvc 6/15
> > > protocol ip 172.16.70.1 broadcast
> > > protocol ip 172.16.70.2 broadcast
> > > protocol clns 49.0000.0007.0007.0007.00 broadcast
> > > protocol clns 49.0000.0008.0008.0008.00 broadcast
> > > broadcast
> > > encapsulation aal5snap
> > >!
> > >isis circuit-type level-2-only
> > >isis priority 0 level-2
> > >isis hello-multiplier 120
> > >isis hello-interval 40
> > >!
> > >interface ATM2/0
> > >no ip address
> > >shutdown
> > >no atm ilmi-keepalive
> > >!
> > >interface Serial3/0
> > >no ip address
> > >shutdown
> > >!
> > >interface Serial3/1
> > >no ip address
> > >encapsulation frame-relay
> > >frame-relay intf-type dce
> > >frame-relay route 103 interface Serial3/2 301
> > >frame-relay route 107 interface Serial0/0/0:0 701
> > >!
> > >interface Serial3/2
> > >no ip address
> > >encapsulation frame-relay
> > >clockrate 2000000
> > >frame-relay intf-type dce
> > >frame-relay route 301 interface Serial3/1 103
> > >!
> > >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 isis
> > >net 49.0000.0002.0002.0002.00
> > >!
> > >ip kerberos source-interface any
> > >ip classless
> > >no ip http server
> > >!
> > >!
> > >!
> > >alias exec ip sh ip route
> > >alias exec ipx sh ipx route
> > >alias exec int sh ip int brief
> > >!
> > >line con 0
> > >exec-timeout 0 0
> > >transport input none
> > >line aux 0
> > >line vty 0 4
> > >login
> > >!
> > >end
> > >
> > >
> > >
> > >
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 22:33:14 GMT-3