Information to Know Before SVF Deployment

• SVF Technical Characteristics
  
• Application Scenarios for SVF
  
• SVF Service Deployment Limitations
  

SVF Technical Characteristics

A traditional campus network has the following characteristics:

• Core and aggregation devices have fixed services.

• Access devices are widely distributed.

• Access devices use simple, similar service configurations.

• Access devices have many ports.

• The trend towards wired and wireless convergence grows for access devices.

Management and configuration of access devices are time-consuming due to the preceding characteristics. Super Virtual Fabric (SVF) technology effectively simplifies management and configuration of access devices.Figure 4-32  SVF networking diagram 

As shown in Figure 4-32, SVF simplifies campus network management and maintenance. According to characteristics of campus networks, SVF technology allows you to configure and maintain access devices as well as manage access users in a uniform manner.

In an SVF system, a parent manages and configures the SVF system. Client refers to all access devices, including wired access devices (ASs) and wireless access devices (APs).

SVF has the following technical characteristics:

• Manages wired and wireless users on the parent in a uniform manner.
• Configures services of access switches (ASs) through the parent. For the configurable services and service configuration modes, see SVF Service Deployment Limitations.
• Maintains the status of ASs and access points (APs) through the parent, including device registration status and heartbeat, version and patch status, important alarms, port status, and user status of all ASs and APs.
• Supports at most two levels of ASs (level-1 and level-2 ASs) and one level of APs. When eSight is used to manage the SVF system, SVF can better simplify device management.

The following table lists SVF hardware and software requirements.

Select APs whose type and version are supported by the parent, and see the version mapping of the device model for the parent to determine which APs the parent supports.Table 4-28  Supported parent and AS switch models

Application Scenarios for SVF

Based on SVF technical characteristics, the parent must be connected to ASs and APs across a Layer 2 network and ASs must be deployed at the access layer of a campus network and directly connected to users. ASs cannot be used as aggregation devices. In versions earlier than V200R011C10, user-side ports of ASs cannot be added to an Eth-Trunk. In V200R011C10 or later versions, user-side ports of ASs can be added to an Eth-Trunk. Due to these limitations, SVF applies to the following scenarios. If your network does not meet the following SVF networking requirements, SVF cannot be deployed on your network. You are advised to log in to each device to configure services.

Scenario 1: Wired Campus Network Access

In a wired campus network access scenario, all user terminals access a campus network through wired links. In such a scenario, user terminals are directly connected to ASs, and the parent functions as the access gateway of users. SVF supports two types of networking, depending on whether the parent and ASs are directly connected or connected across an intermediate network:

• Networking in which the parent and ASs are directly connected, as shown in Figure 4-33
  1. The parent can be a standalone device, a cluster switch system (CSS) of two modular devices, or a stack of multiple member devices.
  2. At most two levels of ASs are supported in an SVF system. Each AS can be a standalone device or a stack of multiple member devices. In V200R008C00 and earlier versions, each AS can be a stack of up to three member devices that are the same model and provide the same number of ports. From V200R009C00, each AS can be a stack of up to five member devices that are the same model and provide the same number or different numbers of ports.
  3. User terminals can access the network through level-1 or level-2 ASs. The parent functions as the access gateway of users.
  If a new campus network is built with unconfigured devices, this networking is recommended.Figure 4-33  Networking in which the parent and ASs are directly connected on a wired campus network 
  
• Networking in which the parent and ASs are connected across an intermediate network, as shown in Figure 4-34
  1. The parent can be a standalone device, a cluster switch system (CSS) of two modular devices, or a stack of multiple member devices.
  2. An SVF system supports at most one level of ASs. Each AS can be a standalone device or a stack of multiple member devices. In V200R008C00 and earlier versions, each AS can be a stack of up to three member devices that are the same model and provide the same number of ports. From V200R009C00, each AS can be a stack of up to five member devices that are the same model and provide the same number or different numbers of ports.
  3. User terminals can access the network through ASs. The parent functions as the access gateway of users.
  If a campus network is reconstructed and devices of different vendors are deployed on the campus network, this networking is recommended.Figure 4-34  Networking in which the parent and ASs are connected across an intermediate network on a wired campus network 
  

Scenario 2: Wired and Wireless Converged Campus Network Access

On a wired and wireless converged campus network, some user terminals access the network wiredly, while others access the network wirelessly. In the scenario, the parent functions as the access gateway of users. SVF supports two types of networking, depending on whether the parent and ASs&APs are connected across an intermediate network:

• Networking in which the parent and ASs&APs are directly connected, as shown in Figure 4-35
  1. The parent can be a standalone device, a cluster switch system (CSS) of two modular devices, or a stack of multiple member devices.
  2. An SVF system supports at most two levels of ASs (level-1 and level-2 ASs). Each AS can be a standalone device or a stack of multiple member devices. In V200R008C00 and earlier versions, each AS can be a stack of up to three member devices that are the same model and provide the same number of ports. From V200R009C00, each AS can be a stack of up to five member devices that are the same model and provide the same number or different numbers of ports.
  3. APs can be connected to level-1 or level-2 ASs.
  4. Wired user terminals access the network through level-1 or level-2 ASs. Wireless user terminals access the network through APs. The parent functions as the access gateway of users.
  If a new campus network is built with unconfigured devices, this networking is recommended.Figure 4-35  Networking in which the parent and ASs&APs are directly connected on a wired and wireless converged campus network 
  
• Networking in which the parent and ASs&APs are connected across an intermediate network, as shown in Figure 4-36
  1. The parent can be a standalone device, a cluster switch system (CSS) of two modular devices, or a stack of multiple member devices.
  2. An SVF system supports at most one level of ASs. Each AS can be a standalone device or a stack of multiple member devices. In V200R008C00 and earlier versions, each AS can be a stack of up to three member devices that are the same model and provide the same number of ports. From V200R009C00, each AS can be a stack of up to five member devices that are the same model and provide the same number or different numbers of ports.
  3. APs are connected to ASs.
  4. Wired user terminals access the network through ASs. Wireless user terminals access the network through APs. The parent functions as the access gateway of users.
  If a campus network is reconstructed and devices of different vendors are deployed on the campus network, this networking is recommended.Figure 4-36  Networking in which the parent and ASs&APs are connected across an intermediate network on a wired and wireless converged campus network 
  

Scenario 3: Campus Network of Multiple SVF Systems

On a campus network with more than 200 access devices, you can set up multiple SVF systems to simplify campus network management, as shown in Figure 4-37.Figure 4-37  Campus network of multiple SVF systems 

SVF Service Deployment Limitations

SVF supports two service configuration modes: centralized mode and independent mode.

• In centralized mode, all service configurations for ASs are performed on the parent. Therefore, the services that can be configured on ASs depend on the services that can be configured on the parent, but not on the services supported by a standalone access switch. AS-supported services apply to most access switches.

  In centralized mode, you can deliver service configurations to multiple ASs using profiles or global batch configuration or configure a single AS directly.

• Since V200R010C00, in independent mode, you can log in to an AS to configure it using commands.

  The independent mode supports more service configurations than the centralized mode. When services cannot be batch configured on the parent for an AS, log in to the AS to configure it independently. After the AS changes from the centralized mode to independent mode, the configuration file generated using profiles or directly configured before the mode switchover will be retained.

The following describes the configurable functions in different service configuration modes.

Centralized Mode (Batch Configuration: Functions Globally Delivered)

Centralized Mode (Batch Configuration: Functions Delivered Using Profiles)

Centralized Mode (Single Configuration: Functions Delivered Using the direct-command Command)

 NOTE:

The interface view cannot be the Eth-Trunk interface view.

Centralized Mode (Configurable Commands After Logins to ASs Using the attach-as Command or Console Port)

Commands that can be configured after you log in to an AS in centralized configuration mode are mainly used for fault diagnosis.

• In the user view and diagnostic view, all commands are supported except the commands listed in Table 4-29. Additionally, in V200R009 and earlier versions, the diagnostic view can be displayed only after the diagnose-command command is executed in the user view.

  Table 4-29  Commands not supported in the user view and diagnostic view of ASs

  Command	View
  configuration copy file file-name to running	User view
  configuration copy startup to file file-name	User view
  configuration exclusive	User view
  format drive	User view
  lldp clear neighbor [ interface interface-type interface-number ]	User view
  local-user change-password	User view
  lock	User view
  startup patch patch-name [ slave-board | slot slot-id ]	User view
  startup saved-configuration configuration-file [ slot slot-id ]	User view
  startup system-software system-file [ all | slave-board | slot slot-id ]	User view
  save [ all ] [ configuration-file ]	User view
  save logfile [ all ]	User view
  reboot [ fast | save diagnostic-information ]	User view
  schedule reboot { at time | delay interval [ force ] }	User view
  rollback	User view
  cli enable-config	Diagnostic view
  configuration datasync start script-file script-file { result-file result-file }	Diagnostic view
  test-device port loopback slot { slot-id | interface { interface-typeinterface-number1 [ to interface-type interface-number2 ] } &<1-10> }	Diagnostic view
  stack enable undo stack enable	Diagnostic view
  undo startup system-software	Diagnostic view

