- Does RouterOS response appropriately to the
ping mpls pseudowireorping mpls ipv4commands from a Cisco?
When testing this I get timeouts from the Cisco side even through the VC is up;
Mikrotik - Loopback Bridge - 10.0.2.14/32
Cisco - Loopback0 - 10.0.2.1/32
Link network - 10.0.2.32/30
Cisco side - 10.0.2.33
Mikrotik side - 10.0.2.34
OSPF is used between the two.
Mikrotik Side:
/interface vpls monitor 0
remote-label: 26
local-label: 45
remote-status:
transport: 10.0.2.1/32
transport-nexthop: 10.0.2.33
imposed-labels: 26
Cisco Side:
show mpls l2transport vc 1307 det
Local interface: Vl1307 up, line protocol up, Eth VLAN 1307 up
Interworking type is Ethernet
Destination address: 10.0.2.34, VC ID: 1307, VC status: up
Output interface: Vl808, imposed label stack {45}
Preferred path: not configured
Default path: active
Next hop: 10.0.2.34
Create time: 00:00:10, last status change time: 00:00:10
Signaling protocol: LDP, peer 10.0.2.14:0 up
Targeted Hello: 10.0.2.1(LDP Id) -> 10.0.2.34
Status TLV support (local/remote) : enabled/not supported
Label/status state machine : established, LruRru
Last local dataplane status rcvd: no fault
Last local SSS circuit status rcvd: no fault
Last local SSS circuit status sent: no fault
Last local LDP TLV status sent: no fault
Last remote LDP TLV status rcvd: not sent
MPLS VC labels: local 25, remote 45
Group ID: local 0, remote 0
MTU: local 1998, remote 1998
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, send 0
Everything looks good, and the Mikrotik is able to forward packets to the Cisco - I have yet to get the customer connected on the Cisco side but wanted to test return traffic and unfortunately I get timeouts on the ping mpls pseudowire command from the Cisco ( Other Cisco LDP/MPLS endpoints respond just fine from this box in the same MPLS cloud, so I know this Cisco box is fine ). Normal Ping works fine, pseudowire and mpls ipv4 do not… but the packets DO arrive at the mikrotik ( verified via traffic sniffer )