Once a license is registered the next renewal attempt takes place after 6 months thus you need to connect to the CSSM to get license register. ----- snip ------ Registration: Status: REGISTERED Smart Account: XXXXXXXXXXX Virtual Account: XXXXXXXXXXX Export-Controlled Functionality: Allowed Initial Registration: SUCCEEDED on Sep 19 12:29:44 2018 CDT Last Renewal Attempt: None Next Renewal Attempt: Mar 18 12:29:44 2019 CDT <------------ Registration Expires: Sep 19 12:21:39 2019 CDT License Authorization: Status: AUTHORIZED on Sep 19 12:31:48 2018 CDT Last Communication Attempt: SUCCEEDED on Sep 19 12:31:48 2018 CDT Next Communication Attempt: Oct 19 12:31:47 2018 CDT Communication Deadline: Dec 18 12:25:46 2018 CDT ... View more

KS3, Please share the complete product ID of the device. ... View more

Alexander, Flash is internal storage of the switch (not removable), you can save the copy of startup configuration on the usbflash0: and then transfer it to the other switch in case of any failure. ... View more

show logging onboard switch 1 uptime I would suggest opening a TAC case so that engineer can further investigate and look into hardware/software component. If you plan on opening a TAC case please attach following outputs. 1) show version 2) show module 3) show logging onboard switch 1 uptime 4) dir crashinfo: 5) Information about how frequently it reboot. Good luck! ... View more

show logging onboard switch 1 detail ... View more

Thomaz, Please share the following information from the switch. 1) show module 2) show logging onboard detail ... View more

Andrew, That's true that starting 16.9.1 Smart Licensing is the only option to register the license. It is not necessary to have direct access to the internet from your Cisco devices. Customers can setup an HTTP Proxy or a Satellite Proxy server to connect their devices to register the license. Customers can work with their Cisco Account team to get help to set up Cisco SSM account on their behalf (if does not exists already) which will be located at software.cisco.com and all your purchased licenses will appear under the Smart account. We understand that it is an added step to register the license but it gives the customer the ability to keep a track of all the purchased licenses and CSSM gives you granularity (how many licenses you purchased, how many are in use, how many are left). Earlier when you use to purchase the license it was limited to only one product and if the device was decommissioned then that license was of no use. The beauty of Smart license is that you can reuse the license on any other devices (as long as it support those licenses) once you decide to decommission the device from your network. After a certain time period if your devices are not able to communicate to the smart account (direct or through proxy) then CSSM thinks that device is dead and it pulls the license back in the Smart Account pool and is good to reuse which is cost-effective. ... View more

George, Currently, we have two proxy setups which are available. Either HTTP proxy or Satellite proxy server. For Satellite proxy server you can download the ISO image from CCO page. Link: https://software.cisco.com/download/home/286285506/type/286285517/os/Linux/release/5.0.1 Create a VM using vSphere Client with a System requirement as follows. • Minimum 60GB hard disk. Ideal 200GB • 8GB Memory • 4 vCPUs I would suggest working with TAC to set up a Satellite proxy server. ... View more

Cisco Account team can help you to set up Cisco SSM account on your behalf (if does not exists already) which will be located at software.cisco.com and all your purchased licenses will appear in that account. Tokens are used to register a software license to a given device. Once you have Cisco SSM account setup and the Default/Virtual Account shows the licenses then you can work with TAC to register the licenses. ... View more

Inactive(NA) means it is Non AED which means  your local ASR's are not able to communicate over ISIS internally since they make decision automatically who will be the forwarder for which vlan. I'm sure you won't see local ASR under "show otv isis aed svr req local info" on which you see Inactive(NA) show otv isis neighbor - this should show local ASR under "Tag Site" Run adjacency debugs to check if they are exchanging ISIS packets. ... View more

Hi David, I believe we are getting IP from DHCP server, right? Please share vlan 38 configuration. Can we try to hard code vlan on IP Phone? Maybe DHCP is assigning IP in data vlan. Run "debug ip packet" during non-business hours and shut/no shut the interface. (before this log this session) Run Embedded captures on 3850 and perform shut/no shut. Example: Switch#monitor capture TEST interface gi1/0/34  monitor capture TEST match ipv4  any any  monitor capture TEST file location flash:mycap.pcap buffer-size 10  monitor capture TEST limit packets 100 Once this is configured, you must start the capture. If a file already exists on the flash with this name, it prompts you if wish to overwrite this. Switch#monitor capture TEST start A file by the same capture file name already exists, overwrite?[confirm] To check outputs Switch#show monitor capture file flash:TEST.pcap Switch#show monitor capture file flash:TEST.pcap detailed You can also transfer file to your PC and run Wireshark to get detailed analysis. (Please share) Most probably packet is not being tagged properly. In case if you have opened TAC case do share SR# Regards, Vivek Sharma ... View more

ciscoreg2, Which device are we using here? Also, please SPAN port while file transfer and try to match how much byte of data is transferred, it may be padding. But need to look into captures. Regards, Vivek Sharma ... View more

check sea_console logs from both active and standby supervisor. Mostly we would see logs as below: %VSLP-SW1-3-VSLP_LMP_FAIL_REASON: Te1/5/15: Timeout (30000msec) waiting for Hello packet from peer %VSLP-SW1-3-VSLP_LMP_FAIL_REASON: Te1/5/16: Timeout (30000msec) waiting for Hello packet from peer %VSLP-SW1-2-VSL_DOWN:   All VSL links went down while switch is in ACTIVE role   This VSLP LMP link failure is common issue on SY1, SY2 and on SY3. There is no reported issues in SY4, though I would suggest to get on SY4a (which is maintenance release of SY4) in case you find VSL LMP link failure log messages on SY4 then open TAC case, so that TAC can report this issue to developers.   ... View more