How to Configure SNMP on a BDCOM Switch or OLT: Step-by-Step Tutorial

Category: Networking Tutorials
Suggested URL Slug: snmp-configuration-bdcom-switch-olt
Focus Keyword: SNMP Configuration on BDCOM OLT
Meta Description: Learn how to configure SNMP on a BDCOM switch or OLT with step-by-step CLI commands, monitoring server setup, verification, and troubleshooting tips.

Introduction

SNMP (Simple Network Management Protocol) is an important protocol used by network administrators and Internet Service Providers (ISPs) to monitor and manage networking devices remotely.

If you operate a BDCOM GPON OLT, EPON OLT, or Ethernet switch, SNMP can help you monitor device availability, interface traffic, system information, and other supported network statistics from a centralized monitoring server.

In this tutorial, you will learn how to configure SNMP on a BDCOM device, connect it to a monitoring server, test SNMP communication, and troubleshoot common problems.

Important: BDCOM command syntax varies by model and firmware. The commands below are examples; verify them against your device’s CLI help or model-specific manual before applying them.

1. What Is SNMP?

SNMP stands for Simple Network Management Protocol. It allows a monitoring application to collect information from network devices.

For example, a network administrator can use SNMP to monitor:

• Device uptime and availability
• CPU and memory usage, where supported
• Ethernet interface status and traffic
• Bandwidth utilization
• Device identification and system information
• Supported optical, PON, and ONU statistics
• Network alerts and SNMP traps

SNMP is supported by many switches, routers, servers, and optical network devices, although the available metrics depend on the device and its Management Information Base (MIB).

2. SNMP Versions

There are three commonly encountered SNMP versions.

For production networks, SNMPv3 with authentication and privacy is recommended when supported by both the BDCOM firmware and monitoring software.

If SNMPv2c is required, use a strong community string, read-only access, and an access restriction that permits only your monitoring server.

3. Example Network Topology

Before configuring SNMP, prepare the IP addresses for your BDCOM device and monitoring server.

These addresses are examples only. Replace them with the actual management IP addresses used in your network.

The monitoring server must be able to reach the BDCOM device’s management IP address.

4. Step 1: Access the BDCOM Device

Connect to the BDCOM switch or OLT using its supported console or SSH management method.

After logging in, enter privileged mode and configuration mode.

Example:

Switch> enable
Switch# config

The exact command and prompt may differ by model. Some BDCOM devices use a prompt such as Switch_config#.

If your device uses different commands, check its CLI help or official configuration guide.

5. Step 2: Configure the SNMP Community

For SNMPv2c, the community string acts like a shared credential between the monitoring server and the device.

A documented BDCOM command format is:

Switch_config# snmp-server community 0 YOUR_STRONG_COMMUNITY RO

Replace YOUR_STRONG_COMMUNITY with a strong, unique value.

In this command format:

• snmp-server community configures the community string.
• 0 is a community-string type option in firmware that supports this syntax.
• YOUR_STRONG_COMMUNITY is the example placeholder.
• RO represents read-only access.

Note: Confirm the accepted parameters and read-only syntax on your particular BDCOM model. Do not configure read-write access unless you have a specific management requirement and understand the security implications.

6. Step 3: Configure the SNMP Monitoring Host

The monitoring server is the system that collects information from your switch or OLT.

For firmware supporting the following BDCOM command format, an example is:

Switch_config# snmp-server host 192.168.1.100 version v2c YOUR_STRONG_COMMUNITY authentication configure snmp

Replace:

• 192.168.1.100 with your monitoring server’s IP address.
• YOUR_STRONG_COMMUNITY with the same community string configured on the device.

This command format is firmware-dependent. If the device rejects it, use its built-in CLI help or the manual for the exact model rather than assuming the same syntax works on every BDCOM switch and OLT.

Also note that an SNMP polling configuration and an SNMP trap destination are separate functions on many devices.

7. Step 4: Save the Configuration

Some BDCOM platforms support the following command to save the configuration:

Switch_config# write all

Confirm that the command is supported on your device and that the configuration is saved successfully.

Saving the configuration helps preserve changes after a reboot.

8. Step 5: Verify SNMP Communication

After configuring SNMP, test whether your monitoring server can retrieve information from the BDCOM device.

On a Linux monitoring server with Net-SNMP utilities installed, run:

snmpwalk -v2c -c 'YOUR_STRONG_COMMUNITY' \
192.168.1.10 1.3.6.1.2.1.1

Replace the community string and device IP with your actual values.

The OID 1.3.6.1.2.1.1 represents the standard SNMP system group. It includes objects such as:

• sysDescr: System description
• sysName: System name
• sysUpTime: System uptime

If the command returns system information, basic SNMP polling is working.

If the request times out, check the device’s management IP, community string, SNMP version, routing, firewall rules, and any SNMP access restrictions.

Avoid sharing actual community strings in screenshots, articles, or public support forums.

9. Step 6: Add the BDCOM Device to a Monitoring System

After confirming SNMP communication, add the device to your preferred monitoring platform.

Option A: Zabbix

Zabbix can monitor supported SNMP devices, interfaces, and performance metrics.

General setup:

