cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
684
Views
0
Helpful
2
Replies

SNMPtrap to two different server (in two different network)

maxime.creuset
Level 1
Level 1

Good morning,

We have an issue with the SNMPTRAP source IP (platform 3925).
We would like to send trap to two different server (which are in two different network).
For the first, server and router are in the same network.
For the second, server is in a network unknown by the router (it just have a route to join it)

When we don't configure an snmptrap source interface, the router use interface in the same network that the gateway to join the destination server.
It's ok for the first server (two entities are in the same network).
The second server is configured to received snmptrap from an IP not included in the same network that the gateway used to join it.
So when it received snmptrap, source IP is not that it expects and it delete.

We try to configure a NAT of the source IP used to send snmptrap but whitout success.
I think that it's due to NAT a packet generated by the router itself.

Have you solution or any idea to resolve this problem?

A second solution would be to include in IOS the possibility to configure many snmptrap source for many server like this :
router#snmp-server source-interface [X] [Y1] <= where [X] is the interface name and [Y1] the server destination IP.
router#snmp-server source-interface [X] [Y2] <= where [X] is the interface name and [Y2] the server destination IP.

Thanks for your help
Bests regards
Maxime

2 Replies 2

maxime.creuset
Level 1
Level 1

Good afternoon,

I have always the problem and always no idea.

Nobody has any idea?

Thanks for your help
Bests regards
Maxime

Hitesh Vinzoda
Level 4
Level 4

As i understand,

SNMP-SERVER (NEAR)>>>>>>RTR(SNMP)>>>>> WAN >>>> RTR-FAR >>> SNMP-SERVER(FAR)

You can NAT the SNMP traffic when it is reaching at the FAR-SERVER

on the FAR-RTR, you define a specific ACL to match source-address of the router used to generate SNMP TRAPS and destination as SNMP-SERVER(FAR) with destination port as 162.

Then source NAT it to one of the IP addresses from the FAR-SNMP-SERVER subnet.

HTH

Hitesh