[Xorp-users] Fwd: Re: virtual link
Tomek
segv at o2.pl
Mon May 4 22:38:18 PDT 2009
Dnia 2 maja 2009 18:52 Tomek <segv at o2.pl> napisał(a):
> Hi,
> Thank you guys for yours replies.
> I use xorp ver. 1.6 at R4,R3 and the rest uses 1.5.
> So R3 doesn't learn about R4 what is really strange, dunno why..
> Below I listed my config files from R3 and R4:
>
> ********* R3 ***************
> interfaces {
> restore-original-config-on-shutdown: false
> interface eth1 {
> vif eth1 {
> address 192.168.2.30 {
> prefix-length: 24
> }
> }
> }
> interface eth2 {
> vif eth2 {
> address 192.168.3.30 {
> prefix-length: 24
> }
> }
> }
> interface eth3 {
> vif eth3 {
> address 192.168.6.30 {
> prefix-length: 24
> }
> }
> }
> }
>
> fea {
> unicast-forwarding4 {
> disable: false
> forwarding-entries {
> retain-on-startup: false
> retain-on-shutdown: false
> }
> }
> }
> protocols {
> ospf4 {
> router-id: 192.168.0.30
>
> area 0.0.0.1 {
> interface eth3 {
> vif eth3 {
> address 192.168.6.30 {
> interface-cost: 2
> }
> }
> }
> }
>
> area 0.0.0.0 {
> /* virtual-link 192.168.0.40 {
> transit-area: 0.0.0.1
> }
> */
> interface eth1 {
> vif eth1 {
> address 192.168.2.30 {
> interface-cost: 3
> }
> }
> }
> interface eth2 {
> vif eth2 {
> address 192.168.3.30 {
> interface-cost: 1
> }
> }
> }
> }
> }
> }
>
> ********* END ***************
>
> ********* R4 ***************
>
> interfaces {
> restore-original-config-on-shutdown: false
> /* interface eth1 {
> description: "Ethernet Interface #1"
> disable: false
> default-system-config
> }
> */
> interface eth2 {
> description: "Ethernet Interface #2"
> disable: false
> default-system-config
> }
> interface eth3 {
> description: "Ethernet Interface #3"
> disable: false
> default-system-config
> }
> }
>
> fea {
> unicast-forwarding4 {
> disable: false
> forwarding-entries {
> retain-on-startup: false
> retain-on-shutdown: false
> }
> }
>
> }
> protocols {
> ospf4 {
> router-id: 192.168.0.40
> area 0.0.0.1 {
>
> /* interface eth1 {
> vif eth1 {
> address 192.168.4.40 {
> interface-cost: 4
> }
> }
> }
> */
> interface eth2 {
> vif eth2 {
> address 192.168.5.40 {
> interface-cost: 6
> }
> }
> }
> }
> area 0.0.0.3 {
> interface eth3 {
> vif eth3 {
> address 192.168.7.40 {
> interface-cost: 1
> }
> }
> }
> }
> }
> }
>
>
> ********* END ***************
>
> ********* R5 ***************
> interfaces {
> restore-original-config-on-shutdown: false
> interface eth1 {
> description: "Ethernet Interface #1"
> disable: false
> default-system-config
> }
> interface eth2 {
> description: "Ethernet Interface #2"
> disable: false
> default-system-config
> }
>
> }
>
> fea {
> unicast-forwarding4 {
> disable: false
> forwarding-entries {
> retain-on-startup: false
> retain-on-shutdown: false
> }
> }
>
> }
> protocols {
> ospf4 {
> router-id: 192.168.0.50
> area 0.0.0.1 {
> interface eth1 {
> vif eth1 {
> address 192.168.6.50 {
> interface-cost: 2
> }
> }
> }
> interface eth2 {
> vif eth2 {
> address 192.168.5.50 {
> interface-cost: 6
> }
> }
> }
> }
>
> }
> }
>
> ********* END ***************
>
> BR
> Tom
>
> Dnia 1 maja 2009 18:17 Bruce Simpson napisał(a):
>
> > Tomek wrote:
> > > Hi,
> > >
> > > I've got a problem with xorp configuration.
> > > Actually in my case situation looks like this:
> > >
> > > R3 R5 R4 R6
> > >
> > > where:
> > >
> > > R3 is an ABR of area 0 (left side) and area 1 (right side)
> > > R5 is internal of area 1
> > > R4 is ABR of area 1(left side) and area 3 (right side)
> > > R6 internal of area 3
> > >
> > > everything works fine until i want to configure virtual link between R3 and R4
> > > I added virtual-link section to area 0.0.0.0 in ospf4 section
> > >
> > ...
> >
> > * Which version of XORP are you using?
> > * Which platform are you using XORP on?
> > > area 0.0.0.0 {
> > > virtual-link 192.168.0.40 {
> > > transit-area: 0.0.0.1
> > > }
> > > ....
> > > and tried to add virtual-link to R4 without succeed because of error:
> > > Command failed Virtual link must be in area 0.0.0.0
> > >
> > > my question is how to configure virtual link at R4 ?
> > >
> >
> > This could be a problem in vlinks traversing area borders, or more
> > likely, a problem with the lookup by router ID.
> >
> > I'd have to check this code more fully before I could respond in detail
> > about that.
> >
> > The configuration steps you posted look correct, assuming that you are
> > configuring XORP up on R3.which is an ABR. But is area 1 a transit area
> > or a stub area? An NSSA area is *not* valid for virtual links, they can
> > only be configured across transit areas.
> >
> > More general questions:
> > Does R3 learn about R4 without the virtual-link config?
> > If so, which area(s) does R3 learn that R4 is in?
> > Does R5 see the same topology (neighbours) as R3 and R4?
> >
> > thanks,
> > BMS
> >
>
More information about the Xorp-users
mailing list