Menu
▾
▴
devmon-support
|
From: Peter W. <pet...@gm...> - 2009-10-21 17:46:58
|
Hi all, In the past I've discovered a few times that CRC errors on our fibre channel switch caused us many harm. I installed devmon next to Xymon and I made a status-check with the documentation. All is working well, for the status check (online, location etc). So far so good. Now I want some real stuff to be monitored. The 20 fibre channel ports on the switch (CRC errors, underrun etc). I have access to this switch. I have access to the MIB description ( http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_2_x/fabricware/mibs/reference/guide/alliance.html) but I am wondering... If I would like to monitor all 20 ports, do I have to create 20 subdirs with contents (oids, thresholds ) for each port? There mus be an easier approach, but then again: I'm fairly new to devmon. When I issue a snmpwalk-command, for example: $ snmpwalk -v2c -c public ip.address.masked.here 1.3.6.1.3.94.4.5.1.40 It responds with 20 ports. How can I sample it all up to one oids-file (for example in the fc_error-directory) but have an table-like-output for each switchport. Any help is very much appreciated. Regards, Peter |
|
From: Geoff H. <geo...@gm...> - 2009-10-21 18:09:03
|
Hi Peter, Typically, you would need to use a "branch" type in the oids file if that will work .. instead of "leaf" type. Most MIB's are organized so the you have a base oid and then each port is .1, .2, .3 on the end of the base oid. The "branch" type will grab all of them. If you review the "docs/TEMPLATES" file in the devmon install directory, it explains it better and how to display them in a table in the messages file. Geoff On Wed, Oct 21, 2009 at 1:46 PM, Peter Welter <pet...@gm...>wrote: > Hi all, > > In the past I've discovered a few times that CRC errors on our fibre > channel > switch caused us many harm. I installed devmon next to Xymon and I made a > status-check with the documentation. All is working well, for the status > check (online, location etc). So far so good. > > Now I want some real stuff to be monitored. The 20 fibre channel ports on > the switch (CRC errors, underrun etc). I have access to this switch. I have > access to the MIB description ( > > http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_2_x/fabricware/mibs/reference/guide/alliance.html > ) > but I am wondering... > If I would like to monitor all 20 ports, do I have to create 20 subdirs > with > contents (oids, thresholds ) for each port? There mus be an easier > approach, > but then again: I'm fairly new to devmon. > > When I issue a snmpwalk-command, for example: > > $ snmpwalk -v2c -c public ip.address.masked.here 1.3.6.1.3.94.4.5.1.40 > > It responds with 20 ports. > > How can I sample it all up to one oids-file (for example in the > fc_error-directory) but have an table-like-output for each switchport. > > Any help is very much appreciated. > > Regards, Peter > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Devmon-support mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devmon-support > |
|
From: Buchan M. <bg...@st...> - 2009-10-22 10:35:49
|
On Wednesday, 21 October 2009 18:46:19 Peter Welter wrote: > Hi all, > > In the past I've discovered a few times that CRC errors on our fibre > channel switch caused us many harm. I installed devmon next to Xymon and I > made a status-check with the documentation. All is working well, for the > status check (online, location etc). So far so good. > > Now I want some real stuff to be monitored. The 20 fibre channel ports on > the switch (CRC errors, underrun etc). I have access to this switch. I have > access to the MIB description ( > http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_2_x/fab >ricware/mibs/reference/guide/alliance.html) but I am wondering... > If I would like to monitor all 20 ports, do I have to create 20 subdirs > with contents (oids, thresholds ) for each port? There mus be an easier > approach, but then again: I'm fairly new to devmon. > > When I issue a snmpwalk-command, for example: > > $ snmpwalk -v2c -c public ip.address.masked.here 1.3.6.1.3.94.4.5.1.40 > > It responds with 20 ports. > > How can I sample it all up to one oids-file (for example in the > fc_error-directory) but have an table-like-output for each switchport. > > Any help is very much appreciated. I have the beginning of a template for MDS9500 SAN directors, but so far only for interface load and CDP. Our MDS9506 SAN directors don't have the OID you use above (so, probably support an older version of this MIB). They are running m9500-sf1ek9-mz 3.2(3a),Compiled 1/10/2008. However, you may want to start with that. Our 9216i's (on m9200-ek9-mz Version 3.2(3a),Compiled 1/10/2008) behave the same as our MDS9506's, so while I will add a template for them too, it's not (yet) going to help you. I am not sure if I will be able to get someone to upgrade these to a newer IOS. Regards, Buchan |
|
From: Peter W. <pet...@gm...> - 2009-10-23 10:07:01
|
Hi Geoff & Buchan,
A break through this morning, finally. Thanks to your encouraging mail, I
discovered that running devmon interactively and in verbose mode is very
infomative if things do no work out right.
I do use the TABLE:-directive but it never showed up in Xymon. The table
output however, was made the way I wanted it. It showed however binary
values. Yoohoo!
Alarming on (, 9�,��,, |,�, )
Alarming on (|,x,l,�, , )
Alarming on (,,,,@&,)
Alarming on ()
<table border=1 cellpadding=5>
<tr><td>connUnitPortStatCountError</td><td>InvalidCRC</td></tr>
<tr><td></td><td></td></tr>
<tr><td> 9�</td><td></td></tr>
<tr><td>��</td><td></td></tr>
<tr><td></td><td></td></tr>
<tr><td> |</td><td></td></tr>
<tr><td>�</td><td></td></tr>
<tr><td> </td><td></td></tr>
<tr><td>|</td><td></td></tr>
<tr><td>x</td><td></td></tr>
<tr><td>l</td><td></td></tr>
<tr><td>�</td><td></td></tr>
<tr><td> </td><td></td></tr>
<tr><td> </td><td></td></tr>
<tr><td></td><td></td></tr>
<tr><td></td><td></td></tr>
<tr><td></td><td></td></tr>
<tr><td></td><td></td></tr>
<tr><td>@&</td><td> </td></tr>
<tr><td></td><td></td></tr>
<tr><td></td><td></td></tr>
</table>
Devmon version 0.3.1-beta1 running on xxxx
So since the output is hexadecimal (I think that is what snmpwalk tells me,
below), I could simply convert this to integers using the CONVERT-transform
option. Now the table can be seen in Xymon, but unfortunately the output is
not correct.
So I must be making another mistake here :-(
the oids-file:
connUnitPortStatCountInvalidCRC : .1.3.6.1.3.94.4.5.1.40 : branch
connUnitPortStatCountError : .1.3.6.1.3.94.4.5.1.3 : branch
the transforms-file:
IntconnUnitPortStatCountInvalidCRC : CONVERT:
{connUnitPortStatCountInvalidCRC} hex
IntconnUnitPortStatCountError : CONVERT: {connUnitPortStatCountError}
hex
the message-file:
TABLE:
connUnitPortStatCountError|InvalidCRC
{IntconnUnitPortStatCountError}|{IntconnUnitPortStatCountInvalidCRC}
xymon$ ~/server/ext/devmon/devmon-0.3.1-beta1/templates/mds9000/if_err>
snmpwalk -v2c -c Communitystring fiberswitch-address .1.3.6.1.3.94.4.5.1.40
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.1
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.2
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.3
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.4
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.5
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.6
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.7
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.8
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.9
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.10
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.11
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.12
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.13
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.14
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.15
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.16
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.17
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.18
= Hex-STRING: 00 00 00 00 00 00 00 01 <=== One CRC error!
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.19
= Hex-STRING: 00 00 00 00 00 00 00 00
SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.20
= Hex-STRING: 00 00 00 00 00 00 00 00
Do you have any hints/suggestions?
Thanks,
Peter
2009/10/22 Buchan Milne <bg...@st...>
> On Wednesday, 21 October 2009 18:46:19 Peter Welter wrote:
> > Hi all,
> >
> > In the past I've discovered a few times that CRC errors on our fibre
> > channel switch caused us many harm. I installed devmon next to Xymon and
> I
> > made a status-check with the documentation. All is working well, for the
> > status check (online, location etc). So far so good.
> >
> > Now I want some real stuff to be monitored. The 20 fibre channel ports on
> > the switch (CRC errors, underrun etc). I have access to this switch. I
> have
> > access to the MIB description (
> >
> http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_2_x/fab
> >ricware/mibs/reference/guide/alliance.html) but I am wondering...
> > If I would like to monitor all 20 ports, do I have to create 20 subdirs
> > with contents (oids, thresholds ) for each port? There mus be an easier
> > approach, but then again: I'm fairly new to devmon.
> >
> > When I issue a snmpwalk-command, for example:
> >
> > $ snmpwalk -v2c -c public ip.address.masked.here 1.3.6.1.3.94.4.5.1.40
> >
> > It responds with 20 ports.
> >
> > How can I sample it all up to one oids-file (for example in the
> > fc_error-directory) but have an table-like-output for each switchport.
> >
> > Any help is very much appreciated.
>
> I have the beginning of a template for MDS9500 SAN directors, but so far
> only
> for interface load and CDP. Our MDS9506 SAN directors don't have the OID
> you
> use above (so, probably support an older version of this MIB). They are
> running m9500-sf1ek9-mz 3.2(3a),Compiled 1/10/2008.
>
> However, you may want to start with that.
>
> Our 9216i's (on m9200-ek9-mz Version 3.2(3a),Compiled 1/10/2008) behave the
> same as our MDS9506's, so while I will add a template for them too, it's
> not
> (yet) going to help you.
>
> I am not sure if I will be able to get someone to upgrade these to a newer
> IOS.
>
> Regards,
> Buchan
>
|
|
From: Buchan M. <bg...@st...> - 2009-10-23 11:07:17
|
On Friday, 23 October 2009 11:06:28 Peter Welter wrote:
> Hi Geoff & Buchan,
>
> A break through this morning, finally. Thanks to your encouraging mail, I
> discovered that running devmon interactively and in verbose mode is very
> infomative if things do no work out right.
>
> I do use the TABLE:-directive but it never showed up in Xymon. The table
> output however, was made the way I wanted it. It showed however binary
> values. Yoohoo!
>
> Alarming on (, 9�,��,, |,�, )
> Alarming on (|,x,l,�, , )
> Alarming on (,,,,@&,)
> Alarming on ()
> <table border=1 cellpadding=5>
> <tr><td>connUnitPortStatCountError</td><td>InvalidCRC</td></tr>
> <tr><td></td><td></td></tr>
> <tr><td> 9�</td><td></td></tr>
> <tr><td>��</td><td></td></tr>
> <tr><td></td><td></td></tr>
> <tr><td> |</td><td></td></tr>
> <tr><td>�</td><td></td></tr>
> <tr><td> </td><td></td></tr>
> <tr><td>|</td><td></td></tr>
> <tr><td>x</td><td></td></tr>
> <tr><td>l</td><td></td></tr>
> <tr><td>�</td><td></td></tr>
> <tr><td> </td><td></td></tr>
> <tr><td> </td><td></td></tr>
> <tr><td></td><td></td></tr>
> <tr><td></td><td></td></tr>
> <tr><td></td><td></td></tr>
> <tr><td></td><td></td></tr>
> <tr><td>@&</td><td> </td></tr>
> <tr><td></td><td></td></tr>
> <tr><td></td><td></td></tr>
> </table>
>
>
> Devmon version 0.3.1-beta1 running on xxxx
>
> So since the output is hexadecimal (I think that is what snmpwalk tells me,
> below), I could simply convert this to integers using the CONVERT-transform
> option. Now the table can be seen in Xymon, but unfortunately the output is
> not correct.
>
> So I must be making another mistake here :-(
>
> the oids-file:
>
> connUnitPortStatCountInvalidCRC : .1.3.6.1.3.94.4.5.1.40 : branch
> connUnitPortStatCountError : .1.3.6.1.3.94.4.5.1.3 : branch
>
> the transforms-file:
>
> IntconnUnitPortStatCountInvalidCRC : CONVERT:
> {connUnitPortStatCountInvalidCRC} hex
> IntconnUnitPortStatCountError : CONVERT: {connUnitPortStatCountError}
> hex
>
> the message-file:
>
> TABLE:
> connUnitPortStatCountError|InvalidCRC
> {IntconnUnitPortStatCountError}|{IntconnUnitPortStatCountInvalidCRC}
>
> xymon$ ~/server/ext/devmon/devmon-0.3.1-beta1/templates/mds9000/if_err>
> snmpwalk -v2c -c Communitystring fiberswitch-address
> .1.3.6.1.3.94.4.5.1.40
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.1 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.2 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.3 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.4 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.5 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.6 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.7 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.8 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.9 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.10 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.11 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.12 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.13 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.14 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.15 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.16 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.17 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.18 = Hex-STRING: 00 00 00 00 00 00 00 01 <=== One CRC error!
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.19 = Hex-STRING: 00 00 00 00 00 00 00 00
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
>0.20 = Hex-STRING: 00 00 00 00 00 00 00 00
>
>
> Do you have any hints/suggestions?
I am not sure if there is a more efficient way to do this, but I dealt with Hex-
String values in a test I haven't yet made available (as it will probably
cause the all-clear-tests issue on version of devmon without another local
change I am testing on many routers). In the example here, I am converting the
cipsStaticCryptomapPeerB OID, which looks like this:
CISCO-SMI::ciscoExperiment.62.1.2.3.3.1.4.5.99.105.115.99.111.10 = Hex-STRING:
41 3D 88 04
to a printable string in the cipsStaticCryptomapPeer OID:
$ cat /usr/share/devmon/templates/cisco-2811/vpn/oids
cipsStaticCryptomapType : 1.3.6.1.4.1.9.10.62.1.2.3.3.1.2 : branch
cipsStaticCryptomapDescr : 1.3.6.1.4.1.9.10.62.1.2.3.3.1.3 : branch
cipsStaticCryptomapPeerB : 1.3.6.1.4.1.9.10.62.1.2.3.3.1.4 : branch
cipsStaticCryptomapNumPeers : 1.3.6.1.4.1.9.10.62.1.2.3.3.1.5 : branch
$ cat /usr/share/devmon/templates/cisco-2811/vpn/transforms
cipsStaticCryptomapPeerp1B : SUBSTR :{cipsStaticCryptomapPeerB} 0 1
cipsStaticCryptomapPeerp2B : SUBSTR :{cipsStaticCryptomapPeerB} 1 1
cipsStaticCryptomapPeerp3B : SUBSTR :{cipsStaticCryptomapPeerB} 2 1
cipsStaticCryptomapPeerp4B : SUBSTR :{cipsStaticCryptomapPeerB} 3 1
cipsStaticCryptomapPeerp1H : UNPACK : {cipsStaticCryptomapPeerp1B} H2
cipsStaticCryptomapPeerp2H : UNPACK : {cipsStaticCryptomapPeerp2B} H2
cipsStaticCryptomapPeerp3H : UNPACK : {cipsStaticCryptomapPeerp3B} H2
cipsStaticCryptomapPeerp4H : UNPACK : {cipsStaticCryptomapPeerp4B} H2
cipsStaticCryptomapPeerp1 : CONVERT : {cipsStaticCryptomapPeerp1H} hex
cipsStaticCryptomapPeerp2 : CONVERT : {cipsStaticCryptomapPeerp2H} hex
cipsStaticCryptomapPeerp3 : CONVERT : {cipsStaticCryptomapPeerp3H} hex
cipsStaticCryptomapPeerp4 : CONVERT : {cipsStaticCryptomapPeerp4H} hex
cipsStaticCryptomapPeer : REGSUB : {cipsStaticCryptomapPeerB}
/.*/{cipsStaticCryptomapPeerp1}.{cipsStaticCryptomapPeerp2}.
{cipsStaticCryptomapPeerp3}.{cipsStaticCryptomapPeerp4}/
If you need all 8 hex pairs, you could need 8 SUBSTR, 8 UNPACK, and 8 CONVERT
transforms. If you only need the last value, you could get away with just one
of each.
I plan on adding some better operators to automatically convert from common
SNMP types (or, possibly some automatic conversion of types).
Regards,
Buchan
|
|
From: Peter W. <pet...@gm...> - 2009-10-23 12:24:31
|
Hi Buchan,
Thanks for your response. I do have a column now that shows 1 error for port
18. This is OK. But I want to make sure I understand you correctly before I
shout HOORAY!... From the Cisco-manpage:
connUnitPortStatCountInvalidCRC (1.3.6.1.3.94.4.5.1.40)
Count of frames received with invalid CRC. This count is part of the Link
Error Status Block (LESB). (FC-PH 29.8). Loop ports should not count CRC
errors passing through when monitoring. This is a Fibre Channel-only
statistic.
Syntax Description
OCTET STRING (SIZE (8)) --->
Does this mean that I have to script all 8 hex-parts? Now, I did only the
following, which corresponds the real value:
connUnitPortStatCountInvalidCRC1B : SUBSTR:
{connUnitPortStatCountInvalidCRC} 7 1
connUnitPortStatCountInvalidCRC1H : UNPACK:
{connUnitPortStatCountInvalidCRC1B} H2
IntconnUnitPortStatCountInvalidCRC : CONVERT:
{connUnitPortStatCountInvalidCRC1H} hex
But when the value increases and goed beyond FF (I would say 256) I would
have do do some MATH to represent the actual error count? There, where you
performed some REGSUB-actions?
Regards,
Peter
2009/10/23 Buchan Milne <bg...@st...>
> >
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.
> >0.18 = Hex-STRING: 00 00 00 00 00 00 00 01 <=== One CRC error!
> >
> > Do you have any hints/suggestions?
>
> I am not sure if there is a more efficient way to do this, but I dealt with
> Hex-
> String values in a test I haven't yet made available (as it will probably
> cause the all-clear-tests issue on version of devmon without another local
> change I am testing on many routers). In the example here, I am converting
> the
> cipsStaticCryptomapPeerB OID, which looks like this:
>
> CISCO-SMI::ciscoExperiment.62.1.2.3.3.1.4.5.99.105.115.99.111.10 =
> Hex-STRING:
> 41 3D 88 04
>
> to a printable string in the cipsStaticCryptomapPeer OID:
>
> $ cat /usr/share/devmon/templates/cisco-2811/vpn/oids
> cipsStaticCryptomapType : 1.3.6.1.4.1.9.10.62.1.2.3.3.1.2 : branch
> cipsStaticCryptomapDescr : 1.3.6.1.4.1.9.10.62.1.2.3.3.1.3 : branch
> cipsStaticCryptomapPeerB : 1.3.6.1.4.1.9.10.62.1.2.3.3.1.4 : branch
> cipsStaticCryptomapNumPeers : 1.3.6.1.4.1.9.10.62.1.2.3.3.1.5 : branch
>
> $ cat /usr/share/devmon/templates/cisco-2811/vpn/transforms
> cipsStaticCryptomapPeerp1B : SUBSTR :{cipsStaticCryptomapPeerB} 0 1
> cipsStaticCryptomapPeerp2B : SUBSTR :{cipsStaticCryptomapPeerB} 1 1
> cipsStaticCryptomapPeerp3B : SUBSTR :{cipsStaticCryptomapPeerB} 2 1
> cipsStaticCryptomapPeerp4B : SUBSTR :{cipsStaticCryptomapPeerB} 3 1
>
> cipsStaticCryptomapPeerp1H : UNPACK : {cipsStaticCryptomapPeerp1B} H2
> cipsStaticCryptomapPeerp2H : UNPACK : {cipsStaticCryptomapPeerp2B} H2
> cipsStaticCryptomapPeerp3H : UNPACK : {cipsStaticCryptomapPeerp3B} H2
> cipsStaticCryptomapPeerp4H : UNPACK : {cipsStaticCryptomapPeerp4B} H2
>
> cipsStaticCryptomapPeerp1 : CONVERT : {cipsStaticCryptomapPeerp1H} hex
> cipsStaticCryptomapPeerp2 : CONVERT : {cipsStaticCryptomapPeerp2H} hex
> cipsStaticCryptomapPeerp3 : CONVERT : {cipsStaticCryptomapPeerp3H} hex
> cipsStaticCryptomapPeerp4 : CONVERT : {cipsStaticCryptomapPeerp4H} hex
>
> cipsStaticCryptomapPeer : REGSUB : {cipsStaticCryptomapPeerB}
> /.*/{cipsStaticCryptomapPeerp1}.{cipsStaticCryptomapPeerp2}.
> {cipsStaticCryptomapPeerp3}.{cipsStaticCryptomapPeerp4}/
>
>
> If you need all 8 hex pairs, you could need 8 SUBSTR, 8 UNPACK, and 8
> CONVERT
> transforms. If you only need the last value, you could get away with just
> one
> of each.
>
> I plan on adding some better operators to automatically convert from common
> SNMP types (or, possibly some automatic conversion of types).
>
>
> Regards,
> Buchan
>
|
|
From: Geoff H. <geo...@gm...> - 2009-10-23 12:39:51
|
Hmm, not sure. It looks good to me. Maybe it is because the hex string has
spaces in it, that it doesn't convert it properly. I have also never done a
convert on the branch. Buchan might know though.
Once you have it working, would you be able to provide the template? We are
soon (not yet) going to be implementing 2 x 9509's and 2 x 9134's, so I
would like to see if it works and modify for those as well (and submit back
to the group).
Thanks.
Geoff.
On Fri, Oct 23, 2009 at 6:06 AM, Peter Welter <pet...@gm...>wrote:
> Hi Geoff & Buchan,
>
> A break through this morning, finally. Thanks to your encouraging mail, I
> discovered that running devmon interactively and in verbose mode is very
> infomative if things do no work out right.
>
> I do use the TABLE:-directive but it never showed up in Xymon. The table
> output however, was made the way I wanted it. It showed however binary
> values. Yoohoo!
>
> Alarming on (, 9�,��,, |,�, )
> Alarming on (|,x,l,�, , )
> Alarming on (,,,,@&,)
> Alarming on ()
> <table border=1 cellpadding=5>
> <tr><td>connUnitPortStatCountError</td><td>InvalidCRC</td></tr>
> <tr><td></td><td></td></tr>
> <tr><td> 9�</td><td></td></tr>
> <tr><td>��</td><td></td></tr>
> <tr><td></td><td></td></tr>
> <tr><td> |</td><td></td></tr>
> <tr><td>�</td><td></td></tr>
> <tr><td> </td><td></td></tr>
> <tr><td>|</td><td></td></tr>
> <tr><td>x</td><td></td></tr>
> <tr><td>l</td><td></td></tr>
> <tr><td>�</td><td></td></tr>
> <tr><td> </td><td></td></tr>
> <tr><td> </td><td></td></tr>
> <tr><td></td><td></td></tr>
> <tr><td></td><td></td></tr>
> <tr><td></td><td></td></tr>
> <tr><td></td><td></td></tr>
> <tr><td>@&</td><td> </td></tr>
> <tr><td></td><td></td></tr>
> <tr><td></td><td></td></tr>
> </table>
>
>
> Devmon version 0.3.1-beta1 running on xxxx
>
> So since the output is hexadecimal (I think that is what snmpwalk tells me,
> below), I could simply convert this to integers using the CONVERT-transform
> option. Now the table can be seen in Xymon, but unfortunately the output is
> not correct.
>
> So I must be making another mistake here :-(
>
> the oids-file:
>
> connUnitPortStatCountInvalidCRC : .1.3.6.1.3.94.4.5.1.40 : branch
> connUnitPortStatCountError : .1.3.6.1.3.94.4.5.1.3 : branch
>
> the transforms-file:
>
> IntconnUnitPortStatCountInvalidCRC : CONVERT:
> {connUnitPortStatCountInvalidCRC} hex
> IntconnUnitPortStatCountError : CONVERT: {connUnitPortStatCountError}
> hex
>
> the message-file:
>
> TABLE:
> connUnitPortStatCountError|InvalidCRC
> {IntconnUnitPortStatCountError}|{IntconnUnitPortStatCountInvalidCRC}
>
> xymon$ ~/server/ext/devmon/devmon-0.3.1-beta1/templates/mds9000/if_err>
> snmpwalk -v2c -c Communitystring fiberswitch-address
> .1.3.6.1.3.94.4.5.1.40
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.1
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.2
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.3
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.4
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.5
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.6
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.7
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.8
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.9
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.10
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.11
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.12
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.13
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.14
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.15
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.16
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.17
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.18
> = Hex-STRING: 00 00 00 00 00 00 00 01 <=== One CRC error!
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.19
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
> SNMPv2-SMI::experimental.94.4.5.1.40.16.0.0.13.236.25.211.23.0.0.0.0.0.0.0.0.20
> = Hex-STRING: 00 00 00 00 00 00 00 00
>
>
> Do you have any hints/suggestions?
>
> Thanks,
> Peter
>
> 2009/10/22 Buchan Milne <bg...@st...>
>
> > On Wednesday, 21 October 2009 18:46:19 Peter Welter wrote:
> > > Hi all,
> > >
> > > In the past I've discovered a few times that CRC errors on our fibre
> > > channel switch caused us many harm. I installed devmon next to Xymon
> and
> > I
> > > made a status-check with the documentation. All is working well, for
> the
> > > status check (online, location etc). So far so good.
> > >
> > > Now I want some real stuff to be monitored. The 20 fibre channel ports
> on
> > > the switch (CRC errors, underrun etc). I have access to this switch. I
> > have
> > > access to the MIB description (
> > >
> >
> http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/sw/rel_2_x/fab
> > >ricware/mibs/reference/guide/alliance.html) but I am wondering...
> > > If I would like to monitor all 20 ports, do I have to create 20 subdirs
> > > with contents (oids, thresholds ) for each port? There mus be an easier
> > > approach, but then again: I'm fairly new to devmon.
> > >
> > > When I issue a snmpwalk-command, for example:
> > >
> > > $ snmpwalk -v2c -c public ip.address.masked.here 1.3.6.1.3.94.4.5.1.40
> > >
> > > It responds with 20 ports.
> > >
> > > How can I sample it all up to one oids-file (for example in the
> > > fc_error-directory) but have an table-like-output for each switchport.
> > >
> > > Any help is very much appreciated.
> >
> > I have the beginning of a template for MDS9500 SAN directors, but so far
> > only
> > for interface load and CDP. Our MDS9506 SAN directors don't have the OID
> > you
> > use above (so, probably support an older version of this MIB). They are
> > running m9500-sf1ek9-mz 3.2(3a),Compiled 1/10/2008.
> >
> > However, you may want to start with that.
> >
> > Our 9216i's (on m9200-ek9-mz Version 3.2(3a),Compiled 1/10/2008) behave
> the
> > same as our MDS9506's, so while I will add a template for them too, it's
> > not
> > (yet) going to help you.
> >
> > I am not sure if I will be able to get someone to upgrade these to a
> newer
> > IOS.
> >
> > Regards,
> > Buchan
> >
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Devmon-support mailing list
> Dev...@li...
> https://lists.sourceforge.net/lists/listinfo/devmon-support
>
|
|
From: Buchan M. <bg...@st...> - 2009-10-23 16:29:29
|
On Friday, 23 October 2009 13:39:40 Geoff Hallford wrote: > Hmm, not sure. It looks good to me. Maybe it is because the hex string has > spaces in it, that it doesn't convert it properly. I have also never done a > convert on the branch. Buchan might know though. > > Once you have it working, would you be able to provide the template? We are > soon (not yet) going to be implementing 2 x 9509's and 2 x 9134's, so I > would like to see if it works and modify for those as well (and submit back > to the group). The 9506's I have access to don't support these OIDs, the existing cisco- mds9500 template in svn should work with the 9509s at least. Please start with that template, if there is more that we can get out of them, I would like to integrate it. Regards, Buchan |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X