Cisco MDS port channel with USC FI

Hello,
Can anyone help me to configure/troubleshoot Cisco MDS 9148 with Cisco USC ? M stuck in port channel..i have configured but interfaces are not coming UP.It is showing init state.
My Topology is like,
Nexus 5000-->USC FI (single FI) -->Cisco MDS 9148
--> Two Chassis
Any help would be highly appreciated...
Thanx

TMC-UCSFI-A-A(nxos)# sh interface brief
Interface Vsan   Admin Admin   Status          SFP    Oper Oper   Port
                  Mode   Trunk                          Mode Speed Channel
                         Mode                                 (Gbps)
fc1/31     1      NP     off     errDisabled      swl    --           --
fc1/32     1      NP     off     errDisabled      swl    --           --
Ethernet      VLAN   Type Mode   Status Reason                   Speed     Port
Interface                                                                   Ch #
Eth1/1        1      eth fabric up      none                        10G(D) --
Eth1/2        1      eth fabric up      none                        10G(D) --
Eth1/3        1      eth fabric up      none                        10G(D) --
Eth1/4        1      eth fabric up      none                        10G(D) --
Eth1/5        1      eth access down    SFP not inserted            10G(D) --
Eth1/6        1      eth access down    SFP not inserted            10G(D) --
Eth1/7        1      eth access down    SFP not inserted            10G(D) --
Eth1/8        1      eth access down    SFP not inserted            10G(D) --
Eth1/9        1      eth access down    SFP not inserted            10G(D) --
Eth1/10       1      eth access down    SFP not inserted            10G(D) --
Eth1/11       1      eth access down    SFP not inserted            10G(D) --
Eth1/12       1      eth access down    SFP not inserted            10G(D) --
Eth1/13       1      eth access down    SFP not inserted            10G(D) --
Eth1/14       1      eth access down    SFP not inserted            10G(D) --
Eth1/15       1      eth trunk up      none                        10G(D) 100
Eth1/16       1      eth trunk up      none                        10G(D) 100
Eth1/17       1      eth fabric up      none                        10G(D) --
Eth1/18       1      eth fabric up      none                        10G(D) --
Eth1/19       1      eth fabric up      none                        10G(D) --
Eth1/20       1      eth fabric up      none                        10G(D) --
Eth1/21       1      eth access down    SFP not inserted            10G(D) --
Eth1/22       1      eth access down    SFP not inserted            10G(D) --
Eth1/23       1      eth access down    SFP not inserted            10G(D) --
Eth1/24       1      eth access down    SFP not inserted            10G(D) --
Eth1/25       1      eth access down    SFP not inserted            10G(D) --
Eth1/26       1      eth access down    SFP not inserted            10G(D) --
Eth1/27       1      eth access down    SFP not inserted            10G(D) --
Eth1/28       1      eth access down    SFP not inserted            10G(D) --
Eth1/29       1      eth access down    SFP not inserted            10G(D) --
Eth1/30       1      eth access down    SFP not inserted            10G(D) --
output ommitted
TMC-UCSFI-A-A(nxos)#
Here it shows that Fc1/31- 32 which are in trunk , status is errdisabled and admin trunk mode is off

Similar Messages

Cisco MDS Port channel load balancing

A customer recently asked an interesting question about exchange based load balancing on an FC port channel. The platform is UCS with an 8 and 16 port channel per fabric interconnect on two separate UCS domains. The application is Oracles data warehousing which has been known to saturate 4 x 8gb fc links. Since the balancing method is exchange based what constitutes the start and end of an exchange? We are trying to avoid a condition where and intense read write conversation locks to a single link in the port channel and not spread across 8/16 links. Where can I find more information about exchange based routing protocol or how should I go about managing extreme io in a converged infrastructure.

The default loadbalance method on FI and MDS is src-dst-ox-id based. Note that loadbalancing is done by a device on *outgoing traffic*. FI and MDS do not have to negotiate anything here. Technically, one device can do src-dst-id based while the other can use src-dst-ox-id. However, in your case there is no reason for such a change.
As I wrote before, If all of the links in the port-channel are touching the max capacity, you should recommend your customer to increase links in the bundle (max 16) or upgrade to 16G links. If few of the links are heavily utilized while other links in the same port-channel are under utilized, you may want to check the application or HBA for capability of breaking down the large reads/writes under smaller exchanges. If no traffic is going on few of the links at all, then I would suspect UCS to FI pinning as well.

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> 
            <port>8088</port>
        </socket-address>
    </well-known-addresses>
    <address>1.2.3.260</address> 
    <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

Cisco MDS 9148 compatibility with Finisar FTLF-8524-P2BNV SFP+

Hello,
I have a Cisco MDS 9148 switch with Finisar FTLF-8524-P2BNV SFP+ modules. I am told by the guys configuring the equipment that these modules are not identified in the switch interface.
I am curious if there could be a compatibility problem (I have not found a compatibility list) or any other issue which could cause the behaviour.
Thank you

How to configure a port channel with VLAN trunking (and make it work..)

We're trying to configure a port channel group with trunked ports to connect a NetApp HA pair. We want to create two data LIFs and connect them to the switch stack. We are trying to create 2 data lifs, one for cifs and one for nfs that are on different vlans.
We want the same ports to be able to allow multiple vlans to communicate. (trunked)
These data lifs should be able to fail over to different nodes in the HA pair and still be able to communicate on the network.
What this means is that we have to connect 4 ports each for each node in the NetApp HA Pair to the switches and create a port channel of some type that allows for trunked vlans. When we configure the ports, the configuration is as follows (below):
We are only able to configure an IP on one of the vlans.
When we configure an IP from another vlan for the data lif, it does not respond to a ping.
Does anyone have any idea what I'm doing wrong on the Cisco switch?
interface GigabitEthernet4/0/12
description Netapp2-e0a
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
channel-protocol lacp
channel-group 20 mode active
end
interface GigabitEthernet4/0/13
description Netapp2-e0c
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
channel-protocol lacp
channel-group 20 mode active
end
interface GigabitEthernet6/0/12
description Netapp2-e0b
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
channel-protocol lacp
channel-group 20 mode active
end
interface GigabitEthernet6/0/13
description Netapp2-e0d
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
channel-protocol lacp
channel-group 20 mode active
end
interface Port-channel20
description Netapp2-NFS
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
spanning-tree portfast
spanning-tree bpduguard enable
end

Our problem was fixed by the storage people. They changed the server end to trunk, and the encapsulation / etherchannel.
I like all the suggestions, and they probably helped out with the configuration getting this to work.
Thanks!
interface Port-channel20
description Netapp2-NFS
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
switchport mode trunk
interface GigabitEthernet4/0/12
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
switchport mode trunk
channel-protocol lacp
channel-group 20 mode active
interface GigabitEthernet4/0/13
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
switchport mode trunk
channel-protocol lacp
channel-group 20 mode active
interface GigabitEthernet6/0/12
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
switchport mode trunk
channel-protocol lacp
channel-group 20 mode active
interface GigabitEthernet6/0/13
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 10,20,511,519
switchport mode trunk
channel-protocol lacp
channel-group 20 mode active

Port-channel with Private VLANs on Nexus1000v

Hi all,
It says that private vlans are not supported on port-channel ports ont Nexus 1000v L2 Switching Guide.
AFAIK, if you have two ports between ESX VEM and physical switch and both these ports are configured as 802.1Q and carrying the same VLANs, when the port which carries the traffic at the moment fails, the other port do not failover automatically. This is mentioned in "Nexus 1000v Deployment Guide version 2" as ,
"Individual Uplinks : A standard uplink is an uplink that is not a member of a PortChannel from the VEM to a physical switch. It provides
no capability to load balance across multiple standard uplink links and no high-availability characteristics. When a standard uplink fails, no secondary link exists to take over. Defining two standard uplinks to carry the same VLAN involves the risk of creating loops within the environment and is an unsupported configuration. Cisco NX-OS will post warnings when such a condition occurs. "
Does anyone have any idea in order for the attached topology to work. Do I have to forward each and every VLAN from different ports ? If I do that how am I going to manage different VLANs and still have that hosts in the same primary VLAN with same IP subnet ?
Thanks in advance.
Dumlu

Hi,
You can't have M and F ports in single port channel irrespective what code version you are running , it will throw error on you..
nor you can have m1 port channel one side and another f port channel other side , port channel

Write all digitall ports (Channels) with decimal value

Hi,
it is possible to write all digital port with a decimal value for a device with 96 channels in the same time?
I have a USB 6509 device and I want to write each bit whit value 1 in loop (for the first port I write 0,1,2,4,8,16, 32, 64 and 128) with line "Dev3/port0/line0:7", but if I want to write all the ports in the same time how to set the line and the "DAQmx write.vi"?
Thank you.
Solved!
Go to Solution.
Attachments:
Untitled 1.vi ‏13 KB

