You may want to try another way. I have my IDSM blades reporting to two different locations(The IDS MC and another device that listens for PostOffice). To do that, select the device. Under TOC for that device, select remote host and add a second host.
I should have mentioned that I had considered that. I run 25+ probes, and the destination, other than IDS MC, that I want all alerts to go to is a system located behind two firewalls; would require lots of rules.
Anyway, looks like I'll just be manually editing the postoffice configuration files; routes, hosts, smid, destinations etc.
Editing the routes and hosts files may setup the communication channel, but it is smid that actually forwards the alarms.
The routes and hosts files also get dynamically modified when sensors are added or removed by Security Monitor.
Smid in CSPM and the Unix Director both support the forwarding of alarms to other boxes. The smid used in Security Monitor, however, is not the same smid used in CSPM. In fact Security Monitor's own processes replace the older traditional smid in order to boost performance, and so will ignore any changes you might make to smid.conf.
The forwarding of alarms by Security Monitor is on the list of requests for future versions.
In CSPM and Unix Director the multi-tier system was more necessary because each GUI could really only support one local user. So a remote user needed forwarded copies of the alarms.
With the Security Monitor, however, there is now multi-user support. If the users at the higher tier system needed to view alarms on Security Monitor then you can simply allow an incoming web connnection (configure the firewalls to allow it) from the ip addresses of the users on the higher tier to access the Security Monitor and even the IDS Management Center of the lower tier. You can even give the higher tier users their own usernames/passwords and can restrict their access if necessary, and the connection can be encrypted with SSL.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR
and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity
options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in
HA DocumentationCode download linksGoalRequirementLimitationsSupported
ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationCo...
Question I am currently unable to specify "crypto keyring" command when
configuring VPN connection on my cisco 2901 router. The following
licenses have been activated on my router :