[c-nsp] ASR901 to ME3600X xconnect
Pshem Kowalczyk
pshem.k at gmail.com
Thu Feb 28 19:40:27 EST 2013
Hi,
I'm already setting the MTU on the xconnect itself. The device doesn't
seem to support changing the interface MTU:
asr901A(config-if)#int gi0/0
asr901A(config-if)#mtu 1500
% Interface GigabitEthernet0/0 does not support user settable mtu.
but this works fine:
service instance 1 ethernet
encapsulation dot1q 17
rewrite ingress tag pop 1 symmetric
xconnect 10.123.29.1 4321 encapsulation mpls
mtu 1500
if I don't set the mtu to 1500 then on the ME3600x I get an error
message about MTU.
kind regards
Pshem
On 1 March 2013 12:55, Sigurbjörn Birkir Lárusson
<sigurbjornl at vodafone.is> wrote:
> Default MTU off the xconnect on the 901 is 9216, could that be your
> problem? XConnect won't come up with non-matching MTUs
>
> Kind regards,
> Sibbi
>
> On 28.2.2013 21:34, "Pshem Kowalczyk" <pshem.k at gmail.com> wrote:
>
>>Hi,
>>
>>I'm testing an asr901. We're looking at using for l2vpn termination.
>>For some reason the xconnect refuses to stand up between asr901 and
>>me3600x. Similar setup between two 3600x works fine.
>>
>>Relevant config on the asr901:
>>
>>!
>>hostname asr901A
>>!
>>
>>boot system flash:/asr901-universalk9-mz.152-2.SNH1.bin
>>
>>
>>
>>mpls label protocol ldp
>>mpls ldp discovery targeted-hello accept
>>mpls traffic-eng tunnels
>>bridge-domain 2
>>
>>l2 router-id 10.123.129.3
>>!
>>interface Loopback0
>> ip address 10.123.129.3 255.255.255.255
>>!
>>interface Tunnel3000
>> ip unnumbered Loopback0
>> mpls ip
>> tunnel mode mpls traffic-eng
>> tunnel destination 10.123.129.1
>> tunnel mpls traffic-eng autoroute announce
>> tunnel mpls traffic-eng path-option 1 dynamic
>> tunnel mpls traffic-eng record-route
>> tunnel mpls traffic-eng fast-reroute
>>!
>>interface GigabitEthernet0/0
>> duplex full
>> no negotiation auto
>> service instance 1 ethernet
>> encapsulation dot1q 17
>> rewrite ingress tag pop 1 symmetric
>> xconnect 10.123.29.1 4321 encapsulation mpls
>> mtu 1500
>> !
>>!
>>interface Vlan2
>> mtu 9216
>> description to me3600x
>> ip address 10.123.29.6 255.255.255.252
>> ip router isis vc-core
>> mpls traffic-eng tunnels
>> clns mtu 9083
>> isis network point-to-point
>> isis metric 10
>>!
>>router isis vc-core
>> net 49.0001.0101.2312.9003.00
>> is-type level-2-only
>> ispf level-2
>> metric-style wide
>> set-overload-bit on-startup wait-for-bgp
>> spf-interval 5 50 200
>> prc-interval 5 50 200
>> lsp-gen-interval 5 50 200
>> log-adjacency-changes
>> passive-interface default
>> no passive-interface Vlan2
>> mpls traffic-eng router-id Loopback0
>> mpls traffic-eng level-2
>>
>>
>>on the ME3600X the xconnect looks like this:
>>
>>interface GigabitEthernet0/11
>> description not in use
>> switchport trunk allowed vlan none
>> switchport mode trunk
>> mtu 9100
>> service-policy output PM-INT-1G-OUT
>> service instance 17 ethernet
>> encapsulation dot1q 4094
>> rewrite ingress tag pop 1 symmetric
>> xconnect 10.123.29.3 4321 encapsulation mpls
>> mtu 1500
>>
>>I can see the ISIS and LDP up between asr901 and me3600x:
>>
>>asr901A#sh mpls ldp neighbor
>> Peer LDP Ident: 10.123.129.1:0; Local LDP Ident 10.123.129.3:0
>> TCP connection: 10.123.129.1.646 - 10.123.129.3.26629
>> State: Oper; Msgs sent/rcvd: 1207/1201; Downstream
>> Up time: 17:22:15
>> LDP discovery sources:
>> Targeted Hello 10.123.129.3 -> 10.123.129.1, active, passive
>> Targeted Hello 10.123.129.3 -> 10.123.29.1, active
>> Addresses bound to peer LDP Ident:
>> 10.123.129.1 10.123.29.5 10.123.29.1
>>
>>asr901A#sh isis neighbors
>>
>>Tag vc-core:
>>System Id Type Interface IP Address State Holdtime Circuit Id
>>accr01cgr L2 Vl2 10.123.29.5 UP 24 01
>>
>>
>>Yet the actual vc doesn't come up:
>>
>>asr901A#sh mpls l2transport vc detail
>>Local interface: Gi0/0 up, line protocol up, Eth VLAN 17 up
>> Destination address: 10.123.29.1, VC ID: 4321, 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: 00:17:34, last status change time: 00:13:54
>> Signaling protocol: LDP, peer 10.123.129.1:0 up
>> Targeted Hello: 10.123.129.3(LDP Id) -> 10.123.29.1, LDP is DOWN, no
>>binding
>> Status TLV support (local/remote) : enabled/None (no remote binding)
>> LDP route watch : disabled
>> 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 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 16, remote unassigned
>> Group ID: local 0, remote unknown
>> MTU: local 1500, remote unknown
>> Remote interface description:
>> Sequencing: receive disabled, send disabled
>> Control Word: On (configured: autosense)
>> Dataplane:
>> SSM segment/switch IDs: 0/0 (used), PWID: 2
>> 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
>>
>>The error 'Local peer access circuit is down' is all I get on the 901,
>>on the me3600x I get:
>>accr01cgr#sh mpls l2transport vc 4321 detail
>>Local interface: Gi0/11 up, line protocol up, Eth VLAN 4094 down
>> Destination address: 10.123.29.3, VC ID: 4321, 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: 17:49:18, last status change time: 1w3d
>> Last label FSM state change time: 17:06:57
>> Signaling protocol: LDP, peer unknown
>> Targeted Hello: 10.123.129.1(LDP Id) -> 10.123.29.3, LDP is DOWN, no
>>binding
>> Status TLV support (local/remote) : enabled/None (no remote binding)
>> LDP route watch : enabled
>> Label/status state machine : local standby, AC-ready, LnuRnd
>> 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 status
>> Last remote LDP TLV status rcvd: None (no remote binding)
>> Last remote LDP ADJ status rcvd: None (no remote binding)
>> MPLS VC labels: local 21, remote unassigned
>> Group ID: local 0, remote unknown
>> MTU: local 1500, remote unknown
>> Remote interface description:
>> Sequencing: receive disabled, send disabled
>> Control Word: On (configured: autosense)
>> Dataplane:
>> SSM segment/switch IDs: 0/0 (used), PWID: 6
>> 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
>>
>>Ethernet VLAN is down and the same error message 'Local peer access
>>circuit is down' shows up.
>>
>>Debug on the ASR901 reveals the following:
>>*Mar 1 04:02:29.779: AToM[10.123.29.1, 4321]: Receive status update
>>*Mar 1 04:02:29.779: AToM[10.123.29.1, 4321]: . Receive AC
>>STATUS(DOWN AC(rx/tx faults))
>>*Mar 1 04:02:29.779: AToM[10.123.29.1, 4321]: .. AC status DOWN
>>AC(rx/tx faults)
>>*Mar 1 04:02:29.779: AToM[10.123.29.1, 4321]: ... Local peer access
>>circuit is down
>>*Mar 1 04:02:29.779: AToM[10.123.29.1, 4321]: .... S:Evt local down in
>>LndRnd
>>*Mar 1 04:02:29.779: AToM[10.123.29.1, 4321]: ..... NMS: VC oper state:
>>DOWN
>>*Mar 1 04:02:29.783: AToM[10.123.29.1, 4321]: ..... NMS: err
>>codes: loc-ac-rx-err
>>*Mar 1 04:02:29.783: AToM[10.123.29.1, 4321]: ..... NMS:
>>: + loc-ac-tx-err
>>*Mar 1 04:02:29.783: AToM[10.123.29.1, 4321]: ..... SYSLOG: VC is
>>DOWN, Loc AC Err
>>*Mar 1 04:02:29.783: AToM[10.123.29.1, 4321]: ... Local ready
>>*Mar 1 04:02:29.783: AToM[10.123.29.1, 4321]: ... Local service is
>>ready; send a label
>>
>>I have no idea why I get those errors on the AC.
>>Any hints will be greatly appreciated.
>>
>>kind regards
>>Pshem
>>_______________________________________________
>>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