17/02/2017

Cisco – ASR 920 VPLS – manual

Das schnellste und einfachste VPLS:

Auf einem ASR 920 hab ich 1 Interface fuer VPLS konfiguriert, am anderen ASR 920 hab ich 2 Interfaces in der selben VPLS Instanz. Angesteckt hab ich dann zwei MikroTiks um zu sehen ob sie sich alle sehen 😉

ASR 920 – 1:

bridge-domain 2
 mac limit maximum addresses 1024
 member GigabitEthernet0/0/1 service-instance 1

l2 vfi VPLS2 manual
 vpn id 2
 bridge-domain 2
 mtu 1540
 neighbor 10.1.1.2 encapsulation mpls

interface GigabitEthernet0/0/1
 mtu 1540
 no ip address
 negotiation auto
 service instance 1 ethernet
  encapsulation default
  l2protocol forward

 
ASR 920 – 2:

bridge-domain 2
 mac limit maximum addresses 1024
 member GigabitEthernet0/0/1 service-instance 1
 member GigabitEthernet0/0/2 service-instance 1

l2 vfi VPLS2 manual
 vpn id 2
 bridge-domain 2
 mtu 1540
 neighbor 10.1.1.1 encapsulation mpls

interface GigabitEthernet0/0/1
 mtu 1540
 no ip address
 negotiation auto
 service instance 1 ethernet
  encapsulation default
  l2protocol forward

interface GigabitEthernet0/0/2
 mtu 1540
 no ip address
 negotiation auto
 service instance 1 ethernet
  encapsulation default
  l2protocol forward

 

Das schaut dann so aus:

Router#sh mpls l2 vc 2 de
Local interface: VFI VPLS2 vfi up
  Interworking type is Ethernet
  Destination address: 10.1.1.2, VC ID: 2, VC status: up
    Output interface: Te0/0/26, imposed label stack {18}
    Preferred path: not configured
    Default path: active
    Next hop: 10.100.1.2
  Create time: 00:41:56, last status change time: 00:26:52
    Last label FSM state change time: 00:26:52
  Signaling protocol: LDP, peer 10.1.1.2:0 up
    Targeted Hello: 10.1.1.1(LDP Id) -> 10.1.1.2, LDP is UP
    Graceful restart: not configured and not enabled
    Non stop routing: not configured and not enabled
    Status TLV support (local/remote)   : enabled/supported
      LDP route watch                   : enabled
      Label/status state machine        : established, LruRru
      Last local dataplane   status rcvd: No fault
      Last BFD dataplane     status rcvd: Not sent
      Last BFD peer monitor  status rcvd: No fault
      Last local AC  circuit status rcvd: No fault
      Last local AC  circuit status sent: No fault
      Last local PW i/f circ status rcvd: No fault
      Last local LDP TLV     status sent: No fault
      Last remote LDP TLV    status rcvd: No fault
      Last remote LDP ADJ    status rcvd: No fault
    MPLS VC labels: local 17, remote 18
    Group ID: local n/a, remote 0
    MTU: local 1540, remote 1540
    Remote interface description:
  Sequencing: receive disabled, send disabled
  Control Word: On (configured: autosense)
  SSO Descriptor: 10.1.1.2/2, local label: 17
  Dataplane:
    SSM segment/switch IDs: 16393/8199 (used), PWID: 2
  VC statistics:
    transit packet totals: receive 2519, send 1291
    transit byte totals:   receive 1681716, send 1620763
    transit packet drops:  receive 0, seq error 0, send 0


Router#

 
Und so:

Router#sh bridge-domain 2
Bridge-domain 2 (2 ports in all)
State: UP                    Mac learning: Enabled
Aging-Timer: 300 second(s)
Maximum address limit: 1024
    GigabitEthernet0/0/1 service instance 1
    vfi VPLS2 neighbor 10.1.1.2 2

   Nile Mac Address Entries

   BD    mac addr        type     ports
   ----------------------------------------------------------------------------------------------
   2     000c.4270.d28d  DYNAMIC  10.1.1.2, 2
   2     4c5e.0c7c.1a52  DYNAMIC  10.1.1.2, 2
   2     d4ca.6d21.20b3  DYNAMIC  Gi0/0/1.Efp1

Router#

 
Wir sehen 3 verschiedene MAC Adressen, was auch 3 verschiedene MikroTiks sind. QinQ geht auch ueber den Link und BPDUs ebenfalls. Ich habe den kleinsten MikroTik (mAP) als STP Root Bridge konfiguriert und die andere beiden sehen ihn auch als Root Bridge!

Blick von MikroTik RB751G-2HnD:

 

Und so sah das in echt aus: