VPLS - SPA-4XOC3-POS - Core Facing ?

Hi NetPros,
I know this topic has been discussed many times in forum and I could find useful information on specific hardware support in 7604.
However my requirement is bit strange (as it sounds to me). I have the below hardware:
7604 chassis
Sup 720-3B
SIP 400
SPA-4XOC3-POS
WS-X6516A-GBIC
As I gone through the forum, I understood the only constraint in 7604 with VPLS is that the core facing should be either SIP-400/SIP-600 with Gigi SPA, ES-10G and OSM.
1. But my problem now is I have SIP-400 with SPA-4XOC3-POS. Can this SPA be used on wan facing side for MPLS to work. To my understanding, core should only do label swapping and not mandatory that core facing should be Gigi. Though my typical core facing PE (NPEG1 now) side is only on Gigi, in this case of VPLS with 7604 I dont have Gigi and have to purchase so thought if SPA-4XOC3-POS works then atleast I go ahead and test VPLS. Procuring Gigi SPA will take some time due to business approvals.
2. If only Gigi SPA should be on the core facing side, then which Gigi SPA should be supported. Will 1 Gigi SPA support or I have to go for 10 Gigi SPA?
thanks
Arun

Hi Arun
--- > Can this SPA be used on wan facing side for MPLS to work. To my understanding, core should only do label swapping and not mandatory that core facing should be Gigi.
As per my understanding you what to configure VPLS on POS interface facing towards CE.
Or You want to use POS for Core facing i.e. internal network towards " P "
If towards "P" then yes it should work because xconnect vfi require L3 that is IP routing to reach other end and that can possible via static configuration or via BGP auto discovery.
and If towards CE then i don't think it work. Below is the specification.
I have not tested but if possible you can check weather you will get any command "xconnect vfi " under POS interface that connect towards CE.
As per my understanding you can terminate VPLS link using Access Port , Trunk Port , Dot1q Tunnel for CE.
just check !!
mpls label protocol ldp
mpls ldp logging neighbor-changes
mpls ldp router-id Loopback0
l2 vfi l2vpn manual
vpn id 1
neighbor 10.0.0.2 encapsulation mpls
neighbor 10.0.0.3 encapsulation mpls
neighbor 10.0.0.4 encapsulation mpls
int loopback 1
1.1.1.1 255.255.255.255
And try to configure xconnect vfi under POS interface . But i don't think because VPLS Provide L2 service .
Regards
Chetan Kumar
http://chetanress.blogspot.com

Similar Messages

Can we use SPA-4XOC3-POS-V2 on 7600-SIP-400

Hi,
We have ordered 2 x SPA-4XOC3-POS to use on 7604, we have received SPA-4XOC3-POS-V2 from our supplier.
I know that the SPA-4XOC3-POS-V2 are for the 12000, is there a way to use them on a 7600-SIP-400??
Any help is appreciated.
Thank you.
Hitch

This SPA is not supported on SIP-400 on 7600s. You need to get a NON V2 SPA.
Atif

A-VPLS core facing links hardware requirements.

v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
Hi,
I plan to deploy an Advanced VPLS (A-VPLS) to interconnect two Data Centers consisting in one VSS1440 at each site, which are going to be connected via two Gigabit DWDM links. According with the documentation, every Cat6500 box should include a SIP-400 for VPLS processing, but I still have the following question:
The Restrictions for L2VPN Advanced VPLS section of the L2VPN Advanced VPLS guide states the following:
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-fareast-language:EN-US;}
The L2VPN Advanced VPLS feature supports the following line cards and shared port adapters (SPAs):
- 7600-SIP-400 (core facing)
- Gigabit and 10-gigabit Ethernet SPAs (2X1GE-V1, 2X1GE-V2 and 1X10GE-V2 SPA)
According to this, should I include SIP-400 SPAs (models like 2X1GE-V1 or 2X1GE-V2) in every SIP-400 to connect the gigabitehternet DWDM VPLS core facing links?
Or can i take advantage of any existing gigabit ports included in the SUP720-10G for that purpose?
Regards in advance.

