Nexus 5548UP and UCS 6120's

I have two nexus 5548's configured as a vPC peers and two ucs 6120's configure in a cluster. The 5548's are connected to two catalyst 6500 via trunks that are in a VSS configuration. My question is, i have the ucs 6120 managment 0 ports connected to the 5k's, 6120-A mgmt0 to 5k-1 and 6120-B to 5k-2, everytime i fail the ucs 6120-A (primary) i lose ping to the cluster ip and can't manage ucs 6120-B at all even though it is pingable. Below are snippets on how the management ports are configured on the 5K's. Any Idea's?
nx5k-1
interface Ethernet1/13
description 6120-A:MGMT0
switchport mode trunk
switchport trunk native vlan 100
switchport trunk allowed vlan 100
speed 1000
channel-group 12 mode active
interface port-channel12
description 6120:A:MGMT
switchport mode trunk
vpc 12
switchport trunk native vlan 100
switchport trunk allowed vlan 100
spanning-tree port type network
speed 1000
nx5k-2
interface Ethernet1/13
description 6120-B:MGMT0
switchport mode trunk
switchport trunk native vlan 100
switchport trunk allowed vlan 100
speed 1000
channel-group 12 mode active
interface port-channel12
description 6120:B:MGMT
switchport mode trunk
vpc 12
switchport trunk native vlan 100
switchport trunk allowed vlan 100
spanning-tree port type network
speed 1000

you need to configure UCS management failover monitoring
http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/gui/config/guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_0101010.html#concept_8EFB3986365C4F69A6C3B9BBC14D16FE
Sent from Cisco Technical Support iPad App

Similar Messages

Cisco Nexus 5548UP and FI6248UP compatibility with FC SFP

Cisco Nexus 5548UP and FI 6248UP comes with Unified Ports. What are the SFP types this port can take? 1Gig, 10Gig and 2/4/8FC. Could you please clarify?
Thanks,
Cheriyan

Hi Cheriyan,
Here is te URL to the 6200 series FI data sheet:
http://www.cisco.com/en/US/prod/collateral/ps10265/ps11544/data_sheet_c78-675245.pdf
Check for the table to supported SFPs.
Same for the 5500 switches
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/data_sheet_c78-618603.html.
Hope this helps!
./Abhinav

ESXi 4.1 NIC Teaming's Load-Balancing Algorithm,Nexus 7000 and UCS

