Parent
|
By default, the S5730-HI, S5731-H, S5731S-H, S5732-H24S6Q, S5732-H48S6Q, S6730S-H, and S6730-H work in parent mode, and the S5732-H24UM2CC, S5732-H48UM2CC, S6730-S, S6730S-S, S6720-SI, S6720S-SI, S6720-EI, and S6720S-EI work in AS mode. The switch models mentioned above can function as the parent or AS, you can run the [ undo ] as-mode disable command to change their working mode. In addition, for the switch models that support the WLAN function, when they work in AS mode, the WLAN function becomes unavailable.
|
AS
|
When an AS is an S5700-10P-LI, S5700-10P-PWR-LI-AC, S2720-EI (V200R009C00 and V200R010C00) or S2750-EI and Layer 3 hardware forwarding for IPv4 packets has been enabled using the assign forward-mode ipv4-hardware command in the system view before the AS joins an SVF system, the AS cannot negotiate to join the SVF system if the AS directly connects to the parent and the management VLAN cannot be configured if the AS connects to the parent across a network.
To solve these problems, start the AS in standalone mode and run the undo assign forward-mode command in the system view to disable Layer 3 hardware forwarding for IPv4 packets.
- If the AS is a stack set up using service ports and running V200R009C00 or a later version, you need to configure the stack function on the AS and then connect the AS to the SVF system. This requirement does not apply to the AS that is a stack set up using stack cards.
In V200R008C00 and earlier versions, each AS can be a stack of up to three member devices that are the same model and provide the same number of ports. From V200R009C00, each AS can be a stack of up to five member devices that are the same model and provide the same number or different numbers of ports.
- From V200R009C00, an AS can be a stack of the same device series but different device models. If an AS is a stack, you can run the slot command to modify the preconfigured device type. To determine which different device models can set up a stack, see "Stacking Support and Version Requirements" in Stack Configuration in the Configuration Guide - Device Management.
- An AS cannot connect to a parent if the parent runs V200R009C00, and the AS is a stack running V200R007C00 or V200R008C00 and has a member switch with a stack ID larger than 2. To connect the AS to the parent, remove the member switch with a stack ID larger than 2 from the stack, upgrade the stack to V200R009C00 or a later version, and then connect the removed member switch to the stack. This member switch will synchronize with the master switch's configuration file and system software. Subsequently, the AS can connect to the parent.
- Stack member switches connected using downlink service ports cannot join an SVF system as ASs.
- In an SVF system, the last four ports of the S6720-32X-SI-32S-AC, S6720-32X-LI-32S-AC, S6720S-32X-LI-32S-AC, S6720-16X-LI-16S-AC, and S6720S-16X-LI-16S-AC are used as uplink ports. Therefore, a stack set up using the last four ports can join an SVF system as an AS.
|
AP
|
If an AP has been connected to the parent before the SVF function is enabled, the parent cannot collect topology information about the AP after the uni-mnguni-mng command is used to enable the SVF function. You need to run the commit { all | ap ap-id } command in the WLAN view to commit the AP configuration. Subsequently, the parent can collect topology information about the AP.
- From V200R011C10, WLAN configurations are automatically delivered, without the need of running the commit all command.
If APs need to connect to an SVF system with an S12700/S12700E/S9700/S7700 functioning as the parent, X series cards must be installed on the parent to manage APs.
|
Fabric port
|
When GE optical interfaces are connected to XGE optical interfaces to connect level-1 ASs to the parent or connect level-2 ASs to level-1 ASs, these interfaces must use GE instead of XGE optical modules.
When an AS connects to APs, all member ports of the Eth-Trunk bound to the fabric port that connects the parent to the AS must be ports on X series cards or ports on non-X series cards. Otherwise, APs cannot go online.
- In V200R008 and earlier versions, an AS can only connect to the upstream parent or AS using fixed uplink ports or ports on an extension card. Since V200R009, downlink service ports of an AS can also be connected to the upstream parent or AS after you configure them as member ports of an upstream fabric port using the uni-mng up-direction fabric-port member interface interface-type interface-number [ to interface-number ] command.
- A downlink service port of an AS cannot be configured as a member port of upstream and downstream fabric ports simultaneously. If this configuration is performed, the AS will be unable to go online after a reboot. If the reset slot command is executed in the slot of the AS, the AS will reset repeatedly.
- Ports on an AS subcard and uplink service port on an AS can only be used as member ports of a fabric port or as stack member ports and cannot be used as service ports.
- From V200R009C00, AS uplink ports can be used to connect to the parent or level-1 AS or set up a stack and be configured as downlink fabric ports to connect to other ASs.
On the S6720-EI, S6720S-EI, S6720-LI, S6720S-LI, S6720-SI, and S6720S-SI, 40GE ports and 10GE ports split from 40GE ports cannot be configured as downlink fabric ports.
|
CAPWAP
|
Configured CAPWAP tunnel parameters apply to the SVF system. To ensure that the CAPWAP tunnel of the SVF system works normally, you are advised to retain the default CAPWAP tunnel parameters. For details on how to configure CAPWAP tunnel parameters, see Configuring CAPWAP Tunnel Parameters.
|