Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cisco: NSP

ipv6 traffic graph

 

 

Cisco nsp RSS feed   Index | Next | Previous | View Threaded


sgala at sgala

May 21, 2012, 2:11 PM

Post #1 of 7 (1522 views)
Permalink
ipv6 traffic graph

Hi,

how do you graph your ipv6 traffic on a cisco router if you have an interface that route v4 and v6 mixed traffic?

Does exist a MIB to do this or whatever else?

Thanks!

Matteo
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


chip.gwyn at gmail

May 21, 2012, 3:20 PM

Post #2 of 7 (1477 views)
Permalink
Re: ipv6 traffic graph [In reply to]

I've been screen scraping "show interfaces accounting" and taking the
data from the IPv6 row and shoving it into RRD. Be aware of the
following however:

The Pkts Out and Chars Out fields display IPv6 packet counts only. The
Pkts In and Chars In fields display both IPv4 and IPv6 packet counts,
except for tunnel interfaces. For tunnel interfaces, the IPv6 input
packets are counted as IPv6 packets only.

Due to hardware limitations on the ASIC, PFC IPv4 and IPv6 packets
cannot be differentiated in the Pkts In and Chars In fields for IP
count the IPv6 and IPv4 packets that are hardware forwarded. The Pkts
In and Chars In fields for IPv6 only count software-forwarded packets.
The IP Pkts Out and Chars Out fields show IPv4 packets, and the IPv6
Pkts Out and Chars Out fields show IPv6 packets.

http://www.cisco.com/en/US/docs/ios/interface/command/reference/ir_s4.html#wp1241100


Hope that helps a bit.

--chip


On Mon, May 21, 2012 at 5:11 PM, Matteo Sgalaberni <sgala [at] sgala> wrote:
> Hi,
>
> how do you graph your ipv6 traffic on a cisco router if you have an interface that route v4 and v6 mixed traffic?
>
> Does exist a MIB to do this or whatever else?
>
> Thanks!
>
> Matteo
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/



--
Just my $.02, your mileage may vary,  batteries not included, etc....

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


gert at greenie

May 22, 2012, 12:35 AM

Post #3 of 7 (1466 views)
Permalink
Re: ipv6 traffic graph [In reply to]

Hi,

On Mon, May 21, 2012 at 06:20:35PM -0400, chip wrote:
> I've been screen scraping "show interfaces accounting" and taking the
> data from the IPv6 row and shoving it into RRD. Be aware of the
> following however:
>
> The Pkts Out and Chars Out fields display IPv6 packet counts only. The
> Pkts In and Chars In fields display both IPv4 and IPv6 packet counts,
> except for tunnel interfaces. For tunnel interfaces, the IPv6 input
> packets are counted as IPv6 packets only.

That's for 6500/7600 with Sup720. Other platforms do not have this
particular weirdness.

gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany gert [at] greenie
fax: +49-89-35655025 gert [at] net


sgala at sgala

Jun 7, 2012, 11:05 PM

Post #4 of 7 (1359 views)
Permalink
Re: ipv6 traffic graph [In reply to]

I opened a TAC to Cisco and finally they told me these OID:

ipIfStatsTable
http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en&translate=Translate&objectInput=1.3.6.1.2.1.4.31.3#oidContent

ipIfStatsEntry
http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en&translate=Translate&objectInput=1.3.6.1.2.1.4.31.3.1#oidContent

but are only supported on > 15.1(3)T

can someone try them and tell me if these are running or not. I don't have any routers with that IOS version.

I understood that the Cisco engineers (and IOS developers) are a bit not sure about this... and I'm not trust very well on this feedback...

Matteo
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


sgala at sgala

Jun 7, 2012, 11:39 PM

Post #5 of 7 (1356 views)
Permalink
Re: ipv6 traffic graph [In reply to]

----- Original Message -----
> Matteo, we're running ipv6 on a pair of ASR1004's running
> IOS-XE verison 15.2(1)S2. Is there an snmpwalk command
> I can run for you that would tell if the needed info is
> present?

