For the syslog message processing and forwarding scenario, a syslog daemon that is running on a remote system collects the syslog messages from the managed devices that are running the BGP or OSPF protocols. The daemon then writes the messages to a single syslog file on the remote system.
A user installs a separate instance of the Network Protocol Management Suite on the remote system and manually starts two instances of the built-in syslog adapter:
An instance started as a BGP syslog adapter to serve Network Protocol Manager for BGP.
An instance started as an OSPF syslog adapter to serve Network Protocol Manager for OSPF.
To configure syslog message processing and forwarding:
On the local system, where the Network Protocol Manager for BGP or Network Protocol Manager for OSPF reside, ensure that the value of the SyslogName parameter in the BASEDIR/smarts/conf/bgp/bgp.conf file or the BASEDIR/smarts/conf/ospf/ospf.conf file is set to "" (empty string).
On the remote system, where the syslog file resides, install an instance of the Network Protocol Management Suite.
During the installation, do not install any of the Network Protocol Manager products as services.
On the remote system, go to the BASEDIR/smarts/bin directory in the Network Protocol Manager installation area and start the syslog adapters.
A sample command line for a target Network Protocol Manager for BGP named INCHARGE-BGP is:
sm_adapter --name=INCHARGE-BGP-SYSLOG --server=INCHARGE-BGP --output=BGP-SYSLOG --daemon --tail=<full path to log file> bgp/bgp-syslog.asl sm_adapter --name=INCHARGE-OSPF-SYSLOG --server=INCHARGE-OSPF --output=OSPF-SYSLOG --daemon --tail=<full path to log file> ospf/ospf-syslog.asl