Addition details with OCP4.8 /4.10:
• OCP 4.10 uses OVN-Kubernetes for cluster networking since we have Dual stack enabled here from cluster level, and in Openshift 4.8 cluster networking is Openshift SDN since it is only IPv4.
You probably meant “securityEngineID” instead “contextEngineID” right?
The security engine ID I discovered from the agent if auto-discovery is enabled in SNMP4J.
As the discovery mechanism is standardised, there must not be any compatibility issue.
Thanks for the reply!
SNMP agent is a net-snmp module in the network element.
SNMP4J is the management pod - which sends get/set requests to net-snmp agent.
When sending get requests from SNMP4J management pod - context engineId which identifies the network element is not sent in the PDU in OCP4.10 where as context engineID is sent in OCP4.8.
The network element identifies the PDU with contextEngineId and responds to the SNMP4J pod but does not respond when context engineID is not in PDU in OCP4.10.
If the contextEngineID is not set (i.e., is empty) in the ScopedPDU to be sent then there are two options:
If the contextEngineID is empty (null) and there is a contextEngineID discovered for the target address, then this will be used. Otherwise, if target is a SecureTarget, the contextEngineID is discovered according to the method defined in RFC 5343.
It will be set to the authoritative engine ID by MPv3.prepareOutgoingMessage.