cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1348
Views
4
Helpful
4
Replies

Catalyst Stacks - Priority

Claudia de Luna
Spotlight
Spotlight

Hi,

We are using the APIC-EM controller to stage quite a few 3850 and 3650 stacks.

Setting the switch priority is a command entered at the privileged EXEC prompt (vs in config mode) and these are routinely failing.

What is the recommended approach for these type of configuration commands?  See config load log below.

Received response from pnp agent for message correlatorId: CiscoPnP-1.0-6-290-3C3C7414-6 but with error code : ZTD_CMD_ERROR Response String: ERROR:PnP Service Error 1402:Invalid input detected

service log:

Loading https://192.0.2.2:443/api/v1/file/onetimedownload/51d1dd82-a586-4e47-8cb9-4800965ea918 !

switch 1 priority 15

           ^

% Invalid input detected at '^' marker.

switch 2 priority 14

           ^

% Invalid input detected at '^' marker.

% You already have RSA keys defined named ops-cd03.4-d4-s1.portseattle.org.

% They will be replaced.

% The key modulus size is 2048 bits

% Generating 2048 bit RSA keys, keys will be non-exportable...

[OK] (elapsed time was 2 seconds)

AutoQoS Error: AutoQoS already configured

% Range command terminated because it failed on GigabitEthernet1/0/1

% Range command terminated because it failed on GigabitEthernet1/0/1

switchport access vlan

                        ^

% Invalid input detected at '^' marker.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

% % Duplicate permit statement ignored.

Warning: The cli will be deprecated soon

'tacacs-server host 10.254.11.5 single-connection'

Please move to 'tacacs server ' CLI

Warning: The cli will be deprecated soon

'tacacs-server host 10.6.104.5 single-connection'

Please move to 'tacacs server ' CLI

4 Replies 4

aradford
Cisco Employee
Cisco Employee

Hi Claudia,

this looks like the switch member numbers are not correct?

If you do a "show switch" is there a member #1?

<longer conversation to follow on stack switch member numbers and limitations>

Adam

Yes, there is a switch 1. In this case we needed to pre-provition stacks.

config would look something like this:

vlan X

name xxxx

!##################### Global Config Template Processing #####################!

!

switch 2 provision ws-c3650-24pd

!

switch 3 provision ws-c3650-24pd

!

switch 4 provision ws-c3650-24pd

!

switch 5 provision ws-c3650-24pd

!

switch 1 priority 15

!

switch 2 priority 14

!#####################START of Global TEMPLATE #####################

!#

hostname xxx

I understand now.

My usual trick to solve an "exec" command is to use a self-destructing EEM script.

I have a number of examples in blogs.  There is a sophisticated example here Network Automation with Plug and Play (PnP) – Part 7

You could try something like:

event manager applet POST_PNP

event timer countdown time 30

action 1.0 cli command "enable"

action 1.1 cli command "switch 1 priority 15"

action 1.2 cli command "switch 2 priority 14"

action 2.3 cli command "no event manager applet POST_PNP"

action 2.8 cli command "end"

You put this just before the "end" in your PnP configuration file.

Adam

when i tested the above there was an issue:

The "switch 1 priority 15" command is an interactive command, and prompts you for a "y/n" response.

I also did another "wr me" to get rid of the EEM script from the startup configuration file as well as the running config.

A working version of the EEM script is:

event manager applet POST_PNP

event timer countdown time 30

action 1.0 cli command "enable"

action 1.1 cli command "switch 1 priority 15"  pattern "continue"

action 1.2 cli command "y"

action 1.8 cli command "config t"

action 2.3 cli command "no event manager applet POST_PNP"

action 2.8 cli command "end"

action 2.9 cli command "wr mem"

action 3.0 cli command "end"