In independent mode, you can log in to an AS to configure this AS. Currently, the independent mode is supported by level-1 and level-2 ASs only when the parent is directly connected to ASs.
If a level-1 AS uses the centralized mode, level-2 ASs connected to this level-1 AS cannot be changed to the independent mode. If a level-1 AS uses the independent mode, level-2 ASs connected to this level-1 AS can use either the independent or centralized mode. However, configurations for service interoperability with the level-2 AS, for example, adding ports to service VLANs, must be manually performed on the level-1 AS because this level-1 AS uses the independent mode and so cannot have service configurations delivered from the parent.
If an AS is changed from the independent mode to centralized mode, the configuration file saved in independent mode will be deleted, and then the AS restarts and goes online with any configuration file.
For services that can be configured for an AS in independent mode, see Service Configuration Supported on an AS.
The system view is displayed.
The uni-mng view is displayed.
An administrator is created to log in to the AS. An administrator needs to be created before the independent mode is configured.
Level-1 AS (configuration of the fabric port that connects the parent to a level-1 AS)
Run interface fabric-port port-id
The fabric port view is displayed.
Run port connect independent-as
The independent mode is enabled on the fabric port that connects the parent to a level-1 AS.
Level-2 AS (configuration of the fabric port that connects a level-1 AS to a level-2 AS)
Run as name as-name
The AS view is displayed.
Run down-direction fabric-port port-id connect independent-as
The independent mode is enabled on the fabric port that connects a level-1 AS to a level-2 AS.
Log in to the AS from the parent.
In addition to logging in to an AS from the parent, you can log in to an AS through the console port of the AS.
Return to the AS user view.
The configuration is saved to the flash memory of the AS and the AS configuration file is uploaded to the parent.
After this step is performed, the AS configuration file uploaded to the parent will be saved to the flash:/unimng/ind-cfg directory or the cfcard:/unimng/ind-cfg directory on some parent switch models. If the file name format is unimng-xxxx-xxxx-xxxx.zip (xxxx-xxxx-xxxx indicates the management MAC address of an AS), and the service configuration mode of this AS is independent mode, it is not allowed to delete this configuration file.
After the upload config command is executed, the AS configuration file may fail to be uploaded to the parent. The possible causes include insufficient storage space on the parent and a fault of the link between the AS and parent.
To prevent services from being affected, it is recommended not to delete the configuration file saved on the AS.
The AS configuration file saved on the parent can ensure configuration integrity for the AS. For example, after an AS goes online again or is replaced, the AS will compare its saved configuration file with that saved on the parent. If the two files are inconsistent, the configuration file saved on the parent will replace the configuration file saved on the AS and take effect after the AS restarts.