Configuring Extended Edge Switching Topology with Full Automation

You can automatically configure an Extended Edge Switching topology fully or in part. This capability allows for the more rapid and accurate setup of an Extended Edge Switching architecture.

However, the disadvantage of full automation is that you must start with an unconfigured controlling bridge (CB) (out of the shipping box) or unconfigure the CB switch. To avoid unconfiguring the CB, but to still avoid manually configuring the entire Extended Edge Switching topology, consider using partial automation (see Configuring Extended Edge Switching Topology with Partial Automation (Auto-configuration)).
Note

Note

Do not attach bridge port extenders (BPEs) to a partitioned port. Unconfiguring the CB removes the port partition configuration, and this causes full automation to fail.
Full automation for Extended Edge Switching performs the following tasks:
  1. Determines if the switch is capable of being a CB.
  2. Detects if any BPEs are attached.
  3. Enables VPEX mode on the CB.
  4. If you are setting up redundant CBs (see Redundant Controlling Bridges):
    • Detects the other CB.
    • Creates a VLAN on only the port(s) between the CBs.
    • Adds link local IP address to the VLAN.
    • Creates a LAG for the port(s) between the MLAG peers.
    • When the CB detects the IP address of the other CB VLAN, creates the MLAG peer.
  5. Enables Extended Edge Switching auto-configuration (see Configuring Extended Edge Switching Topology with Partial Automation (Auto-configuration), which performs the following tasks:
    1. Assigns the next available slot number to each BPE.
    2. Creates LAGs/MLAGs on cascade ports.
    3. Adds ports to existing cascade port LAGs.
Note

Note

For full automation, the entire process can take about 6–7 minutes to complete depending upon the configuration.

To start full automation for Extended Edge Switching:
  1. (Optional) If you are setting up redundant CBs, connect the two CBs to each other.
  2. Attach BPE(s).
  3. Ensure that none of the following files are present on the CB(s):
    • default.xsf
    • default.py
    • autoexec.xsf
    • autoexec.py

    For information about locating and deleting files on the switch, see Using the ExtremeXOS File System.

  4. Ensure that the CB(s) do not have a configuration. Run unconfigure switch {all | erase [all | nvram]}. Use either:
    • unconfigure switch—removes configuration, but leaves other settings intact.
    • unconfigure switch all—removes configuration and resets all settings to factory defaults (recommended).
  5. Reboot the CB(s).
  6. The configuration applied by automation is not automatically saved. Save the configuration:
    • Manually: save configuration {primary | secondary | existing-config | new-config}
    • Automatically: save configuration automatic {every minutes {primary | secondary | existing-config | new-config} | never}

For information about troubleshooting an Extended Edge Switching topology, see Troubleshooting an Extended Edge Switching Topology.

Note

Note

To avoid having automation start if you do want it to, run terminate vpex ztp or perform some configuration prior to attaching BPEs or have a default.xsf (or other similar file) file in place.

To view automation status, use the command show vpex.

9036717-00 Rev AB