Configuration Guide Specifications and Limitations

Specifications and Limitations

This section lists the specifications and limitations of features supported on S8600E series products.

Feature Description
DCB 1. S8600E-ED/DB products support 8 CNPV.
2. S8600E-ED/DB products do not support the congestion-notification cnm-data-len command, so the
0-byte initial data is carried in the CNM.
3. For S8600E-ED/DB products, PFC and ETS can be enabled on interfaces independently.
4. S8600E-ED/DB products support three traffic classes.
5. S8600E-EB products do not support DCB.
VM Support 1. S8600E-EB products do not support VM Support.
FCoE 1. S8600E-EB products do not support FCoE.
TRILL 1. S8600E-EB products do not support TRILL.
L2GRE 1. S8600E-EB products do not support L2GRE.
2. For S8600E series products, TTL is configured in the global configuration mode instead of in the
L2GRE instance.
IP Multicasting 1. For S8600E series products, the default CPP value of PIM packets is 1000pps and that of IGMP packets
is 1000pps. Packets whose CPP value exceeds this value are discarded. If over 1000 multicast
forwarding entries are to be created through the PIM protocol, it is recommended to set the CPP value of
PIM packets to be equal to the entry number. If over 1000 multicast forwarding entries are to be created
through the IGMP protocol, it is recommended to set the CPP value of IGMP packets to be equal to the
entry number.
IPv6 1. For S8600E series products, the default CPP value of PIMv6 packets is 1000pps and that of MLD
Multicasting packets is 1000pps. Packets whose CPP value exceeds this value are discarded. If over 1000 multicast
forwarding entries are to be built through the PIMv6 protocol, it is recommended to set the CPP value of
PIMv6 packets to be equal to the entry number. If over 1000 multicast forwarding entries are to be built
through the MLD protocol, it is recommended to set the CPP value of IGMP packets to be equal to the
entry number.
ISIS 1. S8600E series products are enabled with CPU protection by default. There is a default limit to the
number of packets corresponding to each destination group address of IS-IS (AllISSystems,
AllL1ISSystems, AllL2ISSystems) that are sent to CPU. If there are many adjacencies or if Hello
packets are sent at short intervals, the IS-IS packet number received by the switch may exceed the
default limit, causing constant oscillation of adjacency. In this case, it is recommended to increase the
limit to the IS-IS packet number by configuring CPU protection commands in the global configuration
mode.
PBR For S8600E series products:

1. If the policy-based routing (PBR) is configured with a null ACL, all packets are matched; if the
policy-based routing is configured with an ACL without any ACE, the system matches the packets with
Configuration Guide Specifications and Limitations

the ACL of the next policy, and all packets are matched and are forwarded with common routing.

2. PBR is applied to only the packets sent to the local switch. If you do not want to apply PBR to a specific
incoming IPv4/IPv6 packet, add the ACE “deny the switch IPv4/v6 address” in the ACL manually.
Network 1. S8600E series products support 64 equivalent paths, and each path contains up to 32 equivalent
Service routes. The equivalent path is a collection of routes with the same prefix that share the same next hop.
Module
MAC Address 1. For S8600E-ED products, a filtering MAC address occupies space twice as large as a common MAC
address does. For example, though the size of a global filtering MAC address is 10KB, the filtering MAC
address takes up 20KB available space.
2. S8600E-ED/DB/EB products neither learn nor forward the packet with both the source MAC address
and the destination MAC address consisting of 0 only.
Global IP-MAC 1. For S8600E series products, if global IP+MAC binding and port security/802.1X are both applied, all
Binding secure users can communicate with each other no matter whether the security channel is enabled or
not.
2. For S8600E series products, if IPv6 compatible mode and port security/802.1X authentication are both
applied, all IPv6 packets bound with the MAC address are allowed to go through the interface.
Port Security 1. For S8600E series products, if the security port is configured with IP+MAC binding and IPv6 compatible
mode, the IPv6 packets consistent with the secure address but not with IP+MAC binding are allowed to
go through the interface. The control plane traffic is not allowed to go through.
QinQ 1. S8600E-ED/DB/EB products support 4 TPIDs in the global configuration mode, namely, 0x8100 and 3
any values.
Aggregated 1. For S8600E-ED/DB products, each aggregate port supports up to 8 member ports, and the device
Port supports up to 256 aggregate ports by default.

