ospf and logical-system

mumuloxmumulox Member Posts: 31 ■■□□□□□□□□
Hello,

I'm trying to run ospf between 2 logical-system in one olive but I don't know why it's not working.

My config is simple:

root# show
## Last changed: 2009-12-21 23:49:30 UTC
version 9.6R1.13;
system {
root-authentication {
encrypted-password "$1$b94Y98rx$6MsOEmIpjB4xLUTqogkkU0"; ## SECRET-DATA
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
}
logical-systems {
R1 {
interfaces {
fxp1 {
unit 10 {
vlan-id 10;
family inet {
address 10.10.10.1/24;
}
}
}
}
protocols {
ospf {
area 0.0.0.0 {
interface 10.10.10.1;
}
}
}
}
R2 {
interfaces {
fxp2 {
unit 10 {
vlan-id 10;
family inet {
address 10.10.10.2/24;
}
}
}
}
protocols {
ospf {
area 0.0.0.0 {
interface 10.10.10.2;
}
}
}
}
}
interfaces {
fxp0 {
speed 10m;
link-mode full-duplex;
unit 0 {
family inet {
address 192.168.0.15/24;
}
}
}
fxp1 {
vlan-tagging;
}
fxp2 {
vlan-tagging;
}
}


root# run ping logical-system R1 10.10.10.2
PING 10.10.10.2 (10.10.10.2): 56 data bytes
64 bytes from 10.10.10.2: icmp_seq=0 ttl=64 time=2.692 ms
64 bytes from 10.10.10.2: icmp_seq=1 ttl=64 time=0.585 ms
^C
--- 10.10.10.2 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.585/1.639/2.692/1.054 ms

root# run ping logical-system R2 10.10.10.1
PING 10.10.10.1 (10.10.10.1): 56 data bytes
64 bytes from 10.10.10.1: icmp_seq=0 ttl=64 time=0.428 ms
64 bytes from 10.10.10.1: icmp_seq=1 ttl=64 time=0.392 ms
64 bytes from 10.10.10.1: icmp_seq=2 ttl=64 time=0.365 ms
^C
--- 10.10.10.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.365/0.395/0.428/0.026 ms
root# run show ospf neighbor logical-system R1

[edit]
root# run show ospf neighbor logical-system R2

[edit]

root# run show interfaces terse
Interface Admin Link Proto Local Remote
dsc up up
fxp0 up up
fxp0.0 up up inet 192.168.0.15/24
fxp1 up up
fxp1.10 up up inet 10.10.10.1/24
fxp1.32767 up up
fxp2 up up
fxp2.10 up up inet 10.10.10.2/24
fxp2.32767 up up
gre up up
ipip up up
lo0 up up
lo0.16384 up up inet 127.0.0.1 --> 0/0
lo0.16385 up up inet
lsi up up
mtun up up
pimd up up
pime up up
tap up up


For routing between logical-systems do I need to connect two real interfaces with a loop cable even if I can ping from one logical-system to another? fxp1 and fxp2 are not bridged with physical interfaces.

Thanks

Comments

  • Robert_74Robert_74 Member Posts: 38 ■■□□□□□□□□
    Seems like your OSPF interface are not defined properly.
    Instead of <interface 0.10.10.1> use <interface fxp1.10> or whatever interaces are in use.
    Hope it will help
    Thanks
    Robert
  • mumuloxmumulox Member Posts: 31 ■■□□□□□□□□
    no,it is not working. I don't understand if I need to connect fxp1 and fxp2 with a crossover cable or not, or the logical-router works by default .
  • zoidbergzoidberg Member Posts: 365 ■■■■□□□□□□
    I second what Robert said there.

    edit
    delete logical-systems R1 protocols ospf interface 10.10.10.1
    set logical-systems R1 protocols ospf interface fxp1.10
    delete logical-systems R1 protocols ospf interface 10.10.10.2
    set logical-systems R1 protocols ospf interface fxp2.10
    show | compare
    commit and-quit

    If that still doesn't work, include some new ospf outputs so we can see what's going on. I haven't done logical systems inside of an olive before, so I'm not certain about the physical connectivity requirements. I thought you needs to loop the ports, but I really don't know.
  • mumuloxmumulox Member Posts: 31 ■■□□□□□□□□
    logical-systems {
    R1 {
    interfaces {
    fxp1 {
    unit 10 {
    vlan-id 10;
    family inet {
    address 10.10.10.1/24;
    }
    }
    }
    }
    protocols {
    ospf {
    area 0.0.0.0 {
    interface fxp1.10;
    }
    }
    }
    }
    R2 {
    interfaces {
    fxp2 {
    unit 10 {
    vlan-id 10;
    family inet {
    address 10.10.10.2/24;
    }
    }
    }
    }
    protocols {
    ospf {
    area 0.0.0.0 {
    interface fxp2.10;
    }
    }
    }
    }
    }
    interfaces {
    fxp1 {
    vlan-tagging;
    }
    fxp2 {
    vlan-tagging;
    }
    }

    root# run show arp
    MAC Address Address Name Interface Flags
    00:aa:00:60:00:02 10.10.10.1 10.10.10.1 fxp2.10 none
    00:aa:00:60:00:03 10.10.10.2 10.10.10.2 fxp1.10 none
    Total entries: 2


    root# run show ospf interface logical-system R1
    Interface State Area DR ID BDR ID Nbrs
    fxp1.10 DR 0.0.0.0 10.10.10.1 0.0.0.0 0

    root# run show ospf interface logical-system R2
    Interface State Area DR ID BDR ID Nbrs
    fxp2.10 DR 0.0.0.0 10.10.10.2 0.0.0.0 0

    root# run ping logical-system R1 10.10.10.2
    PING 10.10.10.2 (10.10.10.2): 56 data bytes
    64 bytes from 10.10.10.2: icmp_seq=0 ttl=64 time=7.178 ms
    ^C
    --- 10.10.10.2 ping statistics ---
    1 packets transmitted, 1 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 7.178/7.178/7.178/0.000 ms

    [edit]
    verbose output suppressed, use <detail> or <extensive> for full protocol decode
    Address resolution is ON. Use <no-resolve> to avoid any reverse lookup delay.
    Address resolution timeout is 4s.
    Listening on fxp1, capture size 1500 bytes

    Reverse lookup for 224.0.0.5 failed (check DNS reachability).
    Other reverse lookup failures will not be reported.
    Use <no-resolve> to avoid reverse lookups on IP addresses.

    13:42:51.986712 Out IP 10.10.10.1 > 224.0.0.5: OSPFv2, Hello, length 44
    13:43:00.598393 Out IP 10.10.10.1 > 224.0.0.5: OSPFv2, Hello, length 44

    root# run monitor traffic interface fxp2 size 1500
    verbose output suppressed, use <detail> or <extensive> for full protocol decode
    Address resolution is ON. Use <no-resolve> to avoid any reverse lookup delay.
    Address resolution timeout is 4s.
    Listening on fxp2, capture size 1500 bytes

    Reverse lookup for 224.0.0.5 failed (check DNS reachability).
    Other reverse lookup failures will not be reported.
    Use <no-resolve> to avoid reverse lookups on IP addresses.

    13:43:21.052225 Out IP 10.10.10.2 > 224.0.0.5: OSPFv2, Hello, length 44
    13:43:29.081812 Out IP 10.10.10.2 > 224.0.0.5: OSPFv2, Hello, length 44
    ^C
    2 packets received by filter
    0 packets dropped by kernel
  • mumuloxmumulox Member Posts: 31 ■■□□□□□□□□
    I start olive with this command:

    qemu olive1.img -daemonize -serial telnet::2001,server,nowait -localtime -net nic,vlan=1,macaddr=00:aa:00:60:00:01,model=i82559er -net tap,vlan=1,ifname=tap0,script=no -net nic,vlan=2,macaddr=00:aa:00:60:00:10 model=i82559er -net nic,vlan=2,macaddr=00:aa:00:60:00:20,model=i82559er -net nic,vlan=2,macaddr=00:aa:00:60:00:30,model=i82559er -m 1024

    tap0 is bridged with eth1, tap1 bridge with eth2 (phisycal interfaces in my pc).
    If I connect the 2 interfaces with a crossover cable it will result a layer2 loop.
    My problem is that multicast traffic is olny in out direction. Ping works between the 2 logical-routers.
    I don't have a problema with multicast in olive because I cand run ospf between a cisco router and olive
  • AldurAldur Juniper Moderator Member Posts: 1,460
    wasn't there a problem with qemu in the old days that prevented ospf from working due to multicast problems?
    "Bribe is such an ugly word. I prefer extortion. The X makes it sound cool."

    -Bender
  • mumuloxmumulox Member Posts: 31 ■■□□□□□□□□
    Aldur wrote: »
    wasn't there a problem with qemu in the old days that prevented ospf from working due to multicast problems?

    Yes, it was, but ospf works ok between my cisco router and olive

    C1812#show ip ospf ne de
    Neighbor 192.168.0.15, interface address 192.168.0.15
    In the area 0 via interface Vlan1
    Neighbor priority is 128, State is FULL, 6 state changes
    DR is 192.168.0.1 BDR is 192.168.0.15
    Options is 0x42
    Dead timer due in 00:00:37
    Neighbor is up for 00:00:04
    Index 1/1, retransmission queue length 2, number of retransmission 0
    First 0x83ADC63C(1)/0x0(0) Next 0x83ADC63C(1)/0x0(0)
    Last retransmission scan length is 0, maximum is 0
    Last retransmission scan time is 0 msec, maximum is 0 msec
    Link State retransmission due in 848 msec

    root# run show ospf neighbor detail
    Address Interface State ID Pri Dead
    192.168.0.1 fxp0.0 Full 192.168.0.1 1 13
    Area 0.0.0.0, opt 0x52, DR 192.168.0.1, BDR 0.0.0.0
    Up 00:00:26, adjacent 00:00:26

    [edit]
  • mumuloxmumulox Member Posts: 31 ■■□□□□□□□□
    mumulox wrote: »
    Yes, it was, but ospf works ok between my cisco router and olive

    C1812#show ip ospf ne de
    Neighbor 192.168.0.15, interface address 192.168.0.15
    In the area 0 via interface Vlan1
    Neighbor priority is 128, State is FULL, 6 state changes
    DR is 192.168.0.1 BDR is 192.168.0.15
    Options is 0x42
    Dead timer due in 00:00:37
    Neighbor is up for 00:00:04
    Index 1/1, retransmission queue length 2, number of retransmission 0
    First 0x83ADC63C(1)/0x0(0) Next 0x83ADC63C(1)/0x0(0)
    Last retransmission scan length is 0, maximum is 0
    Last retransmission scan time is 0 msec, maximum is 0 msec
    Link State retransmission due in 848 msec

    root# run show ospf neighbor detail
    Address Interface State ID Pri Dead
    192.168.0.1 fxp0.0 Full 192.168.0.1 1 13
    Area 0.0.0.0, opt 0x52, DR 192.168.0.1, BDR 0.0.0.0
    Up 00:00:26, adjacent 00:00:26

    [edit]


    problem solved,i just upgraded my qemu to 0.11

    root# run show ospf neighbor logical-router R1
    Address Interface State ID Pri Dead
    10.10.10.2 fxp1.10 Full 10.10.10.2 128 32

    Thank you all for responses.
Sign In or Register to comment.