[c-nsp] cisco-nsp Digest, Vol 90, Issue 75

Alex Foster afoster at gammatelecom.com
Thu May 27 12:03:49 EDT 2010


Zzzzzzzzzzzzzzzzzzzz

--- original message ---
From: "cisco-nsp-request at puck.nether.net" <cisco-nsp-request at puck.nether.net>
Subject: cisco-nsp Digest, Vol 90, Issue 75
Date: 27th May 2010
Time: 4:59:40 pm


Send cisco-nsp mailing list submissions to
        cisco-nsp at puck.nether.net

To subscribe or unsubscribe via the World Wide Web, visit
        https://puck.nether.net/mailman/listinfo/cisco-nsp
or, via email, send a message with subject or body 'help' to
        cisco-nsp-request at puck.nether.net

You can reach the person managing the list at
        cisco-nsp-owner at puck.nether.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-nsp digest..."


Today's Topics:

   1. Cisco 7606 RSP720 - no SVI bit/packets counters (Dean Belev)
   2. Re: Link Discovery Error (jaikar gupta)
   3. Re: Link Discovery Error (Peter Rathlev)
   4. Re: sh module csm 2 probe real (Marco van den Bovenkamp)
   5. Re: Link Discovery Error (jaikar gupta)
   6. Re: Link Discovery Error (Peter Rathlev)


----------------------------------------------------------------------

Message: 1
Date: Thu, 27 May 2010 15:09:15 +0300
From: Dean Belev <dbelev at gmail.com>
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] Cisco 7606 RSP720 - no SVI bit/packets counters
Message-ID: <4BFE60EB.80602 at gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi all,

Another strange Cisco behavior - or may be unknown one.
Creating SVI interface with a lot of traffic passing through - nothing
suspicious.
Until ...

/7606#sh int vlan XXX
Vlan537 is up, line protocol is up
   Hardware is EtherSVI, address is MAC (bia 001c.b0b7.6400)
   Description: 0449-070C001#NetLan_Int
   Internet address is IP/30
   MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
      reliability 255/255, txload 1/255, rxload 0/255
   Encapsulation ARPA, loopback not set
   Keepalive not supported
   ARP type: ARPA, ARP Timeout 04:00:00
   Last input 00:00:00, output 00:00:00, output hang never
   Last clearing of "show interface" counters 00:08:18
   Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
   Queueing strategy: fifo
   Output queue: 0/40 (size/max)
*30 second input rate 0 bits/sec, 0 packets/sec
   30 second output rate 0 bits/sec, 0 packets/sec*
L2 Switched: ucast: 25025 pkt, 2426613 bytes - mcast: 0 pkt, 0 bytes
   L3 in Switched: ucast: 3597038 pkt, 3755053095 bytes - mcast: 0 pkt,
0 bytes mcast
   L3 out Switched: ucast: 2000511 pkt, 602156179 bytes mcast: 0 pkt, 0
bytes
      3678505 packets input, 3803335802 bytes, 0 no buffer
      Received 0 broadcasts (0 IP multicasts)
      0 runts, 0 giants, 0 throttles
      0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
      1899084 packets output, 568639522 bytes, 0 underruns
      0 output errors, 0 interface resets
      0 unknown protocol drops
      0 output buffer failures, 0 output buffers swapped out/
####
7606#sh int vlan XXX summary

  *: interface is up
  IHQ: pkts in input hold queue     IQD: pkts dropped from input queue
  OHQ: pkts in output hold queue    OQD: pkts dropped from output queue
  RXBS: rx rate (bits/sec)          RXPS: rx rate (pkts/sec)
  TXBS: tx rate (bits/sec)          TXPS: tx rate (pkts/sec)
  TRTL: throttle count

   Interface                  IHQ      IQD      OHQ      OQD
RXBS     RXPS     TXBS     TXPS     TRTL
--------------------------------------------------------------------------------------------------------
*VlanXXX                       0        0        0        0 *0
0        0        0 *      0
#######