2. For S8600E-EB products, each aggregate port supports up to 8 member ports, and the device supports
up to 128 aggregate ports by default.

3. For S8600E-ED/DB products, the supported aggregate port capacity mode includes 256*8, 128*16,
64*32, and 32*64. The maximum number of the member ports of an aggregate port is 8. 16, 32, 64
corresponding to each capacity mode, and the maximum number of aggregate ports is 256, 128, 64
and 32 respectively.
4. For S8600E-ED/DB/EB products, if you perform load balancing based on the source MAC address, the
destination MAC address, or the combination of the source MAC address and the destination MAC
address, the device takes fields of Ethernet type and VLAN as equivalence factors by default.

5. For S8600E-ED/DB/EB products, in the non-enhanced mode, load balancing of IGMP Snooping and
multicast packets is based on t src-ip, dst-ip or src-ip+dst-ip; traffic balancing of unknown unicast
packets, multicast packets and broadcast packets is based on src-mac, dst-mac or src-mac+dst-mac.
But a L3 packet (unknown unicast packets, unknown multicast packets and unknown broadcast
packets) cannot achieve load balancing based on src-ip or dst-ip on a L2 port. However, the enhanced
mode can address this problem with load balancing based on the packet type.

6. In the src-dst-ip-l4port mode, modification to the L4port affects the traffic balancing of unicast packets
Configuration Guide Specifications and Limitations

on S8600E-ED/DB/EB products.

7. S8600E-ED/DB products support aggregate-port-based load balancing. The aggregate-port-based load

balancing configuration supports SMAC, DMAC, SMAC+DMAC, SIP, DIP or SIP+DIP.

8. S8600E-ED/DB products support configuration of the following enhanced traffic balancing templates:

L2 template: src-mac dst-mac vlan l2-protocol src-port

IPv4 template: src-ip dst-ip protocol vlan l4-src-port l4-dst-port src-port

IPv6 template: src-ip dst-ip protocol vlan l4-src-port l4-dst-port src-port

MPLS template: top-label 2nd-label vlan src-ip dst-ip src-port

9. S8600E-EB products support configuration of the following enhanced traffic balancing templates:

L2 template: src-mac dst-mac vlan l2-protocol src-port

IPV4 template: src-ip dst-ip protocol vlan l4-src-port l4-dst-port src-port

IPV6 template: src-ip dst-ip protocol vlan l4-src-port l4-dst-port src-port

MPLS template: top-label 2nd-label vlan src-ip dst-ip src-port

10. The default configuration of the enhanced traffic balancing templates of S8600E-EB products are listed
below:

IPv4 template: src-ip dst-ip

IPv6 template: src-ip dst-ip

L2 template: src-mac dst-mac vlan

MPLS template: top-label 2nd-label

11. For S8600E-ED/DB/EB products, if the enhanced MPLS template contains the VLAN field, the
balancing algorithm takes effect only when the ingress packet is a tagged MPLS packet and the action
is popping the tag.

12. S8600E-EB products do support FCoE/TRILL enhanced template.

SPAN-RSPAN 1. For S8600E-ED/DB/EB products, when traffic mirroring is applied in the output direction, if the mirrored
packets are multicast routing packets, the packets that come out of the destination traffic mirroring port
are the multicast packets before being routed.
2. For S8600E series products, the switching function should be forcedly enabled before configuring the
destination traffic monitoring port.
3. For S8600E-ED/DB products, when traffic mirroring function is applied in the output direction on the
TRILL encapsulation port, if the mirrored packets are non-unicast TRILL packets, the packets that come
out of the destination traffic mirroring port are the TRILL packets before being encapsulated.
4. For S8600E-ED/DB/EB products when traffic mirroring is applied in the output direction on the tunnel
source port, if the mirrored packets are multicast tunnel packets, the packets that come out of the
destination traffic mirroring port are the packets before being tunnel-encapsulated.
5. For S8600E-ED/DB products, when traffic mirroring is applied in the output direction on the MPLS port,
Configuration Guide Specifications and Limitations

