Abstract: This tutorial will guide the new comer on how to configure the FMUX04
with SNMP option for management and how to access the enterprise MIB for ...
FMUX04 SNMP Tutorial
Abstract: This tutorial will guide the new comer on how to configure the FMUX04 with SNMP option for management and how to access the enterprise MIB for monitoring Optical signal/BER and E1/T1 channel status (OK, LOS, BPV). Requirements: FMUX04 w/SNMP version 1.12 MIB file version 1.13 1:1 DB9F to DB9M console cable Ethernet cable Management PC (in this example using MG-Soft MIB browser) Setup: Connect AC power to the FMUX04. Connect the console cable from FMUX04 to PC running terminal emulation (in this example we use PuTTY). Do not connect LAN to SNMP port yet. Configure the terminal emulation for 19200,8,N,1 Procedure: 1. Power on the FMUX04 and allow a few seconds to boot.
2. Press the [Enter] key to display the login screen.
3. Press 1 to do local login (factory default requires no password)
4. Press 2 to Configure System
5. Press 7 to enter SNMP configuration
The SNMP Agent is the FMUX04’s SNMP engine. This is where the IP address, mask and gateway are set. The manager configuration is where we assign managers the authority to access the Agent via SNMP. Manager’s are set by IP address and assigned community strings as well as being able to enable trap messages to be sent. 6. Press 1 to setup the SNMP agent.
7. Press 1 to set the agent’s IP address. Enter the address without dots and include any leading zeros. For example, to set the address 172.24.1.120, key in 172024001120. Press 2 to set the subnet mask and press 3 to set the default gateway address. Below is an example of the unit setup for this lab exercise.
8. Press [ESC] to return to the SNMP configuration screen
9. Press 2 to enter the manager setup screen.
10. 11. 12. 13.
Press 5 and set the R/W community string; in this example we are making it ‘private’ Press 6 and set the read-only community string; in this example we are making it ‘public’ Press 2 and enter all zeros, press 2 to set community Read-only and press 2 to disable traps. Repeat for items 3 & 4
Now we have both community strings set and we have cleared out the access IPs for 2,3&4.
14. Press 1 and key in the IP address of the NMS or management PC (172.24.1.251 in our example) Press 1 to use R/W community string for access and press 1 again to enable sending traps to this manager. The screen will now look like this:
15. After verifying the settings on the above screen, press [ESC] to return to the SNMP configuration page.
16. Press 4 to save settings and reboot the SNMP agent. This will take about 20 seconds so wait for it. 17. Connect the FMUX04 SNMP LAN port to the network with the management PC. 18. From the management PC, ping the FMUX04 SNMP agent to be sure it can be reached on the network.
(In our example, our manager is at 172.24.1.251 and the FMUX04 SNMP agent is 172.24.1.120.)
The following screens were captured using the MG-Soft MIB Browser software. Trial versions are available from MG-Soft. You can use these as an example on how to access FMUX04 SNMP for management. 19. Key in the agent’s IP address and click the tool. A popup window appears. Select SNMP v1, enter ‘private’ into both the Read and Set community and click OK.
20. Immediate the agent should reply with its uptime. We have good communication and SNMP is responding.
21. Select the MIB compiler tool. The compiler will pop up. From the ‘File’ menu, select Compile.
22. Browse to and select the MIB file for the FMUX04, click Open. MIB will be compiled.
23. After the compilation has finished, the save dialogue box will appear. Select the item and save or just click Save All. Place in the default folder.
24. Refresh the folders, find the compiled MIB in the lower window, move it to the upper window.
25. Switch to the Query tab and open the tree to the localOptical; do SNMP walk.
When localOpticalLOS is off, the fiber link is good.
Disconnect the fiber link. A number of trap messages will be received, but most note worthy is the optical signal LOS on.
Besides the unsolicited trap messages, we may also poll the NMSP agent to view the localOpticalLOS status.
Additionally, we may also poll the E1/T1 connection status. Under normal condition, the localChxLOS will be off.
If we disconnect CH1 E1/T1 signal and then re-poll the SNMP, the localCH1LOS will be on.
The ‘Alarm Buffer’ which hold the last 100 alarm events can also be read via SNMP.
