01-02 Device Management
01-02 Device Management
2 Device Management
2.1 Stack
2.2 SVF
2.3 Cloud-based Management
2.4 PoE
2.5 Monitor
2.6 OPS
2.7 Energy-Saving Management
2.8 Information Center
2.9 Fault Management
2.10 NTP
2.11 PTP
2.12 Synchronous Ethernet
2.1 Stack
2.1.1 Recommended Stack Deployment Scenarios
Scenario 1: The Stack System Operates on Aggregation Switches
This is the most common scenario when aggregation switches set up a stack system, as shown
in Figure 2-1.
The following switch models can set up a stack system in this scenario: S6700EI, S6720S-EI,
S6720EI, S6720HI, S5700HI, S5710HI, S5710EI, S5700EI, S5700SI, S5720EI, S5720HI,
and S5730HI.
In this scenario, each switch in a stack connects to a core device through Eth-Trunk. The stack
system simplifies management of aggregation devices and improves uplink reliability of
access devices.
Aggregation Stack
Access
AP
User
Core CSS
AC
Aggregation
Stack
Access
AP
User
Aggregation
Access
Stack1 Stack2
Stack3
User AP
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:
l 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.
l 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.
Feature Limitations
Stack Setup Guidelines
l A stack contains a maximum of five, eight, or nine stack members depending on switch
models. To ensure high forwarding performance and reliability, ensure that the number
of stack members of each switch series does not exceed the recommended value. For
example, the recommended number of S5700LI switches in a stack is 2 to 5. For the
recommended value of each switch series, see "Service Port Stacking Support" or "Stack
Card Stacking Support".
l When setting up a stack containing a mix of different switch models, follow the
following rules:
– A stack cannot be set up among different switch series. For example, a stack cannot
be set up among the S5700 and S6700 switches.
– A stack cannot be set up among different switch models of the same switch series.
For example, a stack cannot be set up among the S5720EI and S5720HI switches.
– A stack can be set up among only certain different switch models of the same
switch series. For example, a stack can be set up among the S5720SI and S5720S-
SI switches but not among the S5720LI and S5720S-LI switches. For details about
whether a stack can be set up among different switch models, see stack support of
different switch models in Stacking Support and Version Requirements. As
described in Remarks of S6720LI and S6720S-LI Service Port Stacking
Support, a stack can be set up among all S6720LI models, among all S6720S-LI
models, but not among the S6720LI and S6720S-LI models.
Version restrictions:
l 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.
MAD specifications:
l You can configure a maximum of eight direct detection links for each member switch in
a stack.
l You can configure the relay mode on a maximum of four Eth-Trunks in a stack.
l 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.
After multiple switches form a stack, the following features cannot be configured in the
stack:
When you establish a stack on the switches that support both stack card connection and
service port connection, such as S5720-C-EI, note the following:
l All member switches must use the same stack connection mode.
l When a member switch has stack cards installed and the service port stack configuration,
the switch uses the service port connection mode to establish a stack. It does not use the
stack card connection mode even though a stack fails to be established in service port
connection mode and stack cards are connected correctly.
l A switch uses the stack card connection mode to establish a stack only when it has no
service port stack configuration.
l If a switch is currently using the stack card connection mode, perform the service port
stack configuration on the switch before changing the stack connection mode to service
port connection. After the service port stack configuration is complete, the switch uses
the service port connection mode when restarting.
l If a switch using the stack card connection mode has service port configuration, a
smooth upgrade cannot be performed on the switch.
l If a switch is currently using the service port connection mode, correctly connect stack
cards and stack cables and clear the existing service port stack configuration before
changing the stack connection mode to stack card connection. You can use the reset
stack-port configuration command to clear the existing service port stack
configuration.
l When changing service port connection to stack card connection, you are advised to
remove the cables connected to service ports to prevent loops.
Deployment Recommendations
l Connect a stack to other network devices using an Eth-Trunk and add one port of each
member switch to the Eth-Trunk.
l 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.
l If storm control needs to be configured on many ports, replace storm control with traffic
suppression to save CPU resources.
l If port security needs to be configured on many ports, replace port security with MAC
address learning limiting to save CPU resources.
l 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.
Licensing Requirements
Stacking is not under license control.
Version Requirements
NOTE
Switches can set up a stack through stack card connection and service port connection based on stack port
types. Service port connections are classified into ordinary and dedicated cable connections based on cable
types.
l Ordinary cable connection: Switches use optical cables, network cables, and high-speed cables to set
up a stack.
l Dedicated cable connection: Switches use dedicated stack cables to set up a stack. This connection
mode is also called zero-configuration stacking.
NOTE
For details about software mappings, visit Hardware Query Tool and search for the desired product
model.
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using other
cables may cause exceptions in the stack system, for example, frequent error-down events on stack ports.
l Combo ports cannot function as stack member ports.
l For stacking-supported service ports, some of them can be used as stack ports, whereas some can be used
as ordinary service ports.
l After a UCL group is created using the ucl-group command on S2720EI switches, a stack cannot be set
up.
l Since V200R011C10, S2720EI and S2750EI series switches can set up stacks in service port stacking
mode using dedicated stack cables.
l The number of S2750EIs used to set up a stack is recommended to be 2 to 5.
l For S2700EIs and S2710SIs, if the stack system works only in Layer 2 and Layer 3 forwarding scenarios,
the number of stack member switches is recommended to be 2 to 5. If the stack system works in user
access or gateway scenarios that require protocol interaction, the number of stack member switches is
recommended to be 2 or 3.
l The S2720EI has only one model, S2720-28TP-EI-AC, in V200R006C10, V200R009C00, and
V200R010C00. The S2720-28TP-EI-AC cannot be upgraded to V200R011C00 and later versions. The
number of S2720-28TP-EI-ACs used to set up a stack is recommended to be 2 to 5. In V200R011C10 and
later versions, the number of S2720EIs used to set up a stack is recommended to be 2 to 9.
S270 First two GE 1.5 m SFP 2.5 l Among S2700EI switches, only the
0EI ports on the stack cable Gbit/s S2700-52P-EI-AC and S2700-52P-
front panel PWR-EI support the stacking
function. A stack can be set up
between the S2700-52P-EI-AC and
S2700-52P-PWR-EI.
l A switch supports a maximum of two
logical stack ports, and each logical
stack port contains one stack member
port. A switch supports a maximum
of two stack member ports.
S271 First two GE 1.5 m SFP 2.5 l Any models of the S2710SI series
0SI ports on the stack cable Gbit/s can set up a stack.
front panel l A switch supports a maximum of two
logical stack ports, and each logical
stack port contains one stack member
port. A switch supports a maximum
of two stack member ports.
S275 Two SFP l 1 m SFP+ 2.5 l Any models of the S2750EI series
0EI optical ports passive Gbit/s can set up a stack.
high- l On an S2750EI switch, only the first
speed and second service ports from the
copper right can be configured as stack
cables member ports of a logical stack port.
l 10 m SFP l A switch supports a maximum of two
+ active logical stack ports, and each logical
high- stack port contains one or two stack
speed member ports. Each switch can use a
copper maximum of two service ports as
cables stack member ports.
l 3 m and
10 m
AOC
cables
l 6GE stack
optical
module
(SFP-6GE
-LR) and
optical
fiber
l 0.5 m and
1.5 m SFP
+
dedicated
stack
cable
(supporte
d in
V200R01
1C10 and
later
versions)
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using other
cables may cause exceptions in the stack system, for example, frequent error-down events on stack ports.
l Combo ports cannot function as stack member ports.
l For stacking-supported service ports, some of them can be used as stack ports, whereas some can be used
as ordinary service ports.
l If the stack system works only in Layer 2 and Layer 3 forwarding scenarios, the number of stack member
switches is recommended to be 2 to 5. If the stack system works in user access or gateway scenarios that
require protocol interaction, the number of stack member switches is recommended to be 2 or 3.
S370 First two GE 1.5 m SFP 2.5Gb l All models support the stacking
0EI ports on the stack cable it/s function except that a stack cannot be
front panel set up between the S3752EI and
S3728EI.
l A switch supports a maximum of two
logical stack ports, and each logical
stack port contains one stack member
port. A switch supports a maximum
of two stack member ports.
S370 First two GE 1.5 m SFP 2.5Gb l All models support the stacking
0SI ports on the stack cable it/s function except that a stack cannot be
front panel set up between the S3752SI and
S3728SI.
l A switch supports a maximum of two
logical stack ports, and each logical
stack port contains one stack member
port. A switch supports a maximum
of two stack member ports.
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using other
cables may cause exceptions in the stack system, for example, frequent error-down events on stack ports.
l The number of stacked switches is recommended to be 2 to 5.
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using
other cables may cause exceptions in the stack system, for example, frequent error-down events on
stack ports.
l Combo ports cannot function as stack member ports.
l For stacking-supported service ports, some of them can be used as stack ports, whereas some can be
used as ordinary service ports.
l S5700LI series switches are classified into S5700-P-LI, S5700-TP-LI, and S5700-X-LI based on
their uplink interface types. A stack cannot be set up between S5700-P-LI, S5700-TP-LI, and
S5700-X-LI.
l S5700S-LI series switches are classified into S5700S-P-LI and S5700S-X-LI based on their uplink
interface types. A stack cannot be set up between S5700S-P-LI and S5700S-X-LI.
l Among S5700LI series switches, only the S5700-10P-LI-AC, S5700-10P-PWR-LI-AC, S5700-28P-
LI-BAT, S5700-28P-LI-24S-BAT do not support stacking function.
l Among S5700S-LI series switches, the S5700S-28P-LI-AC and S5700S-52P-LI-AC do not support
stacking function.
l Since V200R011C10, S5700LI and S5700S-LI series switches can set up stacks in service port
stacking mode using dedicated stack cables.
l The number of stacked switches is recommended to be 2 to 5.
ur later
SF versions)
P
op
tic
al
po
rts
l 0.5 m and
1.5 m SFP
+
dedicated
stack
cable
(supporte
d in
V200R01
1C10 and
later
versions)
V200R01
1C10 and
later
versions)
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using
other cables may cause exceptions in the stack system, for example, frequent error-down events on
stack ports.
l Combo ports cannot function as stack member ports.
l For stacking-supported service ports, some of them can be used as stack ports, whereas some can be
used as ordinary service ports.
l The number of stacked switches is recommended to be 2 to 5.
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using
other cables may cause exceptions in the stack system, for example, frequent error-down events on
stack ports.
l Combo ports cannot function as stack member ports.
l For stacking-supported service ports, some of them can be used as stack ports, whereas some can be
used as ordinary service ports.
l Since V200R011C10, S5720HI series switches can set up stacks in service port stacking mode using
dedicated stack cables. S5730HI series switches of all versions can set up stacks in service port
stacking mode using dedicated stack cables.
l The number of stacked switches is recommended to be 2 to 9.
Optical ports l 1 m, 3 m, 10
on a 4-port and 5 m Gbit/s
10GE SFP+
interface card passive
high-
speed
copper
cables
l 10 m SFP
+ active
high-
speed
copper
cables
l 3 m and
10 m
AOC
cables
l 10GE
SFP+
optical
module
and
optical
fiber
Optical ports l 1 m, 3 m, 10
on an 8-port and 5 m Gbit/s
10GE SFP+
interface card passive
high-
speed
copper
cables
l 10 m SFP
+ active
high-
speed
copper
cables
l 3 m and
10 m
AOC
cables
l 10GE
SFP+
optical
module
and
optical
fiber
Electrical Category 6A 10
ports on an 8- or higher Gbit/s
port 10GE network
interface card cables (If
Category 6
cables are
used, ensure
that the
cables meet
requirements
of TSB-155.)
Optical ports l 1 m, 3 m, 40
on a 2-port and 5 m Gbit/s
40GE QSFP+
interface card passive
high-
speed
copper
cables
l QSFP+
optical
module
(QSFP-40
G-SR-BD
not
supported
) and
optical
fiber
l 10 m
QSFP+
AOC
cable
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using other
cables may cause exceptions in the stack system, for example, frequent error-down events on stack ports.
l The number of stacked switches is recommended to be 2 to 5.
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using other
cables may cause exceptions in the stack system, for example, frequent error-down events on stack ports.
l Combo ports cannot function as stack member ports.
l For stacking-supported service ports, some of them can be used as stack ports, whereas some can be used
as ordinary service ports.
l Since V200R011C10, S5710-X-LI series switches can set up stacks in service port stacking mode using
dedicated stack cables.
l The number of stacked switches is recommended to be 2 to 5.
d in
V200R01
1C10 and
later
versions)
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using other
cables may cause exceptions in the stack system, for example, frequent error-down events on stack ports.
l Combo ports cannot function as stack member ports.
l For stacking-supported service ports, some of them can be used as stack ports, whereas some can be used
as ordinary service ports.
l The number of stacked switches is recommended to be 2 to 5.
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using
other cables may cause exceptions in the stack system, for example, frequent error-down events on
stack ports.
l S5720EI series switches are classified into S5720-C-EI, S5720-PC-EI, S5720-X-EI, and S5720-P-EI
based on their uplink interface types.
l In V200R009C00 and later versions, if MPLS-incapable S5720EIs exist in a stack, this stack cannot
have MPLS enabled. If member devices in a stack are running MPLS services, adding MPLS-
incapable S5720EIs to the stack is not allowed. To check whether S5720EIs support MPLS, run the
display device capability command.
l The number of stacked switches is recommended to be 2 to 9.
S5720- Two ports on each l 1 m, 3 m, 5 m Any models of the S5720EI series can
C-EI ES5D21VST000 QSFP+ set up a stack.
and stack card passive high-
S5720- speed cables
PC-EI l QSFP+ optical
module (only
QSFP-40G-
SR4 and
QSFP-40G-
iSR4
supported) and
matching
optical fiber
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using
other cables may cause exceptions in the stack system, for example, frequent error-down events on
stack ports.
l Combo ports cannot function as stack member ports.
l For stacking-supported service ports, some of them can be used as stack ports, whereas some can be
used as ordinary service ports.
l In V200R009C00 and later versions, if MPLS-incapable S5720EIs exist in a stack, this stack cannot
have MPLS enabled. If member devices in a stack are running MPLS services, adding MPLS-
incapable S5720EIs to the stack is not allowed. To check whether S5720EIs support MPLS, run the
display device capability command.
l The number of stacked switches is recommended to be 2 to 9.
Electrical Category 6A 10
ports on a 2- or higher Gbit/s
port 10GE network
electrical cables (If
interface card Category 6
cables are
used, ensure
that the
cables meet
requirements
of TSB-155.)
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using
other cables may cause exceptions in the stack system, for example, frequent error-down events on
stack ports.
l Combo ports cannot function as stack member ports.
l For stacking-supported service ports, some of them can be used as stack ports, whereas some can be
used as ordinary service ports.
l After a UCL group is created using the ucl-group command on S5720LI&S5720S-LI switches, a
stack cannot be set up.
l S5720LI series switches are classified into S5720-P-LI, S5720-TP-LI, and S5720-X-LI based on
their uplink interface types.
l S5720S-LI series switches are classified into S5720S-P-LI, S5720S-TP-LI, and S5720S-X-LI based
on their uplink interface types.
l S5720-28X-LI-24S-AC, S5720-28X-LI-24S-DC, and S5720S-28X-LI-24S-AC do not support
electrical ports. Therefore, they cannot set up stacks using electrical ports.
l MultiGE port on the S5720-28X-PWH-LI-AC cannot be configured as a stack member port.
l If you want to set up a mixed stack of S5720SV2-28P-LI-AC and other switch models, only a mixed
stack of the S5720SV2-28P-LI-AC and S5720SV2-52P-LI-AC is supported.
l In a stack set up using electrical interfaces, when adding a new member switch or replacing a faulty
member switch, to prevent a packet loop caused by a failure to add the new member in case of
insufficient ACL resources, you are advised to configure the service ports used in both the new
switch and the stack as stack ports before connecting the switch to the stack using cables.
l Since V200R011C10, S5720LI and S5720S-LI series switches can set up stacks in service port
stacking mode using dedicated stack cables.
l The number of stacked switches is recommended to be 2 to 9.
Electrical Category 5 or 1
ports on the higher Gbit/s
front panel network
cable
Electrical Category 5 or 1
ports on the higher Gbit/s
front panel network
cable
Electrical Category 5 or 1
ports on the higher Gbit/s
front panel network
cable
Electrical Category 5 or 1
ports on the higher Gbit/s
front panel network
cable
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using
other cables may cause exceptions in the stack system, for example, frequent error-down events on
stack ports.
l Combo ports cannot function as stack member ports.
l For stacking-supported service ports, some of them can be used as stack ports, whereas some can be
used as ordinary service ports.
l After a UCL group is created using the ucl-group command on S5720SI&S5720S-SI&S5720I-SI
switches, a stack cannot be set up.
l S5720SI series switches are classified into S5720-P-SI and S5720-X-SI based on their uplink
interface types.
l S5720S-SI series switches are classified into S5720S-P-SI and S5720S-X-SI based on their uplink
interface types.
l MultiGE ports of an S5720-14X-PWH-SI-AC cannot be used as stack member ports.
l In V200R010 and later versions, any models of S5720I-SI, S5720SI and S5720S-SI can set up a
stack. When different models need to set up a stack, they must use stack ports of the same type. That
is, they either all use electrical ports on front panels or all use SFP+ or SFP optical ports. In
V200R009 and earlier versions, S5720-14X-PWH-SI-AC cannot set up a stack with S5720S-SI or
other S5720SI models. The S5720S-SI can set up a stack with all S5720SI models except
S5720-14X-PWH-SI-AC.
l Since V200R010, two SFP+ optical ports of an S5720-14X-PWH-SI-AC can be used as stack
member ports. If SFP+ optical ports of an S5720-14X-PWH-SI-AC have been configured as stack
member ports but the switch needs to be downgraded to V200R009 or an earlier version, delete the
stack member port configuration of SFP+ optical ports before the downgrade. If this configuration is
not deleted before the downgrade, a stack that cannot run normally will be set up after the
downgrade. You need to disable the stacking function to delete the stack member port configuration
of SFP+ optical ports.
l Among S5720I-SI series switches, the S5720I-6X-PWH-SI-AC and S5720I-10X-PWH-SI-AC do
not support the stacking function.
l In a stack set up using electrical interfaces, when adding a new member switch or replacing a faulty
member switch, to prevent a packet loop caused by a failure to add the new member in case of
insufficient ACL resources, you are advised to configure the service ports used in both the new
switch and the stack as stack ports before connecting the switch to the stack using cables.
l Since V200R011C10, S5720SI and S5720S-SI series switches can set up stacks in service port
stacking mode using dedicated stack cables. S5720I-SI series switches of all versions can set up
stacks in service port stacking mode using dedicated stack cables.
l The number of stacked switches is recommended to be 2 to 9.
S572 Four SFP l 1 m and 3 10 l When SFP optical ports are used as
0-P- optical ports m SFP+ Gbit/s stack ports, a switch supports a
SI passive maximum of two logical stack ports,
and high- and each logical stack port contains
S572 speed one or two stack member ports. Each
0S-P- copper switch can use a maximum of four
SI cables service ports as stack member ports.
l 5 m SFP+ When a logical stack port contains
passive two stack member ports, the logical
high- stack port can contain only stack
speed member ports 1 and 2 or stack
copper member ports 3 and 4.
cables l When electrical ports on the front
(supporte panel are used as stack ports, a switch
d in supports a maximum of two logical
V200R00 stack ports, and each logical stack
9 and port supports at least one stack
later member port and at most eight stack
versions) member ports. A switch supports a
l 10 m SFP maximum of 16 stack member
+ active ports.On a switch with 48 electrical
high- ports, the first and last 24 ports must
speed be added to two separate logical stack
copper ports to ensure that a stack can be set
cables up successfully.
l 3 m and l Since V200R010, if stack member
10 m ports are connected using 1 m or 3 m
AOC SFP+ passive high-speed copper
cables cables, their working speed can be
increased to 12 Gbit/s using the stack
l 10GE port speed command. After their
SFP+ working speed is increased to 12
optical Gbit/s, switches using these ports
module cannot set up a stack with switches
and using ports with the working speed
optical 10 Gbit/s.
fiber
l 0.5 m and
1.5 m SFP
+
dedicated
stack
cable
(supporte
d in
V200R01
1C10 and
later
versions)
Electrical Category 5 or 1
ports on the higher Gbit/s
front panel network
cable
S572 Four SFP+ l 1 m and 3 10 l When SFP+ optical ports are used as
0-X- optical ports m SFP+ Gbit/s stack ports, a switch supports a
SI passive maximum of two logical stack ports,
and high- and each logical stack port contains
S572 speed one or two stack member ports. Each
0S-X- copper switch can use a maximum of four
SI cables service ports as stack member ports.
l 5 m SFP+ When a logical stack port contains
passive two stack member ports, the logical
high- stack port can contain only stack
speed member ports 1 and 2 or stack
copper member ports 3 and 4.
cables l When electrical ports or downlink
(supporte SFP optical ports on the front panel
d in are used as stack ports, a switch
V200R00 supports a maximum of two logical
9 and stack ports, and each logical stack
later port supports at least one stack
versions) member port and at most eight stack
member ports. A switch supports a
l 10 m SFP
maximum of 16 stack member
+ active
ports.On a switch with 48 electrical
high-
ports, the first and last 24 ports must
speed
be added to two separate logical stack
copper
ports to ensure that a stack can be set
cables
up successfully.
l 3 m and
l Since V200R010, several new
10 m
S5720-X-SI models with downlink
AOC
SFP optical ports are available. These
cables
switches allow using downlink SFP
l 10GE optical ports on the front panel as
SFP+ stack member ports. If one member
optical switch uses downlink SFP optical
module ports as stack member ports, all the
and other member switches must also use
optical downlink SFP optical ports as stack
fiber member ports.
l 0.5 m and l Since V200R010, if stack member
1.5 m SFP ports are connected using 1 m or 3 m
+ SFP+ passive high-speed copper
dedicated cables, their working speed can be
stack increased to 12 Gbit/s using the stack
cable port speed command. After their
(supporte working speed is increased to 12
d in Gbit/s, switches using these ports
V200R01
Electrical Category 5 or 1
ports on the higher Gbit/s
front panel network
cable
Downlink GE SFP 1
SFP optical optical Gbit/s
ports on the module and
front panel optical fiber
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using
other cables may cause exceptions in the stack system, for example, frequent error-down events on
stack ports.
l Stack card stacking and service port stacking (including ordinary cable stacking and dedicated stack
cable stacking) cannot be used together. If service port configurations are correct, service port
stacking is preferred over stack card stacking. If stack card stacking has been used to set up a stack,
to use service port stacking to set up the stack, you need to restart the stack to make service port
stacking takes effect after configuring service port stacking.
l 40GE ports on the ES5D21VST000 stack card cannot be used together with 40GE ports on the
ES5D21Q04Q01 card to set up a stack.
l The number of stacked switches is recommended to be 2 to 9.
S5730S Two stack ports l 1 m, 3 m, 5 m l Any models of the S5730SI can set
I on the QSFP+ up a stack.
ES5D21VST000 passive high- l 40GE ports do not support the
dedicated stack speed cables stacking function after they are split
card l QSFP+ optical into 10GE ports.
module and
fiber
l 10 m QSFP+
AOC cable
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using
other cables may cause exceptions in the stack system, for example, frequent error-down events on
stack ports.
l Combo ports cannot function as stack member ports.
l For stacking-supported service ports, some of them can be used as stack ports, whereas some can be
used as ordinary service ports.
l Stack card stacking and service port stacking (including ordinary cable stacking and dedicated stack
cable stacking) cannot be used together. If service port configurations are correct, service port
stacking is preferred over stack card stacking. If stack card stacking has been used to set up a stack,
to use service port stacking to set up the stack, you need to restart the stack to make service port
stacking takes effect after configuring service port stacking.
l 40GE ports on interface card cannot be used together with 40GE ports on the ES5D21VST000 stack
card to set up a stack.
l S5730SI series switches of all versions can set up stacks in service port stacking mode using
dedicated stack cables.
l The number of stacked switches is recommended to be 2 to 9.
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using
other cables may cause exceptions in the stack system, for example, frequent error-down events on
stack ports.
l Stack card stacking and service port stacking (including ordinary cable stacking and dedicated stack
cable stacking) cannot be used together. If service port configurations are correct, service port
stacking is preferred over stack card stacking. If stack card stacking has been used to set up a stack,
to use service port stacking to set up the stack, you need to restart the stack to make service port
stacking takes effect after configuring service port stacking.
l 40GE ports on the ES5D21VST000 stack card cannot be used together with 40GE ports on the
ES5D21Q04Q01 card to set up a stack.
l The number of stacked switches is recommended to be 2 to 9.
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using
other cables may cause exceptions in the stack system, for example, frequent error-down events on
stack ports.
l Combo ports cannot function as stack member ports.
l For stacking-supported service ports, some of them can be used as stack ports, whereas some can be
used as ordinary service ports.
l Stack card stacking and service port stacking (including ordinary cable stacking and dedicated stack
cable stacking) cannot be used together. If service port configurations are correct, service port
stacking is preferred over stack card stacking. If stack card stacking has been used to set up a stack,
to use service port stacking to set up the stack, you need to restart the stack to make service port
stacking takes effect after configuring service port stacking.
l 40GE ports on interface card cannot be used together with 40GE ports on the ES5D21VST000 stack
card to set up a stack.
l S5730S-EI series switches of all versions can set up stacks in service port stacking mode using
dedicated stack cables.
l The number of stacked switches is recommended to be 2 to 9.
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using
other cables may cause exceptions in the stack system, for example, frequent error-down events on
stack ports.
l Combo ports cannot function as stack member ports.
l The number of stacked switches is recommended to be 2 to 5.
l 10GE
SFP+
optical
module
and
optical
fiber
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using
other cables may cause exceptions in the stack system, for example, frequent error-down events on
stack ports.
l For stacking-supported service ports, some of them can be used as stack ports, whereas some can be
used as ordinary service ports.
l The first 12 10GE ports of the S6720-50L-HI-48S cannot be used as stack member ports.
l S6720HI series switches of all versions can set up stacks in service port stacking mode using
dedicated stack cables.
l The number of stacked switches is recommended to be 2 to 9.
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using
other cables may cause exceptions in the stack system, for example, frequent error-down events on
stack ports.
l Combo ports cannot function as stack member ports.
l Ports on the ES5D21X08S00 card of S6720EI series switches cannot function as stack ports.
l Since V200R011C10, S6720EI and S6720S-EI series switches can set up stacks in service port
stacking mode using dedicated stack cables.
l The number of stacked switches is recommended to be 2 to 9.
40GE ports l 1 m, 3 m, 40
on the front and 5 m Gbit/s
panel QSFP+
passive
high-
speed
copper
cables
l QSFP+
optical
module
(QSFP-40
G-SR-BD
not
supported
) and
optical
fiber
l 10 m
QSFP+
AOC
cable
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using
other cables may cause exceptions in the stack system, for example, frequent error-down events on
stack ports.
l Combo ports cannot function as stack member ports.
l For stacking-supported service ports, some of them can be used as stack ports, whereas some can be
used as ordinary service ports.
l Since V200R011C10, S6720LI and S6720S-LI series switches can set up stacks in service port
stacking mode using dedicated stack cables.
l The number of stacked switches is recommended to be 2 to 9.
10GE optical l 1 m, 3 m, 10
ports on the and 5 m Gbit/s
front panel SFP+
passive
high-
speed
copper
cables
l 10 m SFP
+ active
high-
speed
copper
cables
l 3 m and
10 m
AOC
cables
l 10GE
SFP+
optical
module
and
optical
fiber
l 0.5 m and
1.5 m SFP
+
dedicated
stack
cable
(supporte
d in
V200R01
1C10 and
later
versions)
l For the cables that can be used as stack cables, see "Cables" in the Hardware Description. Using
other cables may cause exceptions in the stack system, for example, frequent error-down events on
stack ports.
l Combo ports cannot function as stack member ports.
l For stacking-supported service ports, some of them can be used as stack ports, whereas some can be
used as ordinary service ports.
l Since V200R011C10, S6720SI and S6720S-SI series switches can set up stacks in service port
stacking mode using dedicated stack cables.
l The number of stacked switches is recommended to be 2 to 9.
Electrical Category 6A 10
ports on the or higher Gbit/s
front panel network
cables (If
Category 6
cables are
used, ensure
that the
cables meet
requirements
of TSB-155.)
2.2 SVF
2.2.1 Involved Network Elements
SVF networking involves the following components:
l Parent
l AS
l AP
2.2.4 Specifications
S9303 32 0 512
S9303E 32 0 512
S9306E, 64 0 2048
S9312E
S6720EI, 32 0 32
S6720S-EI
S6720SI, 32 0 32
S6720S-SI
NOTE
In an SVF system, ASs and APs share the CAPWAP link specifications. That is, the maximum number of
ASs and APs cannot exceed the maximum number of CAPWAP links. For example, when an S12710
functions as the parent in an SVF system and 256 ASs have connected to the SVF system, a maximum of
5888 (6144-256) APs can connect to the SVF system.
If DTLS encryption is configured for packets transmitted in a CAPWAP tunnel, recommendations on the
maximum number of ASs and APs supported on the parent are as follows:
l S12704, S12708, S12710, S12712: The maximum numbers of ASs and APs do not exceed 32 and 96
respectively.
l S9712, S9706, S7712, S7706, S7706 PoE, S9703, S7703, S7703 PoE, S6720HI, S5720HI, S5730HI:
The maximum numbers of ASs and APs do not exceed 16 and 48 respectively.
l S9303, S9306, S9310, S9312, S9303E, S9306E, S9312E, S9310X: The maximum numbers of ASs do
not exceed 16.
l S6720EI, S6720S-EI, S6720SI, S6720S-SI: The maximum numbers of ASs do not exceed 16.
l The preceding AS or AP specifications apply to scenarios where all ASs or APs go online. If both ASs
and APs go online, it is recommended that the value of AS*3+AP do not exceed the maximum number
of APs.
l When the number of ASs or APs exceeds the maximum value, a high CPU usage may occur, affecting
existing services.
AS administrator 16
profile
Network 16
enhanced profile
User access 16
profile
Network QoS 32
profile
Only
V200R013C00
and later versions
support create this
profile.
Configure the SVF An SVF system supports two forwarding modes: centralized
forwarding mode. forwarding and distributed forwarding.
l In centralized forwarding mode, traffic forwarded by the local
AS and forwarded between ASs is sent to the parent for
forwarding.
l In distributed forwarding mode, an AS directly forwards local
traffic and the parent forwards traffic between ASs.
NOTE
l 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.
l In centralized forwarding mode, after an AS goes offline, traffic of its
attached network cannot be forwarded by the parent and will be
interrupted.
l 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.
Configure the URL To improve web application security, data from untrustworthy
encoding function sources must be encoded before being sent to clients. URL
for an AS (This encoding is most commonly used in web applications. After URL
function is supported encoding is enabled for ASs, special characters in redirected URLs
in V200R009 and are converted to secure formats, preventing clients from mistaking
later versions). them for syntax signs or instructions and unexpectedly modifying
the original syntax. In this way, cross-site scripting attacks and
injection attacks are prevented. By default, URL encoding is
enabled in ASs. This function can be disabled using the portal url-
encode disable command.
Table 2-26 Commands not supported in the user view and diagnostic view of ASs
Command View
l Commands that are supported in other views are used for service diagnosis and fault
location. In V200R009 and earlier versions, the uni-mng diag-mode enable command
must be executed first to enable the diagnostic mode.
Function Command
Function Command
Pare l The parent can be a standalone device, a stack system, or a cluster switch
nt system (CSS).
l The S5730HI, S6720SI, S6720S-SI, S6720EI or S6720S-EI can function as the
parent or AS. By default, S5730HI works in parent mode, and other switches
work in AS mode. To change the switch working mode, run the as-mode
disable command. When the S5730HI work in AS mode, the WLAN function
becomes unavailable.
l ASs or APs connecting to an SVF system can be different models.
AP l If an AP has been connected to the parent before the SVF function is enabled,
the parent cannot collect topology information about the AP after the uni-
mnguni-mng command is used to enable the SVF function. You need to run the
commit { all | ap ap-id } command in the WLAN view to commit the AP
configuration. Subsequently, the parent can collect topology information about
the AP.
l From V200R011C10, WLAN configurations are automatically delivered,
without the need of running the commit all command.
l If APs need to connect to an SVF system with an S12700/S9700/S7700
functioning as the parent, X series cards must be installed on the parent to
manage APs.
Fabri l Service ports of fixed switches are classified into uplink and downlink service
c ports. For details about uplink and downlink service ports, see the "Naming
port Conventions" section in the Hardware Description - Chassis.
l 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.
l When an AS connects to APs, all member ports of the Eth-Trunk bound to the
fabric port that connects the parent to the AS must be ports on X series cards or
ports on non-X series cards. Otherwise, APs cannot go online.
l In V200R008 and earlier versions, an AS can only connect to the upstream
parent or AS using fixed uplink ports or ports on an extension card. Since
V200R009, downlink service ports of an AS can also be connected to the
upstream parent or AS after you configure them as member ports of an
upstream fabric port using the uni-mng up-direction fabric-port member
interface interface-type interface-number [ to interface-number ] command.
l A downlink service port of an AS cannot be configured as a member port of
upstream and downstream fabric ports simultaneously. If this configuration is
performed, the AS will be unable to go online after a reboot. If the reset slot
command is executed in the slot of the AS, the AS will reset repeatedly.
l Ports on an AS subcard and uplink service port on an AS can only be used as
member ports of a fabric port or as stack member ports and cannot be used as
service ports.
l From V200R009C00, AS uplink ports can be used to connect to the parent or
level-1 AS or set up a stack and be configured as downlink fabric ports to
connect to other ASs.
l On the S6720EI, S6720S-EI, S6720LI, S6720S-LI, S6720SI, and S6720S-SI,
40GE ports and 10GE ports split from 40GE ports cannot be configured as
downlink fabric ports.
CAP l Configured CAPWAP tunnel parameters apply to the SVF system. To ensure
WAP that the CAPWAP tunnel of the SVF system works normally, you are advised to
retain the default CAPWAP tunnel parameters. For details on how to configure
CAPWAP tunnel parameters, see Configuring CAPWAP Tunnel Parameters.
l In versions earlier than V200R011C10, Eth-Trunk can be manually created and deleted
on an AS in centralized mode. In V200R011C10 and later versions, Eth-Trunk cannot be
manually created and deleted on an AS in centralized mode and must be created and
deleted on the parent.
l In an SVF system, the maximum frame length allowed by interfaces cannot be
configured on an AS. Therefore, the maximum frame length is the default value 9216
(including the CRC field).
l After an AS goes online, a static ARP entry in which the IP address is the management
address of the parent is generated on the AS. Deleting the static ARP entry is not
allowed. Otherwise, the AS may be forcibly removed from the SVF system.
l Internal attacks in the management VLAN will cause an AS to go offline. You need to
identify the attack source and then shut down the attacked port or remove the port from
the management VLAN.
l After an AS goes offline, traffic on the network attached to the AS cannot be forwarded
in the following scenarios:
– The parent and AS run V200R012C00 or an earlier version. In versions earlier than
V200R012C00, after an AS goes offline, its downlink service ports will all be error
down.
– The SVF system works in centralized forwarding mode. In centralized forwarding
mode, after an AS goes offline, traffic on the network attached to the AS cannot be
forwarded through the parent.
– The level-1 AS service configuration mode is set to independent mode using the
port connect independent-as command or the level-2 AS service configuration
mode is set to independent mode using the down-direction fabric-port connect
independent-as command, and downlink service ports of the AS have
authentication configurations. After an AS goes offline, AS authentication fails, so
traffic on the network attached to the AS cannot be forwarded.
l When an AS goes offline and needs to go online again, and the AS configuration is
changed on the parent after the AS goes offline, the AS restarts and then goes online
again.
l After an AS is changed to the independent mode, it is recommended that you just add or
remove the fabric port of the AS to or from a VLAN. If you perform other configurations
on the fabric port, the AS may go offline. For details, see the description of the port
connect independent-as command.
When an AS connects to the parent across a Layer 2 network, pay attention to the
following points
l Automatic AS discovery is not supported, and fabric ports of the parent and AS need to
be manually configured.
l The indirectly-connected fabric port of the parent and configured uplink fabric port of
the AS do not support connection error check. The administrator needs to ensure the
connection correctness of the Eth-Trunk, and the AS can only connect to third-party
network devices through Eth-Trunks in manual load balancing mode.
l The administrator needs to ensure that the downlink fabric port of the parent and the
intermediate Layer 2 network are correctly configured, the SVF management VLAN and
service VLAN between the parent and AS are correctly connected, and the intermediate
network transparently transmits data traffic between the parent and AS. Therefore, the
intermediate network must be a pure Layer 2 network.
l The AS does not support the MAD function because this function requires that third-
party devices support the MAD relay function.
l In centralized forwarding mode, traffic from the network segment where the AS resides
may be forwarded by the intermediate network but not the parent.
l After the AS is configured to work in client mode, the AS can only be manually
configured to return to the standalone mode and must be restarted. If the AS is a stack,
new stack member devices will be automatically configured to work in client mode after
the AS is configured to work in client mode.
Licensing Requirements
Cloud-based management is a basic feature of a switch and is not under license control.
Version Requirements
NOTE
The version support described in this section indicates only the cloud-based management configurations
supported by switches. For the versions used in the Agile Controller-Campus and cloud management
solutions, see "Version Mapping and Restraints" in the Huawei Cloud Managed Solution.
S5720EI V200R013C00
S5730HI V200R013C00
S6720S-LI V200R013C00
Feature Limitations
l In V200R012C00SPC600, after an S5720LI stack or S5720SI stack has been set up, the
stack can register with the cloud management platform. In V200R013C00 and later
versions, after the switches that support cloud-based management establish a stack, the
stack can register with the cloud management platform.
l If an unconfigured switch runs in traditional management or cloud-based management
mode and cannot obtain the controller IP address, the switch periodically sends
registration packets to the registration center to obtain the controller IP address. You can
access the console port and run the display work-mode command to check the switch
operating mode:
– If the switch is working in traditional mode, no action is required because the input
on the console port stops the switch from sending registration packets to the
registration center.
– If the switch is working in cloud-based management mode, to prevent the switch
from sending registration packets to the registration center, configure Option 148 on
a DHCP server to enable the switch to obtain the controller IP address through the
DHCP server or configure the controller IP address on the switch using a command
or through the web system.
l In cloud-based management mode, the user name and password configured through the
web system or serial port are effective only before the switch registers with the cloud
management platform. After the switch registers, the cloud management platform will
deliver the user name and password to the switch, which will override the ones
configured in other ways. The user name and password delivered from the cloud
management platform are required for login to a cloud-managed switch as long as the
switch has registered with the cloud management platform.
l For the switch models (S5720LI, S5720S-LI, S5720I-6X-PWH-SI-AC, S5720I-10X-
PWH-SI-AC, S5720I-12X-SI-AC, and S5720I-12X-PWH-SI-DC) that do not support
real-time clock (RTC), whena traditional switch changes its management mode through
the registration center, ensure that the system time of the switch is within the validity
period of the PKI certificate. Otherwise, the switch cannot change its management mode.
l For the switch models (S5720LI, S5720S-LI, S5720I-6X-PWH-SI-AC, S5720I-10X-
PWH-SI-AC, S5720I-12X-SI-AC, and S5720I-12X-PWH-SI-DC) that do not support
RTC, if the device system time is not within the PKI certificate validity period after the
switch is changed to the cloud-based management mode, the system time is
automatically set to the start time of the PKI certificate validity period so that the switch
can register with the cloud management platform successfully. After the switch registers
with the cloud management platform successfully, the cloud management platform
changes the device system time to the correct time.
l In V200R010C00 and V200R011C00, a switch working in cloud-based management
mode does not have a configuration file. Service configurations delivered from the cloud
management platform are saved in a specific database of the platform. If a configuration
file is loaded to the switch through misoperations, for example, using the BootROM
menu, the switch will return to the traditional mode after a restart.
l In versions earlier than V200R011C10, it is not allowed to change a stacked switch to
the cloud-based management mode. In V200R011C10 and later versions, it is allowed to
change a stacked switch to the cloud-based management mode. Therefore, in versions
earlier than V200R011C10, if the current slot ID of a switch is not 0 or the current slot
ID is 0 but the slot ID for the next startup is not 0, it is not allowed to change the switch
to the cloud-based management mode.
l In V200R011C10 and later versions, a switch working in cloud-based management mode
has a configuration file. Service configurations delivered from the cloud management
platform are saved to the configuration file of the switch. To ensure that the
configurations recorded by the cloud management platform are consistent with those in
the configuration file of the switch, do not specify a configuration file for the switch
again, for example, using the BootROM menu to specify a new configuration file.
Otherwise, the configurations in the existing configuration file of the switch may be lost.
l After the switch is changed to the cloud-based management mode, a virtual management
interface Meth0/0/2 will be automatically generated for the cloud management platform
to locate faults on the switch. This interface has a fixed IP address configured. In
versions earlier than V200R011C10, this fixed IP address is 192.168.2.1/30. In
V200R011C10 and later versions, this fixed IP address is 169.254.2.1/30. After the
switch is upgraded to V200R011C10 or later, this fixed IP address becomes
169.254.2.1/30.
l After the switch is changed to the cloud-based management mode, in versions earlier
than V200R011C10, the management IP address of the switch can only be dynamically
allocated by the DHCP server. In V200R011C10 and later versions, this management IP
address can be dynamically allocated by the DHCP server or use the IP address
configured on a VLANIF interface used to communicate with the DHCP server.
l If the IP address dynamically assigned by the DHCP server to the switch is on the
network segment 192.168.1.0/24, the switch cannot register with the cloud management
platform for authentication.
l Since V200R012C00, the switch can auto-negotiate the PNP VLAN when working in
cloud-based management mode. In this way, the switch can be plug-and-play in the
cloud management solution.
l After the switch is changed to the cloud-based management mode, pay attention to the
following points:
– The trust dscp command configuration will be automatically generated on all
interfaces.
– If an error occurs in the cloud-based management process of the switch, detailed
error information of the process will be saved in the directory flash:/core_dump.
– The switch is disconnected from and then reconnected to the controller during patch
activation if the switch needs to have patches installed and the patch file contains
the cloud management-related process patch of the .bin type.
– In addition to the commands related to the cloud-based management configuration,
the switch supports only some commands used in traditional management mode for
fault location. Table 2-30 lists the commands supported in cloud-based
management mode.
All commands in the Commands starting with Setting the date and time,
user view the following keywords using command clock
in the user view are not datetime HH:MM:SS
supported: YYYY-MM-DD may
l configuration cause the switch unable
to register with the cloud
l clock daylight- management platform.
saving-time Therefore, confirm the
l clock timezone action before you use the
l format command.
l local-user
l lock
l startup saved-
configuration
l save (except save
logfile)
l reboot (except reboot
fast)
l schedule
l rollback
l reset saved-
configuration (not
supported in
V200R011C10 and
later versions)
2.4 PoE
Involved Network Elements
Powered devices (PDs)
Licensing Requirements
PoE is a basic feature of a switch and is not under license control.
Version Requirements
NOTE
Only switches with "PWR" or "PWH" in the device names are PoE switches. Whether switches support PoE
depends on the hardware. Non-PoE switches cannot be changed to PoE switches through software upgrades.
S2710SI V100R006(C03&C05)
S5710-C-LI V200R001C00
Several
NOTE
For details about software mappings, visit Hardware Query Tool and search for the desired product
model.
Feature Limitations
PoE Power Supplies Supported by the Switch
l In the versions earlier than V100R005, all PoE power supplies are 250 W non-constant
current power supplies. When two power supplies are used, they are used for power
redundancy, but do not offer power.
l In V100R005 and later versions, PoE power supplies include 250 W and 500 W constant
current power supplies. When two 250 W or 500 W constant current power supplies are
used, the power supplies can be used for power redundancy and offer power at the same
time.
l In V200R002 and later versions, PoE power supplies include 250 W, 500 W, 580 W, and
1150 W constant current power supplies. When two 580 W or 1150 W constant current
power supplies are used, the power supplies can be used for power redundancy and offer
power at the same time.
l In V200R007 and later versions, PoE power supplies include 250 W, 500 W, 580 W, 650
W, and 1150 W constant current power supplies. When two 580 W, 650 W, or 1150 W
constant current power supplies are used, the power supplies can be used for power
redundancy and offer power at the same time.
l In V200R013 and later versions, 1000 W constant current PoE power supplies are
available . These power supplies can be used in the same switch as 580 W and 1150 W
constant current power supplies. When two constant current power supplies are used,
these power supplies can be used for power redundancy and provide power at the same
time.
l Downlink electrical interfaces of PoE switches provide PoE power and each interface
supports a maximum of 200 m power supply distance. The PoE switch can transmit both
current and data on a pair of signal cables.
l For the available PoE power, maximum number of ports, and power module type
provided by different PoE switch models, see "Chassis" in the Hardware Description of
the specific switch model. PoE switches have "PWR" or "PWH" in the product names.
For details about PoE power supply configuration, see "Power Supply Configuration" of
the specific switch model.
PoE function
l The switch supports power supply capability negotiation using the Link Layer Discovery
Protocol (LLDP).
l The switch supports perpetual power supply and fast power-on.
l If a switch supports PoE, its PoE feature is not affected after it joins a stack.
l The switches can only be connected to APs of the specified models, including P7052DN/
AP7152DN, AP6052DN, AP8082DN/AP8182DN, AP7060DN, and AP7052DE.
l Supported PoE power supply standards include 60 w PoE++, 30 w PoE+, and 15.4 w
PoE. There is a 5 w power loss per 100 m.
l The maximum PoE power supply distance can reach 200 m only when the following
network cables are used.
Table 2-32 Ports and network cables required for providing the maximum PoE power
supply distance of 200 m
S5720I-SI can be connected to Huawei cameras over a long distance. When ports of these
switches work at the 100M rate, the maximum transmission distance can be 200 m. When
ports of these switches work at the 10M rate, the maximum transmission distance can be 250
m.
l The supported camera models include: M2220-I, M2221-FL, M2221-VL, M2260-I, and
M2220-I(8-32mm).
l When the transmission distance exceeds 100 m, cables of Cat5e or higher category must
be used.
2.5 Monitor
Involved Network Elements
Monitoring interfaces are used together with the NMS and monitored devices.
Licensing Requirements
Monitoring interface is a basic feature of a switch and is not under license control.
Version Requirements
Only the S5720I-SI series (except S5720I-6X-PWH-SI-AC and S5720I-10X-PWH-SI-AC)
switches support this feature.
The S3700HI and S5700HI also support monitoring interfaces, but the implementation is
different from that in the S5720I-SI. The monitoring interface function described in this
chapter applies only to the S5720I-SI series switches.
Feature Limitations
One S5720I-SI switch can monitor two peer devices.
2.6 OPS
Involved Network Elements
Other network elements are not required.
Licensing Requirements
OPS is a basic feature of a switch and is not under license control.
Version Requirements
S5710-X-LI V200R012C00
NOTE
For details about software mappings, visit Hardware Query Tool and search for the desired product
model.
Feature Limitations
OPS Specifications
the subscription event may not be matched because invisible characters cannot be
entered in the CLI.
l To prevent failures to copy or delete Python script files, ensure that the command lines
subscribed using ops.cli.subscribe are different from the names of Python script files.
When a timer event subscription API (ops.timer.cron, ops.timer.relative, ops.timer.absolute, or
ops.timer.countdown) is used and the timer is set improperly, for example, a short cycle is set
when the ops.timer.relative API is used to set the cyclic timer.
l If the action triggered by the timer is to restart the switch by running the reboot fast
command, the switch restarts repeatedly. In this case, you can press Ctrl+B to enter the
BootLoad menu when the switch is started and modify the configuration file to restore
the switch.
l If the action triggered by the timer is to restart the interface by running the restart
(interface view) command, or shut down or restart the interface repeatedly by running
the shutdown and undo shutdown commands, the interface cannot be used and the
CPU usage of the switch increases, affecting the switch performance.
l If the action triggered by the timer is to record logs, the logs of other service modules
will be deleted as the flash memory space becomes smaller, affecting fault analysis and
location.
In the Python script, if the CLI channel is opened using the ops.cli.open API, use the
ops.cli.close API to close the CLI channel after commands are executed.
In OPS API, the value of a character string cannot contain \0.
Other Restrictions
l OPS cannot be configured after the working mode of the switch is switched to the cloud-
based management mode.
l You can configure a Python script assistant only after the Python script is installed.
l You need to be familiar with the Python language and correctly write Python scripts.
l Switches running V200R012 support Python 2.7.3, and switches running V200R013
support Python 2.7.15. When editing a Python script, ensure that the used Python version
matches the switch software version.
Licensing Requirements
Energy-saving management is a basic feature of a switch and is not under license control.
Version Requirements
S2710SI V100R006(C03&C05)
S5710-C-LI V200R001C00
NOTE
For details about software mappings, visit Hardware Query Tool and search for the desired product
model.
Feature Limitations
l During device sleeping configuration, if you run the speed { 10 | 100 } command on any
awakening port to set the port rate to 10 or 100 Mbit/s or run the loopback internal
command on any awakening port to configure the loopback detection mode, the device
cannot enter the sleeping state. To enable the device to enter the sleeping state, you need
to configure the awakening port on which the speed { 10 | 100 } or loopback internal
command has been configured as a non-awakening port or delete the speed { 10 | 100 }
or loopback internal command configuration from the awakening port.
l When the interval between the sleeping start time and end time is less than 10 minutes,
the device will not enter the sleeping state.
l Run a command to view logs in the log buffer. Only the latest logs are saved in the log
buffer.
l Run a command to view logs in the storage device.
l Export logs to a log server and view logs on the server.
The first two methods do not require other network elements. To use the third method, you
need a server to save logs.
Licensing Requirements
Information center is a basic feature of a switch and is not under license control.
Version Requirements
S2710SI V100R006(C03&C05)
S5710-C-LI V200R001C00
NOTE
For details about software mappings, visit Hardware Query Tool and search for the desired product
model.
Feature Limitations
None
Licensing Requirements
Fault management is a basic feature of a switch and is not under license control.
Version Requirements
S3700HI V200R001C00
S5710-C-LI V200R001C00
NOTE
For details about software mappings, visit Hardware Query Tool and search for the desired product
model.
Feature Limitations
The following products and versions support configuration of the delayed alarm and event
reporting:
l S5730HI and S6720HI: All versions
l S5720EI, S5720HI, S6720EI, and S6720S-EI: V200R011C00 and later versions
2.10 NTP
Involved Network Elements
Other network elements are required to support NTP.
Licensing Requirements
NTP is a basic feature of a switch and is not under license control.
Version Requirements
S2710SI V100R006(C03&C05)
S5710-C-LI V200R001C00
NOTE
For details about software mappings, visit Hardware Query Tool and search for the desired product
model.
Feature Limitations
l The existing configuration will not be deleted when the NTP service is disabled.
l If the device does not support Real-Time Clock (RTC), it is recommended that you
configure NTP to ensure time accuracy in logs. The following models do not support
RTC:
– S2720EI
– S2750EI
– S5700-10P-LI-AC
– S5700-10P-PWR-LI-AC
– S5700-28P-LI-BAT
– S5700-28P-LI-24S-BAT
– S5720LI
– S5720S-LI
– S5720I-6X-PWH-SI-AC
– S5720I-10X-PWH-SI-AC
– S5720I-12X-SI-AC
– S5720I-12X-PWH-SI-DC
l If the switch does not support RTC, manually set the device time. If the switch is
powered off and restarts, the device time will become inaccurate. You need to manually
set the device time again.
2.11 PTP
Involved Network Elements
None
Licensing Requirements
PTP is a basic feature of a switch and is not under license control.
Version Requirements
Only the S6720HI series switches support PTP.
Feature Limitations
PTP Constraints
l All the intermediate devices on the PTP synchronization path must support PTP.
l Frequency signals are transmitted bidirectionally, and time signals are transmitted
unidirectionally. For frequency signals, a crossover cable is required; for time signals, a
straight-through cable is required.
l PTP Announce messages contain the clock attributes of the peer device to establish the
master-slave hierarchy of interfaces. Therefore, prohibit a PTP interface from receiving
Announce messages from different devices.
PTP Precautions
NOTE
Before configuring PTP for time synchronization, ensure frequency synchronization on the entire
network. To implement frequency synchronization, configure synchronous Ethernet. This chapter
describes only PTP time synchronization. For details about how to configure PTP for frequency
synchronization, see "Synchronous Ethernet Configuration" in Device Management.
l PTP messages are Layer 2 broadcast messages by default. If incorrect configuration is
performed, loops or broadcast storms occur and downstream devices are seriously
affected. To avoid broadcast storms or loops, configure VLAN or STP before enabling
PTP on an interface.
l By default, a device obtains frequency signals through synchronous Ethernet and obtains
time signals through PTP. When PTP is used for clock synchronization, you are advised
to configure the device to obtain frequency signals and time signals through PTP.
l The switch supports PTP only after its working mode has been set to enhanced mode
using the set service-mode command.
Licensing Requirements
Synchronous Ethernet is not under license control.
Version Requirements
Only the S6720HI series switches support synchronous Ethernet.
NOTE
For details about software mappings, visit Hardware Query Tool and search for the desired product
model.
Feature Limitations
l None