[c-nsp] ASR9k to Me3600x VPLS
Jason Lixfeld
jason at lixfeld.ca
Sun Mar 10 20:17:02 EDT 2013
Waris,
Is this an IOS issue or an XR issue? I feel I may be running up against the same issue when I begin to deploy this in the near future.
--
Sent from my mobile device
On 2013-03-10, at 8:05 PM, "Waris Sagheer (waris)" <waris at cisco.com> wrote:
> Hi Pashem,
> You are right there is an issue with the control word between the two platforms and this issue is in the process of getting fixed. I'll get back to you with the date of fixed image. BTW can you try to flap the interface?
>
>
> Best Regards,
>
> [http://www.cisco.com/web/europe/images/email/signature/horizontal06.jpg]
>
> Waris Sagheer
> Technical Marketing Manager
> Service Provider Access Group
> waris at cisco.com<mailto:waris at cisco.com>
> Phone: +1 408 853 6682
> Mobile: +1 408 835 1389
>
> CCIE - 19901
>
>
> <http://www.cisco.com/>
>
>
>
> [Think before you print.] Think before you print.
>
> This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.
>
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>
>
> From: Pshem Kowalczyk <pshem.k at gmail.com<mailto:pshem.k at gmail.com>>
> Date: Sunday, March 10, 2013 2:12 PM
> To: adam vitkovsky <adam.vitkovsky at swan.sk<mailto:adam.vitkovsky at swan.sk>>
> Cc: "cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>" <cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>>
> Subject: Re: [c-nsp] ASR9k to Me3600x VPLS
>
> Hi,
>
> The discovery works fine - we have the prefix length specified on the
> Me3600x, both devices know that they have to build the LSP it's just
> not coming up and I think it's not coming up because the control word
> can not be negotiated properly.
>
> kind regards
> Pshem
>
>
> On 11 March 2013 10:38, Adam Vitkovsky <adam.vitkovsky at swan.sk<mailto:adam.vitkovsky at swan.sk>> wrote:
> Hi Pshem,
> Isn't the "prefix-length-size 2" the problem?
>
> From Cisco web page:
>
> Interoperability Between Cisco IOS XR and Cisco IOS on VPLS LDP Signaling
>
> The Cisco IOS Software encodes the NLRI length in the fist byte in bits
> format in the BGP Update message. However, the Cisco IOS XR Software
> interprets the NLRI length in 2 bytes. Therefore, when the BGP neighbor with
> VPLS-VPWS address family is configured between the IOS and the IOS XR, NLRI
> mismatch can happen, leading to flapping between neighbors. To avoid this
> conflict, IOS supports prefix-length-size 2 command that needs to be enabled
> for IOS to work with IOS XR. When the prefix-length-size 2 command is
> configured in IOS, the NLRI length is encoded in bytes. This configuration
> is mandatory for IOS to work with IOS XR.
>
> This is a sample IOS configuration with the prefix-length-size 2 command:
>
> router bgp 1
> address-family l2vpn vpls
> neighbor 5.5.5.2 activate
> neighbor 5.5.5.2 prefix-length-size 2 --------> NLRI length = 2 bytes
> exit-address-family
>
>
> adam
>
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net<mailto:cisco-nsp-bounces at puck.nether.net>
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Pshem Kowalczyk
> Sent: Sunday, March 10, 2013 10:03 PM
> To: cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
> Subject: [c-nsp] ASR9k to Me3600x VPLS
>
> Hi,
>
> I hope that collective knowledge can help me here.
> We're trying to build a simple VPLS between an ASR9k (IOS XR 4.2.3) and
> ME3600x (IOS 15.3(1)S) using BGP autodiscovery and LDP for signaling.
>
> THe VPLS is not coming up,as the pseudowires are not up, I've located the
> issue to the control word - the 9k runs with 'disabled' whilst the ME3600x
> runs on autosense and that is failing as it results on 'control word on':
>
> ME3600X:
>
> Local interface: VFI VFI-1-20H731 vfi up
> Interworking type is Ethernet
> Destination address: 10.123.110.1, VC ID: 2105, VC status: down
> Last error: Local peer access circuit is down
> Output interface: none, imposed label stack {}
> Preferred path: not configured
> Default path: no route
> No adjacency
> Create time: 16:02:58, last status change time: 12w2d
> Last label FSM state change time: 16:02:58
> Signaling protocol: LDP, peer 10.123.110.1:0 up
> Targeted Hello: 10.123.143.1(LDP Id) -> 10.123.110.1, LDP is DOWN, no
> binding
> Status TLV support (local/remote) : enabled/None (no remote binding)
> LDP route watch : enabled
> Label/status state machine : local ready, LruRnd
> 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: Not sent
> Last local PW i/f circ status rcvd: No fault
> Last local LDP TLV status sent: No fault
> Last remote LDP TLV status rcvd: None (no remote binding)
> Last remote LDP ADJ status rcvd: None (no remote binding)
> MPLS VC labels: local 212, remote unassigned
> AGI: type 1, len 8, 000A 4454 0000 0839
> Local AII: type 1, len 4, 0A7B 8F01 (10.123.143.1)
> Remote AII: type 1, len 4, 0A7B 6E01 (10.123.110.1)
> Group ID: local n/a, remote unknown
> MTU: local 9000, remote unknown
> Remote interface description:
> Sequencing: receive disabled, send disabled
> Control Word: On (configured: autosense) <=========================
> Dataplane:
> SSM segment/switch IDs: 0/0 (used), PWID: 31
> VC statistics:
> transit packet totals: receive 0, send 0
> transit byte totals: receive 0, send 0
>
> ASR9k:
>
> (sh l2vpn bridge-domain)
>
> List of VFIs:
> VFI VFI-1-20H731 (up)
> VPN-ID: 2105, Auto Discovery: BGP, state is Provisioned (Service
> Connected)
> Route Distinguisher: 17492:10012105
> Import Route Targets:
> 17492:2105
> Export Route Targets:
> 17492:2105
> Signaling protocol: LDP
> AS Number: 17492
> VPLS-ID: 17492:2105
> L2VPN Router ID: 10.123.110.1
> PW: neighbor 10.123.143.1, PW ID 17492:2105, state is down ( all ready
> ) (Segment-down)
> PW class not set, XC ID 0xc000001e
> Encapsulation MPLS, Auto-discovered (BGP), protocol LDP
> Source address 10.123.110.1
> PW type Ethernet, control word disabled, interworking none
> PW backup disable delay 0 sec
>
> Sequencing not set
>
> PW Status TLV in use
> MPLS Local Remote
> ------------ ------------------------------
> -------------------------
> Label 16015 212
> BGP Peer ID 10.123.110.1 10.123.143.1
> LDP ID 10.123.110.1 10.123.143.1
> AII 10.123.110.1 10.123.143.1
> AGI 17492:2105 17492:2105
> Group ID 0x5 0x0
> Interface VFI-1-20H731 unknown
> MTU 9000 9000
> Control word disabled enabled
> PW type Ethernet Ethernet
> VCCV CV type 0x2 0x12
> (LSP ping verification) (LSP ping
> verification)
> VCCV CC type 0x6 0x3
> (control word)
> (router alert label) (router alert label)
> (TTL expiry)
> ------------ ------------------------------
> -------------------------
> Incoming Status (PW Status TLV):
> Status code: 0x0 (Up) in Notification message
> MIB cpwVcIndex: 3221225502
> Create time: 07/03/2013 17:19:14 (16:04:16 ago)
> Last time status changed: 07/03/2013 17:19:30 (16:03:59 ago)
> MAC withdraw message: send 0 receive 0
> Error: illegal control word <======================
> Static MAC addresses:
> DHCPv4 snooping: disabled
> IGMP Snooping profile: none
> VFI Statistics:
> drops: illegal VLAN 0, illegal length 0
>
>
> Does anyone have it going between the 9k and ME3600x?
>
> kind regards
> Pshem
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net<mailto:cisco-nsp at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
> _______________________________________________
> 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