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
Similar Messages
-
Port-channel Problem between Fabric Interconnect and N7K vPC
Dear all,
I have a problem with Port-channel Uplink between Fabric Interconnect with N7K using vPC
This is my network topology for UCS Deployment
In N7K I has configured vPC for red link and green link, at Fabric Interconnect A I has configured Port-Channel with member is Port 1 and Port 2, uplink is red link. At Fabric Interconnect B, I has configured Port-Channel with member is Port 1 and Port 2, uplink is green link.
The show interface port-channel on N7K is good, every port-channel is up and have all member. But At Fabric Interconnnect, when I see on UCS Manager, the status of Port-Channel on Fabic A and Fabric B is fault with Additional Info: No operational member. Although all link is link up and I has status of Port-Channel is enable on UCS Manager. When I see the Properties of Port 1, Port 2 on Port-channel, I see the membership status is : individual. This mean port-channel is not up and no membership in this configuration. I want to using port-channel for load balance and plus more bandwidth for uplink to 20Gig. I don't understand why ?
Please help me resolve this problem, I has send the capture screen of UCS Manager when I show status of Port-channel and Port-member in port-channel in attach items.
Anyone can help me to resolve this, thanks you very much. Please reference attach items for more detail about fault.
Thanks,
Trung.Thanks Matthew very much,
I has resolved this problem. The reason of problem is miss match protocol of port-channel between N7K and Fabric Interconnect. The Fabric Interconnect always use LACP protocol, but N7K using Port-channel mode on, that why the port-channel failed. I has configured LACP for port-channel in N7K, it has resolved the problems.
Thanks,
Trung. -
Fabric Interconnect Uplink port channeling...
Hi,
We setup port channel of two 10G uplink interfaces on each Fabric Interconnect. Everything is running as expected.
However we noticed that under 'Port-Channel # (Fabric #)' setting on LAN tap, 'Admin Speed' was set to '10Gbps'.
Should we leave this configuration as is or match to the maximum bandwidth of port Channel we set up (20Gbps)?
I only see four options on each port channel configuration, 1 Gbps, 10Gbps, 20Gbps and 40Gbps so I'm not sure if we should change this setting.
Thank youHello,
You do not need to change the speed ( admin ). 20 Gbps configuration is applicable for certain server models.
-------- NXOS output -----------------
FI-A(nxos)# sh run int port-channel 1
interface port-channel1
description U: Uplink
switchport mode trunk
speed 10000
FI-A(nxos)# show int port-channel 1
port-channel1 is up
Hardware: Port-Channel, address: 547f.ee67.e0fb (bia 547f.ee67.e0fb)
Description: U: Uplink
MTU 1500 bytes, BW 20000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is trunk
full-duplex, 10 Gb/s
FI-A(nxos)# sh int bri
Port-channel VLAN Type Mode Status Reason Speed Protocol
Interface
Po1 1 eth trunk up none a-10G(D) lacp
There is cosmetic defect where we list the operational speed as 10 Gbps instead of 20Gbps
FI-A /eth-uplink/fabric # show port-channel detail
Port Channel:
Port Channel Id: 1
Name: FIA
Admin State: Enabled
Oper State: Up
Speed: 10 Gbps
Oper Speed: 10 Gbps
State Reason:
flow control policy: default
HTH
Padma -
Fabric Interconnect To MDS 9148 FC Port Channel/Trunks
Is it possible to create both a Port Channel and Trunk on a Cisco MDS 9148? Yes correct?
Or can I only trunk between the 2 MDS switches and not the MDS to Fabric Interconnect?
These FC links would be connected to a 2248XP Fabric Interconnect carrying multiple VSANs from the MDS to the Fabric Interconnect.
ThanksHello,
Yes, you can have trunk links grouped into port channel ( F port-channel trunking ) between FI and MDS.
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
Padma -
Port-channel L2 problem with Fabric Interconnect and Nexus 7010
Hi,
i using port-channel from both fabric interconnect to N7k with 3 cables per Fabric Interconnect.
but, my problem is when i creating port-channel, Fabric Interconnect don't support mode ON dan rate-mode share in Interface 10G Nexus 7010.
I was trying :
1. I using non dedicated port in Nexus 7010.
- rate-mode share
- channel-group 1 mode active
- switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was suspended
2. I using non dedicated port in Nexus 7010
- rate-mode share
- channel group 1 mode on
- switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was came up, but in Fabric interconnect was failed.
3. I using dedicated port in Nexus 7010
- rate-mode share
- channel group 1 mode active
- switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was suspended
4. I using dedicated port in Nexus 7010
- rate-mode dedicated
- channel group 1 mode active
- switchport mode trunk
when i using this option, the port-channel in Nexus 7010 was came up and running well.
but, the problem is my costumer do not want using a dedicated rate-mode. if i using dedicated mode the only available port is 8 interfaces instead of 32 ports. i want to using rate-mode share in nexus 7010.
is there any way to configuring port-channel using mode on in fabric interconnect ? i was trying using CLI to create port-channel in Fabric interconect but i cannot configure the channel group protocol.
i attach the topology of N7K with Fabric interconnect.
regards,
Berwin HHi Manish,
the issue was solved, i was fix it last week.
the solution is:
i enable the license grace-priode (since my license is Enterprise so cannot create VDC) then i create a VDC (ex: VDC 2) so i allocate the interface on all module
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin-top:0cm;
mso-para-margin-right:0cm;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0cm;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
N7K-M132XP-12 to VDC 2. after that i delete VDC 2 then all interface back to VDC 1 (default vdc). then i enable the rate-mode share in dedicated port and bundle into port-channel and its working.
i dont know why it must move to VDC first then it will working, maybe cisco can explain the reasons.
So here the result of my port-channel :
SVRN7KFARM-HO-01# show port-channel summary
Flags: D - Down P - Up in port-channel (members)
I - Individual H - Hot-standby (LACP only)
s - Suspended r - Module-removed
S - Switched R - Routed
U - Up (port-channel)
Group Port- Type Protocol Member Ports
Channel
1 Po1(SU) Eth LACP Eth1/1(P) Eth1/2(P) Eth1/3(P)
Eth1/4(P) Eth1/25(P)
2 Po2(SU) Eth LACP Eth1/9(P) Eth1/10(P) Eth1/11(P)
Eth1/12(P) Eth1/26(P)
3 Po3(SU) Eth LACP Eth1/17(P) Eth1/18(P)
4 Po4(SU) Eth NONE Eth10/32(P) Eth10/34(P) Eth10/35(P)
Eth10/36(P)
Thanks.
Berwin H -
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,
MattHi 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. -
SAN Port-Channel between Nexus 5000 and Brocade 5100
I have a Nexus 5000 running in NPV mode connected to a Brocade 5100 FC switch using two FC ports on a native FC module in the Nexus 5000. I would like to configure these two physical links as one logical link using a SAN Port-Channel/ISL-Trunk. An ISL trunking license is already installed on the Brocade 5100. The Nexus 5000 is running NX-OS 4.2(1), the Brocade 5100 Fabric OS 6.20. Does anybody know if this is a supported configuration? If so, how can this be configured on the Nexus 5000 and the Brocade 5100? Thank you in advance for any comments.
Best regards,
FlorianI tried that and I could see the status light on the ports come on but it still showed not connected.
I configured another switch (a 3560) with the same config and the same layout with the fiber and I got the connection up on it. I just cant seem to get it on the 4506, would it be something with the supervisor? Could it be wanting to use the 10gb port instead of the 1gb ports? -
FabricPath vPC port-channel err-disabled CE Vlan?
I have a pair of Nexus 56128 configured with fabric path and vpc+. The Nexus pair has UCS connected downstream using vpc port-channels. When a Vlan is in mode fabricpath, it's ok for the vpc+ peer-link and the vpc port-channel to UCS. However when I changed the vlan to classic Ethernet, it's err-diabled in the vpc port-channels.
Is this the normal behavior of fabric path domain? In other words, CE Vlans and fabric path Vlans cannot use the same Layer 2 path, correct?
If I need to transport CE Vlans and fabric path Vlans from Nexus (fabric path vpc+) to UCS, I have to use a separate non-vpc port-channel for the CE Vlans between each Nexus and UCS?
ThanksI have a pair of Nexus 56128 configured with fabric path and vpc+. The Nexus pair has UCS connected downstream using vpc port-channels. When a Vlan is in mode fabricpath, it's ok for the vpc+ peer-link and the vpc port-channel to UCS. However when I changed the vlan to classic Ethernet, it's err-diabled in the vpc port-channels.
Is this the normal behavior of fabric path domain? In other words, CE Vlans and fabric path Vlans cannot use the same Layer 2 path, correct?
If I need to transport CE Vlans and fabric path Vlans from Nexus (fabric path vpc+) to UCS, I have to use a separate non-vpc port-channel for the CE Vlans between each Nexus and UCS?
Thanks -
FC Port Channel between UCS and MDS.
Hi All,
I am new to Cisco Fabric Concepts. In my enviornment i have a F port channel(8 Port Group) created on MDS 9513 switch and this Fport
channel is connected to Cisco UCS 6296 FI. The Cisco UCS Blade servers are connected to the Fabric Interconnect .
On MDS NPIV is enabled.
Can anyone explain the below questions.
1. Why do we create an F port Channel Group and connect it to the UCS FI? Is this something similar to Brocade Edge to AG Switch Connectivity.
2. How to configure F port Channel Group in MDS . Can anyone explain with an example.
3. Do we need to make any Configuration on UCS FI ports for server connectivity and Channel port Connectivity if yes what are the steps required to
do the same.Does the WWPN shows up in the FLOGI Database if the connectivity and configuration looks good in UCS FI and MDS.
4. What happens when a VSAN on MDS switch is added to the Port Channel.
Thanks and Regards,
Santosh suryaLook at my remarks in
https://supportforums.cisco.com/discussion/12468266/fc-port-channels-between-mds-and-ucs-fi-best-practice
1. Why do we create an F port Channel Group and connect it to the UCS FI? Is this something similar to Brocade Edge to AG Switch Connectivity.
F port channel is proprietary; therefore any such F port channel between UCS FI and Brocade doesn't work.
2. How to configure F port Channel Group in MDS . Can anyone explain with an example.
see eg.
https://supportforums.cisco.com/sites/default/files/legacy/9/9/2/53299-UCS_1-4-1_F-port_channel-trunk-v1.pdf
3. Do we need to make any Configuration on UCS FI ports for server connectivity and Channel port Connectivity if yes what are the steps required to
see eg.
https://supportforums.cisco.com/sites/default/files/legacy/9/9/2/53299-UCS_1-4-1_F-port_channel-trunk-v1.pdf
Does the WWPN shows up in the FLOGI Database if the connectivity and configuration looks good in UCS FI and MDS.
flogi database is on the MDS, not FI; there are however UCS CLI commands, like "show npv ...."
4. What happens when a VSAN on MDS switch is added to the Port Channel.
If its not created on UCS, it will just not become the status "up" -
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...
ThanxTMC-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 -
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?
ThanksSimon,
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. -
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.
SiMAll 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 -
Hi, Cisco Experts:
Can I have a definitive answer to the following?
q1.
EMC mentioned that they do not support FC Port Channel & Trunking with regard to our UCS Fabric Interconnects/MDS/VNX5300?
Is that any truth in that?
We are trying a Cisco UCS solutions with MDS and EMC VNX in the mix-SAN Boot basically, ESXi 5.1 and all others.
q2.
From MDS all the ways up to EMC VNX, is there such concept too-FC Port Channel & Trunking, assuming we are doing FC Port Channel & Trunking from FInterconnect to MDS?
Please let me know.
Appreciate it.
SiMHi Sim,
We support FC port channel and trunking between UCS FI and MDS.
Is EMC saying about the port channel between the MDS and VNX? Is there any document EMC pointed out?
With respect to booting from SAN, yes, you can boot from SAN with MDS and EMC VNX as long as the OS is supported in the UCS system. You can refer to
http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html for the supported OS versions.
Hope this answers your question.
-Ganesh -
Creating san-port-channel on 6248 using CLI
I can create the san port channel using UCS manager. But I would like to know the syntax using CLI. So far I was able to figure out the following. One thing missing was moving the port channel from the default VSAN(1) to a different VSAN i.e VSAN 10 in my case. I have looked at the CLI guide, but have not found the commands syntax. Appreciate if anyone can post the syntax
### Create Port Channel ###
scope fc-uplink
scope fabric a
create port-channel 1
enable
set name port-channel-1
set adminspeed auto
commit-buffer
end
### Add interfaces to Port Channel ###
scope fc-uplink
scope fabric a
scope port-channel 1
create member-port 1 29
exit
create member-port 1 30
commit-buffer
endThanx Wdey. That's exactly what I was looking for. Here is the syntax which works for me.
scope fc-uplink
scope fabric a
create port-channel 1
enable
set name port-channel-1
set adminspeed auto
commit-buffer
end
scope fc-uplink
scope fabric a
enter port-channel 1
enable
enter member-port 1 29
enable
exit
enter member-port 1 30
enable
exit
set adminspeed auto
exit
enter vsan VSAN10 10 10
set fc-zoning disabled
set fcoe-vlan 10
set id 10
enter member-port-channel a 1
exit
localize
exit
end
commit-buffer -
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
Maybe you are looking for
-
Is there a way of using a mail merge function while on the iphone or ipad, i wish to email a "Word style, ot TXT" document to 250 of my contacts, I have tried downloading my contacts to my PC's outlook but only 1 contact comes across at a time despit
-
ChaRM Report of Corrections With Errors
We are having an issue when the Maint Cycle phase is Go-Live, if a tester performs successful testing on a Normal Correction, the status is changed to Consolidated; however, the Normal Correction gets the error "Action Cannot be Performed During this
-
Dear All my client use price standard S in purchase order(comes from material master) but when we use item category L in purchase order we want price doesn't come from material master but come from info record. please guide me best regards R.T
-
Windows Media Player & Video Streaming
Hi, there! Is it possible to send Video Streaming (using JMF) to Windows Media Player? If so, how could I do that??? Thank You very much!! Cesar
-
Move Adobe Connect 7.5 to new server hardware
What is the process for moving Adobe Connect to new server hardware. We are currently running Adobe Connect Pro 7.5 (7.5.1.0.100) on a Win2K3 SP2 server. We would like to move Connect over to new server hardware running Win2K8 R2 (64-bit). The Connec