12-08-2014 02:07 AM - edited 03-05-2019 12:18 AM
Hi,
I have a problem when creating xconnect from CRS router to 7606, the xconnect status always unresolved. The CRS and 7606 is directly
connected and here is the configuration :
CRS Configuration
l2vpn
pw-class test1
encapsulation mpls
transport-mode vlan
!
!
xconnect group TESTXCONNECT
p2p VLAN123_TESTXCONNECT
interface GigabitEthernet0/0/2/7.123
neighbor 1.1.1.105 pw-id 123
pw-class test1
!
interworking ethernet
!
interface GigabitEthernet0/0/2/7.123
mtu 1518
dot1q vlan 123
#sh int gigabitEthernet 0/0/2/7.123
Mon Dec 8 15:45:09.977 WIB
GigabitEthernet0/0/2/7.123 is up, line protocol is up
Interface state transitions: 1
Hardware is VLAN sub-interface(s), address is ccef.6f06.3021
Internet address is Unknown
MTU 1518 bytes, BW 100000 Kbit (Max: 100000 Kbit)
reliability 255/255, txload 0/255, rxload 0/255
Encapsulation 802.1Q Virtual LAN, VLAN Id 123, loopback not set,
ARP type ARPA, ARP timeout 04:00:00
Last input never, output never
Last clearing of "show interface" counters never
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
Received 0 broadcast packets, 0 multicast packets
0 packets output, 0 bytes, 0 total output drops
Output 0 broadcast packets, 0 multicast packets
7606 Configuration
sh run int gigabitEthernet 1/43.123
Building configuration...
Current configuration : 114 bytes
!
interface GigabitEthernet1/43.123
encapsulation dot1Q 123
xconnect 1.1.1.223 123 encapsulation mpls
end
Verification
7606#show mpls l2transport vc 123
Local intf Local circuit Dest address VC ID Status
------------- -------------------------- --------------- ---------- ----------
Gi1/43.123 Eth VLAN 123 1.1.1.223 123 DOWN
7606#traceroute mpls ipv4 1.1.1.105/32 source 1.1.1.223
Mon Dec 8 15:20:56.531 WIB
Tracing MPLS Label Switched Path to 1.1.1.105/32, timeout is 2 seconds
Codes: '!' - success, 'Q' - request not sent, '.' - timeout,
'L' - labeled output interface, 'B' - unlabeled output interface,
'D' - DS Map mismatch, 'F' - no FEC mapping, 'f' - FEC mismatch,
'M' - malformed request, 'm' - unsupported tlvs, 'N' - no rx label,
'P' - no rx intf label prot, 'p' - premature termination of LSP,
'R' - transit router, 'I' - unknown upstream index,
'X' - unknown return code, 'x' - return code 0
Type escape sequence to abort.
0 1.1.1.162 MRU 9000 [Labels: implicit-null Exp: 0]
! 1 1.1.1.161 4 ms
CRS#ping mpls ipv4 1.1.1.105/32 source 1.1.1.223
Mon Dec 8 15:21:26.703 WIB
Sending 5, 100-byte MPLS Echos to 1.1.1.105/32,
timeout is 2 seconds, send interval is 0 msec:
Codes: '!' - success, 'Q' - request not sent, '.' - timeout,
'L' - labeled output interface, 'B' - unlabeled output interface,
'D' - DS Map mismatch, 'F' - no FEC mapping, 'f' - FEC mismatch,
'M' - malformed request, 'm' - unsupported tlvs, 'N' - no rx label,
'P' - no rx intf label prot, 'p' - premature termination of LSP,
'R' - transit router, 'I' - unknown upstream index,
'X' - unknown return code, 'x' - return code 0
Type escape sequence to abort.
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 3/4/5 ms
CRS#show l2vpn xconnect
Mon Dec 8 15:21:48.247 WIB
Legend: ST = State, UP = Up, DN = Down, AD = Admin Down, UR = Unresolved,
SB = Standby, SR = Standby Ready
XConnect Segment 1 Segment 2
Group Name ST Description ST Description ST
------------------------ ------------------------- -------------------------
TESTXCONNECT
VLAN123_TESTXCONNECT
UR Gi0/0/2/7.123 UR 1.1.1.105 123 UR
--------------------------------------------------------------------------------
CRS#show l2vpn xconnect detail
Mon Dec 8 15:22:11.088 WIB
Group TESTXCONNECT, XC VLAN123_TESTXCONNECT, state is unresolved; Interworking Ethernet
Not provisioned reason(s):
AC I/F not ready
AC: GigabitEthernet0/0/2/7.123, state is unresolved
PW: neighbor 1.1.1.105, PW ID 123, state is unresolved
any idea why the xconnect status is showing unresolved?
12-08-2014 10:30 PM
this case is solved, you will get unresolved status if you didn't add l2transport command in the interface, hopefully this post can help others who have same problem like me.
interface GigabitEthernet0/0/2/7.123 l2transport
mtu 1518
dot1q vlan 123
02-28-2018 08:55 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide