Highlighted
Robert_Day1
1 Copper

Multiple Trap Adapters --> Multiple OI Servers

Hi Everyone,


We are trying to build out our new Smarts environment.  Our design includes 1 server where 3 trap adapter instances run and listen on different ports.  Our company can be separated into 3 sections.  Each of these three sections traps to a different trap adapter.  We also have 3 separate SAM servers.  What we need to figure out is how to set up our trap adapters to they each forward to a different OI. 

Any help on this would be awesome.

Rob

0 Kudos
1 Reply
DanMajor
1 Copper

Re: Multiple Trap Adapters --> Multiple OI Servers

Gday Rob,

We do something similar. We currently have a central trap exploder that based of the originating IP address of the trap then forwards the trap to one of six region-based exploders (our deployment is broken down into geographical regions because of the size of our network). Each region has it's own SAM/OI/IP/NPM domains in it and all the SAM components run off the one server and the IP/NPM off another.

We've achieved this by using the SM_SITEMOD and SM_WRITEABLE environment variables in the service definitions to specify a different local folder structure for each region on the one server.

Below is the sm_service --cmdline output for two of our regional trap exploders as an example (East Aus and Central West Aus regions):

East Region

sm_service install --force  --unmanaged  --startmode=manual \

'--name=east-trapd-rcvr' \

'--description=EAST SNMP Trap Receiver Adapter' \

'--env=SM_SITEMOD=/opt/InCharge8/SAM/smarts/local-east:/opt/InCharge8/SAM/smarts/local:/opt/InCharge8/SAM/smarts' \

'--env=SM_WRITEABLE=/opt/InCharge8/SAM/smarts/local-east' \

'/opt/InCharge8/SAM/smarts/bin/sm_trapd' \

'--name=CCNP-EAST-TRAP-RCVR' \

'--server=CCNP-EAST-TRAP-OI' \

'--config=icoi' \

'--port=42413' \

'--sport=42412' \

'--model=sm_actions' \

'--rules=icoi-trapd/trap_mgr_parse.asl' \

'--output=CCNP-EAST-TRAP-RCVR.log'

Central West Region

sm_service install --force  --unmanaged  --startmode=manual \

'--name=east-trapd-rcvr' \

'--description=EAST SNMP Trap Receiver Adapter' \

'--env=SM_SITEMOD=/opt/InCharge8/SAM/smarts/local-east:/opt/InCharge8/SAM/smarts/local:/opt/InCharge8/SAM/smarts' \

'--env=SM_WRITEABLE=/opt/InCharge8/SAM/smarts/local-east' \

'/opt/InCharge8/SAM/smarts/bin/sm_trapd' \

'--name=CCNP-EAST-TRAP-RCVR' \

'--server=CCNP-EAST-TRAP-OI' \

'--config=icoi' \

'--port=42413' \

'--sport=42412' \

'--model=sm_actions' \

'--rules=icoi-trapd/trap_mgr_parse.asl' \

'--output=CCNP-EAST-TRAP-RCVR.log'

Using the SM_SITEMOD/SM_WRITABLE like we have means that we can have configurations/scripts defined at the region level (local-east/conf/etc), or the general level (local/conf/etc) before failing back to defaults.

Is this the sort of thing you're trying to achieve?

Dan.