No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FAQ-Can VPLS of the V5 Platform Interconnect with VPLS of the V3 Platform

Publication Date:  2012-07-27 Views:  40 Downloads:  0
Issue Description
Q:
A carrier uses the MA5200Gs to deliver point-to-multipoint VPLS services on the V3 platform. An MA5200G needs to interconnect with other MA5200Gs in the same VPN instance. To achieve this feature, you need to repeatedly run the mpls-vc peer-address vc-id command on the MA5200G. That is, different VCs are used for PE-PE interconnections in a VPN instance.
The ME60s in a VPN instance on the V5 platform use the same VSI for interconnection. If both MA5200Gs on the V3 platform and ME60s on the V5 platform are used to deliver VPLS services, they may encounter a problem of matching between VCs and VSIs. Therefore, they cannot deliver point-to-multipoint services. In addition, a VPN instance cannot be configured with multiple VSIs. Thus, the ME60s cannot interconnect with the ME60s.
If devices of the same platform version are used in the carrier network, no preceding problems exist. 
 
Alarm Information
Null
Handling Process
A:
To achieve interconnection between the ME60s on the V5 platform and the MA5200Gs on the V3 platforms, you can run dedicated commands the ME60. The testing environment is shown as follows:
1. Verify the networking network
Establish interconnections between MA5200G-1 and the ME60 and between MA5200G-1 and MA5200G-2 respectively.
2. Configurations
Configure the ME60 as follows:
Create a VSI.
vsi for_52 static
pwsignal ldp
vsi-id 4094 //Specify a VSI ID.
peer 60.30.0.1 negotiation-vc-id 4095 //Configure the same VSI ID of MA5200G-1.
Bind the VSI to an interface.
[ME60-10-GigabitEthernet8/0/3.1]dis this
#
interface GigabitEthernet8/0/3.1
vlan-type dot1q 10
l2 binding vsi for_52
#
return
3. Configure MA5200G-1 (version 2332).
Configure the upstream port connecting the P or PE device.
[For_z64650-Ethernet7/1/8]dis this
#
interface Ethernet7/1/8
undo shutdown
ip address 192.168.12.10 255.255.255.252
isis enable 1
mpls
mpls ldp
Create an LDP.
[For_z64650-mpls-ldp-remote0]dis this
#
mpls ldp
remote-peer 0
remote-ip 60.10.0.1 //Create a remote LDP regardless of a direct connection or not; otherwise, the VSI cannot be Up.
#
Create a VSI.
[For_z64650-vsi-for_52]dis this
#
l2vpn vpn-instance for_52
mpls-vc 192.168.62.4 4096 //Establish the MPLS connection with MA5200G-2.
mpls-vc 60.10.0.1 4095 //Establish the MPLS connection with the ME60.
#
return
Bind the VSI to an interface.
[For_z64650-Ethernet1/1/15.1]dis this
#
interface Ethernet1/1/15.1
user-vlan 10
undo shutdown
bas
access-type l2vpn for_52
#
return
4. Configure MA5200G (version 2332). Configurations are similar to that of MA5200G-1. 
 
Root Cause
Null
Suggestions
Null

END