Juniper EX and IPv6

[truman at suspicious.org]

After the interesting post regarding ipv6 forwarding on ex-series, I asked one our engineers to test this out. Everything worked fine with no specific IPv6 configuration on the EX running junos 9.3

Details below:

it works fine in 9.3 .

M10i ------- EX -------- M160


EX in L2 mode with trunk-port to M10i and M160, and also configured a L3-interface vlan.10 on EX,  both transit and local originated icmp6 traffic works fine.


lab at m10i-re0# run show interfaces terse ge-0/0/0 
Interface               Admin Link Proto    Local                 Remote
ge-0/0/0                up    up  
ge-0/0/0.0              up    up   inet     20.1.1.1/24     
                                   inet6    fe80::205:8500:af3:b000/64
                                            fec0:1:1:1::1/64
                                   mpls    


lab at m160# run show interfaces terse ge-6/1/0 
Interface               Admin Link Proto    Local                 Remote
ge-6/1/0                up    up  
ge-6/1/0.0              up    up   inet     20.1.1.2/24     
                                   inet6    fe80::290:6900:a4e:3f13/64
                                            fec0:1:1:1::2/64


lab at EX4200-IPG# run show interfaces terse vlan.10 
Interface               Admin Link Proto    Local                 Remote
vlan.10                 up    up   inet6    fe80::219:e2ff:fe50:a300/64
                                            fec0:1:1:1::3/64



lab at m10i-re0# run ping fec0:1:1:1::2    
PING6(56=40+8+8 bytes) fec0:1:1:1::1 --> fec0:1:1:1::2
16 bytes from fec0:1:1:1::2, icmp_seq=0 hlim=64 time=1.022 ms
16 bytes from fec0:1:1:1::2, icmp_seq=1 hlim=64 time=0.849 ms
16 bytes from fec0:1:1:1::2, icmp_seq=2 hlim=64 time=0.985 ms
^C
--- fec0:1:1:1::2 ping6 statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/std-dev = 0.849/0.952/1.022/0.074 ms

[edit]
lab at m10i-re0# run ping fec0:1:1:1::3    
PING6(56=40+8+8 bytes) fec0:1:1:1::1 --> fec0:1:1:1::3
16 bytes from fec0:1:1:1::3, icmp_seq=0 hlim=64 time=1.069 ms
16 bytes from fec0:1:1:1::3, icmp_seq=1 hlim=64 time=0.763 ms
16 bytes from fec0:1:1:1::3, icmp_seq=2 hlim=64 time=1.097 ms
16 bytes from fec0:1:1:1::3, icmp_seq=3 hlim=64 time=1.029 ms
^C
--- fec0:1:1:1::3 ping6 statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/std-dev = 0.763/0.989/1.097/0.133 ms


lab at m10i-re0# run show ipv6 neighbors 
IPv6 Address                 Linklayer Address  State       Exp Rtr Interface
fec0:1:1:1::2                00:90:69:4e:3f:13  stale       1044 yes ge-0/0/0.0  
fec0:1:1:1::3                00:19:e2:50:a3:00  stale       1113 yes ge-0/0/0.0  



lab at EX4200-IPG# run show version 
fpc0:
--------------------------------------------------------------------------
Hostname: EX4200-IPG
Model: ex4200-24f
JUNOS Base OS boot [9.3-20080816.0]
JUNOS Base OS Software Suite [9.3-20080816.0]
JUNOS Kernel Software Suite [9.3-20080816.0]
JUNOS Crypto Software Suite [9.3-20080816.0]
JUNOS Online Documentation [9.3-20080816.0]
JUNOS Enterprise Software Suite [9.3-20080816.0]
JUNOS Packet Forwarding Engine Enterprise Software Suite [9.3-20080816.0]
JUNOS Routing Software Suite [9.3-20080816.0]
JUNOS Web Management [9.3-20080816.0]

Kind regards,
Truman Boyes


------Original Message------
From: Pekka Savola
Sender: ipv6-ops-bounces+truman=suspicious.org at lists.cluenet.de
To: Udo Steinegger
Cc: ipv6-ops at lists.cluenet.de
Sent: Nov 8, 2008 9:25 AM
Subject: Re: Juniper EX and IPv6

On Sat, 8 Nov 2008, Udo Steinegger wrote:
> You need family ethernet-switching rather than family
> Inet6 on your Interface/unit.
> Guess that was your problem.
>
> My setup:
> Host--ex4200--ex4200--host
>
> Works just Fine with JunOS 9.x, with x equals to 0, 1 and 2

In our case, it wasn't enough.  Example:

interfaces {
     ...
     ge-0/0/39 {
         unit 0 {
             family ethernet-switching;
         }
     }
     ...
     vlan {
         unit 0 {
             family inet {
                 filter {
                     input ACL;
                 }
                 address x.x.x.x/24;
             }
             family inet6; <== had to be added
         }
     }

vlans {
     default {
         vlan-id 1;
         l3-interface vlan.0; <== had to be added
     }
}

I'd suspect that adding family inet and a v4 address for management 
purposes made the software confused whether it should be a switch or 
router; however, v4 packets were switched fine without adding these 
two options, v6 weren't.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings



Sent via BlackBerry® from Telstra