Aside from being in linecard mode, that status looks correct for a standalone
qfx.
===
{master:0}
cmyers@lab-qfx5100-1> show virtual-chassis
Virtual Chassis ID: 79a5.39fa.6314
Virtual Chassis Mode: Enabled
Mstr Mixed Route
Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID
Interface
0 (FPC 0) Prsnt ############ qfx5100-48s-6q 128 Master* N VC
Member ID for next new member: 1 (FPC 1)
===
The "request virtual-chassis reactivate", and possibly a reboot after, should
get it where you want it to be.
It is a little bit confusing at first, but it is always operating as a
virtual-chassis. It simplifies development and testing by treating standalone
as "virtual-chassis with 1 member" case rather than having "virtual-chassis
with 1-n members" mode and a separate "standalone" mode. The EX4200/EX8200 do
the same thing, although not as obviously.
-Chad
On Nov 13, 2015, at 1:11 PM, Michael Loftis <[email protected]> wrote:
> Oh also... request virtual-chassis recycle member-id N for old member IDs
>
> On Fri, Nov 13, 2015 at 10:08 AM, Michael Loftis <[email protected]> wrote:
>> It might be it's in split mode? request virtual-chassis reactivate ?
>> It's odd that it shows itself as a linecard but also master role. The
>> other thing you could do is maybe explicitly set it as a routing
>> engine? in config set virtual-chassis member 0 serial-number XXX role
>> routing-engine
>>
>> Whatever is going on is just software having to do with it previously
>> being in a line card role.
>>
>> On Fri, Nov 13, 2015 at 9:38 AM, Dave Peters - Terabit Systems
>> <[email protected]> wrote:
>>> That's another weird part. It's not connected to anything, and there's no
>>> vc-port recognized:
>>>
>>> root> show virtual-chassis
>>>
>>> Virtual Chassis ID: 1517.c443.48e0
>>> Virtual Chassis Mode: Enabled
>>> Mstr Mixed Route
>>> Neigh
>>> bor List
>>> Member ID Status Serial No Model prio Role Mode Mode
>>> ID I
>>> nterface
>>> 0 (FPC 0) Prsnt TR0214440089 qfx5100-48c-6q 128 Master* N VC
>>>
>>> Member ID for next new member: 1 (FPC 1)
>>>
>>> {linecard:0}
>>> root> show virtual-chassis vc-port
>>> fpc0:
>>> --------------------------------------------------------------------------
>>>
>>> {linecard:0}
>>> root>
>>>
>>> I think I've got a lemon, here, but as always, I really appreciate
>>> everyone's input.
>>>
>>> Thanks much.
>>>
>>> --Dave Peters
>>>
>>> -----Original Message-----
>>> From: Alexandre Guimaraes [mailto:[email protected]]
>>> Sent: Friday, November 13, 2015 8:22 AM
>>> To: Dave Peters - Terabit Systems; [email protected]
>>> Subject: RES: VC on a QFX5100 won't go away
>>>
>>>> show virtual-chassis
>>>
>>> Preprovisioned Virtual Chassis
>>> Virtual Chassis ID: cf12.a99f.e63b
>>> Virtual Chassis Mode: Enabled
>>> Mstr Mixed Route
>>> Neighbor List
>>> Member ID Status Serial No Model prio Role Mode Mode
>>> ID Interface
>>> 0 (FPC 0) Prsnt TA3714071234 qfx5100-48s-6q 129 Master* N VC
>>> 2 vcp-255/0/50
>>>
>>> 1 vcp-255/0/51
>>> 1 (FPC 1) Prsnt TA3714141234 qfx5100-48s-6q 129 Backup N VC
>>> 0 vcp-255/0/50
>>>
>>> 2 vcp-255/0/51
>>> 2 (FPC 2) Prsnt TA3714141234 qfx5100-48s-6q 0 Linecard N VC
>>> 1 vcp-255/0/50
>>>
>>> 0 vcp-255/0/51
>>>
>>>
>>> See vcp-255/0/51 ports:
>>>
>>>> show virtual-chassis vc-port
>>> fpc0:
>>> --------------------------------------------------------------------------
>>> Interface Type Trunk Status Speed Neighbor
>>> or ID (mbps) ID Interface
>>> PIC / Port
>>> 0/50 Configured -1 Up 40000 2
>>> vcp-255/0/51
>>> 0/51 Configured -1 Up 40000 1
>>> vcp-255/0/50
>>>
>>> fpc1:
>>> --------------------------------------------------------------------------
>>> Interface Type Trunk Status Speed Neighbor
>>> or ID (mbps) ID Interface
>>> PIC / Port
>>> 0/50 Configured -1 Up 40000 0
>>> vcp-255/0/51
>>> 0/51 Configured -1 Up 40000 2
>>> vcp-255/0/50
>>>
>>> fpc2:
>>> --------------------------------------------------------------------------
>>> Interface Type Trunk Status Speed Neighbor
>>> or ID (mbps) ID Interface
>>> PIC / Port
>>> 0/50 Configured -1 Up 40000 1
>>> vcp-255/0/51
>>> 0/51 Configured -1 Up 40000 0
>>> vcp-255/0/50
>>>
>>>
>>> So:
>>>
>>> request virtual-chassis vc-port delete pic-slot X port Y member Z
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> -----Mensagem original-----
>>> De: juniper-nsp [mailto:[email protected]] Em nome de
>>> Dave Peters - Terabit Systems Enviada em: quinta-feira, 12 de novembro de
>>> 2015 18:05
>>> Para: [email protected]
>>> Assunto: [j-nsp] VC on a QFX5100 won't go away
>>>
>>> Hi all--
>>>
>>> I've been trying to remove the VC config from a QFX5100 running
>>> 13.2X51-D38, and I'm not having any luck. I've tried zeroizing and going
>>> into the shell to remove the files in the config/vchassis folder, but I'm
>>> having no luck. Looking at the config, I'm seeing:
>>>
>>> root> show configuration
>>>
>>> <snip>
>>> commit {
>>> factory-settings {
>>> reset-virtual-chassis-configuration;
>>> reset-chassis-lcd-menu;
>>> <snip>
>>>
>>> root>
>>>
>>> Which isn't on a factory default system, but I can't seem to clear that
>>> portion of the configuration, and I when I delete the .conf files from the
>>> shell, the commit/factory-settings/reset-vc stuff pops up all over again.
>>>
>>> This is probably a really simple thing, but I'm not getting it. Can anyone
>>> help?
>>>
>>> Thanks much.
>>>
>>> --Dave Peters
>>> _______________________________________________
>>> juniper-nsp mailing list [email protected]
>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>> _______________________________________________
>>> juniper-nsp mailing list [email protected]
>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>>
>>
>> --
>>
>> "Genius might be described as a supreme capacity for getting its possessors
>> into trouble of all kinds."
>> -- Samuel Butler
>
>
>
> --
>
> "Genius might be described as a supreme capacity for getting its possessors
> into trouble of all kinds."
> -- Samuel Butler
> _______________________________________________
> juniper-nsp mailing list [email protected]
> https://puck.nether.net/mailman/listinfo/juniper-nsp
________________________________
This message may contain confidential information and is intended for specific
recipients unless explicitly noted otherwise. If you have reason to believe you
are not an intended recipient of this message, please delete it and notify the
sender. This message may not represent the opinion of Intercontinental
Exchange, Inc. (ICE), its subsidiaries or affiliates, and does not constitute a
contract or guarantee. Unencrypted electronic mail is not secure and the
recipient of this message is expected to provide safeguards from viruses and
pursue alternate means of communication where privacy or a binding message is
desired.
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
