From: Aiello, S. \(G. C. consultant\) <ste...@ge...> - 2007-01-23 15:11:46
|
Check the docs/TEMPLATE file, below is a snippet: The 'sysdesc' variable is used by the type auto-detection that Devmon does when it initially reads the host from the bb-hosts file (when using the --readbbhosts command line argument). This value should be unique when compared to the value of the other templates. It's a regular expression, so you can match a fairly complicated pattern, if you so desire. You can also hardcode a device to use a specific template via the DEVMON tag used in the bb-hosts file, DEVMON:model(vendor;model). See docs/USING for more info on options that can be used with the DEVMON tag. > -----Original Message----- > From: dev...@li...=20 > [mailto:dev...@li...] On=20 > Behalf Of Jeff Horn > Sent: Tuesday, January 23, 2007 10:03 AM > To: dev...@li... > Subject: [Devmon] Creating a template for Devmon >=20 >=20 > I have been trying to create a template to use with a=20 > Neoteris Secure Access Server, but I can't seem to get the=20 > specs file right to work with the device. I run "devmon -vvvv=20 > --readbbhosts" and get the message "No matching templates for=20 > device: myserver". Here is the output from snmpwalk. Which=20 > string should I use for the vendor or model in the specs=20 > file? Which parameter in the specs file is supposed to be the=20 > one to match with the device information expected when devmon=20 > starts up? I also have the device mib from Juniper, but it=20 > doesn't really give me much more to go on. >=20 > Jeff >=20 > SNMPv2-MIB::sysDescr.0 =3D STRING: SA-4000=20 > SNMPv2-MIB::sysObjectID.0 =3D OID: UCD-SNMP-MIB::unknown=20 > SNMPv2-MIB::sysUpTime.0 =3D Timeticks: (34392654) 3 days,=20 > 23:32:06.54 SNMPv2-MIB::sysContact.0 =3D STRING: Jeff=20 > SNMPv2-MIB::sysName.0 =3D STRING: Secure Access Server=20 > SNMPv2-MIB::sysLocation.0 =3D STRING: Machine Room=20 > SNMPv2-MIB::sysServices.0 =3D INTEGER: 72=20 > SNMPv2-MIB::sysORLastChange.0 =3D Timeticks: (1) 0:00:00.01=20 > SNMPv2-MIB::sysORID.1 =3D OID: IF-MIB::ifMIB=20 > SNMPv2-MIB::sysORID.2 =3D OID: SNMPv2-MIB::snmpMIB=20 > SNMPv2-MIB::sysORID.3 =3D OID: TCP-MIB::tcpMIB=20 > SNMPv2-MIB::sysORID.4 =3D OID: IP-MIB::ip SNMPv2-MIB::sysORID.5=20 > =3D OID: UDP-MIB::udpMIB SNMPv2-MIB::sysORID.6 =3D OID:=20 > SNMP-VIEW-BASED-ACM-MIB::vacmBasicGroup > SNMPv2-MIB::sysORID.7 =3D OID:=20 > SNMP-FRAMEWORK-MIB::snmpFrameworkMIBCompliance > SNMPv2-MIB::sysORID.8 =3D OID: SNMP-MPD-MIB::snmpMPDCompliance=20 > SNMPv2-MIB::sysORID.9 =3D OID: = SNMP-USER-BASED-SM-MIB::usmMIBCompliance > SNMPv2-MIB::sysORDescr.1 =3D STRING: The MIB module to describe=20 > generic objects for network interface sub-layers=20 > SNMPv2-MIB::sysORDescr.2 =3D STRING: The MIB module for SNMPv2=20 > entities SNMPv2-MIB::sysORDescr.3 =3D STRING: The MIB module=20 > for managing TCP implementations SNMPv2-MIB::sysORDescr.4 =3D=20 > STRING: The MIB module for managing IP and ICMP=20 > implementations SNMPv2-MIB::sysORDescr.5 =3D STRING: The MIB=20 > module for managing UDP implementations=20 > SNMPv2-MIB::sysORDescr.6 =3D STRING: View-based Access Control=20 > Model for SNMP. SNMPv2-MIB::sysORDescr.7 =3D STRING: The SNMP=20 > Management Architecture MIB. SNMPv2-MIB::sysORDescr.8 =3D=20 > STRING: The MIB for Message Processing and Dispatching.=20 > SNMPv2-MIB::sysORDescr.9 =3D STRING: The management information=20 > definitions for the SNMP User-based Security Model.=20 > SNMPv2-MIB::sysORUpTime.1 =3D Timeticks: (0) 0:00:00.00=20 > SNMPv2-MIB::sysORUpTime.2 =3D Timeticks: (0) 0:00:00.00=20 > SNMPv2-MIB::sysORUpTime.3 =3D Timeticks: (0) 0:00:00.00=20 > SNMPv2-MIB::sysORUpTime.4 =3D Timeticks: (0) 0:00:00.00=20 > SNMPv2-MIB::sysORUpTime.5 =3D Timeticks: (0) 0:00:00.00=20 > SNMPv2-MIB::sysORUpTime.6 =3D Timeticks: (0) 0:00:00.00=20 > SNMPv2-MIB::sysORUpTime.7 =3D Timeticks: (1) 0:00:00.01=20 > SNMPv2-MIB::sysORUpTime.8 =3D Timeticks: (1) 0:00:00.01=20 > SNMPv2-MIB::sysORUpTime.9 =3D Timeticks: (1) 0:00:00.01=20 > IF-MIB::ifNumber.0 =3D INTEGER: 13 IF-MIB::ifIndex.1 =3D INTEGER:=20 > 1 IF-MIB::ifIndex.2 =3D INTEGER: 2 IF-MIB::ifIndex.3 =3D INTEGER:=20 > 3 IF-MIB::ifIndex.4 =3D INTEGER: 4 IF-MIB::ifIndex.5 =3D INTEGER:=20 > 5 IF-MIB::ifIndex.6 =3D INTEGER: 6 IF-MIB::ifIndex.7 =3D INTEGER:=20 > 7 IF-MIB::ifIndex.8 =3D INTEGER: 8 IF-MIB::ifIndex.9 =3D INTEGER:=20 > 9 IF-MIB::ifIndex.10 =3D INTEGER: 10 IF-MIB::ifIndex.11 =3D=20 > INTEGER: 11 IF-MIB::ifIndex.12 =3D INTEGER: 12=20 > IF-MIB::ifIndex.13 =3D INTEGER: 13 IF-MIB::ifDescr.1 =3D STRING:=20 > lo IF-MIB::ifDescr.2 =3D STRING: tap0 IF-MIB::ifDescr.3 =3D=20 > STRING: teql0 IF-MIB::ifDescr.4 =3D STRING: int0=20 > IF-MIB::ifDescr.5 =3D STRING: ext0 IF-MIB::ifDescr.6 =3D STRING:=20 > bond0 IF-MIB::ifDescr.7 =3D STRING: bond1 IF-MIB::ifDescr.8 =3D=20 > STRING: bond2 IF-MIB::ifDescr.9 =3D STRING: bond3=20 > IF-MIB::ifDescr.10 =3D STRING: bond4 IF-MIB::ifDescr.11 =3D=20 > STRING: bond5 IF-MIB::ifDescr.12 =3D STRING: bond6=20 > IF-MIB::ifDescr.13 =3D STRING: bond7 IF-MIB::ifType.1 =3D=20 > INTEGER: softwareLoopback(24) IF-MIB::ifType.2 =3D INTEGER:=20 > ethernetCsmacd(6) IF-MIB::ifType.3 =3D INTEGER: other(1)=20 > IF-MIB::ifType.4 =3D INTEGER: ethernetCsmacd(6)=20 > IF-MIB::ifType.5 =3D INTEGER: ethernetCsmacd(6)=20 > IF-MIB::ifType.6 =3D INTEGER: ethernetCsmacd(6)=20 > IF-MIB::ifType.7 =3D INTEGER: ethernetCsmacd(6)=20 > IF-MIB::ifType.8 =3D INTEGER: ethernetCsmacd(6) (and so on and=20 > so on and so on) .... >=20 > -------------------------------------------------------------- > ----------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the=20 > chance to share your opinions on IT & business topics through=20 > brief surveys - and earn cash=20 > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge &CID=3DDEVDEV _______________________________________________ Devmon-support mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devmon-support |