This was first thought to be a isolated case.  after checking the rest of
my network it appears that all MX-5 have the same issue.Devices connected
to a cisco 3550 as and Access device are unable to ping the MX5 irb.

network topology as follows:

NE ------C3550------MX-5

The NE is an access port connected to and access port on the 3550.

If the NE becomes a Trunk port the problem goes away.  If the Cisco 3550 is
replaced with a Cisco 4006 or an EX4200 the problem also goes away.

Is there anything unique that the 3550 does when building the frame to
egress that could explain the issue??

Jason




On Tue, Apr 30, 2013 at 11:18 AM, Jason Fortier <[email protected]>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 [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to