01-23-2009 11:24 AM
Hello.
I am trying to configure a L2 pseudowire L2 that ejecutes inteworking in the following topology
the pswudowire is not active buy I don't find anything wrong in the configuration. I Have tried with in and ethernet interworking but the pseudowire alway remais as showed below
(CPE1 FRAME RELAY)---alcatel cloud inteworking----ATM---(PE1)--MPLS--(PEP2)-VLAN44--(CPE2 VLAN 44)
((PE1 Configuration- cisco 12410/PRP, disk0:c12kprp-k4p-mz.120-32.SY7.bin))
pseudowire-class inter-ether
encapsulation mpls
interworking ip
Current configuration : 275 bytes
!
interface ATM0/0.5 point-to-point
description ### Prueba interworking ATM-Ethernet ####
mtu 1500
no ip directed-broadcast
no atm enable-ilmi-trap
snmp trap link-status
pvc 0/10 l2transport
encapsulation aal5snap
xconnect 10.19.1.4 10 pw-class inter-ether
!
end
PEC12COL01#show mpls l2transport vc deta
Local interface: AT0/0.5 up, line protocol up, ATM AAL5 0/10 up
MPLS VC type is ATM AAL5, interworking type is IP
Destination address: 10.19.1.4, VC ID: 10, VC status: down
Create time: 01:06:05, last status change time: 00:00:34
Signaling protocol: LDP, peer 10.19.1.4:0 up
MPLS VC labels: local 297, remote unassigned
Group ID: local 0, remote unknown
MTU: local 1500, remote unknown
Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
packet totals: receive 0, send 0
byte totals: receive 0, send 0
packet drops: receive 0, seq error 0, send 0
=================================================================================
=================================================================================
((PE2 Configuration, CISCO7609, c7600s72033-adventerprisek9-mz.122-33.SRC2.bin))
pseudowire-class inter-ether
encapsulation mpls
interworking ip
!
PEP76CAN01#sh run int GigabitEthernet8/20
Building configuration...
Current configuration : 76 bytes
!
interface GigabitEthernet8/20
no ip address
speed 100
duplex full
end
!
interface GigabitEthernet8/20.10
encapsulation dot1Q 44
xconnect 10.19.1.16 10 pw-class inter-ether
end
PEP76CAN01#show mpls l2transport vc detail
Local interface: Gi8/20.10 up, line protocol up, Eth VLAN 44 up
MPLS VC type is Eth VLAN, interworking type is IP
Destination address: 10.19.1.16, VC ID: 10, VC status: down
Output interface: none, imposed label stack {}
Preferred path: not configured
Default path: no route
No adjacency
Create time: 00:53:11, last status change time: 00:29:31
Signaling protocol: LDP, peer unknown
Targeted Hello: 10.19.1.4(LDP Id) -> 10.19.1.16
Status TLV support (local/remote) : enabled/unknown (no remote binding)
Label/status state machine : local standby, AC-ready, LnuRnd
Last local dataplane status rcvd: no fault
Last local SSS circuit status rcvd: no fault
Last local SSS circuit status sent: not sent
Last local LDP TLV status sent: not sent
Last remote LDP TLV status rcvd: unknown (no remote binding)
MPLS VC labels: local 27, remote unassigned
Group ID: local 0, remote unknown
MTU: local 1500, remote unknown
Remote interface description:
Sequencing: receive disabled, send disabled
VC statistics:
packet totals: receive 0, send 0
byte totals: receive 0, send 0
packet drops: receive 0, seq error 0, send 0
PEP76CAN01#
01-23-2009 11:26 AM
CPE1 status of the DLCI
RP-MPLS-MAQT-CAN#SHO FRAME-relay PVC 17
PVC Statistics for interface Serial0/0:0 (Frame Relay DTE)
DLCI = 17, DLCI USAGE = LOCAL, PVC STATUS = INACTIVE, INTERFACE = Serial0/0:0.17
input pkts 0 output pkts 0 in bytes 0
out bytes 0 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0
30 second input rate 0 bits/sec, 0 packets/sec
30 second output rate 0 bits/sec, 0 packets/sec
pvc create time 00:30:32, last time pvc status changed 00:30:14
RP-MPLS-MAQT-CAN#SHOW IP INTER BRIE
Interface IP-Address OK? Method Status Protocol
Serial0/0:0.17 1.1.1.2 YES manual down down
02-14-2009 11:29 PM
Hello
Did you enabled directed ldp session between two edge Pe of the MPLS network which is a necessity for your l2 pseudowire to come up in mpls.
Tarun
02-15-2009 04:28 AM
Hello Pedro,
I notice that second PE doesn't see up the ATM PE
Signaling protocol: LDP, peer unknown
Targeted Hello: 10.19.1.4(LDP Id) -> 10.19.1.16
while the first PE says:
that it sees the peer up.
So verify ip routing for loopback interfaces the ip addresses have to be published in your IGP routing protocol and be also advertised by LDP to create external MPLS label (end-to-end LSP with destination remote loopback ip address).
Another possible issue is the ATM/FR interworking part, the FR DTE says its FR subif is down down and the pvc is inactive.
Verify if Alcatel network is correctly configured to create a PVC with that DLCI on the FR side and that arrives on the ATM PE node.
Hope to help
Giuseppe
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