interface vlan-tagging in olive

prince862prince862 Member Posts: 3 ■□□□□□□□□□
in Juniper
hi, i made two olives -- each of them is bulit in following way :
olive1 --
attached two junos-supported NIC : <Intel EtherExpress Pro 10/100B Ethernet> on my COMPAQ machine
installed freeBSD 4.10 and then junOS 8.1R1.5
olive2 ---
same but with junOS 8.2 on freeBSD 4.4
i named my olives as "labR1" and "labR2". the NICs were found as fxp0 and fxp1.
i connected fxp0 to my office LAN switch from where i telnet to labR1 and labR2.
then i directly connected the fxp1 interface of both machines via a cross-over cable.


now, if i configure the fxp1.0 without VLAN i can ping from one olive to another.
but, if i configure the fxp1.0 with VLAN tag then i can not ping from one to another.

below is the non-VLAN configuration:

labR1 ---- 
[edit]
amin@labR1# show interfaces 
fxp0 {
    unit 0 {
        family inet {
            address 172.16.20.30/24;
        }
    }
}
fxp1 {
    unit 0 {
        family inet {
            address 172.91.1.1/24;
        }
    }
}
lo0 {
    unit 0 {
        family inet {
            address 1.1.1.1/32;
        }
    }
}


[edit]
amin@labR1#
labR2 ----
[edit]
amin@labR2# show interfaces 
fxp0 {
    unit 0 {
        family inet {
            address 172.16.20.31/24;
        }
    }
}
fxp1 {
    unit 0 {
        family inet {
            address 172.91.1.2/24;
        }
    }
}
lo0 {
    unit 0 {
        family inet {
            address 2.2.2.2/32;
        }
    }
}
output from labR1 ----
[edit]
amin@labR1# run ping 172.91.1.2 
PING 172.91.1.2 (172.91.1.2): 56 data bytes
64 bytes from 172.91.1.2: icmp_seq=0 ttl=64 time=0.216 ms
64 bytes from 172.91.1.2: icmp_seq=1 ttl=64 time=0.174 ms
64 bytes from 172.91.1.2: icmp_seq=2 ttl=64 time=0.139 ms
64 bytes from 172.91.1.2: icmp_seq=3 ttl=64 time=0.140 ms
64 bytes from 172.91.1.2: icmp_seq=4 ttl=64 time=0.129 ms
ò^C
--- 172.91.1.2 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.129/0.160/0.216/0.032 ms
now, i configured fxp1.0 with vlan-id 5 in both olive:

[edit]
amin@labR1# show interfaces 
fxp0 {
    unit 0 {
        family inet {
            address 172.16.20.30/24;
        }
    }
}
fxp1 {
    vlan-tagging;
    unit 0 {
        vlan-id 5;
        family inet {
            address 172.91.1.1/24;
        }
    }
}
lo0 {
    unit 0 {
        family inet {
            address 1.1.1.1/32;
        }
    }
}

[edit]
amin@labR1#

now --- labR2 ----

[edit]
amin@labR2# show interfaces 
fxp0 {
    unit 0 {
        family inet {
            address 172.16.20.31/24;
        }
    }
}
fxp1 {
    vlan-tagging;
    unit 0 {
        vlan-id 5;
        family inet {
            address 172.91.1.2/24;
        }
    }
}
lo0 {
    unit 0 {
        family inet {
            address 2.2.2.2/32;
        }
    }
}

[edit]
amin@labR2#

now, i can not ping fxp1 of labR2 from labR1 ----

[edit]
amin@labR1# run ping 172.91.1.2 count 4 
PING 172.91.1.2 (172.91.1.2): 56 data bytes
ò^C
--- 172.91.1.2 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
[edit]
amin@labR1#


hope, someone will give me a way so that i can ping via vlan-enabled fxp1 interface.

basically, i need multiple logical interfaces to use in fxp1. and i found no way but to use vlan-tagging for that purpose. but the vlanned conf is not working.

