FC Port Channel, Storage Cloud???

Hi. Cisco gurus:
May I have the authoritative answers on the following?
1. What is the Use Case of FC Port Channel under SAN Cloud assuming I have the typical Cisco VSAN setup-1 VSAN tied to 1 SAN Switch and 1 FCoE VLAN and another VSAN with diff. VSAN and FCoE ids, etc?
1.1 What is the commands needed in MDS switch to match the FC Port Channel in UCS so as to make it works, so to speak.
1.2 Will it make any differences between the End-Host Mode and Switch Mode?
2.
What is the benefits of FC Port Channels? Is it REALLY necessary at all assuming the same as 1 above with 2 Uplink FC Per Fabric Interconnect?
3.
What is the Use Case of Storage Cloud? Is it ONLY for direct-attached FC storage to our Fabric Interconnect?
Thank again. Help me to help Cisco to sell more UCS.
SiM

Sim, assuming you aren't using pin groups UCS will automatically re-pin the server vNIC/vHBA in the evnet of a LAN/SAN uplink failure. This re-pinning will take a few seconds but that isn't enough that you would notice the down time.
With a port channel no re-pinning has to happen as there is only a single logical uplink. When physical connection in a port channels fails there is a sub-second convergence time.
Port channels offer better band-width utilization because all servers are pinned to a single logical uplink.
If you do not have MDS FC switches then you can't create a SAN port channel. For non-MDS environments with 2 or more FC uplinks UCS will perform dynamic pinning of server vHBAs to those uplinks in a round-robin fashion. If one of the uplinks fails UCS will re-pin those vHBAs to another uplink.
Most of our UCS customers don't need VSAN trunking as they ony have 1 VSAN northbound from each fabric but if you did have more the one VSAN on your fabric then you could provision a vHBA to be in that VSAN. For example lets say you had 2 storay arrays on each SAN fabric and each was in its own VSAN. You could create vHBAs in the different VSANs so that you could build a server that has access to LUNs in either array.

Similar Messages

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 Best Practice

Hi All,
I have a MDS9509 with port channels going to my Cisco blade switches on my HP Proliant blade enclosure.
I have NO ports left on my MDS9509, but DO have some remaining on the blade enclosure.
The question is, can i port channel from the blade enclosure to another edge switch (MDS9148)?
Is that a supported configuration/Best Practice and what are the ramifications if I do that?
So I'm going from Core, to edge and then to edge switch with port channel.
Thanks,
Matt

Hi Matthew,
Sorry for the misunderstanding, your to-be diagram cleared up a lot for me :-)
First off, yes, it will work. There's no reason it shouldn't and if you have the external ports free on your 9124e, you can hook up a new switch.
It's far from a conventional design, because blade switches are supposed to go in the Edge. It's not a best practice.
What I would recommend is that you move some of the storage from your edge to the 9148, and treat it as a collapsed core, sharing an edge switch (the blade switch). You can then ISL the 9148 and the 9509 together into a somewhat sensible topology.
So for one fabric this would be
(disk)---9148 --- 9509 -- (disks) (some moved to the left to free up space for ISLs)
9124e
Or you can contact your sales team and look to swap some Linecards with higher port density ones.
Lastly I would like to note that, however you link up the switches, most combinations available to you will 'work'. So as a temp solution you can go ahead with the (core - blade - edge) scenario. Just know that you'll be introducing bottlenecks and potential weak points into your network.

What can be the max difference in cable lengths that we can have between the ISLs in a port-channel between MDS switches?

Hello All
What can be the max difference in cable lengths that we can have between the ISLs in a port-channel between MDS switches? Do we have any documentation?
Thanks
Chetan

competitive solution instead recommends a distance variance of 30 meters or less among ISLs within a trunk. If the distance variance is greater than 30 meters, undesired and degraded performance will occur. For example, if a trunk has a distance of 100 kilometers, the competitive trunking solution allows a cable length variance of only 0.03 percent!
ref;
http://www.cisco.com/c/en/us/products/collateral/storage-networking/mds-9500-series-multilayer-directors/white_paper_c11-534878.html
hth
regards
inayath
**********PLZ dont forget to rate if this info is helpfull.

Change defaut port for personal cloud

Hey, i own 3 iomega nas for a long time and never been able to use the personal cloud.
What happens is my ISP blocks the defauts ports used by iomega for personal cloud, 80 and 443.
I have already changed my ISP and looks like here in brazil the lowers ports are all blocked. Port 50500 or midia is fine.
How can i change the defaut ports, to use for example 8080 and 4430?
I also need to change ports because if i want to use all 3 personal cloud it wont work if they using all same ports.

