Options

unit 20 not supported in fxp0 in juniper olive qemu

vishalsablevishalsable Member Posts: 15 ■□□□□□□□□□
hi,

I am preparing for JNCIP examination, i have installed olive in my PC, thanks to blog inevitable olive for JNCIE.

I am running olive with 2 logical routers, logical router R1 and logical router R2.

but i am facing a problem that when i am assigning IP addres to fxp0 with unit 20 vlan-id 20,
during commit the router gives an error as

[edit]
root# commit
[edit logical-routers R1 interfaces fxp0]
'unit 20'
Only unit 0 is valid for this interface
error: configuration check-out failed

[edit]
root#

Please help me.

Comments

  • Options
    AldurAldur Member Posts: 1,460
    good call rossonieri icon_cheers.gif

    To add to what rossonieri said, fxp1-7 will allow you to specify other logical units then 0 so this restriction just pertains to fxp0.
    "Bribe is such an ugly word. I prefer extortion. The X makes it sound cool."

    -Bender
  • Options
    rossonieri#1rossonieri#1 Member Posts: 799 ■■■□□□□□□□
    [edit]
    root# commit
    [edit logical-routers R1 interfaces fxp0]
    'unit 20'
    Only unit 0 is valid for this interface
    error: configuration check-out failed

    [edit]
    root#

    just an addition, how about doing some "commit check" prior to push that "commit" button?
    and after that - how about some "commit confirm"?

    and, do remember that aldur icon_lol.gif hahaha, just kidding buddy icon_lol.gif
    the More I know, that is more and More I dont know.
  • Options
    vishalsablevishalsable Member Posts: 15 ■□□□□□□□□□
    Thanks for the solution,

    also, before commiting I have checked commit check, same error.
  • Options
    rossonieri#1rossonieri#1 Member Posts: 799 ■■■□□□□□□□
    hi,
    also, before commiting I have checked commit check, same error.

    of course - it (the commit check" button) will prompt you the same warning/error message as that from the "commit" button command :)

    the benefit is that it (the "commit check") will allow you to review your config modification as if it was being executed, either correctly configured nor false. its output? you decide what to do next :)

    HTH.
    the More I know, that is more and More I dont know.
  • Options
    vishalsablevishalsable Member Posts: 15 ■□□□□□□□□□
    hi,

    I have created two logical routers R1 and R2.

    Logical router R1 has set interface fxp1 and Logical router R2 has set interface fxp2.

    but i am not able to ping each other.

    Please see the confiuration.

    }
    logical-routers {
    R1 {
    interfaces {
    fxp1 {
    unit 20 {
    vlan-id 20;
    family inet {
    address 20.1.1.1/30;
    }
    }
    }
    }
    }
    R2 {
    interfaces {
    fxp2 {
    unit 20 {
    vlan-id 20;
    family inet {
    address 20.1.1.2/30;
    }
    }
    }
    }
    }
    }
    interfaces {
    fxp0 {
    vlan-tagging;
    }
    fxp1 {
    vlan-tagging;
    }

    root# run ping logical-router R1 20.1.1.1
    PING 20.1.1.1 (20.1.1.1): 56 data bytes
    64 bytes from 20.1.1.1: icmp_seq=0 ttl=64 time=0.316 ms
    64 bytes from 20.1.1.1: icmp_seq=1 ttl=64 time=0.795 ms
    64 bytes from 20.1.1.1: icmp_seq=2 ttl=64 time=0.514 ms
    64 bytes from 20.1.1.1: icmp_seq=3 ttl=64 time=0.495 ms
    ^C
    --- 20.1.1.1 ping statistics ---
    4 packets transmitted, 4 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 0.316/0.530/0.795/0.171 ms

    [edit]
    root#

    [edit]
    root# run ping logical-router R1 20.1.1.2
    PING 20.1.1.2 (20.1.1.2): 56 data bytes

    ^C
    --- 20.1.1.2 ping statistics ---
    8 packets transmitted, 0 packets received, 100% packet loss

    [edit]
    root#


    Please help me i am not able to ping.......
  • Options
    rossonieri#1rossonieri#1 Member Posts: 799 ■■■□□□□□□□
    hi there,

    very nice :)
    now that you have playing with LRs - what an improvement :)
    Please help me i am not able to ping.......

    ok, here is the thing - since you're on JNCIP prep now,
    from this output :

    interfaces {
    fxp0 {
    vlan-tagging;
    }
    fxp1 {
    vlan-tagging;
    }

    you should be able to troubleshoot the error - how come you're not able to ping from R1 using fxp1 to R2 using fxp2,
    let us know if you still having hard time to configure :)

    cheers ;)
    the More I know, that is more and More I dont know.
  • Options
    AldurAldur Member Posts: 1,460
    ok, here is the thing - since you're on JNCIP prep now,
    from this output :

    interfaces {
    fxp0 {
    vlan-tagging;
    }
    fxp1 {
    vlan-tagging;
    }

    you should be able to troubleshoot the error - how come you're not able to ping from R1 using fxp1 to R2 using fxp2,

    ha, I had to have a double take to see what you were talking about, then was like ohhh yea, i see what's missing :D

    Lets sit back and see if the OP can figure it out from the hints you gave 68416045.wGDPMlLK.popcorn.gif
    "Bribe is such an ugly word. I prefer extortion. The X makes it sound cool."

    -Bender
  • Options
    rossonieri#1rossonieri#1 Member Posts: 799 ■■■□□□□□□□
    aldur,

    ha, I had to have a double take to see what you were talking about, then was like ohhh yea, i see what's missing

    dude, july 17th is about a month - you dont want to get messy with the proctor do you?
    Lets sit back and see if the OP can figure it out from the hints you gave

    ok, i'm out of VIP ticket - but, i dont mind if you have a spare one? :D

    hahaha ... just kidding mate ;)

    i like this joke thing icon_lol.gif

    ps : that popcorn looks good btw icon_lol.gif
    the More I know, that is more and More I dont know.
  • Options
    AldurAldur Member Posts: 1,460
    lol, man I'm so fried from studying services and all the issues that i've be working with at work that i tend to not see straight these days. And yes the 17th is coming up soon, and yes, i am scared ;) I do feel like i have a handle on services though plus I've got 12 days straight that I won't be working so I'll have some good time to cram icon_study.gif
    "Bribe is such an ugly word. I prefer extortion. The X makes it sound cool."

    -Bender
  • Options
    vishalsablevishalsable Member Posts: 15 ■□□□□□□□□□
    the problem u have said is correct,

    Also i have configured R1 on fxp1 and R2 on fxp2,

    I have tried various thing but i am not able to ping the 2 routers.

    Please hep me out.....
  • Options
    vishalsablevishalsable Member Posts: 15 ■□□□□□□□□□
    hi vishal?

    ok, here are some rules so we dont get confuse :)
    1. when we say olive - then it refers to the olive hardware emulation
    2. say 'jemu' then it refers to olive qemu instance

    ok, which one is yours?
    if you are using olive - make sure you've checked your NIC HW, cables etc.
    if you are doing jemu - make sure you've checked your qemu settings, cables etc.

    and of course - doing #run sh inter terse or #run sh conf interface will be helpful ;)

    and a little guide on doing ping on LR :
    [edit logical R1]
    #run ping logical R1 <destination_R2> source <source_R1> count <count>
    #run ping logical R1 <destination_R2> source <source_R1> rapid

    HTH.




    root# run show interfaces terse
    Interface Admin Link Proto Local Remote
    dsc up up
    fxp0 up up
    fxp0.0 up up inet 192.168.1.1/30
    fxp0.32767 up up
    fxp1 up up
    fxp1.0 up up inet 192.168.1.2/30
    fxp1.32767 up up
    gre up up
    ipip up up
    lo0 up up
    lo0.16385 up up inet
    inet6 fe80::2aa:ff:fe00:101
    lsi up up
    mtun up up
    pimd up up
    pime up up
    tap up up

    [edit]
    root#

    [edit]
    root# show
    version 8.1R2.4;
    system {
    root-authentication {
    encrypted-password "$1$N/XhEZzG$4HeT/XXk8eGh8uQp6A94k."; ## SECRET-DATA
    }
    login {
    user vishal {
    uid 2000;
    class super-user;
    authentication {
    encrypted-password "$1$u7GLsF87$xEQtc.wfClPvbZG2phv4C."; ## SECR
    ET-DATA
    }
    }
    }
    syslog {
    user * {
    any emergency;
    }
    file messages {
    any notice;
    authorization info;
    }
    file interactive-commands {
    interactive-commands any;
    }
    }
    }
    logical-routers {
    R1 {
    interfaces {
    fxp0 {
    unit 0 {
    vlan-id 2;
    family inet {
    address 192.168.1.1/30;
    }
    }
    }
    }
    }
    R2 {
    interfaces {
    fxp1 {
    unit 0 {
    vlan-id 2;
    family inet {
    address 192.168.1.2/30;
    }
    }
    }

    }
    }
    }
    interfaces {
    fxp0 {
    vlan-tagging;
    }
    fxp1 {
    vlan-tagging;
    }
    }

    [edit]
    root#


    root# ... R1 192.168.1.2 source 192.168.1.1 interface fxp0 count 100
    PING 192.168.1.2 (192.168.1.2): 56 data bytes


    this is the configuration, but i am not able tp ping.

    please help.....
  • Options
    miraculixmiraculix Member Posts: 2 ■□□□□□□□□□
    Try specifying the same vlan for all of the qemu interfaces, and avoid using fxp0 altogether. For example:

    jqemu.exe -L pc-bios -m 128 -hda OLIVE.img -serial telnet::2001,server -kernel-kqemu -localtime -net nic,vlan=1,macaddr=00:aa:00:00:01:01,model=i82559er -net tap,vlan=1,ifname=Tap1 -net nic,vlan=1,macaddr=00:aa:00:00:02:02,model=i82559er -net tap,vlan=1,ifname=Tap2 -net nic,vlan=1,macaddr=00:aa:00:00:03:03,model=i82559er -net tap,vlan=1,ifname=Tap3

    root@olive> show configuration
    ## Last commit: 2009-06-22 11:17:21 UTC by root
    version 8.4R2.3;
    system {
    host-name olive;
    }
    logical-routers {
    R1 {
    interfaces {
    fxp1 {
    unit 10 {
    vlan-id 10;
    family inet {
    address 192.168.10.1/24;
    }
    }
    }
    }
    }
    R2 {
    interfaces {
    fxp2 {
    unit 10 {
    vlan-id 10;
    family inet {
    address 192.168.10.2/24;
    }
    }
    }
    }
    }
    }
    interfaces {
    fxp1 {
    vlan-tagging;
    }
    fxp2 {
    vlan-tagging;
    }
    }


    root@olive> ping logical-router R1 192.168.10.2 count 5
    PING 192.168.10.2 (192.168.10.2): 56 data bytes
    64 bytes from 192.168.10.2: icmp_seq=0 ttl=64 time=1.028 ms
    64 bytes from 192.168.10.2: icmp_seq=1 ttl=64 time=1.912 ms
    64 bytes from 192.168.10.2: icmp_seq=2 ttl=64 time=1.454 ms
    64 bytes from 192.168.10.2: icmp_seq=3 ttl=64 time=1.449 ms
    64 bytes from 192.168.10.2: icmp_seq=4 ttl=64 time=1.933 ms

    --- 192.168.10.2 ping statistics ---
    5 packets transmitted, 5 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 1.028/1.555/1.933/0.337 ms

    HTH
  • Options
    vishalsablevishalsable Member Posts: 15 ■□□□□□□□□□
    hey i have tried all the options but not working, i dont know why

    i am running Jqemu


    C:\qemu>jqemu.exe -L . -m 128 -hda Olive.img -serial telnet::1001,server -kernel
    -kqemu -localtime -net nic,vlan=1,macaddr=00:aa:00:00:01:01,model=i82559er -net
    tap,vlan=1,ifname=Tap1 -net nic,vlan=1,macaddr=00:aa:00:00:02:02,model=i82559er
    -net tap,vlan=1,ifname=Tap2 -net nic,vlan=1,macaddr=00:aa:00:00:03:03,model=i825
    59er -net tap,vlan=1,ifname=Tap3

    QEMU waiting for connection on: :1001,server

    also disabled the firewall.......

    no luck.....

    option 1


    root@juniperolive# show
    version 8.1R2.4;
    system {
    host-name juniperolive;
    root-authentication {
    encrypted-password "$1$N/XhEZzG$4HeT/XXk8eGh8uQp6A94k."; ## SECRET-DATA
    }
    login {
    user vishal {
    uid 2000;
    class super-user;
    authentication {
    encrypted-password "$1$u7GLsF87$xEQtc.wfClPvbZG2phv4C."; ## SECR
    ET-DATA
    }
    }
    }
    syslog {
    user * {
    any emergency;
    }
    file messages {
    any notice;
    authorization info;
    }
    file interactive-commands {
    interactive-commands any;
    }
    }
    }
    logical-routers {
    R1 {
    interfaces {
    fxp1 {
    unit 10 {
    vlan-id 10;
    family inet {
    address 192.168.1.1/30;
    }
    }
    }
    }
    }
    R2 {
    interfaces {
    fxp2 {
    unit 10 {
    vlan-id 10;
    family inet {
    address 192.168.1.2/30;
    }
    }
    }
    }
    }
    }
    interfaces {
    fxp1 {
    vlan-tagging;
    }
    fxp2 {
    vlan-tagging;
    }
    }

    [edit]
    root@juniperolive#

    [edit]
    root@juniperolive# ping
    ^
    unknown command.
    root@juniperolive# run ping lo
    ^
    'lo' is ambiguous.
    Possible completions:
    <host> Hostname or IP address of remote host
    logical-router Name of logical router
    + loose-source Intermediate loose source route entry (IPv4)
    root@juniperolive# run ping logical-router R1 192.168.1.2 count 5
    PING 192.168.1.2 (192.168.1.2): 56 data bytes
    ^C
    --- 192.168.1.2 ping statistics ---
    5 packets transmitted, 0 packets received, 100% packet loss

    [edit]
    root@juniperolive#

    [edit]
    root@juniperolive# ... R1 192.168.1.2 source 192.168.1.1 count 5
    PING 192.168.1.2 (192.168.1.2): 56 data bytes
    ^C
    --- 192.168.1.2 ping statistics ---
    5 packets transmitted, 0 packets received, 100% packet loss

    [edit]
    root@juniperolive#

    [edit]
    root@juniperolive# ...l-router R1 192.168.1.2 source 192.168.1.1 count 5
    PING 192.168.1.2 (192.168.1.2): 56 data bytes

    ^C
    --- 192.168.1.2 ping statistics ---
    5 packets transmitted, 0 packets received, 100% packet loss

    [edit]
    root@juniperolive# run ping logical-router R1 192.168.1.2 count 5
    PING 192.168.1.2 (192.168.1.2): 56 data bytes
    ^C
    --- 192.168.1.2 ping statistics ---
    5 packets transmitted, 0 packets received, 100% packet loss

    [edit]
    root@juniperolive#



    option 2:

    root@juniperolive# set logical-routers R1

    [edit]
    root@juniperolive#

    [edit]
    root@juniperolive# set logical-routers R2

    [edit]
    root@juniperolive#

    [edit]
    root@juniperolive# set logical-routers R1 interfaces fxp0.0 uni
    ^
    syntax error.
    root@juniperolive# set logical-routers R1 interfaces fxp0.0 ?
    Possible completions:
    <[Enter]> Execute this command
    accounting-profile Accounting profile name
    + apply-groups Groups from which to inherit configuration data
    + apply-groups-except Don't inherit configuration data from these groups
    bandwidth Logical unit bandwidth (informational only)
    description Text description of interface
    disable Disable this logical interface
    encapsulation Logical link-layer encapsulation
    > family Protocol family
    no-traps Don't enable SNMP notifications on state changes
    traps Enable SNMP notifications on state changes
    vlan-id Virtual LAN identifier value for 802.1q VLAN tags
    | Pipe through a command
    [edit]
    root@juniperolive# ...an-id 5 family inet address 192.168.1.1/30

    [edit]
    root@juniperolive#

    [edit]
    root@juniperolive# set logical-routers R2 interfaces fxp1.0 vlan-id 5 famil...

    [edit]
    root@juniperolive#

    [edit]
    root@juniperolive# commit
    commit complete

    [edit]
    root@juniperolive#

    [edit]
    root@juniperolive# show
    version 8.1R2.4;
    system {
    host-name juniperolive;
    root-authentication {
    encrypted-password "$1$N/XhEZzG$4HeT/XXk8eGh8uQp6A94k."; ## SECRET-DATA
    }
    login {
    user vishal {
    uid 2000;
    class super-user;
    authentication {
    encrypted-password "$1$u7GLsF87$xEQtc.wfClPvbZG2phv4C."; ## SECR
    ET-DATA
    }
    }
    }
    syslog {
    user * {
    any emergency;
    }
    file messages {
    any notice;
    authorization info;
    }
    file interactive-commands {
    interactive-commands any;
    }
    }
    }
    logical-routers {
    R1 {
    interfaces {
    fxp0 {
    unit 0 {
    vlan-id 5;
    family inet {
    address 192.168.1.1/30;
    }
    }
    }
    }
    }
    R2 {
    interfaces {
    fxp1 {
    unit 0 {
    vlan-id 5;
    family inet {
    address 192.168.1.2/30;
    }
    }
    }
    }
    }
    }

    [edit]
    root@juniperolive# run show interfaces terse
    Interface Admin Link Proto Local Remote
    dsc up up
    fxp0 up up
    fxp1 up up
    fxp2 up up
    gre up up
    ipip up up
    lo0 up up
    lo0.16385 up up inet
    inet6 fe80::2aa:ff:fe00:101
    lsi up up
    mtun up up
    pimd up up
    pime up up
    tap up up

    [edit]
    root@juniperolive#

    [edit]
    root@juniperolive# run ping logical-router R1 192.168.1.1
    PING 192.168.1.1 (192.168.1.1): 56 data bytes
    ping: sendto: Can't assign requested address
    ping: sendto: Can't assign requested address
    ping: sendto: Can't assign requested address
    ^C
    --- 192.168.1.1 ping statistics ---
    3 packets transmitted, 0 packets received, 100% packet loss

    [edit]
    root@juniperolive#

    [edit]
    root@juniperolive# dela
    ^
    unknown command.
    root@juniperolive# delete logical-routers R1

    [edit]
    root@juniperolive#

    [edit]
    root@juniperolive# delete logical-routers R2

    [edit]
    root@juniperolive#

    [edit]
    root@juniperolive# show
    version 8.1R2.4;
    system {
    host-name juniperolive;
    root-authentication {
    encrypted-password "$1$N/XhEZzG$4HeT/XXk8eGh8uQp6A94k."; ## SECRET-DATA
    }
    login {
    user vishal {
    uid 2000;
    class super-user;
    authentication {
    encrypted-password "$1$u7GLsF87$xEQtc.wfClPvbZG2phv4C."; ## SECR
    ET-DATA
    }
    }
    }
    syslog {
    user * {
    any emergency;
    }
    file messages {
    any notice;
    authorization info;
    }
    file interactive-commands {
    interactive-commands any;
    }
    }
    }

    [edit]
    root@juniperolive# commit

    se commit complete

    [edit]
    root@juniperolive#

    [edit]
    root@juniperolive# set logical-routers R1 interfaces fxp1.0 uni
    ^
    syntax error.
    root@juniperolive# ...mily inet address 192.168.1.1/30

    [edit]
    root@juniperolive#

    [edit]
    root@juniperolive# set logical-routers R2 interfaces fxp2.0 family inet add...

    [edit]
    root@juniperolive#

    [edit]
    root@juniperolive# commit
    commit complete

    [edit]
    root@juniperolive#

    [edit]
    root@juniperolive# ping
    ^
    unknown command.
    root@juniperolive# run ping logical-router R1 192.168.1.2 count 5
    PING 192.168.1.2 (192.168.1.2): 56 data bytes
    ping: sendto: Can't assign requested address
    ping: sendto: Can't assign requested address
    ping: sendto: Can't assign requested address
    ping: sendto: Can't assign requested address

    ^C
    --- 192.168.1.2 ping statistics ---
    4 packets transmitted, 0 packets received, 100% packet loss
  • Options
    miraculixmiraculix Member Posts: 2 ■□□□□□□□□□
    Well, other than verifying that your Tap interfaces are in fact bridged together within the Windows host, the only other suggestion I can offer is upgrading from 8.1 to 8.4. I did encounter weird connectivity problems in 8.1 between logical routers that didn't seem to pop up in 8.4.
  • Options
    vishalsablevishalsable Member Posts: 15 ■□□□□□□□□□
    i will install 8.4 and check whether it will work or not....
  • Options
    vishalsablevishalsable Member Posts: 15 ■□□□□□□□□□
    hi vishal,

    so i see. you're run it under windows. hmm, well that will be something to look at since i dont spend much time doing jemu under windows - probably aldur has something for you since he's the windows guy ;). and i dont exactly know how you do it back there - so its very relative here,

    but btw, things for you to check - just like i said before :
    - look at cluepon.net to see whether your junos version is supported for jemu?
    - make sure you check your bridging config under windows, see if there are bridging loop on the switch, check if your bridge did correctly set up etc.
    - try to check your jemu config - its a C-coded config - so case-sensitive.

    from what i see, looks like either your junos version is not supported under olive, or
    your installation was not a successful one, i dont know?

    until then, good luck ;)

    hi rossonieri,

    can i use qemu in ubuntu.......
  • Options
    rossonieri#1rossonieri#1 Member Posts: 799 ■■■□□□□□□□
    hi vishal,

    sure thing :)
    the More I know, that is more and More I dont know.
  • Options
    vishalsablevishalsable Member Posts: 15 ■□□□□□□□□□
    can anybody tell me, where i can get junos 8.4 R software

    I search lot of sites, but no luck.....
  • Options
    AldurAldur Member Posts: 1,460
    Networking Security and Performance Solutions - Juniper Networks :D

    JUNOS is proprietary software so you'll need to download it from the Juniper website. Other means would be piracy icon_surprised.gif
    "Bribe is such an ugly word. I prefer extortion. The X makes it sound cool."

    -Bender
  • Options
    vishalsablevishalsable Member Posts: 15 ■□□□□□□□□□
    hey,

    i have changed my junos as well
    but no luck, can anybody solve the problem, is there any problem with the laptop.

    I am using Dell latitude E6500.

    also chk the configuration


    root@juniper-olive> show configuration
    version 7.4R1.7;
    system {
    host-name juniper-olive;
    root-authentication {
    encrypted-password "$1$uCqc3gxg$d0OnPI4h/KDp6/j8QD3dj."; ## SECRET-DATA
    }
    login {
    user vishal {
    uid 2000;
    class super-user;
    authentication {
    encrypted-password "$1$lupwkXYy$Z1bsjo.e2DsMdQEtXB4I1."; ## SECR
    ET-DATA
    }
    }
    }
    syslog {
    user * {
    any emergency;
    }
    file messages {
    any notice;
    authorization info;
    }
    file interactive-commands {
    interactive-commands any;
    }
    }
    }
    logical-routers {
    R1 {
    interfaces {
    fxp1 {
    unit 10 {
    vlan-id 10;
    family inet {
    address 192.168.1.1/30;
    }
    }
    }
    }
    }
    R2 {
    interfaces {
    fxp2 {
    unit 10 {
    vlan-id 10;
    family inet {
    address 192.168.1.2/30;
    }
    }
    }
    }
    }
    }
    interfaces {
    fxp1 {
    vlan-tagging;
    }
    fxp2 {
    vlan-tagging;
    }
    }

    root@juniper-olive> show interfaces terse
    Interface Admin Link Proto Local Remote
    dsc up up
    fxp0 up up
    fxp1 up up
    fxp1.10 up up inet 192.168.1.1/30
    fxp2 up up
    fxp2.10 up up inet 192.168.1.2/30
    gre up up
    ipip up up
    lo0 up up
    lo0.16385 up up inet
    inet6 fe80::2aa:ff:fe00:101
    lsi up up
    mtun up up
    pimd up up
    pime up up
    tap up up

    root@juniper-olive> ping logical-router R2 192.168.1.2
    PING 192.168.1.2 (192.168.1.2): 56 data bytes
    64 bytes from 192.168.1.2: icmp_seq=0 ttl=64 time=2.245 ms
    64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=1.633 ms
    64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=1.515 ms
    ^C
    --- 192.168.1.2 ping statistics ---
    3 packets transmitted, 3 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 1.515/1.798/2.245/0.320 ms

    root@juniper-olive>

    root@juniper-olive> ping logical-router R2 192.168.1.1
    PING 192.168.1.1 (192.168.1.1): 56 data bytes
    ^C
    --- 192.168.1.1 ping statistics ---
    5 packets transmitted, 0 packets received, 100% packet loss

    root@juniper-olive>

    root@juniper-olive> show version
    Hostname: juniper-olive
    Model: olive
    JUNOS Base OS boot [7.4R1.7]
    JUNOS Base OS Software Suite [7.4R1.7]
    JUNOS Kernel Software Suite [7.4R1.7]
    JUNOS Packet Forwarding Engine Support (M20/M40) [7.4R1.7]
    JUNOS Routing Software Suite [7.4R1.7]
    JUNOS Online Documentation [7.4R1.7]
    JUNOS Crypto Software Suite [7.4R1.7]

    root@juniper-olive>

    root@juniper-olive> ping logical-router R1 192.168.1.1
    PING 192.168.1.1 (192.168.1.1): 56 data bytes
    64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=3.591 ms
    64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.642 ms
    64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.548 ms

    ^C
    --- 192.168.1.1 ping statistics ---
    3 packets transmitted, 3 packets received, 0% packet loss
    round-trip min/avg/max/stddev = 1.548/2.260/3.591/0.942 ms

    root@juniper-olive> ping logical-router R1 192.168.1.2
    PING 192.168.1.2 (192.168.1.2): 56 data bytes
    ^C
    --- 192.168.1.2 ping statistics ---
    5 packets transmitted, 0 packets received, 100% packet loss


    please help me....
Sign In or Register to comment.