Switching

Hello all,

I recently replaced a VC member of an EX4200 stack. The replacement went fine but I noticed that when I run a show interface terse it is showing 48 extra ports. However, if I run show virtual chassis it only shows the 3 members that are there. I have serached the knowledge base to no avail, maybe I am not asking the right questions. It does not appear to be affecting anything but it is a little misleading to my admins.

Has any one run into this before, and if so how can I resolve this?

Thanks,

Cole

Even though you are just replacing a member in the VC, for the VC that is a new member and it gets assigned a new FPC ID. The FPC ID that you used for the member replaced will be saved in case you later decide to plug in back to the VC the member that you removed earlier.

You can recycle that FPC ID so it will be used for the next member that you will add to the VC.

Also, you can renumber the new FPC ID that was assigned to the one used for the member that was replaced. This will change the interface naming as well.

Here is more information about this:

http://www.juniper.net/techpubs/en_US/junos12.3/topics/task/installation/virtual-chassis-ex4200-member-replacing-cli.html

=====

If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.

parau,

Thank you for the reply. The show virtual-chassis status is showing that the next available member number is 3, which is what it should be, please see below. I ran the recycle FPC ID when the switch was replaced.

Member ID  Status   Serial No    Model     prio  Role      Mode ID  Interface
0 (FPC 0)  Prsnt    SERIAL ex4200-48t 250  Master*      N  1  vcp-0
                                                                 2  vcp-1
1 (FPC 1)  Prsnt    SERIAL ex4200-48t 225  Backup       N  0  vcp-1
2 (FPC 2)  Prsnt    SERIAL ex4200-48t 128  Linecard     N  0  vcp-0

Member ID for next new member: 3 (FPC 3)

When I run the show interface terse command it shows the port numbers for the 4th switch that is not there. The odd thing is that it is showing some of those interfaces in down/up status. Will the request virtual-chassis recycle member-id 3 clear this up?

ge-3/0/0                up    down
ge-3/0/1                up    down
ge-3/0/2                up    down
ge-3/0/3                up    down
ge-3/0/4                up    down
ge-3/0/5                up    down
ge-3/0/6                up    up
ge-3/0/7                up    down
ge-3/0/8                up    up
ge-3/0/9                up    down
ge-3/0/10               up    down
ge-3/0/11               up    down
ge-3/0/12               up    down
ge-3/0/13               up    up
ge-3/0/14               up    down
ge-3/0/15               up    down
ge-3/0/16               up    up
ge-3/0/17               up    down
ge-3/0/18               up    down
ge-3/0/19               up    down
ge-3/0/20               up    down
ge-3/0/21               up    down
ge-3/0/22               up    down
ge-3/0/23               up    down
ge-3/0/24               up    down
ge-3/0/25               up    down
ge-3/0/26               up    down
ge-3/0/27               up    down
ge-3/0/28               up    down
ge-3/0/29               up    down
ge-3/0/30               up    down
ge-3/0/31               up    down
ge-3/0/32               up    down
ge-3/0/33               up    down
ge-3/0/34               up    down
ge-3/0/35               up    down
ge-3/0/36               up    down
ge-3/0/37               up    down
ge-3/0/38               up    down
ge-3/0/39               up    down
ge-3/0/40               up    down
ge-3/0/41               up    down
ge-3/0/42               up    down
ge-3/0/43               up    down
ge-3/0/44               up    down
ge-3/0/45               up    down
ge-3/0/46               up    down
ge-3/0/47               up    down

Is it possible by any chance that ge-3/*/* be an exact copy of another FPC interfaces?

For instance, ge-3/0/6 is actually ge-1/0/6.

In any case, try to recycle one more time the ID 3.

=====

If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.

Unfortunalty this did not work. I am thinking maybe a reboot will clear these out.

Reboot cleared this up.