Specifications

Configuring SNMP
March 28, 2011 Page 18 of 27
View Name = All
Subtree OID = 1.3.6.1.2.1.1.1.0.244
Subtree mask = ff:df
View Type = included
Storage type = nonVolatile
Row status = active
YoucanseebytheunexpectedSubtreeOIDvaluethatthisviewactuallyaccommodatesonlythe
right‐most8bitsoftheentereddecimalvalue1012.Thehexadecimalequivalentis0x3f4,andthe
decimalequivalentof0xf4is244.Itisthereforetruethatthisdefinedsubtreewillgetaʺhit
ʺon
multipleportvalues(244,500,756,1012,etc), shouldtheyexist.Thishasnothingtodowiththe
mask,andeverythingtodowiththereasonablelimitationsofMI Bdesign.
AnSNMPqueryoftheetherStatsEntrybranchusingthecommunitynameassociatedwiththis
definedviewwoulddisplaya
resultsimilertothefollowing.
Object Instance Type Value
etherStatsIndex 1012 INTEGER 1012
etherStatsDataSource 1012 OBJECT ID 1.3.6.1...11012
etherStatsDropEvents 1012 Counter 54323
etherStatsOctets 1012 Counter 302877211
etherStatsPkts 1012 Counter 1592774
etherStatsBroadcastPkts 1012 Counter 793487
etherStatsMulticastPkts 1012 Counter 729406
etherStatsCRCAlignErrors 1012 Counter 0
etherStatsUndersizePkts 1012 Counter 0
etherStatsOversizePkts 1012 Counter 0
etherStatsFragments 1012 Counter 0
etherStatsJabbers 1012 Counter 0
etherStatsCollisions 1012 Counter 0
etherStatsPkts64Octets 1012 Counter 0
etherStatsPkts65to127Octets 1012 Counter 458931
etherStatsPkts128to255Octets 1012 Counter 55190
etherStatsPkts256to511Octets 1012 Counter 656909
etherStatsPkts512to1023Octets 1012 Counter 57
etherStatsPkts1024to1518Octets 1012 Counter 1
etherStatsOwner 1012 OCTET STRING monitor
etherStatsStatus 1012 INTEGER valid(1)
Configuring Secure SNMP Community Names
Procedure 4providesanexampleofarecommendedconfigurationthatwillpreventunsecured
SNMPv1/v2caccessofpotentiallysecuritycompromisinginformation.
Asdiscussedpreviouslyinthisdocument,SNMPv1andv2careinherentlyinsecuredevice
managementprotocols.Communitynamesusedtodefineaccesslevelsarepassedincleartextin
allprotocolframes
senttothemanagedentityandmaybevisiblebyread‐onlySNMPuserswhen
queryingcertainSNMPconfiguration‐relatedobjects.Inaddition,youmaybefurtherexposing
yournetworkduetoconfigurationconventionswhichreusethecommunitynamesinother
aspectsofentitymanagement,suchasCLIloginpasswords,and
SNMPsecuritynames.
Note: Any use of the mask parameter assumes the View Type is configured as included.
Parameters included or excluded cannot be specified along with the mask parameter.