Analyzing Virtual Chassis Fabrics
This topic describes how to analyze Virtual Chassis Fabrics (VCFs). The Run Fabric Analyzer task analyzes a VCF and provides information about its health, connectivity, and topology. The Fabric Analyzer works on VCFs configured in spine-and-leaf mode.
This topic describes:
Procedure for Analyzing a Virtual Chassis Fabric
Fabric analysis is automatically performed on managed VCFs. You do not need to manually run the analyzer.
To see the results of the analysis of a VCF:
- Click Monitor in the Network Director banner.
- Select the VCF to analyze in the View pane.
- Select the Fabric Analysis tab.
For information about using the tabs within the Fabric Analysis tab, see the following sections:
Using the Fabric Health Check Tab
To check the health of a VCF, select the Fabric Health Check tab on the Fabric Analysis tab in Monitor mode. The Fabric Health Check tab shows connectivity information about the VCF. Each leaf device is listed in the Leaves column, and each spine device is a table column. Each cell indicates the connectivity status between the leaf device and the spine device.
Using the Topology Tab
The Topology tab displays a topology diagram of the VCF as shown in Figure 1. Mouse over a member to view details of that member.
The details that are displayed in the top panel of the Virtual Chassis Topology view are described in Table 1.
Table 1: Common Details for the Virtual Chassis and Virtual Chassis Fabric
All members of a Virtual Chassis configuration share one Virtual Chassis identifier (VCID). This identifier is derived from internal parameters.
The provisioning mode of the member. Provision mode can be autoprovisioned, preprovisioned or not preprovisioned.
Autoprovisioning a Virtual Chassis Fabric (VCF) enables you to “plug and play” devices into your VCF after minimal initial configuration.
In a VCF, you can have two to four members configured in the Routing Engine role. Of this, one member acts as the master Routing Engine and another member acts as the backup Routing Engine. In a preprovisioned configuration, the selection of which member functions as the master Routing Engine and which as the backup Routing Engine is determined by the software based on the primary-role election algorithm.
In a configuration that is not preprovisioned, the selection of the primary and backup is determined by the primary-role priority value and secondary factors in the primary-role election algorithm.
Indicates whether the Virtual Chassis is mixed or not.
The following details are displayed in the Virtual Chassis Topology view for each member depending on the role of the member as shown in Table 2.
Table 2: Details of VC/VCF Members
Name of the member switch provided while configuring the device. The device name is displayed as a label.
Serial number of the member switch.
Platform of the device. Platform can be QFX3500, QFX3600, or QFX5100.
The primary-role priority value. This is the most important factor in determining the role of the member switch within the Virtual Chassis configuration.
Operational role of the device. A device might be configured for a particular role, but can operate in the same or a different role. For example, a spine device configured with a Routing Engine role might operate as a line card. Therefore, the operational role of this device is Line Card.
Operational role can be Routing Engine or Line Card.
The configured role of the device. This can be Routing Engine or Line card.
Displays the status of each member device: