The variable name remains lcpu.busyPer in both probes. It is also the first variable in the <snmp-device-variables> section on both probes.
On Aug 24, 2010, at 6:37 PM, William Fisher wrote: > On 8/24/10 3:45 PM, Andrew Kee wrote: >> I am in the process of changing the probes for our 3750s over to a new >> probe that will monitor stack status. I noticed that the chart for >> CPU Percent Busy (OID: 1.3.6.1.4.1.9.2.1.56.0) is changing to uptime >> (OID: 1.3.6.1.2.1.1.3.0) when I change to the new probe. This same >> problem does not happen in reverse. When I apply the new probe and >> begin charting CPU Percent Busy, the chart will remain CPU Percent >> Busy if I switch back to the old probe. The old probe does not chart >> uptime at all. The chart will show an error if the line to pull >> uptime is removed from the new probe. >> Has anyone else run in to this? > To deal with probe changes, InterMapper associates the variable names in your > probes with an internal ID used to identify the specific data sets. Try to > retain existing variable names between your old and new probes. InterMapper > may be falling back on the order of the variables in the probe if it can't > manage to sync with the variable names. > > -- > Bill Fisher > Dartware, LLC > ____________________________________________________________________ > List archives: > http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ > To unsubscribe: send email to: [email protected] > ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [email protected]
