Interface Naming Conventions; Vsf Member Roles; Member Priority - HP Aruba JL253A Management And Configuration Manual

and becomes a Commander, will retain its member ID, while the other will automatically be assigned a different
unassigned member ID from the pool and reboot.
NOTE: If the VSF member ID changes when joining a VSF virtual chassis, it will cause a reboot of
that member and not the whole VSF virtual chassis.

Interface naming conventions

An interface is named in the following format:
Interface name
<member ID>/<port-index> For example: 1/1, 2/24.
Definition
<member ID >
VSF member ID of the switch. The VSF member ID will be a part of the interface name in a VSF fabric,
whether a device has formed a VSF fabric with other devices, or not. A single device is also considered to be
a standalone VSF fabric.
<port-index >
Index of the port on the device. Port index depends on the number of ports available on the linecard (or
Interface Module).
For example, on VSF, an interface name would take this form:
<member ID>/<interface-module><port-index>
2/4
where 2 is the member ID and 4 is the port-index.

VSF member roles

• Commander: Control and management plane protocols run on the Commander, which is responsible for
managing the forwarding databases, synchronizing them with the Standby and controlling all line cards
including that of the Standby.
• Standby: Standby is a stateful backup device for the Commander and is ready to take control of the VSF
virtual chassis if the Commander device fails. This enables the VSF virtual chassis to continue its operations
seamlessly in the event of a failure.
• Member: All devices in the stack other than the commander and standby are called member switches. The
member switch does not run any networking protocols and has no states. The ports on this switch are directly
controlled and programmed by the commander switch. When a standby takes over as commander, one of the
member switches is upgraded to standby role.
NOTE: All switches in the VSF stack will have the same software version. During stack formation,
switches which do not have the same software version as the commander, will be updated to the
commander's software. This will cause a reboot of the updated switch.

Member priority

Member priority determines the possibility of a member device being elected as the Commander. A member with
higher priority is more likely to be elected as the Commander. The default priority is 128, but can be between 1
and 255.
652 Aruba 2930F / 2930M Management and Configuration Guide
for ArubaOS-Switch 16.08