what does these values mean snmpEtherStatsRXNoErrors and snmpEtherStatsTXNoErrors ?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

what does these values mean snmpEtherStatsRXNoErrors and snmpEtherStatsTXNoErrors ?

L4 Transporter

Hi,

 

Trying to rule out the a file transfer througputput issue,  looking at the interface stats,

 

1.  Is there a technote explain these values mean?

2.  What are these values mean snmpEtherStatsRXNoErrors and snmpEtherStatsTXNoErrors ?  

 

Thanks,

 

E

 

admin@PAN5260(active)> show system state filter-pretty sys.s1.p21.*

sys.s1.p21.capability: [
auto,
40Gb/s-full,
100Gb/s-full,
]
sys.s1.p21.cfg: {
farloop: False,
mode: Autoneg,
mru: 10048,
nearloop: False,
pause-frames: True,
setting: auto,
}
sys.s1.p21.detail: {
snmpBcmEtherStatsPkts1519to1522Octets: 0x76e7efb3da,
snmpBcmEtherStatsPkts1522to2047Octets: 0x1,
snmpBcmReceivedPkts1024to1518Octets: 0xef7496da,
snmpBcmReceivedPkts128to255Octets: 0x138bed9aa,
snmpBcmReceivedPkts1519to2047Octets: 0x18970ada0a,
snmpBcmReceivedPkts256to511Octets: 0xdddd4674,
snmpBcmReceivedPkts512to1023Octets: 0x59ff10508,
snmpBcmReceivedPkts64Octets: 0x5ff43efa,
snmpBcmReceivedPkts65to127Octets: 0x60c9b129c,
snmpBcmTransmittedPkts1024to1518Octets: 0x4da507bb22,
snmpBcmTransmittedPkts128to255Octets: 0x1c36d46b7,
snmpBcmTransmittedPkts1519to2047Octets: 0x5e50e4d9d1,
snmpBcmTransmittedPkts256to511Octets: 0x1fdacbec9,
snmpBcmTransmittedPkts512to1023Octets: 0xa6422784f,
snmpBcmTransmittedPkts64Octets: 0xba4d1bb2,
snmpBcmTransmittedPkts65to127Octets: 0xec2fa90e1,
snmpDot1dTpPortInFrames: 0x27a99be7a1,
snmpDot1dTpPortOutFrames: 0xc99870bf5f,
snmpEtherStatsBroadcastPkts: 0xade36,
snmpEtherStatsMulticastPkts: 0x1432c34,
snmpEtherStatsOctets: 0x4b8eff6eadf65,
snmpEtherStatsPkts: 0xf1420ca700,
snmpEtherStatsPkts1024to1518Octets: 0x4e947c51fc,
snmpEtherStatsPkts128to255Octets: 0x2fc2c2061,
snmpEtherStatsPkts256to511Octets: 0x2db8a053d,
snmpEtherStatsPkts512to1023Octets: 0x1004137d57,
snmpEtherStatsPkts64Octets: 0x11a415aac,
snmpEtherStatsPkts65to127Octets: 0x14cf95a37d,
snmpEtherStatsRXNoErrors: 0x27a99be7a1,
snmpEtherStatsTXNoErrors: 0xc99870bf5e,
snmpIfHCInBroadcastPkts: 0x54,
snmpIfHCInMulticastPkts: 0x1402bc5,
snmpIfHCInOctets: 0xa9450db5adc6,
snmpIfHCInUcastPkts: 0x27a85bbb88,
snmpIfHCOutBroadcastPckts: 0xadde2,
snmpIfHCOutMulticastPkts: 0x3006f,
snmpIfHCOutOctets: 0x40faae935319f,
snmpIfHCOutUcastPkts: 0xc99862e10e,
snmpIfInBroadcastPkts: 0x54,
snmpIfInMulticastPkts: 0x1402bc5,
snmpIfInNUcastPkts: 0x1402c19,
snmpIfInOctets: 0xa9450db5adc6,
snmpIfInUcastPkts: 0x27a85bbb88,
snmpIfOutBroadcastPkts: 0xadde2,
snmpIfOutMulticastPkts: 0x3006f,
snmpIfOutNUcastPkts: 0xdde51,
snmpIfOutOctets: 0x40faae935319f,
snmpIfOutUcastPkts: 0xc99862e10e,
}
sys.s1.p21.phy: {
link-partner: { },
media: QSFP-Plus-Fiber,
sfp: {
connector: LC,
encoding: 64B66B,
identifier: QSFPP,
transceiver: ,
vendor-name: FINISAR CORP. ,
vendor-part-number: FTL4C1QE1C ,
vendor-part-rev: A1e<A4>,
},
type: Ethernet,
}
sys.s1.p21.qos: {
cir: 100000000,
flow: 1040,
index: 0,
queue: 280,
type: bypass,
}
sys.s1.p21.rate: {
duration: 68,
last-sample: 2019-07-17 11:30:31,
rx-broadcast: 0,
rx-bytes: 40537224,
rx-multicast: 3,
rx-unicast: 35029,
tx-broadcast: 0,
tx-bytes: 90330672,
tx-multicast: 0,
tx-unicast: 73956,
}
sys.s1.p21.state: board_port_autoneg_enabled
sys.s1.p21.stats: {
rx-broadcast: 84,
rx-bytes: 186114047847878,
rx-multicast: 20982725,
rx-unicast: 170328308616,
tx-broadcast: 712162,
tx-bytes: 1143126638277023,
tx-multicast: 196719,
tx-unicast: 865845043470,
}
sys.s1.p21.status: {
farloop: False,
link: Up,
mode: Autoneg,
mru: 10048,
nearloop: False,
pause-frames: True,
setting: 40Gb/s-full,
type: QSFP-Plus,
}

