About Enterasys Matrix N7

bluespray · Post by **bluespray** » Thu Oct 06, 2005 11:01 pm

Does anyone have experience using cacti for Enterasys Matrix N7mostly the CPU Usage?

Thanks!

hosierd · Post by **hosierd** » Fri Feb 24, 2006 6:50 pm

We've been using Cacti for a couple of years to monitor traffic and errors on our Cabletron/Enterasys gear. Everything from 2nd & 3rd Gen cards in E6/E7 to 4th Gen DFEs in E7/N7 chassis. Have not tired to monitor the CPU usage but it should be pretty straight forward.

Post by **gandalf** » Sat Feb 25, 2006 12:11 pm

bluespray wrote:Does anyone have experience using cacti for Enterasys Matrix N7mostly the CPU Usage?

Thanks!

Yes. I may export the needed Templates. But will have to wait until at least Wednesday next week.
Reinhard

NHDave · Post by **NHDave** » Wed Nov 29, 2006 5:36 pm

Has anyone got this working yet?

Post by **gandalf** » Tue Dec 05, 2006 4:01 am

Here are the templates for Matrix N7 CPU

Reinhard

NHDave · Post by **NHDave** » Tue Dec 12, 2006 11:16 pm

gandalf wrote:Here are the templates for Matrix N7 CPU

Reinhard

Excellent!! Much appreciated, they work great!

Post by **gandalf** » Wed Dec 13, 2006 1:23 pm

Well, let's turn it the other way round. ARe you aware of more OIDs for N7 (or C2's) that are interesting to know about? I'll extend the templates, if I get the OIDs
Reinhard

NHDave · Post by **NHDave** » Sun Dec 24, 2006 9:10 am

One interesting set I've found:

1.3.6.1.4.1.5624.1.2.49.1.3.1 etsysResourceStorageTable OBJECT-TYPE SYNTAX Branch MAX-ACCESS No Access STATUS Current DESCRIPTION
The Table of storage utilization in the chassis.

1.3.6.1.4.1.5624.1.2.49.1.3.1.1 etsysResourceStorageEntry OBJECT-TYPE SYNTAX Branch MAX-ACCESS No Access STATUS Current DESCRIPTION
An entry for one storage area in the chassis.

1.3.6.1.4.1.5624.1.2.49.1.3.1.1.1 etsysResourceStorageType OBJECT-TYPE SYNTAX Integer {
other(1), ram(2), flash(3) }

1.3.6.1.4.1.5624.1.2.49.1.3.1.1.2 etsysResourceStorageTypeID OBJECT-TYPE SYNTAX Unsigned Integer MAX-ACCESS No Access STATUS Current DESCRIPTION
A unique arbitrary value per storage type assigned to the entry.

1.3.6.1.4.1.5624.1.2.49.1.3.1.1.3 etsysResourceStorageDescr OBJECT-TYPE SYNTAX OCTET String ( SIZE ( 0..255 ) ) TEXTUAL-CONVENTION SnmpAdminString DISPLAY-HINT 255a MAX-ACCESS Read Only STATUS Current DESCRIPTION
A textual description of this storage area.

1.3.6.1.4.1.5624.1.2.49.1.3.1.1.4 etsysResourceStorageSize OBJECT-TYPE SYNTAX Unsigned Integer MAX-ACCESS Read Only STATUS Current DESCRIPTION
The size, in Kilobytes, of the storage area.

1.3.6.1.4.1.5624.1.2.49.1.3.1.1.5 etsysResourceStorageAvailable OBJECT-TYPE SYNTAX Unsigned Integer MAX-ACCESS Read Only STATUS Current DESCRIPTION
The available space, in Kilobytes, left on the storage area.

There is also a power one but ours is not enabled:

1.3.6.1.4.1.5624.1.2.50 etsysPowerEthernetMibExtMIB OBJECT-TYPE SYNTAX Module Identity DESCRIPTION
This MIB module defines a portion of the SNMP MIB under the Enterasys Networks enterprise OID pertaining to the allocation of power in a Pse chassis.

raddy · Post by **raddy** » Sun Dec 24, 2006 4:05 pm

Don't know what you are after in particular and I dont use them myself but try the link for SNMP info on them.

http://www.mibdepot.com/cgi-bin/vendor_ ... =enterasys

Hope it helps.

Post by **gandalf** » Thu Dec 28, 2006 5:37 am

These are readings from one of our N7.
Storage:

Code: Select all