• Commands that are supported in other views are used for service diagnosis and fault location. In V200R009 and earlier versions, the uni-mng diag-mode enable command must be executed first to enable the diagnostic mode.

  Table 4-30  Commands supported in other views

  Command	Function	Configuration Notes
  port-mirroring undo port-mirroring	Binds a mirrored port to an observing port.	You are not advised to perform service configurations on Eth-Trunk member ports of an AS that are bound to a fabric port, as doing so may cause a failure of SVF system setup.
  traffic-mirror undo traffic-mirror	Configures the traffic mirroring function.	You are not advised to perform service configurations on Eth-Trunk member ports of an AS that are bound to a fabric port, as doing so may cause a failure of SVF system setup.
  observe-port undo observe-port	Configures an observing port.	Generally, an observing port is dedicated to monitoring forwarding of mirrored traffic. Therefore, configuring an AS port with service configurations as an observing port is not recommended. If a port has been configured as an observing port, do not deliver service configurations to this port through service profiles or the direct-command command. You are not advised to perform service configurations on Eth-Trunk member ports of an AS that are bound to a fabric port, as doing so may cause a failure of SVF system setup.
  traffic-statistic undo traffic-statistic	Enables the traffic statistics collection function.	If you delete the traffic-statistic command that is delivered by the parent to an AS, you will fail to obtain traffic statistics about the AS on the parent. You are not advised to perform service configurations on Eth-Trunk member ports of an AS that are bound to a fabric port, as doing so may cause a failure of SVF system setup.
  capture-packet	Configures the packet header obtaining function.	You are not advised to perform service configurations on Eth-Trunk member ports of an AS that are bound to a fabric port, as doing so may cause a failure of SVF system setup.
  acl 2000-2999 undo acl 2000-2999	Creates or deletes an ACL rule.	If the number of traffic policies on an AS reaches the upper limit, the parent fails to deliver the IPSG or DAI configurations. Run the display uni-mng commit-result profile command on the parent to check the configuration delivery result. If the command output shows that the configuration delivery fails, run the display uni-mng execute-failed-record profile as name as-name command to check execution failure records after the configuration is delivered to an AS. The command output provides detailed information about the delivery failure. You can log in to the AS to check whether the ACL resources are used up.
  acl 3000-3998 undo acl 3000-3998
  acl 4000-4997 undo acl 4000-4997
  rule undo rule	Creates an ACL rule.	-
  interface Eth-Trunk undo interface Eth-Trunk	Creates or deletes an Eth-Trunk interface or displays the Eth-Trunk interface view.	In V200R011C10 and later versions, you can only enter the Eth-Trunk interface view and cannot create or delete Eth-Trunk interfaces. Do not delete Eth-Trunk0 or Eth-Trunk interfaces that are bound to the downlink fabric port from an AS.
  interface GigabitEthernet	Displays the GE interface view.	-
  interface XGigabitEthernet	Displays the XGE interface view.	-
  interface Ethernet	Displays the Ethernet interface view.	-
  interface MultiGE	Displays the MultiGE interface view.	This command is only supported by S5720-14X-PWH-SI-AC, S5720-28X-PWH-LI-AC, and S6720SI.
  display	Displays the device status or configurations.	-
  quit	Returns to the upper-level view.	-
  return	Returns to the user view.	-
  interface stack-port	Displays the stack port view.	-
  shutdown interface undo shutdown interface	Shuts down/restores a stack member port.	This command is configured in the stack port view.
  mad restore	Restores all the blocked interfaces of a standby switch that enters the Recovery state after its stack splits.	-
  reset trace instance(supported in V200R010 and later versions)	Clears all the diagnosis instances on a device.	-
  save trace information(supported in V200R010 and later versions)	Saves diagnosis information in the buffer area as a file.	-
  Commands starting with the trace keyword (supported in V200R010 and later versions) Commands starting with the undo trace keyword(supported in V200R010 and later versions)	Used for service diagnosis and executed in the system view.	-

Independent Mode (Configurable Commands After Logins to ASs Using the attach-as Command or Console Port)

The independent mode has been supported since V200R010. In independent mode, the commands listed in the following table can be configured on ASs. When configuring these commands, pay attention to the following points:

• These commands vary depending on the AS device type. For details, see the command reference of these devices.
• In independent mode, configuring some commands may cause an AS's failure to go online. To prevent this problem, some commands listed in the following table are not supported. If an unsupported command is executed on an AS, an error message is displayed.

See more please click 

https://support.huawei.com/enterprise/en/doc/EDOC1000069520/9aadccc0/comprehensive-configuration-examples