Problem Description

We are in a process to migrate a network from M20 router to M120 router.

The current network connectivity can be seen below.

TNMS L2Martini M10i 3745 M20

Fe-3/3/ Fe-0/3/3.650 Fe-0/1/ 0.650 3.650 2960 Fe-3/2/2.0 Lsq-2/2/0.3

Fe-3/1/11.0

Fe-3/1/ L2Martini 0/3 4.650 3550 M120

Currently there is a TNMS server at local site which uses CLNS to manage a device

Called hiT at remote end. The traffic from TNMS is first carried to the Cisco 3745 router

Then to cisco 3550 switch in vlan 650 and then futher to the trunk link between M20 and

3550.From M20 it is carried through a l2circuit to a remote site i.e. M10i and then further towards the hiT in vlan 650.

At present the l2circuit between M20 and M10 is working fine.

The current neighborship between cisco 3745 router and hiT is as follows.

IIB103-MW-3745-01#sh clns ne | i 650

0090.AEC7.05C0 Fa0/1.650 00d0.930b.c2ad Up 10 L1 IS-IS

IIB103-MW-3745-01#sh clns n

Area 1: System Id Interface SNPA State Holdtime Type Protocol 0090.AEC7.05C0 Fa0/1.650 00d0.930b.c2ad Up 10 L1 IS-IS

The current configuration for layer 2 circuit at M20 and M10 I is as follows. L2Circuit at M20 local site.

Local loop back is 172.16.0.1 unit 650 { description VLAN-TO-M10i_HiT; encapsulation vlan-ccc; vlan-id 650; family ccc; } neighbor 17.16.0.3; neighbor 172.16.0.1; neighbor 172.16.0.3 { interface fe-3/3/0.651 { virtual-circuit-id 651; description "to IPW023_BSC1"; } interface fe-3/3/0.650 { virtual-circuit-id 650; description "to M10_HiT"; } }

L2Circuit at M10i Remote Site.

Local loop back is 172.16.0.3 unit 650 { description VLAN-TO-M10i_HiT; encapsulation vlan-ccc; vlan-id 650; family ccc; }

neighbor 172.16.0.1 { interface fe-3/3/0.651 { virtual-circuit-id 651; description "to IPW023_BSC1"; } interface fe-3/3/0.650 { virtual-circuit-id 650; description "to IPW023_HiT"; } }

The configuration at trunk link connected to local site at M20 is as follows. fe-3/3/0 { vlan-tagging; encapsulation vlan-ccc; unit 650 { description VLAN-M10i_HiT; encapsulation vlan-ccc; vlan-id 650; family ccc; } }

Situation after migration of tunnel at M120

To migrate this L2Circuit from M20 to M120 vlan 650 is activated at a trunk link

Connected between M120 and 3550 with appropriate configurations and deactivation of

This Vlan at M20 trunk link.

After configuration the status of hiT appears as down in TNMS server and neighborship between Cisco 3745 router and hiT appears as follows.

IIB103-MW-3745-01#show clns n

Area 1: System Id Interface SNPA State Holdtime Type Protocol 0090.AEC7.05C0 Fa0/1.650 00d0.930b.c2ad Up 21 IS ES-IS

However the L2Circuit stays up between M120 and M10i routers.

L2Circuit at M120 local site.

Local loop back is 172.16.0.11 unit 650 { description VLAN-TO-M10i_HiT; encapsulation vlan-ccc; vlan-id 650; family ccc; } neighbor 17.16.0.3; neighbor 172.16.0.1; neighbor 172.16.0.3 { interface fe-3/1/4.651 { virtual-circuit-id 651; description "to IPW023_BSC1"; } interface fe-3/1/4.650 { virtual-circuit-id 650; description "to M10_HiT"; } }

L2Circuit at M10i Remote Site. unit 650 { description VLAN-TO-M10i_HiT; encapsulation vlan-ccc; vlan-id 650; } l2circuit { traceoptions { file L2CKt world-readable; flag error; flag connections; flag route; flag fec; } neighbor 172.16.0.11 { interface fe-0/3/3.651 { virtual-circuit-id 651; } interface fe-0/3/3.650 { virtual-circuit-id 650; } The configuration at trunk link connected to local site at M20 is as follows. fe-3/1/4 { vlan-tagging; encapsulation vlan-ccc; unit 650 { description VLAN-TO-M10i_HiT; encapsulation vlan-ccc; vlan-id 650; family ccc; } }

What should be done in order to allow communication between the TNMS and hiT.

Changes after L2Circuit Migration

1-Link type changed from L1 to IS and protocol became IS-IS to ES-IS.