You can setup reading and writing in 8-bit ports with the 6509. So you could just write 128 to "Dev3/port0". If you want to write to all 12 ports, I recommend making a task that is multiple channels on the 6509 module, each channel in the task being a port. You can then use the Multiple Channel, Single Sample to write your values. Your values will need to be in an array of U8.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Cisco FXO Port disconnect with DMS-10

Hello,
We have a situation where FXO ports are connected to DMS-10 at telco end. DMS-10 doesn't send out any disconnect tone or power denial. Is there a way to detect on CISCO ISR that remote party has disconnected call? Is there a way to disconnect a call after no activity on line after certain amount of time? CO has confirm that they have increase silent on lines to give ISR chance to disconnect the call.
Thank You.

timer media-inactive To enable the timer for media inactivity detection using the digital signal processor (DSP) (based on RTP as the only criterion) and to configure a multiplication factor based on the real-time control protocol (RTCP) timer interval, use the timer media-inactive command in gateway configuration mode. To reset to the default, use the no form of this command. timer media-inactive multiple no timer media-inactive multiple
When the timer media-inactive command is used, the gateway uses the inactivity timer as a combination of the timer media-inactive command and the ip rtcp report interval command. The timer media-inactive command uses DSP statistics. This capability is based on the configuration of callfeature parameters using application command-line interface (CLI) to enable control. The media are considered inactive only if there is no transfer of RTP packets in the send direction and no RTP packets in the receive direction. If RTP is present in either the send or receive direction, it is considered active. In this mode, DSP filters out any comfort noise packets, and the presence of any comfort noise packet is considered inactivity in either direction. The multiple argument (or multiplication factor) is multiplied by the interval that is set using the ip rtcp report interval command. This command configures the average interval between successive RTCP report transmissions for a given voice session. For example, if the value argument is set to 25,000 milliseconds, an RTCP report is sent every 25 seconds, on average. If no RTP packets are received during the calculated interval, the call is disconnected. The gateway signals the disconnect to the VoIP network and the time-division multiplexing (TDM) network so that upstream and downstream devices can clear their resources.
Sent from Cisco Technical Support iPad App

Cisco MDS 9148 compatibity with EMC VNX 5300

Hi Cisco ,
We have 2 MDS 9148 switches running on NX-OS 5.0(1a). These switches are connected to EMC VNX 5300 currently running on 05.31 version.
We are planning to upgrade both Switches and VNX.
So my query to you guys is, I am thinking to upgrade Switch to NX-OS 5.2(8c). Will this 5.2(8c) support the VNX 5300 05.32 version.
Please suggest.
Pranav.

Please check
http://www.emc.com/interoperability
and
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/interoperability/matrix/intmatrx/Matrix1.html

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

MDS configuration for port channel

I've tried to set up the new FC port channel upload to a pair of MDS 9124s, but as I don't know enough about the MDS side I can't get the link to come up. Are there any references available anywhere that tell you blow by blow exactly how to configure the MDS side of the port channel? Or perhaps a sample working config?
Thanks

