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


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


The level 2 AS cannot connect with the level 1 AS in a SVF setup

Publication Date:  2016-07-29 Views:  1074 Downloads:  0

Issue Description

When establishing a SVF network, the level 1 AS(S5700 ) successfully connects with the parent(S12700) but the level 2 AS (S5700) cannot connect with the level 1 AS

The following logs are received: 

Jul 28 2016 09:12:54+02:00 DST S12700 MBR/5/CONNECTERROR:OID Connection error on the fabric-port in unified management. (Reason=The switch has been in uni-mng system force mode.(GigabitEthernet0/0/3 on AS-level1))

SVF Configuration:

as name leaf model S5700-52P-PWR-LI-AC mac-address xxxx-xxxx-xxxx
as name level1 model S5700-52X-LI-48CS-AC mac-address xxxx-xxxx-xxxx
down-direction fabric-port 1 member-group interface Eth-Trunk 1
port Eth-Trunk 1 trunkmember interface GigabitEthernet 0/0/1
port Eth-Trunk 1 trunkmember interface GigabitEthernet 0/0/3
as name level2 model S5700-28TP-LI-AC mac-address xxxx-xxxx-xxxx



The alarm in question announces that the level 2 switch has been forcibly configured in client mode, hence is not being able to start the negotiation with the level 1 AS.

To solve the problem, we would need to configure the mode of the level 2 AS to standalone by running the “undo uni-mng enable " command  in the user interface on the level 2 AS

 Standalone mode: is the common switch mode. In this mode, the switch is an independently operating switch.  When the switch is in a standalone mode and has no configuration file and no input on the console port, the switch can perform auto-negotiation with the parent to select its working mode and continue the svf setup process.