SNMPv2-SMI::enterprises.5624.1.2.49.1.3.1.1.3.71.2.1 = STRING: "RAM device 1"
SNMPv2-SMI::enterprises.5624.1.2.49.1.3.1.1.3.71.3.1 = STRING: "Images & Miscellaneous"
SNMPv2-SMI::enterprises.5624.1.2.49.1.3.1.1.3.71.3.2 = STRING: "Nonvolatile Data Storage"
SNMPv2-SMI::enterprises.5624.1.2.49.1.3.1.1.4.71.2.1 = Gauge32: 131072
SNMPv2-SMI::enterprises.5624.1.2.49.1.3.1.1.4.71.3.1 = Gauge32: 16384
SNMPv2-SMI::enterprises.5624.1.2.49.1.3.1.1.4.71.3.2 = Gauge32: 16384
SNMPv2-SMI::enterprises.5624.1.2.49.1.3.1.1.5.71.2.1 = Gauge32: 8894
SNMPv2-SMI::enterprises.5624.1.2.49.1.3.1.1.5.71.3.1 = Gauge32: 10124
SNMPv2-SMI::enterprises.5624.1.2.49.1.3.1.1.5.71.3.2 = Gauge32: 14384

You see, this is all quite static memory (RAM device, Images and NVS). Personally, I find those not that interesting. Dynamic main memory readings would be better.

And for Power, I only get

Code: Select all

SNMPv2-SMI::enterprises.5624.1.2.50.1.1.1.0 = INTEGER: 1
SNMPv2-SMI::enterprises.5624.1.2.50.1.1.2.0 = INTEGER: 2
SNMPv2-SMI::enterprises.5624.1.2.50.1.1.3.0 = Gauge32: 100
SNMPv2-SMI::enterprises.5624.1.2.50.1.2.1.1.1.11 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.2.1.1.1.12 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.2.1.1.1.13 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.2.1.1.1.14 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.2.1.1.1.15 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.2.1.1.1.16 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.2.1.1.1.17 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.2.1.1.2.11 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.2.1.1.2.12 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.2.1.1.2.13 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.2.1.1.2.14 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.2.1.1.2.15 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.2.1.1.2.16 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.2.1.1.2.17 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.3.1.0 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.3.2.0 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.3.3.0 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.3.4.0 = Gauge32: 0
SNMPv2-SMI::enterprises.5624.1.2.50.1.3.5.0 = INTEGER: 3
SNMPv2-SMI::enterprises.5624.1.2.50.1.3.6.1.2.1 = INTEGER: 1
SNMPv2-SMI::enterprises.5624.1.2.50.1.3.6.1.2.2 = INTEGER: 1
SNMPv2-SMI::enterprises.5624.1.2.50.1.3.6.1.2.3 = INTEGER: 1
SNMPv2-SMI::enterprises.5624.1.2.50.1.3.6.1.2.4 = INTEGER: 1

Not that interesting at all. So I will leave this off
Reinhard

Ancalagon · Post by **Ancalagon** » Wed Feb 27, 2008 3:11 am

Old thread, I know... but perhaps interesting:

The N7 has CPU-data for every slot. So you have

.1.3.6.1.4.1.5624.1.2.49.1.1.1.1.2.X.1 = 5sec
.1.3.6.1.4.1.5624.1.2.49.1.1.1.1.3.X.1 = 60sec
.1.3.6.1.4.1.5624.1.2.49.1.1.1.1.4.X.1 = 300sec

and the value of "X" depends on the slot:

Slot 1 = 71
Slot 2 = 72
.
.
Slot 7 = 77

hth
Stefan

Atkatla · Post by **Atkatla** » Thu Apr 17, 2008 3:48 pm

Hi, I want to watch our N7's too. How can I obtain the necessary data? (CPU-data for all 7 slots)

If I understood correctly I have to use GetSNMPdata (Indexed). And I have to write an XML data query?
The tutorials discribed the snmp-walk method. But can I use it here? I am asking because it is not the last number which "walks".

The other method would be "get".

The 'get' method obtains a list of indexes and does an snmpget for each index of the OID specified for this field.

Where do I specify them? Simply writing
<oid>firstoid</oid>
<oid>secondoid</oid>
and so on...?

This is from the tutorials:

Code: Select all

   <fields>
      <ifIndex>
         <name>Index</name>
         <method>walk</method>
         <source>value</source>
         <direction>input</direction>
         <oid>.1.3.6.1.2.1.2.2.1.1</oid>
      </ifIndex>
   </fields>

Or is the a possibility to let the second last number "walk" while the last number is fixed to one?

Post by **gandalf** » Fri Apr 18, 2008 8:29 am

See SNMP Data Query Howto at second link of my sig. Use a two-dimensional <oid_index_parse>OID/REGEXP: option (google for old threads)
Reinhard

niobe · Post by **niobe** » Mon Apr 21, 2008 1:45 pm

Can anyone share any related templates for Enterasys C series?

Post by **gandalf** » Mon Apr 21, 2008 2:58 pm

We're using >100 C2. But I still do not have interesting private MIB OIDs, so no template here. If you know some OIDs you're interested in, I will give it a go and share results
Reinhard

Cacti