04-27-2023 11:17 AM
Not sure what is going on here:
93180-01-CORE(config)# logging server 172.24.0.243 facility local6 use-vrf default
93180-01-CORE(config)# show logging server
Logging server: enabled
{172.24.4.11}
server severity: notifications
server facility: local7
server VRF: default
server port: 514
{172.24.14.7}
server severity: notifications
server facility: local7
server VRF: default
server port: 9514
{172.24.0.243}
This server is temporarily unreachable
server severity: notifications
server facility: local6
server VRF: default
server port: 514
93180-01-CORE(config)# ping 172.24.0.243 vrf default
PING 172.24.0.243 (172.24.0.243): 56 data bytes
64 bytes from 172.24.0.243: icmp_seq=0 ttl=126 time=0.806 ms
64 bytes from 172.24.0.243: icmp_seq=1 ttl=126 time=0.425 ms
64 bytes from 172.24.0.243: icmp_seq=2 ttl=126 time=0.492 ms
64 bytes from 172.24.0.243: icmp_seq=3 ttl=126 time=0.463 ms
64 bytes from 172.24.0.243: icmp_seq=4 ttl=126 time=0.453 ms
--- 172.24.0.243 ping statistics ---
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0.425/0.527/0.806 ms
93180-01-CORE(config)#
04-27-2023 11:17 PM
Hello @Steven-Williams-83,
You can ping frome the 93180 the syslog server is one thing ; and the syslog servie unreachable is an other thing. You can ping it, then you are OK with the network (L3) connectivity. But the service (L7) is unavailable on your syslog server. Does the service run?
The output indicates that the logging server is temporarily unreachable. The fact that you were able to successfully ping the server from the switch suggests that there may be an issue with the syslog service running on the server or with the configuration of the syslog service.
To further troubleshoot:
--Check the syslog configuration on the server and ensure that it is set up to receive messages from the switch on the correct port and facility.
--Check the status of the syslog service on the server to ensure that it is running and accepting connections.
10-09-2023 08:57 AM
I have had the same issue, multiple times when adding a new logging server
Simply remove the logging config and re-add
no logging source-interface GigabitEthernet0/0 vrf Mgmt-vrf
no logging host 1192.168.1.99 vrf Mgmt-vrf
no logging host 192.168.254.99 vrf Mgmt-vrf
logging source-interface GigabitEthernet0/0 vrf Mgmt-vrf
logging host 1192.168.1.99 vrf Mgmt-vrf
logging host 192.168.254.99 vrf Mgmt-vrf
You may have to wait for or cause a syslog to happen (no shut/shut an interface not in use)
I seen this a lot with 9200 and 9300 Nexus different versions of IOSXE
12-04-2023 01:38 AM
have the same problem.
when i config logging server, it always temporarily unreachable on some switch.
after check the config diff,that happens when i config no autostate on the svi which is the syslog source-interface.
after delete it,the syslog server worked.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide