[c-nsp] What does Storm Control really does in Catalyst switches

Servio Lima slima at telconet.net
Fri Dec 29 11:10:04 EST 2006


Hi

I'd like to know how does storm-control unicast in Catalysts switches 
really work, meaning what is really going on at the memory and 
process level whenever an unicast packet arrives to a port with storm 
control enabled. Does the port discriminates between "valid" unicast 
traffic (unicast packets really aimed to the user connected to the 
port) and "invalid" unicast traffic (traffic whose destination is 
somebody else but arrives to the port)?

Servio


At 14:55 28/12/2006, 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: risks of service contract non-renewal (Rodney Dunn)
>    2. Re: Input Queue 7500 (Rodney Dunn)
>    3. Re: upgrade firmware on Cat6k / CatOS modules?
>       (Sukumar Subburayan)
>    4. NAT Translation ques.. (Christian Koch)
>    5. Re: NAT Translation ques.. (Church, Chuck)
>    6. Re: NAT Translation ques.. (Christian Koch)
>    7. Re: Etherchannel (Eusebio L?pez)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Thu, 28 Dec 2006 12:16:08 -0500
>From: Rodney Dunn <rodunn at cisco.com>
>Subject: Re: [c-nsp] risks of service contract non-renewal
>To: Adam Greene <maillist at webjogger.net>
>Cc: cisco-nsp at puck.nether.net
>Message-ID: <20061228121607.C6333 at rtp-cse-489.cisco.com>
>Content-Type: text/plain; charset=us-ascii
>
>There are always pros and cons.
>
>One con is your support contract helps pay on the backend a lot
>of the Cisco folks that contribute here on these aliases. :)
>
>That's a pro hopefully for keeping the conract. :)
>
>Happy Holidays...
>
>
>On Thu, Dec 28, 2006 at 11:53:12AM -0500, Adam Greene wrote:
> > Thanks to all who replied to this question, both on and off list. Your
> > replies were very helpful!!!
> >
> >
> >
> > ----- Original Message -----
> > From: "Mark D. Nagel" <mnagel at willingminds.com>
> > To: <cisco-nsp at puck.nether.net>
> > Sent: Friday, December 22, 2006 6:16 PM
> > Subject: Re: [c-nsp] risks of service contract non-renewal
> >
> >
> > > Adam Greene wrote:
> > >> I've got a customer who is thinking of letting the service contracts on
> > >> its Cisco gear (L2 and L3 switches) expire, since the switches have
> > >> limited lifetime warranties, they have cold spares and if they need
> > >> technical assistance, they can ask yours truly.
> > >>
> > >> I think the risk of doing this is that they will lose access 
> to software
> > >> upgrades, except in the case of free upgrades to redress security
> > >> vulnerabilities.
> > >>
> > >> I wonder if there are any other risks they should be aware of. I assume
> > >> they will still be able to gain access to CCO even without a valid
> > >> service contract, for example.
> > >>
> > >>
> > >
> > > Firmware updates (not upgrades, i.e., IP Base to Advanced IP) for fixed
> > > switches are also available free on CCO, so unless you need TAC support
> > > or need faster than 10 business day RMA turnaround, you should be OK.
> > > For more details, see:
> > >
> > > 
> http://www.cisco.com/en/US/products/hw/switches/ps4916/products_qanda_item09186a0080185383.shtml
> > >
> > > Relevant excerpt:
> > >
> > > *Q.* How do I get a "no additional cost" Cisco IOS Software update for
> > > my fixed-configuration or stackable Cisco Catalyst switch?
> > > *A.* Customers that own a software license for any of the eligible
> > > fixed-configuration or stackable Cisco Catalyst series may obtain a
> > > software update at Cisco.com.
> > > Visit
> > > http://tools.cisco.com/support/downloads/pub/MDFTree.x?butype=switches,
> > > or from http://www.cisco.com <http://www.cisco.com/>, click on
> > > "Downloads" and select "Switch Software". Downloading software requires
> > > a Cisco.com username and password. If you do not have a Cisco.com
> > > username, you can obtain one by clicking on "Register" at the top of any
> > > Cisco.com Webpage (http://tools.cisco.com/RPF/register/register.do).
> > >
> > > WARRANTY AND SERVICE
> > >
> > > The hardware warranty available on Cisco Catalyst 3750, 3560, 3550, 3500
> > > XL, 2970, 2960, 2950/LRE, 2940, 2900 XL, and Express 500 Series switches
> > > is the Limited Lifetime Hardware Warranty. This warranty automatically
> > > comes with the purchase of eligible Cisco Catalyst products, free of
> > > charge. It offers free advanced replacement of products within 10
> > > business days. For more information about the Limited Lifetime Hardware
> > > Warranty, visit:
> > > 
> http://www.cisco.com/en/US/products/prod_warranties_item09186a00800e6e6e.html.
> > >
> > >
> > > Regards,
> > > Mark
> > >
> > > --
> > > Mark D. Nagel, CCIE #3177 <mnagel at willingminds.com>
> > > Principal Consultant, Willing Minds LLC (http://www.willingminds.com)
> > > cell: 949-279-5817, desk: 714-630-4772, fax: 949-623-9854
> > >
> > > _______________________________________________
> > > 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
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>
>------------------------------
>
>Message: 2
>Date: Thu, 28 Dec 2006 12:17:39 -0500
>From: Rodney Dunn <rodunn at cisco.com>
>Subject: Re: [c-nsp] Input Queue 7500
>To: omar parihuana <omar.parihuana at gmail.com>
>Cc: nsp <cisco-nsp at puck.nether.net>
>Message-ID: <20061228121739.D6333 at rtp-cse-489.cisco.com>
>Content-Type: text/plain; charset=us-ascii
>
>It's a long email to explain in detail so let's just start simple:
>
>'sh run' of the interfaces that this traffic is coming in and going
>out of.
>
>clear count
>
>and get 'sh int stat' every 30 seconds for 2 minutes so we can see
>what % is being process switched. Get 'sh cef int' and 'sh ip int'
>for all interfaces.
>
>What type of traffic is it? internet? etc...?
>
>On Wed, Dec 27, 2006 at 06:11:11PM -0500, omar parihuana wrote:
> > Thanks Anton for your reply.
> >
> > CEF is enable (ip cef global configuration command is configured):
> >
> > R#show interfaces switching
> > FastEthernet4/1/0
> >           Throttle count          8
> >         Drops         RP        491         SP          0
> >   SPD Flushes       Fast       2561        SSE          0
> >   SPD Aggress       Fast          0
> >  SPD Priority     Inputs          0      Drops          0
> >
> >      Protocol       Path    Pkts In   Chars In   Pkts Out  Chars Out
> >         Other    Process          0          0     436870   26212200
> >             Cache misses          0
> >                     Fast          0          0          0          0
> >                Auton/SSE          0          0          0          0
> >            IP    Process 2226190620 2002650219 2393235708 2822177457
> >             Cache misses        623
> >                     Fast 1763768067  234570619 1779057481 4136533720
> >                Auton/SSE          0          0          0          0
> >       DEC MOP    Process          0          0       7270     559790
> >             Cache misses          0
> >                     Fast          0          0          0          0
> >                Auton/SSE          0          0          0          0
> >
> > Also, I enable ip route-cache flow in this interface because 
> there is a long
> > access-list (in accordance to suggestion the previous link -the drops and
> > flash increase slower than without the ip route-cache flow) Currently the
> > 7513 is attached to Black Box (Allied Telesin Switch, that unfortunately, I
> > don't have admin) is possible that Allied Telesin Switch cause this input
> > queue drops, because the low performance of Allied, sometimes the CPU
> > processor reach 80% too.
> >
> > 7513-118.1#sh cef drop
> > CEF Drop Statistics
> > Slot  Encap_fail  Unresolved 
> Unsupported    No_route      No_adj  ChkSum_Err
> > 
> RP          3747           0         656          32           0           0
> > 7513-118.1#
> >
> > So far, unfortunately, the counter is increasing...
> >
> > Input queue: 56/75/247/178 (size/max/drops/flushes); Total output drops: 0
> >
> > Thanks!!
> >
> > Rgds.
> >
> >
> > On 12/27/06, Anton Kapela <tk at 5ninesdata.com> wrote:
> > >
> > >
> > >
> > > > I've noticed the input queue interface ethernet from my 7513
> > > > (drops and flushes is increasing)
> > >
> > > That counter doesn't mean what Cisco lets you think it means....
> > >
> > > >  Encapsulation ARPA, loopback not set
> > > >   Keepalive set (10 sec)
> > > >   Full-duplex, 100Mb/s, 100BaseTX/FX
> > > >   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:35:20
> > > >   Input queue: 5/75/1053/6148 (size/max/drops/flushes); Total
> > > > output drops:
> > > > 0   <<<<< SEE HERE!
> > >
> > > > This behavior is normal, for that traffic (About 45Mbps in
> > > > some cases) ???
> > >
> > > That should not be observed unless you're: running cef-less, being
> > > directly attacked, or attached to noisy-ass layer-2 that faces, oh, say,
> > > a few thousand collocation customers with 50 or 60 ip address
> > > secondary's configured. Any of those situations could be causing what
> > > you're seeing, and let me be clear: none of them would be characterized
> > > as normal.
> > >
> > > > How can I decrease that counters? some suggestions for set up
> > > > in Ethernet Interface???
> > >
> > > First of all, 'sh int' input queue is a depiction of the state of
> > > packets which were placed into queue for the "ip_input" process; i.e.
> > > these are packets waiting to be "process switched." This is generally
> > > bad. Before you go any further in troubleshooting this, check to ensure
> > > that cef is enabled on your router.
> > >
> > > If it is, then start debugging and checking your switching path. You can
> > > do this by becoming more familiar with the 7500 switching architecture.
> > > I'd suggest the following URLs to get yourself started:
> > >
> > > 1)      http://tinyurl.com/7fw4p
> > >
> > > Be sure to focus on this part of the page:
> > >
> > > 2)      http://tinyurl.com/wg8qz
> > >
> > >
> > > Also, use the following commands on interfaces which you're seeing the
> > > input queue drops on:
> > >
> > > #sh int FastEthernet3/0/0 switching
> > >
> > > #sh int FastEthernet3/0/0 stats
> > >
> > > #sh int FastEthernet3/0/0 accounting
> > >
> > > In a nutshell, when you see actual ip_input queue drops (which is what
> > > the 'sh int' is displaying), things are "not good."
> > >
> > > Any protocol which requires RSP/RP attention must be punted to the host
> > > processor. This includes stuff like certain layer-2 ethertype
> > > broadcasts, ARP, BFD, OSPF Hellos, certain other multicast, DHCP, and
> > > CDP, in addition to packets directly addressed to the routers interfaces
> > > or control plane. If cef is disabled entirely on your box, then this
> > > counter will be including buffered packets about to be switched, which
> > > it normally (when cef is running) would not.
> > >
> > > You can get a feel for what protocol 'groups' are listening (read:
> > > configuring cef to punt packets up to the host rsp/rp) on an interface
> > > by looking at the routers hardware & software IDB allocation. To see it,
> > > use:
> > >
> > > #sh idb
> > >
> > > [snip]
> > >
> > > HWIDB#1   Serial1/0/0:1 (HW IFINDEX(10001), HW SB CDP(4), Serial(3), MAC
> > > ADDR(1))
> > > HWIDB#2   Serial1/0/0:2 (HW IFINDEX(10001), HW SB CDP(4), Serial(3), MAC
> > > ADDR(1))
> > > HWIDB#3   Serial1/0/0:3 (HW IFINDEX(10001), HW SB CDP(4), Serial(3), MAC
> > > ADDR(1))
> > > [snip]
> > >
> > > SWIDB#1   Serial1/0/0:1 (SW CDP(4), NetBIOS(2), DSS(3), KEEPALIVE(1))
> > > SWIDB#2   Serial1/0/0:2 (SW CDP(4), NetBIOS(2), DSS(3), KEEPALIVE(1))
> > > SWIDB#3   Serial1/0/0:3 (SW CDP(4), NetBIOS(2), DSS(3), KEEPALIVE(1))
> > > [snip]
> > >
> > > Good luck,
> > >
> > > -Tk
> > >
> >
> >
> >
> > --
> > Omar E.P.T
> > -----------------
> > Certified Networking Professionals make better Connections!
> >
> > http://omarept.blogspot.com/
> >
> >   Usysnet Corp
> > Open Source Solutions
> > www.usysnet.com.pe
> > _______________________________________________
> > 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/
>
>
>------------------------------
>
>Message: 3
>Date: Thu, 28 Dec 2006 09:21:11 -0800 (PST)
>From: Sukumar Subburayan <sukumars at cisco.com>
>Subject: Re: [c-nsp] upgrade firmware on Cat6k / CatOS modules?
>To: Gert Doering <gert at greenie.muc.de>
>Cc: cisco-nsp at puck.nether.net
>Message-ID: <Pine.GSO.4.64.0612280916030.19789 at sj-cse-392.cisco.com>
>Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
>
>comments inline..
>
>sukumar
>
>
>
>
>On Thu, 28 Dec 2006, Gert Doering wrote:
>
> > Hi,
> >
> > a colleague ran across an interesting problem today.  We were trying to
> > build a 2x100 Mbit etherchannel between a Cat6k (Sup1a, CatOS 7.6(14))
> > and a Cat2950-24 (various recent IOS versions), and the channel refused
> > to come up - always one port on the Cat6k side went into "errdisable"
> > (the first port to be enabled worked, the second port went to errdisable,
> > but it didn't matter *which* port was enabled first, and which port
> > second).
> >
> > Today, we tried ports on different modules, and interesting enough,
> > as soon as module 7 isn't involved, the channeling "just works".
> >
> > This is what we have:
> >
> > 3   48   WS-X6348-RJ-45      SAD04250LZ3 Hw : 1.1
> >                                         Fw : 5.3(1)
> >                                         Sw : 7.6(14)
> > 5   48   WS-X6248-RJ-45      SAD04150EK1 Hw : 1.2
> >                                         Fw : 5.1(1)CSX
> >                                         Sw : 7.6(14)
> > 7   48   WS-X6248-RJ-45      SAD035101TR Hw : 1.1
> >                                         Fw : 4.2(0.24)VAI78
> >                                         Sw : 7.6(14)
> >
> > The combination 5/31+7/31 does not work (second port to come up goes
> > to errdisable).
> >
> > The combinations 5/31+5/16 and 5/31+3/34 both work "as designed" - come
> > up as channel + trunk, and do what we want them to.
> >
> > Now - the only difference we can see is "Fw" on the 6248 in Slot 7.  Which
> > might be relevant or not.
> >
> > --> questions to the audience:
> >
> >  - is "Fw:" relevant in any way after the switch has booted (available
> >    documentation seems to suggest that this is only boot code)
> >
>
>No, the 'Fw:' is not relevant after the switch is booted.
>
> >  - *if* the "Fw:" is relevant: is there a way to upgrade it?
> >
>
>also, the 'Fw:' for the linecard cannot be upgraded. The linecard SW 'Sw:'
>is bunded with CatOS and that is the one which can be upgraded.
>
> > At this point we're not actually trying to get the channel on 5/31+7/31
> > to work (we're happy with 5/31+3/34), we're just trying to understand
> > the issues involved, and what might cause a difference between
> > modules 5 and 7.
> >
>
>OK, since you are not trying to get channeling work between 5/31 & 7/31,
>this may not interest you. But, if you want to go further here are some
>suggestions.
>
>Was the errdisable due to channel misconfig? Was there any other syslogs
>printed? If you just had allowed vlan list to say vlan 1-10 (instead of
>the entire 1K vlan) on both sides and then try channeling does it work?
>
>To me the problem seem to be some parameters between slot 7 and other slot
>ports din't agree.
>
>If the problem can be recreated we can look at 'show agc mod/port..' for
>both the ports and see what the etherchannel internal port datastructure
>is.
>
> > For documentation, in case someone wants to ask for it: both sides of the
> > channel have been set to "unconditionally on" (set port channel ... on,
> > set trunk ... on dot1q), and VTP is not involved (both switches set to
> > VTP transparent, with different VTP domains).
> >
> > gert
> > --
> > USENET is *not* the non-clickable part of WWW!
> > 
> //www.muc.de/~gert/
> > Gert Doering - Munich, 
> Germany                             gert at greenie.muc.de
> > fax: 
> +49-89-35655025                        gert at net.informatik.tu-muenchen.de
> > _______________________________________________
> > 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/
> >
>
>
>------------------------------
>
>Message: 4
>Date: Thu, 28 Dec 2006 13:13:56 -0500
>From: "Christian Koch" <ckoch at globix.com>
>Subject: [c-nsp] NAT Translation ques..
>To: <cisco-nsp at puck.nether.net>
>Message-ID:
> 
><6F5C7CC2952F3241BFFF2859848C52BF028D59F7 at nyc-ex2000.internal.globix.com.bkp>
>
>Content-Type: text/plain;       charset="us-ascii"
>
>Can someone explain to me what causes NAT Misses? There seem to be an
>awful lot and they are incrementing
>
>thanks
>
>#sh ip nat statistics
>Total active translations: 28 (13 static, 15 dynamic; 15 extended)
>Outside interfaces:
>   Serial0/0.5, Serial0/0.7
>Inside interfaces:
>   FastEthernet0/0
>Hits: 4148  Misses: 67
>Expired translations: 0
>Dynamic mappings:
>-- Inside Source
>[Id: 1] access-list 1 pool remote refcount 15
>  pool remote: netmask 255.255.255.240
>         start 10.10.10.91 end 10.10.10.91
>         type generic, total addresses 1, allocated 0 (0%), misses 0
>#
>
>
>------------------------------
>
>Message: 5
>Date: Thu, 28 Dec 2006 12:28:55 -0600
>From: "Church, Chuck" <cchurch at multimax.com>
>Subject: Re: [c-nsp] NAT Translation ques..
>To: "Christian Koch" <ckoch at globix.com>, <cisco-nsp at puck.nether.net>
>Message-ID:
>         <516F24A4808E3A449402F0B5CA9E762009142B at MSPEXBE02.wamnet.inc>
>Content-Type: text/plain;       charset="us-ascii"
>
>NAT misses are normal.  A packet that needs to be translated, and for
>which a current translation doesn't exist, will be considered a miss,
>and a translation is created.  If your misses were higher or close to
>your number of hits, I'd be suspicious of a worm or something like that.
>But your ratio looks pretty normal.
>
>
>Chuck Church
>Network Engineer
>CCIE #8776, MCNE, MCSE
>Multimax, Inc.
>Enterprise Network Engineering
>Home Office - 864-335-9473
>Cell - 864-266-3978
>cchurch at multimax.com
>
>-----Original Message-----
>From: cisco-nsp-bounces at puck.nether.net
>[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Christian Koch
>Sent: Thursday, December 28, 2006 1:14 PM
>To: cisco-nsp at puck.nether.net
>Subject: [c-nsp] NAT Translation ques..
>
>Can someone explain to me what causes NAT Misses? There seem to be an
>awful lot and they are incrementing
>
>thanks
>
>#sh ip nat statistics
>Total active translations: 28 (13 static, 15 dynamic; 15 extended)
>Outside interfaces:
>   Serial0/0.5, Serial0/0.7
>Inside interfaces:
>   FastEthernet0/0
>Hits: 4148  Misses: 67
>Expired translations: 0
>Dynamic mappings:
>-- Inside Source
>[Id: 1] access-list 1 pool remote refcount 15
>  pool remote: netmask 255.255.255.240
>         start 10.10.10.91 end 10.10.10.91
>         type generic, total addresses 1, allocated 0 (0%), misses 0
>#
>_______________________________________________
>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/
>
>
>
>------------------------------
>
>Message: 6
>Date: Thu, 28 Dec 2006 13:36:24 -0500
>From: "Christian Koch" <ckoch at globix.com>
>Subject: Re: [c-nsp] NAT Translation ques..
>To: "Church, Chuck" <cchurch at multimax.com>,
>         <cisco-nsp at puck.nether.net>
>Message-ID:
> 
><6F5C7CC2952F3241BFFF2859848C52BF028D59F8 at nyc-ex2000.internal.globix.com.bkp>
>
>Content-Type: text/plain;       charset="us-ascii"
>
>  Chuck,
>
>Thanks for the explanation! That helped :)
>
>
>
>|-----Original Message-----
>|From: Church, Chuck [mailto:cchurch at multimax.com]
>|Sent: Thursday, December 28, 2006 1:29 PM
>|To: Christian Koch; cisco-nsp at puck.nether.net
>|Subject: RE: [c-nsp] NAT Translation ques..
>|
>|NAT misses are normal.  A packet that needs to be translated,
>|and for which a current translation doesn't exist, will be
>|considered a miss, and a translation is created.  If your
>|misses were higher or close to your number of hits, I'd be
>|suspicious of a worm or something like that.
>|But your ratio looks pretty normal.
>|
>|
>|Chuck Church
>|Network Engineer
>|CCIE #8776, MCNE, MCSE
>|Multimax, Inc.
>|Enterprise Network Engineering
>|Home Office - 864-335-9473
>|Cell - 864-266-3978
>|cchurch at multimax.com
>|
>|-----Original Message-----
>|From: cisco-nsp-bounces at puck.nether.net
>|[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Christian Koch
>|Sent: Thursday, December 28, 2006 1:14 PM
>|To: cisco-nsp at puck.nether.net
>|Subject: [c-nsp] NAT Translation ques..
>|
>|Can someone explain to me what causes NAT Misses? There seem
>|to be an awful lot and they are incrementing
>|
>|thanks
>|
>|#sh ip nat statistics
>|Total active translations: 28 (13 static, 15 dynamic; 15
>|extended) Outside interfaces:
>|  Serial0/0.5, Serial0/0.7
>|Inside interfaces:
>|  FastEthernet0/0
>|Hits: 4148  Misses: 67
>|Expired translations: 0
>|Dynamic mappings:
>|-- Inside Source
>|[Id: 1] access-list 1 pool remote refcount 15  pool remote:
>|netmask 255.255.255.240
>|        start 10.10.10.91 end 10.10.10.91
>|        type generic, total addresses 1, allocated 0 (0%),
>|misses 0 # _______________________________________________
>|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/
>|
>|
>
>
>
>------------------------------
>
>Message: 7
>Date: Thu, 28 Dec 2006 20:52:37 +0100
>From: Eusebio L?pez <eusebio at palmanet.net>
>Subject: Re: [c-nsp] Etherchannel
>To: "Tassos Chatzithomaoglou" <achatz at forthnet.gr>
>Cc: cisco-nsp at puck.nether.net
>Message-ID:
>         <DD3D311D04A60048A1A4A57A745F550F0C0561 at srburns.palmanet.pns>
>Content-Type: text/plain;       charset="utf-8"
>
>I have formed it thus, but it does not do load-balancing. The single 
>traffic goes by a way
>
>         -----Mensaje original-----
>         De: Tassos Chatzithomaoglou [mailto:achatz at forthnet.gr]
>         Enviado el: jue 28/12/2006 13:12
>         Para: Eusebio L??pez
>         CC: cisco-nsp at puck.nether.net
>         Asunto: Re: [c-nsp] Etherchannel
>
>
>
>         I guess you could try the following:
>
>         2950
>         ----
>         int x/x
>         channel-group x mode on
>
>         3500XL
>         ------
>         int x/x
>         port group x
>
>
>         Just make sure you have all ports shut before assigning 
> them to groups.
>
>         --
>         Tassos
>
>         Eusebio Lo'pez wrote on 28/12/2006 1:49 ????:
>         > I have formed Etherchannel configuration between two 
> Catalyst 2950 and work perfectly. The problem is that I want to use 
> a C3524XL with ios c3500xl-c3h2s-mz.120-5.WC9.bin and I do not find 
> command channel-group. I will be able to use the command port group?
>
>         >
>         > Cheers
>         >
>         > _______________________________________________
>         > 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 49, Issue 103
>******************************************



More information about the cisco-nsp mailing list