thanks for ur patience.
· Share on FacebookShare on Twitter

Comments

  • AldurAldur Member Posts: 1,460
    There really shouldn't be a problem with assigning vlans to fxp ports. I have a bunch of olives, 17 to be exact, and 5 j2300 routers, and I have no problem using vlans on the olive fxp ports. I actually have to use vlans because I have the olives sliced up into logical routers and each fxp port is a logical router with multiple vlan'd units coming off each port.

    I reviewed your config and there shouldn't be an issue with using vlans. The only thing I can think of is that olives can act very funny if they are on differing version of code. I would recommend getting both olives on the same version of code and then trying again.
    "Bribe is such an ugly word. I prefer extortion. The X makes it sound cool."

    -Bender
    · Share on FacebookShare on Twitter
  • prince862prince862 Member Posts: 3 ■□□□□□□□□□
    Aldur wrote:
    There really shouldn't be a problem with assigning vlans to fxp ports. I have a bunch of olives, 17 to be exact, and 5 j2300 routers, and I have no problem using vlans on the olive fxp ports. I actually have to use vlans because I have the olives sliced up into logical routers and each fxp port is a logical router with multiple vlan'd units coming off each port.

    I reviewed your config and there shouldn't be an issue with using vlans. The only thing I can think of is that olives can act very funny if they are on differing version of code. I would recommend getting both olives on the same version of code and then trying again.

    thanks a lot for your reply.
    like your case, i need multiple logical interfaces for the sake of multiple logical routers.
    and mutiple uints require vlanned interface which is not working.

    well, now i will try to fix the version mismatch and update the result ....
    · Share on FacebookShare on Twitter
  • AldurAldur Member Posts: 1,460
    Also, did you put 8.x on the olives right after the freeBSD install? There is know issues with anything past 7.2 as a first install, normally from what I've seen you can even complete the install. You can upgrade/downgrade the junos after that but if you went straight from freeBSD to 8.x that could also cause a problem. Olives seem just to have a mind of their own :D

    Btw, what are you putting the olives together for, going down the M/T series cert track?
    "Bribe is such an ugly word. I prefer extortion. The X makes it sound cool."

    -Bender
    · Share on FacebookShare on Twitter
  • prince862prince862 Member Posts: 3 ■□□□□□□□□□
    Aldur wrote:
    Also, did you put 8.x on the olives right after the freeBSD install? There is know issues with anything past 7.2 as a first install, normally from what I've seen you can even complete the install. You can upgrade/downgrade the junos after that but if you went straight from freeBSD to 8.x that could also cause a problem. Olives seem just to have a mind of their own :D

    Btw, what are you putting the olives together for, going down the M/T series cert track?
    at last it worked. u were right -- the problem was version related. here is the findings ---

    ----olive1 : junOS 8.1R1.5 (upgraded) on freeBSD 4.10
    olive 2: JunOS 8.2R2.4 (installed) on freeBSD 4.4
    --- vlan did not work
    ----olive1 : junOS 8.1R1.5 (upgraded) on freeBSD 4.10
    olive 2: JunOS 7.0R1.5 (installed) on freeBSD 4.10
    ---- vlan did not work
    olive1 : junOS 7.0R1.5 (installed) on freeBSD 4.10
    olive 2: JunOS 7.0R1.5 (installed) on freeBSD 4.10
    ---- vlan works
    · Share on FacebookShare on Twitter
  • AldurAldur Member Posts: 1,460
    Thats great to hear that the vlans are working now, those olives sure can be finicky but now that you got it all working you can practice to your hearts desire :D

    Also, if you need to get your olives on a higher version of code for any reason just upgrade them now like you would a normal router.
    "Bribe is such an ugly word. I prefer extortion. The X makes it sound cool."

    -Bender
    · Share on FacebookShare on Twitter
Sign In or Register to comment.