Hi, Cisco Gurus:
Please help me in answering the following questions (UCSM 1.4(xx), 2 UCS 6140XP, 2 Nexus 7000, M81KR in B200-M2, No Nexus 1000V, using VMware Distributed Switch:
Q1. For me to configure vPC on a pair of Nexus 7000, do I have to connect Ethernet Uplink from each Cisco Fabric Interconnect to the 2 Nexus 7000 in a bow-tie fashion? If I connect, say 2 10G ports from Fabric Interconnect 1 to 1 Nexus 7000 and similar connection from FInterconnect 2 to the other Nexus 7000, in this case can I still configure vPC or is it a validated design? If it is, what is the pro and con versus having 2 connections from each FInterconnect to 2 separate Nexus 7000?
Q2. If vPC is to be configured in Nexus 7000, is it COMPULSORY to configure Port Channel for the 2 Fabric Interconnects using UCSM? I believe it is not. But what is the pro and con of HAVING NO Port Channel within UCS versus HAVING Port Channel when vPC is concerned?
Q3. if vPC is to be configured in Nexus 7000, I understand there is a limitation on confining to ONLY 1 vSphere NIC Teaming's Load-Balancing Algorithm i.e. Route Based on IP Hash. Is it correct?
Again, what is the pro and con here with regard to application behaviours when Layer 2 or 3 is concerned? Or what is the BEST PRACTICES?
I would really appreciate if someone can help me clear these lingering doubts of mine.
God Bless.
SiM

Sim,
Here are my thoughts without a 1000v in place,
Q1. For me to configure vPC on a pair of Nexus 7000, do I have to connect Ethernet Uplink from each Cisco Fabric Interconnect to the 2 Nexus 7000 in a bow-tie fashion? If I connect, say 2 10G ports from Fabric Interconnect 1 to 1 Nexus 7000 and similar connection from FInterconnect 2 to the other Nexus 7000, in this case can I still configure vPC or is it a validated design? If it is, what is the pro and con versus having 2 connections from each FInterconnect to 2 separate Nexus 7000? //Yes, for vPC to UCS the best practice is to bowtie uplink to (2) 7K or 5Ks.
Q2. If vPC is to be configured in Nexus 7000, is it COMPULSORY to configure Port Channel for the 2 Fabric Interconnects using UCSM? I believe it is not. But what is the pro and con of HAVING NO Port Channel within UCS versus HAVING Port Channel when vPC is concerned? //The port channel will be configured on both the UCSM and the 7K. The pro of a port channel would be both bandwidth and redundancy. vPC would be prefered.
Q3. if vPC is to be configured in Nexus 7000, I understand there is a limitation on confining to ONLY 1 vSphere NIC Teaming's Load-Balancing Algorithm i.e. Route Based on IP Hash. Is it correct? //Without the 1000v, I always tend to leave to dvSwitch load balence behavior at the default of "route by portID".
Again, what is the pro and con here with regard to application behaviours when Layer 2 or 3 is concerned? Or what is the BEST PRACTICES? UCS can perform L2 but Northbound should be performing L3.
Cheers,
David Jarzynka

Nexus 5548UP and LACP

Hello,
I am trying to setup LACP on the Nexus 5548UP 10 Gig switch on Port-channel 3. However, when I setup LACP, eth ports 7 and 8 (on Port-channel 3) go into either inactive or down state (as below). The 10 gig ports (7 and 8) are connected to a server which has LACP capability.
ns5500(config-if)# do sh 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)
        M - Not in use. Min-links not met
Group Port-       Type     Protocol Member Ports
      Channel
1     Po1(SU)     Eth      NONE      Eth1/15(P)   Eth1/16(P)
3     Po3(SD)     Eth      LACP      Eth1/7(D)    Eth1/8(D)
LACP setup as follows:
feature lacp
interface port-channel3
switchport access vlan 10
speed 10000
interface Ethernet1/7
switchport access vlan 10
channel-group 3 mode active
interface Ethernet1/8
switchport access vlan 10
channel-group 3 mode active
It would be great if anyone can help me with getting LACP up and running on the 10 Gig Nexus 5548UP. Please let me know if you need more information.
Thanks!

Thanks for your response. I do have vlan10 created and it is active. Thanks for correcting individual state instead of inactive.
I ran a few lacp commands below including "show lacp counters"
ns5500(config)# show lacp counters
                    LACPDUs         Marker      Marker Response    LACPDUs
Port              Sent   Recv     Sent   Recv     Sent   Recv      Pkts Err
port-channel3
Ethernet1/7        163655 13948    0      0        0      0        0
Ethernet1/8        161700 13976    0      0        0      0        0
By looking at LACP PDUs can we say that LACP is up and running?
ns5500(config)# show lacp port-channel
port-channel3
System Mac=54-7f-ee-8d-83-fc
Local System Identifier=0x8000,54-7f-ee-8d-83-fc
Admin key=0x2
Operational key=0x2
Partner System Identifier=0x0,0-0-0-0-0-0
Operational key=0x0
Max delay=0
VPC ID=0
Aggregate or individual=1
Member Port List=7-8
In the below command, it still says, interfaces 7 and 8 are down? What does that mean? An issue with the host? Is there anyway to test the nexus switch to check if it is doing its part and working correctly?
ns5500(config)# 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)
        M - Not in use. Min-links not met
Group Port-       Type     Protocol Member Ports
      Channel
1     Po1(SD)     Eth      NONE      --
3     Po3(SD)     Eth      LACP      Eth1/7(D)    Eth1/8(D)
Thanks.

Nexus 5548UP and GLC-LH-SM showing sfpinvali

Hi gurus, have just received a 5548UP and when a 1GB GLC-LH-SM is inserted into the system it shows as being invalid.
Eth0/1       --                 sfpInvali 1         auto 10G     1/10g
4 different SFPs have been tried in numerous interfaces on the system. I have also upgraded the software to 5.0(2).
And I have tried setting the speed to 1GB on the interface.
Any ideas on what simple configuration task I have missed?
LP

Hi,
I've the same issue with GLC-T 1Gbps SFP tranceiver and NX-5548UP with L3 Daughter Card.
sh int e1/32 status
Port          Name               Status    Vlan      Duplex Speed   Type
Eth1/32       VLAN99             notconnec 99        full    1000    SFP-1000BAS
The cable is connected and in the other device (switch 2960x) the ethernet interface is UP
My configuration :
NX-OS : version 5.2(1)N1(4)
interface Ethernet1/32
description VLAN99
switchport access vlan 99
speed 1000
sh mod
Mod Ports Module-Type                       Model                  Status
1   32    O2 32X10GE/Modular Universal Plat N5K-C5548UP-SUP        active *
3   0     O2 Daughter Card with L3 ASIC     N55-D160L3-V2          ok
Tranceiver info :
Ethernet1/32
    transceiver is present
    type is SFP-1000BASE-T
    name is CISCO-METHODE
    part number is SP7041_Rev_E
    revision is E
    serial number is 00000MTC163405CF
    nominal bitrate is 1300 MBit/sec
    Link length supported for copper is 100 m
    cisco id is --
    cisco extended id number is 4
DOM is not supported
Interface capa :
Ethernet1/32
Model:                 N5K-C5548UP-SUP
Type (SFP capable):    10Gbase-(unknown)
Speed:                 1000,10000
Duplex:                full
Trunk encap. type:     802.1Q
Channel:               yes
Broadcast suppression: no
Flowcontrol:           rx-(off/on),tx-(off/on)
Rate mode:             none
QOS scheduling:        rx-(6q1t),tx-(1p6q0t)
CoS rewrite:           no
ToS rewrite:           no
SPAN:                  yes
UDLD:                  yes
Link Debounce:         yes
Link Debounce Time:    yes
MDIX:                  no
Pvlan Trunk capable:   yes
TDR capable:           no
FabricPath capable:    yes
Port mode:             Switched
FEX Fabric:            yes
Any idea ?
Regards,
Julien.

Interoperability between Cisco Nexus 5548UP and IBM FC3171

Dear Techies,
We have a Cisco Nexus Switch 5548UP already in our environment with DS-SFP-FC8G-SW installed. We are planning to procure IBM Pure Flex Chassis without FC Switch, since we already have Nexus that can provide this facility. But in order to connect IBM Flex with Cisco Nexus we are planning to use IBM FC3171 Switch with IBM 44X1964 Transceivers which will act as a Mediator/Pass Through Switch for connecting IBM and Cisco.
If any expert knows OR have used this scenario, please let me know since I am interested to know if it will work in this scenario or not.
Regards,
Farhan.

Dear prkrishn
I am working on the Data Center Solution between two Data Center, details underneath
DC 1 Site
1. 2 x DC Core Switch (Nexus 7009) - will be used for Servers, Application, IBM V7000, Database, etc.
2. 2 x Network Core Switch (Cisco 6509) - Handle Campus and Inter Building connection.
3. IBM V7000 (SAN)
DC 2 Site
1. 2 x DC Core Switch (Nexus 7009) - will be used for Servers, Application, IBM V7000, Database, etc.
2. 2 x Network Core Switch (Cisco 6509) - Handle Campus and Inter Building connection.
3. IBM V7000 (SAN)
With the above mention setup, can I configure FCIP between DC1 & DC2 using Nexus 7009? or I need FCIP capable Switch such as IBM SAN Switch (SAN06-BR), I was wondering if I can configure FCIP on Nexus 7009 DC Switch.
Hoping for your kind response at earliest.
Kind Regards,
Arnold

3750 and Nexus 5548UP Support

I am working on a project that was handed down and several different engineers got their hands on. The project is (or should have been) a simple data storage/center. Fixing all the design problems has left me with very little time to research the security folks issues and I need help.
We are using Cisco Nexus 5548UP for our data center core and distribution/routing to encryptors connecting our remote sites which use Cisco 3750X series switches. The Nexus is running NOS 5.2(1)N1(4) and the 3750s use 12.2(55) IP base.
These are our particular issues:
1) For management and monitoring, what would be a good product to use to support this? If Cisco Prime Infrastructure, what ports would need to be allowed/opened through firewalls/ACLs (SNMP, syslog, etc)?
2) For switch login, the network security folks are reluctant to use TACACS and want to push for LDAP instead. Using Active Directory, is there any way to get the Cisco Nexus 5548UP and Cisco 3750Xs talking to Active Directory? I've found both 'yes' and 'no' answers online and am not sure. Do I need to use a different NOS and/or IOS? Are there specific directions somewhere? Or is it not possible?
3) Without TACACS, is there any way to implement command logging to a syslog server on the Nexus? On the 3750s, I make the following changes and all commands are relayed to our syslog server:
Enable
Configure terminal
Archive
Log config
Logging enable
Logging size 500
Hidekeys
Notify syslog
End
Is there anything similar for the Nexus?
4) In conjunction with #3, we need to be able to log each login attempt (success and failure) to a syslog server on the Nexus. On the 3750, using the "login on-[failure/success] log", it is can setup easy enough. On the Nexus, I haven't been able to find anything similar. I can't find any instructions on setting this up on the Nexus, though.
5) What IOS/NOS do we need to use to be able to lock out users after 3 failed logins (again, without using TACACS)?
If you need more information, please ask.
V/R,
Chris

