Example for Configuring Egress Devices on Small- and Medium-Sized Campus or Branch Networks

Huawei Campus Switch includes S1700, S2300, S2700, S3300, S3700, S5300, S5700, S600-E, S6300, S6700, S7700, S7900, S9300, S9300X, S9700, S12700 Series. In this article, HongTelecom will introduce the Example for Configuring Egress Devices on Small- and Medium-Sized Campus or Branch Networks for Huawei S7700/S9700 Switch.

Example for Configuring Egress Devices on Small- and Medium-Sized Campus or Branch Networks

Overview

A campus network egress is often located between an enterprise’s internal network and external network to provide the only ingress and egress for data traffic between the internal and external networks. Small- and medium-scale enterprises want to deploy multiple types of services on the same device to reduce initial investment on enterprise network construction and long-term O&M cost. Enterprise network users require access to the Internet and virtual private networks (VPNs). To reduce network construction and maintenance costs, small- and medium-scale enterprises often lease the Internet links of carriers to build VPNs. Some campus networks requiring high reliability often deploy two egress routers to implement device-level reliability and use reliability techniques such as link aggregation, Virtual Router Redundancy Protocol (VRRP), and active and standby routes to ensure campus network egress reliability. Huawei AR series routers can be used as egress devices and work with Huawei S series switches to provide a cost-effective network solution for small- and medium-scale campus networks. Campus network egress devices must provide the following functions:

  • Provide the network address translation (NAT) outbound and NAT server functions to translate between private and public network addresses, so that internal users can access the Internet and Internet users can access internal servers.
  • Support the construction of VPNs through the Internet so that branches of the enterprise can communicate over VPNs.
  • Encrypt data to protect data integrity and confidentiality, ensuring service transmission security.
  • Egress devices of small- and medium-scale campus networks must be reliable, secure, low-cost, and easy to maintain.

Configuration Notes

This configuration example:

  • Applies to small- and medium-sized enterprise campus/branch egress solutions.
  • Provides only the enterprise network egress configuration. For the internal network configuration, see “Small- and Mid-Sized Campus Networks” in the HUAWEI S Series Campus Switches Quick Configuration.
  • Uses S series switches running V200R008 and AR series routers running V200R003.

Networking Requirements

The headquarters and branch of an enterprise are located in different cities and far from each other. The headquarters has two departments (A and B), and the branch has only one department. A cross-regional enterprise campus network needs to be constructed to meet the following requirements:

  • Both users in the headquarters and branch have access to the Internet. In the headquarters, users in Department A can access the Internet, but users in Department B are not allowed to access the Internet. In the branch, all users can access the Internet.
  • The headquarters has a web server to provide WWW service so that external users can access the internal server.
  • The headquarters and branch need to communicate through VPNs over the Internet and communication contents must be protected.
  • The headquarters’ campus network egress requires link-level reliability and device-level reliability.
  • The branch does not need high reliability.

A comprehensive configuration solution, as shown in Figure 1, is provided to meet the preceding requirements. The solution adopts a multi-layer, modular, redundant, and secure design and applies to small- and medium-scale enterprise or branch campus networks.

Solution Overview

  • Deploy Huawei S2700&S3700 switches (ACC1, ACC2, and SwitchA) at the access layer, deploy Huawei S5700 switches (CORE) at the core layer, and deploy Huawei AR3200 routers (RouterA, RouterB, and RouterC) at the campus network egress.
  • In the headquarters, use redundancy between two AR egress routers (RouterA and RouterB) to ensure device-level reliability. In the branch, deploy one AR router as the egress router.
  • In the headquarters, set up a stack (CORE) between two S5700 core switches to ensure device-level reliability.
  • In the headquarters, deploy Eth-Trunks between access switches, the CORE, and egress routers to ensure link-level reliability.
  • In the headquarters, assign a VLAN to each department and transmit services between departments at Layer 3 through VLANIF interfaces of the CORE.
  • Use the CORE of the headquarters as the gateway for users and servers, and deploy a DHCP server to assign IP addresses to users.
  • Deploy the gateway for branch users on the egress router.
  • Deploy VRRP between the two egress routers of the headquarters to ensure reliability.
  • Construct an Internet Protocol Security (IPSec) VPN between the headquarters and branch over the Internet to enable communication while ensuring data transmission security.
  • Deploy Open Shortest Path First (OSPF) between the two egress routers and CORE of the headquarters to advertise user routes for future capacity expansion and maintenance.

Configuration Roadmap

The configuration roadmap is as follows:

  1. Deploy the headquarters and branch campus networks.In the headquarters, deploy a stack and link aggregation, configure VLANs and IP addresses for interfaces, and deploy a DHCP server to allow users in the headquarters campus network to communicate. Users within a department communicate at Layer 2 through access switches, and users in different departments communicate at Layer 3 through the VLANIF interfaces of the CORE.

    In the branch, configure VLANs and IP addresses for interfaces on access switches and egress routers, and deploy a DHCP server to allow users in the branch campus network to communicate.

  2. Deploy VRRP.To ensure reliability between the CORE and two egress routers of the headquarters, deploy VRRP between the two egress routers so that VRRP heartbeat packets are exchanged through the CORE. Configure RouterA as the master device and RouterB as the backup device.

    To prevent service interruption in the case of an uplink failure on RouterA, associate the VRRP status with the uplink interface of RouterA. The association ensures a fast VRRP switchover when the uplink fails.

  3. Deploy routes.To steer uplink traffic of devices, configure a default route with the VRRP virtual address as the next hop on the CORE of the headquarters, and configure a default route on each egress router of the headquarters and branch, with the next hop pointing to the IP address of the connected carrier network device (public network gateway address).

    To steer the return traffic of two egress routers of the headquarters, configure OSPF between the two egress routers and CORE, and advertise all user network segments on the CORE into OSPF and then to the two egress routers.

    On RouterD, to steer traffic generated by access to the web server from external networks, configure two static routes of which the destination address is the public network address of the web server and next-hop addresses are uplink interface addresses of the two egress routers. To ensure simultaneous route switchover and VRRP switchover, set the route with next hop pointing to RouterA as the preferred one. When this route fails, the route with next hop pointing to RouterB takes effect.

  4. Configure NAT outbound.To enable internal users to access the Internet, configure NAT on the uplink interfaces of the two egress routers for translation between private network addresses and public network addresses. Use an ACL to permit the source IP address of packets from Department A so that users in Department A can access the Internet while users in Department B cannot.
  5. Configure a NAT server.To enable external users to access the internal web server, configure a NAT server on the uplink interfaces of the two egress routers to translate between the public and private network addresses of the server.
  6. Deploy IPSec VPN.To enable users in the headquarters and branch to communicate through a VPN, configure IPSec VPN between the egress routers of the headquarters and branch for secure communication.
 NOTE:

For the enterprise internal network configuration, see “Small- and Mid-Sized Campus Networks” in the HUAWEI S Series Campus Switches Quick Configuration.

Data Plan

Table 1, Table 2, and Table 3 provide the data plan.

Table 1 Data plan for link aggregation of interfaces
DEVICE LAG INTERFACE PHYSICAL INTERFACE
RouterA Eth-Trunk1 GE2/0/0GE2/0/1
RouterB Eth-Trunk1 GE2/0/0GE2/0/1
CORE Eth-Trunk1 GE0/0/1GE1/0/1
Eth-Trunk2 GE0/0/2GE1/0/2
Eth-Trunk3 GE0/0/3GE1/0/3
Eth-Trunk4 GE0/0/4GE1/0/4
ACC1 Eth-Trunk1 GE0/0/1GE0/0/2
ACC2 Eth-Trunk1 GE0/0/1GE0/0/2
 NOTE:

All Eth-Trunk interfaces work in Link Aggregation Control Protocol (LACP) mode.

Table 2 VLAN plan
DEVICE DATA REMARKS
RouterA Eth-Trunk1.100: Configure a dot1q termination sub-interface to terminate packets of VLAN 100. Connects to the CORE of the headquarters.
RouterB Eth-Trunk1.100: Configure a dot1q termination sub-interface to terminate packets of VLAN 100. Connects to the CORE of the headquarters.
CORE Eth-Trunk1: a trunk interface that transparently transmits packets of VLAN 10. Connects to department A of the headquarters.
Eth-Trunk2: a trunk interface that transparently transmits packets of VLAN 20. Connects to department B of the headquarters.
GE0/0/5: an access interface with VLAN 30 as the default VLAN. Connects to the web server of the headquarters.
Eth-Trunk3: a trunk interface that transparently transmits packets of VLAN 100. Connects to RouterA of the headquarters.
Eth-Trunk4: a trunk interface that transparently transmits packets of VLAN 100. Connects to RouterB of the headquarters.
ACC1 Eth-Trunk1: a trunk interface that transparently transmits packets of VLAN 10. Connects to the CORE of the headquarters.
Ethernet0/0/2: an access interface with VLAN 10 as the default VLAN. Connects to PC1 in department A.
ACC2 Eth-Trunk1: a trunk interface that transparently transmits packets of VLAN 20. Connects to the CORE of the headquarters.
Ethernet0/0/2: an access interface with VLAN 20 as the default VLAN. Connects to PC3 in department B.
RouterC GE2/0/0.200: Configure a dot1q termination sub-interface to terminate packets of VLAN 200. Connects to SwitchA (access switch) of the branch.
SwitchA GE0/0/1: a trunk interface that transparently transmits packets of VLAN 200. Connects to RouterC (egress router) of the branch.
Ethernet0/0/2: an access interface with VLAN 200 as the default VLAN. Connects to PC5 in the branch.

Table 3 IP address plan
DEVICE DATA REMARKS
RouterA GE1/0/0: 202.10.1.2/24Eth-Trunk1.100: 10.10.100.2/24 GE1/0/0 connects to the carrier network.Eth-Trunk1.100 connects to the CORE of the headquarters.
RouterB GE1/0/0: 202.10.2.2/24Eth-Trunk1.100: 10.10.100.3/24
CORE VLANIF 10: 10.10.10.1/24VLANIF 20: 10.10.20.1/24

VLANIF 30: 10.10.30.1/24

VLANIF 100: 10.10.100.4/24

VLANIF 10 functions as the user gateway of department A.VLANIF 20 functions as the user gateway of department B.

VLANIF 30 functions as the gateway of the web server.

VLANIF 100 connects to egress routers.

Web server IP address: 10.10.30.2/24Default gateway: 10.10.30.1 Public network IP address translated by the NAT server: 202.10.100.3
PC1 IP address: 10.10.10.2/24Default gateway: 10.10.10.1 IP address 10.10.10.2/24 is allocated to the PC through DHCP in this example.
PC3 IP address: 10.10.20.2/24Default gateway: 10.10.20.1 IP address 10.10.20.2/24 is allocated to the PC through DHCP in this example.
RouterD InterfaceB: interface number GigabitEthernet1/0/0 and IP address 202.10.1.1/24InterfaceC: interface number GigabitEthernet2/0/0 and IP address 202.10.2.1/24 RouterD is a carrier network device. The interface number used here is an example. When configuring a device, use the actual interface number.
RouterE InterfaceA: interface number GigabitEthernet1/0/0 and IP address 203.10.1.1/24 RouterE is a carrier network device. The interface number used here is an example. When configuring a device, use the actual interface number.
RouterC GE1/0/0: 203.10.1.2/24GE2/0/0.200: 10.10.200.1/24
PC5 IP address: 10.10.200.2/24Default gateway: 10.10.200.1 IP address 10.10.200.2/24 is allocated to the PC through DHCP in this example.

 

