Port Channel via SCE8000

Dear community members,
I need to increase the link capacity of 10GE ​​to 20GE between two Cisco7609, so I feel the need to configure port channel between them, my little problem is that I have a SCE 8080 in the middle of both 7600 currently is configured inline.
The SCE has 4 modules 1X10GE-L-V2 (currently in use 2), I was investigated and the truth is that I not found anything concrete about how to configure the SCE to "pass" etherchannel through it, could help me with this ..?
What the SCE needs to support 20GE of traffic? (configuration and software)
I have two 10GE ​​ports available on the SCE
Could you please give me a hand
Thank you very much

Hi there,
I do not think so you need port channel, you can have two links going to two 10G ports on one SCE. The only thinkg you need to take care of is:
http://www.cisco.com/en/US/docs/cable/serv_exch/serv_control/broadband_app/rel38x/sce8000_cli_ref/CLI_Ref_1.html#wp2376046
Also check this one
http://www.cisco.com/en/US/docs/cable/serv_exch/serv_control/broadband_app/rel38x/prod_overview/product_overview.html#wp47099
Thanks,
Minja

Similar Messages

  • 3750-2960 Vlans Issue via Port Channel

    Im trying to get all my vlans to pass thru to my 2960 user level switches, from my 3750 stack.
    Each one of my 2960 stack is connected to my 3750 via port channel. Here is my port setup.
    I have Vlans 1,210,214,216,220,306,406 on my 3750 stack. I cannot see those vlans on my 2960 stack. Why is that? What am I missing from the config?
    Thanks...
    3750 ports:
    interface GigabitEthernet1/0/41
    description Uplink to ETHSW03
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 1,210,214,216,220,306,406
    switchport mode trunk
    snmp trap mac-notification change added
    snmp trap mac-notification change removed
    spanning-tree guard loop
    channel-protocol lacp
    channel-group 7 mode active
    interface GigabitEthernet1/0/42
    description Uplink to ETHSW03
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 1,210,214,216,220,306,406
    switchport mode trunk
    snmp trap mac-notification change added
    snmp trap mac-notification change removed
    spanning-tree guard loop
    channel-protocol lacp
    channel-group 7 mode active
    interface Port-channel7
    description Uplink to ETHSW03
    switchport trunk encapsulation dot1q
    switchport trunk allowed vlan 1,210,214,216,220,306,406
    switchport mode trunk
    snmp trap mac-notification change added
    snmp trap mac-notification change removed
    spanning-tree guard loop
    Here are my 2960 ports setup:
    interface GigabitEthernet1/0/47
    description Uplink to CORE01
    switchport trunk allowed vlan 1,210,214,216,220,306,406
    switchport mode trunk
    snmp trap mac-notification change added
    snmp trap mac-notification change removed
    spanning-tree guard loop
    channel-protocol lacp
    channel-group 1 mode active
    interface GigabitEthernet1/0/48
    description Uplink to CORE01
    switchport trunk allowed vlan 1,210,214,216,220,306,406
    switchport mode trunk
    snmp trap mac-notification change added
    snmp trap mac-notification change removed
    spanning-tree guard loop
    channel-protocol lacp
    channel-group 1 mode active
    interface Port-channel1
    description Uplink to CORE01
    switchport trunk allowed vlan 1,210,214,216,220,306,406
    switchport mode trunk
    snmp trap mac-notification change added
    snmp trap mac-notification change removed
    spanning-tree guard loop

    I have 1 stack of 3750, connected with flex technology.
    I have 3 stacks of 4-2960s, connected with flex technology.
    Then, each 2960 stack is connected to my 3750 stack via port channels (gig ports x2).
    Now, this is a second office site. We are connected to our datacenter via private ethernet line, and thats where most of our vlans and servers reside.
    Output from 3750
    P-DB-CORE01#sh vtp status
    VTP Version capable             : 1 to 3
    VTP version running             : 1
    VTP Domain Name                 : NULL
    VTP Pruning Mode                : Disabled
    VTP Traps Generation            : Disabled
    Device ID                       : 6c41.6a9c.a280
    Configuration last modified by 10.2.20.1 at 3-3-93 23:43:55
    Feature VLAN:
    VTP Operating Mode                : Transparent
    Maximum VLANs supported locally   : 1005
    Number of existing VLANs          : 19
    Configuration Revision            : 0
    MD5 digest                        : 0x3D 0x05 0x4D 0x8C 0x31 0x07 0x34 0xDA
                                        0x2F 0x60 0xE8 0x24 0xA6 0x27 0x59 0x24
    Output from 2960
    P-ETHSW03-20.4#sh vtp status
    VTP Version capable             : 1 to 3
    VTP version running             : 1
    VTP Domain Name                 : NULL
    VTP Pruning Mode                : Disabled
    VTP Traps Generation            : Disabled
    Device ID                       : c07b.bcb2.9a80
    Configuration last modified by 10.2.20.2 at 1-3-14 13:02:15
    Local updater ID is 10.2.20.4 on interface Vl1 (lowest numbered VLAN interface found)
    Feature VLAN:
    VTP Operating Mode                : Server
    Maximum VLANs supported locally   : 255
    Number of existing VLANs          : 7
    Configuration Revision            : 5
    MD5 digest                        : 0x89 0x91 0xBA 0xE3 0x12 0x1B 0xDB 0x1D
                                        0x75 0x43 0x7F 0x8D 0x62 0x5A 0x09 0x70

  • OSPF load balancing across multiple port channels

    I have googled/searched for this everywhere but haven't been able to find a solution. Forgive me if I leave something out but I will try to convey all relevant information. Hopefully someone can provide some insight and many thanks in advance.
    I have three switches (A, B, and C) that are all running OSPF and LACP port channelling among themselves on a production network. Each port channel interface contains two physical interfaces and trunks a single vlan (so a vlan connecting each switch over a port channel). OSPF is running on each vlan interface.
    Switch A - ME3600
    Switch B - 3550
    Switch C - 3560G
    This is just a small part of a much larger topology. This part forms a triangle, if you will, where A is the source and C is the destination. A and C connect directly via a port channel and are OSPF neighbors. A and B connect directly via a port channel and are OSPF neighbors. B and C connect directly via a port channel and are OSPF neighbors. Currently, all traffic from A to C traverses B. I would like to load balance traffic sourced from A with a destination of C on the direct link and on the links through B. If all traffic is passed through B, traffic is evenly split on the two interfaces on the port channel. If all traffic is pushed onto the direct A-C link, traffic is evenly balanced on the two interfaces on that port channel. If OSPF load balancing is configured on the two vlans from A (so A-C and A-B), the traffic is divided to each port channel but only one port on each port channel is utilized while the other one passes nothing. So half of each port channel remains unused. The port channel on B-C continues to load balance, evenly splitting the traffic received from half of the port channel from A.
    A and C port channel load balancing is configured for src-dst-ip. B is a 3550 and does not have this option, so it is set to src-mac.
    Relevant configuration:
    Switch A:
    interface Port-channel1
    description Link to B
     port-type nni
     switchport trunk allowed vlan 11
     switchport mode trunk
    interface Vlan11
     ip address x.x.x.134 255.255.255.254
    interface Port-channel3
    description Link to C
     port-type nni
     switchport trunk allowed vlan 10
     switchport mode trunk
    interface Vlan10
     ip address x.x.x.152 255.255.255.254
    Switch B:
    interface Port-channel1
     description Link to A
     switchport trunk encapsulation dot1q
     switchport trunk allowed vlan 11
     switchport mode trunk
    interface Vlan11
     ip address x.x.x.135 255.255.255.254
    interface Port-channel2
     description Link to C
     switchport trunk encapsulation dot1q
     switchport trunk allowed vlan 12
     switchport mode trunk
    interface Vlan12
     ip address x.x.x.186 255.255.255.254
    Switch C:
    interface Port-channel1
     description Link to B
     switchport trunk encapsulation dot1q
     switchport trunk allowed vlan 12
     switchport mode trunk
    interface Vlan12
     ip address x.x.x.187 255.255.255.254
    interface Port-channel3
     description Link to A
     switchport trunk encapsulation dot1q
     switchport trunk allowed vlan 10
     switchport mode trunk
    interface Vlan10
     ip address x.x.x.153 255.255.255.254

    This is more FYI. 10.82.4.0/24 is a subnet on switch C. The path to it is split across vlans 10 and 11 but once it hits the port channel interfaces only one side of each is chosen. I'd like to avoid creating more vlan interfaces but right now that appears to be the only way to load balance equally across the four interfaces out of switch A.
    ME3600#sh ip route 10.82.4.0
    Routing entry for 10.82.4.0/24
      Known via "ospf 1", distance 110, metric 154, type extern 1
      Last update from x.x.x.153 on Vlan10, 01:20:46 ago
      Routing Descriptor Blocks:
        x.x.x.153, from 10.82.15.1, 01:20:46 ago, via Vlan10
          Route metric is 154, traffic share count is 1
      * x.x.x.135, from 10.82.15.1, 01:20:46 ago, via Vlan11
          Route metric is 154, traffic share count is 1
    ME3600#sh ip cef 10.82.4.0
    10.82.4.0/24
      nexthop x.x.x.135 Vlan11
      nexthop x.x.x.153 Vlan10
    ME3600#sh ip cef 10.82.4.0 internal       
    10.82.4.0/24, epoch 0, RIB[I], refcount 5, per-destination sharing
    sources: RIB 
    ifnums:
    Vlan10(1157): x.x.x.153
    Vlan11(1192): x.x.x.135
    path 093DBC20, path list 0937412C, share 1/1, type attached nexthop, for IPv4
    nexthop x.x.x.135 Vlan11, adjacency IP adj out of Vlan11, addr x.x.x.135 08EE7560
    path 093DC204, path list 0937412C, share 1/1, type attached nexthop, for IPv4
    nexthop x.x.x.153 Vlan10, adjacency IP adj out of Vlan10, addr x.x.x.153 093A4E60
    output chain:
    loadinfo 088225C0, per-session, 2 choices, flags 0003, 88 locks
    flags: Per-session, for-rx-IPv4
    16 hash buckets             
    < 0 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
    < 1 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
    < 2 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
    < 3 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
    < 4 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
    < 5 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
    < 6 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
    < 7 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
    < 8 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
    < 9 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
    <10 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
    <11 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
    <12 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
    <13 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
    <14 > IP adj out of Vlan11, addr x.x.x.135 08EE7560
    <15 > IP adj out of Vlan10, addr x.x.x.153 093A4E60
    Subblocks:                                                                                  
    None

  • WLC LAG Mode and Port Channel

    So I was reading the controller best practices and got this:
    When you use LAG, the controller relies on the switch for the load balancing decisions on traffic that come from the network. It expects that traffic that belongs to an AP always enters on the same port. Use only ip-src or ip-src ip-dst load balancing options in the switch EtherChannel configuration. Some switch models might use unsupported load balancing mechanisms by default, so it is important to verify.
    This is how to verify the EtherChannel load balancing mechanism:
    switch#show etherchannel load-balance
    EtherChannel Load-Balancing Configuration:
    src-dst-ip
    EtherChannel Load-Balancing Addresses Used Per-Protocol:
    Non-IP: Source XOR Destination MAC address
    IPv4: Source XOR Destination IP address
    IPv6: Source XOR Destination IP address
    This is how to change the switch configuration (IOS):
    switch(config)#port-channel load-balance src-dst-ip
    Now Cisco switches by default will do src-mac.  If I make this change obviously this would be a global change.  I don't believe it should cause any performance issues but wanted to get some expert opinions on this.  Switches my controller will be connected to will also have two routers connected as well via Port Channel.
    I'm trying to understand the reasoning behind this.

    I've never seen that command cause any issues in any deployment I've worked on.
    HTH,
    Steve

  • ASA port-channel command on IOS v. 9.0(4)

    I have configured 2 of ASA 5550 on a port channel as follows:
    =======================================
    router# show version
    Cisco Adaptive Security Appliance Software Version 8.4(2)
    router# show module
      0 ASA 5550 Adaptive Security Appliance         ASA5550            JMX1226L1S9
      1 SSM-4GE Included with ASA 5550 System        SSM-4GE-INC        JAF1224ATNS
    router# show interface Port-channel48
    Interface Port-channel48 "", is up, line protocol is up
      Hardware is EtherChannel/ON, BW 2000 Mbps, DLY 10 usec
        Auto-Duplex(Full-duplex), Auto-Speed(1000 Mbps)
        Input flow control is unsupported, output flow control is off
        Media-type configured as RJ45 connector
        Available but not configured via nameif
        MAC address 001f.ca97.44e2, MTU not set
        IP address unassigned
      Members in this channel:
          Active:   Gi1/2 Gi1/3
    router# show startup-config
    interface GigabitEthernet1/2
     channel-group 48 mode on
     no nameif
     no security-level
     no ip address
    interface GigabitEthernet1/3
     channel-group 48 mode on
     no nameif
     no security-level
     no ip address
    interface Port-channel48
     no nameif
     no security-level
     no ip address
    interface Port-channel48.4
     vlan 4
    interface Port-channel48.5
     vlan 5
    After migrating to version 9.0(4) I could not configure channel group on int g 1/2.
    =======================================
    router# show version
    Cisco Adaptive Security Appliance Software Version 9.0(4)
    router# show module
      0 ASA 5550 Adaptive Security Appliance         ASA5550            JMX1421L333
      1 SSM-4GE Included with ASA 5550 System        SSM-4GE-INC        JAF1419ALAK
    router# configure terminal
    router(config)# interface GigabitEthernet1/2
    router(config-if)#  channel-group 48 mode on
                          ^
    ERROR: % Invalid input detected at '^' marker.
    router(config-if)# ?
    So I have the following questions about verion 9:
    1. Can I still use port-channels on a sigle ASA?
    2. Should I replace port-channel by lacp command on a sigle ASA?
    3. Does lacp command can be used only on clusters ?
    Att.,
    Rosa

    The following is documented in the config guide for both 8.4 and 9.0:
    •You cannot use interfaces on the 4GE SSM, including the integrated 4GE SSM in slot 1 on the ASA 5550, as part of an EtherChannel. 
    So, even with 8.4 it was probably never meant to work.

  • Create port channel between UCS-FI and MDS 9124 (F Mode)

    Dear Team,
    We were trying to create  port channel between UCS FI and MDS 9124
    But the port channel not getting active in F mode on MDS 9124
    FI is in FC End Host Mode
    We have enabled FC uplink trunking on FI
    We have enabled NPIV on MDS
    We have enabled trunk on MDS
    FI and MDS in default VSAN
    To check we changed the FI mode to FC Switching mode and port channels became active but in E mode
    when we enabled FC uplink trunking on FI and FC Switching mode port channels became active in TE mode
    but in both the above cases showflogi database shows WWPN of SAN alone not showing any from FI.
    How to achive this?
    Have read that no need to change the swicthing mode to FC Switching mode and keep as FC Endhost mode
    SO how to achieve Port channel with F mode in MDS and FI ( Mode showing as NProxy)
    Does it has to do anything with MDS NX-OS version? (https://supportforums.cisco.com/thread/2179129)
    If yes how to upgrade as license for ports came along with Device and we do not have any PAC/PAK or license file as it came
    with license
    Also we have seen 2 files availabe for download (m9100-s2ek9-kickstart-mz.5.2.8b.bin and m9100-s2ek9-mz.5.2.8b.bin) which to use
    Thanks and Regards
    Jose

    Hi Jo Bo,
    what version of software if your MDS running?
    On your UCS do connect nxos and show inteface brieft and look at the mac address.
    it is possible that you might be hitting the bug below. if this is the case you might need to upgrade the firmware on your MDS.
    Add MAC OUI "002a6a", "8c604f", "00defb" for 5k/UCS-FI
    http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCty04686
    Symptom:
    Nexus switch unable to connect any other Nexus or other Cisco Switch in NPV mode with a F port-channel.   Issue might be seen in earlier 5.1 releases like
    5.1.3.N1.1a
    but not the latest
    5.1.3.N2.1c
    release. Issue is also seen in
    5.2(1)N1(1)
    and
    6.0(2)N1(1)
    and later releases.
    Conditions:
    Nexus configured for SAN PortChannels or NPIV trunking mode Nexus connected to UCS via regular F port channel where UCS in NPV mode  NPV edge switch: Port WWN OUI from UCS FI  or other Cisco manufactured switch:  xx:xx:00:2a:6a:xx:xx:xx   OR  xx:xx:8c:60:4f:xx:xx:xx
    Workaround:
    Turn-off trunking mode on Nexus 5k TF-port Issue does not happen with standard  F-PORT Remove SAN Portchannel config
    Further Problem Description:
    To verify the issue please collect  show flogi internal event-history errors  Each time the port is attempted OLS, NOS, LRR counters will increment. This can be determined via the following output,  show port internal info all show port internal event-history errors

  • Does Solaris 10 support cisco Virtual Port Channels over IP?

    Does anyone know if Solaris 10 support cisco Virtual Port Channels open IP?

    Hi user11114413,
    The issue you are seeing actually has little to do with VIP, and more to do with there being multiple IP addresses for us to choose from on your box. For such multi-IP boxes, you'll want to tell us the IP to use, and in your case you want to tell as a VIP. This can be done either by editing your operational configuration file, and including an <address> element within the <unicast-listener> element, or via the tangosol.coherence.localhost system property. For example:
    <unicast-listener>
        <well-known-addresses>
            <socket-address id="1">
                <address>1.2.3.260</address> <!--virtual ip -->
                <port>8088</port>
            </socket-address>
        </well-known-addresses>
        <address>1.2.3.260</address> <!--virtual ip -->
        <port>8088</port>
    </unicast-listener>or
    java ... -Dtangosol.coherence.localhost=1.2.3.260If you are using the same operational configuration on all nodes in your cluster then the system property approach is likely preferable, and would only be necessary on the two machines sharing the VIP.
    As for using VIP or an extended WKA list, the choice is yours, either will work. If you do go the VIP route, it would obviously be a very bad idea to simultaneously use the same VIP and port at the same time from the two machines.
    thanks,
    Mark
    Oracle Coherence

  • Stacking 3750s and Port Channel

    We're replacing legacy switches with 3750s in the coming months, and I have a question about stacking and port channel.
    The 3750s will be Layer 2 switches, and each will be uplinked via Gigabit fiber to a pair of 6500s acting as Layer 3 distribution switches.
    One thing I'm not sure about is if it will be possible to built Port Channel links for 2, 3, or 4 GB across different switches, or if I can only put Port Channels on the same switch. My understanding is with stacking it appears as one big switch and I can built Port Channels however I want, but am not 100% if this design will work.

    You can certainly configure EtherChannels across different 3750s in the same stack, thus avoiding your single point of failure by having the aggregate ports all in one switch.
    However in the scenario the port channel has to be configured explicitly to ON, PaGP is not supported across stack members.
    3750 stack switches appear as a single logical switch with a single management address. From which you can configure all physical ports. It is important to remember that you configure your switch priorities accordingly in order to govern which switch is your master, and also set a secondary.
    Regards
    Allan.
    Please kindly rate this post if you find this information helpful.

  • FEX-2232 FCoE Port channel limitation

    Hi all,
    i havea single FEX 2232 single homed to nexus 5020 via port-channel. at the FEX 2232, i connected a server which have 2 X CNA and running two vlans: vlan 200 for ethernet and vlan 300 for FCoE.
    i connected the server to the single fex via port-channel and allowed vlan 200 & 300. at the N5K i bounded single vfc interface to this port-channel.
    when i am issuing the show flogi database i see only single PWWN.
    as i understand, a single vfc interface can only see single PWWN, is this correct ?
    if it does, how can i have my setup running in a way that ethernet traffic  will used port-channel and for fcoe traffic i will see two PWWN ?
    please advise,
    Avi.

    It is not necessary to create another FCoE Vlan if the logins are coming on the same n5k. If there is a requirement for multiple fcoe logins on the same n5k, then it will need to be single link port channels instead of multiple links in the port channel. That way we acquire the ability to bind each physical port via port-channel into a separate vfc. In your case ideally you can have two n5ks with two n2232s single homed to each n5k and the server dual homed with 1 port each connected to two separate 2232s in active-active teaming. That way you can bind the physical interfaces into single virtual port channel on the respective n5ks. at that point, you can separate the san traffic into different vsan/vlan and make sure you dont trunk the fcoe vlan over the vpc peer link.
    Hope this helps, Vinayak.

  • IOS to NXOS VPC PORT CHANNEL

    Hello
    I have a pair of Nexus 5K's in a VPC domain and some 2960's as VPC members, with a port channel to the domain.
    Topology is as follows:
    5K1 and 5K2 in VPC domain
    VPC from 5K1 and 5K2 to 2960
    2960 has gi0/1 and gi0/2 in 1 port channel
    gi0/1 to 5k1, gi0/2 to 5k2
    I know that what I am going to ask may be totally against the purpose of VPC, but, I am looking for a way to favour gi0/1 for traffic, rather than load balancing over gi0/1 and gi0/2. The reaon for this is that I would like to benefit from the lack of loop that VPC provides, but would also like to have a primary and secondary link as the majority of traffic should actually go via 5K1, rather than 5K2.
    Any suggestions welcome.
    Many thanks in advance
    Anthony

    Hi Anthony,
    The Cisco NX-OS software load balances traffic across all operational interfaces in a portchannel by hashing the addresses in the frame to a numerical value that selects one of the links in the channel. Port channels provide load balancing by default. Port-channel load-balancing uses MAC addresses, IP addresses, or Layer 4 port numbers to select the link. Port-channel load balancing uses either source or destination addresses or ports, or both source and destination addresses or ports.
    You can configure the load-balancing mode to apply to all port channels that are configured on the entire device or on specified modules. The per-module configuration takes precedence over the load-balancing configuration for the entire device. You can configure one load-balancing mode for the entire device, a different mode for specified
    modules, and another mode for the other specified modules. You cannot configure the load-balancing method per port channel.
    You can configure the type of load-balancing algorithm used. You can choose the load-balancing algorithm that determines which member port to select for egress traffic by looking at the fields in the frame.
    Note:  The default load-balancing mode for Layer 3 interfaces is the source and destination IP address, and the default load-balancing mode for non-IP interfaces is the source and destination MAC address.
    From the config mode you can try different load-balacing method ,
    port-channel load-balance {dest-ip-port | dest-ip-port-vlan |
    destination-ip-vlan | destination-mac | destination-port | source-dest-ip-port | source-dest-ip-port-vlan | source-dest-ip-vlan | source-dest-mac | source-dest-port | source-ip-port | source-ip-port-vlan | source-ip-vlan | source-mac | source-port} [module-number]
    To Summarize: I cannot say which port would be selected, it purely depends on type of frame you are sending with the combination of the load-balance method.
    After tweaking you can also know from the command which link the traffic is taking,
    NEXUS2-SPAN# show port-channel load-balance forwarding-path interface port-channel 71 src-ip 1.1.1.1 dst-ip 2.2.2.2 vlan 51 module 2
    Module 2: Missing params will be substituted by 0's.
    Load-balance Algorithm: src-dst ip-l4port
    RBH: 0xb0       Outgoing port id: Ethernet8/8
    we can also try tweaking the same load-balancing on the 2960 also. It purely depends on the load-balancing algorithm. Below is for 2960 Load-balancing tweaking,
    http://www.cisco.com/en/US/docs/switches/lan/catalyst2960/software/release/12.2_53_se/configuration/guide/swethchl.html
    Even after doing this i wouldnt say 100% it would select one link.
    Hope this helps!
    Thanks,
    Richard.
    *Rate if this is useful

  • Why don't channel-group numbers match on a VSS port-channel link?

    Hi All,
    I have two 6509's that are VSS'd together via four 10gig links on each side. The configuration was done before I started this job, but in reviewing the configs I see that the 10gbps VSS heartbeat links are port-channeled together on each side, but one side is channel-group 2, while the other end of the bundle is channel-group 1.
    I thought that channel-group numbers needed to match on both ends of the port-channel for it to form correctly?
    I'm guessing that this has to happen because the switches are virtually one, so you can't put all 8 links into the same channel-group number or there would be nothing to connect to on the other side. Therefore, the "switch virtual link #" command is the real code that tells the switch where the other end of the link is, regardless of channel-group number, correct?

    Dean,
    The channel-group number does not have to be the same on each end. The four ports on switch A have to be in the same channel-group, and the four ports on switch B have to be in the same channel-group, but there's no communication across that line about what the channel-group is called. It's just a name. From a design standpoint it is nice to have them the same on both sides, but it's not always simple to allow for that in the design of a network.
    -Jameson

  • N7K Port Channel Layer 3 VLAN Question

    I have 2 N7K switches and would like to connect them via port channel and put the channel in VLAN 101. I have the following config, does it make sense? Thanks in advance!
    interface eth 3/1
    switchport
    channel-group 101 mode active
    interface eth 3/2
    switchport
    channel-group 101 mode active
    interface port-channel 101
    switchport
    switchport mode access
    switchport access vlan 10
    spanning-tree network type edge
    interface vlan 10
    ip address 10.1.1.1/24

    Could be something like this in the both sides (if the port numbers match):
    conf t
    feature lacp
    feature interface-vlan
    interface eth 3/1
    switchport
    channel-group 101 mode active
    interface eth 3/2
    switchport
    channel-group 101 mode active
    interface port-channel 101
    switchport
    switchport mode access
    switchport access vlan 101
    spanning-tree port type network
    interface vlan 101
    ip address 10.1.1.1/24
    no shut
    end
    vlan 101
    end
    *(This ip address will be available in only one box, you can use a FHRP as well, to increase the level of reachability)

  • FC port channels between MDS and UCS FI best practice?

    Hi,
    We would like to create FC port channels between our UCS FI's and MDS9250 switches.
    At the moment we have 2 separate 8Gbps links to the FI's.
    Are there any disadvantages or reasons to NOT do this?
    Is it a best practice?
    Thanks.

    As Walter said, having port-channels is best practice.  Here is a little more information on why.
    Let's take your example of two 8Gbps links, not in a port-channel ( and no static pinning ) for Fibre Channel connectivity:
    Hosts on the UCS get automatically assigned ( pinned ) to the individual uplinks in a round-robin fashion.
    (1)If you have some hosts that are transferring a lot of data, to and from storage, these hosts can end up pinned to the same uplink and could hurt their performance. 
    In a port-channel, the hosts are pinned to the port-channel and not individual links.
    (2)Since hosts are assigned to an individual link, if that link goes down, the hosts now have to log back into the fabric over the existing working link.   Now you would have all hosts sharing a single link. The hosts will not get re-pinned to a link until they leave and rejoin the fabric.  To get them load balanced again would require taking them out of the fabric and adding them back, again via log out, power off, reload, etc...
    If the links are in a port-channel, the loss of one link will reduce the bandwidth of course, but when the link is restored, no hosts have to be logged out to regain the bandwidth.
    Best regards,
    Jim

  • MDS9513 Add ISL to Port Channel problem.

    Hi Experts,
    I have a problem when add a new ISL to an existing Port Channel config.
    The ISL port is up state and correctly configured like another ports in port channel.
    Looks bellow the error:
    MDS1300M6A# show port-channel summary
    Interface                 Total Ports        Oper Ports        First Oper Port
    port-channel 1                 4                 4                  fc12/48
    port-channel 2                 2                 2                  fc6/47
    MDS1300M6A# show port-channel database
    port-channel 1
        Administrative channel mode is active
        Operational channel mode is active
        Last membership update failed: port not compatible [Resources Unavailable]
        First operational port is fc12/48
        4 ports in total, 4 ports up
        Ports:   fc12/48  [up] *
                 fc10/48  [up]
                 fc11/48  [up]
                 fc9/48   [up]
    Anyone seen this?
    Tks
    Wellington

    That did the trick - specifically setting the port channel to rate-mode shared.  Certainly solved the problem as far as getting all the deisred ports up in the channel, but where I still have a knowledge gap is the operational difference between dedicated and shared.  Are there any Cisco docs (beyond the command reference guide to toggle the feature) that explains why you'd choose one versus the other, and what it means from a design perspective?
    On a different note, while I'm no expert, here's some background to consider for others who may encounter the same issue (whether on UCS or a Nexus 5K).  I  (and our network team) come from an IOS background, so while the IOS "parts" of NX-OS are pretty familiar, the SAN "parts" of NX-OS are a little new.  We're also more CLI oriented, and while not impossible to configure via CLI, in our environment, the GUI for UCS seems to be more popular across the board - and we're still learning that piece as well.
    Our storage team is very familiar with SAN-OS, so they're very comfortable with the SAN "parts" of NX-OS.  But, they're very used to configuring the MDS switches via the GUI, which is what got us off track a bit.  In our scenario, creating a SAN port channel on the MDS via the GUI didn't give us the option for setting "switchport rate-mode shared"  Not saying it's not there in the GUI, but we certainly couldn't find it.
    Long story short, if the configuration of the SAN port channel on the MDS is in question, check it via the CLI and make any necessary changes there as a quick workaroud.

  • ASA5580 port channel to 6509 VSS

    Hi All,
    I hope this is the correct location for this.
    Anyway, here's the situation I'm trying to configure several VLANs on my ASA to uniquely allocate to contexts, the VLANs will be trunked from my VSS.
    Unfortunately I'm not clear on how to achieve this, the configuration guide for 8.4 talks about multiple contexts and routed setups all which don't appear to apply exactly. I've configured the port channel at both ends and I've configured sub-interfaces on the port channel and assigned VLAN IDs. These sub-interfaces are then allocated to the contexts to set 'ip address' etc. I've not been able to successfully test this configuration and I am concerned that it is incorrect..
    If anyone has any advice or suggestions I would be grateful?
    Many thanks.

    Well the good news is that I have been able to test my configuration.
    Using an infrequently utilised VLAN I disabled the current interface and brought up an allocated port on the new ASA which I successfully pinged the subinterface ip of (configured via a context of the ASA). The complication was using the correct VRF as the source! 
    All is good ready for the cut-over.
    Regards.

Maybe you are looking for