FCoE Port Channels on Single Nexus 5K - possible?
I'm looking for information regarding FCoE on a single Nexus 5548. I'm trying to set up a port channel from a Netapp filer's CNA adapters (2 twinax cables). I was told that for some reason port channels do not work on a single Nexus 5K design (i.e. no vPC), but I didn't know if that meant simply without the use of LACP. I've configured it in both fashions, and it seems that the VFCs do not want to come up, meaning that my filers cannot log in to the SAN. This behavior is what was described to me as what would happen if I tried doing a port channel in this way - basically I've bound the VFCs to the port channels, and since the port channels are composed of ports on the same switch, it just doesn't work. Seems odd that this would bet the case, though it would normally force me to simply buy a second N5K (sneaky sneaky).
Any tips?
That's not my issue. I'm using only one Nexus 5K, meaning that if I want to have a port channel running between the 5K and the Netapp filers, I have to bind the virtual fibre channel interfaces to that port channel. I believe that in doing so, when there are more than one links as a member of that port channel, the VFCs simply go down by design and will not come up. For some reason VFCs require to be bound to a single physical interface, whether that interfaces is a single phyiscal port or a port channel that's only configured to have one port in it.
Either way, I had to configure the Netapp side to be active/passive. I've bound the VFCs to each port (total of 4, so 4 VFCs as well). No port channels are being used on the Nexus side. This is not ideal but it works.
I would still like to see some documentation regarding the behavior of the VFCs when presented with multiple links in this way. Has anyone seen any documentation regarding this?
Similar Messages
-
FEX-2232 FCoE Port channel limitation
Hi all,
i havea single FEX 2232 single homed to nexus 5020 via port-channel. at the FEX 2232, i connected a server which have 2 X CNA and running two vlans: vlan 200 for ethernet and vlan 300 for FCoE.
i connected the server to the single fex via port-channel and allowed vlan 200 & 300. at the N5K i bounded single vfc interface to this port-channel.
when i am issuing the show flogi database i see only single PWWN.
as i understand, a single vfc interface can only see single PWWN, is this correct ?
if it does, how can i have my setup running in a way that ethernet traffic will used port-channel and for fcoe traffic i will see two PWWN ?
please advise,
Avi.It is not necessary to create another FCoE Vlan if the logins are coming on the same n5k. If there is a requirement for multiple fcoe logins on the same n5k, then it will need to be single link port channels instead of multiple links in the port channel. That way we acquire the ability to bind each physical port via port-channel into a separate vfc. In your case ideally you can have two n5ks with two n2232s single homed to each n5k and the server dual homed with 1 port each connected to two separate 2232s in active-active teaming. That way you can bind the physical interfaces into single virtual port channel on the respective n5ks. at that point, you can separate the san traffic into different vsan/vlan and make sure you dont trunk the fcoe vlan over the vpc peer link.
Hope this helps, Vinayak. -
Maximum number of interfaces in Port Channel on Nexus 5596
Let me preface this by saying I am not a network expert....
I noticed that our customer had configured a port channel on their Nexus 5596 comprised of 16 interfaces. I thought the maximum number of interfaces in a port channel was 8 interfaces? I see in the Nexus 7000 documentation that if you configure 16 interfaces, the remaining 8 will be in "hot standby." Is this the same behavior on the Nexus 5000 series?
Thank you.Same behavior on the 5500 series and other Cisco switches like 3750, 3850 , etc..
HTH -
I want to create a port channel on my nexus switch which will be connected to my server.
will someone please share with me the configuration for the same ?Hi,
From server side create LACP port-channel and same from switch end.
Nexus-SW
=======
interface Ethernet1/1-2
description [connection to SRV-01]
switchport
switchport access vlan 10
channel-group 20 mode active
no shutdown
interface port-channel20
description [connection to SRV-01]
switchport
vpc 20
switchport access vlan 10 -
Interface port-channel btw N2K and Brocade VDX
Dear all,
I tried to configure a port-channel between a nexus 2K (2FEX) and a brocade VDX (VDX6710).
As you seen below, my configuration :
N2K
Po10
switchport access vlan 200
Eth101/1/6
switchport access vlan 200
channel-group 10 mode active (used LACP)
Eth102/1/6
switchport access vlan 200
channel-group 10 mode active (used LACP)
VDX
interface Port-channel 27
vlag ignore-split
speed 1000
switchport
switchport mode access
switchport access vlan 200
spanning-tree shutdown
no shutdown
interface GigabitEthernet 21/0/31
channel-group 27 mode active type standard
lacp timeout long
no shutdown
interface GigabitEthernet 22/0/31
channel-group 27 mode active type standard
lacp timeout long
no shutdown
Unfortunately, we can't up the link for interfaces and so the port-channel.
We have the next message from the N5K for FEX :
%ETHPORT-5-IF_ADMIN_UP: Interface Ethernet101/1/6 is admin up .
%ETHPORT-5-SPEED: Interface Ethernet101/1/6, operational speed changed to 1 Gbps
%ETHPORT-5-IF_DUPLEX: Interface Ethernet101/1/6, operational duplex mode changed to Full
%ETHPORT-5-IF_RX_FLOW_CONTROL: Interface Ethernet101/1/6, operational Receive Flow Control state changed to off
%ETHPORT-5-IF_TX_FLOW_CONTROL: Interface Ethernet101/1/6, operational Transmit Flow Control state changed to on
%ETHPORT-5-IF_UP: Interface Ethernet101/1/6 is up in mode access
%ETHPORT-5-IF_DOWN_NONE: Interface Ethernet101/1/6 is down (None)
%ETHPORT-5-IF_DOWN_ERROR_DISABLED: Interface Ethernet101/1/6 is down (Error disabled. Reason:BPDUGuard)
Any idea about the configuration ?
Thanks for your help.
MatthieuFexes are really made to connect hosts and not switches . So the ports should not see bpdu's so bpduguard is err-disabling the ports.
Spanning Tree Protocol
HIFs go down with the BPDUGuard errDisable message
HIFs go down accompanied with the message, BPDUGuard errDisable.
Possible Cause
By default, the HIFs are in STP edge mode with the BPDU guard enabled. This means that the HIFs are supposed to be connected to hosts or non-switching devices. If they are connected to a non-host device/switch that is sending BPDUs, the HIFs become error-disabled upon receiving a BPDU.
Solution
Enable the BPDU filter on the HIF and on the peer connecting device. With the filter enabled, the HIFs do not send or receive any BPDUs. Use the following commands to confirm the details of the STP port state for the port: -
About n1000v with port channel
there is a n1000v connected to multiple upstream switches in the customer's production environment.
the following is from the Cisco Nexus 1000V Interface Configuration Guide, Release4.2(1)SV2(2.1).
You use vPC-HM mode to create a port channel when the switch is connected to multiple upstream switches
that are not clustered.
my question is,
can I use LACP with multiple upstream switches that are not clustered?
can I use LACP with multiple upstream switches that are stacked?
if I stack multiple upstream switches,does it mean clustered?
thanks.Hi,
See some of the guidelines:
Guidelines and Limitations
Port channeling has the following guidelines and restrictions:
•All ports in the port channel must be in the same Cisco Nexus 1000V module; you cannot configure port channels across Cisco Nexus 1000V modules.
•Port channels can be formed with multiple upstream links only when they satisfy the compatibility requirements and under the following conditions:
–The uplinks from the host are going to the same upstream switch.
–The uplinks from the host going to multiple upstream switches are configured with vPC-HM.
•You can configure multiple port channels on a device.
•After you configure a port channel, the configuration that you apply to the port channel interface affects the port channel member ports. The configuration that you apply to the member ports affects only the member port where you apply the configuration.
•You must remove the port security information from a port before you can add that port to a port channel. Similarly, you cannot apply the port security configuration to a port that is a member of a channel group.
•You can configure ports that belong to a port channel group as PVLAN ports.
•Any configuration changes that you apply to the port channel is applied to every member interface of that port channel.
•Channel member ports cannot be a source or destination SPAN port.
That said LACP should work on switches that are not clustered and meet the conditions above.
A stack is treated as one unit which means that would be like you have just one big chassis.
Stacking does not the same as clustering it works different. so if you stack them that would be a stack not a cluster
http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_4/interface/configuration/guide/n1000v_if_5portchannel.html#wp1270746
Hope this helps. -
We have two Cisco ASA 55XX Firewalls and both are in HA (Active/Standy). Two ports from each Firewall is connecting two ports of Nexus 5K Switch and running port channel between Firewall & Nexus Switch and port-channel is UP. And Switches having back to back connection with allowed all VLAN trunk port.
FW01 ----------------- SW01 (Two ports with Port channel)
FW02 ----------------- SW02 (Two ports with Port channel)
I have VLAN 10 with IP Subnet 10.10.10.0/28
SW01 : 10.10.10.2
SW02 : 10.10.10.3
HSRP IP : 10.10.10.1
FWs : 10.10.10.4 & 10.10.10.5
Firewall Default Gateway : 10.10.10.1
Problem : I am not able Ping Firewall IPs from Nexus Switches. When I checked ARP table in Nexus Switch; I have observed that Firealls two IPs having same MAC address; when I checked that MAC address in the Firewall; that MAC address is Port channel interface MAC address.
This is issue (two IPs learing same MAC address) from ASA.
How to fix this issue ?
Thanks
VenkatHi,
What version of IOS are you running on the ASAs?
see table-12-3 in this link:
http://www.cisco.com/c/en/us/td/docs/security/asa/asa84/configuration/guide/asa_84_cli_config/interface_start.html
Also, since the 4500x are in VSS mode, you need to bundle one link from each switch and use LACP.
HTH -
Hi,
I'm still new to the Cisco nexus environment. I need help on how to configure 10gb FC Port-Channel between Cisco Nexus 5548UP switch and the 6513 catalyst switch.
Please help.
Regards,Hi,
Sorry for late response...
Its 10Gb ethernet between Nexus 5548 and 6513 Catalyst switch.
I have already done the configuration but still need to be tested,
kindly see the configurations below and correct me if i am wrong.
Nexus 5548:
Switch(config)#interface port-channel 60
Switch(config-if)#description Link-to-6513_CatalystSW
Switch(config-if)#switchport mode trunk
Switch(config-if)#no shut
Switch(config)#feature lacp
Switch(config)#interface eth1/3-4
Switch(config-if)#description Link-to-6513_CatalystSW
Switch(config-if)#switchport mode trunk
Switch(config-if)#channel-group 60 mode active
Switch(config-if)#no shut
The cables are currently disconnected on both switch interfaces uplinks, will connect them when i test the configs
Catalyst 6513:
Switch(config)#interface port-channel 60
Switch(config-if)#description Link-to-Nexus_EMC_VNX
Switch(config-if)#switchport trunk encapsulation dot1q
Switch(config-if)#switchport mode trunk
Switch(config-if)#switchport nonegotiable
Switch(config-if)#no shut
Switch(config)interface range TenGigabitEthernet 6/6-7
Switch(config-if)#description Link-to-Nexus_EMC_VNX
Switch(config-if)#switchport trunk encapsulation dot1q
Switch(config-if)#switchport mode trunk
Switch(config-if)#switchport nonegotiable
Switch(config-if)#channel-protocol lacp
Switch(config-if)#channel-group 60 mode desirable
Switch(config-if)#no shut
Waiting for your response.
Regards,
Selby -
Single Nexus 5548UP- FCoE configuration with multiple server ports
Hello Everyone,
I am new to Networking so please bear with me.
Here is some background information. We have a SINGLE Nexus 5548 UP switch to which we are connecting both the storage and the UCS C240 M3 servers (with CNA). Both the storage and server has 2 ports each going to this nexus switch.
We want to implement FCoE with this solution.
Below are the steps (for server ports) that I have followed to configure the nexus. But the port not logging into the SAN (no flogi) with the config.
Enable Features
config t
feature lacp
feature dot1x
feature interface-vlan
feature sshServer
feature npiv
end
Confgure Ethernet Ports - Server
configure
interface ethernet 1/17
description To_UCS_rack_server_1_FCoE_port_1
switchport mode trunk
switchport trunk native vlan 6
switchport trunk allowed vlan 1,6
spanning-tree port type edge trunk
priority-flow-control mode on
no shutdown
end
configure
interface ethernet 1/18
description To_UCS_rack_server_1_FCoE_port_2
switchport mode trunk
switchport trunk native vlan 6
switchport trunk allowed vlan 1,6
spanning-tree port type edge trunk
priority-flow-control mode on
no shutdown
end
Create VLAN
configure
vlan 6
name FCOE_VLAN
fcoe vsan 6
end
Setup FCoE QOS
configure terminal
system qos
service-policy type qos input fcoe-default-in-policy
service-policy type queuing input fcoe-default-in-policy
service-policy type queuing output fcoe-default-out-policy
service-policy type network-qos fcoe-default-nq-policy
end
Create vfc for Initiators (UCS Servers)
configure
interface vfc 17
bind interface ethernet 1/17
switchport description virtual_fiber_channel_Server1_Port1
end
configure
interface vfc 18
bind interface ethernet 1/18
switchport description virtual_fiber_channel_Server1_Port2
end
Adding vFC’s to VSAN
configure
vsan database
vsan 6 interface vfc 17
vsan 6 interface vfc 18
Create Zonesets and Zones
configure
show flogi database vsan 6 ----> Do not see any pwwn here???
show fcns database vsan 6
Any help in the regard would be highly appreciated.
Cheers,
KSFixed the issue. "switchport trunk native vlan 6" was causing the issue. Maybe the storage and Servers were not configured with proper VLAN's. I removed the native vlan and everything logged in fine.
Any how I have configured a single zone with all 3 servers pWWN's. I know single initiator zoning is the way to go.
Can you please guide me if I can move these servers in their separate zones without any outages? If it helps, all severs have 2 pWWN's. The current zoneset is active with that single zone.
Please let me know if you need any additional details.
Cheers,
KS -
Nexus 6K: Port-Channel Load-Balance
Hi all,
I configured "port-channel load-balance ethernet source-dest-mac" on Nexus 6001. But when I use "show run all | in load-balance", it displays module 1 and module 2 are still using source-dest-ip for port-channel load-balance. And for command "show port-channel load-balance" and "show port-channel load-balance forwarding-path interface", it still shows switch using MAC for hash algorithm. The NXOS is 6.0(2)N1(2a).
Does anybody know:
- What is the function of "port-channel load-balance ethernet source-dest-ip module" and in which situation this command will be effective?
- It shows "port-channel load-balance ethernet source-dest-ip module" command for both module 1 and 2. Module 1 is N6K Supervisor and module 2 is 4xQSFP Ethernet Module. Is it possible to set different load-balance algorithm to these 2 modules?
# show run all | in load-balance
port-channel load-balance ethernet source-dest-mac
port-channel load-balance ethernet source-dest-ip module 1
port-channel load-balance ethernet source-dest-ip module 2
# show port-channel load-balance
Port Channel Load-Balancing Configuration:
System: source-dest-mac
Port Channel Load-Balancing Addresses Used Per-Protocol:
Non-IP: source-dest-mac
IP: source-dest-mac
# show port-channel load-balance forwarding-path interface port-channel 30 vlan 150 src-ip 172.25.228.6 dst-ip 172.25.226.97
Missing params will be substituted by 0's.
Load-balance Algorithm on switch: source-dest-mac
crc_hash: 977 Polynomial: CRC10b Outgoing port id Ethernet1/2
Param(s) used to calculate load-balance:
seed: 0x701
dst-mac: 0000.0000.0000
src-mac: 0000.0000.0000
# show module
Mod Ports Module-Type Model Status
1 48 Norcal 64 Supervisor N6K-C6001-64P-SUP active *
2 10 Nexus 4xQSFP Ethernet Module N6K-C6001-M4Q ok
Mod Sw Hw World-Wide-Name(s) (WWN)
1 6.0(2)N2(3) 1.0 --
2 6.0(2)N2(3) 1.0 --Hi all,
I configured "port-channel load-balance ethernet source-dest-mac" on Nexus 6001. But when I use "show run all | in load-balance", it displays module 1 and module 2 are still using source-dest-ip for port-channel load-balance. And for command "show port-channel load-balance" and "show port-channel load-balance forwarding-path interface", it still shows switch using MAC for hash algorithm. The NXOS is 6.0(2)N1(2a).
Does anybody know:
- What is the function of "port-channel load-balance ethernet source-dest-ip module" and in which situation this command will be effective?
- It shows "port-channel load-balance ethernet source-dest-ip module" command for both module 1 and 2. Module 1 is N6K Supervisor and module 2 is 4xQSFP Ethernet Module. Is it possible to set different load-balance algorithm to these 2 modules?
# show run all | in load-balance
port-channel load-balance ethernet source-dest-mac
port-channel load-balance ethernet source-dest-ip module 1
port-channel load-balance ethernet source-dest-ip module 2
# show port-channel load-balance
Port Channel Load-Balancing Configuration:
System: source-dest-mac
Port Channel Load-Balancing Addresses Used Per-Protocol:
Non-IP: source-dest-mac
IP: source-dest-mac
# show port-channel load-balance forwarding-path interface port-channel 30 vlan 150 src-ip 172.25.228.6 dst-ip 172.25.226.97
Missing params will be substituted by 0's.
Load-balance Algorithm on switch: source-dest-mac
crc_hash: 977 Polynomial: CRC10b Outgoing port id Ethernet1/2
Param(s) used to calculate load-balance:
seed: 0x701
dst-mac: 0000.0000.0000
src-mac: 0000.0000.0000
# show module
Mod Ports Module-Type Model Status
1 48 Norcal 64 Supervisor N6K-C6001-64P-SUP active *
2 10 Nexus 4xQSFP Ethernet Module N6K-C6001-M4Q ok
Mod Sw Hw World-Wide-Name(s) (WWN)
1 6.0(2)N2(3) 1.0 --
2 6.0(2)N2(3) 1.0 -- -
Nexus port channel load balance
Hi
I just want to clarify one setting for the port channel load balance on Nexus 6k switch. If I use the load balance option source-dest-ip-only, will following four converstions be load balanced?
10.10.10.1 -> 192.168.1.1
10.10.10.2 -> 192.168.1.1
10.10.10.1 -> 192.168.1.1
10.10.10.1 -> 192.168.1.2
Thanks. LeoHi Leo,
I think there may be typo in your question as I only see three conversations and not four. That aside I've not seen the Nexus port-channel load balancing sufficiently well documented to be able to give you the exact answer.
In their configuration guides Cisco only include the following statement:
Cisco NX-OS load balances traffic across all operational interfaces in a port channel by reducing part of the binary pattern formed from the addresses in the frame to a numerical value that selects one of the links in the channel.
There is other documentation that states the load balancing algorithm uses a CRC-8 based polynomial, but as we don't know exactly which parts of the frame are used in the calculation, I don't see it's possible to calculate the answer and so derive the link that will be used for a given conversation.
While I've not seen full documentation regarding the science used in the calculation, what Cisco have done is provide a command on the switch CLI that will allow you to determine which link of a port-channel will be used.
If you run the command show port-channel load-balance forwarding-path interface port-channel vlan src-ip dst-ip then one of the parts of the output is the member link of the port-channel that will be used for that flow.
You can find full details of the options for the show port-channel load-balance command in the command reference.
One other point to remember is that the load balancing across a port-channel is unidirectional, and the hashing might be completely different for the return flow of a conversation. For example it is entirely possible that traffic from A to B could use one link of a port-channel, while the return traffic from B to A for the same conversation could use a different link.
In general I would use the source-dest-port option for load balancing on the Nexus switches as this will obviously include the Layer-4 port numbers in the calculation, and so give you a better distribution of flows across all member links.
Regards -
Multiple vsan traffic over single port-channel
Hi -
Scenario - 2 interface uplink (port-channel - Po10 ) from NetApp FAS-A to N5548-A & B. Po10 is currently configured with vPC10 and vFC10 at N5k end. single vfc currently mapped with a single vsan (vfc10 with vsan 1011).
Q - Is it possible to make the Port-channel to pass multiple vsan (vsan 1011 & 1012). If yes, then how (over same vfc or by separate vfc on same port-channel)
SubhankarThis router’s capability is only limited and dependent on the services that your ISP has given or allowed for you to use. I think it really has to be a one is to one configuration, not only with this router because I haven’t noticed any router that has this feature so far. This is really another idea for Linksys can work on.
-
FCoE capable Storage Array connected directly to Nexus 5000 FCoE port
hi,
can someone help me verify if it is possible to connect an FCoE capable SAN storage to a Nexus 5000 FCoE port? thanks!yes, i have connected both EMC VNX and NetApp to N5Ks FCoE. EMC requires active mode twinax or fiber.
-
Nexus 6004: Question about port-profile type port-channel
I'm setting up a new deployment of Nexus 6004 switches and want to utilize port-profiles as much as possible to simplify management down the road.
All uplinks to other switches, routers and firewalls will be connected using VPC:s. On the port-channels (vpc) the only thing that will change over time is the allowed vlans.
It seems that port-profiles of the type port-channel does not behave in the same way as those with type ethernet, at least not when adding vlans.
If I modify the port-profile using "switchport trunk allowed vlan add XXX" it will delete the previous config and only retain "switchport trunk allowed vlan add XXX", and not merge it with the previous config as is expected.
Question: Is this a bug or is it working as intended?
RH_N6K4_01(config-sync)# switch-profile rh
Switch-Profile started, Profile ID is 1
RH_N6K4_01(config-sync-sp)# port-profile type port-channel FIREWALL-UPLINK
RH_N6K4_01(config-sync-port-prof)# switchport trunk allowed vlan 3
RH_N6K4_01(config-sync-port-prof)# verify
Verification Successful
RH_N6K4_01(config-sync-sp)# commit
Verification successful...
Proceeding to apply configuration. This might take a while depending on amount of configuration in buffer.
Please avoid other configuration changes during this time.
Commit Successful
RH_N6K4_01(config-sync)# show port-profile
SHOW PORT_PROFILE
port-profile FIREWALL-UPLINK
type: Port-channel
description:
status: enabled
max-ports: 512
inherit:
config attributes:
switchport mode trunk
switchport trunk allowed vlan 3
evaluated config attributes:
switchport mode trunk
switchport trunk allowed vlan 3
assigned interfaces:
===================================
RH_N6K4_01(config-sync-sp)# port-profile type port-channel FIREWALL-UPLINK
RH_N6K4_01(config-sync-port-prof)# switchport trunk allowed vlan add 84
RH_N6K4_01(config-sync-port-prof)# verify
Verification Successful
RH_N6K4_01(config-sync-sp)# commit
Verification successful...
Proceeding to apply configuration. This might take a while depending on amount of configuration in buffer.
Please avoid other configuration changes during this time.
Commit Successful
RH_N6K4_01(config-sync)# show port-profile
SHOW PORT_PROFILE
port-profile FIREWALL-UPLINK
type: Port-channel
description:
status: enabled
max-ports: 512
inherit:
config attributes:
switchport mode trunk
switchport trunk allowed vlan add 84
evaluated config attributes:
switchport mode trunk
switchport trunk allowed vlan add 84
assigned interfaces:
Expected behavior here would be "switchport trunk allowed vlan 3,84". This only occurs when using "port-profile type port-channel" not when using "port-profile type ethernet"<> is template syntax and is generally the type of object a container holds.. So it is defining that the MSGQUEUE type is a deque holding struct_buffer*'s.
-
UCS FI 6248 to Nexus 5548 San port-channel - not working
Hi all,
I'm sure I am missing something fairly obvious and stupid but I need several sets of eyes and help.
Here is the scenario:
I want to be able to create san port-channels between the FI and Nexus. I don't need to trunk yet as I can't even get the channel to come up.
UCS FI 6248:
Interfaces fc1/31-32
Nexus 5548
interfaces fc2/15-16
FI is in end-host mode and Nexus is running NPIV mode with fport-channel-trunk feature enabled.
I'm going to output the relevants configurations below.
Nexus 5548:
NX5KA(config)# show feature | include enabled
fcoe 1 enabled
fex 1 enabled
fport-channel-trunk 1 enabled
hsrp_engine 1 enabled
interface-vlan 1 enabled
lacp 1 enabled
lldp 1 enabled
npiv 1 enabled
sshServer 1 enabled
vpc 1 enabled
interface san-port-channel 133
channel mode active
no switchport trunk allowed vsan all
switchport trunk mode off
interface fc2/15
switchport trunk mode off
channel-group 133 force
no shutdown
interface fc2/16
switchport trunk mode off
channel-group 133 force
no shutdown
NX5KA# show vsan membership
vsan 1 interfaces:
fc2/13 fc2/14
vsan 133 interfaces:
fc2/15 fc2/16 san-port-channel 133
vsan 4079(evfp_isolated_vsan) interfaces:
vsan 4094(isolated_vsan) interfaces:
NX5KA# show san-port-channel summary
U-Up D-Down B-Hot-standby S-Suspended I-Individual link
summary header
Group Port- Type Protocol Member Ports
Channel
133 San-po133 FC PCP (D) FC fc2/15(D) fc2/16(D)
UCS Fabric Interconnect outputs:
UCS-FI-A-A(nxos)# show san-port-channel summary
U-Up D-Down B-Hot-standby S-Suspended I-Individual link
summary header
Group Port- Type Protocol Member Ports
Channel
133 San-po133 FC PCP (D) FC fc1/31(D) fc1/32(D)
UCS-FI-A-A(nxos)#
UCS-FI-A-A(nxos)# show run int fc1/31-32
!Command: show running-config interface fc1/31-32
!Time: Fri Dec 20 22:58:51 2013
version 5.2(3)N2(2.21b)
interface fc1/31
switchport mode NP
channel-group 133 force
no shutdown
interface fc1/32
switchport mode NP
channel-group 133 force
no shutdown
UCS-FI-A-A(nxos)#
UCS-FI-A-A(nxos)# show run int san-port-channel 133
!Command: show running-config interface san-port-channel 133
!Time: Fri Dec 20 22:59:09 2013
version 5.2(3)N2(2.21b)
interface san-port-channel 133
channel mode active
switchport mode NP!Command: show running-config interface san-port-channel 133
!Time: Sat May 16 04:59:07 2009
version 5.1(3)N1(1)
interface san-port-channel 133
channel mode active
switchport mode F
switchport trunk mode off
Changed it as you suggested...
Followed the order of operations for "no shut"
Nexus FC -> Nexus SAN-PC -> FI FC -> FI SAN-PC.
Didn't work:
NX5KA(config-if)# show san-port-channel summary
U-Up D-Down B-Hot-standby S-Suspended I-Individual link
summary header
Group Port- Type Protocol Member Ports
Channel
133 San-po133 FC PCP (D) FC fc2/15(D) fc2/16(D)
NX5KA(config-if)#
Here is the output as you requested:
NX5KA(config-if)# show int san-port-channel 133
san-port-channel 133 is down (No operational members)
Hardware is Fibre Channel
Port WWN is 24:85:00:2a:6a:5a:81:00
Admin port mode is F, trunk mode is off
snmp link state traps are enabled
Port vsan is 133
1 minute input rate 1256 bits/sec, 157 bytes/sec, 0 frames/sec
1 minute output rate 248 bits/sec, 31 bytes/sec, 0 frames/sec
3966 frames input, 615568 bytes
0 discards, 0 errors
0 CRC, 0 unknown class
0 too long, 0 too short
2956 frames output, 143624 bytes
0 discards, 0 errors
46 input OLS, 41 LRR, 73 NOS, 0 loop inits
257 output OLS, 189 LRR, 219 NOS, 0 loop inits
last clearing of "show interface" counters never
Member[1] : fc2/15
Member[2] : fc2/16
NX5KA(config-if)#
NX5KA(config-if)# show int brief
Interface Vsan Admin Admin Status SFP Oper Oper Port
Mode Trunk Mode Speed Channel
Mode (Gbps)
fc2/13 1 auto on sfpAbsent -- -- --
fc2/14 1 auto on sfpAbsent -- -- --
fc2/15 133 F off init swl -- 133
fc2/16 133 F off init swl -- 133
Maybe you are looking for
-
Runtime error in Universal Worklist in portal
Hi! An error occurs when I open the page Universal Worklist - Administration under System Administration > System Configuration > Universal Worklist & Workflow. The error message is: Portal runtime error. An exception occurred while processing your r
-
Dear All, Can anybody help me with the config guide for Letter of Credit in Export Sales. Points shall be awarded for the best resolution. Best Regards, Indrajit
-
How to disable text can be adopted from inforecord (PO text)
Hi, I have a issue in PO output, when I try to create a PO through ME21N transaction, the inforecord PO text is not printing in PO output. It is printing only when I click on the option text can be adopted from inforecord (PO text). This option is th
-
JAVA invocation interface (jar files) BouncyCastle
Hi! I am developing a C++ application which needs the use of BouncyCastle security provider. So I attach to the compilation classpath the jar bouncycastle jar file. Compilation is OK. When i try to trigger mi application jvm crashes. I think that is
-
hi all, i have bean class,JSP Dynpage and JSP.when i run the portal it shows Error occurs during the rendering of jsp component.....for second JSP...first JSP is running fine... bean class =========== public class ClassFirst { public String name