About Us

As a world leading Huawei networking products supplier, Hong Telecom Equipment Service LTD(HongTelecom) keeps regular stock of Huawei router and switch and all cards at very good price, also HongTelecom ship to worldwide with very fast delivery.

For related articles, visit the HongTelecom Blog and HongTelecom WordPress.
For real pictures of related product, visit the HongTelecom Gallery.
To buy related product, visit the HongTelecom Online Shop.

何诗名片

MQC for Huawei S7700/S9700 Switch

Huawei Campus Switch includes S1700, S2300, S2700, S3300, S3700, S5300, S5700, S600-E, S6300, S6700, S7700, S7900, S9300, S9300X, S9700, S12700 Series. In this article, HongTelecom will introduce the MQC for Huawei S7700/S9700 Switch.

MQC

Involved Network Elements

Other network elements are not required.

Licensing Requirements

MQC is a basic feature of the switch and is not under license control.

Version Requirements

Table 1 describes the products and versions supporting MQC.

Table 1 Products and versions supporting MQC
PRODUCT PRODUCT MODEL SOFTWARE VERSION
S7700 S7703, S7706, and S7712 V100R003C01, V100R006C00, V200R001(C00&C01), V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00
S9700 S9703, S9706, and S9712 V200R001(C00&C01), V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007(C00&C10), V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00
 NOTE:

For details about software mappings, visit Hardware Query Tool and search for the desired product model.

Feature Limitations

  • Table 2 describes the specifications of MQC.

    Table 2 Specifications of MQC
    ITEM SPECIFICATION
    Maximum number of traffic classifiers
    • Versions earlier than V100R006: 255
    • V100R006 to V200R002: 256
    • V200R003 and later versions: 512
    Maximum number of if-match rules in a traffic classifier 2048
    Maximum number of traffic behaviors 256
    Maximum number of traffic policies 256
    Maximum number of traffic classifiers bound to a traffic policy 256
  • Applying a traffic policy consumes ACL resources. If ACL resources are insufficient, the traffic policy will fail to be applied. Assume that an if-match rule in a traffic policy occupies one ACL. When the traffic policy is applied to M interfaces, M ACLs are occupied. When the traffic policy is applied to L VLANs on a switch with N LPUs, L*N ACLs are occupied. When the traffic policy is applied to the system on a switch with N LPUs, N ACLs are occupied. Table 3 describes the ACL resource usage of if-match rules.

    Table 3 ACLs occupied by traffic classification rules
    TRAFFIC CLASSIFICATION RULE ACL RESOURCE USAGE
    if-match vlan-id start-vlan-id [ to end-vlan-id ] [ cvlan-id cvlan-id ]if-match cvlan-id start-vlan-id [ to end-vlan-id ] [ vlan-id vlan-id ] Rules are delivered according to the VLAN ID range and multiple ACLs are occupied. You can run the display acl division start-id to end-id command to check how ACL resources are used in a specified VLAN range.
    if-match acl { acl-number | acl-name }if-match ipv6 acl { acl-number | acl-name } Uplink: When the range resources are exhausted, rules containing range port-start port-end are delivered and multiple ACLs are occupied. Each rule containing tcp-flag established occupies two ACLs. (The ACL resource usage on X series cards is similar to that in the downlink direction.)Downlink: Rules containing range port-start port-end are delivered according to the port number range, and multiple ACLs are occupied. In other situations, one rule occupies one ACL. You can run the display acl division start-id to end-id command to check how ACL resources are used in a specified port number range.
    Other if-match rules Each rule occupies one ACL.
  • A traffic policy can be applied to the system, a VLAN, an SSID profile, or an interface. When a traffic policy needs to be applied in multiple views, apply the traffic policy in the interface view/SSID profile view, VLAN view, and system view in sequence. If the switch supports the SSID profile view and different interface views, apply the traffic policy in the VLANIF interface view, WLAN-ESS interface view/SSID profile view, sub-interface view of physical interfaces/Eth-Trunk sub-interface view, and physical interface view/Eth-Trunk interface view/port group view in sequence.
  • When packets match multiple traffic policies, the following rules apply:
    • If traffic classification rules in the traffic policies are of the same type, only one traffic policy takes effect. The precedence of the traffic policies depends on the objects to which they are applied: interface/SSID profile > VLAN > system. That is, the traffic policy applied to an interface has the highest priority, whereas the traffic policy applied to the system has the lowest priority. If the traffic policies are applied to an SSID profile and different interfaces, the precedence of the traffic policies is as follows: VLANIF interface > WLAN-ESS interface/SSID profile > sub-interface of physical interface/Eth-Trunk sub-interface > physical interface/Eth-Trunk interface/port group. When different traffic policies are applied in the same view, the precedence of the policies depends on the configuration sequence.
    • For the X series cards: If traffic classification rules in the traffic policies are of different types, only one traffic policy takes effect. The precedence of the traffic policies depends on the objects to which they are applied: interface > VLAN > system. That is, the traffic policy applied to an interface has the highest priority, whereas the traffic policy applied to the system has the lowest priority. If traffic policies are applied to the same object, the traffic policy that contains the traffic classifier with the highest priority takes effect.
    • For other cards except the X series cards: If traffic classification rules in the traffic policies are of different types and the actions do not conflict, all the traffic policies take effect. If actions conflict, the precedence of the traffic policies depends on the precedence of rules in the policies: Layer 2 rule + Layer 3 rule > advanced ACL6 rule > basic ACL6 rule > Layer 3 rule > Layer 2 rule > user-defined ACL rule.

    You are advised to configure traffic policies in descending order of priority; otherwise, traffic policies may not take effect immediately. For details about traffic classification rules, see “Overview of MQC”.

  • If an MQC-based traffic policy and an ACL-based simplified traffic policy matching the same ACL are applied to the same object, the ACL-based simplified traffic policy takes effect.
  • If the ACL rule matches the VPN instance name of packets, the ACL-based traffic policy fails to be delivered.
  • If a traffic policy fails to be applied due to insufficient ACL resources on the switch, you are advised to delete the configuration of the traffic policy. Otherwise, if the configuration is saved and the switch is restarted, configuration of other services that run properly will fail to be restored.
  • If the traffic policy that you want to delete has been applied to the system, an interface, or a VLAN, run the undo traffic-policy command to unbind the traffic policy. Then run the undo traffic policy command in the system view to delete the traffic policy. The traffic policy that is not applied can be deleted directly.
  • On switches in a version earlier than V200R009C00, a traffic policy cannot be applied to a VLANIF interface.

About Us

As a world leading Huawei networking products supplier, Hong Telecom Equipment Service LTD(HongTelecom) keeps regular stock of Huawei router and switch and all cards at very good price, also HongTelecom ship to worldwide with very fast delivery.

For related articles, visit the HongTelecom Blog and HongTelecom WordPress.
For real pictures of related product, visit the HongTelecom Gallery.
To buy related product, visit the HongTelecom Online Shop.

何诗名片

Static VXLAN deployment for Huawei S7700/S9700 Switch

Huawei Campus Switch includes S1700, S2300, S2700, S3300, S3700, S5300, S5700, S600-E, S6300, S6700, S7700, S7900, S9300, S9300X, S9700, S12700 Series. In this article, HongTelecom will introduce the Static VXLAN deployment for Huawei S7700/S9700 Switch.

VXLAN

Involved Network Elements

Other network elements are not required.

Licensing Requirements

Static VXLAN deployment is a basic feature of a switch and is not under license control. The distributed VXLAN gateway and BGP EVPN functions are enhanced VXLAN functions under license control. To use an enhanced VXLAN function, apply for and purchase the required license from the device dealer.

The BGP EVPN-control license does not control route exchanges between devices. However, it regulates the status of the VXLAN tunnel established using BGP EVPN. If the license is not loaded or is invalid, no VXLAN tunnel can be established using BGP EVPN.

For details about how to apply for a license, see Applying for Licenses in the S7700 and S9700 Series Switches License Usage Guide.

Version Requirements

Table 1 Products and versions supporting VXLAN
SERIES PRODUCT MINIMUM VERSION REQUIRED
S7700 S7703 Not supported
S7706 and S7712 V200R011C10, V200R012C00
S9700 S9703, S9706, and S9712 Not supported
 NOTE:

For details about software mappings, visit Hardware Query Tool and search for the desired product model.

Feature Limitations

Only the switches using SRUE, or SRUH main control units support VXLAN.

On a VXLAN network, interfaces can be classified into access-side interfaces and tunnel-side interfaces based on their locations.

  • Access-side interface: is used to connect a traditional network to a VXLAN network. The switch can provide VXLAN network access based on VLANs or traffic encapsulation types. For access based on a VLAN, the access-side interface is a member interface of the VLAN on a switch. For access based on a traffic encapsulation type, the access-side interface is the interface configured with the traffic encapsulation type.
  • Tunnel-side interface: forwards VXLAN packets to a VXLAN tunnel. After VXLAN encapsulation is performed on a switch, the interface performs route iteration based on the destination IP address (IP address of the remote end of the VXLAN tunnel) in the packets. For example, check the VXLAN tunnel and routing table information on the switch. The destination address of the VXLAN tunnel is 10.1.1.1, and the outbound interface of the route whose destination IP address is 10.1.1.1 is GE1/0/1. Therefore, the tunnel-side interface is GE1/0/1.

When a switch functions as a VXLAN tunnel endpoint (VTEP) on a VXLAN network, there must be a tunnel-side interface. Therefore, a card that supports tunnel-side interfaces must be installed on the switch and the tunnel-side interface must reside on the card. Only the interfaces on the X series cards can function as tunnel-side interfaces. If both access-side interfaces and tunnel-side interfaces exist, the cards providing access-side interfaces and those providing tunnel-side interfaces must meet the following mapping requirements:

ACCESS-SIDE TUNNEL-SIDE REMARKS
X series card X series card In this networking scenario, if an inter-card Eth-Trunk is deployed on the tunnel-side, all Eth-Trunk member interfaces must be able to work as tunnel interfaces. Otherwise, VXLAN packets cannot be forwarded on the Eth-Trunk functioning as a tunnel-side interface.
EA or EC series card X series card
  • In this networking scenario, if an inter-card Eth-Trunk is deployed on the tunnel-side, all Eth-Trunk member interfaces must be able to work as tunnel interfaces. Otherwise, VXLAN packets cannot be forwarded on the Eth-Trunk functioning as a tunnel-side interface.
  • In this networking scenario, the card on the access-side cannot function as a VXLAN Layer 3 gateway, and therefore cannot forward user-sent traffic that needs to be routed over VXLAN Layer 3.
  • In this networking scenario, if the access-side interface is also used as an inbound interface of multicast flows, multicast data cannot be forwarded properly.
B, F, SC, EE series card of the S7700 X series card
Be aware of the following when deploying the access-side of VXLAN on the switch:

  • When the encapsulation type of a VXLAN Layer 2 sub-interface is qinq or dot1q, the role of a switch in the VCMP domain cannot be client. Run the vcmp role { server | silent | transparent } command to set the switch to another role or run the vcmp disable command to disable VCMP on the interface.
  • The TPID value for the outer VLAN tag of QinQ packets configured on a VXLAN access-side interface does not take effect on packets entering the VXLAN network.
  • If the VXLAN access-side interface is a Layer 2 sub-interface and its encapsulation type is default, it can only communicate with a Layer 2 sub-interface of the encapsulation type default.