1. Log in to your Zabbix frontend.
2. Open the host configuration section.
3. Create a host for your BDCOM device.
4. Configure its SNMP interface with the device’s management IP.
5. Select a compatible template.
6. Configure the correct SNMP version and credentials.
7. Apply the configuration and check whether the host receives data.

For SNMPv2c, configure the community securely. For SNMPv3, configure the username, authentication protocol, authentication credential, and privacy settings required by the device.

Option B: LibreNMS

LibreNMS is a network monitoring platform designed to discover and monitor network equipment.

General setup:

1. Ensure the LibreNMS server can reach the BDCOM management IP.
2. Add the device using the appropriate SNMP version and credentials.
3. Run device discovery or use the platform’s supported discovery workflow.
4. Review discovered interfaces and traffic graphs.
5. Check whether additional BDCOM MIB support is required for vendor-specific metrics.

The available data depends on the device’s supported MIBs and the monitoring platform’s support for them.

Option C: PRTG Network Monitor

PRTG supports SNMP monitoring through compatible sensors.

General setup:

1. Add the BDCOM device to your monitoring configuration.
2. Set the device’s management IP address.
3. Configure its SNMP version and credentials.
4. Add suitable SNMP traffic or system-information sensors.
5. Verify that the sensors receive data.

Sensor availability and vendor-specific metrics depend on the device and PRTG configuration.

10. SNMP Ports and Firewall Requirements

SNMP monitoring normally uses these UDP ports:

For polling, allow traffic between the monitoring server and the device’s SNMP agent as required by your network and firewall configuration.

For traps, configure the device’s trap destination and allow the required traffic from the device to the monitoring server.

Do not expose SNMP management services directly to the public internet. Restrict access to trusted management networks.

11. Common SNMP Problems and Solutions

Problem 1: SNMP Request Times Out

Possible causes:

• Incorrect device IP address
• Incorrect community string
• SNMP agent or access restrictions
• Routing or firewall problems
• UDP port 161 blocked
• Monitoring server not permitted to query the device

Solution: First verify IP connectivity and routing. Then confirm the SNMP version, credentials, device configuration, and firewall rules.

Problem 2: Incorrect Community String

SNMPv2c requires the community string to match the device configuration.

Solution: Verify the configured string on both sides. Avoid including extra spaces or using a different string in the monitoring application.

Problem 3: Device Is Reachable but Interface Traffic Is Missing

The device may respond to basic SNMP queries but fail to provide the interface information expected by your monitoring platform.

Solution:

• Check interface discovery.
• Confirm that interface counters are available.
• Verify the relevant standard or vendor-specific MIBs.
• Confirm that the monitoring template supports the device.
• Check whether the firmware exposes the required metrics.

Problem 4: OLT or ONU Information Is Missing

Basic SNMP connectivity does not guarantee access to every GPON or EPON metric.

Solution: Check the exact BDCOM model, firmware, supported MIBs, and monitoring software compatibility. Vendor-specific OIDs may be required to retrieve PON, ONU, optical power, or other specialized information.

Problem 5: SNMP Traps Are Not Received

Polling and trap delivery are different operations. A device may respond to SNMP polling while failing to send traps.

Solution: Verify the configured trap destination, supported trap configuration commands, destination IP, UDP port 162, and firewall rules. Confirm that the monitoring application is listening for traps.

12. SNMP Security Best Practices

SNMP configuration should follow good network security practices.

• Prefer SNMPv3 with authentication and encryption where supported.
• Use read-only permissions for monitoring whenever possible.
• Use a unique and strong community string if SNMPv2c is necessary.
• Restrict SNMP access to authorized monitoring servers.
• Avoid exposing UDP ports 161 and 162 to untrusted networks.
• Do not publish credentials in documentation or screenshots.
• Review device logs and monitoring alerts regularly.
• Keep device firmware and monitoring software updated according to vendor guidance.

13. Frequently Asked Questions

What is the default SNMP port?

SNMP polling commonly uses UDP port 161. SNMP traps and informs commonly use UDP port 162 at the receiving monitoring system.

Can I monitor a BDCOM OLT using Zabbix?

Yes, if the device exposes the required SNMP objects and the Zabbix configuration or template supports them. Additional MIBs or templates may be needed for vendor-specific metrics.

Can SNMP show GPON ONU optical power?

It may be possible if the particular BDCOM OLT firmware exposes optical-power information through supported SNMP objects. Basic SNMP connectivity alone does not guarantee that this metric is available.

Is SNMPv2c secure?

SNMPv2c does not encrypt its community string or SNMP messages. Prefer SNMPv3 with authentication and privacy when supported. Otherwise, restrict SNMPv2c to a trusted management network.

Why does SNMP work from one server but not another?

Possible reasons include source-IP restrictions, different routing paths, firewall rules, credentials, or different SNMP versions. Check the source address and access permissions for each server.

Conclusion

SNMP is a useful tool for monitoring BDCOM switches and OLTs from a centralized network monitoring platform. With a correctly configured SNMP agent, authorized monitoring server, compatible MIBs, and appropriate security controls, network administrators can monitor device availability, interface traffic, and supported system metrics.

Always verify command syntax against the exact BDCOM model and firmware before making changes in a production network. For advanced OLT metrics, consult the vendor’s model-specific documentation.

More Networking Tutorials: Follow Network Info for practical networking guides, switch configurations, routing tutorials, and troubleshooting articles.