olecoot Posted October 22, 2007 Report Share Posted October 22, 2007 I have several servers that I would like to pull PBXnSIP information via SNMP. I have a working NMS system that I would like to use. Using the information from the WIKI SNMP document, I cannot get the desired results. I used the free version of PRTG and was able to pull the information but do not want to have to purchase additional software packages to monitor PBXnSIP. Why would I not be able to get the same information via a SNMP compliant Network Manager? Quote Link to comment Share on other sites More sharing options...
gotvoip Posted October 22, 2007 Report Share Posted October 22, 2007 It should work. Did you turn on snmp logging and see what the messages were there? Log SNMP events: YesNo I usually set the log level to 9 and just turn on snmp and see what you get when you poll it. Quote Link to comment Share on other sites More sharing options...
olecoot Posted November 5, 2007 Author Report Share Posted November 5, 2007 I can get a response from pbxnsip via snmpget: [root@nms-1 ~]# snmpget -v 1 -c public 10.1.0.12 .1.3.6.1.4.1.25060.1.3 SNMPv2-SMI::enterprises.25060.1.3 = INTEGER: 636 [root@nms-1 ~]# snmpget -v 1 -c public 10.1.0.12 .1.3.6.1.4.1.25060.1.6 SNMPv2-SMI::enterprises.25060.1.6 = INTEGER: 11 How do I change the community string from public to something else? Thanks It should work. Did you turn on snmp logging and see what the messages were there? Log SNMP events: YesNo I usually set the log level to 9 and just turn on snmp and see what you get when you poll it. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 5, 2007 Report Share Posted November 5, 2007 How do I change the community string from public to something else? You can't. That string is hard coded. Is there any need to change it? Quote Link to comment Share on other sites More sharing options...
olecoot Posted November 5, 2007 Author Report Share Posted November 5, 2007 Actually there is ... We use our own community strings. You can't. That string is hard coded. Is there any need to change it? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 5, 2007 Report Share Posted November 5, 2007 Can't you change it to "public" in order to get things working? Quote Link to comment Share on other sites More sharing options...
olecoot Posted November 7, 2007 Author Report Share Posted November 7, 2007 I've done that in our "test" environment but company policy requires our own RO community string in the production equipment. Perhaps this can be included in a future release? Thanks Can't you change it to "public" in order to get things working? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 7, 2007 Report Share Posted November 7, 2007 Please give http://www.pbxnsip.com/download/pbxctrl-2.1.1.2205.exe a shot. There is a new setting in the Admin Settings/Ports section. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.