|
From: KING, K. (ATTSI) <KK...@at...> - 2011-04-13 19:48:59
|
This is transform that is giving me the good index:
procIndex : INDEX : {cimrMsuTrafficRate}{cimrMsuProcBayNumber}
-Kevin
-----Original Message-----
From: KING, KEVIN (ATTSI)
Sent: Wednesday, April 13, 2011 3:41 PM
To: dev...@li...
Subject: Re: [Devmon] Rolling my own test Help
Ok the closest I can get this is creating an index that I can display
with the data to show the proc and traffic direction.
IE the index is 1.1
1.2
23.1 yada yada yada.
So now my devmon report on xymon looks like this:
Slot Bay Processor Current MSU's Max MSU's How long ago
1.1 0 142 213
days, 21:32:40
However I still cannot resolve the actual processor slot and bay.
This is important as processor 1 at the moment is in slot 5/0. If this
is removed or another card added or a failover the processor number
will/can change.
The processor location is in the other two OID's One OID I get slot,
then the second gives me the card processor number.
I apologize for my lack of snmp knowledge, I am learning. It looks like
my oid has a leaf with a branch hanging on it.
In any case with the current transforms I do not see a way to join this
data. The msu data has tx and rx values which gives me 46 lines of data.
And the processor information is 26 lines. I have not found a way link
these. It seems that the MSU OID should have a separate oid for tx mus
and rx msu for each processor.
Then all the transforms would work as described. Unless I am completely
missing something an enhancement to split and join transform may do what
I need.
I am happy to provide whatever information is needed so someone smarter
than I can review this issue.
-Kevin
-----Original Message-----
From: KING, KEVIN (ATTSI)
Sent: Monday, April 11, 2011 1:57 PM
To: dev...@li...
Subject: Re: [Devmon] Rolling my own test Help
Thinking on this some more. I was starting with the data, maybe if I
start with the processor id's then pull the data I will have better
luck. If I pull OID this is what I get. If I read the documents
correctly I should be able to use the index transform to use the last
number here which is the processor. To then match up with the oid for
the MSU's
Can I get some help understanding the example in the docs?
snmpwalk -v2c -c NSDSPO 10.40.29.30 1.3.6.1.4.1.9.9.529.1.2.1.1.8
SNMPv2-SMI::enterprises.9.9.529.1.2.1.1.8.1 = INTEGER: 5
SNMPv2-SMI::enterprises.9.9.529.1.2.1.1.8.2 = INTEGER: 9
SNMPv2-SMI::enterprises.9.9.529.1.2.1.1.8.3 = INTEGER: 8
SNMPv2-SMI::enterprises.9.9.529.1.2.1.1.8.4 = INTEGER: 8
SNMPv2-SMI::enterprises.9.9.529.1.2.1.1.8.5 = INTEGER: 8
SNMPv2-SMI::enterprises.9.9.529.1.2.1.1.8.6 = INTEGER: 9
SNMPv2-SMI::enterprises.9.9.529.1.2.1.1.8.7 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.529.1.2.1.1.8.8 = INTEGER: 8
SNMPv2-SMI::enterprises.9.9.529.1.2.1.1.8.9 = INTEGER: 8
-----Original Message-----
From: KING, KEVIN (ATTSI)
Sent: Monday, April 11, 2011 11:34 AM
To: dev...@li...
Subject: [Devmon] Rolling my own test Help
I have a test I am building for MSU per Processor on a Cisco ITP/Router.
The MSU OID is 1.3.6.1.4.1.9.9.529.1.2.2.1.3. Ok I have the test and get
the data back. Here is a sample below. I now will need to do a
transform. The data after the last digit on the oid walled is 3 after
that is the system processor number and then the traffic direction. (
1=rx 2=tx) then the gauge is the MSU counter.
Ok I want to display this as processor slot/bay rx data
" " tx
data.
The processor slot and bay are in two other oid's. so one oid will give
me the slot for processor 1 then a second oid will give me the bay of
the slot for processor 1.
One thing that has me stuck is the rx tx direction is not in a readable
oid so I can do a switch transform to fill the table.
I am getting mixed up on this. It seems I will have to do a few
transforms on this and not sure where to go with it. I tend to make
things more difficult than needed. So I hope I can get some clarity and
direction for the group.
snmpwalk -v2c -c public host 1.3.6.1.4.1.9.9.529.1.2.2.1.3
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.1.1 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.1.2 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.2.1 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.2.2 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.3.1 = Gauge32: 370
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.3.2 = Gauge32: 347
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.4.1 = Gauge32: 272
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.4.2 = Gauge32: 250
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.5.1 = Gauge32: 371
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.5.2 = Gauge32: 353
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.6.1 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.6.2 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.7.1 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.7.2 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.8.1 = Gauge32: 269
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.8.2 = Gauge32: 292
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.9.1 = Gauge32: 384
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.9.2 = Gauge32: 372
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.10.1 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.10.2 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.11.1 = Gauge32: 357
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.11.2 = Gauge32: 375
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.12.1 = Gauge32: 368
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.12.2 = Gauge32: 377
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.13.1 = Gauge32: 355
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.13.2 = Gauge32: 367
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.14.1 = Gauge32: 379
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.14.2 = Gauge32: 364
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.15.1 = Gauge32: 542
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.15.2 = Gauge32: 525
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.16.1 = Gauge32: 304
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.16.2 = Gauge32: 362
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.17.1 = Gauge32: 574
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.17.2 = Gauge32: 538
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.18.1 = Gauge32: 696
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.18.2 = Gauge32: 668
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.19.1 = Gauge32: 638
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.19.2 = Gauge32: 640
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.20.1 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.20.2 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.21.1 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.21.2 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.22.1 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.22.2 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.23.1 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.529.1.2.2.1.3.23.2 = Gauge32: 0
Kevin H. King
Engineer V Implementations
AT&T
404-444-0410
"You can not please everyone everyday, But everyday please everyone you
can" -me
------------------------------------------------------------------------
------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Devmon-support mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devmon-support
------------------------------------------------------------------------
------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Devmon-support mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devmon-support
------------------------------------------------------------------------
------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and
improve
application availability and disaster protection. Learn more about
boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Devmon-support mailing list
Dev...@li...
https://lists.sourceforge.net/lists/listinfo/devmon-support
|