For any customers of NetScout Systems out there you may have been thoroughly frustrated with their complete lack of focus, support, prioritization of systems management. Essentially, they neither support nor sanction any third party monitoring tool of their devices. However, since these products cost well over $40,000 each the thought of not monitoring performance and availability is anathema. As a result, I have had be somewhat creative in my approach. I have found some successful ways to do this using and modifying the /etc/snmp/snmpd.conf file. Basically, their Infinistreams run an extremely old version of Fedora Core (FC6) if you can believe it. However, since this is an open source OS it does support the NET-SNMP utilities.
Since the NetScout application itself listens on Port 161, adding this to solarwinds is really not an effective way of managing this box/tool. You need to treat the box as a box and the applications as an application. Monitoring the application on port 161 is really useless.
So here's what you need to do.
Make a backup of existing snmpd.conf file
cp /etc/snmp/snmpd.conf /etc/snmp/snmpd.orig
Next edit your snmpd.conf file
vi /etc/snmp/snmpd.conf
# sec.name source community
com2sec notConfigUser default newsnmp
Add to this line
# Make at least snmpwalk -v 1 localhost -c public system fast again.
# name incl/excl subtree mask(optional)
view systemview included .1
Modify this line
# Finally, grant the group read-only access to the systemview view.
# group context sec.model sec.level prefix read write notifaccess notConfigGroup "" any noauth exact all none none
Here's the most important piece...you have to BIND SNMPD.CONF to another UDP Port so add this line anywhere in the snmpd.conf file.
agentaddress infinistreamnameoripadd:10001
Probably good to modify Syslocation and syscontact too
Finally if you want it to show up in the Resources Object tree as a NetScout device you would also add this line anywhere in the file
sysObjectID 1.3.6.1.4.1.141.2.1
# ----------------------------------------------------------------------------- # ----------------------------------------------------------------------------- # -----------------------------------------------------------------------------# ----------------------------------------------------------------------------- Finally, in order to ensure that your IPTABLES can allow this to work..you need to modify IPTABLES to allow NPM to reach the box.
Here's how you do that
iptables -I RH-Firewall-1-INPUT -s 0/0 -p udp --destination-port 10001 -j ACCEPT
/etc/init.d/iptables save
/etc/init.d/iptables stop
/etc/init.d/iptables start
To make sure it worked you want to do this
service iptables status | grep 10001
Next you want to start snmpd so
service snmpd start
Next you want to make sure this works on reboot so add this line
chkconfig snmpd on
Now you will get inside your Orion something like this


Now you can use the Process Explorer in APM to watch for the key application processes which happen to be:
Hope this helps you all.