S series switch enabled with SNMP failed to communicate with a third-party device


Check the following items if an S series switch (except S1700) enabled with SNMP failed to communicate with a third-party device:
1. Whether there are reachable routes between the device and the third-party device.
2. Whether SNMP access control is configured.
3. Whether SNMP is correctly configured, such as community name, group name, user name, version, and port number.

Other related questions:
How do I configure SNMP community name on S series switches
The snmp-agent community { read | write } community-name command can be used to configure community names on S series switches (except S1700). read indicates the read permission and write indicates the write permission. If the same community name is configured, the latter configuration overwrites the earlier community name. The following provides an example: [HUAWEI] snmp-agent community write community001 Community complexity check needs to be performed when SNMP community names are configured on S series switches (except S1700) in versions after V200R002. Community complexity requirements are as follows: 1. The community name must contain at least eight characters. The set password min-length command sets the value of minimum password length which must equal to or be larger than 8. 2. The community must be a combination of at least two of the following: uppercase letters A to Z, lowercase letters a to z, digits, and special characters (excluding question masks). You can use the snmp-agent community complexity-check disable command to disable community name complexity check on a switch. After community name complexity check is disabled, the value of community name length is an integer in the range 1 to 32. The configuration method is as follows: [HUAWEI] snmp-agent community complexity-check disable Note: If a configured community name does not meet complexity requirements, the system is prone to attacks including password cracking from malicious users, affecting system security. Therefore, it is recommended that community name complexity check be enabled.

SNMP port numbers of S series switches
After SNMP is configured on S series switches (except S1700), UDP ports are enabled by default. By default, the port number for SNMP and NMS connection is 161 and the port number for sending alarms to the NMS is 162.
You can use the snmp-agent udp-port port-num command to configure the port number for SNMP and NMS connection.

What is the peripheral policy in FusionCloud?
FusionCloud 6.x supports the following third-party devices: F5 and RadWare load balancers. The F5 load balancer is recommended. Load balancer (F5): In FusionCloud 6.1, the mapping device model is F5 BIG-IP 2000S/4000S, the operating system version is V12.1.X or later, and the plug-in version is In FusionCloud 6.0, the mapping device model is F5 BIGIP LTM 2000S, the operating system version is V12 or later, and the plug-in version is 9.3.3.b2. The F5 company provides information about the device models, operating system and plug-in versions, and sales strategies in China and outside China. Load balancer (Radware): The mapping device model is Radware Alteon5224 and the mapping version is SLB The device does not support network automation. In other words, manual configuration is required.

Can the U1900 series unified gateway interconnect with a third-party device
The U1900 series unified gateway supports the standard SIP protocol. If a third-party device uses the SIP protocol, you can try interconnecting this device with the U1900. During interconnection testing, run the following command to set the value of software parameter 286 to 0: config softargu type 286 value 0.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top