No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

S12700 Series Agile Switches Typical Configuration Examples

This document provides examples for configuring features in typical usage scenarios.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
SVF System Planning

SVF System Planning

Planning SVF System Networking

An SVF system supports at most two levels of ASs and one level of APs. Before setting up an SVF system, determine the SVF application scenario and select the required networking based on deployment restrictions, reliability, and system CPU consumption.

Determining Campus Network Scenarios

When determining campus network scenarios, consider factors such as the terminal quantity, terminal type, whether to reuse existing devices, and CPU/memory capabilities of the parent.

  1. Calculate the number of required ASs based on the number of wired terminals.
  2. Calculate the number of required APs based on the number of wireless terminals.
  3. Determine whether to reuse existing devices. These devices can be reused to transparent transmit packets between the parent and ASs. It is not recommended to connect users to these existing devices, as doing so may cause a failure to set up an SVF system.
  4. An SVF system is configured and maintained on the parent. If more ASs&APs are deployed, more terminals can connect to the campus network, requiring more CPU and memory resources of the parent. Table 5-5 lists the recommended maximum numbers of ASs&APs and access terminals in an SVF system depending on CPU and memory capabilities of the parent. If the number of access terminals exceeds the recommended value, you are advised to divide the campus network into multiple SVF systems according to Scenario 3: Campus Network of Multiple SVF Systems.

    Table 5-5  Recommended maximum numbers of ASs&APs and access terminals

    Model of the Parent

    Recommended Maximum Number of ASs

    Recommended Maximum Number of APs

    S12712/S12710/S12708/S12704

    256

    1000

  5. Select the required networking scenario. Table 5-6 lists the recommended scenarios.
    Table 5-6  Recommended networking scenarios
    Number of Terminals

    Terminal Type

    Recommended Networking Scenario

    The number of terminals does not exceed the recommended value on the parent.

    Only wired terminals exist, and no existing devices need to be reused.

    Scenario 1: Networking in which the parent and ASs are directly connected on a wired campus network

    Only wired terminals exist, and existing devices need to be reused.

    Scenario 1: Networking in which the parent and ASs are connected across an intermediate network on a wired campus network

    Both wired and wireless terminals exist, and no existing devices need to be reused.

    Scenario 2: Networking in which the parent and ASs&APs are directly connected on a wired and wireless converged campus network

    Both wired and wireless terminals exist, and existing devices need to be reused.

    Scenario 2: Networking in which the parent and ASs&APs are connected across an intermediate network on a wired and wireless converged campus network

    The number of terminals exceeds the recommended value on the parent. During system planning, you are advised to divide the campus network into multiple SVF systems. Scenario 3: Campus Network of Multiple SVF Systems shows networking scenarios. In each SVF system, ensure that the number of terminals does not exceed the recommended value on the parent, and select the recommended scenario according to the terminal type.
Networking deployment recommendations
Figure 5-21  Ideal SVF networking

Figure 5-21 shows an ideal SVF networking. It has the following characteristics:

  1. The parent is a CSS of two member devices.
  2. Each Level-1 AS is dual-homed to two member devices of the parent through uplink ports.
  3. When an AS is a stack of multiple member devices, each member device is connected to its upstream device through at least one link.
  4. An AS is connected to upstream devices through uplink optical ports or combo ports.
  5. An AP is single-homed to an AS.

This SVF networking has the following advantages:

  1. Failure of a single link between two devices affects only the bandwidth but not services.
  2. An AS performs multi-active detection (MAD), and its upstream device functions as the MAD relay agent. When the AS splits as a stack, it can work with the upstream device to perform MAD without affecting the system stability.

Implementing the ideal SVF networking may fail because of restrictions such as the distance between devices and cabling difficulties. You need to identify these networking restrictions in advance and take appropriate measures. The following provides suggestions on SVF deployment in different situations:

  1. If the parent is a standalone device:
    1. Deploy two MPUs on the parent to ensure reliability.
    2. Connect each AS to the parent using at least two links and ensure that the links are connected to at least two different LPUs of the parent.
  2. If a level-1 AS cannot be dual-homed to the parent:
    • Use a standalone device at this AS node. If the AS needs to be a stack, deploy member devices in the same physical location and ensure stack cable reliability. Otherwise, device conflicts cannot be resolved after the stack splits, affecting system reliability.
  3. If the AS is a stack of multiple member devices and you cannot ensure that each member device connects to its upstream device through at least one link:
    • Deploy member devices in the same physical location and ensure stack cable reliability. Otherwise, device conflicts cannot be resolved after the stack splits, affecting system reliability.
  4. If member ports of the fabric port that connects an AS to an upstream device can only be connected through twisted pairs:
    • Use copper modules to convert the optical/electrical attributes of ports when uplink ports of ASs are GE ports.
    • Select ASs that have uplink combo ports, for example, some S2750EI models.
Improving System Reliability
  1. Improve reliability of the parent using the following methods:
    1. Set up a CSS of two member devices for the parent.
    2. Deploy MAD to take recovery actions when the CSS splits.
  2. Improve reliability of an AS using the following methods:
    1. If the parent is a CSS of two member devices, dual-home the level-1 AS to two member devices of the parent.
    2. If the AS is a stack of multiple member devices, ensure that each member device is connected to its upstream device through at least one link.
    3. If the AS is a stack of multiple member devices, set up the stack in ring topology.
    4. If the AS is a stack of multiple member devices, deploy all the member devices in the same physical location to reduce the risk of a stack split caused by link failures.

Planning Member Devices of an SVF System

After determining networking of an SVF system, you need to select member devices for the SVF system.

Determining the Parent
  1. Determine the parent device type.

    The parent device type is determined by the campus network scale. For details, see Determining Campus Network Scenarios.

  2. Determine the number of devices for the parent.

    The parent manages and maintains the entire SVF system. You are advised to deploy a CSS of two modular switches as the parent to ensure reliability of the SVF system.

  3. Determine the card type on the parent.
    1. In a wired and wireless convergence scenario, you need to deploy X series cards on the parent.
    2. If an AS needs to connect to two LPUs of the parent, you are advised to connect the AS to LPUs of the same type.
    3. If the campus network provides only wired access and does not require access authentication, you do not need to deploy X series cards on the parent. If access terminals need to be authenticated, you are advised to deploy X series cards on the parent because X series cards support a large number of user entries and allow more flexible access control policies.
    4. You need to use optical interface cards to connect the parent to ASs because uplink ports of most AS types are optical ports. If an AS uses a 10GE optical port to connect to a GE port of the parent, the 10GE optical port must be able to switch to the GE mode through auto sensing.
    5. If the parent connects to ASs only through twisted pairs, you are advised to use ASs with uplink combo ports to connect to the electrical cards of the parent. Otherwise, you need to use copper modules to ensure the connectivity between ASs and the parent.
Determining ASs

Select level-1 and level-2 ASs according to the following requirements:

  1. ASs can connect to the parent only through uplink ports, and uplink ports of most ASs are optical ports. Therefore, when an SVF system has two levels of ASs, use ASs with downlink optical ports as level-1 ASs. Otherwise, you need to use copper modules to ensure the connectivity between level-1 and level-2 ASs.
  2. When services in an SVF system are similar, use ASs of the same type so that faulty ASs can be replaced.
Select ASs according to hardware characteristics and the following tables to meet different networking requirements.
Table 5-7  Recommended AS types in different networking modes

Networking

Device Positioning

Recommended Device Type

Two levels of ASs exist, and level-1 ASs are directly connected to the parent

Level-1 AS

  • S6720EI, S6720S-EI, S6720SI, S6720S-SI, S5730HI, S5720EI with downlink optical ports
  • S6320EI, S6320SI, S5330HI, S5320EI with downlink optical ports

Level-2 AS

  • S6720LI, S6720S-LI, S6720SI, S6720S-SI, S5700LI with uplink GE optical ports, S5700S-LI, S5730SI, S5730S-EI, S5720LI, S5720S-LI, S2750EI, S2720EI, S5720SI, S5720S-SI, S5720I-SI, S5710-X-LI, S600-E
  • S6320SI, S5330SI, S5320LI, S5320SI, S5320EI with downlink optical ports, S2320EI

ASs are directly connected to the parent

AS

  • S6720LI, S6720S-LI, S6720SI, S6720S-SI, S6720EI, S6720S-EI, S5720EI, S5700LI, S5700S-LI, S5730HI, S5730SI, S5730S-EI, S5720LI, S5720S-LI, S2750EI, S2720EI, S5720SI, S5720S-SI, S5720I-SI, S5710-X-LI, S600-E
  • S6320EI, S6320SI, S5330HI, S5330SI, S5320LI, S5320SI, S5320EI, S2320EI

ASs are connected to the parent across an intermediate network

AS

  • S6720LI, S6720S-LI, S6720SI, S6720S-SI, S6720EI, S6720S-EI, S5720EI, S5700LI, S5700S-LI, S5730HI, S5730SI, S5730S-EI, S5720LI, S5720S-LI, S2750EI, S2720EI, S5720SI, S5720S-SI, S5720I-SI, S5710-X-LI, S600-E
  • S6320EI, S6320SI, S5330HI, S5330SI, S5320LI, S5320SI, S5320EI, S2320EI

Devices that do not join the SVF system (intermediate network devices)

Devices with downlink optical ports and supporting Eth-Trunk

Determining APs

You need to select APs that are supported by the parent. First, use the following methods to check whether the AP types are supported by the parent:

  • (Recommended) Run the display ap-type all command on the parent to check the AP types currently supported.
  • Check the version mapping of the device model for the parent to check the AP types supported by the parent.
Download
Updated: 2019-05-16

Document ID: EDOC1000069466

Views: 183156

Downloads: 1836

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next