We have a CAT9K with IOS-XE Version 16.8.1a When I try to execute the upgrade commands for ISSU I get the below error: FAILED: ACTIVATE operation is not allowed in SWITCHED_OVER state Somehow I cannot seem to go around this issue (marked below in green) I googled my way around but I didnt find an answerd, maybe somebody can shed some light on this case. How to get it out active switched-over state ? Its the only 9500 we have, the catalyst 4500 in VSS show different information under the the show issu state detail so I have also no compare information :). FYI: Before I issued the "activate issu" command (with my console port plugged into the Active switch) I issued the install add file tftp://172.16.16.2/ cat9k_iosxe.16.09.01.SPA.bin ------ Here some information about the state of the current stackwise virtual: Switch#install activate issu install_activate: START Wed Sep 26 09:19:14 UTC 2018 install_activate: Activating ISSU *Sep 26 09:19:15.570: %INSTALL-5-INSTALL_START_INFO: Switch 1 R0/0: install_engine: Started install activate ISSU NOTE: Going to start Activate ISSU install process STAGE 0: Initial System Level Sanity Check before starting ISSU =================================================== --- Verifying install_issu supported --- --- Verifying standby is in Standby Hot state --- --- Verifying booted from the valid media --- --- Verifying AutoBoot mode is enabled --- Finished Initial System Level Sanity Check FAILED: ACTIVATE operation is not allowed in SWITCHED_OVER state ERROR: install_activate  exit(2 ) Wed Sep 26 09:19:18 UTC 2018 ------------------------- ! Switch#show switch Switch/Stack Mac Address : 00aa.6ef3.8c80 - Local Mac Address Mac persistency wait time: Indefinite                                              H/W   Current Switch#   Role    Mac Address     Priority Version  State ------------------------------------------------------------------------------------- *1       Active   00aa.6ef3.8c80     1      V01     Ready  2       Standby  00b6.7039.df80     1      V01     Ready Switch#show issu state detail --- Starting local lock acquisition on switch 1 --- Finished local lock acquisition on switch 1 Operation type: Step-by-step ISSU Step-by-step ISSU Install type  : Image installation using ISSU Current state : Active switched-over state Last operation: Abort Completed operations: Operation                           Start time ------------------------------------------------------- Activate location standby Chassis 2 2018-08-21:11:57:56 Activate location standby Chassis 2 2018-09-10:12:57:19 Switchover                          2018-09-11:09:37:17 Switchover                          2018-09-11:10:47:09 Abort                               2018-09-19:09:33:03 State transition: Added -> Added -> Standby activated -> Active switched-over -> Active switched-over Auto abort timer: inactive Running image: flash:packages.conf Operating mode: sso, terminal state reached ! Switch#show redundancy Redundant System Information : ------------------------------        Available system uptime = 20 minutes Switchovers system experienced = 0               Standby failures = 0         Last switchover reason = none                  Hardware Mode = Duplex     Configured Redundancy Mode = sso      Operating Redundancy Mode = sso               Maintenance Mode = Disabled                 Communications = Up Current Processor Information : -------------------------------                Active Location = slot 1         Current Software state = ACTIVE        Uptime in current state = 20 minutes                  Image Version = Cisco IOS Software [Fuji], Catalyst L3 Switch SoftwarCAT9K_IOSXE), Version 16.8.1a, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2018 by Cisco Systems, Inc. Compiled Tue 03-Apr-18 18:49 by mcpre                           BOOT = flash:packages.conf                    CONFIG_FILE =         Configuration register = 0x102 Peer Processor Information : ----------------------------               Standby Location = slot 2         Current Software state = STANDBY HOT        Uptime in current state = 15 minutes                  Image Version = Cisco IOS Software [Fuji], Catalyst L3 Switch SoftwarCAT9K_IOSXE), Version 16.8.1a, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2018 by Cisco Systems, Inc. Compiled Tue 03-Apr-18 18:49 by mcpre                           BOOT = flash:packages.conf                    CONFIG_FILE =         Configuration register = 0x102 ... View more

Hi All, I hope someone can shed some light on my problem :) The Situation is as follow: We have a Cisco Switch  (WS-C3650-24TS) and configured netflowV9 on it.  It should export the cache every 60sec to the some collector ( we will use PRTG from Paessler). The netflow is by the server where PRTG is running on, but somehow it has no volume see screenschot. Paessler said this: We did notice something very important in the Netflow Tester results. The crucial point are the '-1' numbers at the end of each line. The last number for each decoded flow is its volume. -1 is no volume at all. So while the Netflow Tester (and PRTG as well) do get source & destination information, the traffic actually has no volume. Thus the sensor stays grey, as it needs a volume to start working at all.   They say that they dont know the right configuration for every Vendor, so thats why I post it here. The question is why the volume keeps on -1 and how to fix this?    Here the netflow configuration of the Switch   >flow record ipv4_record >match ipv4 protocol >match ipv4 source address >match ipv4 destination address >match transport source-port >match transport destination-port >match interface input >collect transport tcp flags >collect interface output >collect counter packets long >collect counter bytes layer2 long >! >! >flow exporter PRTG >destination 172.16.x.x >source Vlan101 >transport udp 2055 >! >! >flow monitor MAIN_MONITOR >exporter PRTG >cache timeout active 60 >record ipv4_record >  >interface GigabitEthernet1/0/19 >ip flow monitor MAIN_MONITOR input ... View more