Be aware of the following when deploying the tunnel-side of VXLAN on the switch:

  • The switch does not support VXLAN over MPLS LSP tunnel. If VXLAN packets received from a peer are encapsulated by MPLS, the VTEP fails to decapsulate the packets.
  • The switch does not support VXLAN over GRE tunnel. If VXLAN packets received from a peer are encapsulated by GRE, the VTEP fails to decapsulate the packets.
  • If a VXLAN Network Identifier (VNI) has been created on the switch but not bound to VXLAN tunnels, the switch can still encapsulate and decapsulate VXLAN packets received from peers. However, the virtual tunnel end point (VTEP) access service is implemented in only one direction, but service transmission is abnormal.
  • The maximum transmission unit (MTU) determines the maximum number of bytes that can be sent by a device at a time. When a packet enters a VXLAN tunnel, 50 bytes are added to the packet. The switch importing traffic to a VXLAN tunnel cannot fragment packets. Instead, it normally forwards the packet even if the packet size exceeds the interface MTU.
Be aware of the following when deploying VXLAN on the switch in other situations:

  • If a card fails to deliver entries during the VXLAN tunnel establishment due to a hash conflict, the alarm ADPVXLAN_1.3.6.1.4.1.2011.5.25.227.2.1.42 hwVxlanTnlCfgFailed is triggered. To solve the problem, you are advised to adjust VNI IDs and re-configure VXLAN tunnels.
  • In V200R011C10, when an inter-card Eth-Trunk interface is created, it is recommended that you do not bind different Layer 2 VXLAN sub-interfaces of the Eth-Trunk interface to the same BD. Otherwise, Layer 2 unicast services may fail to be forwarded between the Layer 2 sub-interfaces. In addition, you are not advised to configure the Eth-Trunk interface at the tunnel side and the access side simultaneously in this scenario. Otherwise, Layer 2 unicast services may fail to be forwarded between the tunnel side and the access side.
  • In a distributed VXLAN gateway scenario, VXLAN Layer 2 wireless user roaming is supported if the user access VLANs and BD domains of the user access devices are consistent before and after user roaming.
  • In VXLAN scenarios, do not advertise routes destined for the local VTEP address to the peer end of a VXLAN tunnel through a VBDIF interface during route configuration. Otherwise, the next hop of the remote VTEP address of the VXLAN tunnel may be the VBDIF interface on the ingress of the tunnel, causing a loop on the device.
  • If the DHCP relay function is to be deployed in a distributed VXLAN gateway scenario, fixed switches are generally used as aggregation switches. The aggregation switches are configured as distributed VXLAN gateways on which the DHCP relay function is deployed. As routes are randomly selected for load balancing, response packets sent by the DHCP server may be centrally sent to a single user gateway for relay. If the number of BDs is too small or users are unevenly distributed in BDs, the DHCP server may send a large number of response packets to a gateway. As a result, the rate of received packets exceeds the CAR value on the gateway, affecting the rate at which users obtain IP addresses. Therefore, you are advised to take the following measures when there are too many users:

    • In a distributed VXLAN gateway scenario, the rate of concurrent online users (including wired and wireless users) on each aggregation switch depends on the number of aggregation switches. As the number of aggregation switches increases, the rate of concurrent online users on each aggregation switch decreases linearly. The following table provides sample data to describe the maximum rate of concurrent online users on each aggregation switch (S5730HI or S6720HI) with different numbers of aggregation switches.

      NUMBER OF AGGREGATION SWITCHES MAXIMUM RATE OF CONCURRENT ONLINE USERS ON EACH AGGREGATION SWITCH
      Less than or equal to 30 Not limited
      32 25 users per second
      48 15 users per second
      64 5 users per second

      If the S5720HI, S6720EI, or S6720S-EI switches are used as aggregation switches, users on an S5720HI include both wired and wireless users, and users on an S6720EI or S6720S-EI include only wired users. The maximum rate of concurrent online users on each S6720EI or S6720S-EI is 5 users per second.

      To ensure that the user online rate meets the preceding requirements, you can configure the CAR value for packets of the dhcp-server type on aggregation switches. When configuring the CAR value for packets of the dhcp-server type, obey the following formula between the value of cir_value (committed information rate) and the rate of concurrent online users: Rate of concurrent online users = cir_value x 1024/400/8. Assume that the rate of concurrent online users is 5 users per second. The value of cir_value is then calculated as 16, and the DHCP rate limit is configured as follows:

      <HUAWEI> system-view
      [HUAWEI] cpu-defend-policy policy1
      [HUAWEI-cpu-defend-policy-policy1] car packet-type dhcp-server cir 16
      [HUAWEI-cpu-defend-policy-policy1] quit
      [HUAWEI] cpu-defend-policy policy1
      [HUAWEI] cpu-defend-policy policy1 global
      
    • Run the car packet-type packet-type cir cir-value [ cbs cbs-value ] command to increase the CAR value for packets with the packet type being dhcp-client. You can run the display cpu-defend configuration command to view the CAR value for packets. Improper CAR settings affect services on your network. If you need to adjust CAR settings, you are advised to contact technical support personnel for help.
    • Allocate users to different BDs evenly and ensure that the number of BDs is not less than the number of gateway devices. This configuration increases the number of routes involved in route selection, so that the response packets sent by the DHCP server are evenly load balanced among distributed gateway devices.
    • During configuration planning, allocate users to different BDs evenly if possible. The VLAN pool mode is recommended for wireless users, and the number of associated VLANs in each BD must be the same. In this way, users are allocated to different BDs evenly.
    • When planning the IP addresses of distributed gateways, use the first IP addresses of contiguous address segments if possible. This increases the dispersion of hash calculation results during load balancing.
  • When the DHCP relay function is configured on distributed gateways in a distributed VXLAN gateway scenario, you need to run the auto-port-defend whitelist whitelist-number interfaceinterface-type interface-number command to add the tunnel-side interface to the whitelist for port attack defense.

About Us

As a world leading Huawei networking products supplier, Hong Telecom Equipment Service LTD(HongTelecom) keeps regular stock of Huawei router and switch and all cards at very good price, also HongTelecom ship to worldwide with very fast delivery.

For related articles, visit the HongTelecom Blog and HongTelecom WordPress.
For real pictures of related product, visit the HongTelecom Gallery.
To buy related product, visit the HongTelecom Online Shop.

何诗名片

Link Aggregation of Ethernet Switching for Huawei S7700/S9700 Switch

Huawei Campus Switch includes S1700, S2300, S2700, S3300, S3700, S5300, S5700, S600-E, S6300, S6700, S7700, S7900, S9300, S9300X, S9700, S12700 Series. In this article, HongTelecom will introduce the Link Aggregation of Ethernet Switching for Huawei S7700/S9700 Switch.

Link Aggregation

Involved Network Elements

Other network elements are not required.

Licensing Requirements

Ethernet link aggregation is a basic feature of a switch and is not under license control.

Version Requirements

Table 1 Products and versions supporting link aggregation
PRODUCT PRODUCT MODEL SOFTWARE VERSION
S7700 S7703, S7706, S7712 V100R003C01, V100R006C00, V200R001(C00&C01), V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00
S9700 S9703, S9706, S9712 V200R001(C00&C01), V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007(C00&C10), V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00
 NOTE:

For details about software mappings, visit Hardware Query Tool and search for the desired product model.

Feature Limitations

Configuration Notes Before an Eth-Trunk Is Configured

  • You can run the assign trunk { trunk-group group-number | trunk-member member-number }* command to configure the maximum number of Eth-Trunks and maximum number of member interfaces in each Eth-Trunk only when cards with Eth-Trunk specification extension are installed on the switch. For details, see the description of the assign trunk command in “Ethernet Switching Configuration Commands” in the Command Reference of the corresponding version. After the configuration, you can run the display trunk configuration command to check the default specifications of the maximum number of Eth-Trunks that are supported and maximum number of member interfaces in each Eth-Trunk, current specifications, and configured specifications.

    NOTE:

    • If cards without Eth-Trunk specification extension are installed on the switch, this command cannot be run to change the maximum number of Eth-Trunks that are supported and maximum number of member interfaces in each Eth-Trunk. In this case, the switch supports a maximum of 128 Eth-Trunks with each Eth-Trunk supporting a maximum of eight member interfaces in each Eth-Trunk.
    • Cards are classified into cards with and without Eth-Trunk specification extension depending on the support for the assign trunk command. Cards with Eth-Trunk specification extension are as follows and other cards do not support Eth-Trunk specification extension:
      • S7700: FC series, SC series, EE series, and X series cards
      • S9700: FC series, SC series, EE series, X series, ET1D2X48SEC0, and EH1D2X48SEC0 cards
  • Member interfaces cannot be configured with some services or static MAC address entries. For example, when an interface is added to an Eth-Trunk, the interface must use the default link type.
  • Do not configure any member port of an Eth-Trunk as an observing port. If you must do so, ensure that the bandwidth of service traffic on this port and the bandwidth occupied by the mirrored traffic do not exceed the bandwidth limit of the port.
  • Member interfaces of an Eth-Trunk cannot be an Eth-Trunk.
  • In versions earlier than V200R011C10, interfaces with different rates cannot join the same Eth-Trunk. In V200R011C10 and later versions, interfaces with different rates can temporarily join the same Eth-Trunk by running the mixed-rate link enable command.
  • When an Eth-Trunk performs load balancing calculation, the interface rate cannot be used as the calculation weight. When interfaces with different rates are added to the same Eth-Trunk, traffic is evenly load balanced among all the links. Therefore, the bandwidth of member interfaces is calculated by the minimum rate of the member interfaces in the Eth-Trunk. For example, when a GE interface and a 10GE interface are added to the same Eth-Trunk, the rate of the GE interface is used in calculation and the bandwidth of the Eth-Trunk is 2G.
  • Both devices of the Eth-Trunk must use the same number of physical interfaces, interface rate, duplex mode, and flow control mode.
  • If an interface of the local device is added to an Eth-Trunk, an interface of the remote device directly connected to the interface of the local device must also be added to the Eth-Trunk. Otherwise, communication between the two devices will fail.
  • Both devices of an Eth-Trunk must use the same link aggregation mode.
  • In V200R008 and earlier versions, the assign trunk command fails to be executed on the device enabled with SVF, and Eth-Trunk specifications can only use the default settings.
  • When the number of active interfaces falls below the lower threshold, the Eth-Trunk goes Down. This ensures that the Eth-Trunk has a minimum available bandwidth.
  • Before the software version V100R006 is upgraded to any version in the range from V200R001 to V200R011C10, ensure that no Eth-Trunk is established across an ES1D2X40SFC0/ES1D2X16SFC0 board and a non-ES1D2X40SFC0/ES1D2X16SFC0 board. If such an Eth-Trunk exists, traffic forwarding may fail on the Eth-Trunk after the upgrade.

In the following scenarios, there are other configuration notes in addition to the preceding ones.

Table 2 Configuration notes in different scenarios
USAGE SCENARIO PRECAUTION
Switches Are Connected Across a Transmission Device
  • The switches at both ends must use link aggregation in LACP mode.
  • The transmission device between the switches must be configured to transparently transmit LACPDUs.
Switches Connect to Transmission Devices
  • The link aggregation mode on the transmission device must be the same as that of the switch. Configure the transmission device according to its operation guide.
A Switch Connects to a Server
  • Network adapters of the server must be of the same type.
  • The link aggregation modes on the server and access device must be consistent.For example, if an Intel network adapter is used, a server often uses static or IEEE 802.3ad dynamic link aggregation. When the server uses static link aggregation, the access device must use the manual mode. When the server uses IEEE 802.3ad dynamic link aggregation, the access device must use the LACP mode.
  • When a server needs to obtain the configuration file from the remote file server through a switch and link aggregation needs to be used, run the lacp force-forward command on the Eth—Trunk of the switch.
Switches Are Connected Through Inter-card Link Aggregation
Interfaces on different cards of a switch can join the same Eth-Trunk, that is, inter-card Eth-Trunk. Interfaces on cards without Eth-Trunk specification extension can constitute an inter-card Eth-Trunk. Before interfaces on a card with Eth-Trunk specification extension and interfaces on another card constitute an inter-card Eth-Trunk, use the eth-trunk load-balance hash-mode command to configure the hash mode for the card with Eth-Trunk specification extension.

  • When interfaces on different cards with Eth-Trunk specification extension form an Eth-Trunk, ensure that the cards use the same hash mode.
  • When interfaces on the card with Eth-Trunk specification extension form an Eth-Trunk with interfaces on the card without Eth-Trunk specification extension, configure the normal hash mode on the card with Eth-Trunk specification extension.

In earlier versions of V200R010C00, only X series cards among cards with Eth-Trunk specification extension support the hash mode configuration. The hash mode on other cards with Eth-Trunk specification extension has a fixed value of advance. In V200R010C00 and later versions, interfaces on only X series cards among cards with Eth-Trunk specification extension can form Eth-Trunks with interfaces on cards without Eth-Trunk specification extension. Interfaces on other cards with Eth-Trunk specification extension cannot form Eth-Trunks with interfaces on cards without Eth-Trunk specification extension.

In V200R010C00 and later versions, cards with Eth-Trunk specification extension support the hash mode configuration. When the hash mode on a card with Eth-Trunk specification extension is set to normal, interfaces on the card with Eth-Trunk specification extension can form an Eth-Trunk with interfaces on the card without Eth-Trunk specification extension.

Configuration Notes After an Eth-Trunk Is Configured

  • An Ethernet interface can be added to only one Eth-Trunk. To add an Ethernet interface to another Eth-Trunk, delete it from the original one first.
  • After an interface is added to an Eth-Trunk, the Eth-Trunk learns MAC address entries or ARP entries, but the member interface does not.
  • Before deleting an Eth-Trunk, delete member interfaces from the Eth-Trunk.

SpecificationsLink aggregation mode:

  • Manual
  • LACPIf both devices support LACP, link aggregation in LACP mode is recommended.

Link aggregation modes supported by the device:

  • Intra-card: Member interfaces of an Eth-Trunk are located on the same card.
  • Inter-card: Member interfaces of an Eth-Trunk are located on different cards.
  • Inter-chassis: Member interfaces of an Eth-Trunk are located on member devices of a CSS. For details, see Link Aggregation in CSS Scenarios.
  • Inter-device: The inter-device link aggregation refers to E-Trunk. E-Trunk allows links between multiple devices to be aggregated using LACP. For details, see E-Trunk.

Load balancing modes supported by the device:

To prevent data packet mis-sequencing, an Eth-Trunk uses flow-based load balancing.

You can use the following load balancing modes based on actual networking:

  • Source MAC addresses of data frames
  • Destination MAC addresses of data frames
  • Source IP addresses of data frames
  • Destination IP addresses of data frames
  • Exclusive-Or result of source and destination MAC addresses of data frames
  • Exclusive-Or result of source and destination IP addresses of data frames
  • (Enhanced load balancing) VLAN IDs and source physical interface numbers for Layer 2, IPv4, IPv6, and MPLS data frames

About Us

As a world leading Huawei networking products supplier, Hong Telecom Equipment Service LTD(HongTelecom) keeps regular stock of Huawei router and switch and all cards at very good price, also HongTelecom ship to worldwide with very fast delivery.

For related articles, visit the HongTelecom Blog and HongTelecom WordPress.
For real pictures of related product, visit the HongTelecom Gallery.
To buy related product, visit the HongTelecom Online Shop.

何诗名片

Ethernet Interface of Product Use Precautions for Huawei S7700/S9700 Switch

Huawei Campus Switch includes S1700, S2300, S2700, S3300, S3700, S5300, S5700, S600-E, S6300, S6700, S7700, S7900, S9300, S9300X, S9700, S12700 Series. In this article, HongTelecom will introduce the Ethernet Interface of Product Use Precautions for Huawei S7700/S9700 Switch.

Ethernet Interface

Involved Network Element

Other network elements are not required.

Licensing Requirements

An Ethernet interface is a basic feature of a switch and is not under license control.

Version Requirements

Table 1 Products and versions supporting Ethernet interfaces
PRODUCT PRODUCT MODEL VERSION SUPPORTING DIFFERENT TYPES OF INTERFACES
S7700 S7703, S7706, S7712
  • FE electrical interfaces/GE electrical interfaces/GE optical interfaces/XGE optical interfaces:V100R003C01, V100R006C00, V200R001(C00&C01), V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00
  • FE optical interfaces:Not supported in any version
  • 40GE optical interfaces:V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00
  • 100GE optical interfaces:V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00
S9700 S9703, S9706, S9712
  • FE electrical interfaces/GE electrical interfaces/FE optical interfaces/GE optical interfaces/XGE optical interfaces:V200R001(C00&C01), V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007(C00&C10), V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00
  • 40GE optical interfaces:V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00
  • 100GE optical interfaces:V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00

 NOTE:

For details about software mappings, visit Hardware Query Tool and search for the desired product model.

Feature Limitations

  • Table 2 lists the common attributes of Ethernet interfaces.

    Table 2 Common attributes of Ethernet interfaces
    INTERFACE TYPE COMMON ATTRIBUTES REMARKS
    FE electrical interfaces
    • Transmission medium: network cable
    • Rate: 10 Mbit/s and 100 Mbit/s
    • Duplex mode: full-duplex/half-duplex
    • Auto-negotiation: supported
    • Flow control: supported
    • Flow control auto-negotiation: supported
    GE electrical interfaces
    • Transmission medium: network cable
    • Rate: 10 Mbit/s, 100 Mbit/s, and 1000 Mbit/s
    • Duplex mode: full-duplex/half-duplex. When the rate is 1000 Mbit/s, only full-duplex is supported.
    • Auto-negotiation: supported
    • Flow control: supported
    • Flow control auto-negotiation: supported
    The duplex mode cannot be configured for interfaces on the X1E series cards working in either auto-negotiation or non-auto-negotiation mode.
    FE optical interfaces
    • Transmission medium: FE optical module
    • Rate: 100 Mbit/s
    • Duplex mode: full-duplex
    • Auto-negotiation: not supported
    • Flow control: supported
    • Flow control auto-negotiation: not supported
    GE optical interfaces

    When the transmission medium is an FE optical module:

    • Rate: 100 Mbit/s
    • Duplex mode: full-duplex
    • Auto-negotiation: not supported
    • Flow control: supported
    • Flow control auto-negotiation: not supported

    When the transmission medium is a GE optical module:

    • Rate: 100 Mbit/s and 1000 Mbit/s
    • Duplex mode: full-duplex
    • Auto-negotiation: supported
    • Flow control: supported
    • Flow control auto-negotiation: supported

    When the transmission medium is a GE copper module:

    • Rate: 10 Mbit/s, 100 Mbit/s, and 1000 Mbit/s
    • Duplex mode: full-duplex/half-duplex. When the rate is 1000 Mbit/s, only full-duplex is supported.
    • Auto-negotiation: supported
    • Flow control: supported
    • Flow control auto-negotiation: supported
    • By default, auto-negotiation is enabled on GE optical interfaces and rate auto-negotiation is disabled. You can run the speed auto-negotiation command to enable rate auto-negotiation.
    • After a copper module is installed on a GE optical interface of an X2E/X2S series card, the interface can work at the rate of 100 Mbit/s or 1000 Mbit/s (including forcible configuration and auto-sensing), and cannot work at the rate of 10 Mbit/s. When the interface works as an optical interface, it can only work at the rate of 1000 Mbit/s, and cannot work at the rate of 100 Mbit/s.
    XGE (10GE) optical interface

    When the transmission medium is an XGE optical module:

    • Rate: 10000 Mbit/s
    • Duplex mode: full-duplex
    • Auto-negotiation: not supported
    • Flow control: supported
    • Flow control auto-negotiation: not supported

    When the transmission medium is an XGE or GE optical module:

    • Rate: 1000 Mbit/s and 10000 Mbit/s
    • Duplex mode: full-duplex
    • Auto-negotiation: not supported
    • Flow control: supported
    • Flow control auto-negotiation: not supported

    When the transmission medium is a GE optical module:

    • Rate: 1000 Mbit/s
    • Duplex mode: full-duplex
    • Auto-negotiation: supported
    • Flow control: supported
    • Flow control auto-negotiation: not supported

    When the transmission medium is a GE copper module:

    • Rate: 1000 Mbit/s
    • Duplex mode: full-duplex
    • Auto-negotiation: supported
    • Flow control: supported
    • Flow control auto-negotiation: supported
    • Only cards with MAB version 1 in V200R007 and later versions support XGE/GE optical modules. The cards include:

      • SC series cards
      • ES1D2X16SFC00, ES1D2X40SFC0, ES1D2X40SFC0, ES1D2X16SFC00, EH1D2X16SFC0, and EH1D2X40SFC0 cards in the FC series
      • EH1D2X48SEC0 and ET1D2X48SEC0 cards in the EC series
    • Assume that an XGE optical interface has an XGE/GE optical module installed and the interface rate is set to 1000 Mbit/s using the speed auto 1000command. When you run the display interface command on the interface, the command output shows that auto-negotiation is enabled. However, you cannot run the negotiation auto command to configure the auto-negotiation mode.
    • On the S7700, the interfaces on the ES0D0X12SA00 and ES1D2X08SED4 cards, and XGE optical interfaces on the ES1D2S04SX1E and ES1D2S08SX1E cards do not support GE copper modules.
    • On the S9700, the interfaces on the EH1D2X12SSA0, ET1D2X12SSA0 and EH1D2X08SED4 cards, and XGE optical interfaces on the EH1D2S04SX1E, ET1D2S04SX1E, ET1D2S08SX1E and EH1D2S08SX1E cards do not support GE copper modules.
    • After a GE copper module is installed on an XGE interface of an X2E/X2H/X2S series card, the interface can work at the rate of 100 Mbit/s or 1000 Mbit/s, and cannot work at the rate of 10 Mbit/s.
    • After a 1000M optical module is installed on an XGE interface of an X2E/X2H/X2S series card, the interface can work at the rate of 1000 Mbit/s.
    40GE optical interfaces

    When the transmission medium is a 40GE optical module:

    • Rate: 40000 Mbit/s
    • Duplex mode: full-duplex
    • Auto-negotiation: not supported
    • Flow control: supported
    • Flow control auto-negotiation: not supported

    When the transmission medium is a high-speed cable:

    • Rate: 40000 Mbit/s
    • Duplex mode: full-duplex
    • Auto-negotiation: supported
    • Flow control: supported
    • Flow control auto-negotiation: not supported
    • When you run the display interface command on a 40GE optical interface that has a high-speed cable installed, the command output shows that auto-negotiation is enabled. However, you cannot run the negotiation autocommand to configure the auto-negotiation mode.
    100GE optical interfaces

    When the transmission medium is a 100GE optical module:

    • Rate: 100000 Mbit/s
    • Duplex mode: full-duplex
    • Auto-negotiation: not supported
    • Flow control: supported
    • Flow control auto-negotiation: not supported

    When the transmission medium is a 40GE optical module:

    • Rate: 40000 Mbit/s
    • Duplex mode: full-duplex
    • Auto-negotiation: not supported
    • Flow control: supported
    • Flow control auto-negotiation: not supported

    When the transmission medium is a high-speed cable:

    • Rate: 40000 Mbit/s and 100000 Mbit/s
    • Duplex mode: full-duplex
    • Auto-negotiation: supported
    • Flow control: supported
    • Flow control auto-negotiation: not supported
    • Only the EE series cards, ES1D2C04HX2E, ES1D2C04HX2S, ES1D2H02QX2E, ES1D2H02QX2S, ET1D2C04HX2E, ET1D2C04HX2S, ET1D2H02QX2E and ET1D2H02QX2S cards support 100GE interfaces.
    • 100GE interfaces on the EE series cards can only have 100GE optical modules installed.
    • After a 40GE optical module or 40GE high-speed cable is installed on a 100GE interface of an X2E/X2H/X2S series card, the interface can work at the rate of 40 Gbit/s.
  • X series cards do not support the duplex mode configuration.
  • The EH1D2G48TBC0 and EH1D2G48SBC0 cards of the S9700 do not support flow control or flow control auto-negotiation.
  • On the S7700, only the ES1D2L02QFC0 interface card supports the IFG configuration.On the S9700, only the EH1D2L08QFC0, EH1D2L02QFC0, ET1D2L08QSC0, and ET1D2L02QSC0 interface cards support the IFG configuration.
  • On the S7700, only the E series cards (excluding EE cards), ES0D0X12SA00 card and SC cards in the S series, and FC cards in the F series support unidirectional single-fiber communication. A license is required. On the S9700, only the E series cards (excluding EE cards and EH1D2S24CEA0), ET1D2X12SSA0 card, EH1D2X12SSA0 card and SC cards in the S series, and FC cards in the F series support unidirectional single-fiber communication. A license is required.

About Us

As a world leading Huawei networking products supplier, Hong Telecom Equipment Service LTD(HongTelecom) keeps regular stock of Huawei router and switch and all cards at very good price, also HongTelecom ship to worldwide with very fast delivery.

For related articles, visit the HongTelecom Blog and HongTelecom WordPress.
For real pictures of related product, visit the HongTelecom Gallery.
To buy related product, visit the HongTelecom Online Shop.

何诗名片

Easy Deploy Basic Configuration for Huawei S7700 and S9700 Switch

Huawei Campus Switch includes S1700, S2300, S2700, S3300, S3700, S5300, S5700, S600-E, S6300, S6700, S7700, S7900, S9300, S9300X, S9700, S12700 Series. In this article, HongTelecom will introduce the Easy Deploy Basic Configuration for Huawei S7700 and S9700 Switch.

EasyDeploy

Involved Network Elements

EasyDeploy networking involves the following components:

  • DHCP server
  • File server
  • Commander and client

Licensing Requirements

EasyDeploy is a basic feature of a switch and is not under license control.

Version Requirements

Table 1 Products and versions supporting EasyDeploy
SERIES PRODUCT MODEL SOFTWARE VERSION
S9700 S9703, S9706, S9712 V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00
S7700 S7703S7706, S7712 V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00, V200R011C10, V200R012C00
 NOTE:

For details about software mappings, visit Hardware Query Tool and search for the desired product model.

Feature Limitations

  • The EasyDeploy cannot be applied on an IPv6 or VPN network.
  • EasyDeploy is mutually exclusive with USB-based deployment and SVF.
  • In the unconfigured device deployment or faulty device replacement scenarios, if you log in to a device to be configured through its console interface, the device stops the EasyDeploy process and starts to operate.
  • In the unconfigured device deployment and faulty device replacement scenarios, EasyDeploy can only run on the service interfaces in the default VLAN.
  • In the unconfigured device deployment scenario, you can decide whether to specify the configuration file based on actual requirements. If the configuration file is not specified and the upgrade system software is specified, you also need to specify the upgrade version number.
  • There is no limitation on the network location of the Commander as long as there are reachable routes between the Commander and clients that obtain IP addresses.
  • EasyDeploy allows a stack system to act as a client. In this case, the client MAC address is the system MAC address of the stack system, and the client ESN is the ESN of the stack master switch.
  • When the EasyDeploy topology collection function is enabled, the Commander that initiates topology collection will receive a large number of protocol packets if the Network Topology Discovery Protocol (NTDP) needs to collect the topology of more than 200 devices. If the rate of NTDP packets exceeds the default committed access rate (CAR), NTDP packets will be dropped. To prevent packet loss from affecting topology collection, you can run the car (attack defense policy view) command to increase the central processor CAR (CPCAR) of NTDP packets.
  • Datagram Transport Layer Security (DTLS) encryption
    • On a configured switch, EasyDeploy supports DTLS encryption. By default, DTLS encryption is enabled. In the unconfigured device deployment scenario, a switch can be normally deployed regardless of whether DTLS encryption is enabled.
    • If an active/standby switchover occurs on the Commander or between clients when DTLS encryption is enabled, the clients need to go online again. If DTLS encryption is disabled, an active/standby switchover does not affect online management of clients.
    • If a client in a version earlier than V200R010C00 needs to be managed by the Commander in V200R010C00 or a later version and DTLS encryption is enabled on the Commander, you must upgrade the system software of the client to V200R010C00 or a later version. Otherwise, the client cannot join the existing network.
    • If a client in V200R010C00 or a later version needs to be managed by the Commander in a version earlier than V200R010C00, you need to run the easy-operation dtls disable command on the client to disable DTLS encryption.
  • SpecificationsTable 2 lists the product models that support the EasyDeploy and specifications of this feature.

    Table 2 EasyDeploy specifications
    ROLE PRODUCT MODEL VERSION MAXIMUM NUMBER OF MANAGED CLIENTS DESCRIPTION
    Commander S7700 and S9700 S7700 and S9700: V200R003C00 and later 255
    • If the clients are modular switches, EasyDeploy can only be applied to the batch upgrade and batch configuration scenarios.
    • If the clients are fixed switches, EasyDeploy applies to the batch upgrade, batch configuration, unconfigured device deployment, and faulty device replacement scenarios.
    S12700 V200R005C00 and later 255
    S5700HI, S5710HI, S6700EI V200R003C00 to V200R005C00 128
    S5700EI and S5710EI 64
    S5720HI V200R006C00 and later 128
    S5720EI V200R007C00 and later 128
    S6720EI V200R008C00 and later 128
    S6720S-EI V200R009C00 and later 128
    S6720HI V200R012C00 128
    S5730HI V200R012C00 128
    Client
    • All fixed switch models except S1720GFR, S1720GW-E, S1720GWR-E and S1720X-E
    • All modular switch models
    V200R003C00 and later
  • Table 3 lists the types of files that can be loaded through EasyDeploy in various scenarios.

    Table 3 File types supported by EasyDeploy
    USAGE SCENARIO FILE TYPE
    Unconfigured device deployment System software, patch file, web page file, configuration file, and user-defined file
    Faulty device replacement System software, patch file, web page file, configuration file (automatically backed up), and user-defined file
    Batch upgrade System software, patch file, web page file, configuration file, license file (supported when the clients are modular switches), and user-defined file
    Batch configuration Command script

    Each device can download a maximum of three user-defined files, including batch file and login headline file.

About Us

As a world leading Huawei networking products supplier, Hong Telecom Equipment Service LTD(HongTelecom) keeps regular stock of Huawei router and switch and all cards at very good price, also HongTelecom ship to worldwide with very fast delivery.

For related articles, visit the HongTelecom Blog and HongTelecom WordPress.
For real pictures of related product, visit the HongTelecom Gallery.
To buy related product, visit the HongTelecom Online Shop.

何诗名片

Huawei S7700 Switch Card Types

Huawei Campus Switch includes S1700, S2300, S2700, S3300, S3700, S5300, S5700, S600-E, S6300, S6700, S7700, S7900, S9300, S9300X, S9700, S12700 Series. In this article, HongTelecom will introduce Huawei S7700 Switch Card Types.

S7700 Card Types

The following describe the different types of Line Processing Units (LPUs):

  • The S series includes SA and SC interface cards, for example, 24-port 100M/1000M BASE-X interface card (SA, SFP).
  • The E series includes EA, EC, ED, and EE interface cards, for example, 48-port 100M BASE-X interface card (EA, SFP).
  • The F series includes FA and FC interface cards, for example, 48-port 1000M BASE-T interface card (FA, RJ45).
  • The B series has BC interface cards, for example, 48-port 100M/1000M BASE-X interface card (BC, SFP).
  • The X series includes X1E, X2S, X2E, X5E, X5H, X5L, and X5S interface cards, for example, 48-port 10/100/1000BASE-T interface card (X1E, RJ45).
  • All the S7700 cards comply with the FCC standards except the ES0D0X2UXA00, ES0D0X2UXC00, ES0D0X4UXA00, ES0D0X4UXC00, ES1D2X04XED0, ES1D2X08SED4 and ES0D0X12SA00.
  • The FCC-certified cards must be used with the FCC-certified chassis.

Table 1 lists the cards supported by the S7700.

 NOTE:

The cards supported by a switch depend on the software version. For details, see Hardware Query Tool.

Table 1 Cards supported by the S7700
Card Type Card Name Card Description Card Series Supported Version Maximum Power Consumption Weight Part Number

Main control unit

ES0D00SRUA00 S7706/S7706 PoE/S7712 Main Control Unit A S7703 and S7703 PoE chassis: not supported

S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7706 PoE chassis: supported in V200R013C00 and later versions

81 W (including subcards) 2.80 kg (6.17 lb) 03030MQS
Main control unit ES1D2SRUAC00 S7706/S7706 PoE/S7712 Main Control Unit A (optional clock) S7703 and S7703 PoE chassis: not supported

S7706 and S7712 chassis: supported in V200R010C00 and later versions

S7706 PoE chassis: supported in V200R013C00 and later versions

87 W (including subcards) 2.90 kg (6.39 lb) 03032DVG
Main control unit ES0D00SRUB00 S7706/S7706 PoE/S7712 Main Control Unit B (optional clock) S7703 and S7703 PoE chassis: not supported

S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7706 PoE chassis: supported in V200R013C00 and later versions

105 W (including subcards) 2.90 kg (6.39 lb) 03030MQR
Main control unit ES1D2SRUE000 S7706/S7706 PoE/S7712 Main Control Unit E S7703 and S7703 PoE chassis: not supported

S7706 and S7712 chassis: supported in V200R010C00 and later versions

S7706 PoE chassis: supported in V200R013C00 and later versions

105.7 W (including subcards) 3.05 kg (6.72 lb) 03031YLV
Main control unit ES1D2SRUH000 S7706/S7706 PoE/S7712 Main Control Unit H S7703 and S7703 PoE chassis: not supported

S7706 and S7712 chassis: supported in V200R008C00 and later versions

S7706 PoE chassis: supported in V200R013C00 and later versions

