Configure syslog server on Nexus 3548

[thuy.hoang]

Dear Buddy,

Im trying to configure the syslog server on Nexus 3548 but the notification always show "This server is temporarily unreachable" and the server also did not get any logging.

CoreSwitch_1(config)# show logging server
Logging server: enabled
{172.21.3.191}
This server is temporarily unreachable
server severity: notifications
server facility: local7
server VRF: default
server port: 514

I use this command to configure:

"logging server 172.21.0.45 5"

But the Nexus always auto add the command "use-vrf default"

CoreSwitch_1(config)# show run | sec logging
logging server 172.21.3.191 5 use-vrf default
logging source-interface Vlan1
logging timestamp milliseconds
logging monitor 7

I just only use the vrf to configure the keep-alive link in vPC. I tried to change use-vrf management but not luck.

Could anyone have experience on this?

Thanks.

[Reza Sharifi]

Is the syslog server IP reachable from the switch?

Spoiler

[thuy.hoang]

Hi buddy,
Yes, it can reach server from switch normally.

[balaji.bandi]

You have configured VRF here, is the SYSLOG server able to use that VRF.

how are you confirming that SYSLOG Server able to reach, by ping?

if you ping it uses global routing table now VRF

can you post ping results and show IP route vrf all output.

[Sergiu.Daniluk · Accepted solution]

Hello again @thuy.hoang,

The command used for syslog server configuration is:

 logging server host [severity-level [use-vrf vrf-name [facility facility]]]

If your syslog server is in vrf management, use:

switch(config)# logging server 5 172.21.3.191 use-vrf management 

Stay safe,

Sergiu

[thuy.hoang]

Hi Buddy,

Yes, i tried with the correct command and i can ping to logging server, but still not luck. Here is the output.

CoreSwitch_1(config)# ping 172.21.3.191 vrf default
PING 172.21.3.191 (172.21.3.191): 56 data bytes
64 bytes from 172.21.3.191: icmp_seq=0 ttl=127 time=1.437 ms
64 bytes from 172.21.3.191: icmp_seq=1 ttl=127 time=0.958 ms
64 bytes from 172.21.3.191: icmp_seq=2 ttl=127 time=1.032 ms
64 bytes from 172.21.3.191: icmp_seq=3 ttl=127 time=1.029 ms
64 bytes from 172.21.3.191: icmp_seq=4 ttl=127 time=1.015 ms
^C
--- 172.21.3.191 ping statistics ---
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0.958/1.094/1.437 ms
CoreSwitch_1(config)# show logging server
Logging server: enabled
{172.21.3.191}
This server is temporarily unreachable
server severity: notifications
server facility: local7
server VRF: default
server port: 514

I tried on another switch 2960X and it can send the logging to this server.

Thanks.

[thuy.hoang]

Hi @Sergiu.Daniluk ,

Finally, I got the logging from N3K. I removed then re-apply the command as you mentioned. I dont know why because the earlier command is the same.

Anyway, thank you so much for your help. You are hero.

Keep safe :)

[mosharaflink]

Hi @thuy.hoang  @Sergiu.Daniluk 

I am having the same problem with configuring syslog server on Nexus 3k.

I am using a different UDP port rather than the actual one. The server is working with another cisco switch except for nexus 3k. 

SW2(config)# logging server 192168.0.2 6 port 8514 use-vrf default facility syslog

SW2(config)# ping 192168.0.2
PING 192168.0.2 (192168.0.2): 56 data bytes
64 bytes from 192168.0.2: icmp_seq=0 ttl=60 time=1.268 ms
64 bytes from 192168.0.2: icmp_seq=1 ttl=60 time=0.876 ms
64 bytes from 192168.0.2: icmp_seq=2 ttl=60 time=0.755 ms
64 bytes from 192168.0.2: icmp_seq=3 ttl=60 time=0.797 ms
64 bytes from 192168.0.2: icmp_seq=4 ttl=60 time=0.93 ms

Stay safe.

Mosharaf

[Sergiu.Daniluk]

Hi @mosharaflink 

This is an old and closed thread. Open a different question in the appropriate technology section: https://community.cisco.com/t5/data-center-switches/bd-p/discussions-data-center-switches

Take care,

Sergiu