The LRM is s special case transceiver which supports 10 Gbps over older FDDI grade multimode fiber when used with a mode conditioning patch cord. It is not supported on the Nexus 5548UP.
The SFP-10G-LR is used with single mode fiber for spans up to 10 km in length. It is supported on the 5548UP (and most every platform of Cisco's that takes SFPs).
Please see the product data sheet here.

Nexus 5548UP L3 card swap out for L2 cards

Hi everyone,
I have two Nexus 5548UPs and I am going to swap out the L3 cards and put in L2 cards.
I can't seem to get a straight answer out of TAC so I thought I'd try here.
How will this affect the current configuration (apart of course from removing the L3 capability)?
Will swapping the cards clear the config?
Will swapping the cards clear the licenses?
It's a very simple config so that doesn't worry me that much .. but if it will clear the licenses installed than I need to take action on that.
Thanks,
BR

no, no secret aukhadiev
I made a mistake without realising and the interface e1/3 was showing "Interface Ethernet1/3 is down (Inactive)". After spending sometime trying to figure out what was wrong with that interface or switch, it turned out to be that i forgot to add the vlan 40. Now the config looks like this:
N5K-C5548UP Switch
feature interface-vlan
feature lacp
feature dhcp
feature lldp
vrf context management
ip route 0.0.0.0/0 172.16.0.1
vlan 1
vlan 40
vlan 100
service dhcp
ip dhcp relay
interface Vlan1
no shutdown
interface Vlan40
description ** Server VLAN **
no shutdown
ip address 10.144.40.3/25
ip dhcp relay address 10.144.40.39
ip dhcp relay address 10.144.40.40
interface port-channel1
description ** Trunk Link to Switch A g1/0/23-24 **
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,122
speed 1000
interface Ethernet1/1
description ** Trunk Link to Switch A g1/0/23**
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,12
speed 1000
channel-group 1 mode active
interface Ethernet1/2
description ** Trunk Link to Switch A g1/0/24**
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,122
speed 1000
channel-group 1 mode active
interface Ethernet1/3
description **Connected to server B**
switchport access vlan 40
speed 1000
interface mgmt0
description connection to Switch A g2/0/20
no ip redirects
ip address 172.16.0.2/25
Thank you,
JN

Connecting many Brocade switches to Nexus 5548UP

Hello,
I have a SAN network composed of few separate PODs. Each POD is divided into SAN-A and SAN-B. Most of those PODs are Brocade switches (FOS 6.1). There are also few Nexus 5520s. Now, we have built new core infrastructure with Nexus 5548UPs and many MDS 9148s. We would like to move all servers and sotrage from old Brocades to the new SAN. As we cannot move all devices at the same time, all segments must be connected to the core for some time. Each POD has different zoning. Some zonings on Brocade switches are based on PWWN, some on Domain ID and Port ID. In my opinion, the only way of successfuly connecting all PODs together is to merge zones manualy (in excel, etc). and paste them on all switches. However, maybe there is some other way of merging all zones? What if I leave Nexus 5548UP in native mode (so zones from Brocade will not get merged), and only implement that manually merged zoneset on Nexus 5548UP? Will the ISL links get isolated due to zoning merge failure? Or they will maintain operational state even if zones are different on each POD? I do not have any lab boxes, so I cannot test it. Any advidse will be appreciated.
Best regards,
Krzyszof

well since you can not cluster the 45K as a virtual switch ( Cisco with new sup will start support VSS in the 4500 try to check which sup exactly and if you can upgrade as this will make a significant improvement to your design )
anyway the only method that you can use currently is the traditional way which is depending on STP ( use rapid-PVST)
from each N5K use one separate link to each 45K and STP will put on of the links in blocking mode
however you might do some STP and vlan design for load sharing where you can send vlan x over link1 and vlan y over link b to the 45K using STP cost
HTH

Connect Nexus 5548UP-L3 to Catalyst 3750G-24T-E Layer 3 Switch

Please help!
Could anyone out there please assist me with basic configuration between Nexus Switch and Catalyst Switch, so that devices connected on the catalyst switch can talk to devices connected on nexus switch and vice-versa? In my current setup all servers on VLAN 40 are connected on the Catalyst Switch A as shown in the diagram below, and all desktops and all other peripherals are connected on the Catalyst Switch B. I am required to implement/add a new Nexus Switch 5548 that in the future will replace the Switch A. From now I just need to connect both switches together and start moving the server from Switch A to the Nexus Switch.
The current network setup is shown as per diagram below:
SWITCH A – this is a layer 3 switch. All servers are connected to this switch on the VLAN 40.
SWITCH B – all desktops, VoIP telephones, and printers are connected on tis switch. This switch is also a layer 3 switch.
I have connected together the Nexus 5548UP and SWITCH A (3750G) using the GLC-T= 1000BASE-T SFP transceiver module for Category 5 copper wire. The new network is shown as per diagram below:
Below is the configuration I have created in both Switches:
SWITCH A - 3750G
interface Vlan40
description ** Server VLAN **
ip address 10.144.40.2 255.255.255.128
ip helper-address 10.144.40.39
ip helper-address 10.144.40.40
interface Vlan122
description connection to N5K-C5548UP Switch mgmt0
ip address 172.16.0.1 255.255.255.128
no ip redirects
interface Port-channel1
description UpLink to N5K-C5548UP Switch e1/1-2
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,30,40,100,101,122
switchport mode trunk
interface GigabitEthernet1/0/3
description **Connected to server A**
switchport access vlan 40
no mdix auto
spanning-tree portfast
interface GigabitEthernet1/0/20
description connection to N5K-C5548UP Switch mgmt0
switchport access vlan 122
switchport mode access
spanning-tree portfast
interface GigabitEthernet1/0/23
description UpLink to N5K-C5548UP Switch e1/1
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,30,40,100,101,122
switchport mode trunk
channel-group 1 mode active
interface GigabitEthernet1/0/24
description UpLink to N5K-C5548UP Switch e1/2
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,30,40,100,101,122
switchport mode trunk
channel-group 1 mode active
N5K-C5548UP Switch
feature interface-vlan
feature lacp
feature dhcp
feature lldp
vrf context management
ip route 0.0.0.0/0 172.16.0.1
vlan 1
vlan 100
service dhcp
ip dhcp relay
interface Vlan1
no shutdown
interface Vlan40
description ** Server VLAN **
no shutdown
ip address 10.144.40.3/25
ip dhcp relay address 10.144.40.39
ip dhcp relay address 10.144.40.40
interface port-channel1
description ** Trunk Link to Switch A g1/0/23-24 **
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,122
speed 1000
interface Ethernet1/1
description ** Trunk Link to Switch A g1/0/23**
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,12
speed 1000
channel-group 1 mode active
interface Ethernet1/2
description ** Trunk Link to Switch A g1/0/24**
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,122
speed 1000
channel-group 1 mode active
interface Ethernet1/3
description **Connected to server B**
switchport access vlan 40
speed 1000
interface mgmt0
description connection to Switch A g2/0/20
no ip redirects
ip address 172.16.0.2/25
I get a successful response from Server A when I ping the N5K-C5548UP Switch (VLAN 40 interface (10.144.40.3) .But if I try to ping from Server A to Server B or vice-versa the ping fails. From N5K-C5548UP I can ping successful either Server A or Server B. What am I doing wrong here? Is there any additional configuration that I need to add on the Nexus Switch? Please Help. Thank you.

no, no secret aukhadiev
I made a mistake without realising and the interface e1/3 was showing "Interface Ethernet1/3 is down (Inactive)". After spending sometime trying to figure out what was wrong with that interface or switch, it turned out to be that i forgot to add the vlan 40. Now the config looks like this:
N5K-C5548UP Switch
feature interface-vlan
feature lacp
feature dhcp
feature lldp
vrf context management
ip route 0.0.0.0/0 172.16.0.1
vlan 1
vlan 40
vlan 100
service dhcp
ip dhcp relay
interface Vlan1
no shutdown
interface Vlan40
description ** Server VLAN **
no shutdown
ip address 10.144.40.3/25
ip dhcp relay address 10.144.40.39
ip dhcp relay address 10.144.40.40
interface port-channel1
description ** Trunk Link to Switch A g1/0/23-24 **
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,122
speed 1000
interface Ethernet1/1
description ** Trunk Link to Switch A g1/0/23**
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,12
speed 1000
channel-group 1 mode active
interface Ethernet1/2
description ** Trunk Link to Switch A g1/0/24**
switchport mode trunk
switchport trunk allowed vlan 1,30,40,100-101,122
speed 1000
channel-group 1 mode active
interface Ethernet1/3
description **Connected to server B**
switchport access vlan 40
speed 1000
interface mgmt0
description connection to Switch A g2/0/20
no ip redirects
ip address 172.16.0.2/25
Thank you,
JN

Cisco Nexus 5548UP connecting to HP P4330 StoreVirtual over iScsi

Hi,
I need some advice when it comes to how to setup a port-channel between Nexus 5548UP and a HP StoreVirtual 4330 device. The idea is to use 2 10 GB ports in a port-channel group and this far I've this on the port-channel group;
interface port-channel1002
priority-flow-control mode off
switchport access vlan 400
load-interval counter 2 30
load-interval counter 3 300
What about priority-flow-control, any needs to change anything here? Any other things that needs to be considered when using iScsi?
Much appreciated!
Tony Lewis

Hi Tony,
You do not have to worry about PFC. Priority-Flow-Control is something which is related to FCOE or DCBX protocol. With iSCSI as this is a TCP traffic, you have to make sure that you have a proper QOS for the IP Subnet or VLAN that has your iSCSI hosts transmitting the data. As iSCSI rides over TCP this is the major issue that I have seen related to the valid QOS config for the traffic. There is not best practice for it but you have make sure that you added it to a class other than BE or Scavanger class.
Hope this helps.
Cheers,
-amit singh

NEXUS 5548UP LAYOUT - Shared flogi between nexus

Hello,
I have 4 Nexus 5548UP, and I need to do they share information of FLOGI among the switches N5K1 and N5K3.
Today i can do this, the way shown above.
But I would like to have another link redundancy between switches N5K1 and N5K3.
I already tried adding this link redundancy on a port-channel, but when I do that I can not share the FLOGI informations between switches.
I would like your help to know what I can do in this case?.

In your picture I see, that you plan to use classical Fibrechannel for storage and FCoE for servers.
Fibrechannel and multihop FCoE has strict design rules of separate fabrics, which is very different to Ethernet (and IP) networking.
Specially vPC violates this separation; see eg. Fibre Channel over Ethernet Operations
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/n5k_fcoe_ops.html#wp1079705
and
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/mkt_ops_guides/513_n1_1/n5k_enhanced_vpc.html#wp1162674
SAN A and SAN B Traffic Isolation
You can deploy FCoE in an Enhanced vPC topology. Traditionally, the SAN network maintains two fabrics, the SAN A and SAN B. The traffic from side A is isolated from side B. Hosts and storage arrays are attached to host SAN networks for high availability. The FCoE traffic in an Enhanced vPC topology maintain the traffic isolation for two SAN networks. The FCoE command ensures the FCoE traffic from the FEX is only sent to one Cisco Nexus 5000 Series device is as follows:

Diff b/w Nexus 5548P and 5548UP

What is the
Diff b/w Nexus 5548P and 5548UP
regards.

Hi,
A UP or Unified ports allow you to configure ports as Ethernet, native Fibre Channel or Fibre Channel over Ethernet (FCoE) ports. By default, the ports are Ethernet ports but you can change the port mode to Fibre Channel on the following unified ports:
Any port on the Cisco Nexus 5548UP switch or the Cisco Nexus 5596UP switch.
The ports on the Cisco N55-M16UP expansion module that is installed in a Cisco Nexus 5548P switch.
More details:
http://www.cisco.com/web/techdoc/dc/reference/cli/nxos/commands/l2/port.html
Comapre 5548 and 5548:
http://www.cisco.com/en/US/products/ps9670/prod_models_comparison.html
./Abhinav

Use GLC-T to connect ucs 6120 and 2960s (RJ45),.have SFP validation failed problem

hi,every .
i use GLC-T to connect ucs 6120 and cisco2960s (RJ45),.have sfp validation failed problem.
I have done speed to 1G then I am getting error " link not connected" even I have connected the nnetwork cable..

UCS6120-A(nxos)# show interface e1/7
Ethernet1/7 is down (SFP validation failed)
Hardware: 1000/10000 Ethernet, address: 0005.73d2.934e (bia 0005.73d2.934e)
Description: U: Uplink
MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is trunk
auto-duplex, 1000 Mb/s, media type is 10G
Beacon is turned off
Input flow-control is off, output flow-control is off
Rate mode is dedicated
Switchport monitor is off
EtherType is 0x8100
Last link flapped never
Last clearing of "show interface" counters never
30 seconds input rate 0 bits c, 0 bytes c, 0 packets c
30 seconds output rate 0 bits c, 0 bytes c, 0 packets c
Load-Interval #2: 5 minute (300 seconds)
input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
RX
0 unicast packets 0 multicast packets 0 broadcast packets
0 input packets 0 bytes
--More--

Nexus 5548UP - HSRP and vPC, tracking required?

Hi,
We've got two Nexus 5548UPs that are vPC and HSRP peers.
I've had some feedback that I should incorporate the tracking function to close the vPC down in the case of a layer 3 problem, the thing is I'm not sure it's required. I can see in this article it recommends implementing tracking when your L2 peer-link and L3 interfaces are on the same module (which it is in my case).. http://www.cisco.com/en/US/docs/switches/datacenter/sw/design/vpc_design/vpc_best_practices_design_guide.pdf
But in this article it says not to use tracking.. http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/design_guide_c07-625857.pdf
Any one got any real world experience and can offer some feedback.. I don't mind putting it in just want to understand why.
Thanks,
Nick.

Hi Nick
there is two tracking can be use din nexus enviroment
HSRP tracking and vPC tracking
for using one line card for the vPC peer link vPC tracking is recomnded
HSRP tracking is used to track L3 uplinks to the core
Using vPC with HSRP/VRRP object tracking may leads to traffic blackholing in case object tracking is triggered
its better to use separate L3 inter switch link instead of using HSRP tracking
hope this help

Nexus 5548UP and UCS 6120's

Similar Messages

Maybe you are looking for