Hi,
I think as per documents, You can only accomplish A-VPLS by using SIP-400 with above SPA.

Can i use pos 622M as a pos 155M interface, module is SPA-1XOC12-POS

SPA-1XOC12-POS can use as a 155M sdh POS interface?
this is on 7609 sip 400,not a channelized oc 12 interface.
if i connect a 155 M sdh line into this 622M interface,it is single mode fiber. does this work?
thank you!

Hi flyjunli,
I'm quite sure this won't work. The framing won't fit if you connect different interfaces.
BR
Sebastian

My Spa booker POS printer configurations are screwed up since last update.

I have been usung spabooker for 2 years and have configured my CUPS printer a Star tsp 600 a number of times. I am using a mac with OSx 10.6.8. The printer margins were working fine on both of my computers until they upgraded to firefox 6.0. Then they both lost all the configurations and the receipt prints either out of alignment or I can set it to print very small.
The tech support at Star went through the CUPs again and we could not fix it. I remember once this happened before and I need to program the firefox sopftware. I cannot remember what i did last time though. Can you help?

Turns out it was a loose ethernet cable into the Basestation! Just cleaning house here.

Dot1q tunnel VPLS support

Hello Guys,
I am configuring a dot1q tunnel VPLS since it suited our need for the client's requirements. To my surprise the 48 port tx we are using on our 7600 doesn't support this
7609-PPE1(config-if)#switchport mode dot1q-tunnel
Command rejected: Gi2/4 doesn't support 802.1q tunneling.
IOS is s72033-pk9sv-mz.122-18.SXD5.bin
Hardware is 48 SFM-capable 48 port 10/100/1000mb RJ45 WS-X6548-GE-TX
For me to establish a good VPLS in dot1q (dot1q in dot1q) multipoint connection, what hardware with port density is available for this one?
I didn't have any problem with OSM modules, but we have to be practical with the port density.
Your insights will be greatly appreciated.
Thanks.

For vpls to work the core facing should be a osm module.Configure IP routing in the core so that the PE routers can reach each other via IP. Configure MPLS in the core so that a label switched path (LSP) exists between the PE routers.For more info refer
http://www.cisco.com/en/US/products/hw/routers/ps368/products_configuration_guide_chapter09186a00801e5c06.html#wp1338115.

Not able to get the alarms in DFM from 7609-S router in LMS 4.0

Hi Team,
We are facing some problem with DFM alerts for SPA-4XOC3-POS modules. Alerts are not getting generated for these modules. I can the the modules in Cisco View and inventry. Its operation status is also UP. Please provide help to find out the issue.
Attached show version & show module of problematric routers.
Regards
Dheeraj Gupta

