CE6860-SAN switch (48*25GE SFP28, 8*100GE QSFP28, without fan and power modules)
Condition: NOB
RMA Warranty
Description
Offering high-performance, high port density, and low latency, CloudEngine 6800 series switches enable enterprises and carriers alike to build cloud-oriented data center networks. The series features an advanced hardware design combined with either 10 GE, 25 GE, or 50 GE access ports, and 40 GE, 100 GE, or 200 GE uplink ports. Advanced data center features, high-performance stacking technologies, and flexible airflow capabilities complete the series. CloudEngine 6800 is well-suited to both the core and aggregation layers, and is fully compatible with CloudEngine 16800 and 12800 series switches, enabling enterprises to build scalable, simplified, open, and secure networks.
| Basic Information | |
| Description | CE6860-SAN switch (48*25GE SFP28, 8*100GE QSFP28, without fan and power modules) |
| Part Number | 02354FPM |
| Model | CE6860-SAN |
| First supported version | V300R020C10SPC200 |
| Other part numbers | 02354FPN (CE6860-SAN Switch (48*25GE SFP28, 8*100GE QSFP28, 2*AC power modules, 4*fan modules, port-side intake)) 02354FPP (CE6860-SAN Switch (48*25GE SFP28, 8*100GE QSFP28, 2*AC power modules, 4*fan modules, port-side exhaust)) |
| Short Name | CE6860-SAN |
| Technical Specifications | |
| Dimensions with packaging (H x W x D) [mm (in.)] | 225 mm x 860 mm x 650 mm (8.86 in. x 33.86 in. x 25.59 in.) |
| Dimensions without packaging (H x W x D) [mm (in.)] | – Basic dimensions (the depth excludes the parts protruding from the body): 43.6 mm x 442 mm x 420 mm (1.72 in. x 17.40 in. x 16.54 in.) – Maximum dimensions (the depth is the distance from ports on the front panel to the parts protruding from the rear panel): 43.6 mm x 442 mm x 445 mm (1.72 in. x 17.40 in. x 17.52 in.) |
| Weight without packaging [kg (lb)] | 6.7 kg (14.8 lb), excluding optical modules, power modules, and fan modules |
| Weight without packaging (full configuration) [kg (lb)] | 8.7 kg (19.2 lb) (including AC power modules and fan modules, excluding optical modules) |
| Weight with packaging [kg (lb)] | 11.9 kg (26.24 lb) |
| Weight with packaging (full configuration) [kg (lb)] | 13.9 kg (30.64 lb) |
| Chassis height [U] | 1 |
| Installation Type | Cabinet Installation |
| Switching capacity | To obtain data of this specification item, see the corresponding datasheet or contact the product sales personnel. |
| CPU | 4-core, 1.4 GHz |
| Memory | DRAM: 8 GB |
| NOR Flash | 64 MB |
| NAND Flash | 4 GB |
| USB | It can be used for log backup and USB-based deployment. This function is reserved. |
| Power supply mode | AC,DC,HVDC |
| Console port | RJ45 |
| Downlink Service interface | 48 x 25GE SFP28/48 x 50GE SFP56 1. 25GE ports can be used as 10GE ports. 50GE ports can be used as 25GE ports but not 10GE or GE ports. 2. When 25GE ports are upgraded to 50GE ports, eight ports form a group. Note: 1. Support for optical modules: (1) In the case of port-side air intake, downlink ports support 10G-AOC/SR/LR/ER/ZR and 25G-AOC/SR/LR. (2) In the case of port-side air exhaust, downlink ports support 10G-AOC/SR/LR and 25G-AOC/SR/LR. 2. Support for copper cables: When 50GE copper cables are used, contact Huawei engineers for interconnection verification. |
| Uplink Service interface | 8 x 100GE QSFP28/8 x 200GE QSFP56 1. Each 100GE port can be configured as a 40GE port, and each 200GE port can be configured as a 100GE/40GE port. 2. When 100GE ports are upgraded to 200GE, four such ports form a group. 3. 100GE ports are divided into groups 1 to 4 and 5 to 8. Four ports in each group are split together. Ports 2, 4, 6, and 8 can be split into four 25GE ports (whose speeds can be set to 10 Gbit/s). After the split, ports 1, 3, 5, and 7 cannot be used. A 100GE port cannot be split into 2 x 50GE (50GE: 2 x 25GE) ports. 4. 200GE ports cannot be split. Note: 1. Support for optical modules: (1) In the case of port-side air intake, 100GE/200GE ports support 100G-AOC/SR4/CWDM4/LR4/4WDM. (2) In the case of port-side air exhaust, 100GE/200GE ports support 100G-AOC/SR4/CWDM4/LR4 optical modules, but do not support 50GE and 200GE optical modules. 2. Support for copper cables: When 200GE copper cables are used, contact Huawei engineers for interconnection verification. |
| Service port supporting the stack function | Reserved function. This function is not enabled. |
| RTC | Supported |
| Typical power consumption [W] | – 48 x 50G + 8 x 200G: 374 W (50% throughput, copper cables on all ports, normal temperature, dual power modules) – 48 x 25G + 8 x 100G: 360 W (50% throughput, copper cables on all ports, normal temperature, dual power modules), 407 W (50% throughput, short-distance optical modules on all ports, normal temperature, dual power modules) |
| Typical heat dissipation [BTU/hour] | – 48 x 50G + 8 x 200G: 1277 BTU/hour (50% throughput, copper cables on all ports, normal temperature, dual power modules) – 48 x 25G + 8 x 100G: 1229 BTU/hour (50% throughput, copper cables on all ports, normal temperature, dual power modules), 1389 BTU/hour (50% throughput, short-distance optical modules on all ports, normal temperature, dual power modules) |
| Static power consumption [W] | 322 W |
| Static heat dissipation [BTU/hour] | 1100 BTU/hour |
| Maximum power consumption [W] | – 48 x 50G + 8 x 200G: 619 W (100% throughput, downlink 2 W 50G optical modules, uplink 6.5 W 200G optical modules, 40°C, dual power modules) – 48 x 25G + 8 x 100G: 544 W (100% throughput, downlink 1.5 W 25G optical modules, uplink 5 W 100G optical modules, 40°C, dual power modules) |
| Maximum heat dissipation [BTU/hour] | – 48 x 50G + 8 x 200G: 2110 BTU/hour (100% throughput, downlink 2 W 50G optical modules, uplink 6.5 W 200G optical modules, 40°C, dual power modules) – 48 x 25G + 8 x 100G: 1858 BTU/hour (100% throughput, downlink 1.5 W 25G optical modules, uplink 5 W 100G optical modules, 40°C, dual power modules) |
| Number of power modules | 2 |
| Redundant power supply | 1+1 backup |
| Rated input voltage [V] | – 600 W AC&240 V DC power module: 100 V AC to 240 V AC, 50/60 Hz; 240 V DC – 1000 W DC power module: –48 V DC to –60 V DC – 1200 W high-voltage DC power module: 240 V DC to 380 V DC |
| Input voltage range [V] | – 600 W AC&240 V DC power module: 90 V AC to 290 V AC, 45 Hz to 65 Hz; 190 V DC to 290 V DC – 1000 W DC power module: –38.4 V DC to –72 V DC – 1200 W high-voltage DC power module: 190 V DC to 400 V DC |
| Maximum input current [A] | – 600 W AC&240 V DC power module: 8 A (100 V AC to 240 V AC); 4 A (240 V DC) – 1000 W DC power module: 30 A (–48 V DC to –60 V DC) – 1200 W high-voltage DC power module: 8 A |
| Rated output power [W] | – 600 W AC&240 V DC power module: 600 W – 1000 W DC power module: 1000 W – 1200 W high-voltage DC power module: 1200 W |
| Certification | – Complies with safety standards. – Complies with EMC standards. – Complies with environmental protection standards. |
| Power supply surge protection [kV] | – AC power supply protection: 6 kV in common mode and 6 kV in differential mode – 240 V HVDC power supply protection: 4 kV in common mode and 2 kV in differential mode – –48 V DC power supply protection: 4 kV in common mode and 2 kV in differential mode – 380 V HVDC power supply protection: 4 kV in common mode and 2 kV in differential mode |
| Types of fans | Pluggable |
| Number of fans | 4 |
| Redundant fans | The device supports 3+1 backup of fan modules that work in hot standby mode. The system can operate properly for a short period of time after a single fan module fails. You are advised to replace the faulty fan module immediately. |
| Heat dissipation mode | Air cooling |
| Airflow direction | Port-side air intake or port-side air exhaust, depending on the fan modules and power modules that are used. The fan modules and power modules must have the same airflow direction. |
| Availability | 0.9999943515 |
| MTBF [year] | 30.32 years |
| MTTR [hour] | 1.5 hours |
| Noise at normal temperature (27°C, sound pressure) [dB(A)] | – Front-to-back airflow: 49.8 dB(A) on average (maximum: 53.6 dB(A)) – Back-to-front airflow: 47.8 dB(A) on average (maximum: 51.2 dB(A)) |
| Noise at high temperature (40°C, sound pressure) [dB(A)] | – Front-to-back airflow: 67.6 dB(A) on average (maximum: 73.4 dB(A)) – Back-to-front airflow: 68 dB(A) on average (maximum: 75.4 dB(A)) |
| Long-term operating altitude [m (ft.)] | ≤ 5000 m (16404 ft.) |
| Long-term operating relative humidity [RH] | 5% RH to 95% RH, noncondensing |
| Long-term operating temperature [°C (°F)] | 0°C to 40°C (32°F to 104°F) at an altitude of 0–1800 m (0–5906 ft.) Note: When the altitude is 1800–5000 m (5096–16404 ft.), the highest operating temperature reduces by 1°C (1.8°F) every time the altitude increases by 220 m (722 ft.). |
| Storage altitude [m (ft.)] | ≤ 5000 m (16404 ft.) |
| Storage relative humidity [RH] | 5% to 95% RH, non-condensing |
| Storage temperature [°C (°F)] | -40ºC to +70ºC (-40°F to +158°F) |
| RTU License Supported | Yes. By default, only 24 of the 48 x 25GE ports are enabled and can work only at 25 Gbit/s, and the eight 100GE ports can work only at 100 Gbit/s. The following RTU licenses can be used: 88036XTL: 24 x 25GE ports are added. 88036YCK: The speed of 24 x 25GE ports is upgraded to 50 Gbit/s. 88036YCL: The speed of eight 100GE ports is upgraded to 200 Gbit/s. |
| Ethernet Switching>Eth-Trunk | |
| IEEE 802.3ad | Y |
| Ethernet Switching>STP/RSTP/MSTP | |
| Loop prevention | Y |
| IEEE 802.1w(RSTP) | Y |
| IEEE 802.1s(MSTP) | Y |
| Root protection | Y |
| BPDU protection | Y |
| IEEE 802.1d (STP) | Y |
| Ethernet Switching>VBST>VBST function | |
| VBST | Y |
| Ethernet Switching>VLAN>VLAN Basics>Port Link Type | |
| access | Y |
| hybrid | Y |
| trunk | Y |
| IP address and service>ARP Security | |
| Interface-based ARP packet suppression | Y |
| QoS>Congestion Management>Congestion Management>Scheduling management | |
| Queue scheduling algorithm | Y |
| QoS>MQC>Re-marking | |
| Re-marking DSCP values of packets | Y |
| Re-marking outer 802.1p priorities of packets | Y |
| QoS>Re-marking | |
| Re-marking DSCP values of packets | Y |
| Re-marking outer 802.1p priorities of packets | Y |
| QoS>Traffic Policing, Traffic Shaping, and Interface-based Rate Limiting>Traffic Shaping>Interface-based Rate Limiting | |
| Configuring outbound interface-based rate limiting on an interface | Y |
| QoS>Traffic Policing, Traffic Shaping, and Interface-based Rate Limiting>Traffic Shaping>Queue shaping | |
| Configuring queue shaping on an interface | Y |
| Reliability>BFD>BFD Service Scenario>BFD for M-LAG | |
| BFDv6 for M-LAG | Y |
| BFD for M-LAG | Y |
| Reliability>BFD>BFD Service Scenario>BFD session | |
| BFD session performance of a board (when the minimum detection period is configured) | 128 (3 ms x 3) |
| Number of BFD sessions in the system | 1024 |
| Default interval at which BFD packets are sent and received | 1000 ms |
| Reliability>M-LAG>Common mechanism | |
| Maintenance mode | Y |
| M-LAG function | Y |
| Reliability>VRRP | |
| VRRP group | 1024 |
| Security>Local Attack Defense>ARPSec>ARP packet rate limiting | |
| Interface-based ARP packet suppression | Y |
| Security>Local Attack Defense>ICMP Security | |
| ICMP Security-Abnormal Packet Detection | Y |
| Security>MACsec | |
| Enabling MACsec on an Interface | Y |
| Configuring Encryption Algorithms on the MACsec Data Plane | Y |
| Security>Port Security | |
| Port security | Y |
| Security>Storm Suppression>Storm Control | |
| Storm control for unknown multicast packets on an interface | Y |
| Storm control for unknown unicast packets on an interface | Y |
| Storm control for broadcast packets on an interface | Y |
| Security>Storm Suppression>Traffic Suppression | |
| Broadcast storm suppression in a BD | Y |
| Broadcast traffic suppression in a VLAN | Y |
| Multicast traffic suppression in a VLAN | Y |
| System Management>Hardware management>Device Management>Board management>Device restart | |
| Device restart | Y |
| System Monitoring>AnyFlow | |
| Configuring AnyFlow for RoCEv2 packets so that the device can create flow entries for RoCEv2 packets and send the flow entries to the analyzer | Y |
| Creating flow entries for IPv4/IPv6 TCP, UDP, and VXLAN packets | Y |
| Flow entry aggregation | Y |
| License information | Y |
| System Monitoring>IOAM | |
| Collecting queue length information | Y |
| License control items | Y |
| Configuring a VXLAN gateway node (used for communication between two VXLAN tunnels) as an IOAM egress node | Y |
| Configuring the traffic policy for copying and sending IOAM-encapsulated packets to the CPU | Y |
| Performing IOAM decapsulation and encapsulation in sequence for the same flow on the same device | Y |
| Adding IOAM information to specified IPv4, IPv6, TCP, and VXLAN flows | Y |
| System Monitoring>Mirroring | |
| N:1 mirroring | Y |
| 1:N mirroring | Y |
| Inbound port mirroring | Y |
| Flow mirroring | Y |
| Outbound port mirroring | Y |
| System Monitoring>NetStream>NetStream>Flexible flow | |
| Creating IPv4 flexible flows | Y |
| Creating IPv6 flexible flows | Y |
| Creating IPv4 over IPv4 VXLAN flexible flows | Y |
| System Monitoring>NetStream>NetStream>Original flow | |
| Creating IPv4 original flows | Y |
| Creating IPv6 original flows | Y |
| System Monitoring>NetStream>NetStream>Statistics export | |
| Exporting packets carrying IPv4 flexible flow statistics | Y |
| Exporting packets carrying IPv4 original flow statistics in V5 format | Y |
| Exporting packets carrying IPv4 original flow statistics in V9 format | Y |
| Exporting packets carrying IPv6 original flow statistics in V9 format | Y |
| Exporting packets carrying IPv6 flexible flow statistics | Y |
| System Monitoring>NetStream>NetStream>Traffic sampling | |
| Sampling on Eth-Trunk interfaces | Y |
| Data flows can be sampled based on inbound and outbound interfaces. | Y |
| Sampling on Layer 2 sub-interfaces | Y |
| Sampling on Layer 3 sub-interfaces | Y |
| Sampling on physical interfaces | Y |
| System Monitoring>Packet Event>Packet loss visualization | |
| Visualization of statistics about packets discarded due to forwarding exceptions | Y |
| Configuring packet loss visualization for RoCEv2 packets so that the device can create flow entries for RoCEv2 packets and send the flow entries to the analyzer | Y |
| License control items | Y |
| Visualization of statistics about packets that are discarded normally | Y |
| System Monitoring>Service Telemetry | |
| Service metric measurement for I/O quality visualization | Y |
| Configuring the number of polling ports for I/O quality visualization | Y |
| Configuring ACL rules for I/O quality visualization | Y |
| Enabling I/O quality visualization globally | Y |
| Querying the ACL delivery status for I/O quality visualization | Y |
| Enabling I/O quality visualization on a port | Y |
| Querying the delivery status of interfaces for I/O quality visualization | Y |
| Configuring the polling interval for I/O quality visualization | Y |
| License-controlled service telemetry | Y |
| System Monitoring>Telemetry>Telemetry Service>Static Telemetry Configuration | |
| Combination and sending of sampled data in subscription | 1. By default, the sampled data of different sampling paths is sent to the collector separately. The packet combination function combines the sampled data together and sends it to the collector. In this way, the distributed data sending mode is changed to the centralized data sending mode. 2. Packet combination is to combine the sampled data in a sampling period and send the data together. Therefore, packet combination period is the same as the sampling period. If a subscription has multiple sampling periods, the maximum sampling period is configured as the packet combination period. If all sampling periods are 0, the packet combination period is 1s. 3. If the accumulated data reaches 80 KB in the packet combination period, the data is sent immediately. 4. The variable frequency sampling period of telemetry does not affect the packet combination period. 5. The packet combination function and the UDP protocol are mutually exclusive. |
| User Access and Authentication>AAA>Authentication Management>Authentication Management | |
| RADIUS authentication method | Y |
| HWTACACS authentication method | Y |
| User Access and Authentication>AAA>Domain management>Domain management | |
| Domain management | Y |
| User Access and Authentication>AAA>Local user management>Administrator User Management | |
| Configuring local account attributes | Y |
| User Access and Authentication>AAA>RADIUS management>RADIUS authentication | |
| Configuring a primary authentication server | Y |
| VXLAN>VXLAN>Configuring ARP and VXLAN together>BUM flooding | |
| ARP broadcast-to-unicast conversion | Y |
| VXLAN>VXLAN>Configuring IPv6 and VXLAN together>Layer 3 gateway | |
| IPv6 over VXLANv6 Layer 3 gateway | Y |
| VXLAN>VXLAN>Segment VXLAN>DCI | |
| Segment VXLAN implementing Layer 3 communication | Y |
| Segment VXLAN implements Layer 2 communication. | Y |
| Segment VXLANv6 implementing Layer 2 communication | Y |
| Segment VXLANv6 implementing Layer 3 communication | Y |
| VXLAN>VXLAN>VXLAN Service>BUM flooding | |
| ARP broadcast-to-unicast conversion | Y |
| VXLAN>VXLAN>VXLAN tunnel>BGP EVPN | |
| IBGP EVPN and EBGP EVPN on the VXLAN control plane | Y |