the packets that come out of the destination traffic mirroring port are the packets before being revised.
6. For S8600E-ED/DB products, if you want to mirror the TRILL packets, the destination traffic mirroring
port should be TRILL P2P port or routing port.
7. S8600E-ED/DB/EB products only mirror forwarded packets on the port.
8. S8600E-ED/DB/EB products do not support VLAN-based tx mirroring.
Interface 1. For S8600E series products, the inbound ports only support the speed auto and speed 10G
configuration.

2. For the 10 Gigabit fiber port, the auto-negotiation function is disabled forever, that is, the status of
auto-negotiation is OFF forever.

3. When you insert the optical transceiver into the 40 Gigabit fiber port, the auto-negotiation is disabled;
when the copper cable is inserted, the auto-negotiation is enabled.

4. For S8600E series products, the MTU configuration applies on both the ingress ports and egress ports.

5. For all S8600E series products, the actual MTU value is 26 bytes greater than the configured value
(including 14-byte preamble, 4-byte FCS and 2-byte Tag).
6. Only M8600E-12QXS-DB/M8600E-24XS4QXS-DB products support the 40G port to be divided as
4x10G ports.
Storm Control 1. For S8600E series products, the storm control function is disabled and the default value of storm control
is one percent of the port bandwidth.

2. For S8600E series products, if a port is configured with multicast/broadcast/non-unicast storm control
based on PPS, it cannot be configured with unicast storm control based on the bandwidth
percentage/Kbps setting; if a port is configured with multicast/broadcast/non-unicast storm control
based on the bandwidth percentage/Kbps setting, it cannot be configured with unicast storm control
based on PPS.

3. For S8600E series products, the multicast storm control function is disabled by default and the default
value of storm control is one percent of the port bandwidth.

4. For S8600E series products, if a port is configured with unicast/broadcast storm control based on PPS,
it cannot be configured with multicast storm control based on the bandwidth percentage/Kbps setting; if
a port is configured with unicast/broadcast storm control based on the bandwidth percentage/Kbps
setting, it cannot be configured with multicast storm control based on PPS.

5. For S8600E series products, the broadcast storm control function is disabled by default and the default
value of storm control is one percent of the port bandwidth.

6. For S8600E series products, if a port is configured with unicast/multicast storm control based on PPS, it
cannot be configured with broadcast storm control based on the bandwidth percentage/Kbps setting; if
a port is configured with unicast/multicast storm control based on the bandwidth percentage/Kbps
setting, it cannot be configured with broadcast storm control based on PPS.

ACL 1. For S8600E series products, the ACL applied in the input direction does not support the neq matching
of TCP and UDP packets on L4 ports while the ACL applied in the output direction supports only the eq
Configuration Guide Specifications and Limitations

matching of TCP and UDP packets on L4 ports.

2. For the S8600E series products, IPv6 ACL supports the following match fields:

protocol, sip, l4_src, dip, l4_dst, dip, dscp, flow_label.

An IPv6 ACL supports either one of the following match fields:

protocol, sip, l4_src, l4_dst, dscp, flow_label, range

protocol, dip, l4_src, l4_dst, dscp, flow_label, range

An ACL cannot match all the above areas. Besides, the IPv6 ACL does not support the fragment
matching.

The IPv6 ACL applied in the output direction does not support flow label.

When sip and dip fields are matches with the only first 64 bits (the mask length is less or equal to 64),
the above five IPv6 match files are supported.
3. For S8600E series products, the ACL applied to SVI also applies to intra-VLAN bridge forwarding
messages and inter-VLAN routing messages, causing communication failure within the VLAN.
4. S8600E series products cannot identify the fragment flag field in IPv6 packets. Therefore, the fragment
flag is omitted if an IPv6 ACL contains the fragment flag. That is, such an ACL is processed in the same
way as an ACL without a fragment flag, and all packets including the initial fragment packet and
non-initial packets are to be matched.
5. For S8600E series products, the switchover of the fragment match modes is supported only in an IP
extended ACL and expert extended ACL.
6. For S8600E series products, ACL 80 only support the following fields: the source MAC address, the
destination MAC address, VID, ETYPE, IP Protocol Number, IPv4 source IP address, IPv4 destination
IP address, Destination Port Number, Source Port Number, ICMP Type and ICMP Code.
7. For S8600E series products, enabling ACL counters requires more hardware entries. In an extreme
case, this will reduce by half the number of ACEs that can be configured on a device.
NTP 1. Ruijie devices support up to 1024 authentication keys and each server is allowed to configure only one
authentication key for security communication.
QoS 1. The QoS trust mode cannot be configured on the SVI port.
2. For S8600E series products, all member ports of a logical interface should be on the same line card.

3. The member ports of the logical interface must be physical ports or aggregate ports.
4. The DENY action in the ACL matched in a CLASS MAP does not take effect.
5. S8600E series products do not support vid modification.
6. When this command is configured on the egress port, S8600E series products support DSCP
modification for the packets whose traffic exceeds the bandwidth, but the CoS value does not change;
when this command is configured on the ingress port, the CoS value changes with DSCP.

7. S8600E series products support CoS modification for the packets whose traffic exceeds the bandwidth.
When you modify the CoS value, the corresponding DSCP value is modified as well. By configuring the
none-tos option, the DSCP value does not changed with CoS. QoS matching DSCP does not apply to
MPLS packets.
Configuration Guide Specifications and Limitations

8. S8600E series products do not support the non-tos option when the set cos command is configured.

9. For S8600E series products, the rate is limited by the real bandwidth, including the load taken by the
preamble and IFG. (The preamble and IFG occupies 20 bytes,)

10. S8600E series products support the minimum rate-limiting granularity of 8Kbps. The granularity varies
with the rate-limiting configuration. The following table describes the relationship between rate-limiting
range and granularity.

Rate-limiting 64Kbps-2Gbps 2Gbps-4Gbps 4Gbps-8Gbps

Range
Granularity 8Kbps 16Kbps 32Kbps
Rate-limiting 8Gbps-16Gbps 16Gbps-32Gbps 32Gbps-40Gbps
Range
Granularity 64Kbps 128Kbps 256Kbps
In case of traffic bursts, if the burst-size parameter is too small, the actual rate may be too small; if the
burst-size parameter is too great, the actual rate may be too great. The following configuration is
recommended:

1) If the rate-limiting value is smaller than 1024Kbps, it is recommended to set burst-size to1024 KByte.

2) If the rate-limiting value is smaller than 10240Kbps, it is recommended to set burst-size equivalent to the
rate-limiting value or adopt the maximum burst-size configuration supported by the device (The
maximum burst-size is smaller than10240KByte).

3) If the rate-limiting value is greater than 10240Kbps, it is recommended to adopt the maximum burst-size
configuration supported by the device.

11. If the rate is too great, the burst-size parameter should be modified accordingly. Otherwise, the rate
limiting might be inaccurate. The following configuration is recommended:

1) For the 10 Gigabit port or 40 Gigabit port, it is recommended to set the burst-size to 32 or above.
12. You can attach a policy map to the output direction on S8600E series products.

13. For S8600E series products, when the police command is configured on an Aggregate Port (AP), the
rate-limiting configuration can be shared by all AP member ports if the all member ports meet the
following requirements: all AP member ports must be on this line card.

14. For S8600E series products, the CLASS MAP is associated with the ACL. Therefore, QoS configuration
shares the same restriction with ACL configuration. For details, see the ACL Configuration Guide. Policy
maps cannot be configured on the SVI port.

15. You can configure a policy map and attach it to the output direction. The policy map is not supported on
the Aggregate Port.

16. The policy maps attached to the output direction do not support CoS remarking. When the DSCP value
of the packets is remarked, the CoS value is not remarked.

17. The map policy attached to the output direction is not supported on the logical interface. The CLASS
Configuration Guide Specifications and Limitations

MAP is associated with the ACL. Therefore, QoS configuration shares the same restriction with ACL
configuration. For details, see the ACL Configuration Guide.
18. S8600E series products do not support WFQ and SP+WFQ scheduling,

19. S8600E series products adopt SP+DRR balancing algorithm on the VSL port by default. The queue 7
adopts the SP scheduling, and the priority of the other queues is 1. This scheduling configuration
cannot be modified.

20. For S8600E series products, the rate is limited by the real bandwidth, including the load taken by the
preamble and IFG. (The preamble and IFG occupies 20 bytes,)

21. S8600E series products support the minimum rate-limiting granularity of 8Kbps. The granularity varies
with the rate-limiting configuration. The following table describes the relationship between rate-limiting

range and granularity.

Rate-limiting Range 64Kbps-2Gbps 2Gbps-4Gbps 4Gbps-8Gbps

Granularity 8Kbps 16Kbps 32Kbps
Rate-limiting Range 8Gbps-16Gbps 16Gbps-32Gbps 32Gbps-40Gbps
Granularity 64Kbps 128Kbps 256Kbps

22. If the rate is too great, the burst-size parameter should be modified accordingly. Otherwise, the rate
limiting might be inaccurate. The following configuration is recommended:

1) For the 10 Gigabit port or 40 Gigabit port, it is recommended to set the burst-size to 32 or above.

23. You can only use the show run command to verify whether the WRED function is enabled in the global
configuration mode,

24. The lower threshold and the maximum loss rate are called a set of WRED configuration.
S8600E-ED/DB products support 120 sets of WRED configuration.

25. When the lower limit is 100%, the WRED is disabled.

26. S8600E series products support the mapping configuration on the physical port.

27. The administrator can configure the DSCP-threshold mapping by mapping DSCP-CoS to
CoS-Threshold.

28. The administrator can configure the Queue-threshold mapping by mapping CoS-Threshold to
CoS-Queue.

29. In VSU mode, the management packets go to the queue 8 with default priority 7. It is recommended not
to modify this mapping.

sFlow 1. S8600E-ED/DB products support the sFlow statistics function.

2. S8600E-EB products do not support the sFlow statistics function.

3. S8600E-ED/DB products adopt the same sFlow sampling rate range from 4096 to 65535.

4. S8600E-ED/EF products do not support sFlow sampling of cross linecard. That is, if the packets are
Configuration Guide Specifications and Limitations

forwarded to the ED/EF line card from the other line card, the sFlow sampling function on the ED/EF
line card does not take effect.

UFT 1. S8600E-ED/DB/EF products support the UFT mode.

2. For S8600E-ED/EF products, when the UFT mode is set to gateway-ndmax, the available space for
the static MAC address and the filtering address is 1KB.
CPP 1. The default CPU Protection value of S8600E series products:

Packet Type Bandwidth (pps) Packet Priority

bpdu 128 6
arp 10000 1
tpp 128 6
dot1x 1500 2
gvrp 128 5
rldp 128 5
lacp 256 5
rerp 128 5
reup 128 5
lldp 768 5
cdp 768 5
dhcps 1500 2
dhcps6 1500 2
dhcp6-client 1500 2
dhcp6-server 1500 2
dhcp-relay-c 1500 2
dhcp-relay-s 1500 2
option82 1500 2
tunnel-bpdu 128 2
tunnel-gvrp 128 2
unknown-v6mc 128 1
xgv6-ipmc 128 1
stargv6-ipmc 128 1
unknown-v4mc 128 1
xgv-ipmc 128 2
stargv-ipmc 128 2
udp-helper 128 1
dvmrp 128 4
igmp 1000 2
icmp 4500 3
ospf 2000 4
Configuration Guide Specifications and Limitations

ospf3 2000 4
pim 1000 4
pimv6 1000 4
rip 128 4
ripng 128 4
vrrp 256 6
vrrp6 256 6
ttl0 128 0
ttl1 2000 0
hop_limit 800 0
local-ipv4 4000 3
local-ipv6 4000 3
v4uc-route 800 1
v6uc-route 800 1
rt-host 4096 4
mld 1000 2
nd-snp-ns-na 10000 1
nd-snp-rs 1500 1
nd-snp-ra-redirect 1500 1
erps 128 5
mpls-ttl0 128 4
mpls-ttl1 128 4
mpls-ctrl 128 4
isis 2000 4
bgp 128 4
cfm 512 5
web-auth 2000 2
fcoe-fip 1000 4
fcoe-local 1000 4
bfd 5120 6
dldp 3200 6
other 20000 0
trill 1000 4
efm 1000 5
ipv6-all 2000 0
ip-option 800 0
mgmt 25000 -
Dns 200 2
Sdn 20000 0
Configuration Guide Specifications and Limitations

The default bandwidth of every priority’s queue:

Default
Queue
Bandwidth
0 20000
1 20000
2 20000
3 20000
4 20000
5 20000
6 20000
7 20000

The default bandwidth of the CPU port is 100000.

NFPP 1. The NFPP function supports up to 100000 users.
The default NFPP settings of S8600E series products:
Function Sub-option Rate Limit Attach Threshold
per-src-ip 30 3000
per-src-mac 30 3000
arp-guard per-port 5000 8000
scan-per-mac 100 NA
scan-per-ip-mac 100 NA
per-src-ip 2000 2500
icmp-guard
per-port 4000 4500
per-src-ip 20 200
ip-guard per-port 100 400
scan-per-ip 100 NA
per-src-mac 5 10
dhcp-guard
per-port 1200 1500
per-mac 5 10
dhcpv6-guard
per-port 1200 1500
ns-na-guard per-port 2000 5000
rs-guard per-port 500 1000
ra-redirect-guard per-port 500 1000
DoS 1. For S8600E-ED/DB/EF/EB products have the following restriction:
There are four types of invalid TCP packets as follows:

1) TCP packets with both SYN bit and FIN bit.

2) TCP packets without any flag.
3) TCP packets with FIN flag but without ACK flag.
4) TCP packets with SYN flag and source port number ranging from 0 to 1023.
Configuration Guide Specifications and Limitations

2. When protection against invalid TCP packet attack is enabled, BCM series products can filter invalid
TCP packets of the first and fourth types. For the second type of invalid TCP packets, BCM series
products can only filter TCP packets configured without any flag and the sequence number 0. For the
third type of invalid TCP packets, BCM series products can only filter TCP packets configured with the
FIN flag, URG flag and PSH flag and the sequence number 0.
MTU 1. Please note the reasonability of MTU configuration. The IP/IPv6 MTU must be less than the interface
MTU. The Layer interface includes the routed port, Layer AP port and SVI.
PoE 1. Only the M18000-48GT-P-ED/M8600E-48GT-ED/M7800E-48GT-P-ED products support PoE.

RMON 1. Ruijie Networks products support only the Ethernet port statistics.
2. Ruijie Networks products support only the Ethernet port recording.
Syslog
1. For the chassis device working in VSU mode with the log redirection enabled, the log information on the
backup supervisor module is redirected to the master supervisor module for display. When it is
displayed, a corresponding role mark string ( "device number/supervisor module name” ) is added to
the very front of the log content to identify the log information as the redirected log information. In the
VSU environment, if four supervisor modules exist at the same time, there can be four role mark strings,
i.e. ( *1/M1 ),( *1/M2 ),( *2/M1 ),( *2/M2 ).

2. The buffer-size parameter of the logging buffered command ranges from 4KB to 10MB, and the
default value is 1MB.

MPLS-BASE 1. For S8600E series products, the MPLS MTU configured on an interface cannot exceed the size of
packets transmitted on the interface. For the switches adopting ASIC forwarding, this configuration is
invalid. The switches forward packets based on the MTU configured on actual interfaces and directly
discard the packet whose size exceeds the MTU. To modify the MTU of an interface, you can use the
mtu command in the interface configuration mode. Fragmentation is supported by only process
forwarding and router forwarding. You should adjust the MTU value according to the actual application
to avoid performance degradation due to fragmentation.
2. For S8600E series products, TTL in the inner header is copied after TTL replication is enabled, whether
it is smaller than the TTL in the outer header.
3. For S8600E series products, the mpls ip command (global configuration mode) is not used to control
the chip forwarding but to control the software forwarding.
MPLS-L2VPN
1. After enabling the port protection mode on the member ports of the AC in L2VPN, the port protection
mode does not take effect for the non-Trunk member ports.

2. The DHCP packets cannot be transmitted transparently after the ip dhcp snooping command is
enabled.

3. The QoS policy for the DSCP matching does not take effect for the MPLS packets.
4. For switches, the VLAN bound with VPWS has only one member port, which cannot be changed. After
the VLAN member port is changed, the VLAN should be bound with VPWS again.
5. It is recommended to set PW as the ethernetvlan mode if VPLS service is provided on switches
Configuration Guide Specifications and Limitations

through Trunk access or on routers through sub-interface access.

6. For S8600E series products, DHCP packets cannot be transmitted transparently after the ip dhcp
snooping command is enabled.
7. For S8600E series products, VPLS can be bound to only one port.
8. For S8600E series products, VPLS instances are only supported by SVI interfaces and a VPLS
instance can be bound to only one SVI interface.
9. For S8600E series products, one VPLS instance can be configured with mixed access modes. For
example, PEs in one VPLS instance are configured with both Access and Trunk access modes. In such
case, it is recommended to set the VPLS PW encapsulation mode on the PEs to the ethernetvlan
mode.
10. For S8600E series products enabled with VPLS forwarding, the aging time of MAC addresses is
configured by executing the mac-address-table aging-time command in global configuration. It cannot
be configured separately for each VPLS instance.
11. Switches do not support the mac-limit command.
12. Switches do not support the forwarding statistics function.
13. It is not allowed to bind VPLS and VPWS with the default VLAN (VLAN1) when switches adopt L2 VPN
service through Trunk ports.

14. The SVI member ports of VPLS and VPWS bound with switches are Trunk ports or Hybrid ports. The
member ports belong to all SVIs and cannot be enabled with IPv4/IPv6 multicast routing, IGMP
Snooping or MLD Snooping.
15. For switches, the VLAN port bound with the VPLS service cannot be configured with Subvlan, flexible
QinQ, mac-vlan, private-vlan and supper-vlan.

16. For switches, the Kompella VPLS can be bound to only one port.
MPLS-L3VPN 1. By default, tag assignment is performed based on each VRF, The PE removes the tag from the tagged
packets and then forwards it based on the IP routing table.
Intelligent 1. The default priority of the line card is specified as follows:
Monitoring
1) The priority of the VSL line card is higher than that of other line cards.

2) The smaller the slot number is, the higher priority the line card enjoys.
2. The default priority of the line card power supply is specified as follows:
The management board enjoys the highest priority,
The priority of S8600E-FE products is higher than that of the other line cards (including S8600E-VSL
products).
The priority of S8600E-VSL products is higher than that of the other line cards.
The smaller the line card slot number or the FE slot number is, the higher priority the slot enjoys.

When a non-smart line card is inserted in a slot, the slot is automatically powered on and the priority
configuration does not take effect.
3. Information displayed by executing the show power command varies with various products.
For S8600E series product, the following information is displayed: power supply redundancy mode, the
power module of each slot and its status, rated power, output power, output voltage, input/output
voltage, fail/alarm status; the total power, assigned power, and remaining power of the system, the
Configuration Guide Specifications and Limitations

name, required power, assigned power and power supply status of each slot.
4. For S8600E series products, the temperature is measured at the following places: the air intake vent on
the board, the air exhaust vent on the board, the hottest position on the board (two for each board),
CPU (two for multi-service card), MAC(if the engine does not have any MAC chip, “N/A” will be
displayed; if the board has multiple MAC chips, each MAC chip is displayed with one temperature)
The show temperature command is used to display the alarm temperature.\
Hot Swapping 1. S8610E products support multiple switch fabric modules. The switch fabric module is used to forward
data among line cards, The device without switch fabric module is not functional. When all the switch
fabric modules are removed, the device will be automatically reset to switch the traffic on the network to
the backup line.
VSU 1. At least one 10 Gigabit port or one 40 Gigabit port should be specified as the VSL member port. The 10
Gigabit port and the 40 Gigabit port can be the VSL member ports at the same time.
The connection modes between VSL member ports of two chassis:
Connect 10 Gigabit ports through the XFP (or SFP+ ) module with the optical fiber cable.
Connect 40 Gigabit ports through the QXFP module with the optical fiber cable or copper cable.
A 10 Gigabit port cannot be connected to a 40 Gigabit port.
2. S8600E series products support up to 32 VSL member ports.
There is no need to configure VSL AP when configuring the VSL port. The VSL AP performs
auto-negotiation.
The VSL heartbeat detection cannot be configured.
The four separated 10 Gigabit ports broken out from the 40 Gigabit port cannot be configured to the
VSL port.
3. For S8600E series products, any 10 Gigabit port can be configured as the VSL port.

Product Stack Module Common Port Linear Topology Ring Maximum Member
Topology Device Number
S8600E Unsupported Supported Supported Unsupporte 2
series d
products

4. For S8600E series products, any 10 Gigabit port can be configured as the VSL port.
5. In the above topology, the upstream devices must be Ruijie Networks products which support MAD
packet forwarding. S8600E series products support this function.