[j-nsp] EX4200 VC Pity Me

[Brendan Mannella]

I could be completely wrong, but shouldn't the second 4200 be the
backup RE and not forced to be a line card?

Could have something to do with it.



On Apr 3, 2012, at 8:24 PM, Dave Peters <dave at terabitsystems.com> wrote:

> Hi all--
>
> Trying to test a VC with two EX4200s running 10.4R9.2.  Very simple.  I just can't get the backup (or line card) chassis to pass traffic.  Pinging the gateway out of the routing engine or master works fine.  Trying to ping through the backup/line card gives me nothing.  The VC is recognized (per the below).  Something simple I'm doing wrong, I know.  Here's some output (and thanks for any help you might provide):
>
> root> show virtual-chassis
>
> Preprovisioned Virtual Chassis
> Virtual Chassis ID: a8ab.cf0b.66d6
>                                          Mastership            Neighbor List
> Member ID  Status   Serial No    Model    priority    Role      ID  Interface
> 0 (FPC 0)  Prsnt    BP0209472119 ex4200-48t      129  Master*    1  vcp-0
>                                                                 1  vcp-1
> 1 (FPC 1)  Prsnt    FV0211137957 ex4200-48t        0  Linecard   0  vcp-0
>                                                                 0  vcp-1
>
>
> root> show virtual-chassis vc-port member 0
> fpc0:
> --------------------------------------------------------------------------
> Interface   Type              Trunk  Status       Speed        Neighbor
> or                             ID                 (mbps)       ID  Interface
> PIC / Port
> vcp-0       Dedicated           1    Up           32000        1   vcp-0
> vcp-1       Dedicated           2    Up           32000        1   vcp-1
>
> {master:0}
> root> show virtual-chassis vc-port member 1
> fpc1:
> --------------------------------------------------------------------------
> Interface   Type              Trunk  Status       Speed        Neighbor
> or                             ID                 (mbps)       ID  Interface
> PIC / Port
> vcp-0       Dedicated           1    Up           32000        0   vcp-0
> vcp-1       Dedicated           2    Up           32000        0   vcp-1
>
> {master:0}
>
>
>
>
>
> root> show configuration
> ## Last commit: 2012-02-02 09:38:58 UTC by root
> version 10.4R9.2;
> system {
>    root-authentication {
>        encrypted-password bJ/GddyoJuiU2; ## SECRET-DATA
>    }
>    services {
>        web-management {
>            http;
>        }
>    }
>    syslog {
>        user * {
>            any emergency;
>        }
>        file messages {
>            any notice;
>            authorization info;
>        }
>        file interactive-commands {
>            interactive-commands any;
>        }
>    }
> }
> interfaces {
>    ge-0/0/0 {
>        unit 0 {
>            family ethernet-switching;
>        }
>    }
>    ge-0/0/1 {
>        unit 0 {
>            family ethernet-switching;
>        }
>    }
>    ge-0/0/2 {
>        unit 0 {
>            family ethernet-switching;
>
> *!truncated!*
>
>    vlan {
>        unit 0 {
>            family inet {
>                address 192.168.10.188/24;
>            }
>        }
>    }
> }
> routing-options {
>    static {
>        route 0.0.0.0/0 next-hop 192.168.10.77;
>    }
> }
> protocols {
>    igmp-snooping {
>        vlan all;
>    }
>    lldp {
>        interface all;
>    }
>    lldp-med {
>        interface all;
>    }
> }
> ethernet-switching-options {
>    storm-control {
>        interface all;
>    }
> }
> vlans {
>    default {
>        l3-interface vlan.0;
>    }
> }
> poe {
>    interface all;
> }
> virtual-chassis {
>    preprovisioned;
>    no-split-detection;
>    member 1 {
>        role line-card;
>        serial-number FV0211137957;
>    }
>    member 0 {
>        role routing-engine;
>        serial-number BP0209472119;
>    }
> }
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp