I have tried clearing arp for most of the devices, I have also moved the same config to MX480 PE, All NE become reachable. Below is a simple network layout.
NE-----MX5-1------MX5-2----MX480----C7609--MGMTNETWORK When MX5-1 becomes a PE some of the NE be come unreachable. One thing of note it that the MX5-1 mpls interface is on LU 2500 on VLAN 2500. other then that the same FF are plied on the MX480 On Tue, Apr 30, 2013 at 11:18 AM, Jason Fortier <jasoncfort...@gmail.com>wrote: > Hey Guys, > > We are migrating some NE to new MX-5 LER. I have started with moving mgmt > to an IRB, IRB is in the bridge domain and in the routing instance. When > cut over about half the NE are no longer accessible. > > When the NE are cut back to old default GW (resides on a c7609 within a > RI) and pass through the MX as L2 with in the bridge domain only it all > works fine. Only when cutover to the NE PE does it break on some devices. > > All routing appears to be working as some NE with in the subnet > are accessible. not sure why other are not? any idea would be appreciated. > > jfortier@routermx5# show > description "management irb"; > mtu 1600; > unit 101 { > description "Management VLAN101"; > family inet { > address 10.64.0.1/24; > } > } > > jfortier@routermx5# show bridge-domains > 101 { > description "Management VLAN 101"; > domain-type bridge; > vlan-id 101; > interface ge-1/0/1.101; > interface ge-1/0/2.101; > interface ae1.101; > interface ae0.101; > interface ge-1/0/0.101; > routing-interface irb.101; > } > > jfortier@routermx5# show routing-instances mgmt_nes > instance-type vrf; > interface irb.101; > interface irb.102; > route-distinguisher 10.92.6.20:3141; > vrf-target target:64512:101; > vrf-table-label; > > > Jason > > > > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp