L2VPN 6.1

Similar Questions

• Compatibility L2VPN NSX

  Hello world:

  The NSX CIM student guide say about IPSEC (L3VPN)

  Standard IPsec implementation in the industry:

  Interoperability with Cisco, Juniper, Sonicwall and others

  I'm looking for a list of compatible L2VPN suppliers

  Do you know or have you tested L2VPN with a third device?

  Can you tell me the brand and model/version of the device to third parties?

  I'm sure that it is it possible to connect with any car is a very simple technology and is a standard, but I want to be sure.

  Thanks in advance

  Al

  For IPsec, we adhere to the standard Ipsec and IKE RFC (IKEv1). We tested interop against Cisco, Juniper and sonicwall products (there are examples of config with Cisco 2812 + Cisco ASA 5510 WatchGuard Firebox X 500 in the Administrator's Guide too).

  However L2VPN uses protocol tunneling owner and not using L2TP or GRE tunneling standard protocols. The feature is developed by engine extension SSLVPN from the edge; That's why L2VPN use SSL as a transport. And so there is no interoperability with our L2VPN & SSLVPN since it is implemented exclusive.

  Note: For L2VPN, you need not NSX at the remote location. You deploy only the standalone unmanaged Client edge.

  Dimitri

• L2VPN ASR9k circuit of attachment in the switch (not marked frame)

  Hi guys,.

  I am trying to look at the best solution for the creation of a Pseudo-filaires on an ASR9k and extend the accessory circuit in one or the other 6500 or Nexus 6001 switch.

  The circuit of the attachment must not be tagged, so that the customer can push some VLAN they want on their executives. The scenario I'm looking at would imply a 6001 Nexus or 6500 who sat below the PE and provide the physical presentation of the customer.

  I thought a VCA using Dot1q tunnel with each client associated with a tag on the EP and the S switch, but haven't tested it. Another way would be to use a bridge domain to link two interfaces together on the EP, but that would still potentially require Q-in-Q isolate each customer and to enable each client to push some C-tags they want on executives.

  Any help on this would be much appreciated!

  Steve

  the best way to me and I've tested this, would be:

  Customer--(dot1q)--QinQ/tunnel---6500---(AC)---(dot1q-SVLAN)ASR9k(MPLS)

  This way you can provide a vlan transparency without having to return to service each client.

• Missmatch native VLAN on Metro Ethernet Service

  Dear

  We have a curious problem with the subway linking remote sites (by 3600 and 3750) and service headquarters (xconnect with asr9010).

  Here is the configuration:

  RP/0/RSP0 / CPU0:MyPoP - ASR9010-NPE-01 #sh run l2vpn bridge group MyComp bridge-field XC-Cust-P2MP nearby [UPE IP] pw - id [XC]
  Sun Jul 31 17:02:58.955 WIB
  L2VPN
  Bridge MyComp group
  Bridge-field XC-Cust-P2MP
  neighbor [UPE IP] pw - id [XC]
  split horizon group
  !

  myPoP-ME3600-UPE-01 #sh run int g0/20 | s service instance [XC]
  [XC] ethernet service instance
  encapsulation dot1q [XC]
  rewrite tag pop 1 symmetrical penetration
  XConnect [ASR IP] [XC] mpls encapsulation

  3600 we connected 2960 and have this journal:

  Jul 31 00:05:44 WIB: CDP-4-NATIVE_VLAN_MISMATCH %: incompatibility of VLAN native discovered on GigabitEthernet0/23 (1), with router.user FastEthernet3 (30).
  Jul 31 00:06:44 WIB: CDP-4-NATIVE_VLAN_MISMATCH %: incompatibility of VLAN native discovered on GigabitEthernet0/23 (1), with router.user FastEthernet3 (30).
  Jul 31 00:08:44 WIB: CDP-4-NATIVE_VLAN_MISMATCH %: incompatibility of VLAN native discovered on GigabitEthernet0/23 (1), with router.user FastEthernet3 (30).
  Jul 31 00:10:45 WIB: CDP-4-NATIVE_VLAN_MISMATCH %: incompatibility of VLAN native discovered on GigabitEthernet0/23 (1), with router.user FastEthernet3 (30).
  Jul 31 00:11:45 WIB: CDP-4-NATIVE_VLAN_MISMATCH %: incompatibility of VLAN native discovered on GigabitEthernet0/23 (1), with router.user FastEthernet3 (30).

  I apply this config on 2960:

  C2960-CPE-01 #sh run int g0/23
  Building configuration...

  Current configuration: 239 bytes
  !
  interface GigabitEthernet0/23
  switchport trunk allowed vlan xx, xx, xx, xx, xx, xx, [XC]
  switchport mode trunk
  load-interval 30
  spanning tree enable bpdufilter
  end

  without activating the spanning tree bpdufilter, VLANs [XC] will be blocked.

  do you have the same experience with us, and what is the solution.

  Thank you

  The customer uses a different native lan (using 1 and they use 30).  Easier difficulty for you is probably:

  interface GigabitEthernet0/23  no cdp enable

• Double-tag becomes triple-tag me3600 to ASR91K

  Hello

  I installed a Pseudo-fil between a port on a x-me3600 to an ASR91K frames received on the me3600 are QinQ (101.25 for example) these images are then routed via a xconnect to an ASR91K where I drop them on an interface (which I then 'handbag' to use for the services of the BNG) however on the interface of 9K if I plug in my laptop and use wireshark frames are received with triple-tags (for example 101,101,25) where the external tag is repeated.

  The configuration was working fine on an ASR901, however as soon as I swapped out for a ME3600 901, this problem started.

  How can I get the original qinq passed without the additional tag being added (and why it does this?)

  The concerned formations are the following:

  ME3600:

  interface GigabitEthernet0/3

  switchport trunk allowed vlan no

  switchport mode trunk

  No keepalive

  ethernet 10 service instance

  lack of encapsulation

  XConnect 103.241.59.4 10 mpls encapsulation

  MTU 9216

  ASR9K1:

  L2VPN

  L2VPN

  Group of REMOTE bridge

  Bridge-REMOTE domain

  Mac

  limit

  32000 maximum

  !

  !

  MTU 9216

  transport mode vlan passthrough

  interface GigabitEthernet0/0/0/2.1

  !

  neighbor 103.241.59.2 pw - id 10

  split horizon group

  !

  INTERFACE

  interface GigabitEthernet0/0/0/2

  !

  GigabitEthernet0/0/0/2.1 l2transport interface

  lack of encapsulation

  also all debugging commands show/good would be great, because at this point, the only way I can see what's going on is using wireshark.

  Thank you

  Mike

  Hi Mike,.

  Sure. No worries. The config you had previously as mentioned before should not add a tag, so I was wondering if we are adding and sending via 9 k or 9K it adds.

  My idea would be to first check that is to add, check with more specific encap. According to this result, we can progress further.

  If it's ME add extra, we can try to change for the VC 4 type using the ' interoperability vlan "option on ME and forcing to type 4, as default type it 5?

  Thank you

  Madhu

• Meet the VPLS and EoMPLS circuit

  Hi all

  I have ASR1006 IOS - XE as router PE who have connected to another model with the same PE. And I have VPLS put in place to provide E - LAN service. Interface of multiple GE on the two site have joined this group VPLS. Now that we have an another EP (ISR G2 router, use small scale) who must join that group VPLS. Since IOS ISR G2 do not support VPLS, we can get EoMPLS(E-LINE) service.

  Is it possible to interconnect VPLS and EoMPLS.  Referring to the below example configuration, can I do 110 the Service Instance as a member in bridge - 10 field? Is who would eventually interconnect EoMPLS to VPLS? All the router currently in production. Any ideas would be much appreciated.

  context of PFD l2vpn PFD-TEST / / VPLS
  VPN id 10
  members 10.166.10.2 mpls encapsulation

  Bridge-area 10
  Members GigabitEthernet0/0/0 instance-service 101
  Members GigabitEthernet0/0/0 service instance-102
  Members GigabitEthernet0/0/0-service instance 103
  PFD PFD-TEST members

  interface GigabitEthernet0/0/0
  101 ethernet service instance
  encapsulation dot1q 101
  rewrite tag pop 1 symmetrical penetration
  !
  102 ethernet service instance
  encapsulation dot1q 102
  rewrite tag pop 1 symmetrical penetration
  !
  ethernet 103 service instance
  encapsulation dot1q 103
  rewrite tag pop 1 symmetrical penetration
  !
  110 ethernet service instance
  encapsulation dot1q 110
  rewrite tag pop 1 symmetrical penetration
  XConnect 10.200.149.110 10 mpls encapsulation / / EoMPLS
  !

  I have not tested but I think it should work. We have the two Eompls/VPLS in a hub-and-spoke topology. However given that this topology is not entirely mesh you must disable split horizon for PE2 and PE3 talk to each other.

  PE2 - VPLS - PE1 - EOMPLS - PE3.

  PE1:

  Manual of PFD VPLS-10 L2

  VPN id 10

  Bridge-area 10

  neighbor 102.102.102.102 mpls encapsulation

  neighbor 103.103.103.103 encapsulating mpls non-decoupage of the horizon

  PE2:

  Manual of PFD VPLS-10 L2

  VPN id 10

  Bridge-area 10

  neighbor 101.101.101.101 mpls encapsulation

  PE3:

  interface GigabitEthernet0/0/2

  no ip address

  auto negotiation

  XConnect 101.101.101.101 10 mpls encapsulation

  Best regards

  Anne Isabelle

• NSX scalability in vCloud Air?

  Given that the NSX is managed and operated in the vCenter level, how can the same policies be preserved when migrating an Application (virtual machine or group of virtual machines) with said strategies to vCloud Air, since under blankets, vCloud Air infrastructure is managed by a different vCenter?

  More to come on this topic, as directed by our ads at beginning of the year.  Advanced network features include hypersegmentation, hybrid networks, L2VPN, etc. are coming soon.