Hi David,

it depends on your SNMP security schema, but if you have a simple read community you can use these commands:

snmpwalk -c $YOURCOMMUNITY -v2c $IP 1.3.6.1.2.1.4.31.3
snmpwalk -c $YOURCOMMUNITY -v2c $IP 1.3.6.1.2.1.4.31.3.1

Thanks

Matteo

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


kka at netuse

Jun 7, 2012, 11:39 PM

Post #6 of 7 (1379 views)
Permalink
Re: ipv6 traffic graph [In reply to]

Hi Matteo,

> ipIfStatsTable
> http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en&translate=Translate&objectInput=1.3.6.1.2.1.4.31.3#oidContent
>
> ipIfStatsEntry
> http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en&translate=Translate&objectInput=1.3.6.1.2.1.4.31.3.1#oidContent
>
> but are only supported on > 15.1(3)T
>
> can someone try them and tell me if these are running or not. I don't have any routers with that IOS version.

Here is the output from a 2821 with Advanced IP Services 15.1(4)M:

IP-MIB::ipIfStatsInReceives.ipv4.17 = Counter32: 9438557
IP-MIB::ipIfStatsInReceives.ipv6.17 = Counter32: 21058
IP-MIB::ipIfStatsHCInReceives.ipv4.17 = Counter64: 9438557
IP-MIB::ipIfStatsHCInReceives.ipv6.17 = Counter64: 21058
IP-MIB::ipIfStatsInOctets.ipv4.17 = Counter32: 776641981
IP-MIB::ipIfStatsInOctets.ipv6.17 = Counter32: 1583364
IP-MIB::ipIfStatsHCInOctets.ipv4.17 = Counter64: 776641981
IP-MIB::ipIfStatsHCInOctets.ipv6.17 = Counter64: 1583364
IP-MIB::ipIfStatsInHdrErrors.ipv4.17 = Counter32: 9
IP-MIB::ipIfStatsInHdrErrors.ipv6.17 = Counter32: 0
IP-MIB::ipIfStatsInNoRoutes.ipv4.17 = Counter32: 0
IP-MIB::ipIfStatsInNoRoutes.ipv6.17 = Counter32: 3091
IP-MIB::ipIfStatsInAddrErrors.ipv4.17 = Counter32: 2612
IP-MIB::ipIfStatsInAddrErrors.ipv6.17 = Counter32: 0
IP-MIB::ipIfStatsInUnknownProtos.ipv4.17 = Counter32: 0
IP-MIB::ipIfStatsInUnknownProtos.ipv6.17 = Counter32: 0
IP-MIB::ipIfStatsInTruncatedPkts.ipv4.17 = Counter32: 0
IP-MIB::ipIfStatsInTruncatedPkts.ipv6.17 = Counter32: 0
IP-MIB::ipIfStatsInForwDatagrams.ipv4.17 = Counter32: 39561
IP-MIB::ipIfStatsInForwDatagrams.ipv6.17 = Counter32: 4769
IP-MIB::ipIfStatsHCInForwDatagrams.ipv4.17 = Counter64: 39561
IP-MIB::ipIfStatsHCInForwDatagrams.ipv6.17 = Counter64: 4769
IP-MIB::ipIfStatsReasmReqds.ipv4.17 = Counter32: 0
IP-MIB::ipIfStatsReasmReqds.ipv6.17 = Counter32: 0
IP-MIB::ipIfStatsReasmOKs.ipv4.17 = Counter32: 0
IP-MIB::ipIfStatsReasmOKs.ipv6.17 = Counter32: 0
IP-MIB::ipIfStatsReasmFails.ipv4.17 = Counter32: 0
IP-MIB::ipIfStatsReasmFails.ipv6.17 = Counter32: 0
IP-MIB::ipIfStatsInDiscards.ipv4.17 = Counter32: 0
IP-MIB::ipIfStatsInDiscards.ipv6.17 = Counter32: 0
IP-MIB::ipIfStatsInDelivers.ipv4.17 = Counter32: 5943525
IP-MIB::ipIfStatsInDelivers.ipv6.17 = Counter32: 16289
IP-MIB::ipIfStatsHCInDelivers.ipv4.17 = Counter64: 5943525
IP-MIB::ipIfStatsHCInDelivers.ipv6.17 = Counter64: 16289
IP-MIB::ipIfStatsOutRequests.ipv4.17 = Counter32: 14093597
IP-MIB::ipIfStatsOutRequests.ipv6.17 = Counter32: 6997
IP-MIB::ipIfStatsHCOutRequests.ipv4.17 = Counter64: 14093597
IP-MIB::ipIfStatsHCOutRequests.ipv6.17 = Counter64: 6997
IP-MIB::ipIfStatsOutForwDatagrams.ipv4.17 = Counter32: 4121
IP-MIB::ipIfStatsOutForwDatagrams.ipv6.17 = Counter32: 1678
IP-MIB::ipIfStatsHCOutForwDatagrams.ipv4.17 = Counter64: 4121
IP-MIB::ipIfStatsHCOutForwDatagrams.ipv6.17 = Counter64: 1678
IP-MIB::ipIfStatsOutDiscards.ipv4.17 = Counter32: 0
IP-MIB::ipIfStatsOutDiscards.ipv6.17 = Counter32: 17
IP-MIB::ipIfStatsOutFragReqds.ipv4.17 = Counter32: 0
IP-MIB::ipIfStatsOutFragReqds.ipv6.17 = Counter32: 0
IP-MIB::ipIfStatsOutFragOKs.ipv4.17 = Counter32: 0
IP-MIB::ipIfStatsOutFragOKs.ipv6.17 = Counter32: 0
IP-MIB::ipIfStatsOutFragFails.ipv4.17 = Counter32: 0
IP-MIB::ipIfStatsOutFragFails.ipv6.17 = Counter32: 0
IP-MIB::ipIfStatsOutFragCreates.ipv4.17 = Counter32: 0
IP-MIB::ipIfStatsOutFragCreates.ipv6.17 = Counter32: 0
IP-MIB::ipIfStatsOutTransmits.ipv4.17 = Counter32: 14097709
IP-MIB::ipIfStatsOutTransmits.ipv6.17 = Counter32: 8658
IP-MIB::ipIfStatsHCOutTransmits.ipv4.17 = Counter64: 14097709
IP-MIB::ipIfStatsHCOutTransmits.ipv6.17 = Counter64: 8658
IP-MIB::ipIfStatsOutOctets.ipv4.17 = Counter32: 1109298546
IP-MIB::ipIfStatsOutOctets.ipv6.17 = Counter32: 877639
IP-MIB::ipIfStatsHCOutOctets.ipv4.17 = Counter64: 1109298546
IP-MIB::ipIfStatsHCOutOctets.ipv6.17 = Counter64: 877639
IP-MIB::ipIfStatsInMcastPkts.ipv4.17 = Counter32: 5416789
IP-MIB::ipIfStatsInMcastPkts.ipv6.17 = Counter32: 14246
IP-MIB::ipIfStatsHCInMcastPkts.ipv4.17 = Counter64: 5416789
IP-MIB::ipIfStatsHCInMcastPkts.ipv6.17 = Counter64: 14246
IP-MIB::ipIfStatsInMcastOctets.ipv4.17 = Counter32: 415376568
IP-MIB::ipIfStatsInMcastOctets.ipv6.17 = Counter32: 1014216
IP-MIB::ipIfStatsHCInMcastOctets.ipv4.17 = Counter64: 415376568
IP-MIB::ipIfStatsHCInMcastOctets.ipv6.17 = Counter64: 1014216
IP-MIB::ipIfStatsOutMcastPkts.ipv4.17 = Counter32: 12744699
IP-MIB::ipIfStatsOutMcastPkts.ipv6.17 = Counter32: 79
IP-MIB::ipIfStatsHCOutMcastPkts.ipv4.17 = Counter64: 12744699
IP-MIB::ipIfStatsHCOutMcastPkts.ipv6.17 = Counter64: 79
IP-MIB::ipIfStatsOutMcastOctets.ipv4.17 = Counter32: 1019575818
IP-MIB::ipIfStatsOutMcastOctets.ipv6.17 = Counter32: 5696
IP-MIB::ipIfStatsHCOutMcastOctets.ipv4.17 = Counter64: 1019575818
IP-MIB::ipIfStatsHCOutMcastOctets.ipv6.17 = Counter64: 5696
IP-MIB::ipIfStatsInBcastPkts.ipv4.17 = Counter32: 2342017
IP-MIB::ipIfStatsInBcastPkts.ipv6.17 = Counter32: 0
IP-MIB::ipIfStatsHCInBcastPkts.ipv4.17 = Counter64: 2342017
IP-MIB::ipIfStatsHCInBcastPkts.ipv6.17 = Counter64: 0
IP-MIB::ipIfStatsOutBcastPkts.ipv4.17 = Counter32: 0
IP-MIB::ipIfStatsOutBcastPkts.ipv6.17 = Counter32: 0
IP-MIB::ipIfStatsHCOutBcastPkts.ipv4.17 = Counter64: 0
IP-MIB::ipIfStatsHCOutBcastPkts.ipv6.17 = Counter64: 0
IP-MIB::ipIfStatsDiscontinuityTime.ipv4.17 = Timeticks: (0) 0:00:00.00
IP-MIB::ipIfStatsDiscontinuityTime.ipv6.17 = Timeticks: (0) 0:00:00.00