Simon,
A few items:
1) You are on 1.4.1i Balboa code
2) FI's are in FC switch mode as MDS 9124's don't support F-port channel (NPV/NPIV)
3) It's a lot easier the first time if you have matched speed sfp+ all around. Although, with the correct configs, unmatched speeds can be made to work.
If the FIs are in switch mode and your MDS is running a minimum 3.3 here are some configs that may help:
MDS side interfaces 4/11 and 4/12 are plugged into the UCS fc ports. First setup and ensure ISLs are working properly between UCS and MDS, then configure the port-channels
interface fc4/11
switchport rate-mode dedicated
switchport mode E
switchport trunk mode auto
no shutdown
interface fc4/12
switchport rate-mode dedicated
switchport mode E
switchport trunk mode auto
no shutdown
The UCS GUI Equipment -> Fabric Interconnects -> FI-A -> Set FC Switching Mode. This will cause both FI's to reboot into FC switch mode. This is VERY DISRUPTIVE, both FI's will reboot.
On the UCS CLI you should see this on the UCS fc ports connected to the MDS
cae-sj-ca3-A(nxos)# show running-config interface fc 2/1-2
!Command: show running-config interface fc2/1-2
!Time: Wed Oct 20 16:49:39 2010
version 4.2(1)N1(1.4)
interface fc2/1
switchport mode E
no shutdown
interface fc2/2
switchport mode E
no shutdown
Until you have VSAN trunks enabled, make sure the ports on the UCS and MDS are in the same VSAN. VSAN 1 for example.
Once you have working ISLs, then proceed to turn them into port-channels and enable VSAN trunking. Start with the MDS
Create a channel group, it should look like this
cae-sj-9506-1# show run interface port-channel 3
!Command: show running-config interface port-channel 3
!Time: Wed Oct 20 17:06:01 2010
version 5.0(1a)
interface port-channel 3
channel mode active
switchport mode E
switchport rate-mode dedicated
switchport trunk mode auto <-- VSAN trunking
Enable VSAN trunking on the MDS ISL interfaces, it'll look like this:
cae-sj-9506-1# show run interface fc 4/11-12
!Command: show running-config interface fc4/11-12
!Time: Wed Oct 20 17:07:05 2010
version 5.0(1a)
interface fc4/11
switchport rate-mode dedicated
switchport mode E
switchport trunk mode auto
no shutdown
interface fc4/12
switchport rate-mode dedicated
switchport mode E
switchport trunk mode auto
no shutdown
Add the channel group information to the MDS ISL interfaces:
Enter configuration commands, one per line. End with CNTL/Z.
cae-sj-9506-1(config)# interface fc 4/11-12
cae-sj-9506-1(config-if)# channel-group 3 force
fc4/11 fc4/12 added to port-channel 3 and disabled
please do the same operation on the switch at the other end of the port-channel,
then do "no shutdown" at both ends to bring it up
cae-sj-9506-1(config-if)# show run interface fc 4/11-12
!Command: show running-config interface fc4/11-12
!Time: Wed Oct 20 17:07:39 2010
version 5.0(1a)
interface fc4/11
switchport rate-mode dedicated
switchport mode E
switchport trunk mode auto
channel-group 3 force
no shutdown
interface fc4/12
switchport rate-mode dedicated
switchport mode E
switchport trunk mode auto
channel-group 3 force
no shutdown
Create the SAN port channel on the UCS side
SAN -> SAN Cloud -> Fabric A -> FC Port Channels -> Create Port Channel
After you create the SAN port channel in UCS, make sure and enable it. I also bounce the MDS port channel at this point.
If all is correct, in a few agonizing minutes, the port-channel will be formed and passing data.
cae-sj-ca3-A(nxos)# show interface san-port-channel 1
san-port-channel 1 is trunking
    Hardware is Fibre Channel
    Port WWN is 24:01:00:0d:ec:d3:5d:c0
    Admin port mode is E, trunk mode is on
    snmp link state traps are enabled
    Port mode is TE
    Port vsan is 1
    Speed is 8 Gbps
    Trunk vsans (admin allowed and active) (1,10,26,50,66,100-101,103,123,222,24
0)
    Trunk vsans (up)                       (1,10,50,100,103)
    Trunk vsans (isolated)                 (26,66,101,123,222,240)
    Trunk vsans (initializing)             ()
    5 minute input rate 2312 bits/sec, 289 bytes/sec, 2 frames/sec
    5 minute output rate 1440 bits/sec, 180 bytes/sec, 2 frames/sec
      2669 frames input, 194760 bytes
        0 discards, 0 errors
        0 CRC, 0 unknown class
        0 too long, 0 too short
      2677 frames output, 158316 bytes
        0 discards, 0 errors
    0 input OLS, 1 LRR, 0 NOS, 0 loop inits
Again, make sure you have the ISLs up an running first before configuring the port-channels. It makes troubleshooting much easier.
Let me know if you need any help.

Cisco Nexus 7010 Port-Channel

Hi all,
Hi have install a cisco nexus 7010 with the following modules :
Mod Ports Module-Type Model Status
1 48 1000 Mbps Optical Ethernet XL Modul N7K-M148GS-11L ok
2 48 10/100/1000 Mbps Ethernet XL Module N7K-M148GT-11L ok
5 0 Supervisor Module-2 N7K-SUP2 active *
6 0 Supervisor Module-2 N7K-SUP2 ha-standby
9 48 10/100/1000 Mbps Ethernet XL Module N7K-M148GT-11L ok
10 48 1/10 Gbps Ethernet Module N7K-F248XP-25E ok
After trying to build a port-channel with a 1G port on slot 1 and a 1G port on slot 10 i get a messague with incompatible port.
Can any one tell me if its supported a port-channel with ports on the following modules :
N7K-M148GS-11L
N7K-F248XP-25E
Thanks
Patrício

