Hello, dear!
Have a nice day!
Possible cause:
The SNMP server reports the same msgAuthoritativeEngineID value for the two configurations.
1. Check whether the authentication failure is recorded in logs..
On the OperationCenter page, choose System > Connection Management > Data Report Configuration > Configure Local SNMP, check the security username, password, security protocol, and encryption protocol used for interconnection. The check result shows that configurations on OperationCenter are the same as those on FusionManager and ServiceCenter. Therefore, the authentication failure is not caused by inconsistent usernames, passwords, or protocols.
2. Download the tcpdump tool from the official website and collect packets captured using this tool on the OperationCenter server.
Capture packets as follows:
Log in to the OperationCenter server and switch to user root.
Run the tcpdump -i any port 10163 -nnAs 65535 -vv -w /opt/10163.cap command to capture packets.
This command is used to capture all packets sent to port 10613. The captured packets are automatically saved in file 10613.cap in the /opt directory.
3. Download the Wireshark tool from the official website, use this tool to open this file, and view the packet information.
Check the msgAuthoritativeEngineID value contained in the SNMP packets sent from two FusionManager systems to OperationCenter. The result shows that the two values of msgAuthoritativeEngineID are the same. msgAuthoritativeEngineID uniquely identifies the SNMP station authentication. The conflict values lead to authentication failure.
Troubleshooting Procedure
When OperationCenter interconnects with two FusionManager systems, configure SNMP using SNMPv3 for one interconnection and SNMPv2 for the other interconnection.
Alternatively, use SNMPv2 for both interconnections, as shown in the following figure.
Any further questions, let us know!
.gif)
