08-02-2019 08:29 AM
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
