In an SVF system, two AS service configuration modes are available: centralized mode and independent mode.
In centralized mode, all service configurations for ASs are performed on the parent. Therefore, which services can be configured on ASs depends on the services that can be configured on the parent, but not depend 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. The global batch configuration mode supports only a few functions. The following describes profile-based configuration and direct configuration.
Profile-based Configuration
In profile-based configuration, service profiles on the parent are bound to specified device and port groups to delivery service configurations to ASs. Profile-based configuration involves two concepts:
Device and Port Groups
If multiple ASs or ports in an SVF system need the same configurations, you can add these ASs or ports to the same group for batch configuration. This improves the configuration efficiency.
| Group Type | Member Type in a Group | Description |
|---|---|---|
| AS group | AS | An AS group is a set of ASs. The group implements batch configuration of ASs with the same global configuration. For example, You can configure an AS administrator for the ASs in an AS group. |
| AS port group | Port that connects an AS to a user terminal | An AS port group is a set of AS ports that connect to user terminals. The group implements batch configuration of AS ports with the same configuration. |
| AP port group | Port that connects an AS to an AP | An AP port group is a set of AS ports that connect to APs. All the ports that connect ASs to APs need to be added to an AP port group. |
Service Profiles
A service profile is a set of service configurations. You can bind service profiles to specified device and port groups to deliver the service profiles to corresponding ASs, which then parse and execute services configured in the service profiles.
| Service Profile Type | Bound Object | Description |
|---|---|---|
| AS administrator profile | AS group | An AS administrator profile is used to configure AS administrator services and the rate limit for outgoing ARP and DHCP packets on an uplink fabric port. |
| Network basic profile |
|
A network basic profile is used to configure basic services for AS ports, such as VLANs. |
| Network enhanced profile | AS port group | A network enhanced profile is used to configure enhanced services for AS ports, such as the traffic rate limit and DHCP snooping. |
| User access profile | AS port group | A user access profile is used to configure authentication services for user access (for example, the authentication mode), MAC address learning limiting, and the rate limit for incoming ARP and DHCP packets on an AS port. |
| Network QoS profile | AS port group | A network QoS profile is used to configure QoS services for AS ports, including the packet priority mapping mode, queue scheduling mode, and queue scheduling weight. |
| Traffic policy profile | AS Port Group | A traffic policy profile is used to configure traffic policy functions for AS ports, including the packet re-marking function. |
Direct Configuration
Service configurations can be delivered to ASs through service profiles. Apart from this method, you can also run the direct-command command on the parent to directly deliver some service configurations to ASs.
In independent mode, you can log in to an AS to configure this AS using commands, instead of delivering service configurations to the AS. After the AS has been configured, the configuration file can be saved on the AS and uploaded to the parent using the upload config command.
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 this AS independently. After the AS changes from the centralized mode to independent mode, all the service configurations performed using profiles or directly delivered before mode switching will be retained.
An AS can also use only the independent mode if this mode is pre-configured on the fabric port that connects the parent to this AS before this AS goes online.
Currently, the independent mode is not supported when the parent is connected to ASs across a Layer 2 network.