[c-nsp] cisco-nsp Digest, Vol 60, Issue 60
Padmavathi Chilukoori
paddams.2003 at gmail.com
Mon Nov 19 07:15:46 EST 2007
Hi Oli,
We have a scenario as below;
(LSR)
( LER) [ A ]---------[ B ]======[ C ] (LER)
|
|
[ D ]
( LER )
Following are the 2 signalled LSP's,
LSP1: A---B---C : with X bandwidth.
LSP2: D---B---C : with Y bandwidth.
These two LSP's are sharing the same link between LSR [B] and LER [c], Now,
1: We want to gaurantee LSP1 with X bandwidth, and LSP2 with Y bandwidth.
At LSR [B] how this bandwidths are gauranteed? Is there any scheduler
applied for this, if so, how? what exactly " reservation " of bandwidth
means?
2: If LSP1 is not utilizing its X bandwidth, then we want LSP2 to get that
bandwidth utilized.
How to implement these in Cisco Router & what are the features required?
Thanks in advance,
Padma.
On Nov 19, 2007 2:17 PM, <cisco-nsp-request at puck.nether.net > wrote:
> 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. Re: Invalid packet (too small) length=0
> (Oliver Boehmer (oboehmer))
> 2. Re: OSPF summarization (Oliver Boehmer (oboehmer))
> 3. Re: QoS on 6724/6148 (Oliver Boehmer (oboehmer))
> 4. Re: same Qos on multiple vlans (Oliver Boehmer (oboehmer))
> 5. Re: WRR between LSP's (Oliver Boehmer (oboehmer))
> 6. Re: DCEF and CPP (Gabor Ivanszky)
> 7. Re: Invalid packet (too small) length=0 (Nemeth Laszlo)
> 8. Re: Invalid packet (too small) length=0 (Nemeth Laszlo)
> 9. Re: Weird Error Message in 'sho ver' on GSR after upgrade
> (Arie Vayner (avayner))
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 19 Nov 2007 08:30:35 +0100
> From: "Oliver Boehmer (oboehmer)" <oboehmer at cisco.com>
> Subject: Re: [c-nsp] Invalid packet (too small) length=0
> To: "Nemeth Laszlo" <csirek at externet.hu>, <cisco-nsp at puck.nether.net>
> Message-ID:
> <
70B7A1CCBFA5C649BD562B6D9F7ED7840489FE05 at xmb-ams-333.emea.cisco.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Nemeth Laszlo <> wrote on Saturday, November 17, 2007 9:47 PM:
>
>
> > I received this messages yesterday:
> >
> > Nov 16 21:57:23: Invalid packet (too small) length=0
> > Nov 16 21:57:35: Invalid packet (too small) length=0
> > Nov 16 21:57:48: Invalid packet (too small) length=0
> > Nov 16 21:57:49: Invalid packet (too small) length=0
> > Nov 16 21:57:57: Invalid packet (too small) length=0
> > Nov 16 21:58:00 MET: %BGP-5-ADJCHANGE: neighbor xxx.xxx.xxx.4 Down BGP
> > Notification sent
> > Nov 16 21:58:00 MET: %BGP-3-NOTIFICATION: sent to neighbor
> > xxx.xxx.xxx.4 4/0 (hold time expired) 0 bytes
> > [..]
> >
> > The cpu usage went up to 100% a couple of seconds, and the router lost
> > some BGP peers.
> >
> > The router is a 7606 with Sup720-3BXL, ios:
> > s72033-adventerprisek9_wan- mz.122-18.SXF6.bin
> >
> > Any suggestions?
>
> Hmm, could this have been an attack on your router/infrastructure or a
> broken NIC sending these frames? Could be tricky to analyze (if you
> want, you would need to set up span port and work from there, but enable
> "no mls verify ip length minimum" to actually forward these illegal
> packets).
> You can also investigate using Control plane policing to protect the
> RP..
>
> oli
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 19 Nov 2007 08:34:33 +0100
> From: "Oliver Boehmer (oboehmer)" < oboehmer at cisco.com>
> Subject: Re: [c-nsp] OSPF summarization
> To: "Michael Malitsky" <malitsky at netabn.com>,
> <cisco-nsp at puck.nether.net>
> Message-ID:
> <70B7A1CCBFA5C649BD562B6D9F7ED7840489FE08 at xmb-ams-333.emea.cisco.com
>
> Content-Type: text/plain; charset="us-ascii"
>
> Michael Malitsky <> wrote on Monday, November 19, 2007 2:04 AM:
>
> > Hello,
> >
> > Looking for help with summarizing routes in OSPF. I have a VPN
> > headend which populates a bunch of host routes into OSPF. The
> > routes are contiguous, so I want to aggregate them. The headend
> > itself lacks such functionality, so I am trying to do this on the
> > next OSPF-capable device, which is a PIX v.7.2(2)23. PIX and VPN
> > headend are in area 1, everything else is area 0. On the PIX the
> > host routes show up as "O E2" - OSPF external type 2. I've tried
> > configuring an interarea summary: area 0 range 192.168.3.0
> > 255.255.255.0
> > That doesn't seem to do anything at all. I've also tried an external
> > summary: summary-address 192.168.3.0 255.255.255.0
> > Also does nothing.
>
> you can only summarize external routes on the ASBR. Depending on the
> topology, you could split the OSPF domain in two and use two different
> OSPF processes, redistributing between each other. But I would only
> consider this if the pain is too high. How many externals do you inject?
>
>
> oli
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 19 Nov 2007 08:35:56 +0100
> From: "Oliver Boehmer (oboehmer)" <oboehmer at cisco.com>
> Subject: Re: [c-nsp] QoS on 6724/6148
> To: "MKS" < rekordmeister at gmail.com>, <cisco-nsp at puck.nether.net>
> Message-ID:
> <70B7A1CCBFA5C649BD562B6D9F7ED7840489FE0D at xmb-ams-333.emea.cisco.com
>
> Content-Type: text/plain; charset="us-ascii"
>
> MKS <> wrote on Thursday, November 15, 2007 4:15 PM:
>
> > Hello list
> >
> > I want to terminate customers on cisco 7600 on either 6724 or 6148
> > line cards using subinterfaces.
> > However I need/want to be able to shape/policy and LLQ on each
> > subinterface.
> >
> > On software based routers e.g. 7200 I can do this on an subinterface
> > [...]
> > What are my options on the 6724 or 6148?
>
> You can only police on the cat LAN card, no shaping.
>
> > Buy SIP/SPA?
>
> Yes, guess so..
>
> oli
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 19 Nov 2007 08:40:45 +0100
> From: "Oliver Boehmer (oboehmer)" <oboehmer at cisco.com>
> Subject: Re: [c-nsp] same Qos on multiple vlans
> To: "Arne Larsen" < arl at nordicom.tele.dk>, <cisco-nsp at puck.nether.net>
> Message-ID:
> <70B7A1CCBFA5C649BD562B6D9F7ED7840489FE12 at xmb-ams-333.emea.cisco.com
>
> Content-Type: text/plain; charset="us-ascii"
>
> Arne Larsen <> wrote on Sunday, November 18, 2007 10:12 PM:
>
> > Hi Folks.
> >
> >
> >
> > Can anyone out there help me.
> >
> [..]
> >
> >
> > Is there an easy way to match the diffserv from the SBC on the
> > PE-router on all vlan's.
> >
> > Every vlan is configured with the same bandwidth.
>
> What type of QoS do you want to enforce? You can configure "mls qos
> trust dscp" on the ingress trunk port to classify the .1q packets based
> on the DSCP value in the IP packet to put them into the right WRR queue
> on the outgoing port..
> http://www.cisco.com/en/US/products/hw/switches/ps5023/products_tech_not
> e09186a0080883f9e.shtml has more information about QoS on the 3750..
>
> oli
>
>
> ------------------------------
>
> Message: 5
> Date: Mon, 19 Nov 2007 08:45:11 +0100
> From: "Oliver Boehmer (oboehmer)" <oboehmer at cisco.com>
> Subject: Re: [c-nsp] WRR between LSP's
> To: "Padmavathi Chilukoori" < paddams.2003 at gmail.com>,
> <cisco-nsp at puck.nether.net>
> Message-ID:
> <70B7A1CCBFA5C649BD562B6D9F7ED7840489FE1D at xmb-ams-333.emea.cisco.com
>
> Content-Type: text/plain; charset="us-ascii"
>
> Padmavathi Chilukoori <> wrote on Thursday, November 15, 2007 2:00 PM:
>
> > Hi,
> >
> > We would like to apply WRR (Weighted Round Robin)
> > across LSP's on Cisco.
> > Any idea about it? (Bandwidth for LSP's will be provided using
> > rsvp-te).
>
> which problem are you trying to solve? How do you route traffic via the
> different TE tunnels?
>
> oli
>
>
> ------------------------------
>
> Message: 6
> Date: Mon, 19 Nov 2007 08:31:36 +0100
> From: Gabor Ivanszky <ivanszky at niif.hu>
> Subject: Re: [c-nsp] DCEF and CPP
> To: Networkers < cisco at peakpeak.com>
> Cc: cisco-nsp at puck.nether.net
> Message-ID: <47413BD8.2090009 at niif.hu >
> Content-Type: text/plain; charset="iso-8859-2"
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> I am not sure on this, but on 7500 only dCEF is supported, and dCEF
> runs only on the linecards, and not on the RSP. Control plane policing
> should take place on the RSP, which in turn don't have any congestion
> mgmt/avoidance function at all.
>
> regards,
> Gabor
>
> Networkers wrote:
> > Hi I am trying to turn on control-plane policing on a 7500 with
> > RSP4 and VIP2/50's running 12.2(25)S12, and I have/get this:
> >
> > ip cef distributed ! class-map match-all TrustedControlAddresses
> > match access-group 153 ! policy-map AllowTrustedControlAddresses
> > class TrustedControlAddresses police cir 32000 bc 1500 be 1500
> > conform-action drop exceed-action drop
> >
> >
> > router(config)#control-plane router(config-cp)#service input
> > AllowTrustedControlAddresses service-policy is supported only on
> > VIP interfaces with DCEF enabled error: failed to install policy
> > map AllowTrustedControlAddresses
> >
> > I already have ip cef distributed in the config, and I did an ip
> > route-cache dist under the fast ethernet, ATM and DS3 interfaces
> > installed in the router. What am I missing?
> >
> > Thanks, Chris
> >
> >
> > _______________________________________________ cisco-nsp mailing
> > list cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp archive at
> > http://puck.nether.net/pipermail/cisco-nsp/
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFHQTvYDiqVI6Xm21MRAqGAAKCYbRDkhbVB0+o2Gk3GvmF5ByEznwCgmHUm
> F1hz3915AWdTcx9R3R2RXAA=
> =8Ybm
> -----END PGP SIGNATURE-----
>
>
> ------------------------------
>
> Message: 7
> Date: Mon, 19 Nov 2007 09:39:50 +0100
> From: Nemeth Laszlo <csirek at externet.hu >
> Subject: Re: [c-nsp] Invalid packet (too small) length=0
> To: cisco-nsp at puck.nether.net
> Message-ID: < 47414BD6.4080306 at externet.hu>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Dear Oli!
>
> Oliver Boehmer (oboehmer) i'rta:
> > Nemeth Laszlo <> wrote on Saturday, November 17, 2007 9:47 PM:
> >> I received this messages yesterday:
> >> Nov 16 21:57:23: Invalid packet (too small) length=0
> >> The router is a 7606 with Sup720-3BXL, ios:
> >> s72033-adventerprisek9_wan- mz.122-18.SXF6.bin
> >>
> >> Any suggestions?
> >
> > Hmm, could this have been an attack on your router/infrastructure or a
> > broken NIC sending these frames? Could be tricky to analyze (if you
> > want, you would need to set up span port and work from there, but enable
> > "no mls verify ip length minimum" to actually forward these illegal
> > packets).
> > You can also investigate using Control plane policing to protect the
> > RP..
> >
> > oli
>
> I don't know whitch was the source interface, i have lot of SVI and
ethernet
> interfaces so i think i can't do this monitoring :(
> This incident happened now so first simply, and since then not. I saw
nothing on
> my MRTG graphs (for example: big incomming packets or other interesting
> things...).
>
> I'll try this MLS command.
>
> Thank You!
>
> Laci
>
>
> ------------------------------
>
> Message: 8
> Date: Mon, 19 Nov 2007 09:41:57 +0100
> From: Nemeth Laszlo <csirek at externet.hu>
> Subject: Re: [c-nsp] Invalid packet (too small) length=0
> To: cisco-nsp at puck.nether.net
> Message-ID: <47414C55.1080306 at externet.hu>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Dear Oli!
>
> Oliver Boehmer (oboehmer) i'rta:
> > Nemeth Laszlo <> wrote on Saturday, November 17, 2007 9:47 PM:
> >> I received this messages yesterday:
> >> Nov 16 21:57:23: Invalid packet (too small) length=0
> >> The router is a 7606 with Sup720-3BXL, ios:
> >> s72033-adventerprisek9_wan-mz.122-18.SXF6.bin
> >>
> >> Any suggestions?
> >
> > Hmm, could this have been an attack on your router/infrastructure or a
> > broken NIC sending these frames? Could be tricky to analyze (if you
> > want, you would need to set up span port and work from there, but
enable
> > "no mls verify ip length minimum" to actually forward these illegal
> > packets).
> > You can also investigate using Control plane policing to protect the
> > RP..
> >
> > oli
>
> I don't know whitch was the source interface, i have lot of SVI and
ethernet
> interfaces so i think i can't do this monitoring :(
> This incident happened now so first simply, and since then not. I saw
nothing on
> my MRTG graphs (for example: big incomming packets or other interesting
> things...).
>
> I'll try this MLS command.
>
> Thank You!
>
> Laci
>
>
> ------------------------------
>
> Message: 9
> Date: Mon, 19 Nov 2007 09:46:36 +0100
> From: "Arie Vayner (avayner)" <avayner at cisco.com>
> Subject: Re: [c-nsp] Weird Error Message in 'sho ver' on GSR after
> upgrade
> To: "Michael K. Smith - Adhost" <mksmith at adhost.com>,
> <cisco-nsp at puck.nether.net>
> Message-ID:
> <67F7C1FAF83A074AA3520D8F155782A5A0F1AC at xmb-ams-331.emea.cisco.com
>
> Content-Type: text/plain; charset="us-ascii"
>
> Michael,
>
> Please try issuing the "test mbus clear-jam-counts [<slot>]" command.
> This should clear the warnings.
> If they reappear, it means that you have a problem on these cards. Then
> you should try to reseat the cards, and if it still keeps reappearing,
> RMA them...
>
> I strongly suggest you follow the whole procedure with a TAC case and
> direct guidance from TAC.
>
> Arie
>
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Michael K. Smith
> - Adhost
> Sent: Thursday, November 15, 2007 11:28 AM
> To: cisco-nsp at puck.nether.net
> Subject: [c-nsp] Weird Error Message in 'sho ver' on GSR after upgrade
>
> Hello All:
>
> I just upgraded from 12.0(28)S to 12.0(32)S8 on a 12008 and I'm now see
> this message in a show version.
>
> WARNING: Non-zero CAN jam reset counter in slot 18
> WARNING: Non-zero CAN jam reset counter in slot 19
> WARNING: Non-zero CAN jam reset counter in slot 20
>
> Those are the Switch Fabric Cards. I've searched on CCO but there's
> nothing that matches. Does anyone know what these mean?
>
> Regards,
>
> Mike
>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>
> ------------------------------
>
> _______________________________________________
> cisco-nsp mailing list
> cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
>
> End of cisco-nsp Digest, Vol 60, Issue 60
> *****************************************
>
More information about the cisco-nsp
mailing list