running snmpwalk on ifindex reveals all indices properly, i.e:
IF-MIB::ifName.1 = STRING: Fa1
IF-MIB::ifName.2 = STRING: Gi1/1
IF-MIB::ifName.3 = STRING: Gi1/2
IF-MIB::ifName.4 = STRING: Gi1/3
IF-MIB::ifName.259 = STRING: VLAN-601
IF-MIB::ifName.260 = STRING: VLAN-876
IF-MIB::ifName.261 = STRING: Te5/1--Uncontrolled
IF-MIB::ifName.262 = STRING: Te5/1--Controlled
but when trying to see the octet counts from for example ifindex 261 or 262 I get no results at all:
IF-MIB::ifHCInOctets.230 = Counter64: 0
IF-MIB::ifHCInOctets.231 = Counter64: 0
NOTE: no ifIndex 261 or 262
IF-MIB::ifHCInOctets.293 = Counter64: 0
IF-MIB::ifHCInOctets.294 = Counter64: 0
All other physical interfaces show their values just fine - just not the TenGigE's.
so, dear community: is this a problem, feature or something that can be configured to work differently? or is it just me :-) googling something like "snmp tengigabitethernet counters" brings up mostly problems with the max data rate but in my case the snmp values do not seem to exist at all.
Thank you Vinod. You pointed out the obvious part which I just didn't see.
I'm not supposed to monitor those interfaces with "--(Un)controlled" written next to them. There is proper interface for them instead.
Note to self - when replacing GigE interfaces with TenGigE and then monitoring them with Cacti, remember to reapply suggested interface names to replace old Gi5/1 graph titles with Te5/1. When debugging, I didn't check all the 300+ interfaces of snmpwalk output and assumed that I was looking at the right thing when the last interfaces of the ifIndex snmpwalk output referred to TenGigE ports.
thanks once again Vinod!
"feeling like an idiot" accomplished. over and out.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...