this seems to be a) fixed b) more a cosmetic issue!?   I just found a switch * three SNMPd-crashes since the switch has been booted * the SNMP-Daemon seems to restart just fine everytime it crashes   Nexus# show version | inc "(system:|uptime)" Kernel uptime is 1037 day(s), 16 hour(s), 49 minute(s), 33 second(s) system: version 7.1(4)N1(1)   Nexus# show logging logfile | inc snmpd 2018 Mar 10 03:57:13.814 CET Nexus %SYSMGR-2-SERVICE_CRASHED: Service "snmpd" (PID 3441) hasn't caught signal 8 (core will be saved). 2019 Jan 30 08:47:22.540 CET Nexus %SYSMGR-2-SERVICE_CRASHED: Service "snmpd" (PID 31993) hasn't caught signal 8 (core will be saved). 2019 Dec 18 20:28:09.673 CET Nexus %SYSMGR-2-SERVICE_CRASHED: Service "snmpd" (PID 30001) hasn't caught signal 8 (core will be saved).   Nexus# show core VDC Module Instance Process-name PID Date(Year-Month-Day Time) --- ------ -------- --------------- -------- ------------------------- 1 1 1 snmpd 3441 2018-03-10 03:57:32 1 1 1 snmpd 31993 2019-01-30 08:47:40 1 1 1 snmpd 30001 2019-12-18 20:28:28   * the SNMPd is up and running Nexus# show snmp | inc packets|[1-9].*Out 1215708625 SNMP packets input 1215711537 SNMP packets output 5897 Out Traps PDU 1215704593 Out Get Responses   ...wait   Nexus# show snmp | inc packets|[1-9].*Ou 1215708626 SNMP packets input 1215711538 SNMP packets output 5897 Out Traps PDU 1215704594 Out Get Responses ... View more

I assume, VLAN999 is a unused "dummy" VLAN to tag-all VLANs used for productive traffic at the Catalyst. * at the SG-Switch you could set the port easily to "Native-VLAN: None" and add a "List of tagged VLANs" to the Trunk * at the Catalyst there is always a Native-VLAN at a trunk [unless you configure tag-all] => avoid the useless error-log-message at the SG-Switch using conf t (config)#no cdp log mismatch native ... View more

call this from cloupia-script would be a great solution to avoid having to encode https/basic-auth-stuff in javascript within a custom task.   Might be off-topic, but any other "elegant" solution to call a set of rest-api-calls with dynamically generated urls/parameters? ... View more

"clis" seems to be without broad device-support...   should _this_ really be the way to go if you don't want do write script for every device-type? * try the "clis"-command * if not successful, fall back to "exec"-command which is supported in every device   if {[catch {set showversion [clis {show version}]} e] } { if {[catch {set showversion [exec {show version}]} e] } { puts "ERR: Show Version - $e" break } } puts $showversion   ... View more

scenario all your "ntp server" time-sources are using the same "upstream" time-source ".ACTS." all ntp-servers provide almost the same level of accuracy your router as ntp-client nevertheless is choosing the best time-source   reason for the log-output this "best time-source" seems to slightly change from time to time eg. network-latency between router and ntp-server increases/decreases... the router selects a better (but still almost identical) time-source and generates the log-output shown solution configure one ntp-server to be preferred ntp server 206.246.122.250 prefer ntp server 24.56.178.140 ntp server 64.113.32.5   => this should pin your router permanently to server 206.246.122.250. => the logging should be gone           ... View more

looking at your ssh-server * using "DEBUG"-LogLevel   admin@ubuntu:~/.ssh$ cat /etc/ssh/sshd_config | egrep "Level" #LogLevel VERBOSE LogLevel DEBUG you'll notice:   admin@ubuntu:~/.ssh$ tail -f /var/log/auth.log Aug 28 17:63:92 ubuntu sshd[3218]: Connection closed by authenticating user admin <router-ip> port #nnn [preauth] so the router (ssh-client) drops the session as the server wants to see some authentication-credentials.         ... View more

i know this thread is years old... * just as an update a) ASA Release 9.9 - still no allowas-in https://www.cisco.com/c/en/us/td/docs/security/asa/asa99/configuration/general/asa-99-general-config/route-bgp.html b) BGP intelligence must be placed somewhere else, for example as-override: https://community.cisco.com/t5/service-providers-documents/bgp-pe-ce-routing-protocol-overview-in-mpls-vpns-part-ii/ta-p/3143007#toc-hId--765071651       ... View more

at least the tcp  *:22... LISTEN ...SSHd is missing at 16.8(1)   the "show ip ports all" command displays the listining BGP-Ports, but only established SSH-Ports... ... View more

just as an addon:   Works fine with a) static-GRE-Tunnels b) dynamic-GRE-Tunnels(FlexVPN) - even FlexVPN Site-to-Site Shortcuts!   RTR-95#show cdp neigh Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone, D - Remote, C - CVTA, M - Two-port Mac Relay Device ID Local Intrfce Holdtme Capability Platform Port ID RTR-11 Tunnel4011 154 R I ASR1009-X Virtual-Access3 ***FlexVPN Spoke-to-Hub*** RTR-91 Gig 0/0/0 179 R I ASR1002-H Gig 0/0/1 RTR-17 Virtual-Access1 176 R S I ISR4221/K Virtual-Access1 ***Shortcut: Spoke-to-Spoke***   ... View more

is this not just a link to an Promotional-Bundle - which might be EOSale but not the Blade-Server-Module itself!? this should be the current list of EOSed server-hardware: https://www.cisco.com/c/en/us/support/servers-unified-computing/ucs-b200-m4-blade-server/model.html#End-of-LifeandEnd-of-SaleNotices B200 M2 where EOS at March 1, 2013 B200 M3 where EOS at December 31, 2016. There are usually 6 months between an EOS-announcement and the EOS-date, so i'd assume you have more than 6 months left to order M4-blades since there is no M4-EOS-announcement published. Correct me if i've missed something. ... View more