Junos
Highlighted
Junos

MUX-UNI feature

[ Edited ]
‎02-12-2014 07:02 PM

I wonder, will the MUX-UNI feature correctly work in JUNOS? I mean configuration where you can use ethernet-switching and subinterfaces on the same physical port. (Especially on the EX series switches).

 

This can be configured in 12.3R5.7, but works unidirectionally.

 

EX8208 <---(VIDS:72,3355)---> SWITCH

 

SWITCH HAS

VIF:72:172.16.4.60/24

VIF:3355:172.16.16.60/24

 

EX8208 4.1 and 16.1

 

EX8208 CONFIG:

 

interfaces ge-2/0/43                                    
vlan-tagging;
mtu 9216;
unit 0 {
    vlan-id 0;
    family ethernet-switching;
}
unit 3355 {
    vlan-id 3355;
    family inet {
        address 172.16.16.1/24;
    }
}

 

The subinterface works correctly (bidirectionally) until "unit 0" interface not included into any VLANs.

 

ping 172.16.16.60
PING 172.16.16.60 (172.16.16.60): 56 data bytes
64 bytes from 172.16.16.60: icmp_seq=0 ttl=64 time=10.655 ms
64 bytes from 172.16.16.60: icmp_seq=1 ttl=64 time=3.385 ms
64 bytes from 172.16.16.60: icmp_seq=2 ttl=64 time=3.353 ms
64 bytes from 172.16.16.60: icmp_seq=3 ttl=64 time=3.298 ms
64 bytes from 172.16.16.60: icmp_seq=4 ttl=64 time=3.317 ms

 

If I do:

vlans ETTH-MGMT
description ETTH-MANAGEMENT;
vlan-id 72;
interface {
    ge-2/0/43.0 {
        mapping {
            72 {
                swap;
            }
        }
    }
}

interfaces vlan unit 72
family inet {
    address 172.16.4.1/26;
}

 

(VRF used)

 

ping routing-instance ETTH-MGMT 172.16.4.60    
PING 172.16.4.60 (172.16.4.60): 56 data bytes
64 bytes from 172.16.4.60: icmp_seq=0 ttl=64 time=12.121 ms
64 bytes from 172.16.4.60: icmp_seq=1 ttl=64 time=3.504 ms
64 bytes from 172.16.4.60: icmp_seq=2 ttl=64 time=3.473 ms
64 bytes from 172.16.4.60: icmp_seq=3 ttl=64 time=3.519 ms
64 bytes from 172.16.4.60: icmp_seq=4 ttl=64 time=3.521 ms

ping 172.16.16.60                                        
PING 172.16.16.60 (172.16.16.60): 56 data bytes ^C
--- 172.16.16.60 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss

 

Seems like the switching module does not allow packets to reach the subinterface.

show interfaces ge-2/0/43.3355    
  Logical interface ge-2/0/43.3355 (Index 81) (SNMP ifIndex 1016)
    Flags: SNMP-Traps 0x0 VLAN-Tag [ 0x8100.3355 ]  Encapsulation: ENET2
    Input packets : 11
    Output packets: 21
    Protocol inet, MTU: 1500
      Flags: None
      Addresses, Flags: Is-Preferred Is-Primary
        Destination: 172.16.16/24, Local: 172.16.16.1, Broadcast:
172.16.16.255

 Ping from the switch:

TEST#ping 172.16.16.1
Pinging 172.16.16.1 with 18 bytes of data&colon;

PING: no reply from 172.16.16.1
PING: timeout
PING: no reply from 172.16.16.1
PING: timeout
PING: no reply from 172.16.16.1
PING: timeout
PING: no reply from 172.16.16.1
PING: timeout

----172.16.16.1 PING Statistics----
4 packets transmitted, 0 packets received, 100% packet loss

 Look again at EX8208:

run show interfaces ge-2/0/43.3355                   
  Logical interface ge-2/0/43.3355 (Index 81) (SNMP ifIndex 1016)
    Flags: SNMP-Traps 0x0 VLAN-Tag [ 0x8100.3355 ]  Encapsulation: ENET2
    Input packets : 11
    Output packets: 21
    Protocol inet, MTU: 1500
      Flags: None
      Addresses, Flags: Is-Preferred Is-Primary
        Destination: 172.16.16/24, Local: 172.16.16.1, Broadcast:
172.16.16.255

 

Input packets count did not change.

 

But on the other side (switch) I still can see a fresh ARP for the EX8208.

TEST#sh arp

  VLAN    Interface     IP address        HW address          status      
--------------------- --------------- ------------------- --------------- 
vlan 72    gi1/0/1    172.16.4.1      3c:8a:b0:09:e8:01   dynamic         
vlan 3355  gi1/0/1    172.16.16.1     3c:8a:b0:09:e8:8e   dynamic 

 

Do you think it worth waiting for the appearance of this feature in future releases?

Feedback