Back to Blog
Collapse device intermapper5/8/2023 ![]() The best part was that between the 3 servers there where only 2 tape drives. The 3 servers that were being backed up totaled somewhere around 500 gigs…maybe a bit less. The funny thing is that the backups were all on a bunch of 4mm 20 gig (uncompressed) tapes. It seemed like a bit overkill, but then again, it is better to be safe. The previous group of people that managed the backups for these systems had a disaster recovery plan that involved having a rotation of backups that traveled through 3 separate physical locations. ![]() I have been trying to implement a fairly reliable backup system for a few small file servers we have at the office. On the good side, it gave Bill and I a good excuse to use a hammer and a bunch of prying tools to "install" a tape autoloader. That thing really needed to be driven through the desk. It just looked like it busted into the magnet that surrounds the cable near the end. I didn't think the screwdriver actually went into the cable at all. I spent a couple hours between yesterday afternoon, later on that night, and some time this morning trying to figure out why my linux box refused to acknowledge the existence of the Sun StorEdge L8 LTO tape autoloader I hooked up to it. I found out yesterday that apparently using a hammer and a phillips head screw driver to drive a SCSI cable through a maybe 1/8 inch opening between my desk and the cube wall it is screwed into is a bad idea. without jumping through so many hoops.įor anyone that cares, These are the OIDs that seem to make the most sense:ĬpmCPUTotal5sec. 9 at the end does, but go figure… It sure would be nice to just make the OID available in the first place. So apparantly, my problem the whole time was that InterMapper wants the OID to look like this: I happened to be looking through the options for snmpwalk, and notice the “-O n” option, which prints out the OID numerically. So this morning I come into work figuring I would give it a fresh go. So I figure I just completely messed up writing the probe. But none of them work, InterMapper claims none of those OIDs are available in the switch. I get a value and everything! So I write the custom SNMP probe for InterMapper with the 3 OIDs I want to watch. This might be an issue with our version of intermapper, because if I use snmpwalk like this: But of course the only one of those that is actually in our version of the 6509 is cpmCPUTotal5sec.Īnyway, It sure would be nice if the OID was listed in that mib file. If you go to the cpmCPUTotal5secRev section, it says it was deprecated by cpmCPUTotalMonInterval, which when you go to that section. As you can see in the mib excerpt, cpmCPUTotal5sec was deprecated by cpmCPUTotal5secRev. ![]() Part of the fine is the deprecation chain. This object is deprecatedīy cpmCPUTotal5secRev which has the changed range of ![]() This object obsoletes the busyPer object from ![]() "The overall CPU busy percentage in the last 5 second For the 5 second CPU Load according to the MIB file this is what I need: Look at the number of mibs available just for the 6500 series:Īll I am looking for is the CPU load and the amount of memory available. Granted I am not nearly as familiar with SNMP stuff as I would like to be, but come on. Sure, cisco has a nice repository of all the MIBs for all their equipment, but they are all uncompiled and missing the actual OIDs. so I spent hours yesterday trying to get it to work. I was trying to get the SNMP probe it has for cisco equipment to work with our Cisco 6509 switch, but apparantly cisco decided that it would be fun to use completely differant OIDs for that line of switches. At my work we use InterMapper to monitor all our equipment. ![]()
0 Comments
Read More
Leave a Reply. |