How to monitoring 3rd-party devices with RG-OCE-Network Manager(NM) via SNMP？

IIntroduction

The Ruijie OCE (Omni-Control Engine) is an easy and efficient on-premises network management solution for enterprise office,manufactory, K12 school, ISP and MSP to provide management features on local.The solutions include device deployment, monitoring, network optimization, and operational life cycle management; providing customers with plug-and-play deployment and operation and maintenance (O&M). It satisfies needs ofautomatic RF planning and user experience monitoring. Moreover, it supportsflexible wireless Wi-Fi management, including secure Private Pre-Shared Key(PPSK) authentication (one person, one machine, and one password), and third-party devices monitoring.

IITopology

III Key Configurations

1. Configure SNMP on the 3rd-party device

2. Add the 3rd-party device into the project on the RG-OCE-Network Manager service

IV configuration Steps

1. Configure SNMP on the 3rd-party device
The steps for configuration vary from model to model. Generally, the following parameters need to be configured.

SNMP Version:

• SNMP has multiple versions: SNMPv1, SNMPv2c, and SNMPv3.
  
• SNMPv1 is the original version, and it has limited security features.
  
• SNMPv2 cimproves upon SNMPv1, offering better performance and additional functionalitybut still lacks robust security.
  
• SNMPv3 introduces strong security features, including authentication, encryption, and access control, making it the preferred version for modern implementations.
  
  

User:

• In SNMPv3, User refers to the account used for accessing the SNMP-managed device.The user is associated with specific security credentials (authentication andencryption) and access privileges.
  
  

• In SNMPv1 and SNMPv2c, there is no user concept, but instead, access is controlledby "community strings" (essentially passwords), which can beread-only or read-write.
  
  

Group:

• In SNMPv3, Group refers to a logical grouping of users. A user can belong to oneor more groups, and each group has certain permissions (e.g., read, write, ornotify) on the SNMP data.
  
• The group concept allows administrators to define and manage different access levels based on roles.
  
  

Port Number:

• The port number specifies the communication end point for SNMP traffic. The default port for SNMP is 161 for general queries and 162 for receiving trap messages.
  
• These ports may be configurable, but the default is widely used unless there’s aspecific need for a custom configuration.
  
  

Community:

The device needs to be configured with the samecommunity name as the OCE server.

• The community in SNMP is a string used for access control (especially in SNMPv1 andSNMPv2c).
  
• The community string is essentially a password or key that governs the level of access a user has to an SNMP-managed device. It can be：
  
• Read-onlycommunity: Allows only reading data from the device (e.g.,
  public
  ).
  
  
  • Read-writecommunity: Allows both reading and modifying device data (e.g.,
    private
    ).
    
    
  </li>

NMS Server Name:

• NMS(Network Management System) Server Name refers to the hostname or IP address ofthe server that will receive and process SNMP data from the devices beingmonitored.
  
• Thiscould be a centralized monitoring system or a specific software tool used tomanage the network devices.
  
• Name of the Host Sending Trap Packets (Trap):
  
• Thisrefers to the source device or host sending SNMP traps (unsolicitednotifications) to the NMS or monitoring system.
  
• Atrap is a notification sent by a device (such as a router, switch, or firewall)to alert the NMS of specific events, such as errors or status changes.
  
  

Authentication Mode:

AuthenticationMode is used in SNMPv3 to ensure that the SNMP message comes from a legitimatesource and has not been tampered with.

Common authentication modes are:

No Auth(no authentication) – messages are not authenticated.

Auth– authentication is performed using a hash function (e.g., MD5 or SHA).

Authenticationensures data integrity and verifies the source of SNMP requests.

Encryption Algorithm:

Encryption Algorithm is used in SNMPv3 to protect the confidentiality of the SNMP message.

Encryption is applied after authentication, ensuring that the data is protected fromeavesdropping.

Common encryption algorithms include DES, AES-128, AES-192, and AES-256.

The encryption ensures that sensitive information, such as configuration data or performance metrics, is not visible to unauthorized parties.

2. Add the third party device into the project
Navigate to "Device -> Third-Party Devices" page and click "Add Third-Party Devices"

Input following parameters and click "OK"

IP Range: Indicates the IP range where the deviceis located.

Port: Indicates the SNMP port. The default value is161.

SNMP protocol version: Indicates the SNMP protocolversion. SNMP v2 and SNMP v3 are supported.

Community Name: Indicates the SNMP community name.

V Verification

Click the icon of the 3rd-party device to enter the monitoring page

Information including interface statistics, log history will be listed in the page.