183 W (including subcards) 3.46 kg (7.63 lb) 03031FSL
Main control unit ES1D2SRUH002 S7706/S7706 PoE/S7712 Main Control Unit H (Support Secure Boot) S7703 and S7703 PoE chassis: not supported

S7706 and S7712 chassis: supported in V200R012C00 and later versions

S7706 PoE chassis: supported in V200R013C00 and later versions

183 W (including subcards) 3.46 kg (7.63 lb) 03032TXW
Main control unit ES0D00MCUA00 S7703/S7703 PoE Main Control Unit A S7703 chassis: supported in V100R003C01 and later versions

S7703 PoE chassis: supported in V200R013C00 and later versions

S7706, S7706 PoE, and S7712 chassis: not supported

18 W 0.90 kg (1.98 lb) 03030MPV
Main control unit ES1D2MCUAC00 S7703/S7703 PoE Main Control Unit A (optional clock) S7703 chassis: supported in V200R010C00 and later versions

S7703 PoE chassis: supported in V200R013C00 and later versions

S7706, S7706 PoE, and S7712 chassis: not supported

26 W (including subcards) 0.90 kg (2.0 lb) 03032DVF
Main control unit ES1D2MCUD000 S7703 Main Processing Unit D S7703 chassis: Supported in V200R013C01 and later versions

S7703 PoE, S7706, S7706 PoE, and S7712 chassis: not supported

21 W 1.12 kg (2.47 lb) 03032YFG

Subcard on the main control unit

ES0D00FSUA00 Enhanced Flexible Service Unit S7703 and S7703 PoE chassis: not supported

S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7706 PoE chassis: supported in V200R013C00 and later versions

20 W 0.42 kg (0.93 lb) 03030MQQ
Subcard on the main control unit LE0D00CKMA00 Clock pinch board-1588 S7703, S7706, and S7712 chassis: supported in V200R010C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

6 W 0.10 kg (0.22 lb) 03020PPT
Subcard on the main control unit ES02VSTSA

NOTE:

This card has replaced LE0D0VSTSA00 since July 1, 2013.

Cluster Switching System Service Unit S7703 and S7703 PoE chassis: not supported

S7706 and S7712 chassis: This card is supported in V200R001C00 and later versions, and is sold since July 1, 2013.

S7706 PoE chassis: supported in V200R013C00 and later versions

12 W 1 kg (2.20 lb) 03030QHL
Subcard on the main control unit LE0D0VSTSA00

NOTE:

This card is replaced by ES02VSTSA since July 1, 2013.

Cluster Switching System Service Unit S7703 and S7703 PoE chassis: not supported

S7706 and S7712 chassis: end of marketing on June 30, 2013. Use ES02VSTSA instead.

S7706 PoE chassis: Use ES02VSTSA instead.

12 W 1 kg (2.20 lb)
Subcard on the main control unit ES1D2VS04000 Cluster Switching System Service Unit S7703 and S7703 PoE chassis: not supported

S7706 and S7712 chassis: supported in V200R009C00 and later versions

S7706 PoE chassis: supported in V200R013C00 and later versions

12 W 0.34 kg (0.75 lb) 03030XYD
Monitoring unit EH1D200CMU00

NOTE:

This card has replaced LE0DCMUA0000 since February 1, 2013.

Centralized Monitoring Unit S7703 and S7703 PoE chassis: not supported

S7706 and S7712 chassis: This card is supported since February 01, 2013. It is supported in V100R003C01 and later versions.

S7706 PoE chassis: supported in V200R013C00 and later versions

1 W 0.22 kg (0.48 lb) 03030NWB
Monitoring unit LE0DCMUA0000

NOTE:

This card is replaced by EH1D200CMU00 since February 1, 2013.

Centralized Monitoring Unit S7703 and S7703 PoE chassis: not supported

S7706 and S7712 chassis: end of service on January 31, 2013. Use EH1D200CMU00 instead.

S7706 PoE chassis: Use EH1D200CMU00 instead.

1 W 0.22 kg (0.48 lb)
Value-added service card LE0D0VAMPA00 Value-added service card Supported in V100R003C01 to V200R008C00 120 W 3.10 kg (6.83 lb) 03020RRN
OSPU EH1D2PS00P00

NOTE:

This card is sold since January 1, 2015.

Open Service Platform Unit S7703, S7706 and S7712 chassis: This card is supported in V200R006C00 and later versions, and is sold since January 1, 2015.

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

137.5 W 5.50 kg (12.13 lb) 03021PHK
OSPU ES1D2PS00P00

NOTE:

This card is no longer sold since December 31, 2014.

Open Service Platform Unit S7703, S7706 and S7712 chassis: This card is supported in V200R002C00 and later versions, and is no longer sold since December 31, 2014.

S7703 PoE and S7706 PoE chassis: This card is supported in V200R013C00 and later versions, and is no longer sold since December 31, 2014.

137.5 W 5.50 kg (12.13 lb)

100M interface card

ES0D0F48TA00 48-port 10/100BASE-T interface card (EA, RJ45) EA S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

59 W 2.50 kg (5.51 lb) 03030LXL
100M interface card ES0D0F48TC00 48-port 10/100BASE-T interface card (EC, RJ45) EC S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

70 W 2.62 kg (5.78 lb) 03030MQV
100M interface card ES0DF48TFA00 48-port 10/100BASE-T interface card (FA, RJ45) FA S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

40 W 2.30 kg (5.07 lb) 03030MQW

1000M interface card

ES0D0G24SA00 24-port 100/1000BASE-X interface card (SA, SFP) SA S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

45 W 2.22 kg (4.89 lb) 03030MQP
1000M interface card ES0D0G24SC00 24-port 100/1000BASE-X interface card (EC, SFP) EC S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

63 W 2.66 kg (5.86 lb) 03030MQN
1000M interface card ES1D2G24SED0 24-port 100/1000BASE-X interface card (ED, SFP) ED S7703, S7706 and S7712 chassis: supported in V200R002C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

75 W 2.66 kg (5.86 lb) 03030QJQ
1000M interface card ES1D2G24SX5L 24-Port 100/1000BASE-X Interface Card (X5L, SFP) X5L Supported in V200R013C00 and later versions 84 W 2.82 kg (6.22 lb) 03032WTC
1000M interface card ES1D2G24SX5E 24-Port 100/1000BASE-X Interface Card (X5E, SFP) X5E Supported in V200R013C00 and later versions 84 W 2.82 kg (6.22 lb) 03032WTD
1000M interface card ES0D0G24CA00 24-port 100/1000BASE-X and 8-port 10/100/1000BASE-T combo interface card (SA, SFP/RJ45) SA S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

67 W 2.26 kg (4.98 lb) 03030LGK
1000M interface card ES0DG48CEAT0 36-port 10/100/1000BASE-T and 12-port 100/1000BASE-X interface card (EA, RJ45/SFP) EA S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

62 W 2.50 kg (5.51 lb) 03030JFH
1000M interface card ES0D0G48VA00 48-port 10/100/1000BASE-T PoE interface card (EA, RJ45, PoE) EA S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

64 W (not including PoE power consumption) 2.60 kg (5.73 lb) 03030KQT
1000M interface card ES1D2G48VX5S 48-port 100/1000BASE-T PoE interface card (X5S, RJ45, PoE++) X5S Supported in V200R013C00 and later versions 60 W 3.35 kg (7.39 lb) 03032WSC
1000M interface card ES1D2G48VX5E 48-port 100/1000BASE-T PoE interface card (X5E, RJ45, PoE++) X5E Supported in V200R013C00 and later versions 60 W 3.35 kg (7.39 lb) 03032WSE
1000M interface card ES0DG24TFA00 24-port 10/100/1000BASE-T interface card (FA, RJ45) FA S7703, S7706 and S7712 chassis: supported in V100R006C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

32 W 2.20 kg (4.85 lb) 03030NGA
1000M interface card ES0D0G48TA00 48-port 10/100/1000BASE-T interface card (EA, RJ45) EA S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

62 W 2.50 kg (5.51 lb) 03030MQM
1000M interface card ES0D0G48TC00 48-port 10/100/1000BASE-T interface card (EC, RJ45) EC S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

68 W 2.62 kg (5.78 lb) 03030MQL
1000M interface card ES1D2G48TED0 48-port 10/100/1000BASE-T interface card (ED, RJ45) ED S7703, S7706 and S7712 chassis: supported in V200R002C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

98 W 2.62 kg (5.78 lb) 03030QJR
1000M interface card ES0DG48TFA00 48-port 10/100/1000BASE-T interface card (FA, RJ45) FA S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

48 W 2.50 kg (5.51 lb) 03030MQX
1000M interface card ES1D2G48TX1E 48-port 10/100/1000BASE-T interface card (X1E, RJ45) X1E S7703, S7706 and S7712 chassis: supported in V200R005C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

120 W 2.92 kg (6.44 lb) 03030RFY
1000M interface card ES1D2G48TBC0 48-port 10/100/1000BASE-T interface card (BC, RJ45) BC S7703, S7706 and S7712 chassis: supported in V200R002C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

160 W 2.90 kg (6.39 lb) 03030QJT
1000M interface card ES1D2G48TX5E 48-port 100/1000BASE-T interface card (X5E, RJ45) X5E Supported in V200R013C00 and later versions 60 W 3.06 kg (6.75 lb) 03032WSM
1000M interface card ES1D2G48TX5H 48-port 100/1000BASE-T interface card (X5H, RJ45) X5H Supported in V200R013C00 and later versions 107 W 3.3 kg (7.28 lb) 03032YLY
1000M interface card ES1D2G48TX5L 48-port 100/1000BASE-T interface card (X5L, RJ45) X5L Supported in V200R013C00 and later versions 60 W 3.06 kg (6.75 lb) 03033ANW
1000M interface card ES1D2G48TX5S 48-port 100/1000BASE-T interface card (X5S, RJ45) X5S Supported in V200R013C00 and later versions 60 W 3.06 kg (6.75 lb) 03032WSF
1000M interface card ES1M2G48TX5E 48-port 10/100/1000BASE-T interface card (X5E, RJ45) X5E S7703 chassis: Supported in V200R013C01 and later versions

S7703 PoE, S7706, S7706 PoE, and S7712 chassis: not supported

66 W 3.27 kg (7.21 lb) 03032YFJ
1000M interface card ES1M2G48TX5S 48-port 10/100/1000BASE-T interface card (X5S, RJ45) X5S S7703 chassis: Supported in V200R013C01 and later versions

S7703 PoE, S7706, S7706 PoE, and S7712 chassis: not supported

66 W 3.27 kg (7.21 lb) 03033AGB
1000M interface card ES0D0G48SA00 48-port 100/1000BASE-X interface card (EA, SFP) EA S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

75 W 2.54 kg (5.60 lb) 03030MHB
1000M interface card ES0D0G48SC00 48-port 100/1000BASE-X interface card (EC, SFP) EC S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

92 W 2.66 kg (5.86 lb) 03030MQK
1000M interface card ES1D2G48SED0 48-port 100M/1000M BASE-X interface card (ED, SFP) ED S7703, S7706 and S7712 chassis: supported in V200R001C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

110 W 2.66 kg (5.86 lb) 03030PGN
1000M interface card ES1D2G48SFA0 48-port 100/1000BASE-X interface card (FA, SFP) FA S7703, S7706 and S7712 chassis: supported in V200R001C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

65 W 2.60 kg (5.73 lb) 03030PGM
1000M interface card ES1D2G48SBC0 48-port 100/1000BASE-X interface card (BC, SFP) BC S7703, S7706 and S7712 chassis: supported in V200R002C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

185 W 2.90 kg (6.39 lb) 03030QJS
1000M interface card ES1D2G48SX1E 48-port 100/1000BASE-X interface card (X1E, SFP) X1E S7703, S7706 and S7712 chassis: supported in V200R005C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

140 W 3.04 kg (6.70 lb) 03030RHB
1000M interface card ES1D2G48SX5E 48-Port 100/1000BASE-X Interface Card (X5E, SFP) X5E Supported in V200R013C00 and later versions 110 W 3.1 kg (6.83 lb) 03032WSV
1000M interface card ES1D2G48SX5H 48-Port 100/1000BASE-X Interface Card (X5H, SFP) X5H Supported in V200R013C00 and later versions 162 W 3.3 kg (7.28 lb) 03032YMA
1000M interface card ES1D2G48SX5L 48-Port 100/1000BASE-X Interface Card (X5L, SFP) X5L Supported in V200R013C00 and later versions 110 W 3.1 kg (6.83 lb) 03033ANX
1000M interface card ES1D2G48SX5S 48-Port 100/1000BASE-X Interface Card (X5S, SFP) X5S Supported in V200R013C00 and later versions 110 W 3.1 kg (6.83 lb) 03032WSR

GE/10GE interface card

ES0D0T24XA00 24-port 10/100/1000BASE-T and 2-port 10GBASE-X interface card (EA, RJ45/XFP) EA S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

53 W 2.30 kg (5.07 lb) 03030LMU
GE/10GE interface card ES0D0S24XA00 24-port 100/1000BASE-X and 2-port 10GBASE-X interface card (EA, SFP/XFP) EA S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

65 W 2.40 kg (5.26 lb) 03030KAR
GE/10GE interface card ES1D2S24XEC0 24-port 100/1000BASE-X and 2-port 10GBASE-X interface card (EC, SFP/XFP) EC S7703, S7706 and S7712 chassis: supported in V200R002C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

81 W 2.50 kg (5.51 lb) 03030QJU
GE/10GE interface card ES1D2S04SX1E 4-port 10GBASE-X and 24-port 100/1000BASE-X and 8-port 10/100/1000BASE-T combo interface card (X1E, RJ45/SFP/SFP+) X1E S7703, S7706 and S7712 chassis: supported in V200R005C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

130 W 2.88 kg (6.35 lb) 03030RGX
GE/10GE interface card ES1D2S04SX5E 4-port 10GE SFP+ and 44-port GE SFP interface card (X5E, SFP+) X5E Supported in V200R013C00 and later versions 124 W 3.1 kg (6.83 lb) 03032WTB
GE/10GE interface card ES1D2S08SX1E 8-port 10GBASE-X and 8-port 100/1000BASE-X and 8-port 10/100/1000BASE-T combo interface card (X1E, RJ45/SFP/SFP+) X1E S7703, S7706 and S7712 chassis: supported in V200R005C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

130 W 2.84 kg (6.26 lb) 03030RFX
GE/10GE interface card ES1D2S24SX2E 24-Port 10GE SFP+ Interface and 8-Port GE SFP Interface Card (X2E, SFP+) X2E S7703, S7706, and S7712 chassis: supported in V200R010C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

201.8 W 3.3 kg (7.28 lb) 03031YFJ
GE/10GE interface card ES1D2S24SX2S 24-Port 10GE SFP+ Interface and 8-Port GE SFP Interface Card (X2S, SFP+) X2S S7703, S7706, and S7712 chassis: supported in V200R010C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

192.3 W 3.2 kg (7.05 lb) 03031YFH
GE/10GE interface card ES1D2S16SX2E 16-Port 10GE SFP+ Interface and 16-Port GE SFP Interface Card (X2E, SFP+) X2E S7703, S7706, and S7712 chassis: supported in V200R010C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

192.4 W 3.3 kg (7.28 lb) 03031YFL
GE/10GE interface card ES1D2S16SX2S 16-Port 10GE SFP+ Interface and 16-Port GE SFP Interface Card (X2S, SFP+) X2S S7703, S7706, and S7712 chassis: supported in V200R010C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

182.4 W 3.2 kg (7.05 lb) 03031YFK

10GE interface card

ES0D0X2UXA00 2-port 10GBASE-X interface card (EA, XFP) EA S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

52 W 2.14 kg (4.72 lb) 03030LWF
10GE interface card ES0D0X2UXC00 2-port 10GBASE-X interface card (EC, XFP) EC S7703, S7706 and S7712 Chassis: Supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

61 W 2.26 kg (4.98 lb) 03030LKV
10GE interface card ES1D2X02XEC1 2-port 10GBASE-X interface card (EC, XFP), FCC EC S7703, S7706 and S7712 chassis: supported in V200R003C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

61 W 2.26 kg (4.98 lb) 03030RCV
10GE interface card ES0D0X4UXA00 4-port 10GBASE-X interface card (EA, XFP) EA S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

64 W 2.16 kg (4.76 lb) 03030KSM
10GE interface card ES0D0X4UXC00 4-port 10GBASE-X interface card (EC, XFP) EC S7703, S7706 and S7712 chassis: supported in V100R003C01 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

75 W 2.28 kg (5.03 lb) 03030KAP
10GE interface card ES1D2X04XEC1 4-port 10GBASE-X interface card (EC, XFP), FCC EC S7703, S7706 and S7712 chassis: supported in V200R003C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

75 W 2.28 kg (5.03 lb) 03030RCX
10GE interface card ES1D2X04XED0 4-port 10GBASE-X interface card (ED, XFP) ED S7703, S7706 and S7712 chassis: supported in V200R001C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

93 W 2.30 kg (5.07 lb) 03030PGL
10GE interface card ES1D2X08SED4 8-port 10GBASE-X interface card (ED, SFP+) ED S7703, S7706 and S7712 Chassis: Supported in V200R002C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

198.1 W 2.50 kg (5.51 lb) 03030PQB
10GE interface card ES1D2X08SED5 8-port 10GBASE-X interface card (ED, SFP+) ED S7703, S7706 and S7712 chassis: supported in V200R002C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

198.1 W 2.50 kg (5.51 lb) 03030PQD
10GE interface card ES1D2X08SX5E 8-Port 10GBASE-X Interface Card (X5E, SFP+) X5E Supported in V200R013C00 and later versions 78 W 2.7 kg (5.95 lb) 03032WTG
10GE interface card ES1D2X08SX5H 8-Port 10GBASE-X Interface Card (X5H, SFP+) X5H Supported in V200R013C00 and later versions 130 W 2.94 kg (6.48 lb) 03032YMG
10GE interface card ES1D2X08SX5L 8-Port 10GBASE-X Interface Card (X5L, SFP+) X5L Supported in V200R013C00 and later versions 78 W 2.7 kg (5.95 lb) 03032WTE
10GE interface card ES0D0X12SA00 12-port 10GBASE-X interface card (SA, SFP+) SA S7703, S7706 and S7712 chassis: supported in V100R006C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

85 W 2.30 kg (5.07 lb) 03030NFY
10GE interface card ES1D2X16SFC0 16-port 10GBASE-X interface card (FC, SFP+) FC S7703, S7706 and S7712 chassis: supported in V200R001C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

150 W 2.60 kg (5.73 lb) 03030PGP
10GE interface card ES1D2X16SSC2 16-port 10GBASE-X interface card (SC, SFP+) SC S7703, S7706 and S7712 chassis: supported in V200R008C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

131 W 2.80 kg (6.17 lb) 03031HGQ
10GE interface card ES1D2X32SSC0 32-port 10GBASE-X interface card (SC, SFP+) SC S7703, S7706 and S7712 chassis: supported in V200R008C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

207 W 3.02 kg (6.66 lb) 03031FSQ
10GE interface card ES1D2X32SX2E 32-Port 10GBASE-X Interface Card (X2E, SFP+) X2E S7703, S7706, and S7712 chassis: supported in V200R010C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

213.7 W 3.3 kg (7.28 lb) 03031WHU
10GE interface card ES1D2X32SX2S 32-Port 10GBASE-X Interface Card (X2S, SFP+) X2S S7703, S7706, and S7712 chassis: supported in V200R010C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

203.3 W 3.2 kg (7.05 lb) 03031YFG
10GE interface card ES1D2X40SFC0 40-port 10GBASE-X interface card (FC, SFP+) FC S7703, S7706 and S7712 Chassis: Supported in V200R001C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

183 W 2.90 kg (6.39 lb) 03030PGQ
10GE interface card ES1D2X48SX2S 48-Port 10GBASE-X Interface Card (X2S, SFP+) X2S S7703, S7706, and S7712 chassis: supported in V200R010C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

258.1 W 3.4 kg (7.50 lb) 03031WHX

40GE interface card

ES1D2L02QFC0 2-port 40GBASE-X interface card (FC, QSFP+) FC S7703, S7706 and S7712 chassis: supported in V200R002C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

88 W 2.50 kg (5.51 lb) 03030PFQ
40GE interface card ES1D2L08QX2E 8-Port 40GBASE-X Interface Card (X2E, QSFP+) X2E S7703, S7706, and S7712 chassis: supported in V200R010C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

178.4 W 3.0 kg (6.61 lb) 03031WJD
40GE/100GE interface card ES1D2H02QX2S 2-Port 100GE QSFP28 Interface and 2-Port 40GE QSFP+ Interface Card (X2S, QSFP28) X2S S7703, S7706, and S7712 chassis: supported in V200R010C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

143.5 W 3.05 kg (6.72 lb) 03031YFE
40GE/100GE interface card ES1D2H02QX2E 2-Port 100GE QSFP28 Interface and 2-Port 40GE QSFP+ Interface Card (X2E, QSFP28) X2E S7703, S7706, and S7712 chassis: supported in V200R010C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

153.1 W 3.15 kg (6.94 lb) 03031YFF
100GE interface card ES1D2C02FEE0 2-port 100GBASE-X interface card (EE, CFP) EE S7703, S7706 and S7712 chassis: supported in V200R008C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

339 W 4.20 kg (9.26 lb) 03030XJN
100GE interface card ES1D2C04HX2E 4-Port 100GE QSFP28 Interface Card (X2E, QSFP28) X2E S7703, S7706, and S7712 chassis: supported in V200R010C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

164.8 W 3.15 kg (6.94 lb) 03031YFD
100GE interface card ES1D2C04HX2S 4-Port 100GE QSFP28 Interface Card (X2S, QSFP28) X2S S7703, S7706, and S7712 chassis: supported in V200R010C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

154.7 W 3.05 kg (6.72 lb) 03031YEQ
ACU2 module ACU2 WLAN ACU2 Access Controller Unit (128 AP Control Resource Included)

NOTE:

For details, see manuals of the ACU2 card.

S7703, S7706 and S7712 chassis: supported in V200R005C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

Firewall module ET1D2FW00S00 NGFW module A, with HW general security platform software

NOTE:

For details, see manuals of the NGFW card.

S7703, S7706 and S7712 chassis: supported in V200R005C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

Firewall module ET1D2FW00S01 NGFW module B, with HW general security platform software

NOTE:

For details, see manuals of the NGFW card.

S7703, S7706 and S7712 chassis: supported in V200R005C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

Firewall module ET1D2FW00S02 NGFW Module C, with HW General Security Platform Software

NOTE:

For details, see manuals of the NGFW card.

S7703, S7706 and S7712 chassis: supported in V200R005C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

