From: Stefan Grey (examplebrain@hotmail.com)
Date: Sun Aug 07 2005 - 03:57:32 GMT-3
Yes, I also saw this in the configuration, I removed this but the problem is
still the same:
1. The bb1 router doesn't see the default route to the r2 router.
2. Another very funny thing which I don't uderstand is: When I redistribute
OSPF to Isis level 1 on router r2. All OSPF external route type 2 are in the
routing table of R3. But some of them are in the routing table of BB1 and
some are not. (It would be more clear if there will not be any route of OSPF
in BB2 routing table for me).
So BB2 contains int its isis routing table: L1 routes (no default route to
L1/L2 router) and only some but not all router redistributed from OSPF).
Thanks for the reply.
>From: "Arun Arumuganainar" <aarumuga@hotmail.com>
>Reply-To: "Arun Arumuganainar" <aarumuga@hotmail.com>
>To: "Stefan Grey" <examplebrain@hotmail.com>, <zouta.oxpf@gmail.com>,
><ccielab@groupstudy.com>
>Subject: Re: Isis and ATM
>Date: Sun, 7 Aug 2005 12:04:07 +0530
>
>Hi ,
>
>Is there any reason for configuring "set-overload-bit " .
>
>Default behavior it will install only the connected route and nothing else
>!!!
>
>Try removing this and let me know if you still have the problem .
>
>Thanks and Regards
>Arun
>
>----- Original Message -----
>From: "Stefan Grey" <examplebrain@hotmail.com>
>To: <zouta.oxpf@gmail.com>; <ccielab@groupstudy.com>
>Sent: Sunday, August 07, 2005 11:49 AM
>Subject: Re: Isis and ATM
>
>
> > I also thought that maybe BB1 router is filtering this isis level1
>default
> > route. But look at the configuration below. I have no idia what in the
> > configuration could filter this default route to r2. Maybe you could
>tell
> > me. Thanks (I mentioned this problem when doing IEWBv2 lab2)
> >
> > hostname BB1
> > !
> > logging queue-limit 100
> > !
> > memory-size iomem 10
> > ip subnet-zero
> > !
> > !
> > no ip domain lookup
> > !
> > !
> > !
> > key chain EIGRP
> > key 1
> > key-string CISCO
> > !
> > !
> > !
> > !
> > !
> > !
> > !
> > !
> > no voice hpi capture buffer
> > no voice hpi capture destination
> > !
> > !
> > mta receive maximum-recipients 0
> > !
> > !
> > !
> > !
> > interface Loopback112
> > ip address 112.0.0.1 255.0.0.0
> > !
> > interface Loopback113
> > ip address 113.0.0.1 255.0.0.0
> > !
> > interface Loopback114
> > ip address 114.0.0.1 255.0.0.0
> > !
> > interface Loopback115
> > ip address 115.0.0.1 255.0.0.0
> > !
> > interface Loopback116
> > ip address 116.0.0.1 255.0.0.0
> > !
> > interface Loopback117
> > ip address 117.0.0.1 255.0.0.0
> > !
> > interface Loopback118
> > ip address 118.0.0.1 255.0.0.0
> > !
> > interface Loopback119
> > ip address 119.0.0.1 255.0.0.0
> > !
> > interface Loopback51001
> > ip address 51.0.0.1 255.255.0.0
> > !
> > interface Loopback51101
> > ip address 51.1.0.1 255.255.0.0
> > !
> > interface Loopback51201
> > ip address 51.2.0.1 255.255.0.0
> > !
> > interface Loopback51301
> > ip address 51.3.0.1 255.255.0.0
> > !
> > interface Loopback51401
> > ip address 51.4.0.1 255.255.0.0
> > !
> > interface Loopback51501
> > ip address 51.5.0.1 255.255.0.0
> > !
> > interface Loopback51601
> > ip address 51.6.0.1 255.255.0.0
> > !
> > interface Loopback51701
> > ip address 51.7.0.1 255.255.0.0
> > !
> > interface Loopback200000
> > ip address 200.0.0.1 255.255.255.0
> > !
> > interface Loopback200010
> > ip address 200.0.1.1 255.255.255.0
> > !
> > interface Loopback200020
> > ip address 200.0.2.1 255.255.255.0
> > !
> > interface Loopback200030
> > ip address 200.0.3.1 255.255.255.0
> > !
> > interface Loopback2121801
> > ip address 212.18.0.1 255.255.255.0
> > !
> > interface Loopback2121811
> > ip address 212.18.1.1 255.255.255.0
> > !
> > interface Loopback2121821
> > ip address 212.18.2.1 255.255.255.0
> > !
> > interface Loopback2121831
> > ip address 212.18.3.1 255.255.255.0
> > !
> > interface Loopback12109150
> > ip address 12.109.15.0 255.255.255.255
> > !
> > interface Loopback12109151
> > ip address 12.109.15.1 255.255.255.255
> > !
> > interface Loopback12109152
> > ip address 12.109.15.2 255.255.255.255
> > !
> > interface Loopback12109153
> > ip address 12.109.15.3 255.255.255.255
> > !
> > interface Loopback12109154
> > ip address 12.109.15.4 255.255.255.255
> > !
> > interface Loopback12109155
> > ip address 12.109.15.5 255.255.255.255
> > !
> > interface Loopback12109156
> > ip address 12.109.15.6 255.255.255.255
> > !
> > interface Loopback12109157
> > ip address 12.109.15.7 255.255.255.255
> > !
> > interface Ethernet0/0
> > description HDLC link to BB3 for BGP Peering
> > ip address 172.16.4.1 255.255.255.0
> > half-duplex
> > !
> > interface Serial0/0
> > no ip address
> > shutdown
> > no fair-queue
> > !
> > interface Ethernet0/1
> > no ip address
> > shutdown
> > half-duplex
> > !
> > interface Serial0/1
> > no ip address
> > shutdown
> > !
> > interface ATM1/0
> > no ip address
> > no atm ilmi-keepalive
> > pvc 0/5 qsaal
> > !
> > pvc 0/16 ilmi
> > !
> > !
> > interface ATM1/0.1100 point-to-point
> > description PVC 1/100 to Rack1R6 for PVC Discovery
> > ip address 54.1.2.254 255.255.255.0
> > ip router isis 1
> > pvc 1/100
> > !
> > !
> > !
> > router eigrp 10
> > network 54.0.0.0
> > network 200.0.0.0 0.0.3.255
> > distribute-list EIGRP out
> > no auto-summary
> > !
> > router isis 1
> > net 49.0001.00e0.1e57.e592.00
> > is-type level-1
> > set-overload-bit
> > passive-interface Loopback51001
> > passive-interface Loopback51101
> > passive-interface Loopback51201
> > passive-interface Loopback51301
> > passive-interface Loopback51401
> > passive-interface Loopback51501
> > passive-interface Loopback51601
> > passive-interface Loopback51701
> > !
> > ip http server
> > ip classless
> > ip route 0.0.0.0 0.0.0.0 Null0
> > ip route 204.12.1.0 255.255.255.0 172.16.4.3
> >
> >
> >
> > >From: Zouta oxpf <zouta.oxpf@gmail.com>
> > >Reply-To: Zouta oxpf <zouta.oxpf@gmail.com>
> > >To: Stefan Grey <examplebrain@hotmail.com>
> > >CC: Groupstudy <ccielab@groupstudy.com>
> > >Subject: Re: Isis and ATM
> > >Date: Sat, 6 Aug 2005 22:35:50 -0400
> > >
> > >I overlooked that. Maybe the default route is being deliberately
> > >filtered at the backbone, you know you really do not have that much
> > >control over the backbone. You might have to employ some other means
> > >to have full reachability to those BB routes. If you have access to
> > >the backbone check to make sure that ISIS default is not being
> > >filtered.
> > >
> > >Another area to explore is isis metric style, check isis issues with
> > >metric styles, wide, narrow and transition.
> > >
> > >ZO.
> > >
> > >On 8/6/05, Stefan Grey <examplebrain@hotmail.com> wrote:
> > > >
> > > > Yes I already mentioned this, they are in the same area.
> > > >
> > > > Router R1 is in Area 49.1.....
> > > > Router r2,r3,bb1 are in the same area 49.2.... but in different one
>from
> > > > router R1.
> > > >
> > > >
> > > > >From: Zouta oxpf <zouta.oxpf@gmail.com>
> > > > >Reply-To: Zouta oxpf <zouta.oxpf@gmail.com>
> > > > >To: Stefan Grey <examplebrain@hotmail.com>
> > > > >CC: ccielab@groupstudy.com
> > > > >Subject: Re: Isis and ATM
> > > > >Date: Sat, 6 Aug 2005 15:09:24 -0400
> > > > >
> > > > >Hi Stefan,
> > > > >
> > > > >Is BB1 and R3 in the same ISIS area?
> > > > >
> > > > >ZO
> > > > >
> > > > >On 8/6/05, Stefan Grey <examplebrain@hotmail.com> wrote:
> > > > > > Please could you explain me the following:
> > > > > >
> > > > > > we have such topology
> > > > > >
> > > > > > R1 - R2 -R3 -BB1
> > > > > >
> > > > > > R1-R2-R3 is connected with ethernet
> > > > > > R3-BB1 is connected with ATM
> > > > > >
> > > > > > R1 - int area 1
> > > > > >
> > > > > > r2,r3,BB1 in isis area 2
> > > > > >
> > > > > > R1 - R2 - level-2 only connection
> > > > > >
> > > > > > R2-R3 level 1 conn
> > > > > > R3-BB1 level 1 connection
> > > > > >
> > > > > > 1.R3 see the default isis connection to R2. So it can access all
> > > > >external
> > > > > > routers in outside router R1. (As normally in the stub network).
> > > > > >
> > > > > > BB1 doesn't have this default route. Why?? It have only L1
>routes
>in
> > > > >it's
> > > > > > area and nothing about how to reach the outside routers. I
>thought
> > >that
> > > > >L1
> > > > > > routers should pass the information between each other.
> > > > > >
> > > > > > Any idia??
> > > > > >
> > > > > > When redistributin for example Ospf into isis level1 on R2
>router
>I
> > >also
> > > > >had
> > > > > > the problem that R3 gets some routes which BB1 doesn't.
> > > > > >
> > > > > > I totally don't understand why.
> > > > > >
> > > > > > Please help....
> > > > > >
> > > > > >
>_________________________________________________________________
> > > > > > Chat via voice, text or video - get MSN Messenger FREE!
> > > > > > http://messenger.msn.co.uk
> > > > > >
> > > > > >
> > >_______________________________________________________________________
> > > > > > Subscription information may be found at:
> > > > > > http://www.groupstudy.com/list/CCIELab.html
> > > > >
> > > >
> >_______________________________________________________________________
> > > > >Subscription information may be found at:
> > > > >http://www.groupstudy.com/list/CCIELab.html
> > > >
> > > > _________________________________________________________________
> > > > Accurate weather reports for this week & the weekend!
> > > > http://www.msn.ie/weather
> > >
> > >_______________________________________________________________________
> > >Subscription information may be found at:
> > >http://www.groupstudy.com/list/CCIELab.html
> >
> > _________________________________________________________________
> > Rain or shine, sleet or snow? Visit MSN Weather today!
> > http://www.msn.ie/weather
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
>_______________________________________________________________________
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:18 GMT-3