Road Runner Guide to the Internet
SNMP Scanning Tutorial
using SNMP CFG Admin 1.8
the following guide is not exactly for beginners & assumes anyone who reads it has an understand of this tutorial, or similar tutorial before hand. this guide will explain how to specifically tweak snmp cfg admin 1.8 to work in its most efficient manner when using roadrunner networks.
[the following method would be very similar among all cable isps]
snmp scanning polls thousands of modems for very specific information based on which oids you use for each particular scan. every oid you add is like asking another question. the more oids u add, the longer it takes to complete the scan, the less results u will get, & your cpu usage will continue to climb, nulling untold fortunes & riches of yore.
in other words...dont load up the oid box, its not gonna work right. the reason for that is not all modems are created equal. many dont respond to to the popular oids lists floating around the net. in fact, modems using rr networks dont seem to respond to most popular oids or even use unique oids which can only be discovered using solarwinds or trial & error.
typically the fastest configs are the business class configs [prefix begins with isrc instead of isrr] tend to use modems that respond to even less oids making them ever harder to find. but luckily they all currently respond to the config oid. and thats the only oid u will "need" for your scans.
...which means, if u only use the config oid in your scan u will see the business class configs that would normally be filtered out. the config oid must be used by itself in order for snmp cfg admin to work properly!
in addition, u also have to make sure that the range ur scanning is using the same tftp server as ur local connection. if the hfc ips from your scan uses a different tftp server, then the macs on those hfc ips wont work. u can find out what server their using by adding the tftp oid to your scan. its one of the few [if only] oids u can add to the scan that still gives you a shit ton of results. but i would remove the tftp oid from the scan once u know which hfc ranges use what tftp servers [incase some modems dont reply]
but we are still missing a key piece of information...the mac. from your results in your snmp scan you should have a list of config file names. click the "plus" sign next to the config name you want to use and that ip address below the config name is the modems hfc ip. the final step on the seemingly endless quest for the mac is u enter the hfc ip into a program called "solarwinds" [refer to solarwinds tutorial] to retrieve the holy mac .
below is a tried and tru configuration setup. follow it very closely...
connect directly to modem [no routers, switches, etc]
install snmp cfg admin [follow the readme file]
oid: 1.3.6.1.2.1.69.1.4.5.0 and/or 1.3.6.1.2.1.69.1.4.4.0
wait time ms: 4-10ms [single core cpus should increase wait time]
limit ips: one is plently
hfc range: 65,000 ips
ex: 10.50.0.0 - 10.50.255.255 [less ips the better]
port: always 161
*after about 30,000 configs found the program starts to crap out and begins to count in negatives. it also starts to get veryyy slowww and inefficient
*be sure ur cpu usage does not stay above 90% during the scan. if it does, stop the scan, increase "wait time" if you dont, ur scan could skip valuable configs.