IPS module ET1D2IPS0S00 IPS module A, with HW general security platform software

NOTE:

For details, see manuals of the IPS card.

S7703, S7706 and S7712 chassis: supported in V200R005C00 and later versions

S7703 PoE and S7706 PoE chassis: supported in V200R013C00 and later versions

About Us

As a world leading Huawei networking products supplier, Hong Telecom Equipment Service LTD(HongTelecom) keeps regular stock of Huawei router and switch and all cards at very good price, also HongTelecom ship to worldwide with very fast delivery.

For related articles, visit the HongTelecom Blog and HongTelecom WordPress.
For real pictures of related product, visit the HongTelecom Gallery.
To buy related product, visit the HongTelecom Online Shop.

何诗名片

EH1M00FBX000 Fan Module for Huawei S7700&S9700 Series

Huawei Campus Switch includes S1700, S2300, S2700, S3300, S3700, S5300, S5700, S600-E, S6300, S6700, S7700, S7900, S9300, S9300X, S9700, S12700 Series. In this article, HongTelecom will introduce the EH1M00FBX000 Fan Module for Huawei S7700&S9700 Series.

EH1M00FBX000 Fan Module

A fan module reports an alarm when a fan in it fails. When receiving such an alarm, fix the fault immediately to ensure effective cooling for the chassis.

Version Mapping

A fan module can be installed in:

  • Slot FAN1 in an S9703 chassis.
  • Slots FAN1 and FAN2 in an S9706 chassis.
  • Slots FAN1 to FAN4 in an S9712 chassis.
  • Slot FAN1 in an S7703 PoE chassis.
  • Slots FAN1 and FAN2 in an S7706 PoE chassis.

Table 1 Switch chassis and software versions matching a fan module
Model Name S9700
EH1M00FBX000 Wide-voltage 74 fan box Supported in V200R001C00 and later versions

Table 2 Switch chassis and software versions matching a fan module
Model Name S7703 PoE&S7706 PoE
EH1M00FBX000 Wide-voltage 74 fan box Supported in V200R013C00 and later versions

Appearance

Figure 1 Fan module
Figure 1 Fan module_S7700

Functions

Table 3 Functions of fan modules
Function Description
Hot swapping Supported

Other fan modules are not affected when you install or remove a fan module.

Automatic fan speed adjustment The switch provides intelligent fan speed adjustment based on temperature in each zone. The system monitors the temperature of key components, and adjusts the fan speed based on temperature changes. This intelligent fan speed adjustment function ensures that the system stays within the proper operating temperature range, and reduces power consumption and noise.

A fan module has two fans, and a failure of a fan does not immediately affect system operations. When any fan in a fan module fails, fix the fan module as soon as possible.

Panel Description

Figure 2 Fan module panel
Figure 2 Fan module panel_S7700
1. Air vent 2. Captive screw 3. Fan status indicator 4. Handle

Table 4 Indicators on a fan module panel
Indicator Color Description
RUN/ALM Green Slow blinking: The fan module is working properly, and the communication is normal.

Fast blinking: The fan module is working properly, but communication has not been established.

Red Slow blinking: An alarm was generated. You must determine whether to replace the fan module, depending on the actual situation.

Steady on: The fan module has a hardware failure and needs to be replaced.

Specifications

Table 5 Technical specifications of a fan module
Item Value
Dimensions (W x D x H) 323.9 mm x 74.8 mm x 126.6 mm (12.8 in. x 2.9 in. x 5.0 in.)
Number of fans 2
Weight 1540±20 g
Maximum power consumption 116 W
Maximum wind pressure 692 Pa
Maximum wind rate 245 CFM
Maximum noise 70 dB(A)
Operating voltage range -30 V DC to -73 V DC
Environment specifications
  • Operating temperature: 0°C to 45°C (32°F to 113°F)
  • Operating relative humidity: 5% RH to 95% RH (noncondensing)
  • Storage temperature: -40°C to +70°C (-40°F to +158°F)
  • Storage relative humidity: 5% RH to 95% RH (noncondensing)
Part number 02120666

About Us

As a world leading Huawei networking products supplier, Hong Telecom Equipment Service LTD(HongTelecom) keeps regular stock of Huawei router and switch and all cards at very good price, also HongTelecom ship to worldwide with very fast delivery.

For related articles, visit the HongTelecom Blog and HongTelecom WordPress.
For real pictures of related product, visit the HongTelecom Gallery.
To buy related product, visit the HongTelecom Online Shop.

何诗名片

ES1M00FBX001 Fan Module for Huawei S7703&S7706&S7712

Huawei Campus Switch includes S1700, S2300, S2700, S3300, S3700, S5300, S5700, S600-E, S6300, S6700, S7700, S7900, S9300, S9300X, S9700, S12700 Series. In this article, HongTelecom will introduce the ES1M00FBX001 Fan Module for Huawei S7703&S7706&S7712.

ES1M00FBX001 Fan Module

A fan module reports an alarm when a fan in it fails. When receiving such an alarm, fix the fault immediately to ensure effective cooling for the chassis.

Version Mapping

A fan module can be installed in:

  • Slot FAN1 in an S7703 chassis.
  • Slots FAN1 and FAN2 in an S7706 chassis.
  • Slots FAN1 to FAN4 in an S7712 chassis.
NOTE:

The ES1M00FBX001 fan module can only be installed in an FCC-certified S7700 chassis.

Table 1 Switch chassis and software versions matching a fan module
Model Name S7703&S7706&S7712
ES1M00FBX001 Enhancement wide-voltage 68 fan box Supported in V200R003C00 and later versions

Appearance

Figure 1 Fan module
Figure 1 Fan module_S7700

Functions

Table 2 Functions of fan modules
Function Description
Hot swapping Supported

Other fan modules are not affected when you install or remove a fan module.

Intelligent fan speed adjustment The S7703, S7706, and S7712 series switches provide intelligent fan speed adjustment based on temperature in each zone. The system monitors the temperature of key components, and adjusts the fan speed based on temperature changes. This intelligent fan speed adjustment function ensures that the system stays within the proper operating temperature range, and reduces power consumption and noise.

A fan module has two fans, and a failure of a fan does not immediately affect system operations. When any fan in a fan module fails, fix the fan module as soon as possible.

Panel Description

Figure 2 Fan module panel
Figure 2 Fan module panel_S7700
1. Air vent 2. Captive screw 3. Fan status indicator 4. Handle

Table 3 Indicators on a fan module panel
Indicator Color Description
RUN/ALM Green Slow blinking: The fan module is working properly, and the communication is normal.

Fast blinking: The fan module is working properly, but communication has not been established.

Red Slow blinking: An alarm was generated. You must determine whether to replace the fan module, depending on the actual situation.

Steady on: The fan module has a hardware failure and needs to be replaced.

Specifications

Table 4 Technical specifications of a fan module
Item Value
Dimensions (W x D x H) 323.9 mm x 74.8 mm x 126.6 mm (12.8 in. x 2.9 in. x 5.0 in.)
Number of fans 2
Weight 1140±20 g
Maximum power consumption 43 W
Maximum wind pressure 331 Pa
Maximum wind rate 163 cubic feet per minute (CFM)
Maximum noise 62 dB(A)
Operating voltage range -38.4 V DC to -72 V DC
Environment specifications
  • Operating temperature: 0°C to 45°C (32°F to 113°F)
  • Operating relative humidity: 5% RH to 95% RH (noncondensing)
  • Storage temperature: -40°C to +70°C (-40°F to +158°F)
  • Storage relative humidity: 5% RH to 95% RH (noncondensing)
Part number 02120821

About Us

As a world leading Huawei networking products supplier, Hong Telecom Equipment Service LTD(HongTelecom) keeps regular stock of Huawei router and switch and all cards at very good price, also HongTelecom ship to worldwide with very fast delivery.

For related articles, visit the HongTelecom Blog and HongTelecom WordPress.
For real pictures of related product, visit the HongTelecom Gallery.
To buy related product, visit the HongTelecom Online Shop.

何诗名片

S7703&S7706&S7712 Fan Module

Huawei Campus Switch includes S1700, S2300, S2700, S3300, S3700, S5300, S5700, S600-E, S6300, S6700, S7700, S7900, S9300, S9300X, S9700, S12700 Series. In this article, HongTelecom will introduce the S7703&S7706&S7712 Fan Module.

S7703&S7706&S7712 Fan Module

NOTICE:

A fan module reports an alarm when a fan in it fails. When receiving such an alarm, fix the fault immediately to ensure effective cooling for the chassis.

Version Mapping

A fan module can be installed in:

  • Slot FAN1 in an S7703 chassis.
  • Slots FAN1 and FAN2 in an S7706 chassis.
  • Slots FAN1 to FAN4 in an S7712 chassis.

Table 1 Switch chassis and software versions matching a fan module
MODEL NAME S7703&S7706&S7712
ES0E2FBX Wide-voltage 68 fan box Supported in V100R003C01 and later versions

Appearance

Figure 1 Fan module
Figure 1 Fan module_S7700

Functions

Table 2 Functions of fan modules
FUNCTION DESCRIPTION
Hot swapping SupportedOther fan modules are not affected when you install or remove a fan module.
Intelligent fan speed adjustment The S7703, S7706, and S7712 series switches provide intelligent fan speed adjustment based on temperature in each zone. The system monitors the temperature of key components, and adjusts the fan speed based on temperature changes. This intelligent fan speed adjustment function ensures that the system stays within the proper operating temperature range, and reduces power consumption and noise.

A fan module has two fans, and a failure of a fan does not immediately affect system operations. When any fan in a fan module fails, fix the fan module as soon as possible.

Panel Description

Figure 2 Fan module panel
Figure 2 Fan module panel_S7700
1. Air vent 2. Captive screw 3. Fan status indicator 4. Handle

Table 3 Indicators on a fan module panel
INDICATOR COLOR DESCRIPTION
RUN/ALM Green Slow blinking: The fan module is working properly, and the communication is normal.Fast blinking: The fan module is working properly, but communication has not been established.
Red Slow blinking: An alarm was generated. You must determine whether to replace the fan module, depending on the actual situation.Steady on: The fan module has a hardware failure and needs to be replaced.

Specifications

Table 4 Technical specifications of a fan module
ITEM VALUE
Dimensions (W x D x H) 323.9 mm x 74.8 mm x 126.6 mm (12.8 in. x 2.9 in. x 5.0 in.)
Number of fans 2
Weight 1140±20 g
Maximum power consumption 43 W
Maximum wind pressure 331 Pa
Maximum wind rate 163 cubic feet per minute (CFM)
Maximum noise 62 dBA
Operating voltage range -38.4 V DC to -72 V DC
Environment specifications
  • Operating temperature: 0°C to 45°C (32°F to 113°F)
  • Operating relative humidity: 5% RH to 95% RH (noncondensing)
  • Storage temperature: -40°C to +70°C (-40°F to +158°F)
  • Storage relative humidity: 5% RH to 95% RH (noncondensing)
Part number 02120760

About Us

As a world leading Huawei networking products supplier, Hong Telecom Equipment Service LTD(HongTelecom) keeps regular stock of Huawei router and switch and all cards at very good price, also HongTelecom ship to worldwide with very fast delivery.

For related articles, visit the HongTelecom Blog and HongTelecom WordPress.
For real pictures of related product, visit the HongTelecom Gallery.
To buy related product, visit the HongTelecom Online Shop.

何诗名片