topic Re: Onboarding a switch with preexisting config in Aerohive Migrated Content

Onboarding a switch with preexisting config

a_stan — Thu, 28 Mar 2019 23:35:34 GMT

I have a Dell switch in production. I now need to add it to HiveManager. Must I erase the startup config, reboot the switch and configure it from scratch in HM interface? Or is there a less intrusive way for me to perform this?

Re: Onboarding a switch with preexisting config

bruce_stahlin — Fri, 29 Mar 2019 02:10:52 GMT

I guess it depends on the actual configuration. We create templates, thus permitting us to assign port types, VLANs, etc prior to deployment. If you choose this method, you'll be able to duplicate your config within HIveManager and have a less intrusive migration,.

Re: Onboarding a switch with preexisting config

a_stan — Mon, 15 Apr 2019 22:52:41 GMT

Ok, I created a template, as close to the current config as possible; some options I couldn't configure via web GUI - I added using the supplemental CLI. When I push the config update, it gets stuck at 30% and then the switch reboots. Some (debug) logs right before reboot:

15:17:05 hive12-1 %% DBG HiveAgent: MOD_HTTPS ah_hiveagent_https_client.c:2196: Max retry time[3319] current time[3019]

15:17:05 hive12-1 %% NOTE Link Up: Vl1

15:17:05 hive12-1 %% DBG HiveAgent: HOST_ASYNC ah_hiveagent_async_event_handler.c:446: Got trap, sending result to HM-NG

15:17:05 hive12-1 %% DBG HiveAgent: MOD_HTTPS ah_hiveagent_https_client.c:2196: Max retry time[3319] current time[3019]

15:17:05 hive12-1 %% DBG HiveAgent: HOST_ASYNC ah_hiveagent_async_event_handler.c:446: Got trap, sending result to HM-NG

15:17:05 hive12-1 %% NOTE Link Up: Gi1/0/3

15:17:05 hive12-1 %% DBG

hapiBroadIntfDot1xStatus 1535: Authorizing data device on USP 1/0/3. Enabled learning

15:17:05 hive12-1 %% DBG HAPI LS callback, u 0. p 3

15:17:02 hive12-1 %% ERR There is a monitor session configuration conflict. Destination interface Gi1/0/5 cannot participate in any VLAN. Please remove the mirror config before adding a VLAN on interface Gi1/0/5

15:17:02 hive12-1 %% DBG HiveAgent: MOD_HTTPS ah_hiveagent_https_client.c:2196: Max retry time[3315] current time[3015]

15:17:02 hive12-1 %% DBG HiveAgent: HOST_ASYNC ah_hiveagent_async_event_handler.c:446: Got trap, sending result to HM-NG

15:17:02 hive12-1 %% DBG HiveAgent: MOD_HTTPS ah_hiveagent_https_client.c:2196: Max retry time[3315] current time[3015]

15:17:02 hive12-1 %% DBG HiveAgent: HOST_ASYNC ah_hiveagent_async_event_handler.c:446: Got trap, sending result to HM-NG

15:17:02 hive12-1 %% NOTE Link on Vl1 is failed

15:17:02 hive12-1 %% DBG HiveAgent: MOD_HTTPS ah_hiveagent_https_client.c:2196: Max retry time[3315] current time[3015]

15:17:02 hive12-1 %% NOTE Link Down: Vl1

15:17:02 hive12-1 %% DBG HiveAgent: HOST_ASYNC ah_hiveagent_async_event_handler.c:446: Got trap, sending result to HM-NG

15:17:02 hive12-1 %% DBG HiveAgent: MOD_HTTPS ah_hiveagent_https_client.c:2196: Max retry time[3315] current time[3015]

15:17:01 hive12-1 %% NOTE Link on Gi1/0/3 is failed

15:17:01 hive12-1 %% NOTE Link Down: Gi1/0/3

15:17:01 hive12-1 %% DBG

hapiBroadIntfDot1xStatus 1490: Unauthorizing data device on USP 1/0/3. Disabled learning

15:17:01 hive12-1 %% DBG HAPI LS callback, u 0. p 3

15:17:01 hive12-1 %% DBG HiveAgent: MOD_HTTPS ah_hiveagent_https_client.c:2196: Max retry time[3315] current time[3015]

15:17:01 hive12-1 %% NOTE Link Up: Vl1

15:17:01 hive12-1 %% NOTE Link on Vl15 is failed

15:17:01 hive12-1 %% DBG HiveAgent: MOD_HTTPS ah_hiveagent_https_client.c:2196: Max retry time[3315] current time[3015]

15:17:01 hive12-1 %% DBG HiveAgent: HOST_ASYNC ah_hiveagent_async_event_handler.c:446: Got trap, sending result to HM-NG

15:17:01 hive12-1 %% NOTE Link Down: Vl15

15:17:01 hive12-1 %% DBG HiveAgent: MOD_HTTPS ah_hiveagent_https_client.c:2196: Max retry time[3315] current time[3015]

15:17:01 hive12-1 %% DBG HiveAgent: HOST_ASYNC ah_hiveagent_async_event_handler.c: Got trap, sending result to HM-NG

15:17:00 hive12-1 %% DBG HiveAgent: MOD_HTTPS ah_hiveagent_https_client.c:1770: Poll paused as config is in progress

