Three devices were configured as part of the virtual chassis.

The command was run from the aVCS vMaster.

The aVCS vMaster of the group can always be accessed at IP Address 1.0.0.1.

The aVCS vMaster of the set can always be accessed at IP Address 224.0.0.210.

The command was run from device 3 of the set.

This is aVCS set-id 1.

2

VRID Default is enough

6

5

3

4

Each partition has its own distinct VRID 0.

VRID 0 only exists in the shared partition; private partitions can only contain VRIDs numbered higher than 0.

VRID 0 is initially enabled only in the shared partition; partition administrators can enable VRID 0 in their partitions.

When using VRRP-A on a device with multiple partitions, VRID 0 is automatically disabled.

Any Thunder series devices can be clustered together in an aVCS set

Devices must be the same model but can have different optional hardware cards

Devices must be the same model and have the same optional hardware cards

System logs generated from partition “p1” will be sent to logging server “2.2.2.2”, and only warning severity log messages are sent to the shared logging server’s “192.168.216.45”.

System logs generated from partition “p1” will be sent to logging server “2.2.2.2”, as well as to the shared logging server’s “192.168.216.45”.

System logs generated from partition “p1” will be sent to logging server “2.2.2.2”.

System logs generated from partition “p1” will be sent to the shared logging server’s “192.168.216.45”.

The command is ignored when the current vMaster is in vMaster maintenance mode.

Any subsequent vmaster-take-over command within the chassis with a parameter smaller than 201 is ignored.

The 200 priority is compared to the current vmaster’s default vrid priority to determine which device controls the chassis.

If an administrator on vBlade B were to simultaneously issue command vcs vmaster-take-over 210, vBlade B would become the vMaster.