Nexus 5000 Fabric Management Software

Do I need the Fabric Management software to configure the FC & FCoE features on the N5K?
Can I use the unlicensed version, if I just have (2) N5K's in a cluster?
Do I still need to install the database, if I don't use the Performance Monitor?

yes, you do. If you want to use the server version. There is another option, called "standalone", to pick during the installation. It was free as I know.

Similar Messages

  • Reg Nexus 5000 + 7000 software (Shellshock -bug )

    Hi people.
    Regarding this bug : Shellshock . What is the recomended software upgrade for Nexus 5000 & 7000.
    It is important that the VPC and FCoE is still working, after an upgrade.
    Need recommendation for following devices :
    Nexus 5000
    https://tools.cisco.com/bugsearch/bug/CSCur05017
    All current versions of NX-OS on this platform are affected unless 
    otherwise stated.. This bug will be updated with detailed affected and 
    fixed software versions once fixed software is available.
    Exposure is not configuration dependent.
    Authentication is required to exploit this vulnerability. 
    Nexus 7000
    https://tools.cisco.com/bugsearch/bug/CSCuq98748
    All current versions of NX-OS on this platform are affected unless 
    otherwise stated
    Exposure is not configuration dependent.
    Authentication is required to exploit this vulnerability.
    This bug is fixed in NX-OS versions specified below:
    5.2(9a)
    6.1(5a)
    6.2(8b)
    6.2(10) and above
    Is there anyone that has some information on this ?
    Many thanx in advance,

    Hello.
    Let me look into this for you. Do you have an existing support contract or SmartNet for these Nexus 5000 and 7000 switches, by the way?
    Let me know if you have other concerns as well or e-mail ([email protected]) me directly. 
    Kind regards. 

  • Errors & Discards in Fabric Manager

    I have been getting Errors (about 140) & Discards for some hosts attached to our MDS 9509. Is it something to worry about? What is a normal level of Errors & Discards?

    Send me the: show flogi data, show fcns data and sh int fc 1/x (the interface connected).
    Cisco FMS software for planning purposes is as follows:
    Switches: 200
    End-devices: 5000
    Fabric Monitored: 24
    Concurrent mgmt sessions:16
    The number of switches and end-devices are not limited explicitly by software. An administrator can raise the limits on fabrics and concurrent management sessions if needed.

  • Nexus 5000 - Odd Ethernet interface behavior (link down inactive)

    Hi Guys,
    This would sound really trivial but it is very odd behavior.
    - We have a server connected to a 2, Nexus 5000s (for resiliancy)
    - When there is no config on the ethernet interfaces whatsoever, the ethernet interface is UP / UP, there is minimal amount of traffic on the link etc. E.g.
    Ethernet1/16 is up
      Hardware: 1000/10000 Ethernet, address: 000d.ece7.85d7 (bia 000d.ece7.85d7)
      Description: shipley-p1.its RK14/A13
      MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA
      Port mode is access
      full-duplex, 10 Gb/s, media type is 1/10g
      Beacon is turned off
      Input flow-control is off, output flow-control is off
      Rate mode is dedicated
      Switchport monitor is off
      Last link flapped 00:00:07
      Last clearing of "show interface" counters 05:42:32
      30 seconds input rate 0 bits/sec, 0 packets/sec
      30 seconds output rate 96 bits/sec, 0 packets/sec
      Load-Interval #2: 5 minute (300 seconds)
        input rate 0 bps, 0 pps; output rate 8 bps, 0 pps
      RX
        0 unicast packets  0 multicast packets  0 broadcast packets
        0 input packets  0 bytes
        0 jumbo packets  0 storm suppression packets
        0 runts  0 giants  0 CRC  0 no buffer
        0 input error  0 short frame  0 overrun   0 underrun  0 ignored
        0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
        0 input with dribble  0 input discard
        0 Rx pause
      TX
        0 unicast packets  163 multicast packets  0 broadcast packets
        163 output packets  15883 bytes
        0 jumbo packets
        0 output errors  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble
        0 Tx pause
      1 interface resets
    - As soon as I configure the link to be an access port, the link goes down, flagging "inactivity" E.g.
    sh int e1/16
    Ethernet1/16 is down (inactive)
      Hardware: 1000/10000 Ethernet, address: 000d.ece7.85d7 (bia 000d.ece7.85d7)
      Description: shipley-p1.its RK14/A13
      MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA
      Port mode is access
      auto-duplex, 10 Gb/s, media type is 1/10g
      Beacon is turned off
      Input flow-control is off, output flow-control is off
      Rate mode is dedicated
      Switchport monitor is off
      Last link flapped 05:38:03
      Last clearing of "show interface" counters 05:41:33
      30 seconds input rate 0 bits/sec, 0 packets/sec
      30 seconds output rate 0 bits/sec, 0 packets/sec
      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
        0 jumbo packets  0 storm suppression packets
        0 runts  0 giants  0 CRC  0 no buffer
        0 input error  0 short frame  0 overrun   0 underrun  0 ignored
        0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop
        0 input with dribble  0 input discard
        0 Rx pause
      TX
        0 unicast packets  146 multicast packets  0 broadcast packets
        146 output packets  13083 bytes
        0 jumbo packets
        0 output errors  0 collision  0 deferred  0 late collision
        0 lost carrier  0 no carrier  0 babble
        0 Tx pause
      0 interface resets
    - This behavior is seen on both 5Ks
    - I've tried using a different set of ports, changed SFPs, and fibre cabling to no avail
    - I can't seem to understand this behavior?!  In that, why would configuring the port cause the link to go down?
    - If anyone has experience this before, or could shed some light on this behavior, it would be appreciated.
    sh ver
    Cisco Nexus Operating System (NX-OS) Software
    TAC support: http://www.cisco.com/tac
    Copyright (c) 2002-2010, Cisco Systems, Inc. All rights reserved.
    The copyrights to certain works contained herein are owned by
    other third parties and are used and distributed under license.
    Some parts of this software are covered under the GNU Public
    License. A copy of the license is available at
    http://www.gnu.org/licenses/gpl.html.
    Software
      BIOS:      version 1.2.0
      loader:    version N/A
      kickstart: version 4.2(1)N1(1)
      system:    version 4.2(1)N1(1)
      power-seq: version v1.2
      BIOS compile time:       06/19/08
      kickstart image file is: bootflash:/n5000-uk9-kickstart.4.2.1.N1.1.bin
      kickstart compile time:  4/29/2010 19:00:00 [04/30/2010 02:38:04]
      system image file is:    bootflash:/n5000-uk9.4.2.1.N1.1.bin
      system compile time:     4/29/2010 19:00:00 [04/30/2010 03:51:47]
    thanks
    Sheldon

    I had identical issue
    Two interfaces on two different FEXes were INACTIVE. I have two Nexus 5596 in vPC and A/A FEXes.
    I also use config-sync feature.
    Very same configuration was applied to other ports on other FEXes and they were working with no problems.
    interface Ethernet119/1/1
      inherit port-profile PP-Exchange2003
    I checked VLAN status associated with this profile and it was active (of course it was, other ports were ok).
    I solved it by removing port profile from this port and re-applied it... voila, port changed state to up!
    Very very strange.

  • Management software for VIC [M81KR] card "Cisco VIC Ethernet Interface" - Win 2k8R2

    Hi,
        I am configuring a blade presently that has a VIC (M81KR) card installed.
    In the UCS profile, I configured 4 vNICS
    - 2 vNICS for Public (One on Fabric A, one on Fabric B)
    - 2 vNICS for Private (One on Fabric A, one on Fabric B)
    I have installed the OS (Win Server 2008 R2) and the Ethernet Drivers (Cisco Ethernet Driver).
    What I want to be able to do is to bond/team the links together and tag VLAN traffic.
    -- I've downloaded the Utility ISO from Cisco, however there is no management software for the VIC (That I can see). There is only software for:
        + Broadcomm, QLogic & Emulex..
    Any assistance is appreciated!
    Cheers, Chris.

    Just to add to Simon's comments, we rely on fabric failover rather than a teaming driver.  This take the load off the host and puts it on the adaptor hardware. 
    The only other use case I've heard of for the teaming is in full width blades such as the B250 & B440, where customers may want to team across the two adaptors for great redudancy.  As the MTBF for the adaptors is extremely high, this wasn't seen as a priority/concern.  If you have another business or technical requirement that FF will not solve, please let me know so I can feed this back to our development team.
    As for the VLAN driver, at present you need to configure unique NICs for each VLAN.  I've pushed on this request for some time and I'm told it has been planned for a future release.  I'll check to verify which release the Palo VLAN tagging driver (for windows) is tentatlively planned for and get back to you.
    Regards,
    Robert

  • Cisco MDS 9513/9509 LDAP/AD Auth via SSH & Fabric Manager

    Hello Folks,
    I am trying to look for working config with LDAP auth over SSH. I know how to use them over TACACS+ & Radius. But due to other internal issue, currently I am trying to get the Cisco MDS to directly auth using LDAP/AD. Also, I see no option of LDAP/AD in FM(Fabric Manager), but just TACACS+, Radius, LocalFM and MDS. Do using MDS uses default auth(ie whatever AAA authentication is configured for ? or local DB on the switch).  Does the new DCNM supports LDAP/AD auth on the GUI ?
    Larger goal is SSH(CLI) & FM(GUI) using the same LDAP/AD auth. I understand the snmp-server user issue. But once I have SSH working over LDAP/AD I can figure that out to..
    Here's what I need to ensure when using LDAP/AD auth
    1) What is the exact config for this LDAP/AD auth
    2) How do I ensure that network-admin & network-opertor roles are assigned when certain AD Groups Logins in Like ADMIN-AD-GROUP , OPERATOR-AD-GROUP --> trying to login to the switch
    3) Also using SSL port for LDAP, do details are encrypted over the network.
    4) Do I need to use the PASSWORD in paintext when BINDING the BaseDN ?, can it be an encrypted password.
    Appreciate any info on this. Thanks for your time.

    As of DCNM 6.1 (aka - Fabric Manager Server) we support LDAP authentication adding to existing Radius, TACACS+, local and switch authentications.  You can upgrade from Fabric Manager 5.0 to DCNM 5.2 to DCNM 6.1 if you like to keep current performance, events, config data alive.  We do recommend fresh install as we don't know what state your server dabatabase might be in.  Including some links for you to help out with deployment and best practices (see release notes).
    Resources:
    Main Website:
    http://www.cisco.com/go/dcnm
    How To Video Series:  http://www.cisco.com/en/US/prod/netmgtsw/ps6505/ps9369/cisco_dc_nm_video_library.html
    Install and Licensing Guide:
    http://www.cisco.com/en/US/products/ps9369/prod_installation_guides_list.html
    Evaluation Licenses: http://tools.cisco.com/SWIFT/LicensingUI/Home?FormId=65
    Download Linux and Windows Executables: http://www.cisco.com/cisco/pub/software/portal/select.html?&i=!m&mdfid=281722751
    Data Sheets: http://www.cisco.com/en/US/prod/collateral/netmgtsw/ps6505/ps9369/data_sheet_c78-639737.html
    Install Guide: http://www.cisco.com/en/US/products/ps9369/prod_installation_guides_list.html
    Configure Guide:  http://www.cisco.com/en/US/products/ps9369/products_installation_and_configuration_guides_list.html
    API Programming Guide:
    http://www.cisco.com/en/US/products/ps9369/products_programming_reference_guides_list.html
    Reference Guide: http://www.cisco.com/en/US/products/ps9369/prod_technical_reference_list.html
    Release Notes: http://www.cisco.com/en/US/products/ps9369/tsd_products_support_general_information.html

  • Ask the Expert: Different Flavors and Design with vPC on Cisco Nexus 5000 Series Switches

    Welcome to the Cisco® Support Community Ask the Expert conversation.  This is an opportunity to learn and ask questions about Cisco® NX-OS.
    The biggest limitation to a classic port channel communication is that the port channel operates only between two devices. To overcome this limitation, Cisco NX-OS has a technology called virtual port channel (vPC). A pair of switches acting as a vPC peer endpoint looks like a single logical entity to port channel attached devices. The two devices that act as the logical port channel endpoint are actually two separate devices. This setup has the benefits of hardware redundancy combined with the benefits offered by a port channel, for example, loop management.
    vPC technology is the main factor for success of Cisco Nexus® data center switches such as the Cisco Nexus 5000 Series, Nexus 7000 Series, and Nexus 2000 Series Switches.
    This event is focused on discussing all possible types of vPC along-with best practices, failure scenarios, Cisco Technical Assistance Center (TAC) recommendations and troubleshooting
    Vishal Mehta is a customer support engineer for the Cisco Data Center Server Virtualization Technical Assistance Center (TAC) team based in San Jose, California. He has been working in TAC for the past 3 years with a primary focus on data center technologies, such as the Cisco Nexus 5000 Series Switches, Cisco Unified Computing System™ (Cisco UCS®), Cisco Nexus 1000V Switch, and virtualization. He presented at Cisco Live in Orlando 2013 and will present at Cisco Live Milan 2014 (BRKCOM-3003, BRKDCT-3444, and LABDCT-2333). He holds a master’s degree from Rutgers University in electrical and computer engineering and has CCIE® certification (number 37139) in routing and switching, and service provider.
    Nimit Pathak is a customer support engineer for the Cisco Data Center Server Virtualization TAC team based in San Jose, California, with primary focus on data center technologies, such as Cisco UCS, the Cisco Nexus 1000v Switch, and virtualization. Nimit holds a master's degree in electrical engineering from Bridgeport University, has CCNA® and CCNP® Nimit is also working on a Cisco data center CCIE® certification While also pursuing an MBA degree from Santa Clara University.
    Remember to use the rating system to let Vishal and Nimit know if you have received an adequate response. 
    Because of the volume expected during this event, Vishal and Nimit might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure Community, under the subcommunity LAN, Switching & Routing, shortly after the event. This event lasts through August 29, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

    Hello Gustavo
    Please see my responses to your questions:
    Yes almost all routing protocols use Multicast to establish adjacencies. We are dealing with two different type of traffic –Control Plane and Data Plane.
    Control Plane: To establish Routing adjacency, the first packet (hello) is punted to CPU. So in the case of triangle routed VPC topology as specified on the Operations Guide Link, multicast for routing adjacencies will work. The hellos packets will be exchanged across all 3 routers and adjacency will be formed over VPC links
    http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/operations/n5k_L3_w_vpc_5500platform.html#wp999181
    Now for Data Plane we have two types of traffic – Unicast and Multicast.
    The Unicast traffic will not have any forwarding issues, but because the Layer 3 ECMP and port channel run independent hash calculations there is a possibility that when the Layer 3 ECMP chooses N5k-1 as the Layer 3 next hop for a destination address while the port channel hashing chooses the physical link toward N5k-2. In this scenario,N5k-2 receives packets from R with the N5k-1 MAC as the destination MAC.
    Sending traffic over the peer-link to the correct gateway is acceptable for data forwarding, but it is suboptimal because it makes traffic cross the peer link when the traffic could be routed directly.
    For that topology, Multicast Traffic might have complete traffic loss due to the fact that when a PIM router is connected to Cisco Nexus 5500 Platform switches in a vPC topology, the PIM join messages are received only by one switch. The multicast data might be received by the other switch.
    The Loop avoidance works little different across Nexus 5000 and Nexus 7000.
    Similarity: For both products, loop avoidance is possible due to VSL bit
    The VSL bit is set in the DBUS header internal to the Nexus.
    It is not something that is set in the ethernet packet that can be identified. The VSL bit is set on the port asic for the port used for the vPC peer link, so if you have Nexus A and Nexus B configured for vPC and a packet leaves Nexus A towards Nexus B, Nexus B will set the VSL bit on the ingress port ASIC. This is not something that would traverse the peer link.
    This mechanism is used for loop prevention within the chassis.
    The idea being that if the port came in the peer link from the vPC peer, the system makes the assumption that the vPC peer would have forwarded this packet out the vPC-enabled port-channels towards the end device, so the egress vpc interface's port-asic will filter the packet on egress.
    Differences:  In Nexus 5000 when it has to do L3-to-L2 lookup for forwarding traffic, the VSL bit is cleared and so the traffic is not dropped as compared to Nexus 7000 and Nexus 3000.
    It still does loop prevention but the L3-to-L2 lookup is different in Nexus 5000 and Nexus 7000.
    For more details please see below presentation:
    https://supportforums.cisco.com/sites/default/files/session_14-_nexus.pdf
    DCI Scenario:  If 2 pairs are of Nexus 5000 then separation of L3/L2 links is not needed.
    But in most scenarios I have seen pair of Nexus 5000 with pair of Nexus 7000 over DCI or 2 pairs of Nexus 7000 over DCI. If Nexus 7000 are used then L3 and L2 links are required for sure as mentioned on above presentation link.
    Let us know if you have further questions.
    Thanks,
    Vishal

  • UCS C-Series VIC-1225 to Nexus 5000 setup

    Hello,
    I have two nexus 5000 setup with a vpc peer link. I also have an cisco c240 m3 server with a vic-1225 card that will be running esx 5.1. I also have some 4 2248 fabric extenders. I have been searching for some best practice information on how to best setup this equipment. The nexus equipment is already running, so its more about connecting the c240 and the vic-1225 to the nexus switches. I guess this is better to do rather than to connect to the fabric extenders in order to minmize hops?
    All documention I have found involves setup/configuration etc with fabric interconnects which I dont have, and have been told that I do not need. Does anyone have any info on this? and can point me in the right direction to setup this correctly?
    More specifically, how should I setup the vic-1225 card to the nexus? just create a regular vpc/port-channel to the nexuses? use lacp and set it to active?
    Do I need to make any configuration changes on the vic card via the cimc on the c240 server to make this work?

    Hello again, Im stuck
    This is what I have done. I have created the vPC between my esx host and my two nexus 5000 switches, but it doesnt seem to come up:
    S02# 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
    4     Po4(SD)     Eth      LACP      Eth1/9(D)
    vPC info:
    S02# sh vpc 4
    vPC status
    id     Port        Status Consistency Reason                     Active vlans
    4      Po4         down*  success     success                    -
    vPC config:
    interface port-channel4
      switchport mode trunk
      switchport trunk allowed vlan 20,27,30,50,100,500-501
      spanning-tree port type edge trunk
      vpc 4
    interface Ethernet1/9
      switchport mode trunk
      switchport trunk allowed vlan 20,27,30,50,100,500-501
      spanning-tree port type edge trunk
      channel-group 4 mode active
    Im unsure what I must configure on the cisco 240M3(esx host) side to make this work. I only have the two default interfaces(eth0 and eth1) on the vic-1225 installed in the esx host, and both have the vlan mode is set to TRUNK.
    Any ideas on what I am missing?
    Message was edited by: HDA

  • VPC on Nexus 5000 with Catalyst 6500 (no VSS)

    Hi, I'm pretty new on the Nexus and UCS world so I have some many questions I hope you can help on getting some answers.
    The diagram below is the configuration we are looking to deploy, that way because we do not have VSS on the 6500 switches so we can not create only one  Etherchannel to the 6500s.
    Our blades inserted on the UCS chassis  have INTEL dual port cards, so they do not support full failover.
    Questions I have are.
    - Is this my best deployment choice?
    - vPC highly depend on the management interface on the Nexus 5000 for the keep alive peer monitoring, so what is going to happen if the vPC brakes due to:
         - one of the 6500 goes down
              - STP?
              - What is going to happend with the Etherchannels on the remaining  6500?
         - the Management interface goes down for any other reason
              - which one is going to be the primary NEXUS?
    Below is the list of devices involved and the configuration for the Nexus 5000 and 65000.
    Any help is appreciated.
    Devices
    ·         2  Cisco Catalyst with two WS-SUP720-3B each (no VSS)
    ·         2 Cisco Nexus 5010
    ·         2 Cisco UCS 6120xp
    ·         2 UCS Chassis
         -    4  Cisco  B200-M1 blades (2 each chassis)
              - Dual 10Gb Intel card (1 per blade)
    vPC Configuration on Nexus 5000
    TACSWN01
    TACSWN02
    feature vpc
    vpc domain 5
    reload restore
    reload restore   delay 300
    Peer-keepalive   destination 10.11.3.10
    role priority 10
    !--- Enables vPC, define vPC domain and peer   for keep alive
    int ethernet 1/9-10
    channel-group 50   mode active
    !--- Put Interfaces on Po50
    int port-channel 50
    switchport mode   trunk
    spanning-tree port   type network
    vpc peer-link
    !--- Po50 configured as Peer-Link for vPC
    inter ethernet 1/17-18
    description   UCS6120-A
    switchport mode   trunk
    channel-group 51   mode active
    !--- Associates interfaces to Po51 connected   to UCS6120xp-A  
    int port-channel 51
    swithport mode   trunk
    vpc 51
    spannig-tree port   type edge trunk
    !--- Associates vPC 51 to Po51
    inter ethernet 1/19-20
    description   UCS6120-B
    switchport mode   trunk
    channel-group 52   mode active
    !--- Associates interfaces to Po51 connected   to UCS6120xp-B  
    int port-channel 52
    swithport mode   trunk
    vpc 52
    spannig-tree port   type edge trunk
    !--- Associates vPC 52 to Po52
    !----- CONFIGURATION for Connection to   Catalyst 6506
    Int ethernet 1/1-3
    description   Cat6506-01
    switchport mode   trunk
    channel-group 61   mode active
    !--- Associate interfaces to Po61 connected   to Cat6506-01
    Int port-channel 61
    switchport mode   trunk
    vpc 61
    !--- Associates vPC 61 to Po61
    Int ethernet 1/4-6
    description   Cat6506-02
    switchport mode   trunk
    channel-group 62   mode active
    !--- Associate interfaces to Po62 connected   to Cat6506-02
    Int port-channel 62
    switchport mode   trunk
    vpc 62
    !--- Associates vPC 62 to Po62
    feature vpc
    vpc domain 5
    reload restore
    reload restore   delay 300
    Peer-keepalive   destination 10.11.3.9
    role priority 20
    !--- Enables vPC, define vPC domain and peer   for keep alive
    int ethernet 1/9-10
    channel-group 50   mode active
    !--- Put Interfaces on Po50
    int port-channel 50
    switchport mode   trunk
    spanning-tree port   type network
    vpc peer-link
    !--- Po50 configured as Peer-Link for vPC
    inter ethernet 1/17-18
    description   UCS6120-A
    switchport mode   trunk
    channel-group 51   mode active
    !--- Associates interfaces to Po51 connected   to UCS6120xp-A  
    int port-channel 51
    swithport mode   trunk
    vpc 51
    spannig-tree port   type edge trunk
    !--- Associates vPC 51 to Po51
    inter ethernet 1/19-20
    description   UCS6120-B
    switchport mode   trunk
    channel-group 52   mode active
    !--- Associates interfaces to Po51 connected   to UCS6120xp-B  
    int port-channel 52
    swithport mode   trunk
    vpc 52
    spannig-tree port   type edge trunk
    !--- Associates vPC 52 to Po52
    !----- CONFIGURATION for Connection to   Catalyst 6506
    Int ethernet 1/1-3
    description   Cat6506-01
    switchport mode   trunk
    channel-group 61   mode active
    !--- Associate interfaces to Po61 connected   to Cat6506-01
    Int port-channel 61
    switchport mode   trunk
    vpc 61
    !--- Associates vPC 61 to Po61
    Int ethernet 1/4-6
    description   Cat6506-02
    switchport mode   trunk
    channel-group 62   mode active
    !--- Associate interfaces to Po62 connected   to Cat6506-02
    Int port-channel 62
    switchport mode   trunk
    vpc 62
    !--- Associates vPC 62 to Po62
    vPC Verification
    show vpc consistency-parameters
    !--- show compatibility parameters
    Show feature
    !--- Use it to verify that vpc and lacp features are enabled.
    show vpc brief
    !--- Displays information about vPC Domain
    Etherchannel configuration on TAC 6500s
    TACSWC01
    TACSWC02
    interface range GigabitEthernet2/38 - 43
    description   TACSWN01 (Po61 vPC61)
    switchport
    switchport trunk   encapsulation dot1q
    switchport mode   trunk
    no ip address
    channel-group 61   mode active
    interface range GigabitEthernet2/38 - 43
    description   TACSWN02 (Po62 vPC62)
    switchport
    switchport trunk   encapsulation dot1q
    switchport mode   trunk
    no ip address
    channel-group 62   mode active

    ihernandez81,
    Between the c1-r1 & c1-r2 there are no L2 links, ditto with d6-s1 & d6-s2.  We did have a routed link just to allow orphan traffic.
    All the c1r1 & c1-r2 HSRP communications ( we use GLBP as well ) go from c1-r1 to c1-r2 via the hosp-n5k-s1 & hosp-n5k-s2.  Port channels 203 & 204 carry the exact same vlans.
    The same is the case on the d6-s1 & d6-s2 sides except we converted them to a VSS cluster so we only have po203 with  4 *10 Gb links going to the 5Ks ( 2 from each VSS member to each 5K).
    As you can tell what we were doing was extending VM vlans between 2 data centers prior to arrivals of 7010s and UCS chassis - which  worked quite well.
    If you got on any 5K you would see 2 port channels - 203 & 204  - going to each 6500, again when one pair went to VSS po204 went away.
    I know, I know they are not the same things .... but if you view the 5Ks like a 3750 stack .... how would you hook up a 3750 stack from 2 6500s and if you did why would you run an L2 link between the 6500s ?
    For us using 4 10G ports between 6509s took ports that were too expensive - we had 6704s - so use the 5Ks.
    Our blocking link was on one of the links between site1 & site2.  If we did not have wan connectivty there would have been no blocking or loops.
    Caution .... if you go with 7Ks beware of the inability to do L2/L3 via VPCs.
    better ?
    one of the nice things about working with some of this stuff is as long as you maintain l2 connectivity if you are migrating things they tend to work, unless they really break

  • PFC configuration on Nexus 5000

    Hi,
    I have a CNA in my server connected to cisco nexus 5000 interfcae. I Want to genearate pause frames for FCOE class of traffic using the default class class-fcoe and cos value 3, the firmware version running is 5.0(3) N1 (1b). Can anyone tell me how can i configure it ?
    Thanks,
    Manju

    Sorry for the delayed response, Here is what you asked
    Cisco-5020# sh mod
    Mod Ports  Module-Type                      Model                  Status
    1    40     40x10GE/Supervisor               N5K-C5020P-BF-SUP      active *
    2    8      4x10GE + 4x1/2/4G FC Module      N5K-M1404              ok
    Mod  Sw              Hw      World-Wide-Name(s) (WWN)
    1    5.0(3)N1(1b)    1.2     --
    2    5.0(3)N1(1b)    1.0     20:41:00:0d:ec:b2:15:40 to 20:44:00:0d:ec:b2:15:40
    Mod  MAC-Address(es)                         Serial-Num
    1    000d.ecb2.1548 to 000d.ecb2.156f         JAF1303ACES
    2    000d.ecb2.1570 to 000d.ecb2.1577         JAF1245AJLF
    Cisco-5020#
    Cisco-5020#
    Cisco-5020# sh run
    !Command: show running-config
    !Time: Fri Oct 28 17:40:02 2005
    version 5.0(3)N1(1b)
    feature fcoe
    feature npiv
    feature telnet
    feature lldp
    username admin password 5 $1$v9Tm8Y77$ZSdbOfBxe1.Z9Oz1V9V2B0  role network-admin
    no password strength-check
    ip domain-lookup
    hostname Cisco-5020
    logging event link-status default
    service unsupported-transceiver
    class-map type qos class-fcoe
    class-map type queuing class-all-flood
      match qos-group 2
    class-map type queuing class-ip-multicast
      match qos-group 2
    class-map type network-qos class-all-flood
      match qos-group 2
    class-map type network-qos class-ip-multicast
      match qos-group 2
    policy-map type network-qos jumbo
      class type network-qos class-fcoe
        pause no-drop
        mtu 2158
      class type network-qos class-default
        mtu 9216
    system qos
      service-policy type network-qos jumbo
    snmp-server user admin network-admin auth md5 0x2694501fdfbe5abed9e85d51e4e31038 priv 0x2694501fdfbe5abed9e85d51e4e31038 localizedkey
    snmp-server host 138.239.198.184 traps version 2c public  udp-port 1163
    snmp-server host 138.239.198.184 traps version 2c public  udp-port 1164
    snmp-server host 138.239.198.200 traps version 2c public  udp-port 1163
    snmp-server host 138.239.198.200 traps version 2c public  udp-port 1164
    snmp-server host 138.239.200.118 traps version 2c public  udp-port 1163
    snmp-server host 138.239.198.200 traps version 2c public  udp-port 1163
    snmp-server enable traps entity fru
    snmp-server community snmpv3 group network-operator
    vrf context management
      ip route 0.0.0.0/0 10.192.207.254
    vlan 1-2,8
    vlan 10
      fcoe vsan 10
    vlan 20
      fcoe vsan 20
    vlan 30
    vlan 35
      fcoe vsan 35
    vlan 40,50
    vlan 52
      fcoe vsan 52
    vsan database
      vsan 20
      vsan 52
    fcdomain fcid database
      vsan 52 wwn 10:00:00:00:c9:b1:e5:3d fcid 0x180000 dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:e5:3b fcid 0x180001 dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:4d:e3 fcid 0x180002 dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:ab:ad fcid 0x180003 dynamic
      vsan 52 wwn 10:00:00:00:c9:ad:ac:41 fcid 0x180004 dynamic
      vsan 52 wwn 10:00:00:00:c9:ad:ac:b9 fcid 0x180005 dynamic
      vsan 52 wwn 10:00:00:00:c9:ad:ac:b5 fcid 0x180006 dynamic
      vsan 52 wwn 10:00:00:00:c9:f2:73:d1 fcid 0x180007 dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:4d:e1 fcid 0x180008 dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:ab:a9 fcid 0x180009 dynamic
      vsan 52 wwn 10:00:00:00:c9:f2:73:d5 fcid 0x18000a dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:e5:5d fcid 0x18000b dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:ab:9b fcid 0x18000c dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:ab:99 fcid 0x18000d dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:e5:5b fcid 0x18000e dynamic
      vsan 1 wwn 10:00:00:00:c9:f2:73:b3 fcid 0x050000 dynamic
      vsan 52 wwn 10:00:00:00:c9:ad:ac:47 fcid 0x18000f dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:a7:93 fcid 0x180010 dynamic
      vsan 52 wwn 10:00:00:00:c9:91:f8:19 fcid 0x180011 dynamic
      vsan 52 wwn 10:00:00:00:c9:9c:e0:77 fcid 0x180012 dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:a7:d3 fcid 0x180013 dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:a3:bb fcid 0x180014 dynamic
      vsan 52 wwn 10:00:00:00:c9:97:3b:c5 fcid 0x180015 dynamic
      vsan 52 wwn 10:00:00:00:c9:f2:73:91 fcid 0x180016 dynamic
      vsan 52 wwn 10:00:00:00:c9:a4:00:91 fcid 0x180017 dynamic
      vsan 52 wwn 10:00:00:00:c9:f2:73:8d fcid 0x180018 dynamic
      vsan 52 wwn 20:0f:00:11:0d:7f:a8:00 fcid 0x180019 dynamic
      vsan 52 wwn 20:0f:00:11:0d:7f:a8:01 fcid 0x18001a dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:a3:b7 fcid 0x18001b dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:a5:27 fcid 0x18001c dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:a3:53 fcid 0x18001d dynamic
      vsan 52 wwn 10:00:00:00:c9:bb:c8:37 fcid 0x18001e dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:76:e5 fcid 0x18001f dynamic
      vsan 20 wwn 10:00:00:00:c9:5b:a3:83 fcid 0xd30000 dynamic
      vsan 52 wwn 10:00:00:00:c9:91:00:00 fcid 0x180020 dynamic
      vsan 52 wwn 10:00:00:00:00:91:f7:f1 fcid 0x180021 dynamic
      vsan 1 wwn 10:00:00:00:c9:5b:4d:e3 fcid 0x050001 dynamic
      vsan 52 wwn 10:00:00:00:c9:97:3b:0f fcid 0x180022 dynamic
      vsan 52 wwn 10:00:00:00:c9:3c:8e:21 fcid 0x180023 dynamic
      vsan 52 wwn 10:00:00:00:c9:97:3b:11 fcid 0x180024 dynamic
      vsan 20 wwn 10:00:00:00:c9:b1:e6:b7 fcid 0xd30001 dynamic
      vsan 52 wwn 10:00:f8:19:00:91:f8:19 fcid 0x180025 dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:a3:8b fcid 0x180026 dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:e4:ff fcid 0x180027 dynamic
      vsan 52 wwn 10:00:00:00:c9:3c:8e:25 fcid 0x180028 dynamic
      vsan 52 wwn 50:06:01:61:44:60:23:4f fcid 0x1800ef dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:d6:b9 fcid 0x180029 dynamic
      vsan 52 wwn 10:00:00:00:c9:ad:ac:43 fcid 0x18002a dynamic
      vsan 52 wwn 20:01:00:00:c9:5b:ab:99 fcid 0x18002b dynamic
      vsan 52 wwn 20:02:00:00:c9:5b:ab:99 fcid 0x18002c dynamic
      vsan 52 wwn 50:06:01:60:44:60:23:4f fcid 0x1801ef dynamic
      vsan 52 wwn 10:00:00:00:c9:9d:1f:bf fcid 0x18002d dynamic
      vsan 52 wwn 10:00:00:00:c9:9d:1f:c1 fcid 0x18002e dynamic
      vsan 52 wwn 10:00:00:00:c9:f2:73:d3 fcid 0x18002f dynamic
      vsan 20 wwn 10:00:00:00:c9:bb:c8:37 fcid 0xd30002 dynamic
      vsan 52 wwn 10:00:00:00:c9:12:34:56 fcid 0x180030 dynamic
      vsan 52 wwn 10:00:00:00:c9:12:34:57 fcid 0x180031 dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:ea:81 fcid 0x180032 dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:ea:7f fcid 0x180033 dynamic
      vsan 20 wwn 10:00:00:00:c9:12:34:56 fcid 0xd30003 dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:e5:1b fcid 0x180034 dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:e5:1d fcid 0x180035 dynamic
      vsan 52 wwn 10:00:00:00:c9:bb:c7:8f fcid 0x180036 dynamic
      vsan 52 wwn 10:00:00:00:c9:bb:cb:8f fcid 0x180037 dynamic
      vsan 52 wwn 10:00:00:00:c9:bb:cb:93 fcid 0x180038 dynamic
      vsan 52 wwn 10:00:00:00:c9:bb:c7:93 fcid 0x180039 dynamic
      vsan 20 wwn 10:00:00:00:c9:12:34:57 fcid 0xd30004 dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:ab:c4 fcid 0x18003a dynamic
      vsan 52 wwn 10:00:00:00:c9:bb:17:b7 fcid 0x18003b dynamic
      vsan 52 wwn 10:00:00:00:c9:a0:ce:2d fcid 0x18003c dynamic
      vsan 52 wwn 10:00:00:00:c9:91:f7:f1 fcid 0x18003d dynamic
      vsan 52 wwn 10:00:00:00:c9:5b:ab:c0 fcid 0x18003e dynamic
      vsan 52 wwn 10:00:00:00:c9:b1:e5:5f fcid 0x18003f dynamic
      vsan 52 wwn 10:00:00:00:c9:e3:06:89 fcid 0x180040 dynamic
      vsan 52 wwn 50:06:01:68:44:60:23:4f fcid 0x1802ef dynamic
      vsan 1 wwn 50:06:01:61:44:60:23:4f fcid 0x0500ef dynamic
      vsan 52 wwn 10:00:00:00:c9:d1:16:24 fcid 0x180041 dynamic
      vsan 52 wwn 10:00:00:00:c9:d1:16:25 fcid 0x180042 dynamic
      vsan 52 wwn 10:00:00:00:c9:d1:0a:6d fcid 0x180043 dynamic
      vsan 20 wwn 10:00:00:00:c9:d1:16:25 fcid 0xd30005 dynamic
      vsan 20 wwn 10:00:00:00:c9:d1:16:24 fcid 0xd30006 dynamic
      vsan 20 wwn ff:f2:00:00:c9:12:34:78 fcid 0xd30007 dynamic
      vsan 20 wwn ff:f2:00:00:c9:d1:16:46 fcid 0xd30008 dynamic
      vsan 52 wwn ff:f2:00:00:c9:d1:0a:8c fcid 0x180044 dynamic
      vsan 20 wwn ff:f3:00:00:c9:d1:16:46 fcid 0xd30009 dynamic
      vsan 52 wwn ff:f0:00:00:c9:d1:0a:8c fcid 0x180045 dynamic
      vsan 52 wwn 10:00:00:00:c9:d1:0a:6c fcid 0x180046 dynamic
      vsan 20 wwn ff:f2:00:00:c9:d1:0a:8c fcid 0xd3000a dynamic
      vsan 20 wwn 10:00:00:00:c9:d1:0a:6d fcid 0xd3000b dynamic
      vsan 52 wwn ff:f2:00:00:c9:d1:16:46 fcid 0x180047 dynamic
      vsan 20 wwn ff:f3:00:00:c9:12:34:78 fcid 0xd3000c dynamic
      vsan 52 wwn ff:f3:00:00:c9:12:34:78 fcid 0x180048 dynamic
      vsan 52 wwn 50:06:01:69:44:60:23:4f fcid 0x1803ef dynamic
      vsan 52 wwn ff:f3:00:00:c9:d1:16:46 fcid 0x180049 dynamic
      vsan 52 wwn 10:00:00:00:c9:12:34:5b fcid 0x18004a dynamic
      vsan 52 wwn 10:00:00:00:c9:12:34:5a fcid 0x18004b dynamic
      vsan 52 wwn ff:f2:00:00:c9:12:34:78 fcid 0x18004c dynamic
      vsan 52 wwn 10:00:00:00:c9:a5:ac:f3 fcid 0x18004d dynamic
      vsan 52 wwn 10:00:00:00:c9:a5:ad:15 fcid 0x18004e dynamic
      vsan 52 wwn 10:00:00:00:c9:a5:ac:f5 fcid 0x18004f dynamic
      vsan 52 wwn 20:01:00:00:c9:a5:ac:f3 fcid 0x180050 dynamic
      vsan 52 wwn 20:02:00:00:c9:a5:ac:f3 fcid 0x180051 dynamic
      vsan 52 wwn ff:f3:00:00:c9:12:34:85 fcid 0x180052 dynamic
      vsan 52 wwn 20:00:00:11:0d:77:9c:00 fcid 0x180053 dynamic
      vsan 52 wwn 20:01:00:11:0d:77:9d:00 fcid 0x180054 dynamic
    interface port-channel3
    interface vfc1
      no shutdown
    interface vfc4
    interface vfc9
      bind interface Ethernet1/9
      no shutdown
    interface vfc10
    interface vfc11
      bind interface Ethernet1/11
      no shutdown
    interface vfc19
      bind interface Ethernet1/19
      no shutdown
    interface vfc21
      bind interface Ethernet1/21
      no shutdown
    interface vfc22
      bind interface Ethernet1/22
      switchport trunk allowed vsan 52
      no shutdown
    interface vfc24
      bind interface Ethernet1/24
      switchport trunk allowed vsan 52
      no shutdown
    interface vfc25
      bind interface Ethernet1/25
      switchport trunk allowed vsan 52
      no shutdown
    interface vfc26
      bind interface Ethernet1/26
      switchport trunk allowed vsan 52
      no shutdown
    interface vfc27
      bind interface Ethernet1/27
      no shutdown
    interface vfc28
      bind interface Ethernet1/28
      no shutdown
    interface vfc29
      bind interface Ethernet1/29
      no shutdown
    interface vfc30
      bind interface Ethernet1/30
      switchport trunk allowed vsan 52
      no shutdown
    interface vfc31
      bind interface Ethernet1/31
      shutdown
    interface vfc32
      bind interface Ethernet1/32
      no shutdown
    interface vfc33
      bind interface Ethernet1/33
      no shutdown
    interface vfc34
      bind interface Ethernet1/34
      no shutdown
    interface vfc35
      bind interface Ethernet1/35
      no shutdown
    interface vfc36
      bind interface Ethernet1/36
      no shutdown
    interface vfc37
      bind interface Ethernet1/37
      no shutdown
    interface vfc38
      bind interface Ethernet1/38
      no shutdown
    interface vfc39
      bind interface Ethernet1/39
      no shutdown
    interface vfc40
      bind interface Ethernet1/40
      no shutdown
    vsan database
      vsan 52 interface vfc1
      vsan 52 interface vfc9
      vsan 52 interface vfc11
      vsan 52 interface vfc19
      vsan 52 interface vfc21
      vsan 52 interface vfc22
      vsan 52 interface vfc24
      vsan 52 interface vfc26
      vsan 52 interface vfc27
      vsan 52 interface vfc28
      vsan 52 interface vfc29
      vsan 52 interface vfc30
      vsan 52 interface vfc31
      vsan 52 interface vfc32
      vsan 52 interface vfc33
      vsan 52 interface vfc34
      vsan 20 interface vfc35
      vsan 52 interface vfc36
      vsan 52 interface vfc37
      vsan 52 interface vfc38
      vsan 52 interface vfc39
      vsan 52 interface vfc40
      vsan 52 interface fc2/1
      vsan 52 interface fc2/2
      vsan 52 interface fc2/3
      vsan 52 interface fc2/4
    interface fc2/1
      switchport trunk allowed vsan 1
      switchport trunk allowed vsan add 52
      switchport trunk mode auto
      no shutdown
    interface fc2/2
      switchport trunk mode auto
      no shutdown
    interface fc2/3
      no shutdown
    interface fc2/4
      no shutdown
    interface Ethernet1/1
    interface Ethernet1/2
      speed 1000
    interface Ethernet1/3
    interface Ethernet1/4
    interface Ethernet1/5
    interface Ethernet1/6
    interface Ethernet1/7
      switchport mode trunk
    interface Ethernet1/8
    interface Ethernet1/9
      switchport mode trunk
      switchport trunk allowed vlan 1,10,20,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/10
    interface Ethernet1/11
      priority-flow-control mode on
      switchport mode trunk
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/12
      switchport mode trunk
    interface Ethernet1/13
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/14
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/15
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/16
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/17
    interface Ethernet1/18
      switchport mode trunk
      switchport trunk allowed vlan 1,30
    interface Ethernet1/19
      switchport mode trunk
      switchport access vlan 10
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/20
      switchport mode trunk
      switchport access vlan 52
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/21
      switchport mode trunk
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/22
    interface Ethernet1/23
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/24
      switchport mode trunk
      switchport access vlan 52
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/25
      switchport mode trunk
      switchport trunk allowed vlan 1,8,30,52
    interface Ethernet1/26
      switchport mode trunk
      switchport access vlan 52
      switchport trunk allowed vlan 1,8,30,52
    interface Ethernet1/27
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/28
      switchport mode trunk
      switchport trunk allowed vlan 1,8,30,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/29
      switchport mode trunk
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/30
      description line
      switchport mode trunk
      switchport access vlan 52
      switchport trunk allowed vlan 1,8,30,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/31
      switchport mode trunk
      switchport trunk allowed vlan 1,10,20,52
    interface Ethernet1/32
      switchport mode trunk
      switchport trunk allowed vlan 1,10,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/33
      switchport mode trunk
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/34
      switchport mode trunk
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/35
      switchport mode trunk
      switchport access vlan 10
      switchport trunk allowed vlan 1,10,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/36
      switchport mode trunk
      switchport trunk allowed vlan 1,30,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/37
      switchport mode trunk
      switchport trunk allowed vlan 1,30,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/38
      switchport mode trunk
      switchport trunk allowed vlan 1,10,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/39
      shutdown
      switchport mode trunk
      switchport trunk allowed vlan 1,10,20,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet1/40
      switchport mode trunk
      switchport trunk allowed vlan 1,52
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet2/1
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet2/2
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet2/3
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface Ethernet2/4
      switchport mode trunk
      flowcontrol receive on
      flowcontrol send on
    interface mgmt0
      ip address 10.192.194.111/20
    system default zone default-zone permit
    system default zone distribute full
    line console
    line vty
    boot kickstart bootflash:/n5000-uk9-kickstart.5.0.3.N1.1b.bin
    boot system bootflash:/n5000-uk9.5.0.3.N1.1b.bin
    interface fc2/1
    interface fc2/2
    interface fc2/3
    interface fc2/4
    zone default-zone permit vsan 20
    zone default-zone permit vsan 52
    zoneset distribute full vsan 1
    zoneset distribute full vsan 20
    zoneset distribute full vsan 52
    !Full Zone Database Section for vsan 1
    zone name bg-qa vsan 1
        member pwwn 10:00:00:00:c9:5b:ab:ca
        member pwwn 21:00:00:0c:50:c3:70:23
        member pwwn 21:00:00:0c:50:c3:70:22
        member pwwn 21:00:00:0c:50:c3:70:16
        member pwwn 21:00:00:0c:50:c3:70:1e
        member pwwn 22:00:00:0c:50:c3:70:26
        member pwwn 22:00:00:18:62:06:76:8a
        member pwwn 22:00:00:11:c6:17:68:c3
        member pwwn 22:00:00:0c:50:c3:70:1d
        member pwwn 22:00:00:0c:50:c3:6f:c2
        member pwwn 22:00:00:11:c6:17:68:dc
        member pwwn 21:00:00:0c:50:c3:6a:d0
        member pwwn 21:00:00:0c:50:79:92:90
        member pwwn 21:00:00:11:c6:17:69:a0
        member pwwn 21:00:00:0c:50:79:93:af
        member pwwn 22:00:00:0c:50:48:10:80
        member pwwn 22:00:00:11:c6:18:46:c6
        member pwwn 22:00:00:0c:50:32:2e:0f
        member pwwn 22:00:00:0c:50:48:10:74
        member pwwn 22:00:00:11:c6:18:46:f2
        member pwwn 21:00:00:00:87:13:cb:d1
        member pwwn 21:00:00:0c:50:79:91:0f
        member pwwn 10:00:00:00:c9:3c:8e:49
        member pwwn 10:00:00:00:c9:5b:ab:c2
        member pwwn 10:00:00:00:c9:5b:af:f3
    zone name sf_RAM vsan 1
        member pwwn 10:00:00:00:c9:5b:af:c9
        member pwwn 21:00:00:0c:50:b4:8e:20
    zone name anand vsan 1
        member pwwn 10:00:00:00:c9:65:69:31
        member pwwn 22:00:00:18:62:06:7f:f6
    zone name syedzone vsan 1
        member fwwn 20:11:00:0d:ec:56:7b:40
        member pwwn 50:06:01:60:44:60:23:4f
    zone name bg_qa vsan 1
    zoneset name TOM vsan 1
        member bg-qa
    zoneset name bg_dvt vsan 1
        member sf_RAM
    zoneset name lancer vsan 1
        member anand
    zoneset name bg-qa vsan 1
    zoneset name syed vsan 1
        member syedzone
    zoneset activate name lancer vsan 1
    !Full Zone Database Section for vsan 20
    zone name amrita_zone1 vsan 20
        member pwwn 10:00:00:00:c9:5b:a3:83
        member pwwn 22:00:00:04:cf:89:19:67
        member pwwn 22:00:00:0c:50:48:10:80
        member pwwn 22:00:00:11:c6:18:46:f2
        member pwwn 22:00:00:0c:50:79:93:ae
    zone name amr_zset vsan 20
    zoneset name amr_zset vsan 20
        member amrita_zone1
    zoneset activate name amr_zset vsan 20
    !Full Zone Database Section for vsan 52
    zone name vinod vsan 52
        member pwwn 50:06:01:69:44:60:23:4f
        member pwwn ff:f3:00:00:c9:12:34:78
        member pwwn 10:00:00:00:c9:12:34:5b
        member pwwn 10:00:00:00:c9:12:34:57
    zone name neha vsan 52
    zone name siv1 vsan 52
        member pwwn 10:00:00:00:c9:ad:ac:43
        member pwwn 50:06:01:61:44:60:23:4f
        member pwwn 10:00:00:00:c9:ad:ac:47
    zone name neha1 vsan 52
        member pwwn 10:00:00:00:c9:5b:ab:ad
        member pwwn 50:06:01:60:44:60:23:4f
    zone name neha2 vsan 52
        member pwwn 50:06:01:60:44:60:23:4f
        member pwwn 10:00:00:00:c9:5b:ab:a9
    zone name neha3 vsan 52
        member pwwn 10:00:00:00:c9:9d:1f:bf
        member pwwn 50:06:01:60:44:60:23:4f
    zone name neha4 vsan 52
        member pwwn 50:06:01:60:44:60:23:4f
        member pwwn 10:00:00:00:c9:9d:1f:c1
    zone name chetan vsan 52
        member pwwn 10:00:00:00:c9:f2:73:d3
        member pwwn 50:06:01:60:44:60:23:4f
        member pwwn 10:00:00:00:c9:ad:ac:47
    zone name siv2 vsan 52
        member pwwn 10:00:00:00:c9:d1:0a:6d
        member pwwn ff:f2:00:00:c9:d1:0a:8c
        member pwwn 22:00:00:0c:50:79:93:af
        member pwwn 22:00:00:0c:50:79:92:90
        member pwwn 22:00:00:0c:50:79:91:0f
        member pwwn 20:01:00:11:0d:77:9d:00
    zone name sroy vsan 52
        member pwwn 10:00:00:00:c9:b1:ea:7f
        member pwwn 50:06:01:60:44:60:23:4f
        member pwwn 10:00:00:00:c9:5b:ab:99
        member pwwn 10:00:00:00:c9:bb:cb:8f
        member pwwn 10:00:00:00:c9:5b:ab:c4
        member pwwn 10:00:00:00:c9:d1:16:25
        member pwwn 50:06:01:61:44:60:23:4f
        member pwwn 10:00:00:00:c9:a5:ac:f3
    zone name manju vsan 52
        member pwwn 10:00:00:00:c9:bb:c7:8f
        member pwwn 50:06:01:61:44:60:23:4f
    zone name ram vsan 52
        member pwwn 50:06:01:60:44:60:23:4f
        member pwwn 10:00:00:00:c9:a0:ce:2d
        member pwwn 10:00:00:00:c9:bb:17:b7
        member pwwn 10:00:00:00:c9:5b:a5:27
        member pwwn 10:00:00:00:c9:91:f7:f1
        member pwwn 10:00:00:00:c9:b1:e5:5f
    zone name jana vsan 52
        member pwwn 10:00:00:00:c9:91:f7:f1
        member pwwn 50:06:01:60:44:60:23:4f
    zone name priya vsan 52
        member pwwn 10:00:00:00:c9:e3:06:89
        member pwwn 50:06:01:60:44:60:23:4f
    zoneset name IBMraptor vsan 52
        member vinod
        member siv1
        member neha1
        member neha2
        member neha3
        member neha4
        member chetan
        member siv2
        member sroy
        member manju
        member ram
        member priya
    zoneset name ananda vsan 52
    zoneset name vinod vsan 52
    zoneset activate name IBMraptor vsan 52
    no system default switchport shutdown san
    Cisco-5020# sh system internal dcbx info interface ethernet 1/38
    Interface info for if_index: 0x1a025000(Eth1/38)
    tx_enabled: TRUE
    rx_enabled: TRUE
    dcbx_enabled: TRUE
    DCX Protocol: CIN
    Port MAC address:  00:0d:ec:b2:15:6d
    DCX Control FSM Variables: seq_no: 0x1, ack_no: 0x0,my_ack_no: 0x0, peer_seq_no:
    0x0 oper_version: 0x0,  max_version: 0x0 fast_retries 0x0
    Lock Status: UNLOCKED
    PORT STATE: UP
    LLDP Neighbors
    No DCX tlvs from the remote peer
    6 Features on this intf for Protocol CIN(0)
    3 Features on this intf for Protocol CEE(1)
    6 Features on this intf for Protocol CIN(0)
    Feature type LLS (6)sub_type FCoE Logical Link Status (0)
    feature type 6(LLS)sub_type 0
    Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
         feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 0
         remote_tlv_not_present_notification_sent 0
    Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
         disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x1d9
    Desired config cfg length: 1 data bytes:00
    Operating config cfg length: 0 data bytes:
    Peer config cfg length: 0 data bytes:
    Feature type PFC (3)
    feature type 3(PFC)sub_type 0
    Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
         feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
         remote_tlv_not_present_notification_sent 0
    Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
         disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x179
    Desired config cfg length: 1 data bytes:08
    Operating config cfg length: 0 data bytes:
    Peer config cfg length: 0 data bytes:
    Feature type App(Fcoe) (5)sub_type FCoE (0)
    feature type 5(App(Fcoe))sub_type 0
    Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
         feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
         remote_tlv_not_present_notification_sent 0
    Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
         disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x179
    Desired config cfg length: 1 data bytes:08
    Operating config cfg length: 0 data bytes:
    Peer config cfg length: 0 data bytes:
    Feature type PriMtu (8)
    feature type 8(PriMtu)sub_type 0
    Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
         feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
         remote_tlv_not_present_notification_sent 0
    Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
         disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x179
    Desired config cfg length: 16 data bytes:24    00    24    00    24    00    08    6e    24    00    24    00    24    00    24    00
    Operating config cfg length: 0 data bytes:
    Peer config cfg length: 0 data bytes:
    Feature type PriGrp (2)
    feature type 2(PriGrp)sub_type 0
    Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
         feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
         remote_tlv_not_present_notification_sent 0
    Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
         disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0x179
    Desired config cfg length: 24 data bytes:32    32    00    00    00    00    00    00    00    0f    00    0f    00    0e    20    64    00    0e    00    0e
       00    0e    00    0e
    Operating config cfg length: 0 data bytes:
    Peer config cfg length: 0 data bytes:
    Feature type LLS (6)sub_type LAN Logical Link Status (1)
    feature type 6(LLS)sub_type 1
    Feature State Variables: oper_version 0 error 0 local error 0 oper_mode 0
         feature_seq_no 0 remote_feature_tlv_present 0 remote_tlv_aged_out 1
         remote_tlv_not_present_notification_sent 0
    Feature Register Params: max_version 0, enable 1, willing 0 advertise 1
         disruptive_error 0 mts_addr_node 0x101 mts_addr_sap 0xaf
    Desired config cfg length: 1 data bytes:80
    Operating config cfg length: 0 data bytes:
    Peer config cfg length: 0 data bytes:
    Traffic Counters
    DCBX pkt stats:
        Total frames out: 20296
        Total Entries aged: 27
        Total frames in: 0
        DCBX frames in: 0
        Total frames received in error: 0
        Total frames discarded: 0
        Total TLVs unrecognized: 0
    Cisco-5020#
    Cisco-5020#
    Cisco-5020#
    I am new to this PFC, and first time trying to configure so you can see nothing being configured.

  • 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,
    Florian

    I 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?

  • Fabric Manager not on switches.

    Greetings,
    I just took delivery of some 9216A's and found that Fabric Manager is not on them anymore. Device Manager is but for how long?? I have to download FM or get it for the non existant CD's. When did that start? Being a typical Cisco end user means I never get a login to download software as my vendor is supposed to look after me. It was much easier when it was on the switch. Perhaps not everyone works in sites with easy access to the internet...
    Stephen

    Thanks for the reply. Now I am keen to work out why it is so big. I hope it not just bloated for the sake of it.
    Stephen

  • Nexus 5000 as NTP client

    We run 6509 core routers as NTP servers to other IOS routers/switches & servers of several OS flavours.
    All good.
    Recently added some Nexus 5000s and cannot get them to lock.
    No firewalls or ACLs in the path
    6509 (1 of 4) state:
    LNPSQ01CORR01>sh ntp ass
          address         ref clock     st  when  poll reach  delay  offset    disp
    + 10.0.1.2         131.188.3.220     2   223  1024  377     0.5   -6.23     0.7
    +~130.149.17.21    .PPS.             1   885  1024  377    33.7   -0.26     0.8
    *~138.96.64.10     .GPS.             1   680  1024  377    22.7   -2.15     1.0
    +~129.6.15.29      .ACTS.            1   720  1024  377    84.9   -3.37     0.6
    +~129.6.15.28      .ACTS.            1   855  1024  377    84.8   -3.30     2.3
    * master (synced), # master (unsynced), + selected, - candidate, ~ configured
    Nexus state:
    BL01R01B10SRVS01# sh ntp peer-status
    Total peers : 4
    * - selected for sync, + -  peer mode(active),
    - - peer mode(passive), = - polled in client mode
        remote               local              st  poll  reach   delay
    =10.0.1.1               10.0.201.11            16   64       0   0.00000
    =10.0.1.2               10.0.201.11            16   64       0   0.00000
    =10.0.1.3               10.0.201.11            16   64       0   0.00000
    =10.0.1.4               10.0.201.11            16   64       0   0.00000
    Nexus config:
    ntp distribute
    ntp server 10.0.1.1
    ntp server 10.0.1.2
    ntp server 10.0.1.3
    ntp server 10.0.1.4
    ntp source 10.0.201.11
    ntp commit
    interface mgmt0
      ip address 10.0.201.11/24
    vrf context management
      ip route 0.0.0.0/0 10.0.201.254
    Reachability to the NTP source...
    BL01R01B10SRVS01# ping 10.0.1.1 vrf management source 10.0.201.11
    PING 10.0.1.1 (10.0.1.1) from 10.0.201.11: 56 data bytes
    64 bytes from 10.0.1.1: icmp_seq=0 ttl=253 time=3.487 ms
    64 bytes from 10.0.1.1: icmp_seq=1 ttl=253 time=4.02 ms
    64 bytes from 10.0.1.1: icmp_seq=2 ttl=253 time=3.959 ms
    64 bytes from 10.0.1.1: icmp_seq=3 ttl=253 time=4.053 ms
    64 bytes from 10.0.1.1: icmp_seq=4 ttl=253 time=4.093 ms
    --- 10.0.1.1 ping statistics ---
    5 packets transmitted, 5 packets received, 0.00% packet loss
    round-trip min/avg/max = 3.487/3.922/4.093 ms
    BL01R01B10SRVS01#
    Are we missing some NTP or managment vrf setup in the Nexus 5Ks??
    Thanks
    Rob Spain
    UK

    I have multiple 5020's, 5548's, and 5596's, and they all experience this same problem. Mind you I run strictly layer 2. I don't even have feature interface-vlan enabled. I tried: "ntp server X.X.X.X use-vrf management" as well as "clock protocol ntpt". These didn't help. 
    I was told by TAC that there is a bug (sorry I do not have the ID), but basically NTP will not work over the management VRF. The only way I got NTP to work, was by enabling the feature interface-vlan, and adding a vlan interface with an IP and retrieving NTP through this interface. 
    I upgraded to 5.2 (1) in hopes that this would fix the issue. but it did not. 

  • Cisco Fabric Manager 5.0.7

    Dear Team!
    I have software Cisco Fabric Manager 4.2a (in SAN management server based on Windows Server 2003) Standalone version, which managed our existing fabrics (we have 2) now. In case of OS "Windows 2003 server" going to End of Life/Support, we started prepare new SAN management server based on Windows Server 2008. On this new server I installed new version of software Cisco Fabric Manager 5.0.7 Standalone.
    Question: Is it possible to manage by old Cisco Fabric Manager 4.2 our fabrics after discovere our (existing) fabric, from new SAN management server with C.F.M 5.0.7? Or after discovere management function of fabrics will take new server? Can I manage one fabric from two different servers with Cisco Fabric Manager Standalone software (I mean we have production SAN management server with C.F.M. and SAN management server with C.F.M. for DR site)?

    Hello,
    Thanks for your reply!
    I need two servers with FM as temporary, for implementation and test period only. After that, we will decommission old server and use only one. I asked because I never do discovery existing fabrics in FM, and not sure that if after discovery our fabrics from new server I can manage them from old server. In this case I raised this question.
    As I understood that I can manage our fabrics from two different servers (with different version of FM), but not at one time. Please can you confirm.
    Thanks

  • Trouble installing Fabric Manager 5.0.7 on 2008R2

    Hello all,
    We are about to upgrade our older MDS-9124s to MDS-9148s and I wanted to install the new Fabric Manager. I am trying to install version 5.0.7. I am having a couple issues but am not sure if they are all related. First if I try to select the install links from within start they do not work. The only way I can get the install to start is double clicking the jre file direct. The installation process starts and the dies at what appears to be trying to start postgresql with an error message that initdb cannot be processed because the libpq.dll file cannot be found. If I try to re-run the install it dies becuase the postgre user already exists. I can delete that local account and the installation process will restart only to once again die with the dll error.
    Just for grins I ran the postgresql install seperate and it seems to go through a lot more prompts but figured this was not the proper way to get it installed so canceled it. I also tried running the install from the cmd line as I found in another post and it dies at basically the same point but has a net error message 2221. It looks at though this to means that the user created cannot be accessed so postgresql will not start.
    I am disabling my virus software while trying all of these items.
    Suggestions??/
    Brent

    @dynamoxxx,
         This is a new install and I just completed getting it installed on Friday. I had to actually log onto the server as the local administrator to get it to install. An Admin equivalent account apparently was not good enough. Once I did that it completed just fine. I have come across another apparetly known isse and that is if you exit Fabric Manager and try to go directly back in a box pops up that says Fabric Manager is already running. This is apparently because java never shuts down. You kill the javaws servise and Fabric Manager starts back up without any issue. Of course this also works if you log off the server and back on. This was somthing that I talked with TAC about this morning and since they have quit working on Fabric Manager is not going to be fixed.
    That brings me to DCNA. I am moving to Cisco Prime for the rest of my infrastructure and TAC says that DCNA is a part of that or that basically is DCNA. They were telling me that based upon the code level I am running (5.0(1a)) on my switches that Fabric Manager is better. If  I was running newer 6.2 or 5.2 code then use the DCNM and apparently 5.2(8) is newer than 6.2. They also recommended me waiting until 5.2(8b) come out before upgrading the switches and then moving to DCNA. I will figure out that step once I get my SAN migration completed in a few weeks. Until then I am planning to keep what I have.
    Brent

