Syslogging

Hi Aaron,

 

 

 

I ran the command tcpdump -i 0.0 host x.x.x.x and ran a ping to the remote syslog server I was seeing the packets on 0.0 and not eth0.

 

 

Very strange I ran the command bigpipe syslog list all and saw that the remote server was not listed when I'm sure it was added yesterday, so entered the following again bigpipe syslog remote server x.x.x.x then a b save then after doing this I was able to see packets using the command tcpdump -i 0.0 udp and host x.x.x.x, also I am seeing the packets for logger -p local0.debug "test message" on the same interface.

 

 

I am a little confused what 0.0 is, is this referencing the entire switch on any vlan? I would have expected to see the traffic on the management port eth0.

 

 

My config is setup as follows

 

External Vlan 1.1

 

Internal vlan 1.2

 

 

 

Is there a way of specifying syslog traffic to route over the management network or adding a static route in to send all traffic destined for the syslog server to go via the management network, I have tried via the GUI Network>Routes But get the following error

 

01070330:3: Static route gateway x.x.x.x is not directly connected via an interface. (when entering the IP address of the gateway for the management network)

 

 

Cheers,

 

 

Wilko