Hello rjcarlantonio
I unfortunately do not have a way for you to modify the http/https ports for personal cloud on these devices.
You can however change the 50500 (basic remote storage manager access) port to another port in the 50500-50599 range. I can't say for certain if this will work well for 3 devices trying to host clouds on the same internet connection as personal cloud was not designed for that.
LenovoEMC Contact Information is region specific. Please select the correct link then access the Contact Us at the top right:
US and Canada: https://lenovo-na-en.custhelp.com/
Latin America and Mexico: https://lenovo-la-es.custhelp.com/
EU: https://lenovo-eu-en.custhelp.com/
India/Asia Pacific: https://lenovo-ap-en.custhelp.com/
http://support.lenovoemc.com/

Xconnect 20Gb Port-channel over MPLS Possible?

Can anybody confirm if you can establish an Xconnect between two 20Gb port-channels (2x 10Gig bundle). The core is 40Gig and running MPLS. We have many gigabit pseudowires running over it already.
Our intention is to terminate 10Gig server traffic on 4900M's and then have a 20Gb Port channel trunk link into a 6500 (which is part of the MPLS cloud). We would then issue the xconnect directly on the 20Gig port channel in order to traverse the MPLS Core.
Has anyone configured this before? Are there any caveats to watch out for? What sort of performance hit (if any does) xconnect functionality have on 10Gig Traffic.

Hi,
Yes it's supported but test it first (as always ;-) )
HTH
Laurent.

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.

PIN GROUP, Port Channel

Hi, Cisco Gurus:
Need your authoritative take on the following: Ethernet and FC is all End-Host Mode.
1. If client is using FC Port Channel on all of the FC Uplinks for the 2 Fabric Interconnects with a SINGLE VSAN on each FI, MUST THEY USE SAN PIN GROUP? Currently, they are pinning the vHBA template to this SAN Pin Group. vHBA-Fabric A pins to FC-PIN-GROUP-A and vice-versa,
2.
If FC Port Channel is being used as in 1, from WHICH UCSM option should the VSAN be created?
Should VSAN be STILL created under the Individual Fabric A and B as before?
Or
It have to be Global VSAN or Dual VSAN outside the Fabric A or Fabric B?
3.If client is using Ethernet Port Channel for each Fabric Interconnet or each fabric, must they use LAN PIN GROUP?
Currently, they are pinning the vNIC template to this Pin Group (Fabric A & B). vNICA-Fabric A pins to LAN-PIN-GROUP-A and vice-versa.
Something which I have SELDOM SEE before.
As usual, I know it is easy meat for Cisco gurus. Thanks, PAL.
So Long.
SiM