Maybe you are looking for

  • Access forms File stored in database

    Can any body help in this Call_Form('i:\test\fmb\entgrp'); here entgrp is the FMX file stored in Server which is mapped to i: 1 Now if i want to use this call_form to call the file stored in database what is the syntax 2 and How to invoke this file f

  • Time Machine from old Mac to new Mac

    I recently changed my Macbook Pro (mid 2010) to one of the newer models. I use an external HD via an Airport Extreme (I know its not recommended, but its been working perfectly for over 18 months) I attempted to use a time machine backup to setup the

  • Bridge: Saving color changes in Camera Raw through final output.

    Hello, I am on a Mac and I am trying to use Bridge's Camera Raw to do some simple corrections. I have made a collection to select the photos I want to correct. Now that I am done I am trying to do a Batch Rename and select those files to output to a

  • The backup disk image"/Volumes/TimeMachine/Macintosh.sparsebundle" could not be created (error-2).

    Time machine problem. Backups from my 1TB imac 2009, to a 6 TB RAID configured MyBook Live Duo (3TB+3TB) will not work over ethernet cable. I have 800GB on my 1TB internal drive, have tried the option, command p+r and it does not work. Still get two

  • Acrobat X - Crashes in Lion without fail

    Acrobat X, without fail, will crash every single time it is launched no matter what, no matter how, within 30 seconds of it opening. I've uninstalled and reinstalled, cleaned out Libraries and gotten rid of every trace file, and I've run every update