Page History

If the remote syslog server IP is not routed by the default mgt0 routing rule (for example, if the remote server is in the same subnet as a PKT interface), you must create a static route to route the traffic to that syslog server through the mgt0 The SBC Syslog configuration does not provide a setting for specifying an Interface to use for connectivity to remote syslog servers; instead, the interface is decided using the configured Static Routes. The SBC application automatically creates an ACL to allow connections from the remote server to the mgmt interface. If traffic to the remote server is routed out of a different interface due to the configured Static Routes, then you must either add a new Static Route to route the traffic out of the mgmt interface, or create a new ACL for that interface.