[c-nsp] BVI on ME3600?

Ulrik Ivers ulrik.ivers at excanto.se
Mon Jan 20 16:26:16 EST 2014


Hi,

We are doing routed SVI connected to a vfi between two ME3600 and a Cat6500 (SUP2T). Like this on one of the ME3600:

l2 vfi VPLS-120 manual 
 vpn id 120
 neighbor 172.16.250.11 encapsulation mpls
 neighbor 172.16.250.13 encapsulation mpls

interface Vlan120
 ip vrf forwarding VRF-A
 ip address 10.1.1.1 255.255.255.0
 xconnect vfi VPLS-120


However, I read your question as you have p2p xconnects in the bridge domain, in addition to the vfi? That I have not implemented or tested.

Also, I think the SVI has to be UP for the VC to be  brought up.

Regards,

/Ulrik Ivers

-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Adam Vitkovsky
Sent: den 20 januari 2014 16:29
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] BVI on ME3600?

Hi folks,
Is there a support for bvi or routed interface in bridge-domain or vfi on me3600. 

I'd like to terminate couple of p2p xconnects in a common bridge-domain/vfi along with a vlan interface with vrf designation and ip address and I can't get it working. 


l2 vfi corporate-inet manual
 vpn id 2
 bridge-domain 4001
 neighbor 10.105.1.5 1412171450 encapsulation mpls !
!
interface Vlan4001
 mtu 9000
 vrf forwarding inet
 ip address 192.168.50.4 255.255.255.0
 xconnect vfi corporate-inet


sh l2 vfi
VFI name: corporate-inet, state: down, type: multipoint, signaling: LDP
  VPN ID: 2
  Bridge-Domain 4001 attachment circuits:
    Vlan4001  
  Pseudo-port interface: pseudowire100009
  Interface          Peer Address     VC ID        S
  pseudowire100010   10.105.1.5       1412171450   Y


sh mpls l2 vc 1412171450 det 
Local interface: VFI corporate-inet vfi down
  Interworking type is Ethernet
  Destination address: 10.105.1.5, VC ID: 1412171450, VC status: down
    Last error: Local access circuit is not ready for label advertise
    Output interface: none, imposed label stack {}
    Preferred path: not configured  
    Default path: no route
    No adjacency
  Create time: 00:06:34, last status change time: 4w3d
    Last label FSM state change time: 00:06:34
  Signaling protocol: LDP, peer 10.105.1.5:0 up
    Targeted Hello: 10.105.1.6(LDP Id) -> 10.105.1.5, LDP is UP
    Graceful restart: configured and enabled
    Non stop routing: not configured and not enabled
    Status TLV support (local/remote)   : enabled/supported
      LDP route watch                   : enabled
      Label/status state machine        : remote ready, LndRru
      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: DOWN(hard-down, not-ready)
      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 status
      Last remote LDP TLV    status rcvd: No fault
      Last remote LDP ADJ    status rcvd: No fault
    MPLS VC labels: local unassigned, remote 24 
    Group ID: local unknown, remote 0
    MTU: local unknown, remote 9000
    Remote interface description: [inet] backhaul for corporate inet common
subnet
  Sequencing: receive disabled, send disabled
  Control Word: Off (configured: autosense)
  Dataplane:
    SSM segment/switch IDs: 0/0 (used), PWID: 7
  VC statistics:
    transit packet totals: receive 0, send 0
    transit byte totals:   receive 0, send 0
    transit packet drops:  receive 0, seq error 0, send 0


thanks

adam

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list