All VSANs in the screenshot above are Global. Notice they're not created under the Fabric A/ B section.
Unlike "VLANs", which are almost always Global and normally accessible from each Fabric Interconnect, VSANs are different. Best practice for storage has keeping each SAN Fabric separate. Keeping this in mind, does it make more sense to create VSANs as global or under their respective Fabric interconnects? (Under the separate Fabric Inteconnects of course. The only use case for using Global VSANs is as Craig pointed out - when there is a single Storage switch northbound that both Fabric Interconnects uplink to.
Where this gets confusing is when you're assigning vHBA's to a VSAN.
Ex.
Let's say, as your customer has done, they've created their two VSAN 10 and 20 as "Global". For comparison sake I've also created VSAN 100 just under Fabric-A and VSAN 200 just under Fabric-B. Their VSANs would looks like:
Now, when creating an vHBA under your service profile, you need to assign it to a VSAN. Take a look:
So depending which Fabric (A/B) they want the vHBA connected to the options will change. You can see that by creating the VSANs 10 and 20 as "Global" they appear when either Fabric is selected - Conversly you can see the two 100 and 200 I created under each Fabric, only appear when that fabric is selected.
So what? Well if your upstream SAN switches only use one of the respective VSANs configured and only connect to one Fabric Interconnect, then you can potentially "blackhole" your storage traffic by assigning it to the wrong Fabric Interconnect. Creating the VSANs only under the appropriate Fabric Interconnect prevents this possibility.
SAN Port-Channels have no bearing on this. All a SAN Port Channel does is make mulitple FC Uplinks appear as one - which requires SAN Port Channels configured upstream also. Leaving the FC Uplinks as individual just lets UCS dynamically pin virtual interfaces across the FC uplinks in a round-robin fashion.
In your case you have no need for Pin-Groups either. As Jeremy pointed out, unless you have a specific need for them, it's safer to not use them.
Regards,
Robert

Port-channel / Trunking / VSAN

Hi all,
I have a quick question...
I enabled trunking for all vsans and created a port-channel. I want to use this port-channel for all my vsans.
Does it matter in which vsan I add my port-channel?
If it doesn't matter why can I assign a port-channel to a vsan?
Cheers,
Mike

Mike,
It should be the same configuration on both sides for the port-channel to come up. The reason why you can assign a port-channel to a VSAN is that if you are using an E port then it depends on the matching port-channel VSAN to come up.
TE Port functionality is specific to MDS for enhanced ISL capabilities. E ports can be used for non-cisco switches to make the trunk work seamlessly as an E port.
You can refer to the following for more info:
http://www/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_4_x/trnk.html
http://www/en/US/docs/storage/san_switches/mds9000/sw/rel_3_x/configuration/guides/cli_3_4_x/pc.html
Hope this helps.
- Nikhil

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.

Right way of configuring higher MTU over a Port Channel

Hi guys,
I have a running critical Port-Channel between two locations.
Here's the config
SW1:
interface Port-channel2
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
end
interface GigabitEthernet1/45
switchport trunk encapsulation dot1q
switchport mode trunk
channel-protocol lacp
channel-group 2 mode active
end
interface GigabitEthernet1/46
switchport trunk encapsulation dot1q
switchport mode trunk
channel-protocol lacp
channel-group 2 mode active
end
SW2
interface GigabitEthernet1/1
switchport trunk encapsulation dot1q
switchport mode trunk
channel-protocol lacp
channel-group 2 mode passive
end
interface GigabitEthernet1/2
switchport trunk encapsulation dot1q
switchport mode trunk
channel-protocol lacp
channel-group 2 mode passive
end
interface Port-channel2
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
end
Now I need to increase the MTU from default value to 9198. What the right way to do it and avoid any connectivity loss, PortChannel restart.
Does it matter what switch I start first?
Thanks!
L.E. both SW are WS-C4948

Hi,
Because you are using layer 2 interfaces - there is no fragmentation support at layer 2, and interfaces receiving frames which have an unsupported size will be dropped.
I think the best way for you to proceed is to lab this up; and verify what happens - it may be that you need to make changes on switches at either end of the channel within a very short time frame to prevent too large an outage.
When you are ready to maike your change - think the best way to do this is to use the interface range command, and apply the 'mtu' command to all the interfaces in this range. I don't think it matters which switch you apply this change to first, and I don't believe if you are hinting at the 802.3ad (controlled by system-priority) decision maker, that it makes any difference.
HTH
Mike

Disappointed: ASA 8.4 Redundant using Port-channels

So I finally got all our ASAs upgrade to version 8.4 and was all sorts of excited to configure port-channels to our 6500 + SUP7203B switches. I was severally disappointed to discover that I cannot configure two port-channels and have them be members of a redundant interface pair. It would seem like a logical topology.
Port-channel1 = Gig0/0 & Gig0/1
Port-channel2 = Gig0/2 & Gig0/3
Redundant1 = Port-channel1 & Port-channel2
Port-channel1 would connect to the primary 6500
Port-channel2 would connect to the backup 6500
What would it take to make this work? Am I going to have to wait for 8.5? Will we finally get BGP then too? (Had to get that in there)
http://www.cisco.com/en/US/docs/security/asa/asa84/configuration/guide/interface_start.html#wp1329357
EtherChannel Guidelines
•You can configure up to 48 EtherChannels.
•Each channel group can have eight active interfaces. Note that you can assign up to 16 interfaces to a channel group. While only eight interfaces can be active, the remaining interfaces can act as standby links in case of interface failure.
•All interfaces in the channel group must be the same type and speed. The first interface added to the channel group determines the correct type and speed.
•The device to which you connect the ASA 5500 EtherChannel must also support 802.3ad EtherChannels; for example, you can connect to the Catalyst 6500 switch.
•All ASA configuration refers to the logical EtherChannel interface instead of the member physical interfaces.
•You cannot use a redundant interface as part of an EtherChannel, nor can you use an EtherChannel as part of a redundant interface. You cannot use the same physical interfaces in a redundant interface and an EtherChannel interface. You can, however, configure both types on the ASA if they do not use the same physical interfaces.

Hello Yaplej,
Agree with you but unfortunetly this is not supported yet,
We migh need to wait some time before this desing can be accomplish,
Regards,
If you do not have any other question please mark the question as answered

ASA 5585 port-channels

I want to create a port-channel with 2 10Gbs interfaces on 2 ASA 5585 firewalls, and set them up in a failover pair.
In order to do this, do I simply put two 10Gbs interfaces into a channel and then configure the IP addressing and failover address on the logical port-channel interface? (aka interface po1).
Any limitations with this?

Yes, that is exactly what you do..
Create portchannel on switch and ASA
Trunk the vlan on switch side
Create logical interfaces on ASA

Port-channel question on 9148

hey I have a question about port-channel.
we have a port-channel 10 which contains 4 interfaces as below.
my question is how the port-channel associated with the servers? I mean the output "sh flogi database" as below........
do we need to add port-channel as a zone member ? I think the answer is no since I don;t see the port-channel as a zone member....
=================================================================
tormds01# sh interface port-channel 10
port-channel 10 is up
    Hardware is Fibre Channel
    Port WWN is 24:0a:54:7f:ee:a0:d5:48
    Admin port mode is auto, trunk mode is on
    snmp link state traps are enabled
    Port mode is F
    Port vsan is 510
    Speed is 32 Gbps
    5 minutes input rate 124316072 bits/sec, 15539509 bytes/sec, 9919 frames/sec
    5 minutes output rate 2205921104 bits/sec, 275740138 bytes/sec, 141424 frames/sec
      43540499847 frames input, 70772376296224 bytes
        0 discards, 0 errors
        0 CRC, 0 unknown class
        0 too long, 0 too short
      237450525827 frames output, 442040501099476 bytes
        0 discards, 0 errors
      0 input OLS, 0 LRR, 0 NOS, 0 loop inits
      0 output OLS, 0 LRR, 0 NOS, 0 loop inits
    Member[1] : fc1/1
    Member[2] : fc1/5
    Member[3] : fc1/9
    Member[4] : fc1/13
    Interface last changed at Tue Apr 8 22:16:49 2014
tormds01# sh flogi database
INTERFACE        VSAN    FCID           PORT NAME               NODE NAME
fc1/3            510   0x860000 50:06:01:64:3d:e0:24:d0 50:06:01:60:bd:e0:24:d0
                           [torvnx01_spa0]
fc1/7            510   0x860100 50:06:01:6c:3d:e0:24:d0 50:06:01:60:bd:e0:24:d0
                           [torvnx01_spb0]
fc1/11           510   0x860200 50:06:01:60:3d:e0:24:d0 50:06:01:60:bd:e0:24:d0
                           [torvnx01_spa2]
fc1/15           510   0x860300 50:06:01:68:3d:e0:24:d0 50:06:01:60:bd:e0:24:d0
                           [torvnx01_spb2]
port-channel 10 510   0x860400 24:0a:54:7f:ee:92:3e:80 21:fe:54:7f:ee:92:3e:81
port-channel 10 510   0x860401 20:01:04:25:b5:3a:00:8f 20:01:00:25:b5:30:00:8f
                           [mcvhes0101hba0]
port-channel 10 510   0x860402 20:01:04:25:b5:3a:00:9f 20:01:00:25:b5:30:00:9f
                           [mcvhes0102hba0]
port-channel 10 510   0x860404 20:01:04:25:b5:3a:00:6f 20:01:00:25:b5:30:00:6f
                           [mcvhes0103hba0]
port-channel 10 510   0x860408 20:01:04:25:b5:3a:00:7f 20:01:00:25:b5:30:00:7f
                           [mcvhes0104hba0]
port-channel 10 510   0x86040f 20:01:04:25:b5:3a:00:4f 20:01:00:25:b5:30:00:4f
                           [mcvhes0105hba0]
port-channel 10 510   0x860410 20:01:04:25:b5:3a:00:5f 20:01:00:25:b5:30:00:5f
                           [mcvhes0106hba0]
port-channel 10 510   0x860417 20:01:04:25:b5:3a:00:2f 20:01:00:25:b5:30:00:2f
                           [mcvhes0107hba0]
port-channel 10 510   0x860418 20:01:04:25:b5:3a:00:0f 20:01:00:25:b5:30:00:0f
                           [mcvhes0109hba0]
port-channel 10 510   0x86041b 20:01:04:25:b5:3a:00:bf 20:01:00:25:b5:30:01:bf
                           [mcvhes0110hba0]
port-channel 10 510   0x86041d 20:01:04:25:b5:3a:00:1f 20:01:00:25:b5:30:00:1f
                           [mcvhes0111hba0]
port-channel 10 510   0x86041e 20:01:04:25:b5:3a:00:3f 20:01:00:25:b5:30:00:3f
                           [mcvhes0108hba0]
port-channel 10 510   0x86041f 20:01:04:25:b5:3a:00:ff 20:01:00:25:b5:30:01:ff
                           [mcvhes0112hba0]
port-channel 10 510   0x860423 20:01:04:25:b5:3a:00:df 20:01:00:25:b5:30:01:df
                           [mcvhes0113hba0]
port-channel 10 510   0x860425 20:01:04:25:b5:3a:00:ef 20:01:00:25:b5:30:01:ef
                           [mcvhes0114hba0]
port-channel 10 510   0x860426 20:01:04:25:b5:3a:00:cf 20:01:00:25:b5:30:01:cf
                           [mcvhes0115hba0]
port-channel 10 510   0x860427 20:01:04:25:b5:3a:00:8e 20:01:00:25:b5:30:01:8f
                           [MCDBWS0200hba0]
port-channel 10 510   0x860429 20:01:04:25:b5:3a:00:9e 20:01:00:25:b5:30:01:9f
                           [MCDBWS0201hba0]
port-channel 10 510   0x86042a 20:01:04:25:b5:3a:00:7e 20:01:00:25:b5:30:01:7f
                           [mcvhes0118hba0]
port-channel 10 510   0x86042b 20:01:04:25:b5:3a:00:af 20:01:00:25:b5:30:01:af
                           [mcvhes0116hba0]
port-channel 10 510   0x86042c 20:01:04:25:b5:3a:00:6e 20:01:00:25:b5:30:01:6f
                           [mcvhes0117hba0]
port-channel 10 510   0x86042d 20:01:04:25:b5:3a:00:4e 20:01:00:25:b5:30:01:4f
                           [mcvhes0119hba0]
port-channel 10 510   0x86042e 20:01:04:25:b5:3a:00:5e 20:01:00:25:b5:30:01:5f
                           [mcvhes0120hba0]
port-channel 10 510   0x860431 20:01:04:25:b5:3a:00:2e 20:01:00:25:b5:30:01:2f
                           [awotorprodsql01hba0]
port-channel 10 510   0x860432 20:01:04:25:b5:3a:00:3e 20:01:00:25:b5:30:01:3f
                           [awotorprodsql02hba0]
port-channel 10 510   0x860435 20:01:04:25:b5:3a:00:fe 20:01:00:25:b5:30:00:ef
                           [dbcactv01n3hba0]
port-channel 10 510   0x860436 20:01:04:25:b5:3a:00:de 20:01:00:25:b5:30:00:bf
                           [dbcactv01n4hba0]
port-channel 10 510   0x860439 20:01:04:25:b5:3a:00:ce 20:01:00:25:b5:30:00:8e
                           [mcvhes0123hba0]
port-channel 10 510   0x86043a 20:01:04:25:b5:3a:00:be 20:01:00:25:b5:30:00:af
                           [mcvhes0122hba0]
port-channel 10 510   0x86043c 20:01:04:25:b5:3a:00:ae 20:01:00:25:b5:30:00:9e
                           [mcvhes0124hba0]
port-channel 10 510   0x860443 20:01:04:25:b5:3a:00:8d 20:01:00:25:b5:30:00:6e
                           [mcvhes0125hba0]
port-channel 10 510   0x860445 20:01:04:25:b5:3a:00:ee 20:01:00:25:b5:30:00:cf
                           [mcvhes0121hba0]
port-channel 10 510   0x860446 20:01:04:25:b5:3a:00:9d 20:01:00:25:b5:30:00:7e
                           [mcvhes0126hba0]
port-channel 10 510   0x860447 20:01:04:25:b5:3a:00:6d 20:01:00:25:b5:30:00:4e
                           [mcvhes0127hba0]
port-channel 10 510   0x860449 20:01:04:25:b5:3a:00:7d 20:01:00:25:b5:30:00:5e
                           [mcvhes0128hba0]

I think what you do is F-Port trunking channeling !
port-channel as a zone member ? I assume you will do pwwn based zoning; in which case the answer is NO !

FC Port Channel, Storage Cloud???

Similar Messages

Maybe you are looking for