15:16:59 hive12-1 %% INFO [CLI:hivemanager:127.0.0.1] Access level of user hivemanager@dell.com has been set to 15

15:16:59 hive12-1 %% INFO [CLI:hivemanager:127.0.0.1] New user hivemanager@dell.com has been added

15:16:59 hive12-1 %% DBG Password Successfully Configured

15:16:59 hive12-1 %% DBG HiveAgent: MOD_HTTPS ah_hiveagent_https_client.c:2196: Max retry time[3313] current time[3013]

15:16:59 hive-1 %% INFO [CLI:hivemanager:127.0.0.1] User hivemanager logged in to enable mode.

15:16:59 hive-1 %% DBG HiveAgent: MOD_SSH ah_hiveagent_ssh.c:371: logout is not present in [31ca0038-dd5b-448c-be80-1978b0085eb6] commands

15:16:59 hive-1 %% DBG HiveAgent: MOD_SSH ah_hiveagent_ssh.c:1621: ctr_ha_sessions++

15:16:59 hive-1 %% DBG HiveAgent: MOD_SSH ah_hiveagent_ssh.c:1582: Got session for [31ca0038-dd5b-448c-be80-1978b0085eb6]

15:16:59 hive-1 %% DBG HiveAgent: MOD_SSH ah_hiveagent_ssh.c:2155: Got object with context_id [31ca0038-dd5b-448c-be80-1978b0085eb6] obj num [7]

15:16:59 hive-1 %% DBG HiveAgent: MOD_HTTPS ah_hiveagent_https_client.c:1854: Total work requests from HMNG [7] and Total work responses from HA [6]

15:16:59 hive-1 %% DBG HiveAgent: MOD_SSH ah_hiveagent_ssh.c:2230: Total enqueued [6]

15:16:59 hive-1 %% DBG HiveAgent: MSG_BROKER ah_hiveagent_msg_broker.c:920: Message Broker got work request for action [8]

I know some commands go through (for example hostname changes from hive to hive12). What am I missing?

Re: Onboarding a switch with preexisting config

martin_ryan — Thu, 23 May 2019 06:57:38 GMT

Hi Ana-Maria,

Be warned - I'm new to Dell switches in HiveManager as well - bit Idid have a similar issue. Unfortunately, I tried a number of things to resolve it at the same time so, I'm not sure which solved it - but two things to check;

1) I've couldn't see where routed ports and other layer3 information is to be stored in HiveManager - so, just check that the config push is not "cutting off the branch you're sitting on" - i.e. that the interface you need for HiveManager to reach the switch is not being cut off by inappropriate config.

2) I had AAA running on the switch and one of the issues was that there were authentication failures on the ACS server for user "hivemanager" (or something similar. Ensuring local authentication works and turning off AAA authen and authorization may help.

Best of luck, Martin

Re: Onboarding a switch with preexisting config

andrew_vernon — Fri, 21 Jun 2019 01:48:56 GMT

I know this thread's a couple of months old, but I can consistently recreate your problem on my Dell N2000 series switches. I've found that doing "erase startup-config" on the switch and treating it as new allows HM to configure it, but starting from scratch isn't always an option.

Which switch family are you using? I know N2000 has issues. I've got a couple of new N1100's for testing, so I'm interested in seeing if it's common across Dell platforms.

I also have SR2208P's around, but since they're Aerohive switches, they were on HiveManager from unboxing.

Re: Onboarding a switch with preexisting config

a_stan — Mon, 24 Jun 2019 20:08:29 GMT

It is an N-3000 switch. Eventually I gave up. I was successful adding 2 N-2000 switches in a stack. No outage experienced during the tests. When pushing config from HM to the stack with pre-existing config, it seems to be merging the 2 configurations; I thought it would first wipe it clean and then apply new config. Where the 2 configs conflict - the one pushed from HM is applied on the switch. It all went very smooth.

Still not clear what went wrong with N3000; HM seems to have changed to vty password so I can no longer access the switch (as the console port is broken). It appears online in HM, but I can't change the config on it. ¯_(ツ)_/¯

Re: Onboarding a switch with preexisting config

martin_ryan — Tue, 25 Jun 2019 05:07:17 GMT

Hi BJ,

Assigning port types, VLANs, etc via templates is no problem and we do the same.

However, using the channel-group, sub-interface command, you can create a port channel - a new interface in it's own right. Where in hive manager are you going to configure the characteristics of this new interface? Depending on your needs, a given vlan may include a layer-3 interface which on the CLI, you bring into existence by simply declaring, "interface vlanN". Again, where in hive manager are you going to store the ip address and other characteristics of this interface?

Some answer with "the supplemental CLI" but what happens then? Every time you push a config update - say, changing the vlan a normal, switched port is in - are those supplemental commands executed? Are they looked for in the config and executed if they're missing? How does hive manager ensure that at least one port has been configured with "channel-group" before executing the supplemental commands that presume the existence of a port channel interface? Or, does it assume they pre-exist and execute the port channel commands blindly?

On the CLI, referring to "interface poN" will not be accepted unless you've created the port channel first. How this dependency is expressed in hive manager is far from clear. As a result, in our case, hive manager has been reduced to a glorified equipment monitor with all configuration updates handled by some other means.