Is there a Documentation on OIDs of SNMP running on a datamover?

Hi Pete,

there is no extra docmentation – this part is just the standard MIB-II as defined by RFC’s

If you have a specific issue where you believe a counter isn’t working as it should please open a service request

Rainer

P.S.: I would be nicer to post human friendly names of MIB objects

Hi @Rainer_EMC,

Here is the human readable OID:IF-MIB::ifHCInOctets.1

This reflects the first 10G NIC.

There is already a SR opened but it seems that it is not really understood what i want.

I have provided the counters values including timestamps and the according excerpt of RFC2233

and i get in return documentation on SNMP on Clariion.

This is an output of snmpwalk on the mentioned OID.

The counter wraps (at least) once every 100sec.

15:13:39 IF-MIB::ifHCInOctets.1 = Counter64: 18334748186395944502

15:13:45 IF-MIB::ifHCInOctets.1 = Counter64: 794194984682284143

15:13:50 IF-MIB::ifHCInOctets.1 = Counter64: 1695269562786170629

15:13:55 IF-MIB::ifHCInOctets.1 = Counter64: 2671276352244249276

15:14:00 IF-MIB::ifHCInOctets.1 = Counter64: 3529066649371012842

15:14:05 IF-MIB::ifHCInOctets.1 = Counter64: 4220119834961394792

15:14:11 IF-MIB::ifHCInOctets.1 = Counter64: 4972413309957972869

15:14:16 IF-MIB::ifHCInOctets.1 = Counter64: 5851232634549325037

15:14:21 IF-MIB::ifHCInOctets.1 = Counter64: 6972085413653615617

15:14:26 IF-MIB::ifHCInOctets.1 = Counter64: 8143245282134891626

15:14:31 IF-MIB::ifHCInOctets.1 = Counter64: 9197836620056449906

15:14:36 IF-MIB::ifHCInOctets.1 = Counter64: 10127911332739004588

15:14:41 IF-MIB::ifHCInOctets.1 = Counter64: 11028788346642245909

15:14:46 IF-MIB::ifHCInOctets.1 = Counter64: 11990824161537206905

15:14:51 IF-MIB::ifHCInOctets.1 = Counter64: 13095312784531211474

15:14:56 IF-MIB::ifHCInOctets.1 = Counter64: 14056757989883374130

15:15:01 IF-MIB::ifHCInOctets.1 = Counter64: 15081405090695144414

15:15:07 IF-MIB::ifHCInOctets.1 = Counter64: 16254454796326286143

15:15:12 IF-MIB::ifHCInOctets.1 = Counter64: 17477373770958200906

15:15:17 IF-MIB::ifHCInOctets.1 = Counter64: 398151875615479709

RFC2233:

3.1.6.  Counter Size

   As the speed of network media increase, the minimum time in which

   a 32 bit counter will wrap decreases.  For example, a 10Mbs stream

   of back-to-back, full-size packets causes ifInOctets to wrap in

   just over 57 minutes; at 100Mbs, the minimum wrap time is 5.7

   minutes, and at 1Gbs, the minimum is 34 seconds.  Requiring that

   interfaces be polled frequently enough not to miss a counter wrap

   is increasingly problematic.

   […]

   Instead, this memo adopts expanded, 64 bit, counters.  These

   counters are provided in new "high capacity" groups.  The old,

   32-bit, counters have not been deprecated.  The 64-bit counters

   are to be used only when the 32-bit counters do not provide enough

   capacity; that is, when the 32 bit counters could wrap too fast.

You meant data mover when you said Clariion – right ?

I was asking emcsupport for documentation on datamovers and i got in return documentation on Clariion.

Well – MIB-II is straight from the standard so its not well mentioned in the VNX file SNMP manual

Reading OID’s isn’t fun either

I know the S in SNMP stands for simple – but I guess thats only for the protocol ☺

BTW we do not mention RFC 2233 in the SNMP docs

Only RFC 1213 for MIB-2

It seems that only 2233 mentions 64bit counters like ifHCInOctets

Maybe that’s the reason and you need to use the 32bit version ifInOctets