01-04 Typical Device Management Configuration
01-04 Typical Device Management Configuration
Recommendations
NOTE
The following recommendations are provided based on the positioning of fixed switch models. If
customers have special requirements, it is recommended to deploy high-end devices at a lower
network layer; it is not recommended to deploy low-end devices at a higher network layer. For
example, it is recommended to deploy aggregation switches at the access layer rather than to
deploy access switches at the aggregation layer.
To ensure stack reliability and bandwidth, you are advised to do as follows:
● Ensure that each member device connects to the core device through an uplink port. This
connection prevents upstream traffic forwarding from being affected when any member
device fails.
● When using multiple devices to set up a stack, ensure the same stack bandwidth between
any two devices. Otherwise, the bandwidth of the stack system is the minimum stack
bandwidth.
Ring topology ● High reliability: The first and last Member switches
If a stack link member switches are located near
fails, the need to be one another.
topology connected by a
changes from physical link, so
ring to chain, this topology is
and the stack not applicable to
can still long-distance
function stacking.
normally.
● High link
bandwidth
efficiency: Data
can be
forwarded
along the
shortest path.
Figure 4-5 Only one logical stack port between two member devices
Figure 4-6 Two logical stack ports between two member devices
When using two devices to set up a stack, you are advised to do as follows:
● If the devices provide no more than 28 ports, use the networking with only
one logical stack port. Otherwise, use the back-to-back networking.
● If more member devices need to be added to the stack in the future, use the
back-to-back networking, which will require minimum modification to the
existing system.
● Connect at least two stack cables between the two devices to ensure
reliability.
Feature Limitations
Version restrictions:
● When multiple switches set up a stack, member switches will synchronize the
running version of the master switch. If a member switch does not support
this running version, it will restart repeatedly.
● In V200R009C00, if MPLS-incapable S5320-EIs exist in a stack, this stack
cannot have MPLS enabled. If member devices in a stack are running MPLS
services, adding MPLS-incapable S5320-EIs to the stack is not allowed.
● When two stack member devices use ports on S7Q02001 and ES5D21Q02Q00
cards, respectively, to set up a stack, ensure that the device versions are the
same. Otherwise, the stack ports cannot go Up.
MAD specifications:
● You can configure a maximum of eight direct detection links for each member
switch in a stack.
● You can configure the relay mode on a maximum of four Eth-Trunks in a
stack.
● In V200R008C00 and earlier versions, you can configure a maximum of 64
Eth-Trunks on a relay agent to provide the relay function for multiple stacks.
This restriction does not apply to versions later than V200R008C00.
Deployment Recommendations
● Connect a stack to other network devices using an Eth-Trunk and add one
port of each member switch to the Eth-Trunk.
● When a stack connects to access devices, configure ports directly connected to
terminals as STP edge ports to prevent STP re-calculation when the ports
alternate between Up and Down states. This configuration ensures normal
traffic forwarding.
● If storm control needs to be configured on many ports, replace storm control
with traffic suppression to save CPU resources.
● If port security needs to be configured on many ports, replace port security
with MAC address learning limiting to save CPU resources.
● Loops may occur on a network to which a stack connects. Run the mac-
address flapping action error-down command to set an interface to the
error-down state when MAC address flapping is detected on the interface.
This improves system processing performance and allows the peer device to
detect that the interface becomes Down. Additionally, if the peer device has
redundant links, traffic can be rapidly switched to a normal link.
Configuration Roadmap
1. Power off SwitchA, SwitchB, and SwitchC, install an ES5D00ETPC00 stack card
on each switch, and then power on the three switches.
NOTE
● The ES5D00ETPC00 stack card does not support hot swap. You need to power off a
switch before installing the stack card on the switch.
● You can perform software configurations only after installing a stack card on the
switch.
2. Enable the stacking function.
3. Configure stack IDs and stack priorities for member switches to facilitate
device management and identification.
4. Power off SwitchA, SwitchB, and SwitchC, connect physical member ports
using PCIe cables, and then power on the three switches.
5. Configure an inter-device Eth-Trunk to increase reliability and uplink
bandwidth.
6. Configure multi-active detection (MAD) in relay mode to ensure network
availability when the stack splits. The stack split detection mechanism is
called dual-active detection (DAD) in V200R002 and earlier versions and MAD
in later versions.
Procedure
Step 1 Turn off power supplies of SwitchA, SwitchB, and SwitchC, install an
ES5D00ETPC00 stack card on each switch, and then power on the three switches.
Step 3 Configure stack IDs and stack priorities. The default stack ID is 0, and the default
stack priority is 100.
[SwitchA] stack slot 0 priority 200 //Set the stack priority of the master switch to 200, which is larger
than those of other member switches, and use the default stack ID 0.
[SwitchB] stack slot 0 renumber 1 //Use the default stack priority 100 and set the stack ID to 1.
[SwitchC] stack slot 0 renumber 2 //Use the default stack priority 100 and set the stack ID to 2.
Step 4 Turn off power supplies of SwitchA, SwitchB, and SwitchC, connect physical
member ports using PCIe cables as shown in Figure 4-8, and then power on the
three switches.
NOTE
● Run the save command to save the configurations before you power off the switches.
● STACK 1 port of one switch must be connected to STACK 2 port of another switch.
Otherwise, the stack cannot be set up.
● To ensure that a stack can be set up successfully, you are advised to perform operations
in the following sequence. First, power on the switch that you want to specify as the
master switch. In this example, SwitchA becomes the master switch after you complete
the following operations.
1. Power off SwitchA, SwitchB, and SwitchC.
2. Connect SwitchA and SwitchB with a stack cable.
3. Power on and start SwitchA and then power on SwitchB.
4. Check whether SwitchA and SwitchB set up a stack successfully. For details, see step
5.
5. Connect SwitchC to SwitchB and SwitchA using stack cables and then power on
SwitchC.
6. Check whether SwitchA, SwitchB, and SwitchC set up a stack successfully. For details,
see step 5.
Press the MODE button on any member switch to change the mode status
indicator to the stack mode.
● If the mode status indicators on all the member switches change to the stack
mode, the stack is set up successfully.
● If the mode status indicator on any member switch does not change to the
stack mode, the stack is not set up.
NOTE
● The S5300-EI and S5300-SI use the same mode status indicator to show the stack and speed
modes. After you press the MODE button, the indicator is steady red and off after 45
seconds, indicating that the switch enters the stack mode.
● The S5320-EI has an independent stack mode indicator (STCK indicator). After you press the
MODE button, the indicator is steady green or blinking and off after 45 seconds, indicating
that the switch enters the stack mode.
Log in to the stack to check whether the number of member switches in the stack
is the same as the actual value and whether the stack topology is the same as the
actual hardware connection.
<SwitchA> system-view
[SwitchA] sysname Stack
[Stack] display stack
Stack mode: Card
Stack topology type: Ring
Stack system MAC: xxxx-xxxx-xxx5
MAC switch delay time: 10 min
Stack reserved vlan : 4093
Slot of the active management port: 0
Slot Role Mac address Priority Device type
-------------------------------------------------------------
0 Master xxxx-xxxx-xxx5 200 S5328C-EI
1 Standby xxxx-xxxx-xxx1 100 S5328C-EI
2 Slave xxxx-xxxx-xxx2 100 S5328C-EI
# Create an Eth-Trunk in the stack and configure uplink physical ports as Eth-
Trunk member ports.
[Stack] interface eth-trunk 10
[Stack-Eth-Trunk10] trunkport gigabitethernet 0/0/5
[Stack-Eth-Trunk10] trunkport gigabitethernet 1/0/5
[Stack-Eth-Trunk10] trunkport gigabitethernet 2/0/5
[Stack-Eth-Trunk10] quit
# Create an Eth-Trunk on SwitchD and configure the ports connected to the stack
as Eth-Trunk member ports.
<Quidway> system-view
[Quidway] sysname SwitchD
[SwitchD] interface eth-trunk 10
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/1
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/2
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/3
[SwitchD-Eth-Trunk10] quit
Step 8 Configure MAD in relay mode and configure SwitchD as the relay agent.
# In the stack, configure MAD in relay mode on the inter-device Eth-Trunk.
[Stack] interface eth-trunk 10
[Stack-Eth-Trunk10] mad detect mode relay //This command is used in versions later than V200R002.
The command used in V200R002 and earlier versions is dual-active detect mode relay.
[Stack-Eth-Trunk10] return
----End
Configuration Files
● Stack configuration file (the stack configuration is written to the flash
memory instead of the configuration file)
#
sysname Stack
#
interface Eth-Trunk10
mad detect mode relay
#
interface GigabitEthernet0/0/5
eth-trunk 10
#
interface GigabitEthernet1/0/5
eth-trunk 10
#
interface GigabitEthernet2/0/5
eth-trunk 10
#
return
Networking Requirements
A new enterprise network needs to provide sufficient ports for access devices, and
the network structure should be simple to facilitate configuration and
management.
As shown in Figure 4-9, SwitchA, SwitchB, and SwitchC need to set up a stack in a
ring topology and connect to SwitchD through an inter-device Eth-Trunk. SwitchA,
SwitchB, and SwitchC are the master, standby, and slave switches respectively, with
stack IDs of 0, 1, and 2 and stack priorities of 200, 100, and 100. As the three
switches function as one logical device on the network, the number of ports is
increased and network management and maintenance are simplified.
In this example, S3300-EIs set up a stack.
Configuration Roadmap
1. The stacking function is enabled by default on the S3300-EI. Therefore, these
switches can set up a stack immediately after they are connected using stack
cables, without additional configuration. To facilitate device management and
identification, configure device names, stack IDs, and stack priorities for stack
member switches.
2. Power off SwitchA, SwitchB, and SwitchC, connect physical member ports
using SFP stack cables, and then power on the three switches.
3. Configure an inter-device Eth-Trunk to increase reliability and uplink
bandwidth.
Procedure
Step 1 Configure device names to differentiate devices.
<Quidway> system-view
[Quidway] sysname SwitchC
Step 2 Configure stack IDs and stack priorities. The default stack ID is 0, and the default
stack priority is 100.
[SwitchA] stack slot 0 priority 200 //Set the stack priority of the master switch to 200, which is larger
than those of other member switches, and use the default stack ID 0.
[SwitchB] stack slot 0 renumber 1 //Use the default stack priority 100 and set the stack ID to 1.
[SwitchC] stack slot 0 renumber 2 //Use the default stack priority 100 and set the stack ID to 2.
Step 3 Turn off power supplies of SwitchA, SwitchB, and SwitchC, connect physical
member ports using SFP stack cables as shown in Figure 4-10, and then power on
the three switches.
NOTE
● Run the save command to save the configurations before you power off the switches.
● To ensure that a stack can be set up successfully, you are advised to perform operations
in the following sequence. To specify a member switch as the master switch, power on
that switch first. In this example, SwitchA becomes the master switch after you
complete the following operations.
1. Power off SwitchA, SwitchB, and SwitchC.
2. Connect SwitchA and SwitchB with a stack cable.
3. Power on and start SwitchA and then power on SwitchB.
4. Check whether SwitchA and SwitchB set up a stack successfully. For details, see step
4.
5. Connect SwitchC to SwitchB and SwitchA using stack cables and then power on
SwitchC.
6. Check whether SwitchA, SwitchB, and SwitchC set up a stack successfully. For details,
see step 4.
<SwitchA> system-view
[SwitchA] sysname Stack
[Stack] display stack
Stack topology type: Ring
Stack system MAC: xxxx-xxxx-xxx8
MAC switch delay time: never
Stack reserved vlanid : 4093
Slot Role Mac address Priority Device type
-------------------------------------------------------------
0 Master xxxx-xxxx-xxx8 200 S3328TP-EI
1 Standby xxxx-xxxx-xxx1 100 S3328TP-EI
2 Slave xxxx-xxxx-xxx5 100 S3328TP-EI
# Create an Eth-Trunk on SwitchD and configure the ports connected to the stack
as Eth-Trunk member ports.
<Quidway> system-view
[Quidway] sysname SwitchD
[SwitchD] interface eth-trunk 10
[SwitchD-Eth-Trunk10] trunkport ethernet 0/0/1
[SwitchD-Eth-Trunk10] trunkport ethernet 0/0/2
[SwitchD-Eth-Trunk10] trunkport ethernet 0/0/3
[SwitchD-Eth-Trunk10] return
----End
Configuration Files
● Stack configuration file (the stack configuration is written to the flash
memory instead of the configuration file)
#
sysname Stack
#
interface Eth-Trunk10
#
interface Ethernet0/0/5
eth-trunk 10
#
interface Ethernet1/0/5
eth-trunk 10
#
interface Ethernet2/0/5
eth-trunk 10
#
return
Networking Requirements
A new enterprise network needs to provide sufficient ports for access devices, and
the network structure should be simple to facilitate configuration and
management.
As shown in Figure 4-11, SwitchA, SwitchB, and SwitchC need to set up a stack in
a ring topology and connect to SwitchD through an inter-device Eth-Trunk.
SwitchA, SwitchB, and SwitchC are the master, standby, and slave switches
respectively, with stack IDs of 0, 1, and 2 and stack priorities of 200, 100, and 100.
As the three switches function as one logical device on the network, the number
of ports is increased and network management and maintenance are simplified.
In this example, S5300-LIs set up a stack.
Configuration Roadmap
1. Configure logical stack ports and add physical member ports to the
corresponding logical stack ports to enable packet forwarding between
member switches.
2. Configure stack IDs and stack priorities for member switches to facilitate
device management and identification.
3. Power off SwitchA, SwitchB, and SwitchC, connect physical member ports
using SFP+ stack cables, and then power on the three switches.
4. Configure an inter-device Eth-Trunk to increase reliability and uplink
bandwidth.
5. Configure dual-active detection (DAD) in relay mode to ensure network
availability when the stack splits.
Procedure
Step 1 Configure logical stack ports and add physical member ports to them.
NOTE
Interface stack-port 0/1 of one switch must be connected to interface stack-port 0/2 of
another switch. Otherwise, the stack cannot be set up.
<Quidway> system-view
[Quidway] sysname SwitchA
[SwitchA] stack port interface gigabitethernet 0/0/27 enable
[SwitchA] stack port interface gigabitethernet 0/0/28 enable
[SwitchA] interface stack-port 0/1
[SwitchA-stack-port0/1] port member-group interface gigabitethernet 0/0/27
[SwitchA-stack-port0/1] quit
[SwitchA] interface stack-port 0/2
[SwitchA-stack-port0/2] port member-group interface gigabitethernet 0/0/28
[SwitchA-stack-port0/2] quit
Step 2 Configure stack IDs and stack priorities. The default stack ID is 0, and the default
stack priority is 100.
[SwitchA] stack slot 0 priority 200 //Set the stack priority of the master switch to 200, which is larger
than those of other member switches, and use the default stack ID 0.
[SwitchB] stack slot 0 renumber 1 //Use the default stack priority 100 and set the stack ID to 1.
[SwitchC] stack slot 0 renumber 2 //Use the default stack priority 100 and set the stack ID to 2.
Step 3 Turn off power supplies of SwitchA, SwitchB, and SwitchC, connect physical
member ports using SFP+ stack cables as shown in Figure 4-12, and then power
on the three switches.
NOTE
● Run the save command to save the configurations before you power off the switches.
● To ensure that a stack can be set up successfully, you are advised to perform operations
in the following sequence. To specify a member switch as the master switch, power on
that switch first. In this example, SwitchA becomes the master switch after you
complete the following operations.
1. Power off SwitchA, SwitchB, and SwitchC.
2. Connect SwitchA and SwitchB with a stack cable.
3. Power on and start SwitchA and then power on SwitchB.
4. Check whether SwitchA and SwitchB set up a stack successfully. For details, see step
4.
5. Connect SwitchC to SwitchB and SwitchA using stack cables and then power on
SwitchC.
6. Check whether SwitchA, SwitchB, and SwitchC set up a stack successfully. For details,
see step 4.
● The S6300-EI uses the mode status indicator to show the stack and speed modes. After you
press the MODE button, the indicator is steady red and off after 45 seconds, indicating that
the switch enters the stack mode.
● The S5300-LI and S5310-EI have an independent stack mode indicator (STCK indicator).
After you press the MODE button, the indicator is steady green or blinking and off after 45
seconds, indicating that the switch enters the stack mode.
# Create an Eth-Trunk on SwitchD and configure the ports connected to the stack
as Eth-Trunk member ports.
<Quidway> system-view
[Quidway] sysname SwitchD
[SwitchD] interface eth-trunk 10
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/1
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/2
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/3
[SwitchD-Eth-Trunk10] quit
Step 7 Configure DAD in relay mode on SwitchD and configure SwitchD as the relay
agent.
# In the stack, configure DAD in relay mode on the inter-device Eth-Trunk.
[Stack] interface eth-trunk 10
[Stack-Eth-Trunk10] dual-active detect mode relay
[Stack-Eth-Trunk10] return
----End
Configuration Files
● Stack configuration file (the stack configuration is written to the flash
memory instead of the configuration file)
#
sysname Stack
#
interface Eth-Trunk10
dual-active detect mode relay
#
interface GigabitEthernet0/0/5
eth-trunk 10
#
interface GigabitEthernet1/0/5
eth-trunk 10
#
interface GigabitEthernet2/0/5
eth-trunk 10
#
return
● SwitchD configuration file
#
sysname SwitchD
#
interface Eth-Trunk10
dual-active relay
#
interface GigabitEthernet0/0/1
eth-trunk 10
#
interface GigabitEthernet0/0/2
eth-trunk 10
#
interface GigabitEthernet0/0/3
eth-trunk 10
#
return
Networking Requirements
A new enterprise network needs to provide sufficient ports for access devices, and
the network structure should be simple to facilitate configuration and
management.
As shown in Figure 4-13, SwitchA, SwitchB, and SwitchC need to set up a stack in
a ring topology and connect to SwitchD through an inter-device Eth-Trunk.
SwitchA, SwitchB, and SwitchC are the master, standby, and slave switches
respectively, with stack IDs of 0, 1, and 2 and stack priorities of 200, 100, and 100.
As the three switches function as one logical device on the network, the number
of ports is increased and network management and maintenance are simplified.
In this example, S5300-28X-LI-AC set up a stack.
Configuration Roadmap
1. Configure logical stack ports and add physical member ports to the
corresponding logical stack ports to enable packet forwarding between
member switches.
2. Configure stack IDs and stack priorities for member switches to facilitate
device management and identification.
3. Turn off power supplies of SwitchA, SwitchB, and SwitchC, connect physical
member ports using SFP+ stack cables, and then power on the three switches.
4. Configure an inter-device Eth-Trunk to increase reliability and uplink
bandwidth.
5. Configure multi-active detection (MAD) in relay mode to ensure network
availability when the stack splits.
Procedure
Step 1 Configure logical stack ports and add physical member ports to them.
NOTE
Interface stack-port 0/1 of one switch must be connected to interface stack-port 0/2 of
another switch. Otherwise, the stack cannot be set up.
Step 2 Configure stack IDs and stack priorities. The default stack ID is 0, and the default
stack priority is 100.
[SwitchA] stack slot 0 priority 200 //Set the stack priority of the master switch to 200, which is larger
than those of other member switches, and use the default stack ID 0.
[SwitchB] stack slot 0 renumber 1 //Use the default stack priority 100 and set the stack ID to 1.
[SwitchC] stack slot 0 renumber 2 //Use the default stack priority 100 and set the stack ID to 2.
Step 3 Turn off power supplies of SwitchA, SwitchB, and SwitchC, connect physical
member ports using SFP+ stack cables as shown in Figure 4-14, and then power
on the three switches.
NOTE
● Run the save command to save the configurations before you power off the switches.
● To ensure that a stack can be set up successfully, you are advised to perform operations
in the following sequence. To specify a member switch as the master switch, power on
that switch first. In this example, SwitchA becomes the master switch after you
complete the following operations.
1. Power off SwitchA, SwitchB, and SwitchC.
2. Connect SwitchA and SwitchB with a stack cable.
3. Power on and start SwitchA and then power on SwitchB.
4. Check whether SwitchA and SwitchB set up a stack successfully. For details, see step
4.
5. Connect SwitchC to SwitchB and SwitchA using stack cables and then power on
SwitchC.
6. Check whether SwitchA, SwitchB, and SwitchC set up a stack successfully. For details,
see step 4.
NOTE
● The S5300-SI, S5300-EI, S5300-HI, S6300-EI use the same mode status indicator to show the
stack and speed modes. After you press the MODE button, the indicator is steady red and off
after 45 seconds, indicating that the switch enters the stack mode.
● The S5332-H, S6320-HI, and S6330-H have an independent stack master/slave indicator to
show the MST. If the indicator is off, the switch is not a stack master. If the indicator is
steady green, the switch is a stack master or standalone switch.
● Other models have an independent stack mode indicator (STCK indicator). After you press
the MODE button, the indicator is steady green or blinking and off after 45 seconds,
indicating that the switch enters the stack mode.
# Create an Eth-Trunk on SwitchD and configure the ports connected to the stack
as Eth-Trunk member ports.
<Quidway> system-view
[Quidway] sysname SwitchD
[SwitchD] interface eth-trunk 10
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/1
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/2
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/3
[SwitchD-Eth-Trunk10] quit
Step 7 Configure MAD in relay mode on SwitchD and configure SwitchD as the relay
agent.
# In the stack, configure MAD in relay mode on the inter-device Eth-Trunk.
[Stack] interface eth-trunk 10
[Stack-Eth-Trunk10] mad detect mode relay
[Stack-Eth-Trunk10] return
----End
Configuration Files
● Stack configuration file (the stack configuration is written to the flash
memory instead of the configuration file)
#
sysname Stack
#
interface Eth-Trunk10
mad detect mode relay
#
interface GigabitEthernet0/0/5
eth-trunk 10
#
interface GigabitEthernet1/0/5
eth-trunk 10
#
interface GigabitEthernet2/0/5
eth-trunk 10
#
return
Overview
Service port connection allows member switches to be connected using service
ports, without requiring dedicated stack cards.
Precautions
● Connect member switches using dedicated stack cables based on the
following rules:
– Connect the switches in sequence from top to bottom.
– Ensure that all logical stack ports of the top switch are connected to the
master ends of cables, all logical stack ports of the bottom switch are
connected to the slave ends of cables, and two logical stack ports of the
intermediate switch are connected to the master and slave ends
respectively.
– After the switches have been connected using dedicated stack cables,
they automatically set up a stack and their stack IDs as well as stack
roles are automatically assigned.
– If the switches are not connected in a ring topology, you only need to
ensure that logical stack port 1 of the local switch is connected to logical
stack port 2 of the remote switch. In this situation, these switches can set
up a stack, but their master and standby roles and stack IDs are
randomly generated.
● Ensure that there are no service configurations on the ports that have
dedicated stack cables connected. Otherwise, these ports cannot
automatically become stack ports and the switches cannot set up a stack.
– On ASs in an SVF system, ensure that there are no other configurations
except the shutdown and stp root-protection command configurations
on ports.
– On other switches, ensure that there are no other configurations except
the shutdown command configuration on ports.
● If logical stack port numbers have been manually configured before dedicated
stack cables are connected, the configured port numbers still take effect after
the cables are connected. You need to connect these ports based on the
configured port numbers. If logical stack port numbers are not manually
configured, corresponding logical stack port numbers will be automatically
generated after dedicated stack cables are connected. To view logical stack
ports of ports supporting dedicated stack cables and master as well as slave
ends of the cables connected to these ports, run the display stack port auto-
cable-info command.
Networking Requirements
An enterprise network needs to provide sufficient ports for access devices, and the
network structure should be simple to facilitate configuration and management.
As shown in Figure 4-15, Switches A to C set up a stack in a ring topology and
connect to SwitchD through an inter-chassis Eth-Trunk. To reduce the
configuration, Switches A to C set up a stack using dedicated stack cables. In the
stack, SwitchA needs to function as the master switch, Switch B as the standby
switch, and SwitchC as the slave switch.
This example describes how to use S5320-28P-PWR-LI-AC switches to set up a
stack.
Configuration Roadmap
1. Power off SwitchA, SwitchB, and SwitchC to ensure security.
2. Connect the switches using dedicated stack cables based on dedicated stack
cable connection rules.
3. Power on these switches in the following sequence to ensure that SwitchA,
SwitchB, and SwitchC become the master switch, standby switch, and slave
switch respectively.
4. Save the stack configuration automatically generated for dedicated cable
stacking to the flash memory. This ensures that the stack configuration still
takes effect when these cables are removed or other cables are connected.
5. Configure an inter-chassis Eth-Trunk to increase reliability and uplink
bandwidth.
6. Configure multi-active detection in relay mode to ensure network availability
when the stack splits.
Procedure
Step 1 Power off SwitchA, SwitchB, and SwitchC.
Step 2 Power off SwitchA, SwitchB, and SwitchC and then connect them using dedicated
stack cables as shown in Figure 4-16.
NOTE
● Logical stack port 1 of the local switch must be connected to logical stack port 2 of the
adjacent switch. Otherwise, these switches cannot set up a stack.
● All logical stack ports of SwitchA must be connected to the master ends of dedicated stack
cables, and all logical stack ports of SwitchC must be connected to the slave ends of these
cables.
The preceding power-on sequence can guarantee only roles of these switches but
not their slot IDs. The following assumes that SwitchA, SwitchB, and SwitchC use
automatically generated slot IDs 0, 1, and 2 respectively.
Press the mode switching (MODE) button on any member switch to change the
mode status indicator to the stack mode.
● If the mode status indicators on all member switches change to the stack
mode, a stack has been set up successfully.
● If the mode status indicator on any member switch does not change to the
stack mode, a stack has not been set up.
NOTE
● The S5300-SI, S5300-EI, S5300-HI, S6300-EI use the same mode status indicator to show the
stack and speed modes. After you press the MODE button, the indicator is steady red and off
after 45 seconds, indicating that the switch enters the stack mode.
● The S5332-H, S6320-HI, and S6330-H have an independent stack master/slave indicator to
show the MST. If the indicator is off, the switch is not a stack master. If the indicator is
steady green, the switch is a stack master or standalone switch.
● Other models have an independent stack mode indicator (STCK indicator). After you press
the MODE button, the indicator is steady green or blinking and off after 45 seconds,
indicating that the switch enters the stack mode.
Step 5 Save the stack configuration that is automatically generated for dedicated cable
stacking to the flash memory.
# After verifying that a stack has been set up, save the stack configuration that is
automatically generated for dedicated cable stacking to the flash memory.
[Stack] save stack configuration
Warning: This operation will save all stack configurations to flash. Are you sure you want to continue? [Y/
N]:y
# Create an Eth-Trunk on SwitchD and configure the ports connected to the stack
as Eth-Trunk member ports.
<Quidway> system-view
[Quidway] sysname SwitchD
[SwitchD] interface eth-trunk 10
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/1
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/2
[SwitchD-Eth-Trunk10] trunkport gigabitethernet 0/0/3
[SwitchD-Eth-Trunk10] quit
Step 8 Configure MAD in relay mode on SwitchD and configure SwitchD as the relay
agent.
# In the stack, configure MAD in relay mode on the inter-chassis Eth-Trunk.
[Stack] interface eth-trunk 10
[Stack-Eth-Trunk10] mad detect mode relay
[Stack-Eth-Trunk10] return
----End
Configuration Files
● Stack configuration file (the stack configuration is written to the flash
memory instead of the configuration file)
#
sysname Stack
#
interface Eth-Trunk10
d. After the configuration is complete, check whether SwitchC has the same
stack configuration as SwitchA. If so, power off SwitchC.
e. (Optional) To prevent OSPF, BGP, or LDP flapping during an master/
backup switchover in a stack, configure graceful restart (GR) for the
corresponding protocol. For details, see the configuration guide of the
corresponding protocol.
f. Run the display stack command to check whether SwitchA is the master
switch. If so, run the slave switchover command to perform an active/
standby switchover in the stack. If not, go to the next step.
<HUAWEI> display switchover state //Check whether the active/standby switchover
conditions are met.
Slot 0 HA FSM State(master): realtime or routine backup. //The switchover can be performed
only in this state.
Slot 1 HA FSM State(slave): receiving realtime or routine data.
<HUAWEI> system-view
[HUAWEI] slave switchover enable //Enable the active/standby switchover.
[HUAWEI] slave switchover //Perform an active/standby switchover.
Warning: This operation will switch the slave board to the master board. Continue? [Y/N]:y
After an active/standby switchover is performed, the master switch will
restart. After the switch restarts and joins the stack again, go to the next
step. To check whether the switch has joined the stack again, run the
display stack command.
g. Power off and remove SwitchA.
h. Install SwitchC and connect cables to its service ports, stack ports, and
ports that have dual-active detection (DAD) configured.
i. Power on SwitchC so that SwitchC joins the stack as a new member. Run
the display stack command to check whether SwitchC can set up a stack
with SwitchB.
j. After SwitchC and SwitchB set up a stack, run the display stack
configuration and display stack port commands to check the stack
configuration and interface status. Ensure that the stack configuration is
the same as that used before the device replacement and that interfaces
become Up normally.
k. After confirming all services are normal, run the save command to save
the stack configuration.
l. If the current master and standby switches are different from those
before the device replacement, perform an active/standby switchover.
● Replace one member switch in a stack of three or more member switches
(in a ring topology).
In a stack set up by three or more member switches in a ring topology, the
device replacement procedure is similar to that in a stack of two member
switches. For details, see Replace one member switch in a stack of two
member switches.
● Replace one member switch in a stack of three or more member switches
(in a chain topology).
In a stack set up by three or more member switches in a chain topology, the
replacement procedure of edge switches on both ends is similar to that in a
stack of two member switches. For details, see Replace one member switch
in a stack of two member switches. To replace an intermediate switch,
change the stack connection topology to the ring topology and then replace
the switch according to Replace one member switch in a stack of two
member switches. The procedure is as follows:
a. On edge switches on both ends, create a logical stack port and add
member ports into the logical stack port, and then connect these ports
using cables.
<HUAWEI> system-view
[HUAWEI] interface stack-port 1/1 //Create a logical stack port.
[HUAWEI-stack-port1/1] port interface gigabitethernet 1/0/46 enable //Add a member
port to the logical stack port.
After cables are connected, run the display stack command to check
whether the stack connection topology is changed to the ring topology.
b. After the stack connection topology changes to ring topology, replace the
switch according to Replace one member switch in a stack of two
member switches.
c. To restore the stack connection topology to chain topology after the
replacement, remove the stack cables connected in step 1.
Check information about the stack members with the stack IDs.
The stack IDs need to be changed according to the following rules: After the
change, check whether the change is correct based on the MAC addresses of the
devices.
● Slot 3 → Slot 1
● Slot 1 → Slot 2
● Slot 2 → Slot 3
NOTE
To change the stack IDs, you need to restart the devices, which interrupts services. Therefore,
perform this operation in a specified period.
Procedure
Step 1 Shut down the uplink and downlink ports of the stack to isolate the stack from
the network.
<Stack> system-view
[Stack] interface gigabitethernet 3/0/8
[Stack-GigabitEthernet3/0/8] shutdown
[Stack-GigabitEthernet3/0/8] quit
[Stack] interface gigabitethernet 1/0/9
[Stack-GigabitEthernet1/0/9] shutdown
[Stack-GigabitEthernet1/0/9] quit
[Stack] interface gigabitethernet 2/0/5
[Stack-GigabitEthernet2/0/5] shutdown
[Stack-GigabitEthernet2/0/5] quit
[Stack] interface gigabitethernet 3/0/6
[Stack-GigabitEthernet3/0/6] shutdown
[Stack-GigabitEthernet3/0/6] quit
Step 2 After the stack IDs are changed, the configurations of the interfaces with the
original stack IDs will be lost. Therefore, you need to perform the same
configurations on the new interfaces before changing the stack IDs.
For example: The configurations of the interfaces with the original stack IDs are as
follows:
#
interface GigabitEthernet3/0/6
description ToPC
port link-type access
port default vlan 10
#
interface GigabitEthernet3/0/8
eth-trunk 10
#
interface GigabitEthernet1/0/9
eth-trunk 10
#
interface GigabitEthernet2/0/5
description ToIPPhone-01
Step 3 Change the stack IDs, save the configurations, and restart the switches.
[Stack] stack slot 3 renumber 1
Info: The assigned slot ID already exists in the stack system.
Warning: All the configurations related to the slot ID will be lost after the slot ID is
modified.
Do not frequently modify the slot ID because it will make the stack split. Continue? [Y/
N]:y
Info: Stack configuration has been changed, and the device needs to restart to make the configuration
effective.
[Stack] stack slot 1 renumber 2
Info: The assigned slot ID already exists in the stack system.
Warning: All the configurations related to the slot ID will be lost after the slot ID is
modified.
Do not frequently modify the slot ID because it will make the stack split. Continue? [Y/
N]:y
Info: Stack configuration has been changed, and the device needs to restart to make the configuration
effective.
[Stack] stack slot 2 renumber 3
Info: The assigned slot ID already exists in the stack system.
Warning: All the configurations related to the slot ID will be lost after the slot ID is
modified.
Do not frequently modify the slot ID because it will make the stack split. Continue? [Y/
N]:y
Info: Stack configuration has been changed, and the device needs to restart to make the configuration
effective.
[Stack] quit
<Stack> save
The current configuration will be written to flash:/vrpcfg.zip.
Are you sure to continue?[Y/N]y
Now saving the current configuration to the slot 3.........
Save the configuration successfully.
Now saving the current configuration to the slot 1.
Save the configuration successfully.
Now saving the current configuration to the slot 2.
Save the configuration successfully.
<Stack> reboot
Info: The system is now comparing the configuration, please wait...................
Info: If want to reboot with saving diagnostic information, input 'N' and then execute 'reboot save
diagnostic-information'.
System will reboot! Continue?[Y/N]:y
Step 4 After the restart is complete, check whether the stack status, stack IDs, and
interface configurations are correct. If the configurations on the interfaces are
incorrect, reconfigure the interfaces.
Step 5 If the configurations are correct, enable the uplink and downlink ports of the
stack.
<Stack> system-view
[Stack] interface gigabitethernet 1/0/8
[Stack-GigabitEthernet1/0/8] undo shutdown
[Stack-GigabitEthernet1/0/8] quit
[Stack] interface gigabitethernet 2/0/9
[Stack-GigabitEthernet2/0/9] undo shutdown
[Stack-GigabitEthernet2/0/9] quit
[Stack] interface gigabitethernet 3/0/5
[Stack-GigabitEthernet3/0/5] undo shutdown
[Stack-GigabitEthernet3/0/5] quit
[Stack] interface gigabitethernet 1/0/6
[Stack-GigabitEthernet1/0/6] undo shutdown
[Stack-GigabitEthernet1/0/6] quit
----End
4.2.1.2 Software and Hardware Support for S9300 CSS Card Clustering
Table 4-4 Software and Hardware Support for S9306&S9312 CSS Card Clustering
Device Model ● S9306
● S9312
CSS Card and CSS card: LE0D0VSTSA00 CSS card: LE1D2VS04000 (CSS
Installation Slot (All ports on the CSS ports on the CSS cards must
cards must be have at least one cable
connected.) connected and ports on both
Installation slot: subcard ends of the cable must use the
slots of LE0MSRUA (non- same port number.)
VER.A), LE0DSRUA, and Installation slot: subcard slots of
LE0D00SRUB00 (non- LSS3SRUHA100,
VER.A) LE1D2SRUH000,
LE1D2SRUH100,
CSS card and MPU models are
LE1D2SRUH002,
abbreviated to VSTSA, SRUA, and
LSS3SRUHD000, and
SRUB respectively. LE1D2SRUE000
CSS card and MPU models are abbreviated
to VS04, SRUHA1, SRUH, SRUH1, and SRUE
respectively.
Number of CSS 2 2
Cards
Supported by
Each Chassis
License No
Required
Table 4-5 Software and Hardware Support for S9310 CSS Card Clustering
Device Model S9310
CSS Card and CSS cards are integrated into MPUs (LE1D2SRUKC00 or
Installation Slot LE1D2SRUKC01) and do not need to be installed.
CSS cards are integrated into SFUs (LE1D2SFUK000) and do
not need to be installed.
MPU and SFU models are abbreviated to SRUK and SFUK respectively.
Number of CSS 4
Cards
Supported by
Each Chassis
License No
Required
4.2.1.3 Software and Hardware Support for S9300E CSS Card Clustering
Device Model ● S9306E
● S9312E
CSS Card and CSS card: LE2D2VS08000 (Eight ports on a CSS card are
Installation Slot divided into two groups, each of which must have at least
one cable connected.)
Installation slot: subcard slot of LE2D2SRUC000
CSS card and MPU models are abbreviated to VS08 and SRUC respectively.
Number of CSS 2
Cards
Supported by
Each Chassis
License No
Required
4.2.1.4 Software and Hardware Support for S9310X CSS Card Clustering
Device Model S9310X
CSS Card and CSS cards are integrated into MPUs (LX1D2MFUXC00) and
Installation Slot do not need to be installed.
CSS cards are integrated into SFUs (LX1D2SFUX000) and do
not need to be installed.
MPU and SFU models are abbreviated to MFUX and SFUX respectively.
Number of CSS 4
Cards
Supported by
Each Chassis
License No
Required
4.2.1.5 Software and Hardware Support for S9300 and S9300X Service Port
Clustering
Table 4-6 S9306 and S9312 service port clustering (using SRUA/SRUB/SRUE/
SRUE1/SRUH/SRUHD/SRUH1/SRUHA1 MPU)
LPU ● LE2D2X08SED4 LE1D2L02QFC0
Model ● LE2D2X08SED5
● LE0DX12XSA00
● LE0DX16SFC00
● LE0DX40SFC00
● LE1D2X32SSC0
● LSS3X32SA1E0
● LE1D2X16SSC2
● LSS3X16SA1E0
● LE1D2X08SSC0
● LE1D2X12SSC0
Hardware ● Two S9306, two S9312, or one S9306 and one S9312 can set up
Configura a CSS.
tion ● SRUs in the same chassis must be the same model. To set up a
stack, the local and remote chassis must use SRUs of the same
model, use SRUA and SRUB respectively, or use SRUH and SRUE
respectively, or use SRUH1 and SRUE respectively, or use SRUH
and SRUH1 respectively(both chassis must run V200R010C00 or
a later version).
● Each chassis can have at most two LPUs for CSS connection. It is
recommended that you use the same type of LPUs in a chassis
for CSS connection. The two chassis must use the same type of
ports for CSS connection, for example, 10GE SFP+ optical ports.
● Each LPU allows only one logical CSS port. Each logical CSS port
supports a maximum of 32 physical member ports.
● Some ports on an LPU can function as CSS ports, while other
ports on the LPU function as service ports.
● A CSS can be set up as long as a logical CSS port has one CSS
member port in Up state.
● Ports do not support the CSS function after being split.
License Yes
Required
Table 4-7 S9306 and S9312 service port clustering (using SRUHX1 MPU)
LPU ● LST3X36SX6 LSS3M24VX6E0 ● LST3C02BX ● LST3C06HX6
Model E0 (MultiGE ports) 6E0 (40GE S0
● LST3X24SX6 ports) ● LST3C06HX6
E0 ● LST3L12QX E0
● LST3X24BX6 6E0 ● LST3C02BX6E
E0 0 (100GE
● LST3X24BX6 ports)
S0
● LST3X48SX6
E0
● LST3X48SX6
S0
Hardw ● Two S9306, two S9312, or one S9306 and one S9312 can set up a
are CSS.
Config ● The MPUs in the two chassis must be the SRUHX1.
uratio
n ● Each chassis can have at most two LPUs for CSS connection. It is
recommended that you use the same type of LPUs in a chassis for
CSS connection. The two chassis must use the same type of ports
for CSS connection, for example, 10GE SFP+ optical ports.
● Each LPU allows only one logical CSS port. Each logical CSS port
supports a maximum of 32 physical member ports.
● Some ports on an LPU can function as CSS ports, while other ports
on the LPU function as service ports.
● A CSS can be set up as long as a logical CSS port has one CSS
member port in Up state.
● Ports do not support the CSS function after being split.
License No
Requir
ed
License Yes
Required
Hardw ● A CSS can be set up between two S9300X-4 switches, between one
are S9300X-4 and one S9300X-8, between two S9300X-8 switches,
Config between two S9300X-12 switches, between one S9300X-4 and one
uration S9300X-12, or between one S9300X-8 and one S9300X-12.
● Each chassis can have at most two LPUs for CSS connection. It is
recommended that you use the same type of LPUs in a chassis for
CSS connection. The two chassis must use the same type of ports
for CSS connection, for example, 10GE SFP+ optical ports.
● Each LPU allows only one logical CSS port. Each logical CSS port
supports a maximum of 32 physical member ports.
● Some ports on an LPU can function as CSS ports, while other ports
on the LPU function as service ports.
● A CSS can be set up as long as a logical CSS port has one CSS
member port in Up state.
● Ports do not support the CSS function after being split.
License No
Require
d
4.2.1.6 Software and Hardware Support for S9300E Service Port Clustering
Device ● S9306E
Model ● S9312E
● Each chassis can have at most two LPUs for CSS connection.
It is recommended that you use the same type of LPUs in a
chassis for CSS connection. The two chassis must use the
same type of ports for CSS connection, for example, 10GE
SFP+ optical ports.
● Each LPU allows only one logical CSS port. Each logical CSS
port supports a maximum of 32 physical member ports.
● Some ports on an LPU can function as CSS ports, while other
ports on the LPU function as service ports.
● A CSS can be set up as long as a logical CSS port has one CSS
member port in Up state.
License Yes
Required
Overview of CSS
A Cluster Switch System (CSS), also called a cluster, is a logical switch consisting
of two clustering-capable switches. It provides high forwarding performance and
high network reliability and scalability, while simplifying network management.
● High reliability: Member switches in a CSS work in redundancy mode. Link
redundancy can also be implemented between member switches through link
aggregation.
● High scalability: Switches can set up a CSS to increase the number of ports,
bandwidth, and packet processing capabilities.
● Simplified configuration and management: After two switches set up a CSS,
they are virtualized into one device. You can log in to the CSS from either
member switch to configure and manage the entire CSS.
In CSS card connection mode, member switches are connected using CSS cards on
MPUs or SFUs and cluster cables. Compared with the service port connection
mode, the CSS card connection mode does not occupy common service ports, is
easy to configure, ensures high stability and low latency, but has higher hardware
requirements.
1+N backup of MPUs enables a CSS to run stably as long as one MPU of any
chassis in the CSS is working normally. Compared with the service port connection
mode in which each chassis must have at least one MPU working normally, CSS2
is more reliable. Compared with the MPU-mounted CSS card connection mode in
which each chassis must have two MPUs installed, CSS2 is more flexible.
After a CSS is set up, you are advised to perform the following configurations:
Guidelines
● After two switches set up a CSS, the following features cannot be configured
in the CSS:
– Synchronous Ethernet clock
– Precision Time Protocol (PTP) (IEEE 1588)
– Web system configuration (In V200R001C00, the web system is not
supported. In V200R002C00 and later versions, you can log in to the CSS
through the web system to perform configurations.)
● When configuring MAD, focus on the differences in the command syntax
between V200R002C00 (and earlier versions) and V200R003C00 (and later
versions). In V200R002C00 and earlier versions, the split detection function is
called dual-active detection (DAD).
● Regardless of how many MAD links exist, ports of the standby switch will be
shut down and no longer forward service packets as long as the CSS splits.
Networking Requirements
An enterprise needs to build a network that has a reliable core layer and simple
structure to facilitate configuration and management.
To meet requirements of the enterprise, core switches SwitchA and SwitchB set up
a CSS in CSS card connection mode. SwitchA is the master switch, and SwitchB is
the standby switch. Figure 4-18 shows the network topology. Aggregation
switches connect to the CSS through Eth-Trunks, and the CSS connects to the
upstream network through an Eth-Trunk. In this example, the core switches are
the S9306 switches.
Configuration Roadmap
The configuration roadmap is as follows:
Procedure
Step 1 Install hardware modules.
The following describes only the rule for connecting cluster cables between two
member switches. If you also need to install MPUs and CSS cards and learn about
installation details, see the Switch Cluster Setup Guide.
Select the required connection diagram based on the device model and CSS card
model to connect cluster cables.
NOTE
Follow these rules when connecting VSTSA CSS cards: Each VSTSA CSS card has four ports.
All ports with the same port number and color must be connected, as shown in the
preceding figure. For example, port 1 in blue on the left chassis must be connected to port
1 in blue on the right chassis.
The CSS set up using VSTSA CSS cards allows at most one faulty cluster cable.
NOTE
Figure 4-21 S9310 and S9310X integrated CSS card connections (using 4*10G
ports and 40G ports)
NOTE
Follow these rules when connecting S9310 and S9310X integrated CSS cards:
● On the S9310 and S9310X, the local and peer chassis can be connected using either
MPUs or SFUs or both MPUs and SFUs. MPUs or SFUs in one chassis can only be
connected to the same type of cards (MPUs or SFUs) in the other chassis.
● MPU-integrated and SFU-integrated CSS cards have two types of ports: 4*10G ports
and 40G port. 10G ports with the same port number must be connected, as shown in
the preceding figure. For example, port 1 in blue on the left chassis must be connected
to port 1 in blue on the right chassis.
● The two chassis can set up a CSS as long as they are connected by one cluster cable.
To ensure reliability, it is advised to connect multiple cluster cables. Ensure that all
SFUs are connected using cluster cables.
● To support 1+N MPU backup, ensure that SFUs are connected using cluster cables.
Step 2 Configure the CSS connection mode, CSS ID, and CSS priority.
# Configure the CSS function on SwitchA. Retain the default CSS connection mode
(CSS card connection) and the default CSS ID 1, and set the CSS priority to 100.
<Quidway> system-view
[Quidway] sysname SwitchA
[SwitchA] set css priority 100
# Configure the CSS function on SwitchB. Retain the default CSS connection mode
(CSS card connection), and set the CSS ID to 2 and CSS priority to 10.
<Quidway> system-view
[Quidway] sysname SwitchB
[SwitchB] set css id 2
[SwitchB] set css priority 10
NOTE
To use two S9310s or S9310Xs to establish a CSS, you need to run the css port media-type
command to set the CSS port type to the actual port type used for cluster connections. You can
run the display css status [ saved ] command to check the current and saved CSS port types
based on the CSS port media-type field.
NOTE
After the configuration is complete, run the display css status saved command to check
the CSS configuration.
The command output shows the card status of both member switches, indicating
that the CSS has been set up successfully.
# Check whether CSS links are normal.
<SwitchA> display css channel
Chassis 1 || Chassis 2
================================================================================
Num [SRUB HG] [VSTS Port(Status)] || [VSTS Port(Status)] [SRUB HG]
1 1/7 1/15 -- 1/7/0/1(UP 16G) ---||--- 2/7/0/4(UP 16G) -- 2/8 1/14
2 1/7 0/15 -- 1/7/0/3(UP 16G) ---||--- 2/8/0/2(UP 16G) -- 2/7 0/14
3 1/7 1/14 -- 1/8/0/4(UP 16G) ---||--- 2/7/0/1(UP 16G) -- 2/7 1/15
4 1/7 0/14 -- 1/8/0/2(UP 16G) ---||--- 2/8/0/3(UP 16G) -- 2/8 0/15
5 1/8 1/15 -- 1/8/0/1(UP 16G) ---||--- 2/8/0/4(UP 16G) -- 2/7 1/14
6 1/8 0/15 -- 1/8/0/3(UP 16G) ---||--- 2/7/0/2(UP 16G) -- 2/8 0/14
7 1/8 1/14 -- 1/7/0/4(UP 16G) ---||--- 2/8/0/1(UP 16G) -- 2/8 1/15
8 1/8 0/14 -- 1/7/0/2(UP 16G) ---||--- 2/7/0/3(UP 16G) -- 2/7 0/15
The command output shows that all the CSS links are Up, indicating that the CSS
has been set up successfully.
Step 5 Configure Eth-Trunks between the CSS and its upstream and downstream devices.
# Configure an Eth-Trunk in the CSS and add uplink ports to the Eth-Trunk.
<SwitchA> system-view
[SwitchA] sysname CSS //Rename the CSS.
[CSS] interface eth-trunk 10
[CSS-Eth-Trunk10] quit
[CSS] interface gigabitethernet 1/1/0/4
[CSS-GigabitEthernet1/1/0/4] eth-trunk 10
[CSS-GigabitEthernet1/1/0/4] quit
[CSS] interface gigabitethernet 2/1/0/4
[CSS-GigabitEthernet2/1/0/4] eth-trunk 10
[CSS-GigabitEthernet2/1/0/4] quit
# Configure an Eth-Trunk in the CSS and add the downlink ports connected to
SwitchC to the Eth-Trunk.
[CSS] interface eth-trunk 20
[CSS-Eth-Trunk20] quit
[CSS] interface gigabitethernet 1/1/0/3
[CSS-GigabitEthernet1/1/0/3] eth-trunk 20
[CSS-GigabitEthernet1/1/0/3] quit
[CSS] interface gigabitethernet 2/1/0/5
[CSS-GigabitEthernet2/1/0/5] eth-trunk 20
[CSS-GigabitEthernet2/1/0/5] quit
# Configure an Eth-Trunk in the CSS and add the downlink ports connected to
SwitchD to the Eth-Trunk.
[CSS] interface eth-trunk 30
[CSS-Eth-Trunk30] quit
[CSS] interface gigabitethernet 1/1/0/5
[CSS-GigabitEthernet1/1/0/5] eth-trunk 30
[CSS-GigabitEthernet1/1/0/5] quit
[CSS] interface gigabitethernet 2/1/0/3
[CSS-GigabitEthernet2/1/0/3] eth-trunk 30
[CSS-GigabitEthernet2/1/0/3] return
Operate status: up
Step 6 Configure the MAD function. The following procedure configures MAD in relay
mode and configures SwitchC as the relay agent using the commands applicable
to V200R003C00 and later versions.
# In the CSS, configure MAD in relay mode for the inter-device Eth-Trunk.
<CSS> system-view
[CSS] interface eth-trunk 20
[CSS-Eth-Trunk20] mad detect mode relay //In V200R002C00 and earlier versions, the command is
dual-active detect mode relay.
[CSS-Eth-Trunk20] quit
[CSS] quit
----End
Configuration Files
● CSS configuration file
#
sysname CSS
#
interface Eth-Trunk10
#
interface Eth-Trunk20
mad detect mode relay
#
interface Eth-Trunk30
#
interface GigabitEthernet1/1/0/3
eth-trunk 20
#
interface GigabitEthernet1/1/0/4
eth-trunk 10
#
interface GigabitEthernet1/1/0/5
eth-trunk 30
#
interface GigabitEthernet2/1/0/3
eth-trunk 30
#
interface GigabitEthernet2/1/0/4
eth-trunk 10
#
interface GigabitEthernet2/1/0/5
eth-trunk 20
#
return
● SwitchC configuration file
#
sysname SwitchC
#
interface Eth-Trunk20
mad relay
#
interface GigabitEthernet1/0/1
eth-trunk 20
#
interface GigabitEthernet1/0/2
eth-trunk 20
#
return
● SwitchD configuration file
#
sysname SwitchD
#
interface Eth-Trunk30
#
interface GigabitEthernet1/0/1
eth-trunk 30
#
interface GigabitEthernet1/0/2
eth-trunk 30
#
return
● SwitchE configuration file
#
sysname SwitchE
#
interface Eth-Trunk10
#
interface GigabitEthernet1/0/1
eth-trunk 10
#
interface GigabitEthernet1/0/2
eth-trunk 10
#
return
In service port connection mode, member switches are connected using service
ports, without a need for CSS cards. The service ports must be configured as
physical member ports of logical CSS ports. Figure 4-22 shows physical member
ports and logical CSS ports in a CSS.
Compared with the CSS card connection mode, the service port connection mode
is more flexible but is complex to configure and needs to occupy service ports on
LPUs.
After a CSS is set up, you are advised to perform the following configurations:
● To simplify network configuration, increase uplink bandwidth, and improve
reliability, configure inter-device Eth-Trunks in the CSS, connect downstream
devices to the CSS in dual-homing mode, and add uplink and downlink ports
of the CSS to the Eth-Trunks.
● Configure the multi-active detection (MAD) function in the CSS. Two member
switches in a CSS use the same IP address and MAC address (CSS system MAC
address). Therefore, after the CSS splits, two CSSs using the same IP address
and MAC address exist. To prevent this situation, a mechanism is required to
check for IP address and MAC address conflicts after a split. MAD is a CSS
split detection protocol that provides split detection, multi-active handling,
and fault recovery mechanisms when a CSS splits due to a link failure. This
minimizes the impact of a CSS split on services.
MAD can be implemented in direct or relay mode, but these modes cannot be
configured simultaneously in a CSS. You can configure MAD in relay mode for
a CSS when an inter-device Eth-Trunk is configured in the CSS. The direct
mode occupies additional ports, and these ports can only be used for MAD
after being connected using common cables. In contrast to the direct mode,
the relay mode does not occupy additional ports.
Guidelines
● The service port clustering function is controlled by a license. By default, this
function is disabled on a new device. To use this function, apply for and
purchase a license from the Huawei agent or local office.
● When switches using SRUAs, SRUBs, SRUCs, and SRUDs set up a CSS in
service port clustering mode, the system software file (system startup
package) must be saved in the CF card. If it is saved in the flash memory, the
CSS cannot be set up in service port clustering mode.
● After two switches set up a CSS, the following features cannot be configured
in the CSS:
– Synchronous Ethernet clock
– Precision Time Protocol (PTP) (IEEE 1588)
● When configuring MAD, focus on the differences in the command syntax
between V200R002C00 and V200R003C00 (and later versions). In
V200R002C00, the split detection function is called dual-active detection
(DAD).
● Regardless of how many MAD links exist, ports of the standby switch will be
shut down and no longer forward service packets as long as the CSS splits.
Networking Requirements
An enterprise needs to build a network that has a reliable core layer and simple
structure to facilitate configuration and management and reduce deployment
costs.
To meet requirements of the enterprise, core switches SwitchA and SwitchB set up
a CSS in service port connection mode. SwitchA is the master switch, and SwitchB
is the standby switch. Figure 4-23 shows the network topology. Aggregation
switches connect to the CSS through Eth-Trunks, and the CSS connects to the
upstream network through an Eth-Trunk. In this example, the core switches are
the S9306 switches.
Configuration Roadmap
The configuration roadmap is as follows:
1. Install LPUs on SwitchA and SwitchB, and connect cluster cables. Connect four
service ports on two LPUs of each switch to improve bandwidth and reliability.
2. Set the CSS connection mode on SwitchA and SwitchB and set their CSS IDs to
1 and 2 and CSS priorities to 100 and 10 respectively. These configurations
ensure that SwitchA has a higher probability to become the master switch.
3. Configure two logical CSS ports on each of SwitchA and SwitchB and add two
physical member ports to each logical CSS port.
4. Enable the CSS function on SwitchA and then on SwitchB to ensure that
SwitchA becomes the master switch.
5. Check whether a CSS is set up successfully.
6. Configure uplink and downlink Eth-Trunks for the CSS to improve forwarding
bandwidth and reliability.
7. Configure MAD to minimize the impact of a CSS split on the network.
Procedure
Step 1 Install hardware modules.
The following describes only the rule for connecting cluster cables between two
member switches. If you also need to install LPUs and learn about installation
details, see the Switch Cluster Setup Guide.
Connect cluster cables according to the connection rule shown in Figure 4-24.
NOTE
Step 2 Configure the CSS connection mode, CSS ID, and CSS priority.
# Configure the CSS function on SwitchA. Configure the service port connection
mode, set the CSS priority to 100, and retain the default CSS ID 1.
<Quidway> system-view
[Quidway] sysname SwitchA
[SwitchA] set css mode lpu
[SwitchA] set css priority 100
# Configure the CSS function on SwitchB. Configure the service port connection
mode, and set the CSS ID to 2 and CSS priority to 10.
<Quidway> system-view
[Quidway] sysname SwitchB
[SwitchB] set css mode lpu
[SwitchB] set css id 2
[SwitchB] set css priority 10
NOTE
After the configuration is complete, run the display css status saved command to check
the CSS configuration.
NOTE
After the configuration is complete, run the display css css-port saved command to check
whether the ports are Up.
The command output shows the card status of both member switches, indicating
that the CSS has been set up successfully.
# Check whether the CSS link topology is the same as the actual hardware
connection.
<SwitchA> display css channel all
CSS link-down-delay: 500ms
Chassis 1 || Chassis 2
================================================================================
Num [CSS port] [LPU Port] || [LPU Port] [CSS port]
1 1/1 XGigabitEthernet1/1/0/1 XGigabitEthernet2/1/0/1 2/1
2 1/1 XGigabitEthernet1/1/0/2 XGigabitEthernet2/1/0/2 2/1
3 1/2 XGigabitEthernet1/2/0/1 XGigabitEthernet2/2/0/1 2/2
4 1/2 XGigabitEthernet1/2/0/2 XGigabitEthernet2/2/0/2 2/2
Chassis 2 || Chassis 1
================================================================================
Num [CSS port] [LPU Port] || [LPU Port] [CSS port]
1 2/1 XGigabitEthernet2/1/0/1 XGigabitEthernet1/1/0/1 1/1
2 2/1 XGigabitEthernet2/1/0/2 XGigabitEthernet1/1/0/2 1/1
3 2/2 XGigabitEthernet2/2/0/1 XGigabitEthernet1/2/0/1 1/2
4 2/2 XGigabitEthernet2/2/0/2 XGigabitEthernet1/2/0/2 1/2
The command output shows that the CSS link topology is the same as the actual
hardware connection, indicating that the CSS has been set up successfully.
Step 6 Configure Eth-Trunks between the CSS and its upstream and downstream devices.
# Configure an Eth-Trunk in the CSS and add uplink ports to the Eth-Trunk.
<SwitchA> system-view
[SwitchA] sysname CSS //Rename the CSS.
[CSS] interface eth-trunk 10
[CSS-Eth-Trunk10] quit
[CSS] interface xgigabitethernet 1/3/0/4
[CSS-XGigabitEthernet1/3/0/4] eth-trunk 10
[CSS-XGigabitEthernet1/3/0/4] quit
[CSS] interface xgigabitethernet 2/3/0/4
[CSS-XGigabitEthernet2/3/0/4] eth-trunk 10
[CSS-XGigabitEthernet2/3/0/4] quit
# Configure an Eth-Trunk in the CSS and add the downlink ports connected to
SwitchC to the Eth-Trunk.
[CSS] interface eth-trunk 20
[CSS-Eth-Trunk20] quit
[CSS] interface gigabitethernet 1/4/0/3
[CSS-GigabitEthernet1/4/0/3] eth-trunk 20
[CSS-GigabitEthernet1/4/0/3] quit
[CSS] interface gigabitethernet 2/4/0/5
[CSS-GigabitEthernet2/4/0/5] eth-trunk 20
[CSS-GigabitEthernet2/4/0/5] quit
# Configure an Eth-Trunk in the CSS and add the downlink ports connected to
SwitchD to the Eth-Trunk.
[CSS] interface eth-trunk 30
[CSS-Eth-Trunk30] quit
[CSS] interface gigabitethernet 1/4/0/5
[CSS-GigabitEthernet1/4/0/5] eth-trunk 30
[CSS-GigabitEthernet1/4/0/5] quit
[CSS] interface gigabitethernet 2/4/0/3
[CSS-GigabitEthernet2/4/0/3] eth-trunk 30
[CSS-GigabitEthernet2/4/0/3] return
The command output shows information about member ports in Eth-Trunk 10.
<CSS> display trunkmembership eth-trunk 10
Trunk ID: 10
Used status: VALID
TYPE: ethernet
Working Mode : Normal
Number Of Ports in Trunk = 2
Number Of Up Ports in Trunk = 2
Operate status: up
Step 7 Configure the MAD function. The following procedure configures MAD in relay
mode and configures SwitchC as the relay agent using the commands applicable
to V200R003C00 and later versions.
# In the CSS, configure MAD in relay mode for the inter-device Eth-Trunk.
<CSS> system-view
[CSS] interface eth-trunk 20
[CSS-Eth-Trunk20] mad detect mode relay //In V200R002C00, the command is dual-active detect
mode relay.
[CSS-Eth-Trunk20] quit
[CSS] quit
----End
Configuration Files
● CSS configuration file
#
sysname CSS
#
interface Eth-Trunk10
#
interface Eth-Trunk20
mad detect mode relay
#
interface Eth-Trunk30
#
interface GigabitEthernet1/4/0/3
eth-trunk 20
#
interface XGigabitEthernet1/3/0/4
eth-trunk 10
#
interface GigabitEthernet1/4/0/5
eth-trunk 30
#
interface GigabitEthernet2/4/0/3
eth-trunk 30
#
interface XGigabitEthernet2/3/0/4
eth-trunk 10
#
interface GigabitEthernet2/4/0/5
eth-trunk 20
#
return
When two standalone devices are combined into a CSS, major configuration
changes include:
● The VRRP gateway backup protocol deployed at the aggregation layer is not
required and its configuration needs to be deleted.
● The STP loop prevention protocol deployed at the access layer is not required
and its configuration needs to be deleted.
● The links at the access, aggregation, and core layers are changed to Eth-
Trunks, and related interface configurations need to be changed, including
basic VLAN configuration, QoS configuration, and ACL configuration.
Guidelines
● This operation applies to CSS card clustering and service port clustering.
Before combining two standalone switches into a CSS, ensure that the
hardware and software of the two switches meet CSS requirements. For CSS
card clustering, CSS cards and cluster cables have been prepared. For service
port clustering, service cards that support service port clustering and cluster
cables have been prepared.
● After the CSS function is enabled on a standalone switch and the switch is
restarted, configurations on interfaces of the switch may be lost in some
special configuration scenarios. Therefore, you are advised to back up the
configuration file before enabling the CSS function.
● The following procedure provides only the related configurations. Whether
other configurations need to be changed depends on the actual networking.
Procedure
Step 1 In the original networking, traffic at the access layer is load-balanced among
multiple links through STP and VRRP. In Figure 4-26, some traffic is forwarded
through S1 and some traffic is forwarded through S2.
Step 2 Manually shut down the uplink and downlink ports of S2 to change the STP and
VRRP status so that S2 is isolated from the network and all traffic is forwarded
through S1, as shown in Figure 4-27.
Figure 4-27 Traffic forwarding after an STP and VRRP status switchover
Step 3 Back up the configuration file of S2. After the CSS function is enabled on a
standalone switch, the interface number format on the switch is changed from
slot ID/subcard ID/port number to stack member ID/slot ID/subcard ID/port
number, and the configurations on the interfaces of the switch are lost.
Step 4 Change S2 to the CSS state.
● Procedure for configuring service port clustering
a. Power off S2, install service cards, and power on S2.
b. Configure the CSS connection mode and CSS priority on S2.
<S2> system-view
[S2] set css mode lpu
[S2] set css priority 200 // Set the CSS priority to 200 to make S2 become the CSS master. The
default CSS priority is 1.
[S2] display css status saved // Check whether the configuration is correct.
Current Id Saved Id CSS Enable CSS Mode Priority Master
Force
------------------------------------------------------------------------------
c. Configure service ports as CSS ports. For example, configure service ports
XGE1/0/1, XGE1/0/2, XGE2/0/1, and XGE2/0/2 as CSS ports.
[S2] interface css-port 1
[S2-css-port1] port interface xgigabitethernet 1/0/1 to xgigabitethernet 1/0/2 enable
[S2-css-port1] quit
[S2] interface css-port 2
[S2-css-port2] port interface xgigabitethernet 2/0/1 to xgigabitethernet 2/0/2 enable
[S2-css-port2] quit
Step 5 Change the configuration of S2, which has been changed to a single-chassis
cluster CSS-1. Alternatively, change the configuration after S1 and S2 are
combined into a CSS. Changing the configuration of S2 before S1 and S2 are
combined into a CSS can reduce the traffic loss.
Step 8 Change S1 to the CSS state. After S1 is added to CSS-1, S1 uses the configuration
file of CSS-1.
● Procedure for configuring service port clustering
a. Power off S1, install service cards, connect the cluster cables between S1
and CSS-1, and power on S1.
b. Configure the cluster connection mode and CSS ID and retain the default
CSS priority 1 on S1.
<S1> system-view
[S1] set css mode lpu
[S1] set css id 2
[S1] display css status saved // Check whether the configuration is correct.
Current Id Saved Id CSS Enable CSS Mode Priority Master
Force
------------------------------------------------------------------------------
1 2 Off LPU 1 On
c. Configure service ports as CSS ports. For example, configure service ports
XGE1/0/1, XGE1/0/2, XGE2/0/1, and XGE2/0/2 as CSS ports.
[S1] interface css-port 1
[S1-css-port1] port interface xgigabitethernet 1/0/1 to xgigabitethernet 1/0/2 enable
[S1-css-port1] quit
[S1] interface css-port 2
[S1-css-port2] port interface xgigabitethernet 2/0/1 to xgigabitethernet 2/0/2 enable
[S1-css-port2] quit
Step 10 Change the configurations of CSS-2 and add interfaces of CSS-2 to Eth-Trunks.
1. Add uplink ports XGE2/4/0/1 and XGE2/4/0/2 of CSS-2 to Eth-Trunks.
[CSS] interface eth-trunk 20
[CSS-Eth-Trunk20] trunkport xgigabitethernet2/4/0/1
[CSS-Eth-Trunk20] quit
[CSS] interface eth-trunk 10
[CSS-Eth-Trunk10] trunkport xgigabitethernet2/4/0/2
[CSS-Eth-Trunk10] quit
2. Change the configurations of devices at the core layer and access layer and
bind physical ports to Eth-Trunks. The procedure is similar to the preceding
procedure.
Step 11 Run the undo shutdown command to disable the interfaces of CSS-2 and check
whether Layer 2 and Layer 3 forwarding between CSS-2 and devices at the core
layer and access layer is normal. In this case, S1 and S2 have been combined into
a CSS, as shown in Figure 4-31.
----End
In an SVF system, a parent manages and configures the SVF system. Client refers
to all access devices, including access devices (ASs).
NOTE
● Table1 describes the version mapping between parent and AS. Table2 describes
supported Parent and AS switch models in different software versions.
V200R011C10 V200R011C10
● Networking in which the parent and ASs are directly connected, as shown in
Figure 4-33
a. The parent can be a standalone device, a cluster switch system (CSS) of
two modular devices, or a stack of multiple member devices.
b. At most two levels of ASs are supported in an SVF system. Each AS can
be a standalone device or a stack of multiple member devices.ach 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.
c. User terminals can access the network through level-1 or level-2 ASs. The
parent functions as the access gateway of users.
If a new campus network is built with unconfigured devices, this networking
is recommended.
Figure 4-33 Networking in which the parent and ASs are directly connected
on a wired campus network
Figure 4-34 Networking in which the parent and ASs are connected across an
intermediate network on a wired campus network
Configure the SVF An SVF system supports two forwarding modes: centralized
forwarding mode. forwarding and distributed forwarding.
● In centralized forwarding mode, traffic forwarded by the
local AS and forwarded between ASs is sent to the
parent for forwarding.
● In distributed forwarding mode, an AS directly forwards
local traffic and the parent forwards traffic between
ASs.
NOTE
● In centralized forwarding mode, ports of the ASs connected to
the same fabric port of the parent are isolated and so cannot
communicate at Layer 2, and need to have proxy ARP in the
corresponding VLAN configured using the arp-proxy inner-
sub-vlan-proxy enable command to communicate at Layer 3.
● In centralized forwarding mode, after an AS goes offline, traffic
of its attached network cannot be forwarded by the parent and
will be interrupted.
● In distributed forwarding mode, after an AS goes offline, in
versions earlier than V200R012C00, downlink ports of the AS
are automatically shut down. As a result, traffic of the AS
attached network will be interrupted. In V200R012C00 and
later versions, downlink ports of the AS will not be shut down,
and traffic of the AS attached network will be forwarded as
usual.
By default, the forwarding mode of an SVF system is
distributed forwarding.
Function Description
fabric
port.
, delete
the
existing
configurat
ion before
reconfigur
ing them.
● In
V200R019
and later
versions,
multiple
configurat
ions of
this
command
can be
generated
regardless
of
whether
the VLAN,
IP address,
and MAC
address
are the
same. You
do not
need to
delete the
existing
configurat
ion. If the
newly
configured
VLAN is
the same
as the
existing
one, the IP
address
and MAC
address in
the
original
configurat
ion are
replaced
with the
newly
configured
IP address
and MAC
address. If
the newly
configured
VLAN is
different
from the
existing
one, a
new
configurat
ion is
generated.
● In the user view and diagnostic view, all commands are supported except the
commands listed in Table 4-12.
Table 4-12 Commands not supported in the user view and diagnostic view of
ASs
Command View
Command View
● Commands that are supported in other views are used for service diagnosis
and fault location.
acl 4000-4997
undo acl
4000-4997
● These commands vary depending on the AS device type. For details, see the
command reference of these devices.
Function Command
Function Command
S9312E, S9306E 48
4. Select the required networking scenario. Table 4-15 lists the recommended
scenarios.
Existing Scenario 1:
devices need Networking
to be reused. in which the
parent and
ASs are
connected
across an
intermediat
e network
on a wired
campus
network
Figure 4-36 shows an ideal SVF networking. It has the following characteristics:
1. The parent is a CSS of two member devices.
2. Each Level-1 AS is dual-homed to two member devices of the parent through
uplink ports.
3. When an AS is a stack of multiple member devices, each member device is
connected to its upstream device through at least one link.
4. ASs are connected to upstream devices through uplink optical ports or uplink
combo ports.
This SVF networking has the following advantages:
1. A failure of a single link between two devices affects only the bandwidth but
not services.
2. An AS performs multi-active detection (MAD), and its upstream device
functions as the MAD relay agent. When the AS splits as a stack, it can work
with the upstream device to perform MAD without affecting the system
stability.
Implementing the ideal SVF networking may fail because of restrictions such as
the distance between devices and cabling difficulties. You need to identify these
networking restrictions in advance and take appropriate measures. The following
provides suggestions on SVF deployment in different situations:
1. If the parent is a standalone device:
a. Deploy two MPUs on the parent to ensure reliability.
b. Connect each AS to the parent using at least two links and ensure that
the links are connected to at least two different LPUs of the parent.
2. If a level-1 AS cannot be dual-homed to the parent:
– Use a standalone device as a level-1 AS. If the AS needs to be a stack,
deploy member devices in the same physical location and ensure stack
cable reliability. Otherwise, device conflicts cannot be resolved after the
stack splits, affecting system reliability.
3. If the AS is a stack of multiple member devices and you cannot ensure that
each member device connects to its upstream device through at least one
link:
– Deploy member devices in the same physical location and ensure stack
cable reliability. Otherwise, device conflicts cannot be resolved after the
stack splits, affecting system reliability.
4. If member ports of the fabric port that connects an AS to an upstream device
can only be connected through twisted pairs:
– Use copper modules to convert the optical/electrical attributes of ports
when uplink ports of ASs are GE ports.
– Select ASs that have uplink combo ports.
Determining ASs
Select level-1 and level-2 ASs according to the following requirements:
1. ASs can connect to the parent only through uplink ports, and uplink ports of
most ASs are optical ports. Therefore, when an SVF system has two levels of
ASs, use ASs with downlink optical ports as level-1 ASs. Otherwise, you need
to use copper modules to ensure the connectivity between level-1 and level-2
ASs.
2. When services in an SVF system are similar, use ASs of the same type so that
faulty ASs can be replaced.
Select ASs according to hardware characteristics and the following table to meet
different networking requirements.
Configuration Method
In an SVF system, two AS service configuration modes are available: centralized
mode and independent mode. The two modes cannot be used on the same AS.
In centralized mode, all service configurations for ASs are performed on the
parent. Therefore, which services can be configured on ASs depends on the
services that can be configured on the parent, but not depend on the services
supported by a standalone access switch.
Profile- Create service profiles and specified device and port groups on the
based parent, bind the service profiles to the device and port groups, and
configura then run the commit as { name as-name | all } command to deliver
tion AS service configurations. If multiple ASs or ports in an SVF system
need the same configurations, you can add these ASs or ports to the
same group for batch configuration. In this manner, the
configuration efficiency is improved.
Configuration Roadmap
1. Determine the services to be configured for an AS.
2. Determine the configuration method based on 4.3.1.3 SVF Service
Deployment Limitations. For example, you need to configure SNMP on an
AS. According to "Service Configuration Supported on an AS", you determine
that SNMP can be configured only in independent mode.
3. Configure services based on the configuration method. Figure 4-37 illustrates
the process of delivering configurations from the parent to AS ports using
service profiles.
When configuring services for ASs through port groups, you only need to
focus on user ports on ASs. Whether services of fabric ports need to be
manually configured depends on networking scenarios:
– When the parent is directly connected to ASs, service configurations of
fabric ports on the parent and ASs will be automatically generated
according to service configurations of user ports.
– When the parent is connected to ASs across an intermediate network,
you need to configure services for the fabric port of the parent.
● User ports on each AS can have a maximum of 1 default VLAN, 1 voice VLAN,
and 32 allowed VLANs.
● In versions earlier than V200R011C10, user ports on an AS cannot be
configured as Eth-Trunk member ports. In V200R011C10 or later versions, user
ports on an AS can be configured as Eth-Trunk member ports.
In an SVF system shown in Figure 4-38, the parent functions as the access control
authentication point of all users, and so services of the authentication server only
need to be configured on the parent once, simplifying deployment. The access
control enforcement points of all users are deployed on ASs. To ensure security,
users who fail authentication cannot access ASs.
An SVF system supports three access user authentication modes: MAC, 802.1X,
and Portal. Table 4-19 lists the characteristics and application scenarios of the
three authentication modes.
Attack on the ARP attack with fixed source The CPU usage of the
control plane MAC address parent becomes high, and
traffic of some users is
ARP attack with fixed source interrupted.
IP address
Attack on the ARP Miss attack with fixed The parent has a high CPU
forwarding plane source IP address usage and cannot learn ARP
entries.
ARP attack
with fixed
source IP
address
Attack ARP Miss Configure rate limiting for ARP Miss packets on the
on the attack with parent to limit the packets based on the source IP
forwardi fixed source address.
ng plane IP address
Precautions
● The Super Virtual Fabric (SVF) function on a parent is license controlled. The
license only enables the SVF function but does not control SVF service
specifications and only needs to be loaded on the parent.
● After the SVF function is enabled, switches do not support the In-Service
Software Upgrade (ISSU) function.
● When the parent version is earlier than V200R011C10, the AS version must be
the same as the parent version. Otherwise, this AS cannot go online. For
example, if the parent version is V200R010C00, the AS version must also be
V200R010C00.
● When the parent version is V200R011C10 or later, the parent version and AS
version can be different, but the parent version must be higher than or the
same as the AS version and the AS version must also be V200R011C10 or
later.
● 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.
● If an AS is a stack set up using service ports, the AS must join an SVF system
after having the stacking function configured. This limitation does not apply
to an AS that is a stack set up using stack cards.
● When a cluster switch system (CSS) functioning as the parent is faulty:
– If one member switch in the CSS is faulty, the SVF function is not
affected.
– If the CSS splits but two member switches are working normally, the SVF
function becomes unavailable because ASs do not know which switch is
the parent. In this situation, you are advised to configure the dual-active
detection (DAD) function.
Networking Requirements
A new campus network has a large number of wired and wireless access devices.
The widely distributed access devices complicate management and configuration
of the access layer. Unified management and configuration of wired and wireless
access devices is required to reduce the management cost.
In this example, complete the following operations on access devices:
● Configure the administrator user name and password for access devices.
● Assign VLANs to ports of access devices.
● Set the user access authentication mode to 802.1X authentication.
As shown in Figure 4-39, two aggregation switches (SwitchA and SwitchB) set up
a Cluster Switching System (CSS) to improve reliability and function as the parent
to connect to multiple ASs. Multiple active detection (MAD) in direct mode must
be configured on the parent to avoid conflicts when the CSS splits.
In this example, two S9300s function as the parent, an S5320-28P-SI-AC functions
as a level-1 AS, an S5320-12TP-LI-AC functions as a level-2 AS.
Data Plan
Item Data Description
Ports that connect the GE1/1/0/1 and Add the two ports to
parent to AS1 GE2/1/0/1 Eth-Trunk1 and bind
them to Fabric-port 1.
Ports that connect the GE1/1/0/2 and Add the two ports to
parent to AS2 GE2/1/0/2 Eth-Trunk2 and bind
them to Fabric-port 2.
Ports that connect the GE1/1/0/3 and Add the two ports to
parent to AS3 GE2/1/0/3 Eth-Trunk3 and bind
them to Fabric-port 3.
Ports that connect AS1 GE0/0/23 and GE0/0/24 Add the two ports to
to AS4 Eth-Trunk4 and bind
them to Fabric-port 4.
Ports that connect AS3 GE0/0/23 and GE0/0/24 Add the two ports to
to AS5 Eth-Trunk5 and bind
them to Fabric-port 5.
Configuration Roadmap
1. Configure SwitchA and SwitchB in the parent to set up a CSS using CSS cards
and configure MAD in direct mode to ensure high reliability of the SVF
system.
2. Enable the SVF function on the parent.
3. Configure AS access parameters, including AS names (optional),
authentication mode, and fabric ports that connect the parent to level-1 ASs
and level-1 ASs to level-2 ASs.
4. Connect level-1 ASs to the parent and level-2 ASs using cables.
5. Configure service profiles and bind them to ASs.
6. Log in to ASs to check the service configurations of the ASs.
Procedure
1. Configure SwitchA and SwitchB in the parent to set up a CSS.
# Set the CSS connection mode, CSS ID, and CSS priority to CSS card
connection, 1, and 100 for SwitchA.
<Quidway> system-view
[Quidway] sysname SwitchA
[SwitchA] set css mode css-card
[SwitchA] set css id 1
[SwitchA] set css priority 100
# Set the CSS connection mode, CSS ID, and CSS priority to CSS card
connection, 2, and 10 for SwitchB.
<Quidway> system-view
[Quidway] sysname SwitchB
[SwitchB] set css mode css-card
[SwitchB] set css id 2
[SwitchB] set css priority 10
2. Configure the management VLAN in the SVF system and enable the SVF
function on the parent.
[SwitchA] vlan batch 11
[SwitchA] dhcp enable
[SwitchA] interface vlanif 11
[SwitchA-Vlanif11] ip address 192.168.11.1 24
[SwitchA-Vlanif11] dhcp select interface
[SwitchA-Vlanif11] dhcp server option 43 ip-address 192.168.11.1
[SwitchA-Vlanif11] quit
[SwitchA] capwap source interface vlanif 11
[SwitchA] stp mode rstp
[SwitchA] uni-mng
Warning: This operation will enable the uni-mng mode and disconnect all ASs. STP calculation may
be triggered and service traffic will be affected. Continue? [Y/N]:y
3. Configure AS access parameters.
# (Optional) Configure a name for each AS.
NOTE
● If you do not perform this step, the system will generate AS device information when
ASs connect to the SVF system. An AS name is in the format of system default name-
system MAC address.
● If you need to perform this step, ensure that the configured model and mac-address
parameters are consistent with the actual AS information. The value of mac-address
must be the AS management MAC address or system MAC address. To view the AS
management MAC address, run the display as access configuration command on the
AS. If the management MAC displays --, the value of mac-address is the system MAC
address. If the configured parameters are inconsistent with the actual AS information,
the AS cannot go online.
[SwitchA-um] as name as1 model S5320-28P-SI-AC mac-address 00e0-fc00-0011
[SwitchA-um-as-as1] quit
[SwitchA-um] as name as2 model S5320-28P-SI-AC mac-address 00e0-fc00-0022
[SwitchA-um-as-as2] quit
[SwitchA-um] as name as3 model S5320-28P-SI-AC mac-address 00e0-fc00-0033
[SwitchA-um-as-as3] quit
[SwitchA-um] as name as4 model S5320-12TP-LI-AC mac-address 00e0-fc00-0044
[SwitchA-um-as-as4] quit
[SwitchA-um] as name as5 model S5320-12TP-LI-AC mac-address 00e0-fc00-0055
[SwitchA-um-as-as5] quit
# Configure the fabric port that connects the parent to AS1.
[SwitchA-um] interface fabric-port 1
[SwitchA-um-fabric-port-1] port member-group interface eth-trunk 1
[SwitchA-um-fabric-port-1] quit
[SwitchA-um] quit
[SwitchA] interface gigabitethernet 1/1/0/1
[SwitchA-GigabitEthernet1/1/0/1] eth-trunk 1
[SwitchA-GigabitEthernet1/1/0/1] quit
[SwitchA] interface gigabitethernet 2/1/0/1
[SwitchA-GigabitEthernet2/1/0/1] eth-trunk 1
[SwitchA-GigabitEthernet2/1/0/1] quit
# Configure the fabric port that connects the parent to AS2.
[SwitchA] uni-mng
[SwitchA-um] interface fabric-port 2
[SwitchA-um-fabric-port-2] port member-group interface eth-trunk 2
[SwitchA-um-fabric-port-2] quit
[SwitchA-um] quit
[SwitchA] interface gigabitethernet 1/1/0/2
[SwitchA-GigabitEthernet1/1/0/2] eth-trunk 2
[SwitchA-GigabitEthernet1/1/0/2] quit
[SwitchA] interface gigabitethernet 2/1/0/2
[SwitchA-GigabitEthernet2/1/0/2] eth-trunk 2
[SwitchA-GigabitEthernet2/1/0/2] quit
# Configure the fabric port that connects the parent to AS3.
[SwitchA] uni-mng
[SwitchA-um] interface fabric-port 3
[SwitchA-um-fabric-port-3] port member-group interface eth-trunk 3
[SwitchA-um-fabric-port-3] quit
[SwitchA-um] quit
[SwitchA] interface gigabitethernet 1/1/0/3
[SwitchA-GigabitEthernet1/1/0/3] eth-trunk 3
[SwitchA-GigabitEthernet1/1/0/3] quit
[SwitchA] interface gigabitethernet 2/1/0/3
[SwitchA-GigabitEthernet2/1/0/3] eth-trunk 3
[SwitchA-GigabitEthernet2/1/0/3] quit
# Configure the fabric ports that connect AS1 to AS4 and AS3 to AS5.
[SwitchA] uni-mng
[SwitchA-um] as name as1
[SwitchA-um-as-as1] down-direction fabric-port 4 member-group interface eth-trunk 4
[SwitchA-um-as-as1] port eth-trunk 4 trunkmember interface gigabitethernet 0/0/23 to 0/0/24
[SwitchA-um-as-as1] quit
[SwitchA-um] as name as3
[SwitchA-um-as-as3] down-direction fabric-port 5 member-group interface eth-trunk 5
[SwitchA-um-as-as3] port eth-trunk 5 trunkmember interface gigabitethernet 0/0/23 to 0/0/24
[SwitchA-um-as-as3] quit
[SwitchA-um] quit
# Configure whitelist authentication for ASs to connect to an SVF system.
To view the AS management MAC address, run the display as access
configuration command on the AS. If the management MAC displays --, the
MAC address configured in the whitelist is the AS system MAC address.
Otherwise, the MAC address configured in the whitelist is the AS
management MAC address.
[SwitchA] as-auth
[SwitchA-as-auth] undo auth-mode
[SwitchA-as-auth] whitelist mac-address 00e0-fc00-0011
[SwitchA-as-auth] whitelist mac-address 00e0-fc00-0022
[SwitchA-as-auth] whitelist mac-address 00e0-fc00-0033
[SwitchA-as-auth] whitelist mac-address 00e0-fc00-0044
[SwitchA-as-auth] whitelist mac-address 00e0-fc00-0055
[SwitchA-as-auth] quit
4. Run the reset saved-configuration command to clear the configurations of
ASs, restart the ASs, and then connect level-1 ASs to the parent and level-2
ASs using cables. Subsequently, an SVF system is set up.
NOTE
● Before restarting an AS, check whether the port that connects this AS to the parent is a
downlink port. You can run the display port connection-type access all command on
this AS to view all downlink ports on it. If this port is a downlink port, run the uni-mng
up-direction fabric-port command on this AS to configure this port as an uplink port
before restarting this AS. Otherwise, this AS cannot go online.
● Before connecting an AS to the parent, ensure that the AS has no configuration file and
no input on the console port.
# After connecting cables, run the display as all command to check whether
ASs have connected to the SVF system.
[SwitchA] display as all
Total: 5, Normal: 5, Fault: 0, Idle: 0, Version mismatch: 0
--------------------------------------------------------------------------------
No. Type MAC IP State Name
--------------------------------------------------------------------------------
0 S5320-SI 00e0-fc00-0011 192.168.11.254 normal as1
1 S5320-SI 00e0-fc00-0022 192.168.11.253 normal as2
2 S5320-SI 00e0-fc00-0033 192.168.11.252 normal as3
3 S5320-LI 00e0-fc00-0044 192.168.11.251 normal as4
4 S5320-LI 00e0-fc00-0055 192.168.11.250 normal as5
--------------------------------------------------------------------------------
When the State field in the command output displays normal for an AS, the
AS has connected to the SVF system.
# Run the display uni-mng topology information command to view SVF
topology information.
[SwitchA] display uni-mng topology information
The topology information of uni-mng network:
<-->: direct link <??>: indirect link
T: Trunk ID *: independent AS
------------------------------------------------------------------------------
Local MAC Hop Local Port T || T Peer Port Peer MAC
------------------------------------------------------------------------------
00e0-fc00-1100 0 GE1/1/0/1 1 <-->0 GE0/0/27 00e0-fc00-0011
00e0-fc00-1100 0 GE2/1/0/1 1 <-->0 GE0/0/28 00e0-fc00-0011
00e0-fc00-1100 0 GE1/1/0/2 2 <-->0 GE0/0/27 00e0-fc00-0022
00e0-fc00-1100 0 GE2/1/0/2 2 <-->0 GE0/0/28 00e0-fc00-0022
00e0-fc00-1100 0 GE1/1/0/3 3 <-->0 GE0/0/27 00e0-fc00-0033
00e0-fc00-1100 0 GE2/1/0/3 3 <-->0 GE0/0/28 00e0-fc00-0033
00e0-fc00-0011 1 GE0/0/23 4 <-->0 GE0/0/11 00e0-fc00-0044
00e0-fc00-0011 1 GE0/0/24 4 <-->0 GE0/0/12 00e0-fc00-0044
00e0-fc00-0033 1 GE0/0/23 5 <-->0 GE0/0/11 00e0-fc00-0055
00e0-fc00-0033 1 GE0/0/24 5 <-->0 GE0/0/12 00e0-fc00-0055
------------------------------------------------------------------------------
Total items displayed : 10
Info: The max number of VTY users is 10, and the number
of current VTY users on line is 1.
The current login time is 2016-06-25 22:31:18+00:00.
<HUAWEI>
To check access authentication configuration, you need to run the display authentication
interface interface-type interface-number command on an AS.
Configuration Summary
1. When setting up a CSS for a parent, use the CSS card or service port
connection mode according to networking requirements. This example uses
the CSS card connection.
2. You can configure service profiles and bind them to ASs before or after the
ASs connect to the SVF system. The AS service configuration mode includes
the pre-configured and non-pre-configured modes depending on the time
services are configured. Whatever configuration mode you use, you must run
the commit as { name as-name | all } command to commit the configuration
after completing it.
– Pre-configured mode: Before ASs connect to the SVF system, pre-
configure service profiles, bind them to the ASs, save the configuration on
the parent, and then run the commit as { name as-name | all }
command to commit the configuration. When the ASs connect to the SVF
system, configurations in the service profiles are automatically delivered
to the ASs.
– Non-pre-configured mode: After ASs connect to the SVF system,
configure service profiles, bind them to the ASs, and then run the
commit as { name as-name | all } command to commit the
configuration so that configurations in the service profiles can be
delivered to the ASs.
3. After the SVF function is enabled, the Spanning Tree Protocol (STP) and Link
Layer Discovery Protocol (LLDP) functions are enabled globally on the parent.
Pay attention to the following points when using the STP and LLDP functions
in an SVF system:
– You can disable the STP and LLDP functions only on ports, not globally.
– Do not disable the LLDP function on member ports of a fabric port.
Otherwise, the SVF topology will become abnormal.
4. After the SVF function is enabled, the parent will change STP to Rapid
Spanning Tree Protocol (RSTP) and set the priority of instance 0 to 28762
using the stp instance 0 priority 28672 command. Note that the priority of
instance 0 cannot be set to a value greater than 28672. After the SVF function
Precautions
● The Super Virtual Fabric (SVF) function on a parent is license controlled. The
license only enables the SVF function but does not control SVF service
specifications and only needs to be loaded on the parent.
● After the SVF function is enabled, switches do not support the In-Service
Software Upgrade (ISSU) function.
● When the parent version is earlier than V200R011C10, the AS version must be
the same as the parent version. Otherwise, this AS cannot go online. For
example, if the parent version is V200R010C00, the AS version must also be
V200R010C00.
● When the parent version is V200R011C10 or later, the parent version and AS
version can be different, but the parent version must be higher than or the
Networking Requirements
A new campus network has a large number of wired and wireless access devices.
The widely distributed access devices complicate management and configuration
of the access layer. Unified management and configuration of wired and wireless
access devices is required to reduce the management cost.
In this example, complete the following operations on access devices:
● Configure the administrator user name and password for access devices.
● Assign VLANs to ports of access devices.
● Set the user access authentication mode to 802.1X authentication.
As shown in Figure 4-40, two aggregation switches (SwitchA and SwitchB) set up
a Cluster Switching System (CSS) to improve reliability and function as the parent
to connect to multiple ASs and APs. Multiple active detection (MAD) in direct
mode must be configured on the parent to avoid conflicts when the CSS splits.
In this example, two S12700s function as the parent, an S5320-28P-SI-AC
functions as a level-1 AS, an S5320-12TP-LI-AC functions as a level-2 AS, and an
AP5010DN-AGN functions as an AP.
Data Plan
Item Data Description
Ports that connect the GE1/1/0/1 and Add the two ports to
parent to AS1 GE2/1/0/1 Eth-Trunk1 and bind
them to Fabric-port 1.
Ports that connect the GE1/1/0/2 and Add the two ports to
parent to AS2 GE2/1/0/2 Eth-Trunk2 and bind
them to Fabric-port 2.
Ports that connect the GE1/1/0/3 and Add the two ports to
parent to AS3 GE2/1/0/3 Eth-Trunk3 and bind
them to Fabric-port 3.
Ports that connect AS1 GE0/0/23 and GE0/0/24 Add the two ports to
to AS4 Eth-Trunk4 and bind
them to Fabric-port 4.
Ports that connect AS3 GE0/0/23 and GE0/0/24 Add the two ports to
to AS5 Eth-Trunk5 and bind
them to Fabric-port 5.
Configuration Roadmap
1. Configure SwitchA and SwitchB in the parent to set up a CSS using CSS cards
and configure MAD in direct mode to ensure high reliability of the SVF
system.
2. Enable the SVF function on the parent.
3. Configure AS access parameters, including AS names (optional),
authentication mode, and fabric ports that connect the parent to level-1 ASs
and level-1 ASs to level-2 ASs.
4. Connect level-1 ASs to the parent and level-2 ASs using cables.
5. Configure service profiles and bind them to ASs.
6. Configure the downlink port (GE0/0/24) that connects AS2 to the AP,
configure AP access parameters, power on the AP, and connect the AP and
AS2 using cables to ensure that the AP can connect to the SVF system.
7. Log in to ASs to check the service configurations of the ASs.
Procedure
1. Configure SwitchA and SwitchB in the parent to set up a CSS.
# Set the CSS connection mode, CSS ID, and CSS priority to CSS card
connection, 1, and 100 for SwitchA.
<Quidway> system-view
[Quidway] sysname SwitchA
[SwitchA] set css mode css-card
[SwitchA] set css id 1
[SwitchA] set css priority 100
# Set the CSS connection mode, CSS ID, and CSS priority to CSS card
connection, 2, and 10 for SwitchB.
<Quidway> system-view
[Quidway] sysname SwitchB
[SwitchB] set css mode css-card
[SwitchB] set css id 2
[SwitchB] set css priority 10
2. Configure the management VLAN in the SVF system and enable the SVF
function on the parent.
[SwitchA] vlan batch 11
[SwitchA] dhcp enable
[SwitchA] interface vlanif 11
[SwitchA-Vlanif11] ip address 192.168.11.1 24
[SwitchA-Vlanif11] dhcp select interface
[SwitchA-Vlanif11] dhcp server option 43 ip-address 192.168.11.1
[SwitchA-Vlanif11] quit
[SwitchA] capwap source interface vlanif 11
[SwitchA] stp mode rstp
[SwitchA] uni-mng
Warning: This operation will enable the uni-mng mode and disconnect all ASs. STP calculation may
be triggered and service traffic will be affected. Continue? [Y/N]:y
● If you do not perform this step, the system will generate AS device information when
ASs connect to the SVF system. An AS name is in the format of system default name-
system MAC address.
● If you need to perform this step, ensure that the configured model and mac-address
parameters are consistent with the actual AS information. The value of mac-address
must be the AS management MAC address or system MAC address. To view the AS
management MAC address, run the display as access configuration command on the
AS. If the management MAC displays --, the value of mac-address is the system MAC
address. If the configured parameters are inconsistent with the actual AS information,
the AS cannot go online.
[SwitchA-um] as name as1 model S5320-28P-SI-AC mac-address 00e0-fc00-0011
[SwitchA-um-as-as1] quit
[SwitchA-um] as name as2 model S5320-28P-SI-AC mac-address 00e0-fc00-0022
[SwitchA-um-as-as2] quit
# Configure the fabric ports that connect AS1 to AS4 and AS3 to AS5.
[SwitchA] uni-mng
[SwitchA-um] as name as1
[SwitchA-um-as-as1] down-direction fabric-port 4 member-group interface eth-trunk 4
[SwitchA-um-as-as1] port eth-trunk 4 trunkmember interface gigabitethernet 0/0/23 to 0/0/24
[SwitchA-um-as-as1] quit
[SwitchA-um] as name as3
[SwitchA-um-as-as3] down-direction fabric-port 5 member-group interface eth-trunk 5
[SwitchA-um-as-as3] port eth-trunk 5 trunkmember interface gigabitethernet 0/0/23 to 0/0/24
[SwitchA-um-as-as3] quit
[SwitchA-um] quit
● Before restarting an AS, check whether the port that connects this AS to the parent is a
downlink port. You can run the display port connection-type access all command on
this AS to view all downlink ports on it. If this port is a downlink port, run the uni-mng
up-direction fabric-port command on this AS to configure this port as an uplink port
before restarting this AS. Otherwise, this AS cannot go online.
● Before connecting an AS to the parent, ensure that the AS has no configuration file and
no input on the console port.
# After connecting cables, run the display as all command to check whether
ASs have connected to the SVF system.
[SwitchA] display as all
Total: 5, Normal: 5, Fault: 0, Idle: 0, Version mismatch: 0
--------------------------------------------------------------------------------
No. Type MAC IP State Name
--------------------------------------------------------------------------------
0 S5320-SI 00e0-fc00-0011 192.168.11.254 normal as1
1 S5320-SI 00e0-fc00-0022 192.168.11.253 normal as2
2 S5320-SI 00e0-fc00-0033 192.168.11.252 normal as3
3 S5320-LI 00e0-fc00-0044 192.168.11.251 normal as4
4 S5320-LI 00e0-fc00-0055 192.168.11.250 normal as5
--------------------------------------------------------------------------------
When the State field in the command output displays normal for an AS, the
AS has connected to the SVF system.
# Run the display uni-mng topology information command to view SVF
topology information.
[SwitchA] display uni-mng topology information
The topology information of uni-mng network:
<-->: direct link <??>: indirect link
T: Trunk ID *: independent AS
------------------------------------------------------------------------------
Local MAC Hop Local Port T || T Peer Port Peer MAC
------------------------------------------------------------------------------
00e0-fc00-3456 0 GE1/1/0/1 1 <-->0 GE0/0/27 00e0-fc00-0011
00e0-fc00-3456 0 GE2/1/0/1 1 <-->0 GE0/0/28 00e0-fc00-0011
00e0-fc00-3456 0 GE1/1/0/2 2 <-->0 GE0/0/27 00e0-fc00-0022
00e0-fc00-3456 0 GE2/1/0/2 2 <-->0 GE0/0/28 00e0-fc00-0022
00e0-fc00-3456 0 GE1/1/0/3 3 <-->0 GE0/0/27 00e0-fc00-0033
00e0-fc00-3456 0 GE2/1/0/3 3 <-->0 GE0/0/28 00e0-fc00-0033
00e0-fc00-0011 1 GE0/0/23 4 <-->0 GE0/0/11 00e0-fc00-0044
00e0-fc00-0011 1 GE0/0/24 4 <-->0 GE0/0/12 00e0-fc00-0044
00e0-fc00-0033 1 GE0/0/23 5 <-->0 GE0/0/11 00e0-fc00-0055
00e0-fc00-0033 1 GE0/0/24 5 <-->0 GE0/0/12 00e0-fc00-0055
------------------------------------------------------------------------------
Total items displayed : 10
# Run the display uni-mng upgrade-info verbose command to view all AS
version information.
[SwitchA] display uni-mng upgrade-info verbose
The total number of AS is : 5
----------------------------------------------------------------------------
AS name : as1
Work status : NO-UPGRADE
Startup system-software : flash:/s5320si.cc
Startup version : V200R010C00
Startup patch : --
Next startup system-software : --
Next startup patch : --
Download system-software : --
Download version : --
Download patch : --
Method : --
Upgrading phase : --
Last operation result : --
Error reason : --
Last operation time : --
----------------------------------------------------------------------------
AS name : as2
Work status : NO-UPGRADE
Startup system-software : flash:/s5320si.cc
Startup version : V200R010C00
Startup patch : --
Next startup system-software : --
Next startup patch : --
Download system-software : --
Download version : --
Download patch : --
Method : --
Upgrading phase : --
Last operation result : --
Error reason : --
Last operation time : --
----------------------------------------------------------------------------
AS name : as3
Work status : NO-UPGRADE
Startup system-software : flash:/s5320si.cc
Startup version : V200R010C00
Startup patch : --
Next startup system-software : --
Next startup patch : --
Download system-software : --
Download version : --
Download patch : --
Method : --
Upgrading phase : --
Last operation result : --
Error reason : --
Last operation time : --
----------------------------------------------------------------------------
AS name : as4
Work status : NO-UPGRADE
Startup system-software : flash:/s5320li.cc
Startup version : V200R010C00
Startup patch : --
Next startup system-software : --
Next startup patch : --
Download system-software : --
Download version : --
Download patch : --
Method : --
Upgrading phase : --
Last operation result : --
Error reason : --
Last operation time : --
----------------------------------------------------------------------------
AS name : as5
Work status : NO-UPGRADE
Startup system-software : flash:/s5320li.cc
Startup version : V200R010C00
Startup patch : --
Next startup system-software : --
Next startup patch : --
Download system-software : --
Download version : --
Download patch : --
Method : --
Upgrading phase : --
Last operation result : --
Error reason : --
Last operation time : --
----------------------------------------------------------------------------
5. Configure service profiles and bind them to ASs.
# Configure an AS administrator profile and bind it to all ASs.
[SwitchA] uni-mng
[SwitchA-um] as-admin-profile name admin_profile
[SwitchA-um-as-admin-admin_profile] user asuser password YsHsjx_202206
[SwitchA-um-as-admin-admin_profile] quit
[SwitchA-um] as-group name admin_group
[SwitchA-um-as-group-admin_group] as name-include as
[SwitchA-um-as-group-admin_group] as-admin-profile admin_profile
[SwitchA-um-as-group-admin_group] quit
# Configure network basic profiles and bind them to AS ports.
[SwitchA-um] network-basic-profile name basic_profile_1
[SwitchA-um-net-basic-basic_profile_1] user-vlan 10
[SwitchA-um-net-basic-basic_profile_1] quit
[SwitchA-um] network-basic-profile name basic_profile_2
[SwitchA-um-net-basic-basic_profile_2] user-vlan 20
[SwitchA-um-net-basic-basic_profile_2] quit
[SwitchA-um] port-group name port_group_1
[SwitchA-um-portgroup-port_group_1] as name as1 interface all
[SwitchA-um-portgroup-port_group_1] as name as2 interface gigabitethernet 0/0/1 to 0/0/23 //
GigabitEthernet0/0/24 connects AS2 to the AP.
[SwitchA-um-portgroup-port_group_1] as name as4 interface all
[SwitchA-um-portgroup-port_group_1] network-basic-profile basic_profile_1
[SwitchA-um-portgroup-port_group_1] quit
[SwitchA-um] port-group name port_group_2
[SwitchA-um-portgroup-port_group_2] as name as3 interface all
[SwitchA-um-portgroup-port_group_2] as name as5 interface all
[SwitchA-um-portgroup-port_group_2] network-basic-profile basic_profile_2
[SwitchA-um-portgroup-port_group_2] quit
[SwitchA-um] quit
# Configure a user access profile and bind it to all AS ports.
[SwitchA] dot1x-access-profile name 1
[SwitchA-dot1x-access-profile-1] quit
[SwitchA] authentication-profile name dot1x_auth
[SwitchA-authen-profile-dot1x_auth] dot1x-access-profile 1
[SwitchA-authen-profile-dot1x_auth] quit
[SwitchA] uni-mng
[SwitchA-um] user-access-profile name access_profile
[SwitchA-um-user-access-access_profile] authentication-profile dot1x_auth
[SwitchA-um-user-access-access_profile] quit
[SwitchA-um] port-group name port_group_1
[SwitchA-um-portgroup-port_group_1] user-access-profile access_profile
[SwitchA-um-portgroup-port_group_1] quit
[SwitchA-um] port-group name port_group_2
[SwitchA-um-portgroup-port_group_2] user-access-profile access_profile
[SwitchA-um-portgroup-port_group_2] quit
# Commit the configurations so that the configurations in service profiles can
be delivered to ASs.
[SwitchA-um] commit as all
Warning: Committing the configuration will take a long time. Continue?[Y/N]: y
# Run the display uni-mng commit-result profile command to check
whether the configurations in service profiles have been delivered to ASs.
[SwitchA-um] display uni-mng commit-result profile
Result of profile:
--------------------------------------------------------------------------------
AS Name Commit Time Commit/Execute Result
--------------------------------------------------------------------------------
Info: The max number of VTY users is 10, and the number
of current VTY users on line is 1.
The current login time is 2016-06-25 22:31:18+00:00.
<HUAWEI>
# Check whether service configurations of AS ports are generated.
NOTE
To check access authentication configuration, you need to run the display authentication
interface interface-type interface-number command on an AS.
Configuration Summary
1. When setting up a CSS for a parent, use the CSS card or service port
connection mode according to networking requirements. This example uses
the CSS card connection.
2. You can configure service profiles and bind them to ASs before or after the
ASs connect to the SVF system. The AS service configuration mode includes
the pre-configured and non-pre-configured modes depending on the time
services are configured. Whatever configuration mode you use, you must run
the commit as { name as-name | all } command to commit the configuration
after completing it.
– Pre-configured mode: Before ASs connect to the SVF system, pre-
configure service profiles, bind them to the ASs, save the configuration on
the parent, and then run the commit as { name as-name | all }
command to commit the configuration. When the ASs connect to the SVF
system, configurations in the service profiles are automatically delivered
to the ASs.
– Non-pre-configured mode: After ASs connect to the SVF system,
configure service profiles, bind them to the ASs, and then run the
commit as { name as-name | all } command to commit the
configuration so that configurations in the service profiles can be
delivered to the ASs.
3. After the SVF function is enabled, the Spanning Tree Protocol (STP) and Link
Layer Discovery Protocol (LLDP) functions are enabled globally on the parent.
Pay attention to the following points when using the STP and LLDP functions
in an SVF system:
– You can disable the STP and LLDP functions only on ports, not globally.
– Do not disable the LLDP function on member ports of a fabric port, ports
connected to APs, and AP uplink ports. Otherwise, the SVF topology will
become abnormal.
4. After the SVF function is enabled, the parent will change STP to Rapid
Spanning Tree Protocol (RSTP) and set the priority of instance 0 to 28762
using the stp instance 0 priority 28672 command. Note that the priority of
instance 0 cannot be set to a value greater than 28672. After the SVF function
is disabled, the default priority of instance 0 is restored. When the SVF
function is enabled or disabled, STP recalculates the port roles and changes
the port status. Traffic on the ports will be interrupted temporarily.
5. The MAD relay function is automatically enabled on the Eth-Trunk to which a
downlink fabric port is bound, and the MAD function is automatically enabled
on the Eth-Trunk to which an uplink fabric port is bound to perform MAD in
an AS that is a stack. When the standby switch in the AS is removed, MAD
cannot be performed because the standby switch restarts automatically
without saving the configuration.
6. To prevent the SVF function from being affected, do not perform MIB
operations to modify the configuration automatically generated in an SVF
system, for example, the configuration of STP, LLDP, and Eth-Trunk to which a
fabric port is bound.
7. If an AP has connected to the parent before the SVF function is enabled, the
parent cannot collect topology information about the AP after the uni-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.
8. On the parent, there may be a delay in displaying the output of some
commands executed on ASs, including the patch delete all and patch load
filename all [ active | run ] commands.
9. In an SVF system, the maximum frame length allowed by ports cannot be
configured on an AS. Therefore, the maximum frame length is the default
value 9216 (including the CRC field).
10. Internal attacks of a management VLAN will cause ASs to disconnect from
the SVF system. You need to shut down the attacked ports or remove the
ports from the management VLAN after identifying the attack source.
11. After an AS disconnects from the SVF system, in versions earlier than
V200R012C00, all downlink ports of the AS will be shut down. In
V200R012C00 and later versions, to ensure that downlink networks of the AS
can communicate with each other, downlink ports of the AS will not be shut
down.
12. Configured Control and Provisioning of Wireless Access Points (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.
13. In the SVF system, network access rights available before users pass network
admission control (NAC) authentication can be authorized through
authentication-free rules instead of a user control list (UCL) group.
14. SVF does not support built-in Portal servers.
● When the parent version is earlier than V200R011C10, the AS version must be
the same as the parent version. Otherwise, this AS cannot go online. For
example, if the parent version is V200R010C00, the AS version must also be
V200R010C00.
● When the parent version is V200R011C10 or later, the parent version and AS
version can be different, but the parent version must be higher than or the
same as the AS version and the AS version must also be V200R011C10 or
later.
● 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.
● If an AS is a stack set up using service ports, the AS must join an SVF system
after having the stacking function configured. This limitation does not apply
to an AS that is a stack set up using stack cards.
● When a cluster switch system (CSS) functioning as the parent is faulty:
– If one member switch in the CSS is faulty, the SVF function is not
affected.
– If the CSS splits but two member switches are working normally, the SVF
function becomes unavailable because ASs do not know which switch is
the parent. In this situation, you are advised to configure the dual-active
detection (DAD) function.
Networking Requirements
A new campus network has a large number of wired access devices. The widely
distributed access devices complicate management and configuration of the
access layer. Unified management and configuration of wired access devices is
required to reduce the management cost.
In this example, complete the following operations on access devices:
● Configure the administrator user name and password for access devices.
● Assign VLANs to ports of access devices.
● Set the user access authentication mode to 802.1X authentication.
As shown in Figure 4-41, two aggregation switches (SwitchA and SwitchB) set up
a stack to improve reliability and function as the parent to connect to multiple
ASs. Multiple active detection (MAD) in direct mode must be configured on the
parent to avoid conflicts when the stack splits.
In this example, the parent is S6320-26Q-EI-24S-AC, and ASs are S5300-28P-LI-AC.
Data plan
Item Data Description
Ports that connect the XGE0/0/1 and XGE1/0/1 Add the two ports to
parent to AS1 Eth-Trunk1 and bind
them to Fabric-port 1.
Ports that connect the XGE0/0/2 and XGE1/0/2 Add the two ports to
parent to AS2 Eth-Trunk2 and bind
them to Fabric-port 2.
Ports that connect the XGE0/0/3 and XGE1/0/3 Add the two ports to
parent to AS3 Eth-Trunk3 and bind
them to Fabric-port 3.
Configuration Roadmap
1. Set up a stack between the parent switches using the service port connection
mode. Then set the stack working mode to parent and configure MAD in
direct mode to ensure high reliability of the SVF system.
2. Enable the SVF function on the parent.
3. Configure AS access parameters, including AS names (optional),
authentication mode, and fabric ports that connect the parent to ASs.
4. Connect ASs to the parent using cables.
5. Configure service profiles and bind them to ASs.
6. Log in to ASs to check the service configurations of the ASs.
Procedure
Step 1 Set up a stack between the two switches used as the parent. Set the stack working
mode to parent and configure MAD in direct mode.
# Power off SwitchA and SwitchB, connect the physical member ports with QSFP+
copper ports, and then power on the switches. Connect the member port of logical
stack port 1 on one switch to the member port of logical stack port 2 on the other
switch.
# Log in to the stack and configure it to work in parent mode.
NOTE
Step 2 Configure the management VLAN in the SVF system and enable the SVF function
on the parent.
[SwitchA] vlan batch 11
[SwitchA] dhcp enable
[SwitchA] interface vlanif 11
● If you do not perform this step, the system will generate AS device information when ASs
connect to the SVF system. An AS name is in the format of system default name-system
MAC address.
● If you need to perform this step, ensure that the configured model and mac-address
parameters are consistent with the actual AS information. The value of mac-address must
be the AS management MAC address or system MAC address. To view the AS management
MAC address, run the display as access configuration command on the AS. If the
management MAC displays --, the value of mac-address is the system MAC address. If the
configured parameters are inconsistent with the actual AS information, the AS cannot go
online.
[SwitchA-um] as name as1 model S5300-28P-LI-AC mac-address 00e0-fc00-0011
[SwitchA-um-as-as1] quit
[SwitchA-um] as name as2 model S5300-28P-LI-AC mac-address 00e0-fc00-0022
[SwitchA-um-as-as2] quit
[SwitchA-um] as name as3 model S5300-28P-LI-AC mac-address 00e0-fc00-0033
[SwitchA-um-as-as3] quit
Step 4 Run the reset saved-configuration command to clear the configurations of ASs,
restart the ASs, and then connect ASs to the parent using cables. Subsequently, an
SVF system is set up.
NOTE
● Before restarting an AS, check whether the port that connects this AS to the parent is a
downlink port. You can run the display port connection-type access all command on this
AS to view all downlink ports on it. If this port is a downlink port, run the uni-mng up-
direction fabric-port command on this AS to configure this port as an uplink port before
restarting this AS. Otherwise, this AS cannot go online.
● Before connecting an AS to the parent, ensure that the AS has no configuration file and no
input on the console port.
# After connecting cables, run the display as all command to check whether ASs
have connected to the SVF system.
[SwitchA] display as all
Total: 3, Normal: 3, Fault: 0, Idle: 0, Version mismatch: 0
--------------------------------------------------------------------------------
No. Type MAC IP State Name
--------------------------------------------------------------------------------
0 S5300-P-LI 00e0-fc00-0011 192.168.11.254 normal as1
1 S5300-P-LI 00e0-fc00-0022 192.168.11.253 normal as2
2 S5300-P-LI 00e0-fc00-0033 192.168.11.252 normal as3
--------------------------------------------------------------------------------
When the State field in the command output displays normal for an AS, the AS
has connected to the SVF system.
# Run the display uni-mng topology information command to view SVF
topology information.
[SwitchA] display uni-mng topology information
The topology information of uni-mng network:
<-->: direct link <??>: indirect link
T: Trunk ID *: independent AS
------------------------------------------------------------------------------
Local MAC Hop Local Port T || T Peer Port Peer MAC
------------------------------------------------------------------------------
00e0-fc00-1100 0 XGE0/0/1 1 <-->0 GE0/0/27 00e0-fc00-0011
00e0-fc00-1100 0 XGE1/0/1 1 <-->0 GE0/0/28 00e0-fc00-0011
00e0-fc00-1100 0 XGE0/0/2 2 <-->0 GE0/0/27 00e0-fc00-0022
00e0-fc00-1100 0 XGE1/0/2 2 <-->0 GE0/0/28 00e0-fc00-0022
00e0-fc00-1100 0 XGE0/0/3 3 <-->0 GE0/0/27 00e0-fc00-0033
When the Commit/Execute Result field in the command output displays Success/
Success for an AS, the configurations in service profiles have been delivered to the
AS.
Step 6 Log in to ASs to check the service configurations of the ASs. The following uses
the login to AS1 as example.
# Run the attach as name as-name command on the parent to log in to AS1 and
check whether the configured login user name and password are correct.
[SwitchA-um] attach as name as1
Info: Connecting to the remote AS now. Use the quit command to return to the user view.
Trying 192.168.11.254 ...
Press CTRL+K to abort
Connected to 192.168.11.254 ...
Info: The max number of VTY users is 10, and the number
of current VTY users on line is 1.
The current login time is 2016-03-25 22:31:18+00:00.
<HUAWEI>
----End
Configuration Summary
1. You can configure service profiles and bind them to ASs before or after the
ASs connect to the SVF system. The AS service configuration mode includes
the pre-configured and non-pre-configured modes depending on the time
services are configured. Whatever configuration mode you use, you must run
the commit as { name as-name | all } command to commit the configuration
after completing it.
– Pre-configured mode: Before ASs connect to the SVF system, pre-
configure service profiles, bind them to the ASs, save the configuration on
the parent, and then run the commit as { name as-name | all }
command to commit the configuration. When the ASs connect to the SVF
system, configurations in the service profiles are automatically delivered
to the ASs.
– Non-pre-configured mode: After ASs connect to the SVF system,
configure service profiles, bind them to the ASs, and then run the
commit as { name as-name | all } command to commit the
configuration so that configurations in the service profiles can be
delivered to the ASs.
2. After the SVF function is enabled, the Spanning Tree Protocol (STP) and Link
Layer Discovery Protocol (LLDP) functions are enabled globally on the parent.
Pay attention to the following points when using the STP and LLDP functions
in an SVF system:
– You can disable the STP and LLDP functions only on ports, not globally.
– Do not disable the LLDP function on member ports of a fabric port.
Otherwise, the SVF topology will become abnormal.
3. After the SVF function is enabled, the parent will change STP to Rapid
Spanning Tree Protocol (RSTP) and set the priority of instance 0 to 28762
using the stp instance 0 priority 28672 command. Note that the priority of
instance 0 cannot be set to a value greater than 28672. After the SVF function
In centralized mode, all service configurations for ASs are performed on the
parent. Therefore, which services can be configured on ASs depends on the
services that can be configured on the parent, but not depend on the services
supported by a standalone access switch.
Method Description
Profile- Create service profiles and specified device and port groups on the
based parent, bind the service profiles to the device and port groups, and
configura then run the commit as { name as-name | all } command to deliver
tion AS service configurations. If multiple ASs or ports in an SVF system
need the same configurations, you can add these ASs or ports to the
same group for batch configuration. In this manner, the
configuration efficiency is improved.
Precautions
● Not all services can be configured on an AS. For the services that can be
configured on an AS, see 4.3.1.3 SVF Service Deployment Limitations.
● In versions earlier than V200R020C00, you do not need to configure an AS
administrator before configuring services for an AS in centralized mode. In
V200R020C00 and later versions, before configuring services for an AS in
centralized mode, configure an AS administrator and deliver the configuration
to the AS.
● Before configuring services for an AS, ensure that the AS has gone online.
● In this example, services for ASs are configured in centralized mode.
Networking Requirements
As shown in Figure 4-42, to facilitate management and configuration of a new
campus network, devices at the access, aggregation, and core layers have set up
an SVF system. In this system, two core switches set up a CSS and function as the
parent, aggregation switches function as level-1 ASs, and access switches function
as level-2 ASs. The gateway is deployed on the parent. You need to perform the
following operations on the parent to configure services for ASs:
● Configure the administrator user name and password for each AS.
● Add interfaces on each AS to VLANs.
● Connect an access switch to a server using an Eth-Trunk.
● Set the authentication mode for PCs and printers to MAC address
authentication.
● Configure traffic suppression, traffic rate limiting, and port security for ASs to
improve security.
● Configure descriptions for AS interfaces to identify the interface usage.
In this example, the S9300 functions as the parent, the S5320-28P-SI-AC functions
as a level-1 AS, and the S5320-12TP-LI-AC functions as a level-2 AS.
Data Plan
Item Data Description
Configuration Roadmap
1. Configure the user name and password of the AS administrator in an AS
administrator profile.
2. Create an Eth-Trunk interface for a level-2 AS to connect to a server and add
physical interfaces to this Eth-Trunk interface.
3. Configure a description for each interface to identify the interface usage.
4. Configure VLANs on ASs in batches.
5. Add interfaces to VLANs using network basic profiles.
6. Configure traffic suppression and traffic rate limiting in a network enhanced
profile.
7. Configure port security in a network enhanced profile and set the maximum
number of secure MAC addresses that can be learned on an interface.
8. Configure the user authentication mode in a user access profile.
Procedure
NOTE
After the configuration is complete, run the commit as { name as-name | all } command in
the uni-mng view to commit the configuration so that the configuration can be delivered to
ASs and take effect.
1. Run the display as all command to check whether each AS has gone online.
If the value of State of an AS is normal, the AS goes online normally.
<Quidway> display as all
Total: 4, Normal: 4, Fault: 0, Idle: 0, Version mismatch: 0
--------------------------------------------------------------------------------
No. Type MAC IP State Name
--------------------------------------------------------------------------------
0 S5320-SI 00e0-fc00-0011 192.168.11.254 normal as1
1 S5320-SI 00e0-fc00-0022 192.168.11.253 normal as2
2 S5320-SI 00e0-fc00-0033 192.168.11.252 normal as3
3 S5320-LI 00e0-fc00-0044 192.168.11.251 normal as4
4 S5320-LI 00e0-fc00-0055 192.168.11.250 normal as5
--------------------------------------------------------------------------------
2. Configure the user name and password of the AS administrator in an AS
administrator profile.
After the user name and password are configured for an AS, you need to
enter the user name and password when logging in to the AS through the
console port. However, when running the attach as command on the parent
to log in to an AS, you can automatically log in to the AS without entering
the user name and password of the AS administrator.
<Quidway> system-view
[Quidway] sysname Parent
[Parent] uni-mng
[Parent-um] as-admin-profile name admin_profile // Create an AS administrator profile.
[Parent-um-as-admin-admin_profile] user asuser password YsHsjx_202206 // Configure the user
name and password of the AS administrator in the AS administrator profile.
[Parent-um-as-admin-admin_profile] quit
[Parent-um] as-group name admin_group // Create an AS group.
[Parent-um-as-group-admin_group] as name-include as // Add ASs of which the name contains as
to the AS group.
[Parent-um-as-group-admin_group] as-admin-profile admin_profile // Bind the AS administrator
profile to the AS group.
[Parent-um-as-group-admin_group] quit
3. Create an Eth-Trunk interface on AS 5 and add physical interfaces to the Eth-
Trunk interface.
# Configure port groups and bind a network basic profile to each port group.
[Parent-um] port-group name port_group_1 // Create a port group.
[Parent-um-portgroup-port_group_1] as name as4 interface gigabitethernet 0/0/2 // Add the port
on AS 4 to the port group.
[Parent-um-portgroup-port_group_1] network-basic-profile basic_profile_1 // Bind the network
basic profile basic_profile_1 to this port group.
[Parent-um-portgroup-port_group_1] quit
[Parent-um] port-group name port_group_2
[Parent-um-portgroup-port_group_2] as name as4 interface gigabitethernet 0/0/3
[Parent-um-portgroup-port_group_2] network-basic-profile basic_profile_2
[Parent-um-portgroup-port_group_2] quit
[Parent-um] port-group name port_group_3
[Parent-um-portgroup-port_group_3] as name as5 interface eth-trunk 10
[Parent-um-portgroup-port_group_3] network-basic-profile basic_profile_3
[Parent-um-portgroup-port_group_3] quit
[Parent-um] port-group name port_group_4
[Parent-um-portgroup-port_group_4] as name as5 interface gigabitethernet 0/0/4
[Parent-um-portgroup-port_group_4] network-basic-profile basic_profile_4
[Parent-um-portgroup-port_group_4] quit
10. Log in to ASs to check their service configurations. The following uses AS 4 as
an example.
# On the parent, run the attach as name as-name command to log in to AS
4. You can run the quit command to log out the AS after a successful login.
[Parent-um] attach as name as4
Info: Connecting to the remote AS now. Use the quit command to return to the user
view.
Trying 192.168.11.72 ...
Press CTRL+K to abort
Connected to 192.168.11.72 ...
interface Eth-Trunk3
port link-type hybrid
port hybrid tagged vlan 1 11 20 30 40 50
stp root-protection
stp edged-port disable
mode lacp
mad relay
#
interface GigabitEthernet1/1/0/1
eth-trunk 1
#
interface GigabitEthernet1/1/0/2
eth-trunk 2
#
interface GigabitEthernet1/1/0/3
eth-trunk 3
#
interface GigabitEthernet1/2/0/1
mad detect mode direct
#
interface GigabitEthernet2/1/0/1
eth-trunk 1
#
interface GigabitEthernet2/1/0/2
eth-trunk 2
#
interface GigabitEthernet2/1/0/3
eth-trunk 3
#
interface GigabitEthernet2/2/0/1
mad detect mode direct
#
capwap source interface vlanif11
#
as-auth
whitelist mac-address 00e0-fc00-0011
whitelist mac-address 00e0-fc00-0022
whitelist mac-address 00e0-fc00-0033
whitelist mac-address 00e0-fc00-0044
whitelist mac-address 00e0-fc00-0055
#
uni-mng
as name as1 model S5320-28P-SI-AC mac-address 00e0-fc00-0011
down-direction fabric-port 4 member-group interface Eth-Trunk 4
port Eth-Trunk 4 trunkmember interface GigabitEthernet 0/0/23
port Eth-Trunk 4 trunkmember interface GigabitEthernet 0/0/24
as name as2 model S5320-28P-SI-AC mac-address 00e0-fc00-0022
as name as3 model S5320-28P-SI-AC mac-address 00e0-fc00-0033
down-direction fabric-port 5 member-group interface Eth-Trunk 5
port Eth-Trunk 5 trunkmember interface GigabitEthernet 0/0/23
port Eth-Trunk 5 trunkmember interface GigabitEthernet 0/0/24
as name as4 model S5320-12TP-LI-AC mac-address 00e0-fc00-0044
as name as5 model S5320-12TP-LI-AC mac-address 00e0-fc00-0055
uni eth-trunk 10
port eth-trunk 10 trunkmember interface GigabitEthernet 0/0/2
port eth-trunk 10 trunkmember interface GigabitEthernet 0/0/3
direct-command view GigabitEthernet 0/0/2 command description connect-to-pc1
direct-command view GigabitEthernet 0/0/3 command description connect-to-pc2
direct-command view Eth-Trunk 10 command description connect-to-server
direct-command view GigabitEthernet 0/0/4 command description connect-to-printer
direct-command view GigabitEthernet 0/0/4 command port-security max-mac-num 5
interface fabric-port 1
port member-group interface Eth-Trunk 1
interface fabric-port 2
port member-group interface Eth-Trunk 2
interface fabric-port 3
port member-group interface Eth-Trunk 3
as service-vlan authorization 20 30 40 50
as-admin-profile name admin_profile