All counters but RXBS/RXPS/TXBS/TXPS showing there is a traffic (~400 Mbps).
Also visible using MIB values. But the SVI bits/packets not showing it.
There are 146 SVIs configured there (we have another Cisco 7609 RSP720
with 393 ones and no such a problem present).
We deleted around 10 interfaces trying to release any resources -
without result, delete/create the interface - the same.

Is there any limit I do not know. I tried to read about any limits of
the number of  SVIs - no result.
Are there any assumptions?

Thank you in advance!

Best~

/Dean Belev
Network Management Team
Neterra Ltd.
Sofia, Bulgaria
Phone:    +359 2 974 33 11
Fax:    +359 2 975 34 36
Mobile:    +359 886 663 123
http://www.neterra.net/


------------------------------

Message: 2
Date: Thu, 27 May 2010 17:57:40 +0530
From: jaikar gupta <gupta.jaikar at gmail.com>
To: Lincoln Dale <ltd at cisco.com>
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Link Discovery Error
Message-ID:
        <AANLkTik89TIJetv9moudTIFbR7YSyKeh1ajuO2Itc9t9 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hello Lincoln Dale,

ipNetToMediaTable contains the entry of all the devices which are reachable
from the router but i want to know the devices which are directly connected
with the router.

Thanks & Regards
Jaikar Gupta


On Thu, May 27, 2010 at 6:55 AM, Lincoln Dale <ltd at cisco.com> wrote:

> On 26/05/2010, at 10:30 PM, jaikar gupta wrote:
> > But when we introduce the Cisco Routers (2509 series) in the network and
> run
> > the discovery it doesnt show the links between the Router-Switch as well
> as
> > Router-Router,
> >
> > The problem with the Link discover is that their is no value in the
> > dot1dTpFdbPort(1.3.6.1.2.1.17.4.3.1.2.) OID in Cisco Router.
> > This OID is responsible for creating/finding Neighbours in code.
>
> BRIDGE-MIB is used on Bridges, i.e. switches.
>
> a Cisco c2509 router is not a bridge, its a router with L3 interfaces.
>
>
> cheers,
>
> lincoln.


------------------------------

Message: 3
Date: Thu, 27 May 2010 14:46:11 +0200
From: Peter Rathlev <peter at rathlev.dk>
To: jaikar gupta <gupta.jaikar at gmail.com>
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Link Discovery Error
Message-ID: <1274964371.8452.2.camel at localhost>
Content-Type: text/plain; charset="ISO-8859-1"

On Thu, 2010-05-27 at 17:57 +0530, jaikar gupta wrote:
> ipNetToMediaTable contains the entry of all the devices which are
> reachable from the router but i want to know the devices which are
> directly connected with the router.

You either want MAC-addresses or CDP neighbor information, right? For
the latter you can use CISCO-CDP-MIB::cdpCache*. Newer devices might
support LLDP-MIB instead, which is more cross-platform compatible.

If you're just doing neighbor discovery, what do you need the MAC
address tables/ARP tables for?

--
Peter




------------------------------

Message: 4
Date: Thu, 27 May 2010 14:04:31 +0200
From: Marco van den Bovenkamp <marco at linuxgoeroe.dhs.org>
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] sh module csm 2 probe real
Message-ID: <4BFE5FCF.9010208 at linuxgoeroe.dhs.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 27-5-2010 13:54, Church, Charles wrote:
> Looks like maybe it's computing time wrong.  That date is surprisingly close to the start of UNIX time, which was Jan 1, 1970.
>
> Chuck
>
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Sony Scaria
> Sent: Thursday, May 27, 2010 3:30 AM
> To: cisco-nsp at puck.nether.net
> Subject: [c-nsp] sh module csm 2 probe real
>
>
> hello group,
>
> Can someone please explain me why it is showing "13:36:47 gmt 06/14/70".
> I've searched a lot, but i couldnt find any explanation.
> btw, my switch is sync with precent time.
>
> Switch#sh module csm 2 probe real
>    real = 10.106.110.17:53, probe = PROBE-DNS, type = dns,
>      vserver = W-DNSTCP-O, sfarm = W-DNSTCP-O
>      status = OPERABLE,* current = 13:36:47 gmt 06/14/70,
> *    successes = 236591, last success* = 13:36:48 gmt 06/14/70,*
>      failures = 144, last failure = *09:58:50 gmt 06/11/70,*
>      state = Server is healthy.
>    real = 10.106.110.17:53, probe = PROBE-DNS, type = dns,
>      vserver = W-DNS-O, sfarm = W-DNS-O
>      status = OPERABLE, current = 13:36:47 gmt 06/14/70,
>      successes = 236591, last success = 13:36:48 gmt 06/14/70,
>      failures = 144, last failure = 09:58:50 gmt 06/11/70,
>      state = Server is healthy.
> Switch#sh clock
> 07:26:16.712 gmt Thu May 27 2010

