[j-nsp] vlan tagging, vlan ids, etc.

harry harry at juniper.net
Mon Dec 29 15:58:41 EST 2003


I do not see any problems with the configuration. Some Gig-E PICs have
firmware limitations on VLAN support in a CCC/L2 VPN environment, but I am
not aware of any issues with conventional VLAN tagging.

Have you tried:

1. Deactivating/reactivating the interface to see if a bounce resolves
(maybe try a commit full also)?

2. Looking in the log for any error messages?

3. I suspect the issue lies at the remote end, or in some intervening
device. Can you monitor traffic while pinging to confirm that traffic
(likely an ARP) leaves the interface with appropriate tagging/encapsulation?

This config works for me with two juniper boxes back-to-back:

[edit interfaces ge-0/3/0]
lab at San_Jose-3# show 
vlan-tagging;
unit 0 {
    vlan-id 1;
    family inet {
        address 10.222.29.2/24;
    }
}

[edit interfaces ge-0/3/0]
lab at San_Jose-3# run ping 10.222.29.1 count 1 
PING 10.222.29.1 (10.222.29.1): 56 data bytes
64 bytes from 10.222.29.1: icmp_seq=0 ttl=255 time=1.868 ms

--- 10.222.29.1 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.868/1.868/1.868/0.000 ms

And a dump on the local router while a ping is issued on the remote end:

[edit interfaces ge-0/3/0]
lab at San_Jose-3# run monitor interface ge-0/3/0.0 detail layer2-headers

Listening on ge-0/3/0.0, capture size 96 bytes

. . .
13:52:21.596706  In IP (tos 0x0, ttl 255, id 16701, offset 0, flags [none],
length: 84) 10.222.29.1 > 10.222.29.2: icmp 64: echo request
13:52:21.596791 Out 0:90:69:d6:1c:5d 0:90:69:97:24:1f 8100 102: VID [0:   1]
IP (tos 0x0, ttl 255, id
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^
 47106, offset 0, flags [none], length: 84) 10.222.29.2 > 10.222.29.1: icmp
64: echo reply
13:52:21.626012  In IP (tos 0xc0, ttl   1, id 16702, offset 0, flags [none],
length: 68) 10.222.29.1 > . . .. .

Note that L2 encap stuff in the outhoing echo reply.

HTHs.




> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of 
> David William
> Sent: Monday, December 29, 2003 12:41 PM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] vlan tagging, vlan ids, etc.
> 
> 
> First of all, I don't have much of a juniper background and have been 
> staring at the interfaces and class of service book for some time.
> 
> I have a Gigabit Ethernet connection between two facilities.  
> On one side I 
> have a cisco 3524 switch, on the other, I have a juniper M40 
> running an 
> older version of Junos - 5.2R2.3
> 
> On the juniper side, I have a simple setup of the link... 
> root at edge# show interfaces ge-3/3/0 unit 0 {
>     family inet {
>         no-redirects;
>         address 10.0.0.1/29;
>     }
> }
> 
> I can get across the link to the switch on the other end at 10.0.0.2
> 
> now, when I attempt to create subinterfaces I can no longer 
> get to the 
> switch on the other end.
> 
> root at edge# show interfaces ge-3/3/0
> vlan-tagging;
> unit 0 {
>     vlan-id 1;
>     family inet {
>         no-redirects;
>         address 10.0.0.1/29;
>     }
> unit 1 {
>     vlan-id 2;
>     family inet {
>         no-redirects;
>         address 10.0.1.1/30;
>     }
> unit 2 {
>     vlan-id 3;
>     family inet {
>         no-redirects;
>         address 10.0.2.1/30;
>     }
> }
> 
> I'm new to junos and am just unsure of what I am doing wrong. 
>  According to 
> the documentation this *should* work.
> 
> Any glaring problems with what I am doing?  Maybe its lack of 
> sleep from the 
> holidays that has me misreading this.
> 
> Thanks for any help
> 
> David William
> 
> _________________________________________________________________
> Worried about inbox overload? Get MSN Extra Storage now!  
> http://join.msn.com/?PAGE=features/es
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> http://puck.nether.net/mailman/listinfo/junipe> r-nsp
> 




More information about the juniper-nsp mailing list