Hi Particio,
The port-channel/vPC features require that all uplinks are connected to the same type of
module. You can refer to the following document.
http://www.cisco.com/en/US/partner/docs/switches/datacenter/sw/6_x/nx-os/interfaces/configuration/guide/if_portchannel.html#wp1888267
HTH
Regards
Inayath
*Plz rate if this is helpfull and mark as Answerd if this answerd your query.

Troubleshoot connectivity with Cisco MDS 9124

Hello,
I recentrly discovered that it's become impossible to connect to a CISCO MDS 9124, neither with SSH nor with Serial connection.
What should i do please to resolve that issue please?
Regards!

Hi,
Are you able to access the 9124 by Device Manager, web browser, telnet, or ssh when your laptop is directly connected to the mgmt0 interface and your laptop configured on the same subnet as the mgmt0 interface?
What console settings, console cable, terminal emulator application are you using and does it work with another MDS9000?
Regards,
David

Port Channel 5548 with 6509

My company just purchased a Nexus 5548. I've been fooling around with the configurations and just getting familiar with this equipment. I've already configured a port channel using 2 10gig ports on our 3850 and its working fine.
Now, I'm trying to configure a second port channel with our 6509 1gig ports. Ports comes up. But I cannot communicate between these 2 devices.
Show CDP Neigh shows the other devices. Show Etherchannel summary is blank
This is the config on the 6509
interface Port-channel22
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
interface GigabitEthernet9/7
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 22 mode on (I also tried using Active and desirable)
Config on 5548
Inteface Port-Channel 2
switchport
switchport mode trunk
speed 1000
interface ethernet1/32
switchport mode trunk
speed 1000
channel-group 22 mode on
I also have feature Lacp , interface vlan and vlan dot1q tag native enabled
Any ideas why I cannot communicate between these devices?

This is what is showing on the 5548
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-SPEED: Interface Ethernet1/32, operat
ional speed changed to 1 Gbps
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-IF_DUPLEX: Interface Ethernet1/32, op
erational duplex mode changed to Full
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Etherne
t1/32, operational Receive Flow Control state changed to off
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface Etherne
t1/32, operational Transmit Flow Control state changed to off
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-SPEED: Interface port-channel2, opera
tional speed changed to 1 Gbps
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-IF_DUPLEX: Interface port-channel2, o
perational duplex mode changed to Full
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-IF_RX_FLOW_CONTROL: Interface port-ch
annel2, operational Receive Flow Control state changed to off
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-IF_TX_FLOW_CONTROL: Interface port-ch
annel2, operational Transmit Flow Control state changed to off
2015 Mar 18 08:18:09 DC-5548-01 %ETH_PORT_CHANNEL-5-PORT_UP: port-channel2: Ethe
rnet1/32 is up
2015 Mar 18 08:18:09 DC-5548-01 %ETH_PORT_CHANNEL-5-FOP_CHANGED: port-channel2:
first operational port changed from none to Ethernet1/32
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-IF_UP: Interface Ethernet1/32 is up i
n mode trunk
2015 Mar 18 08:18:09 DC-5548-01 %ETHPORT-5-IF_UP: Interface port-channel2 is up
in mode trunk
My 6509 does not show anything. Now when I do a show etherchannel summary on the 6509, the protocol is lacp.

Fabric Port Channel

Hello,
Once in production, when adding cables in a Fabric PortChannel between an IOM and a FI, ¿is it needed to re-ack the chassis? (so that, we'll have downtime of the whole chassis). Or rather, as it is a Port-Channel the cables are detected automatically, so that it is not needed to re-ack, and so there's no downtime at all...which one is the correct statement?
Thanks,

Hello,
Let us consider following scenario on adding or removing links to existing deployment.
Initial deployment
UCSM 2.0, FI 62XX ,2208 IOM and 2 physical links with port channel configuration ( 2 link discovery policy )
Change
1) If additional links are added and if they need to be utilized and part of port channel, we need to re-ack the chassis.
2) If a link goes down,traffic is distributed across other links in port channel and does not require re-ack. Parameters like bandwidth, VIF ports that are calculated based on initial configuration remains the same.
3) If we physically remove the additional links between IOM / FI, re-acknowledment would create port-channel with original two links.Failure to re-ack will create over subscription ( bandwidth, available VIF ports ) of the network links.Re-ack is not mandatory but it creates appropriate configuration that matches required design criteria.
Caution
Adding or removing links from a fabric port channel is disruptive and may affect the available amount of VIF namespace.
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_0101.html#concept_5D3D88341BFB43468B62B5A77876C67B
Padma

Cisco MDS port channel with USC FI

Similar Messages

Maybe you are looking for