3 REPLIES 3

Cyber Elite
Cyber Elite

@nextgenhappines wrote:

Hi,

1.  Is there a technote explain these values mean?

2.  What are these values mean snmpEtherStatsRXNoErrors and snmpEtherStatsTXNoErrors ?  


1) MIB information can be found HERE, which further links to more detailed MIB documentation.

2) Its dispalying the Transmit and Receive error counters. 

@BPry  Thanks!  

 

I am getting complaint about slow transfer, trying to start from L1 and move up, checking switch ports for errors.  The kb on how to check for crc errors on an interface  is not updated with the newer 5200 platform.  

 

Do I need to worry about those two counters ( snmpEtherStatsRXNoErrors and snmpEtherStatsTXNoErrors ) are iincrementing?  

I got some information back from TAC,  

 

The output from show system state filter-pretty sys.s1.p??  (or you are replace with sys.s1.*, that will show all the interfaces on slot1, if you are using chassis, change from s1 to sX, X is the slot that you want to check)

 

snmpEtherStatsRXNoErrors , snmpEtherStatsTXNoErrors  those counters were "success counters" not indicative of any sort of issue on the device/interface.   I can see if you want to count the errors in %, you can use snmpIfInErrors/(snmpEtherStatsRXNoErrors+snmpEtherStatsTXNoErrors) 

 

This is what I found on the devices that I have acceess to,

 

Here is one example that interface has FCSErrors,  CRCAlignErrors, 

 

sys.s1.p23.detail: {

  snmpBcmEtherStatsPkts1519to1522Octets: 0x792c389c87,

  snmpBcmEtherStatsPkts1522to2047Octets: 0xb,

  snmpBcmEtherStatsPkts2048to4095Octets: 0x2a,

  snmpBcmReceivedPkts1024to1518Octets: 0x1b322a369e,

  snmpBcmReceivedPkts128to255Octets: 0x16b32dd0d2,

  snmpBcmReceivedPkts1519to2047Octets: 0x4c78f5b24a,

  snmpBcmReceivedPkts2048to4095Octets: 0x2a,

  snmpBcmReceivedPkts256to511Octets: 0x11b6aba18b,

  snmpBcmReceivedPkts512to1023Octets: 0x15a960e8ab,

  snmpBcmReceivedPkts64Octets: 0xae6e9f4ec,

  snmpBcmReceivedPkts65to127Octets: 0x35301756da,

  snmpBcmTransmittedPkts1024to1518Octets: 0xccec3f6fa,

  snmpBcmTransmittedPkts128to255Octets: 0x12ee4025bd,

  snmpBcmTransmittedPkts1519to2047Octets: 0x2cb342ea48,

  snmpBcmTransmittedPkts256to511Octets: 0xd979cce6b,

  snmpBcmTransmittedPkts512to1023Octets: 0x133d046ab9,

  snmpBcmTransmittedPkts64Octets: 0x323f784e2,

  snmpBcmTransmittedPkts65to127Octets: 0x3293bb6d53,

  snmpDot1dTpPortInFrames: 0xe5d55b8fef,

  snmpDot1dTpPortOutFrames: 0xa2fc9b3264,

  snmpDot3StatsFCSErrors: 0x3,              <-------------------

  snmpEtherStatsBroadcastPkts: 0x1c3c3429,

  snmpEtherStatsCRCAlignErrors: 0x3,      <--------------------

  snmpEtherStatsMulticastPkts: 0x556403d6,

  snmpEtherStatsOctets: 0x47fed55072a11,

  snmpEtherStatsPkts: 0x188d1f6c254,

  snmpEtherStatsPkts1024to1518Octets: 0x2800ee2d98,

  snmpEtherStatsPkts128to255Octets: 0x29a16df68f,

  snmpEtherStatsPkts256to511Octets: 0x1f4e486ff6,

  snmpEtherStatsPkts512to1023Octets: 0x28e6655364,

  snmpEtherStatsPkts64Octets: 0xe0ae179ce,

  snmpEtherStatsPkts65to127Octets: 0x67c3d2c42d,

  snmpEtherStatsRXNoErrors: 0xe5d55b9011,

  snmpEtherStatsTXNoErrors: 0xa2fc9b3264,

  snmpIfHCInBroadcastPkts: 0xe379328,

  snmpIfHCInMulticastPkts: 0x52a24376,

  snmpIfHCInOctets: 0x2cfa0484ef113,

  snmpIfHCInUcastPkts: 0xe57481b94f,

  snmpIfHCOutBroadcastPckts: 0xe04a101,

  snmpIfHCOutMulticastPkts: 0x2c1c060,

  snmpIfHCOutOctets: 0x1b04d0cb838fe,

  snmpIfHCOutUcastPkts: 0xa2ebd4d106,

  snmpIfInBroadcastPkts: 0xe379328,

  snmpIfInErrors: 0x3,    <-------------------------------

  snmpIfInMulticastPkts: 0x52a24376,

  snmpIfInNUcastPkts: 0x60d9d69e,

  snmpIfInOctets: 0x2cfa0484ef113,

  snmpIfInUcastPkts: 0xe57481b94f,

  snmpIfOutBroadcastPkts: 0xe04a101,

  snmpIfOutMulticastPkts: 0x2c1c060,

  snmpIfOutNUcastPkts: 0x10c66161,

  snmpIfOutOctets: 0x1b04d0cb838fe,

  snmpIfOutUcastPkts: 0xa2ebd4d106,

}

 

It maybe better to just match for error and filter out those NoErrrors.    and see if those counters are increaasing over time..

 

E

  • 5061 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!