Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎05-20-2019 08:04 PM
Hello Everyone. We are migrating our core switches from Nortel 5500 to VSP 7200 Series. For nortel switches we've used OSPF. For VSP's we wanted to use Fabric . we've configured 2 VSP's with MLT between them with IS-IS. we've connected the new cores to old cores by a trunk port with a Management VLAN. From the new switch i am able to ping to other side of the old cores and all the IPs. So i've created a new VLAN in new cores. by using the access port with the new VLAN, i am not able to ping to the other side of the old core. I can only ping the new cores ?? Could you please someone help me out. Thank you in advance.
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎05-22-2019 06:21 PM
Thank you for your response. We have vIST b/w two new cores. The problem was solved after we did the ospf redistribution for IS IS in the new core switches. Thank you.
6 REPLIES 6
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎05-21-2019 02:02 PM
Firstly Thank you for your response Roger. I have default route enabled on the VSP7200 Switch , the route pointed to the old core(Nortel 5530). I am able to ping from the switch. But i could n't ping from new vlan in new core switch. I think its routing issue between the VLANs. I don't know how to route between the IS IS and ospf on the other side ??
Thank you.
Thank you.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎05-21-2019 01:56 PM
It looks like you don't have routing enabled between the ERS5500 and the VSP7200. You either would have to turn on OSPF or add static routes to get your routing tables setup properly.
For a VLAN/IP subnet that is connected on old and new core, you would not need routing, but for subnets that are "behind" the routers, you need to ensure your routing tables are correct and both sides can see each other.
Roger
For a VLAN/IP subnet that is connected on old and new core, you would not need routing, but for subnets that are "behind" the routers, you need to ensure your routing tables are correct and both sides can see each other.
Roger