Lemme guess: uptime of the box is 6 months and two weeks? It probably is
converting the uptime to a date counting from the Unix epoch.

                Regards,

                        Marco.


------------------------------

Message: 5
Date: Thu, 27 May 2010 18:45:25 +0530
From: jaikar gupta <gupta.jaikar at gmail.com>
To: Peter Rathlev <peter at rathlev.dk>
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Link Discovery Error
Message-ID:
        <AANLkTim_qT3ZxDRrLsu6mWWveFUs5UC74hKhf7KwIDES at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Thanks peter but i want to Know MAC-addresses.


Thanks & Regards
Jaikar Gupta


On Thu, May 27, 2010 at 6:16 PM, Peter Rathlev <peter at rathlev.dk> wrote:

> On Thu, 2010-05-27 at 17:57 +0530, jaikar gupta wrote:
> > ipNetToMediaTable contains the entry of all the devices which are
> > reachable from the router but i want to know the devices which are
> > directly connected with the router.
>
> You either want MAC-addresses or CDP neighbor information, right? For
> the latter you can use CISCO-CDP-MIB::cdpCache*. Newer devices might
> support LLDP-MIB instead, which is more cross-platform compatible.
>
> If you're just doing neighbor discovery, what do you need the MAC
> address tables/ARP tables for?
>
> --
> Peter
>
>
>


------------------------------

Message: 6
Date: Thu, 27 May 2010 16:01:00 +0200
From: Peter Rathlev <peter at rathlev.dk>
To: jaikar gupta <gupta.jaikar at gmail.com>
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Link Discovery Error
Message-ID: <1274968860.8452.5.camel at localhost>
Content-Type: text/plain; charset="ISO-8859-1"

On Thu, 2010-05-27 at 18:45 +0530, jaikar gupta wrote:
> Thanks peter but i want to Know MAC-addresses.

Then you use BRIDGE-MIB for switches, and RFC1213-MIB for routers. :-)

Disregarding certain special cases a router will only know MAC addresses
in combination with IP addresses. It does not (usually) bridge just L2
traffic.

Maybe you could rewind a liltle and explain exactly what problem you're
trying to solve?

--
Peter





------------------------------

_______________________________________________
cisco-nsp mailing list
cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp

End of cisco-nsp Digest, Vol 90, Issue 75
*****************************************

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

This is an email from Gamma Telecom Ltd. The contents of this email are confidential to the ordinary user of the email address to which it was addressed. No-one else may place any reliance upon it, or copy or  forward all or any of it in any form (unless otherwise notified). If you receive this email in error, please accept our apology. We should be obliged if you would telephone our postmaster on +44 (0) 808 178 9652 or email itsupport at gammatelecom.com

Gamma Telecom Limited, a company incorporated in  England and Wales, with limited liability, with registered number 4340834, and whose registered office is at 5 Fleet Place London EC4M 7RD and whose  principal place of business is at 1, The Pentangle, Park Street, Newbury Berkshire RG14 1EA.

Main telephone number: +44 (0) 333 240 3000 
Website: http://www.gammatelecom.com
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________



More information about the cisco-nsp mailing list