11-18-2013 07:55 AM - edited 03-01-2019 11:21 AM
Hello
This topic is by way of confirmation of a fact rather than how to do something.
We have a 3rd party who want definitive confirmation that the CIMC platform (v1.4) is sending traps on the default port udp/162 - (so that f-w rules can be configured)
The docos say how to set up snmp traps, and do not mention setting a custom port, so my take on it is that traps are using udp/162 as per standard practice.
Also supporting this thoery is the previous section in the docs, which say snmp udp/161 cannot be altered for comms to the platform.
Has anyone seen any docs stating udp/162 is fixed as the trap port or has knowledge of this being the case.
I believe it to be so, we just need to prove it to somebody else.
Ian
11-18-2013 04:03 PM
Hi Ian,
The Cisco C-Series Standalone Servers use port 161 for SNMP and this is statically assigned. Based on your references above, it appears that your CIMC is running v1.4 so I have provided a link below to configuring and querying SNMP configuration through the CLI for this CIMC version.
Jeff Foster
11-19-2013 02:26 AM
Hi Jeff,
Thanks for the info, but the link you have given is the same doc as I posted at the start of the thread.
While I reliase udp/161 is the port to talk 'to' the platform on, it would be highly unusual to send traps on the same port.
Unfortunately the docs. don't explicitly state this, if it were to be true, so I'm after answer that either says :
- Yes, we send traps (FROM the agent TO the snmp server) on the conventional port udp/162.
OR
- No, we don't use udp/162, we choose the highly unusual option of sending out traps on udp/161 which is normally used for inbound SNMP comms to an agent.
Rgds
Ian
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide