In Smarts, other domains like APM, BGP, OSPF can act as Trap receiver where forwarder rule is added in Trap Exploder which will then be received by respective domains based on port number configured respectively.
Smarts - 10.1.x
Trap receiver is activated by editing the appropriate <Smarts NPM_suite>.conf configuration file for each Smarts NPM suites like ospf.conf, bgp.conf.
The ospf.conf and bgp.conf files are installed by Smarts in the following directories:
Edit domain respective file to activate the corresponding OSPF/BGP trap receiver:
MSI_AdapterManager::BGP-Adapter-Manager {
Config = "bgp"
TrapPort = 162
TraceTraps = TRUE
The NPM trap listener will be automatically started using the port configured (as long as the port is available). The domain log will report if the trap listener has been started successfully.
Example:
In domain log, line "[March 10, 2025 at 10:49:15 PM MDT +404ms] t@1295947520 Trap-Driver-BGP-Adapter-Manager
ASL_MSG-*-ASLP-bgp/bgp-traps.asl: March 10, 2025 at 10:49:15 PM MDT bgp-traps.asl: Activated on port number 162" will be printed.
Trap Trace can be enabled from bgp.conf file as explained in above section or as below:
./dmctl -s <NPM-DOMAIN> put MSI_AdapterManager::<NPM>-Adapter-Manager::TraceTraps TRUE
Example:
./dmctl -s LAB-BGP put MSI_AdapterManager::BGP-Adapter-Manager::TraceTraps TRUE