SG200-18 LACP issue

I have a pfSense based router connected to a SG200-08 switch using round robin load balancing on the switch.
From the SG200-08, if I plug in a Macbook Pro with 2 thunderbolt GigE ethernet dongles, I can successfully get transfer speeds through the router at 1300Mbps.
If I connect an SG200-18 with two Cat6 cables to the SG200-08 and setup a dynamic LAGG on the SG200-08 with a IP/MAC based (LACP enabled) LAGG on the SG200-18 I am maxing out at 940Mbps using the Macbook Pro as a client.
Why is it that I seem to be limited when using the SG200-18.
FWIW, the SG200-18 has firmware version 1.3.5.58, the SG200-08 has 1.0.6.2
Network Overview
2xFTTH 1Gbps links --> pfSense --(load-balance RR)--->SG200-08--(dynamic LAGG)-->SG200-18---LACP LAGG--->Macbook Pro (dual ethernet dongles)

round robin will allow you to use multiple interfaces/switch ports in the same conversation (tcp session).  because of this you can achieve higher transfer speeds.
lacp does not allow you to use multiple interfaces/switch port for the same conversation.  because of this, you are limited to the max throughput of the interface chosen for the session.
it is really the differences in the bonding/port-channeling methods.  i think round-robin can result in high retransmission rates.

Similar Messages

  • SG300-28 SRW2024-K9-EU LACP Issue,

    HI,
    I am facing issue with relating to Link Aggregation (LACP), here with i have Discuss the details below,
    I am tring to make the Two etherchannel setup with using Two SG300-28 Switches connected eachother, (As a stated given Diagram)
    For ex, (Vlan-17,20,21,24,30) pass through One etherchannel
    For ex, (Vlan-201,202,203 pass through Second etherchannel,
    LACP Also i have kept enable for both the etherchannel,
    After creating two etherchannel it is showing one etherchannel is ACTIVE and other one is showing STANDBY,
    if i want to make both the etherchannel should work as ACTIVE than is it possible ?
    if it is possible than please help me out for the configuration and if it is not possible than please guide me why it is made it like ?

    Hi Robert,
    You are right i can get that same features as you have stated in the post, but my problem is relating to LACP,
    not STP,
    See in my given diagram i have purposely kept the switch--1 as Root Bridge for all Vlans And Other it means Switch--2 is a Backup Root Bridge for All the Vlans, And also the Sw-2 Both the Ports i have kept as STP Block Port,  as per the requiremnt i have done the configuration,
    So now there is no any more problem with STP right, than also why its not creating Etherchannel as ACTIVE / ACTIVE Mode, and why it is not working as per the Design. if you have any solutions guide or examples guide for the LACP Configuration, than please share it,
    Thanks for your Input,

  • SG200 SFP GBIC Issue

    Hi All,
    I am facing a weird case of SG200. I had a 3Com5500 switch with Fibre module GBIC connecting to the SG200 (Cisco GBIC). The particular port is untagged to vlan 2 with DHCP. By this way, the SG200 supposed to obtain an IP if it is logically communicating with the 3Com5500 and the PC connecting to the SG200 should get an IP too.
    However, the SG200 seems like no obtaining an IP (the System LED keep blinking) and the PC connected to it does not get an IP too. The port LED of both side is blinking, means that they are physically connected.
    I had
    I had tried to connect the fiber cable with the same GBIC to another unmanaged switch (Cisco SG92) and it is working fine (PC connected to it can get an IP too) .
    I tried to connect the 3Com5500 to the SG200 with UTP and it is working fine too.
    Does anyone meet this issue before? Please advise. Thanks!!

    This is very unusual.
    I have a very strong feeling the issue is related to the modem. I can see that, according to the subnet mask, you will have many more addresses, but it appears to me you are getting public ip addresses on your entire network and that is very atypical.
    Now, the second address you are getting is also a public IP address, and I believe that the modem gave it to you also, maybe because you ran out of your allotted addresses on the first subnet.
    One again, all of this is speculation but I think that I may be right.
    In regards to the switch, two things:
    1- I really don't think this will fix your issue as I'm convinced the problem is not on the switch.
    2- It is still a good idea to upgrade the firmware to the latest to make it more reliable and get new features.
    With that being said, you can go to 1.3.5.58 and upgrade both firmware and boot code and then go to 1.4.0.8 and upgrade just firmware.

  • Nexus 2k to HP Server LACP issue

    Hi,
    We are having problems connecting our Nexus 2k to HP server ports in LACP mode (channel-group mode active).
    The below is snippet from logs, before the port goes into suspended mode.
    2013 Jun  7 17:14:21 PBR-core-1-PoC %LACP-FEX104-3-SYN_COLL_DIS_EN: WARNING: Potential Interop issue on  [Ethernet104/1/7(0x1f670180)]: SYNC, COLLECT and DISTRIBUTE flags enabled too early by partner
    ERROR: Cannot set/reset lacp suspend-individual for port-channel305 that is admin up
    PBR-core-1-PoC(config-if)# 2013 Jun  7 17:14:41 PBR-core-1-PoC %ETH_PORT_CHANNEL-5-PORT_SUSPENDED: Ethernet104/1/7: Ethernet104/1/7 is suspended
    2013 Jun  7 17:14:40 PBR-core-1-PoC %LACP-FEX104-5-LACP_SUSPEND_INDIVIDUAL: LACP port Ethernet104/1/7(0x1f670180) of port-channel port-channel305(0x16000130) not receiving any LACP BPDUs  suspending (individual) port
    Cisco: Nexus 7000 6.1.4 with N2K-C2248TP-1GE 6.1.4
    ->
    HP Ethernet 1Gb 4-port 331FLR Adapter running Windows 2008 R2 sp1, Broadcom  Driver Version : 15.4.0.19
    Has anyone had success with LACP and this setup?
    Cheers,
    J-Dogg
    HP Ethernet 1Gb 4-port 331FLR Adapter

    Hi,
    I'm not sure if you already found this, but the first error is documented, for the Nexus 5000 series at least in the System Messages and Recovery Procedures for the Cisco Nexus 5000 Family:
    Error Message: LACP-3-SYN_COLL_DIS_EN: [chars] : SYNC, COLLECT and DISTRIBUTE flags enabled too early by partner
    Explanation: Potential interop issue. Partner system seems to have enabled sync as well collecting or distributing flags too early even before actor has selected an aggregator
    Recommended Action: No action is required.
    I just love the Recommended Action
    The message is indicating that the LACPDU from the server has the Synchronise, Collecting and Distributing flags all set on the first LACPDU it receives. When the link is first established the LACPDU is only supposed to have the Synchronise flag set, with the Collecting and Distributing flags set once the switch and host are sync'd. There's a prety good diagram of this at Networking Bodges in the Bringing Links Up section.
    On the basis of this it would seem this is possibly a bug in the Broadcom driver. I see on the Broadcom website that version 15.6.0.10 of the driver is available. Are you able to try that driver on this server?
    Regards

  • LACP ISSUE ON NEXUS 5548

    HI,
    i have some servers connected to these ports i see port-channel is up....can any one tell me what exactly "[LACP_ST_PORT_MEMBER_COLLECTING_AND_DISTRIBUTING_ENABLED] "  means ????
    FSM:<Ethernet106/1/13> Transition at 555079 usecs after Fri Jun 20 20:15:20 2014
        Previous state: [LACP_ST_WAIT_FOR_HW_TO_PROGRAM_TRANSMIT_PATH]
        Triggered event: [LACP_EV_PORT_HW_PATH_ENABLED]
        Next state: [LACP_ST_PORT_MEMBER_COLLECTING_AND_DISTRIBUTING_ENABLED]
        Curr state: [LACP_ST_PORT_MEMBER_COLLECTING_AND_DISTRIBUTING_ENABLED]
    FSM:<Ethernet106/1/14> Transition at 558271 usecs after Fri Jun 20 20:15:20 2014
        Previous state: [LACP_ST_WAIT_FOR_HW_TO_PROGRAM_TRANSMIT_PATH]
        Triggered event: [LACP_EV_PORT_HW_PATH_ENABLED]
        Next state: [LACP_ST_PORT_MEMBER_COLLECTING_AND_DISTRIBUTING_ENABLED]
        Curr state: [LACP_ST_PORT_MEMBER_COLLECTING_AND_DISTRIBUTING_ENABLED]
    FSM:<Ethernet106/1/15> Transition at 655069 usecs after Fri Jun 20 20:15:20 2014
        Previous state: [LACP_ST_WAIT_FOR_HW_TO_PROGRAM_TRANSMIT_PATH]
        Triggered event: [LACP_EV_PORT_HW_PATH_ENABLED]
        Next state: [LACP_ST_PORT_MEMBER_COLLECTING_AND_DISTRIBUTING_ENABLED]
       Curr state: [LACP_ST_PORT_MEMBER_COLLECTING_AND_DISTRIBUTING_ENABLED]
    FSM:<Ethernet106/1/16> Transition at 658790 usecs after Fri Jun 20 20:15:20 2014
        Previous state: [LACP_ST_WAIT_FOR_HW_TO_PROGRAM_TRANSMIT_PATH]
        Triggered event: [LACP_EV_PORT_HW_PATH_ENABLED]
        Next state: [LACP_ST_PORT_MEMBER_COLLECTING_AND_DISTRIBUTING_ENABLED]
        Curr state: [LACP_ST_PORT_MEMBER_COLLECTING_AND_DISTRIBUTING_ENABLED]

    Hi,
    As I saw it before, these are just LACP status transition to Curr state: "LACP_ST_PORT_MEMBER_COLLECTING_AND_DISTRIBUTING_ENABLED" which means that LACP is ok. :)
    When you see any other output from "sh lacp internal event-history interface e1/x " command, better check if this interface  or LACP is flapping .
    HTH
    Jay Ocampo

  • Smart swith SG200-08 - Language issue

    Hi,
    After upgarding my switch with the french package language (firmware V1.0.1.0), impossible to save a configuration modification. Error message. To save go back to the native language.
    Someone can confirm ?
    Patrick

    Patrick,
    Please call into SBSC @ 1-866-606-1866 and open a support case, this way it can be documented and lab for possible bug.
    Thanks,
    Jasbryan

  • Disruptive ISSU 6.1.4a- 6.2.8 on Nexus 7010 sup1 because of LACP timers.

    Hi all.
    The problem.
    Today I updated my Nexus 7010 sup1 from 6.1.4a to 6.2.8.
    I want did it in ISSU mode, but after impact check I got this:
    Compatibility check is done:
    Module  bootable          Impact  Install-type  Reason
         1       yes  non-disruptive       rolling  
         2       yes  non-disruptive       rolling  
         3       yes  non-disruptive       rolling  
         4       yes  non-disruptive       rolling  
         5       yes      disruptive         reset  Some LACP ports not in steady state or operating in 'rate fast' mode.
         6       yes      disruptive         reset  Some LACP ports not in steady state or operating in 'rate fast' mode.
         7       yes  non-disruptive       rolling  
         8       yes  non-disruptive       rolling  
         9       yes  non-disruptive       rolling  
        10       yes  non-disruptive       rolling  
    Additional info for this installation:
    Service "lacp" in vdc 1: LACP: Upgrade will be disruptive as 6 switch ports and 0 fex ports are not upgrade ready!!
          Issue the "show lacp issu-impact" cli for more details.
    (modified the impact to <Hitful>  for module <6>)
    Do you want to continue with the installation (y/n)?  [n] y
    I went on with yes and update script reboot both sups after updated all modules.
    It was quite a surprise for me (yes I know I must see word "disruptive" opposite my sups 5 and 6). Because I already had done two ISSU updates on two nexuses (from 5.1.* ->5.2.7 and 5.2.7 -> 6.1.4a) and didn`t have any trouble with LACP timers. Is it a new feature of the 6.* train?
    I have another Nexus that I want to update. And it also has same problem with LACP timers.
    show install all impact give me the same disruptive result because of LACP.
    Can I somehow suppress such ISSU behavior? In case of LACP. I don`t have vPC, just ordinal PC.
    It is a way better if some LACP interfaces flap in process, than an almost 14 minutes of all 7010 chassis reboot that I had.
    Although problem with LACP timers is that they must be the same on the switch side and on the other side. And in case of switches, linux boxes or HP VCs changing LACP timers isn`t a big problem. IT is a biggg problem in case of the Windows Server.
    sh lacp interface ethernet 8/13
    Interface Ethernet8/13 is up
      Channel group is 13 port channel is Po13
    Local Port: Eth8/13   MAC Address= 40-55-39-23-1e-c1
      System Identifier=0x8000,  Port Identifier=0x8000,0x80d
      Operational key=12
      LACP_Activity=active
      LACP_Timeout=Long Timeout (30s)
    Neighbor: 0x1
      MAC Address= ac-16-2d-a4-f2-54
      System Identifier=0xffff,  Port Identifier=0xff,0x1
      Operational key=17
      LACP_Activity=active
      LACP_Timeout=short Timeout (1s)
    They must be the same and equal 30s for successful ISSU

    You probably need to dig a little deeper to get a definitive answer (sup1 or 2, type of cards, etc..) but here is a diagram in the release notes for 6.1 found here:
    http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/nx-os/release/notes/61_nx-os_release_note.html
    If this posts answers your question or is helpful, please consider rating it and/or marking as answered.

  • SG300-10P LACP and PoE

    Hi
    I am using SG300-10 and connected it to two SG200 with LACP and PoE
    When I tried to use ssh client to check poe status via cli, the switch suddenly rebooted.
    After this, the poe is dead.
    I reset the switch, reconfigured the settings but ..
    as soon as I set GE1+GE2 to a LACP group,
    the SG200-8 connected to GE1+GE2 is down, lost power
    when I remove the GE1+GE2 from LACP group, the poe is back ...
    same to any other port.
    only ports that not in LACP listed in "Port Management" "PoE" "Settings"
    is the hardware damanged? I am using the lasted 1.3.0.62 firmware.
    The physical connected is:
    L3 Mode
    GE1+GE2 = LACP <---> SG200-8 nr1
    GE3+GE4 = LACP <---> SG200-8 nr2
    GE5 <---> my pc
    Thanks for any hint/help!

    Thanks for the advice.
    I came home today and found out a power outage happened and somehow the SG300-10P stopped working partly, any device not directly connected to it can't ping the switch or communicated to it or its conncted devices. (even after reboot)
    So I decieded to reset it to the factory default and manually reapply all the setting from my memory, because last few times I tried to use backuped config file, it ended badly. ( the firmware is already updated to latest)
    After that, I followed your advice and set GE1 PoE active and GE2 PoE off, and so on, now both SG200-8 and SLM2008 are getting power from port GE1 and GE3.
    Still, as soon as I add a port to a LACP group, it will disappear from "
    Port Management", "PoE", "Settings" page ..., is that a normal behavior? or is it a problem on SG200 or/and SLM2008?

  • Issue with LACP on SRW2008 with W2k8

    Hello,
    I'm trying to configure the LACP for W2k8 and I have strange thing :
    My network is :
    1 SRW2008 with
    a Synology NAS connected with LACP
    my PC running under W2k8 with LACP
    1 another PC with single
    1 Router running with DD-WRT fw , used for DHCP , WIFI  and for the internet connexion
    I have a Dual NIC Intel  and the LACP is active on my PC w2k8 , I can see my network connected at 2 Gb/s. I can surf ping the swr2008 , my router and my printer connect by wifi. I cannot ping the other PC and my NAS connected to the srw2008.
    when I disconnect 1 cable of my LACP of my PC I can ping everything
    if I configure w2k8 not with lacp but with ALB I can ping everything
    my question is :
    How to configure LACP 802.3ad on w2k8 and have the ping working to the other system connected to the srw2008 ?
    Thanks a lot
    Emmanuel

    Steve,
    Are you having an issue with incoming or outgoing mail?
    If the issue is with outgoing email this article may be helpful:
    http://docs.info.apple.com/article.html?artnum=305634
    If you are using an IMAP server provided by your employer, you may not be able to access the server without VPN.
    Hope this helps,
    Nathan C.

  • Intel Server NIC I350 LACP IEEE802.3ad teaming issue

    Hello Community
    I face an issue which i cannot resolve.
    I have:
    Intel Server System R1208GL4DS with buildin I350 4 ports inet adapter
    OS: Windows Server 2008 R2
    NIC drivers ver 18.4 (PRO set with ANS)
    Data Center provides ieee802.3ad dynamic aggregation teaming connection, It uses 2 ports on my server (0 and 3)
    DC uses Cisco Nexus switches
    SpanningTreeProtocol is ON and cannot be switched off by DC.
    Problem:
    One of the adapters suddenly goes on standby state and doesnot pass traffic.
    As the result the whole connectivity to server and to services I use stuck at that moment.
    There is only one way to resolve is to restart server or restart whole team by changing the team properties.
    Nic properties:
    flow control off
    ofloads off
    rss off
    Team:
    I have tried to change everything playing with any property within nic or team. No luck.
    Some information from DC support of the swith config:
    # sh interface po1113 switchport
    Name: port-channel11
    13
      Switchport: Enabled
      Switchport Monitor: Not enabled
      Operational Mode: trunk
      Access Mode VLAN: 1 (default)
      Trunking Native Mode VLAN: 1 (default)
      Trunking VLANs Allowed: 300,390,398-399
      Voice VLAN: none
      Extended Trust State : not trusted [COS = 0]
      Administrative private-vlan primary host-association: none
      Administrative private-vlan secondary host-association: none
      Administrative private-vlan primary mapping: none
      Administrative private-vlan secondary mapping: none
      Administrative private-vlan trunk native VLAN: 1
      Administrative private-vlan trunk encapsulation: dot1q
      Administrative private-vlan trunk normal VLANs: none
      Administrative private-vlan trunk private VLANs: none
      Operational private-vlan: none
      Unknown unicast blocked: disabled
      Unknown multicast blocked: disabled
    Please advise as I'm almost stuck.
    Thank you.

    May be problem on Cisco side, Cisco is very clever, could assessed network traffic as a problem and close the port. When OS is running, then NIC Teaming working fine, but when you boot up server, "BIOS not running with NIC Teaming", in this moment
    may occur problem on Cisco side.
    I recommend, if you use Cisco, configure NIC Teaming in LACP mode and configure your two ports on Cisco to LACP, it's better way.
    Regards,
    thennet
    Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable. This helps the community, keeps the forums tidy, and recognises useful contributions. Thank you!

  • SG200-26P and LACP

    Hi,
    I have two NAS. Each one from a different manufacturer, QNAP and Synology.
    The two NAS support LACP IEEE802.3ad but in this way QNAP loses 40% of the packets and Synology not work.
    With a Cisco Calatyst 3750 both NAS I work well. Do I have to do something in the SG200 to work?
    Thank you.

    Hi Tom,
    I use the mode   IEEE 802.3ad Dynamic Link Aggregation on the Synolgy and QNAP.
    Maybe I should use another way?
    Thank´s

  • SG200-50 and LACP

    I am trying to setup up an LAG with LACP between the switch and a Synology DS1511+. Every time I enable LACP on the LAG I cannot get the ports to become Active Members.
    Any help would be much appreciated!
    Thank you!

    Hi,
    I checked out the synology manual on their implemenation of Link Agg with LACP and it is very easy to configure, however I have no idea what they are really doing.  It's just click and off she goes. When the ports aren't active in LINK AGG, to me it means that there is a issue maybe with speed or if the remote device is actually running LinkAgg with LACP
    Synology  mention the following taken from their DS1511+ user guide, and I quote.
    IEEE 802.3ad Dynamic Link Aggregation: IEEE 802.3ad is the standard for most Link Aggregation implementations. A switch with 802.3ad support is required to use in this mode.
    Network Fault Tolerance only: If the LAN 1 port becomes unavailable, the system will use LAN 2 to provide service. You can select this option if your switch does not support IEEE 802.3ad.
    I cannot answer why the synology unit is having issues with our standards based LINK Aggregation with LACP.
    Therefore I will put the case for the use of using the synology Fault tolerant option.
    The chart below was taken from a wonderful review from smallnetbuilder showing the throughput stats
    under their testing, in MegaBits per second  (MB/s)
    The DS1511+ seems almost identical to the DS2411+ that was tested, but even the good folk at
    small netbuilder  see the following throughput under RAID5 conditions.
    click on the picture below;
    http://www.smallnetbuilder.com/nas/nas-reviews/31616-synology-ds2411-reviewed
    You have the option to modify my switches LinkAgg LACP parameters if you wish to try to get it working with the synology box.
    Or take synology's advice and run the NAS in fault tolerant mode, if you are having a issue with LACP.
    If the primary  link was to fail,  the backup link on the synoptic box should become active, without the need for trying to mate synoptic LinkAgg LACP and Cisco LinkAgg with LACP.
    regards Dave

  • SG200-50P and Cisco Router Issue

    I have just recently replaced a WS-CE500-24LC switch with a SG200-50P.  I have plugged in a Cisco 1760 router with a fast ethernet into the switch.  On the console of the router I now see these messages:
    Jun 30 16:17:30.492: %PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver
    problem?
    cisco1760#
    Jun 30 16:18:30.495: %PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver
    problem?
    cisco1760#
    Jun 30 16:19:30.498: %PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver
    problem?
    cisco1760#
    Jun 30 16:20:30.501: %PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver
    problem?
    cisco1760#
    Jun 30 16:21:30.504: %PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver
    problem?
    cisco1760#
    Jun 30 16:22:30.514: %PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver
    problem?
    cisco1760#
    Jun 30 16:23:30.517: %PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver
    problem?
    cisco1760#
    Jun 30 16:24:30.520: %PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver
    problem?
    cisco1760#
    Jun 30 16:25:30.523: %PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver
    problem?
    cisco1760#
    Jun 30 16:26:30.526: %PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver
    problem?
    cisco1760#
    Jun 30 16:27:30.528: %PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver
    problem?
    cisco1760#
    Jun 30 16:28:30.531: %PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver
    problem?
    cisco1760#
    Jun 30 16:29:30.534: %PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver
    problem?
    cisco1760#
    Jun 30 16:30:30.537: %PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver
    problem?
    cisco1760#
    Jun 30 16:31:30.540: %PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver
    problem?
    cisco1760#
    Jun 30 16:32:30.543: %PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver
    problem?
    cisco1760#
    Jun 30 16:33:30.545: %PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver
    What does this mean and how do I fix the issue.  As far as I am aware both ends of the link are set to autonegotiate the speed and duplex.
    Thanks for helping.

    Dave,
    1.  Thanks for explaning what the error message means.  I never saw this message when the router was plugged into the WS-CE500-24LC switch.
    2.  I did upgrade to the new firmware, even before I had connected the router to the switch.  I also replaced the cable.  It did not fix the issue.
    3a.  Other than the log messages every minute, I do see any impact to the network that I am aware of.
    Interface counts:
    cisco1760#sh int fastEthernet 0/0
    FastEthernet0/0 is up, line protocol is up
      Hardware is PQUICC_FEC, address is 000c.ce05.d68c (bia 000c.ce05.d68c)
      Description: "Primary LAN Segment"
      MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
         reliability 255/255, txload 2/255, rxload 2/255
      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 never
      Input queue: 0/75/948/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: fifo
      Output queue: 0/40 (size/max)
      5 minute input rate 895000 bits/sec, 245 packets/sec
      5 minute output rate 978000 bits/sec, 293 packets/sec
         199852941 packets input, 838336294 bytes
         Received 1945096 broadcasts, 0 runts, 0 giants, 0 throttles
         482 input errors, 0 CRC, 0 frame, 482 overrun, 0 ignored
         0 watchdog
         0 input packets with dribble condition detected
         234783382 packets output, 4015540432 bytes, 9 underruns
         9 output errors, 0 collisions, 13 interface resets
         0 babbles, 0 late collision, 0 deferred
         0 lost carrier, 0 no carrier
         0 output buffer failures, 0 output buffers swapped out
    cisco1760#sh int fastEthernet 0/0
    FastEthernet0/0 is up, line protocol is up
      Hardware is PQUICC_FEC, address is 000c.ce05.d68c (bia 000c.ce05.d68c)
      Description: "Primary LAN Segment"
      MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
         reliability 255/255, txload 2/255, rxload 2/255
      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 never
      Input queue: 0/75/948/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: fifo
      Output queue: 0/40 (size/max)
      5 minute input rate 878000 bits/sec, 238 packets/sec
      5 minute output rate 962000 bits/sec, 286 packets/sec
         199880510 packets input, 851437952 bytes
         Received 1945469 broadcasts, 0 runts, 0 giants, 0 throttles
         482 input errors, 0 CRC, 0 frame, 482 overrun, 0 ignored
         0 watchdog
         0 input packets with dribble condition detected
         234816750 packets output, 4029944015 bytes, 9 underruns
         9 output errors, 0 collisions, 13 interface resets
         0 babbles, 0 late collision, 0 deferred
         0 lost carrier, 0 no carrier
         0 output buffer failures, 0 output buffers swapped out
    cisco1760#
    cisco1760#sh int fastEthernet 0/0
    FastEthernet0/0 is up, line protocol is up
      Hardware is PQUICC_FEC, address is 000c.ce05.d68c (bia 000c.ce05.d68c)
      Description: "Primary LAN Segment"
      MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
         reliability 255/255, txload 2/255, rxload 2/255
      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 never
      Input queue: 0/75/948/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: fifo
      Output queue: 0/40 (size/max)
      5 minute input rate 895000 bits/sec, 245 packets/sec
      5 minute output rate 978000 bits/sec, 293 packets/sec
         199852941 packets input, 838336294 bytes
         Received 1945096 broadcasts, 0 runts, 0 giants, 0 throttles
         482 input errors, 0 CRC, 0 frame, 482 overrun, 0 ignored
         0 watchdog
         0 input packets with dribble condition detected
         234783382 packets output, 4015540432 bytes, 9 underruns
         9 output errors, 0 collisions, 13 interface resets
         0 babbles, 0 late collision, 0 deferred
         0 lost carrier, 0 no carrier
         0 output buffer failures, 0 output buffers swapped out
    A minute later...
    cisco1760#sh int fastEthernet 0/0
    FastEthernet0/0 is up, line protocol is up
      Hardware is PQUICC_FEC, address is 000c.ce05.d68c (bia 000c.ce05.d68c)
      Description: "Primary LAN Segment"
      MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
         reliability 255/255, txload 2/255, rxload 2/255
      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 never
      Input queue: 0/75/948/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: fifo
      Output queue: 0/40 (size/max)
      5 minute input rate 878000 bits/sec, 238 packets/sec
      5 minute output rate 962000 bits/sec, 286 packets/sec
         199880510 packets input, 851437952 bytes
         Received 1945469 broadcasts, 0 runts, 0 giants, 0 throttles
         482 input errors, 0 CRC, 0 frame, 482 overrun, 0 ignored
         0 watchdog
         0 input packets with dribble condition detected
         234816750 packets output, 4029944015 bytes, 9 underruns
         9 output errors, 0 collisions, 13 interface resets
         0 babbles, 0 late collision, 0 deferred
         0 lost carrier, 0 no carrier
         0 output buffer failures, 0 output buffers swapped out
    cisco1760#
    It appears that just the byte and packet counts are increasing.  Nothing shown in the log of the SG200-50P.  Logging level set to informational in RAM.
    I set both side to 10 M / half-duplex and that also did not affect the messages. 
    Do you have any thoughts on the carrier-delay or keepalive settings on the fast ethernet interface of the router?
    Thanks.

  • SG200 Small business switch - vlan issue

    I have the wonderous task of remotely configuring a few SG200 small business switches.
    I need to create a vlan and move a few ports into that vlan, doesn't sound too difficult.
    I have created the vlans but when I go to add the ports into the vlan the only option I seem to have is General?
    If I specify access I can't say what vlan the port should be in?
    What am I doing wrong?
    All ports are currently in VLAN 1 and are in mode trunk
    I have created 2 new vlans and just want to put 4 ports in VLAN 2 and 4 ports in VLAN 4
    Can anyone impart any wisdom?
    Thanks
    Roger

    Hi Roger,
    Did you try this guide?
    http://sbkb.cisco.com/CiscoSB/Loginr.aspx?login=1&pid=2&app=search&vw=1&articleid=80
    Are you configuring it from GUI or CLI ?
    Regards
    Mariusz

  • LACP Detection issue

    Hi All,
    In this scenario, On port channel 10 we executed spanning-tree port type network but on members of same PO10. There is diff command
    spanning-tree port type normal. In our env. it's running fine. But we are running static port-channel not LACP.
    If we run lacp.. Does LACP will throw error in this scenario? Because i read LACP will always match configuration. between two members or interfaces  NOT Between Portchannel and its member. Kindly help here. Does it true?
    interface port-channel10
      description vPC peer-link
      switchport mode trunk
      switchport trunk native vlan 99
      spanning-tree port type network
      vpc peer-link
    interface Ethernet1/31
      switchport mode trunk
      switchport trunk native vlan 99
      spanning-tree port type normal
      channel-group 10
    interface Ethernet1/32
      switchport mode trunk
      switchport trunk native vlan 99
      spanning-tree port type normal
      channel-group 10

    Hi,
    I think, you will see error and LACP will not work in this scenario.
    For VPC peer link, the STP type should be network for all physical links and the Portchannel.
    It is also recommended to use LACP:
    You can only configure these port channels and vPC peer links statically. All ports in the vPC on each of the vPC peer devices must be in the same VDC. You can configure the port channels and vPC peer links either using LACP or no protocol. We recommend that you use LACP with the interfaces in active mode to configure port channels in each vPC, which ensures an optimized, graceful recovery in a port-channel failover scenario and provides configuration checks against configuration mismatches among the port channels themselves.
    http://www.cisco.com/c/en/us/td/docs/switches/datacenter/sw/5_x/nx-os/interfaces/configuration/guide/if_cli/if_vPC.html
    HTH

Maybe you are looking for