Loading...
Loading...
Syslog messages don't send to server. "show logging info" output shows the following messages although Ping to syslog-sever is fine. ------------------------------------------------------------- DO7010A# ping 10.141.32.177 vrf management PING 10.141.32.177 (10.141.32.177): 56 data bytes 64 bytes from 10.141.32.177: icmp_seq=0 ttl=123 time=1.262 ms 64 bytes from 10.141.32.177: icmp_seq=1 ttl=123 time=0.753 ms 64 bytes from 10.141.32.177: icmp_seq=2 ttl=123 time=1.18 ms 64 bytes from 10.141.32.177: icmp_seq=3 ttl=123 time=0.72 ms 64 bytes from 10.141.32.177: icmp_seq=4 ttl=123 time=0.843 ms --- 10.141.32.177 ping statistics --- 5 packets transmitted, 5 packets received, 0.00% packet loss round-trip min/avg/max = 0.72/0.951/1.262 ms DO7010A# DO7010A# sh logging info Logging console: enabled (Severity: critical) Logging monitor: enabled (Severity: debugging) Logging linecard: disabled Logging timestamp: Milliseconds Logging loopback : disabled Logging server: enabled {10.141.32.177} This server is temporarily unreachable <<<<< server severity: notifications server facility: local7 server VRF: management -------------------------------------------------------------
Under normal conditions.
Run following commands: (config)# no logging server 10.141.32.177 5 use-vrf management facility local6 (config)# logging server 10.141.32.177 5 facility local6 (config)# logging source-interface loopback 0 Configuring logging source-interface will open UDP/syslog socket(514). (config)# logging server 10.141.32.177 5 use-vrf management facility local6 (config)# no logging source-interface loopback 0 UDP/syslog socket(514) is being closed.
This issue applies to Nexus 3000 (N3K) series as well.
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.