Re: [Devmon] MDS9000 fibre channel switch

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

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
>

Re: [Devmon] MDS9000 fibre channel switch

SNMP poller for Xymon

Re: [Devmon] MDS9000 fibre channel switch