The code below looks correct. Is that the expected behavior of your app?
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute">
<mx:Script>
<![CDATA[
public var ValueP2:Number = 0;
private var grossValue:Number = 0;
private var totalValue:Number = 0;
private var finalTotalP2:int = 0;
public function test():void {
if (Number(TextInput2.text) == 1 || Number(TextInput2.text) == 2)
ValueP2 = 1;
totalValue = grossValue + ValueP2;
else if (Number(TextInput2.text) == 3 || Number(TextInput2.text) == 4) {
ValueP2 = 5;
totalValue = grossValue + ValueP2;
else if (Number(TextInput2.text) == 5 || Number(TextInput2.text) == 6) {
ValueP2 = 9;
totalValue = grossValue + ValueP2;
trace("totalValue "+totalValue);
finalValueP2(totalValue);
public function finalValueP2(tVP2:int):int {
var tallyP2:int = 0;
if (tVP2 < 3)tallyP2 = 1;
if (tVP2 >= 3 && tVP2 <5)tallyP2 = 2;
if (tVP2 >= 5 && tVP2 <10)tallyP2 = 3;
finalTotalP2 = tallyP2 * 7;
trace("finalTotalP2 " +finalTotalP2);
return(finalTotalP2);
]]>
</mx:Script>
<mx:TextInput id="TextInput2" enter="test()"/>
</mx:Application>

STM1 Back-to-Back Between ASR 9006 and ASR 903

Dear Gents,
Seeking your usual support to aid me to connect STM1 Back-to-Back between ASR 9006 and ASR 903.
I have ASR 9006 comes with SPA-4XOC3-POS-V2 and SFP-OC3-MM using XR-A9K-PXK9-04.03 IOS-XR.
Also I have ASR 903 comes with A900-IMA4OS interface module with ONS-SI-155-SR-MM SFP using SASR903R1NPEK9-38S IOS-XE.
I'm using Multi Mode fiber cable between them and the interfaces never came UP UP.
Below the configuration i did to both sides.
ASR 903 configuration:
ASR903#sh run | sec contro
controller SONET 0/0/0
framing sdh
clock source internal
aug mapping au-4
au-4 1 pos
interfaces POS0/0/0.1
ip address 10.10.10.2 255.255.255.252
ASR 9006 configuration
ASR9006#sh running-config controller soNET 0/1/0/0
controller SONET0/1/0/0
framing sdh
clock source internal
interface POS0/1/0/0
ipv4 address 10.10.10.1 255.255.255.252
Thanks in advance.

I think your 900 is running in an oc12/stm4 mode (as you seem to subrate the sonet controller), so they have a speed mismatch already although it looks like you're using the right STM1 optic.
also one side you will want to have use clock from line while the other internal, otherwise you'll get a lot of clock slips.
cheers
xander

VPLS support on 10 gig 6704 module core

Hi All,
Does VPLS is supported ,if the core links are in 10 gig 6704 module MPLS enabled ?
Any assistance on this would be really appreciated .
Regards
Anantha Subramanian Natarajan

hi Jon!
Even core-facing SIP-400 supports VPLS.(starting from the SXH release)
http://www.cisco.com/en/US/docs/interfaces_modules/shared_port_adapters/configuration/6500series/76ovwsip.html#wp1062432
Regards,
Niranjan

VPLS on Same Line Card

Hi dear all
Can the ES+ line card be Edge-facing and Core-facing at the same time on RSP-7609-S like the below diagram ?
i know that there is restriction on IOS XR, but i can't find any thing on IOS.
i want to know that the below case support the VPLS or not?
we want to use MPLS/VPN and VPLS at same time.
i would be appreciated if give me the reference for that.
Thank you

Hi Amir,
yes ES+ can be both core and customer (edge) facing card at the same time (even if the 2 links are on the same LC); actually there are some cases where ES+ MUST be both core and customer facing such as H-VPLS with MPLS access.
In general for all VPLS flavours you need a ES+ card (or any other card performing label imposition such as SIP-400, SIP-600, ES20, OSM) facing the core. Then depending the type of access you want to configure you have a choice of customer facing LC. i.e: any PFC based LC for basic VPLS up to ES+ (or the other mentioned above) for H-VPLS with MPLS access.
You find this (inderectly documented) on this page:
http://www.cisco.com/en/US/docs/routers/7600/install_config/ES40_config_guide/es40_chap6.html#wp1463854
regards,
Riccardo

VPLS MTU requirement

Hi All,
We are planning to run VPLS over the DSL link and i think MTU cab be an issue in such scenario as the MTU size will depends uppon the DSL provider settings. So i am not sure how to acheive this solution in terms of MTU issues and also can some one please guide me how to calculate the required MTU for running VPLS in DSL access media ?
MTU on interface to CE ?
MTU on interface to the Core ?
Thanks in advance guys.
Sree

Hi Sree,
the rule for MPLS (hence for VPLS too) is to have the highest MTU you can configure on the core interfaces. Usually ISPs have nowaday 9000.
If this is not possible for VPLS you need to take into consideration the following for Max Frame Size:
Max Frame Size = Link Header + Tunnel label + VC label + Control Word +Transported L2 Header + Payload.
Link Header is the one of your DSL circuit (likely using ATM link header.. anyway it something you should know/ask your provider).
Tunnel label + VC label + Control Word = 12 Bytes (4 bytes per label + 4 bytes for control word which is optional as it sepends on underlying transport media and on vendor implementation... anyway you should consider it)
Transported L2 Header = it depends on what you transport. For Ethernet II encapsulation with dot1q consider 18 bytes (or 14 bytes if customer vlan id is not transported. This depends on implementations once again).
So in the worst scenario where you have CW and you transport customer vlan id you need at least 1530 Bytes + the DSL link header on the core facing interface.
On the customer facing interface I would leave the interface MTU you have (1500 if it is Ethernet - even though the actual value is higher as it considers the L2 link overhead already). Or else you need to change the MTU on every host.. not too handy.
Riccardo

VPLS on 6500

Hi
Please help me, I would like to setup VPLS on two routers (6504) with the following modules and Advanced-Enterprise version 15 IOS. Anybody knows whether this feature is supported or not. If not, what is my minimum requirement for supporting VPLS.
6504# show module
Mod Ports Card Type                              Model              Serial No.
1    2 Supervisor Engine 720 (Active)         WS-SUP720-3BXL     SAL134322F9
3   24 CEF720 24 port 1000mb SFP              WS-X6724-SFP       SAL1219PUZU
4   48 48-port 100FX SFP Ethernet Module      WS-X6148-FE-SFP    SAL1216N2QD
<<... output omitted ...>>
Mod Sub-Module                  Model              Serial       Hw     Status
1 Policy Feature Card 3       WS-F6K-PFC3BXL     SAL134325LA 1.11 Ok
1 MSFC3 Daughterboard         WS-SUP720          SAL13421LZN 4.0    Ok
3 Centralized Forwarding Card WS-F6700-CFC       SAL1218PC9H 4.0 Ok

Hi,
For VPLS, the access facing line card (where the CE will be connected) can be any LAN cards. But the core facing line card where label imposition/disposition happens should be a WAN card like ES, ES+, SIP/OSM etc.
Since it is a setup between 2 devices, you can try EoMPLS (port based) with this setup. You can enable xconnect on the port connecting to CE router.
-Nagendra

SIP-400 SPA-2X1GE

Does SPA interface (SPA-2X1GE) support DWDM SFP? What is maximum number of SPA-2x1GE in one SIP-400 module? Does OSM-4G and 7600-ES20 module support DWDM SFP. What is difference between those cards if we talk about this card as core-facing card, and which card is best solution for core-facing.

Cisco XR 12000 Series SPA Interface Processor 10G 12000-SIP-600 support DWDM.
SPA-2X1GE
SPA-1XOC12-ATM
SPA-8XCHT1/E1

VPLS problem

Hi dear all
Currently we are facing an issue in a VPLS network and I will appreciate your help if you know the solution, thanks in advance.
We have the following topology :
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:Arial;
mso-bidi-theme-font:minor-bidi;
mso-ansi-language:EN-US;
mso-fareast-language:EN-US;}
All routers (PA,PB,PC) have Sup32-8GE-3B without any extra line cards . We configure VPLS on all routers. All routers have the following running configuration . Also verifications show that everything is ok .
1.    Is it possible to configure VPLS on Sup32-GE-3B without any extra line cards?
2.    Why configuration has been done but :
         a.    There is not communication between 3 Cust-A sites (L2 connectivity).
         b.    The following error message displayed when add “IP MPLS” command for uplinks.
MPLS CONFIG on LAN NOT RECOMMENDED: Cross-connect is currently configured on interface vlans   and WAN interfaces are facing the MPLS core. By configuring MPLS on LAN interfaces, AToM on vlan interfaces may be non functional.
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:Arial;
mso-bidi-theme-font:minor-bidi;
mso-ansi-language:EN-US;
mso-fareast-language:EN-US;}
PA-7609#sh run
Building configuration...
Current configuration : 4030 bytes
! Last configuration change at 14:54:05 UTC Thu Jul 29 2010
! NVRAM config last updated at 14:07:27 UTC Thu Jul 29 2010
upgrade fpd auto
version 12.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
service counters max age 5
hostname PA-7609
boot-start-marker
boot system sup-bootdisk:c7600s3223-advipservicesk9-mz.122-33.SRB7.bin
boot-end-marker
enable secret 5 $1$FIyH$5AHHV2qA0noZemUJhZBCL0
no aaa new-model
platform vfi dot1q-transparency
ip subnet-zero
ip vrf forwarding
no ip domain-lookup
ipv6 mfib hardware-switching replication-mode ingress
vtp mode transparent
mls ip multicast flow-stat-timer 9
mls flow ip interface-full
no mls flow ipv6
no mls acl tcam share-global
mls cef error action reset
mpls label protocol ldp
spanning-tree mode pvst
spanning-tree extend system-id
system flowcontrol bus auto
diagnostic cns publish cisco.cns.device.diag_results
diagnostic cns subscribe cisco.cns.device.diag_commands
redundancy
mode rpr
main-cpu
auto-sync running-config
vlan internal allocation policy ascending
vlan dot1q tag native
vlan access-log ratelimit 2000
vlan 100
pseudowire-class mpls
encapsulation mpls
l2 router-id 10.1.1.1
l2 vfi VPLS1 autodiscovery
vpn id 100
interface Loopback1
ip address 10.1.1.1 255.255.255.255
interface GigabitEthernet5/1
no ip address
shutdown
interface GigabitEthernet5/2
no ip address
shutdown
interface GigabitEthernet5/3
no ip address
shutdown
interface GigabitEthernet5/4
no ip address
shutdown
interface GigabitEthernet5/5
no ip address
shutdown
interface GigabitEthernet5/6
no ip address
shutdown
interface GigabitEthernet5/7
no ip address
shutdown
interface GigabitEthernet5/8
no ip address
shutdown
interface GigabitEthernet5/9
no ip address
shutdown
interface GigabitEthernet6/1
ip address 192.168.0.1 255.255.255.252
mpls ip
interface GigabitEthernet6/2
ip address 172.16.0.1 255.255.255.252
mpls ip
interface GigabitEthernet6/3
ip address 192.168.1.18 255.255.255.252
mpls ip
interface GigabitEthernet6/3.200
encapsulation dot1Q 300
interface GigabitEthernet6/4
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 100
switchport mode trunk
interface GigabitEthernet6/5
no ip address
shutdown
interface GigabitEthernet6/6
no ip address
interface GigabitEthernet6/7
no ip address
interface GigabitEthernet6/8
no ip address
interface GigabitEthernet6/9
ip address 200.200.200.1 255.255.255.0
interface Vlan1
no ip address
shutdown
interface Vlan100
no ip address
xconnect vfi VPLS1
router ospf 1
log-adjacency-changes
network 10.1.1.0 0.0.0.255 area 0
network 172.16.0.0 0.0.0.255 area 0
network 192.168.0.0 0.0.0.255 area 0
router bgp 1
no bgp default ipv4-unicast
bgp log-neighbor-changes
bgp update-delay 1
neighbor 10.1.1.2 remote-as 1
neighbor 10.1.1.2 update-source Loopback1
neighbor 10.1.1.3 remote-as 1
neighbor 10.1.1.3 update-source Loopback1
address-family ipv4
no synchronization
no auto-summary
exit-address-family
address-family l2vpn vpls
neighbor 10.1.1.2 activate
neighbor 10.1.1.2 send-community extended
neighbor 10.1.1.3 activate
neighbor 10.1.1.3 send-community extended
exit-address-family
ip classless
no ip http server
no ip http secure-server
mpls ldp router-id Loopback1
bridge 1 protocol vlan-bridge
control-plane
line con 0
stopbits 1
line vty 0 4
session-timeout 60 output
privilege level 15
password 7 12485744532B4F
login
line vty 5 15
session-timeout 60 output
privilege level 15
password 7 12485744532B4F
login
line vty 16
privilege level 15
password 7 055A545C606C0D
login
ntp master 1
mac-address-table synchronize
no mac-address-table learning vlan 2 module 5
mac-address-table learning vlan 100 module 5
no mac-address-table learning vlan 2 module 6
mac-address-table learning vlan 100 module 6
End
PB-7609#sh run
Building configuration...
Current configuration : 3683 bytes
upgrade fpd auto
version 12.2
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
service counters max age 10
hostname PB-7609
boot-start-marker
boot system sup-bootdisk:c7600s3223-advipservicesk9-mz.122-33.SRB7.bin
boot-end-marker
enable secret 5 $1$1YCM$KJ9TC73PD.1v2x8jrVS3S/
no aaa new-model
ip subnet-zero
no ip domain-lookup
ipv6 mfib hardware-switching replication-mode ingress
mls ip multicast flow-stat-timer 9
mls flow ip interface-full
no mls flow ipv6
no mls acl tcam share-global
mls cef error action reset
mpls label protocol ldp
spanning-tree mode pvst
spanning-tree extend system-id
system flowcontrol bus auto
diagnostic cns publish cisco.cns.device.diag_results
diagnostic cns subscribe cisco.cns.device.diag_commands
redundancy
mode rpr
main-cpu
auto-sync running-config
vlan internal allocation policy ascending
vlan dot1q tag native
vlan access-log ratelimit 2000
pseudowire-class mpls
encapsulation mpls
l2 router-id 10.1.1.2
l2 vfi VPLS1 autodiscovery
vpn id 100
interface Loopback1
ip address 10.1.1.2 255.255.255.255
interface GigabitEthernet5/1
no ip address
shutdown
interface GigabitEthernet5/2
no ip address
shutdown
interface GigabitEthernet5/3
no ip address
shutdown
interface GigabitEthernet5/4
no ip address
shutdown
interface GigabitEthernet5/5
no ip address
shutdown
interface GigabitEthernet5/6
no ip address
shutdown
interface GigabitEthernet5/7
no ip address
shutdown
interface GigabitEthernet5/8
no ip address
shutdown
interface GigabitEthernet5/9
no ip address
shutdown
interface GigabitEthernet6/1
ip address 192.168.0.2 255.255.255.252
mpls ip
interface GigabitEthernet6/2
ip address 172.16.0.5 255.255.255.252
mpls ip
interface GigabitEthernet6/3
no ip address
shutdown
interface GigabitEthernet6/4
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 100
switchport mode trunk
l2protocol-tunnel cdp
l2protocol-tunnel stp
l2protocol-tunnel vtp
no cdp enable
spanning-tree bpdufilter enable
interface GigabitEthernet6/5
no ip address
shutdown
interface GigabitEthernet6/6
no ip address
shutdown
interface GigabitEthernet6/7
no ip address
interface GigabitEthernet6/8
no ip address
interface GigabitEthernet6/9
ip address 200.200.200.2 255.255.255.0
interface Vlan1
no ip address
shutdown
interface Vlan100
no ip address
xconnect vfi VPLS1
router ospf 1
log-adjacency-changes
network 10.1.1.0 0.0.0.255 area 0
network 172.16.0.0 0.0.0.255 area 0
network 192.168.0.0 0.0.0.255 area 0
router bgp 1
no bgp default ipv4-unicast
bgp log-neighbor-changes
bgp update-delay 1
neighbor 10.1.1.1 remote-as 1
neighbor 10.1.1.1 update-source Loopback1
neighbor 10.1.1.3 remote-as 1
neighbor 10.1.1.3 update-source Loopback1
address-family ipv4
no synchronization
no auto-summary
exit-address-family
address-family l2vpn vpls
neighbor 10.1.1.1 activate
neighbor 10.1.1.1 send-community extended
neighbor 10.1.1.3 activate
neighbor 10.1.1.3 send-community extended
exit-address-family
ip classless
no ip http server
no ip http secure-server
mpls ldp router-id Loopback1
control-plane
line con 0
stopbits 1
line vty 0 4
session-timeout 60 output
privilege level 15
password 7 12485744532B4F
login
line vty 5 15
session-timeout 60 output
privilege level 15
password 7 12485744532B4F
login
line vty 16
privilege level 15
password 7 1543595F450A68
login
mac-address-table synchronize
mac-address-table learning vlan 100 module 5
mac-address-table learning vlan 100 module 6
End
PC-7609#sh run
Building configuration...
Current configuration : 3896 bytes
upgrade fpd auto
version 12.2
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
service counters max age 10
hostname PC-7609
boot-start-marker
boot system sup-bootdisk:c7600s3223-advipservicesk9-mz.122-33.SRB7.bin
boot-end-marker
enable secret 5 $1$cL//$YpRw8OQfCv2vYXZIvORkU.
no aaa new-model
ip subnet-zero
no ip domain-lookup
ipv6 mfib hardware-switching replication-mode ingress
vtp mode transparent
mls ip multicast flow-stat-timer 9
mls flow ip interface-full
no mls flow ipv6
no mls acl tcam share-global
mls cef error action reset
mpls ldp explicit-null
mpls label protocol ldp
spanning-tree mode pvst
spanning-tree extend system-id
system flowcontrol bus auto
diagnostic cns publish cisco.cns.device.diag_results
diagnostic cns subscribe cisco.cns.device.diag_commands
redundancy
mode sso
main-cpu
auto-sync running-config
vlan internal allocation policy ascending
vlan dot1q tag native
vlan access-log ratelimit 2000
vlan 100
pseudowire-class mpls
encapsulation mpls
l2 router-id 10.1.1.3
l2 vfi VPLS1 autodiscovery
vpn id 100
interface Loopback1
ip address 10.1.1.3 255.255.255.255
interface GigabitEthernet5/1
no ip address
shutdown
interface GigabitEthernet5/2
no ip address
shutdown
interface GigabitEthernet5/3
no ip address
shutdown
interface GigabitEthernet5/4
no ip address
shutdown
interface GigabitEthernet5/5
no ip address
shutdown
interface GigabitEthernet5/6
no ip address
shutdown
interface GigabitEthernet5/7
no ip address
shutdown
interface GigabitEthernet5/8
no ip address
shutdown
interface GigabitEthernet5/9
no ip address
shutdown
interface GigabitEthernet6/1
ip address 172.16.0.2 255.255.255.252
mpls ip
interface GigabitEthernet6/2
ip address 172.16.0.6 255.255.255.252
mpls ip
interface GigabitEthernet6/3
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 100
switchport mode trunk
l2protocol-tunnel cdp
l2protocol-tunnel stp
l2protocol-tunnel vtp
no cdp enable
spanning-tree bpdufilter enable
interface GigabitEthernet6/4
ip address 192.168.1.9 255.255.255.252
mpls ip
interface GigabitEthernet6/5
no ip address
no cdp enable
interface GigabitEthernet6/6
no ip address
interface GigabitEthernet6/7
no ip address
interface GigabitEthernet6/8
no ip address
interface GigabitEthernet6/9
ip address 200.200.200.3 255.255.255.0
speed 10
duplex half
interface Vlan1
no ip address
shutdown
interface Vlan100
no ip address
xconnect vfi VPLS1
router ospf 1
log-adjacency-changes
network 10.1.1.0 0.0.0.255 area 0
network 172.16.0.0 0.0.0.255 area 0
network 192.168.0.0 0.0.0.255 area 0
router bgp 1
no bgp default ipv4-unicast
bgp log-neighbor-changes
bgp update-delay 1
neighbor 10.1.1.1 remote-as 1
neighbor 10.1.1.1 update-source Loopback1
neighbor 10.1.1.2 remote-as 1
neighbor 10.1.1.2 update-source Loopback1
address-family ipv4
no synchronization
no auto-summary
exit-address-family
address-family l2vpn vpls
neighbor 10.1.1.1 activate
neighbor 10.1.1.1 send-community extended
neighbor 10.1.1.2 activate
neighbor 10.1.1.2 send-community extended
exit-address-family
ip classless
no ip http server
no ip http secure-server
mpls ldp router-id Loopback1
bridge 1 protocol vlan-bridge
control-plane
line con 0
stopbits 1
line vty 0 4
session-timeout 60 output
privilege level 15
password 7 12485744532B4F
login
line vty 5 15
session-timeout 60 output
privilege level 15
password 7 12485744532B4F
login
line vty 16
privilege level 15
password 7 075E731F0F295A
login
mac-address-table synchronize
no mac-address-table learning vlan 4
mac-address-table learning vlan 100 module 5
no mac-address-table learning vlan 4 module 6
mac-address-table learning vlan 100 module 6
end
Verification
PA-7609#sh mpls ldp neighbor
    Peer LDP Ident: 200.200.200.2:0; Local LDP Ident 200.200.200.1:0
        TCP connection: 200.200.200.2.11362 - 200.200.200.1.646
        State: Oper; Msgs sent/rcvd: 136/137; Downstream
        Up time: 01:40:27
        LDP discovery sources:
          GigabitEthernet6/1, Src IP addr: 192.168.0.2
          Targeted Hello 10.1.1.1 -> 10.1.1.2, active, passive
        Addresses bound to peer LDP Ident:
         200.200.200.2   192.168.0.2     172.16.0.5      10.1.1.2
    Peer LDP Ident: 200.200.200.3:0; Local LDP Ident 200.200.200.1:0
        TCP connection: 200.200.200.3.64421 - 200.200.200.1.646
        State: Oper; Msgs sent/rcvd: 137/130; Downstream
        Up time: 01:40:26
        LDP discovery sources:
          Targeted Hello 10.1.1.1 -> 10.1.1.3, active, passive
          GigabitEthernet6/2, Src IP addr: 172.16.0.2
        Addresses bound to peer LDP Ident:
          200.200.200.3   172.16.0.2      172.16.0.6      10.1.1.3
PA-7609#sh ip bgp l2vpn vpls all
BGP table version is 18, local router ID is 10.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
   Network          Next Hop            Metric LocPrf Weight Path
Route Distinguisher: 1:100
*> 1:100:10.1.1.1/96                     0.0.0.0                            32768 ?
*>i1:100:10.1.1.2/96                     10.1.1.2                 0    100      0 ?
*>i1:100:10.1.1.3/96                     10.1.1.3                 0    100      0 ?
PA-7609#show xconnect all
Legend: XC ST=Xconnect State, S1=Segment1 State, S2=Segment2 State
UP=Up, DN=Down, AD=Admin Down, IA=Inactive, NH=No Hardware
XC ST Segment 1                         S1 Segment 2                         S2
------+---------------------------------+--+---------------------------------+--
UP     vfi VPLS1                        UP mpls 10.1.1.2:100                 UP
UP     vfi VPLS1                        UP mpls 10.1.1.3:100                 UP
UP     ac   Vl100 100(Eth VLAN)          UP vfi VPLS1                    UP
PA-7609#sh mac-address-table dynamic
Legend: * - primary entry
        age - seconds since last seen
        n/a - not available
vlan   mac address     type    learn     age              ports
------+----------------+--------+-----+----------+--------------------------
No entries present.

Hi,
If you need to run VPLS then you core facing card need to do imposition/disposition. I doubt if the sup32 gig ports can do so. For VPLS to work on 7600 any one of following card is needed.
PWAN2 (OSM)
ES+ (ES40)
ES20
SIP-400
SIP-600
If you have say a lan card like 6748 or 6724 towards core and try to bring up VPLS, it will allow you to provision but VC might not come up. The other message you are getting is normal when you try to enable mpls on a lan card. I think this can be safely ignored.
Thanks,
Madhu

ATM-SPA

Hello all,
I am trying to define a ubr+ service class on PVC for an ATM -SPA (4xOC3 ATM SPA ) but I cannot, I can only implement ubr.
According to this link I read that ubr+ is only supported on SVCs. (http://www.cisco.com/en/US/products/hw/routers/ps368/module_installation_and_configuration_guides_chapter09186a008021ff16.html)
The IOS of my 7600 device is 12.2 (33)SRE2.
What I would like to know is there is any other IOS that supports ubr+ under PVCs.
Thank you very much for your time and effort.
Best regards
Sofia

Just configure UBR and all will be fine.
UBR+ is interesting only in the transport network, not the endpoint.
The reason is supported in SVC is just because the paramenter are communicated at VC setup time, Since PVC has no setup, you may be under the impression that UBR is not supported.

VPLS - SPA-4XOC3-POS - Core Facing ?

Similar Messages

Maybe you are looking for