Best regards,
Klaus

--
Klaus Kastens NetUSE AG
Dr.-Hell-Str. 6, D-24107 Kiel, Germany
Fon: +49 431 2390 400 (06:00 UTC - 16:00 UTC)
Fax: +49 431 2390 499











Vorstand: Dr. Joerg Posewang (Vorsitz), Dr. Roland Kaltefleiter, Andreas Seeger
Aufsichtsrat: Dr. Dirk Lukas (Vorsitz)
Sitz der AG: Kiel, HRB 5358 USt.ID: DE156073942

Diese E-Mail enthaelt vertrauliche oder rechtlich geschuetzte Informationen.
Das unbefugte Kopieren dieser E-Mail oder die unbefugte Weitergabe der
enthaltenen Informationen ist nicht gestattet.

The information contained in this message is confidential or protected by
law. Any unauthorised copying of this message or unauthorised distribution
of the information contained herein is prohibited.

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


sgala at sgala

Jun 8, 2012, 12:01 AM

Post #7 of 7 (1364 views)
Permalink
Re: ipv6 traffic graph [RESOLVED] [In reply to]

----- Original Message -----
> Hi Matteo,
> Here is the output from a 2821 with Advanced IP Services 15.1(4)M:
>
Hi Klaus, wonderful!

So definitively with this new MIB you can make two different IPv4/IPv6 graphs using these OIDs:

For IPv4 only
> IP-MIB::ipIfStatsHCInOctets.ipv4.17 = Counter64: 776641981
> IP-MIB::ipIfStatsHCOutOctets.ipv4.17 = Counter64: 1109298546

For IPv6 only
> IP-MIB::ipIfStatsHCInOctets.ipv6.17 = Counter64: 1583364
> IP-MIB::ipIfStatsHCOutOctets.ipv6.17 = Counter64: 877639

Obviously I immagine that 17 is the ifIndex.

Very very nice.

I will tell thank also the Cisco support, they did a great job, we worked almost 15 days on this ticket and were involved also IOS developers to get a serious answer;)

Thanks,

Matteo
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Cisco nsp RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.