Friday, March 20, 2015

vMX Layer 2 Bridging

Hi all,

Today lets play layer 2 bridging with vMX from Juniper Network










==================================================================

interfaces {
    ge-0/0/0 {
        description "MANAGEMENT PORT PLEASE DO NOT DELETE";
        mac 00:0c:29:44:95:2d;
        unit 0 {
            family inet {
                address 10.210.14.31/24;
            }
        }
    }
    ge-0/0/1 {
        mac 00:0c:29:44:95:37;
        unit 0 {
            family bridge {
                interface-mode trunk;
                vlan-id-list 100;
            }
        }
    }
    ge-0/0/2 {
        mac 00:0c:29:44:95:41;
        unit 0 {
            family bridge {
                interface-mode trunk;
                vlan-id-list 100;
            }
        }
    }
  irb {
        unit 100 {
            family inet {
                address 90.1.1.1/24;
            }
        }
        unit 200 {
            family inet {
                address 90.1.1.2/24;
            }
        }
    }
}
routing-instances {
    sw1 {
        instance-type virtual-switch;
        interface ge-0/0/1.0;
        bridge-domains {
            bd100 {
                vlan-id 100;
                routing-interface irb.100;
            }
        }
    }
    sw2 {
        instance-type virtual-switch;
        interface ge-0/0/2.0;
        bridge-domains {
            bd100 {
                vlan-id 100;
                routing-interface irb.200;
            }
        }
    }
}



==========================================================================


lab@vMX-1> show bridge domain extensive 

Routing instance: sw1
Bridge domain: bd100                          State: Active
Bridge VLAN ID: 100                         
Interfaces:
    ge-0/0/1.0
Total MAC count: 0 

Routing instance: sw2
Bridge domain: bd100                          State: Active
Bridge VLAN ID: 100                         
Interfaces:
    ge-0/0/2.0
Total MAC count: 0 


===========================================================

lab@vMX-1> show route 

inet.0: 5 destinations, 6 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

10.210.14.0/24     *[Direct/0] 4d 03:04:47
                    > via ge-0/0/0.0
10.210.14.31/32    *[Local/0] 4d 03:04:47
                      Local via ge-0/0/0.0
90.1.1.0/24        *[Direct/0] 3d 06:41:08
                    > via irb.100
                    [Direct/0] 3d 06:37:29
                    > via irb.200
90.1.1.1/32        *[Local/0] 3d 06:43:11
                      Local via irb.100
90.1.1.2/32        *[Local/0] 3d 06:39:13
                      Local via irb.200

lab@vMX-1> ping 90.1.1.1 
PING 90.1.1.1 (90.1.1.1): 56 data bytes
64 bytes from 90.1.1.1: icmp_seq=0 ttl=64 time=3.044 ms
^C
--- 90.1.1.1 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 3.044/3.044/3.044/0.000 ms

lab@vMX-1> ping 90.1.1.2    
PING 90.1.1.2 (90.1.1.2): 56 data bytes
64 bytes from 90.1.1.2: icmp_seq=0 ttl=64 time=0.324 ms
64 bytes from 90.1.1.2: icmp_seq=1 ttl=64 time=0.728 ms
64 bytes from 90.1.1.2: icmp_seq=2 ttl=64 time=0.158 ms
^C
--- 90.1.1.2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.158/0.403/0.728/0.239 ms


======================================================================

Interface routing and bridging can communicate with each other to one vMX

you can expand to add more tenant connect to the instances..... and more vlans also

it was just and examples... :))


 

No comments:

Post a Comment