Table Of Contents
Cisco Nexus B22 Fabric Extender for HP
Getting Started GuideInformation about the Cisco Nexus B22 Fabric Extender for HP
Finding the Latest Documentation Online
Installing the Cisco Nexus B22 Fabric Extender for HP
Configuring the Cisco Nexus B22 Fabric Extender for HP
Associating a Fabric Extender to a Fabric Interface
Associating a Fabric Extender to an Ethernet Interface
Associating a Fabric Extender to an EtherChannel
Disassociating a Fabric Extender from an Interface
Configuring the Fabric Extender
Displaying Fabric Extender Information
Displaying Configuration Information
Displaying Chassis Management Information
Cisco Nexus B22 Fabric Extender for HP
Getting Started Guide
This Getting Started Guide describes the Cisco Nexus B22 Fabric Extender for HP and how to start using it. This product is referred to by HP as the Cisco Fabric Extender for HP Bladeystem. This Getting Started Guide includes the following sections:
•Information about the Cisco Nexus B22 Fabric Extender for HP
•Installing the Cisco Nexus B22 Fabric Extender for HP
•Configuring the Cisco Nexus B22 Fabric Extender for HP
•For HP Integrity Superdome 2, the minimum F/W bundle is 2.51.102
Information about the Cisco Nexus B22 Fabric Extender for HP
The Cisco Nexus B22 Fabric Extender for HP provides an extension of the Cisco Nexus switch fabric to the HP blade server edge
The Cisco Nexus B22 Fabric Extenders behave as remote line cards for a parent Cisco Nexus 5000 Series switch. The Fabric Extenders are essentially extensions of the parent Cisco Nexus switch fabric, with the Fabric Extenders and the parent Cisco Nexus switch together forming a distributed modular system.
Up to 24 Cisco Nexus B22 Fabric Extenders can be connected to a single Nexus 5000 Series switch, allowing a single distributed modular system to scale to 384 HP blade servers.
Each Cisco Nexus B22 Fabric Extender connects via 1 or 10 Gigabit Ethernet to up to 16 servers within a HP BladeSystem and the HP Integrity Superdome 2 chassis, and contains 8 10 Gigabit Ethernet fabric uplinks towards the Cisco Nexus 5000 Series switch. Multiple low cost options are available for fabric connections between the Cisco Nexus B22 and the Cisco Nexus 5000 series switch. Low-cost Connections up to 10 meters can be made with copper Twin-ax cable, and longer connections up to 100 meters can use the Fabric Extender Transceiver. Other standard 10 Gigabit Ethernet optics such as 10Gbase-SR and 10Gbase-LR are also supported for these fabric connections.
Finding the Latest Documentation Online
Use the following links to check for the latest documentation for your server product:
•http://www.cisco.com/en/US/products/ps9670/tsd_products_support_series_home.html
•http://h18004.www1.hp.com/products/blades/components/c-class-tech-installing.html
•http://www.hp.com/go/Integrity_Servers-docs
Check these links often to verify that your documentation is up to date.
Shipping Box Contents
The Cisco Nexus B22 Fabric Extender for HP shipping box contains:
•Cisco Nexus B22 Fabric Extender for HP, with 16 internal host ports and 8 external network ports.
•This box may contain 16 Fabric Extender Transceivers. The product ID of the bundle with the Cisco Nexus B22 Fabric Extender and the Fabric Extender Tranceiver is N2K-B22HP-F.
•1 CD that contains
–Getting Started Guide
–Regulatory Compliance and Safety Information
–HP End User License Agreement letter
–Warranty Document
Figure 1 shows the Cisco Nexus B22 Fabric Extender for HP.
Figure 1 Cisco Nexus B22 Fabric Extender for HP
1Midplane connector
2Eight external network ports
3Installation handle
4Unit ID (UID) LED and Health LED
HP Blade System Architecture
Figure 2 shows the rear view of the blade benclosure, in which you install the switch module.
Figure 2 Rear View of the Blade Enclosure
Figure 3 shows the rear of the HP Superdome 2 IOX Enclosure.
Figure 3 Rear of HP Superdome 2 IOX Enclosure
Server Blade Signal Compute Enclosure Interconnect Bay Interconnect Bay LabelsNIC 1(embedded)
1
NIC 2(embedded)
2
NIC 3(embedded)
1
NIC 4(embedded)
2
Consider these prerequisites before you install the switch module:
•Fill any unoccupied interconnect bays or any unoccupied power module bays in the blade enclosure with blanks.
•Identify the bays in which you will insert the switch modules. Plan to install the first switch module in bay 1, the second in bay 2, and so on up to bay 8, if possible. The bay in which you choose to install each switch module depends on whether mezzanine or Ethernet cards are installed in the blade enclosure and how they are configured. See the blade enclosure documentation information about installing and configuring the mezzanine or Ethernet cards.
•See the HP c-Class or HP Integrity Superdome 2 documentation for information on the port mapping between blade enclosures and the switch modules.
Installing the Cisco Nexus B22 Fabric Extender for HP
Caution Properly ground yourself before handling the switch.
Populate all the enclosure interconnect bays with an interconnect module or one of the blank panels provided with the enclosure. For the HP Integrity Superdome 2, the Fabric Extender will go to Bay 1, Bay 2 or both.
To install the Cisco Nexus B22 Fabric Extender for HP in the enclosure:
1. Locate the appropriate interconnect bay at the rear of the enclosure. See the setup and installation guide provided with the enclosure.
2. Press the handle latch to release the handle. See Figure 4.
Figure 4 Releasing the Installation Handle
Note The Cisco Nexus B22 Fabric Extender for HP is a hot-pluggable device. The enclosure may be on or off during installation.
3. Align the Cisco Nexus B22 Fabric Extender for HP with the appropriate interconnect bay, according to the specific configuration for the enclosure. For the HP Integrity Superdome 2, only Bay 1 and Bay 2 are available. Push the switch firmly into the interconnect bay. See Figure 5.
Figure 5 Installing the Fabric Extender Into an Interconnect Bay
4. Press the installation handle into the latch to lock the switch into place.
5. Connect the cables.
6. Configure the Cisco Nexus 5000 switch to recognize and boot up the Cisco Nexus B22 Fabric Extender for HP.
Updating NX-OS
To achieve the best performance, HP recommends updating to the latest NX-OS software version.
The Cisco Nexus B22 Fabric Extender for HP downloads the necessary firmware from the connected Cisco Nexus 5x00 switch. You can update the Cisco Nexus 5x00 Switch without any disruptions using the install all command. Contact the company from whom your Cisco Nexus 5x00 Switch was purchased.
For units purchased through HP, see the HP StorageWorks Single Point of Connectivity Knowledge (SPOCK) website at www.hp.com/storage/spock for the latest HP supported NX-OS version.
If your Nexus 5000 was purchased through HP, obtain the most current NX-OS software from the HP Support Center website:
http://h20565.www2.hp.com/portal/site/hpsc/public
You can download NX-OS software from the Cisco website: http://www.cisco.com/cisco/software/navigator.html?mdfid=282076290&i=rm
If your units are purchased through Cisco, see Cisco Nexus 5000 Series NX-OS Software Upgrade and Downgrade Guide for instructions on how to download NX-OS from Cisco.
The Cisco Nexus B22 Fabric Extender for HP is managed by its parent Cisco Nexus 5000 Series switch over the fabric interfaces through a zero-touch configuration model. You upgrade the Fabric Extender by upgrading the software on the parent Cisco Nexus 5000 Series switch.
When a Fabric Extender is properly associated with a parent switch, the following upgrade operations are performed:
•The switch checks the software image compatibility and upgrades the Fabric Extender if necessary.
•The switch pushes the configuration data to the fabric extender. The Fabric Extender does not store any configuration locally.
•The Fabric Extender updates the switch with its operational status. All fabric extender information is displayed using the switch commands for monitoring and troubleshooting.
In-Service Software Upgrades (ISSUs) are supported on the Cisco Nexus 5000 Series switches. An ISSU can update the software images on your device without disrupting data traffic. An ISSU updates the Kickstart, System, and Fabric Extender image.
The install all command triggers the ISSU on Cisco Nexus 5000 Series switches and the Cisco Nexus B22 Fabric Extender for HP. The command provides the following benefits:
•You can upgrade the Cisco Nexus 5000 Series switches and the Cisco Nexus B22 Fabric Extender for HP using just one command.
•You can receive descriptive information about the intended changes to your system before you continue with the installation. For example, it identifies potential disruptive upgrades.
•You can continue or cancel the upgrade when you see this question (the default is no):
Do you want to continue (y/n) [n] : y•You can upgrade the Cisco NX-OS software using a nondisruptive procedure.
•The command automatically checks the image integrity, which includes the running kickstart and system images. The command sets the kickstart and system boot variables.
•The command performs a platform validity check to verify that a wrong image is not used.
•The Ctrl-c escape sequence gracefully ends the install all command. The command sequence completes the update step in progress and returns to the EXEC prompt.
•After issuing the install all command, if any step in the sequence fails, the upgrade ends.
•The following message appears to warn you about the impact of upgrading the power sequencer:
Warning: please do not remove or power off the module at this time. Note: Power-seq upgrade needs a power-cycle to take into effect. On success of power-seq upgrade, SWITCH OFF THE POWER to the system and then, power it up.•You can force a disruptive upgrade.
For additional information, see the Cisco Nexus 5000 Series NX-OS Software Upgrade and Downgrade Guide.
Configuring the Cisco Nexus B22 Fabric Extender for HP
This section describes how to configure a Cisco Nexus B22 Fabric Extender for HP with a Cisco Nexus 5000 Series switch and includes the following sections:
•Associating a Fabric Extender to a Fabric Interface
•Configuring the Fabric Extender
•Displaying Fabric Extender Information
Associating a Fabric Extender to a Fabric Interface
A Fabric Extender is connected to the switch through physical Ethernet interfaces or an EtherChannel. By default, the switch does not allow the attached Fabric Extender to connect until it has been assigned a chassis ID and is associated with the connected interface.
Note The Fabric Extender may connect to the switch through a number of separate physical Ethernet interfaces or at most one EtherChannel interface.
This section includes the following topics:
•Associating a Fabric Extender to an Ethernet Interface
•Associating a Fabric Extender to an EtherChannel
•Disassociating a Fabric Extender from an Interface
Associating a Fabric Extender to an Ethernet Interface
To associate the Fabric Extender to an Ethernet interface, perform this task:
This example shows how to associate the Fabric Extender to an Ethernet interface on the switch:
switch# configure terminal Enter configuration commands, one per line. End with CNTL/Z. switch(config)# interface ethernet 1/19 switch(config-if)# switchport mode fex-fabric switch(config-if)# fex associate 102This example shows how to display the association of the Fabric Extender and the switch:
switch# show interface ethernet 1/19 fex-intf Fabric FEX Interface Interfaces ---------------------------------------------------Eth1/19 Eth100/1/16 Eth100/1/15 Eth100/1/14 Eth100/1/13Eth100/1/12 Eth100/1/11 Eth100/1/10 Eth100/1/9Eth100/1/8 Eth100/1/7 Eth100/1/6 Eth100/1/5Eth100/1/4 Eth100/1/3 Eth100/1/2 Eth100/1/1Associating a Fabric Extender to an EtherChannel
To associate the Fabric Extender to an EtherChannel, perform this task:
This example shows how to associate the Fabric Extender to an EtherChannel interface on the switch:
switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.switch(config)# interface port-channel 2switch(config-if)# switchport mode fex-fabricswitch(config-if)# fex associate 100switch(config-if)# exitswitch(config)# interface ethernet 1/19switch(config-if)# switchport mode fex-fabricswitch(config-if)# fex associate 100switch(config-if)# channel-group 2switch(config-if)# exitswitch(config)# interface ethernet 1/20switch(config-if)# switchport mode fex-fabricswitch(config-if)# fex associate 100switch(config-if)# channel-group 2switch(config-if)# exitswitch(config)# interface ethernet 1/21switch(config-if)# switchport mode fex-fabricswitch(config-if)# fex associate 100switch(config-if)# channel-group 2switch(config-if)# exitswitch(config)# interface ethernet 1/22switch(config-if)# switchport mode fex-fabricswitch(config-if)# fex associate 100switch(config-if)# channel-group 2switch(config-if)# exit
Note You have to associate each Ethernet interface that is a members of the EtherChannel as a fabric interface as shown in the above example.
This example shows how to display the association of the Fabric Extender and the switch:
switch# show interface port-channel 2 fex-intf Fabric FEX Interface Interfaces ---------------------------------------------------Po2 Eth100/1/1 Eth100/1/2 Eth100/1/3 Eth100/1/4Eth100/1/5 Eth100/1/6 Eth100/1/7 Eth100/1/8Eth100/1/9 Eth100/1/10 Eth100/1/11 Eth100/1/12Eth100/1/13 Eth100/1/14 Eth100/1/15 Eth100/1/16Disassociating a Fabric Extender from an Interface
To disassociate the Fabric Extender from an interface, perform this task:
Command Purposeswitch(config-if)# no fex associate
Disassociates the Fabric Extender unit attached to the interface.
Configuring the Fabric Extender
To configure global features for a Fabric Extender, perform this tasks:
Caution Changing the number of uplinks with the pinning max-links command or the no pinning max-links command disrupts all the host interface ports of the Fabric Extender.
Redistributing the Links
When you provision the Fabric Extender with statically pinned interfaces, the downlink host interfaces on the Fabric Extender are pinned to the fabric interfaces in the order they were initially configured. If you want to maintain a specific relationship of host interfaces to fabric interface across reboots, you should re-pin the links.
You may want to perform this function in these two situations:
•A change in the max-links configuration.
•If you need to maintain the pinning order of host interfaces to fabric interfaces.
Changing the Number of Links
If you initially configured port 19 on the parent switch as your only fabric interface, all 16 host interfaces are pinned to this port. If you provision another port, for example 20, then you must enter the pinning max-links 2 command to redistribute the host interfaces. All host interfaces are brought down and host interfaces 1 to 8 are pinned to fabric interface 19 and host interfaces 9 to 16 are pinned to fabric interface 20.
Maintaining the Pinning Order
The pinning order of the host interfaces is initially determined by the order in which the fabric interfaces were configured. In this example, four fabric interfaces were configured in the following order:
switch(config-fex)#switch(config-fex)#switch(config-fex)# show interface ethernet 1/19 fex-intfFabric FEXInterface Interfaces---------------------------------------------------Eth1/19 Eth100/1/4 Eth100/1/3 Eth100/1/2 Eth100/1/1switch(config-fex)# show interface ethernet 1/20 fex-intfFabric FEXInterface Interfaces---------------------------------------------------Eth1/20 Eth100/1/8 Eth100/1/7 Eth100/1/6 Eth100/1/5switch(config-fex)# show interface ethernet 1/21 fex-intfFabric FEXInterface Interfaces---------------------------------------------------Eth1/21 Eth100/1/12 Eth100/1/11 Eth100/1/10 Eth100/1/9switch(config-fex)# show interface ethernet 1/22 fex-intfFabric FEXInterface Interfaces---------------------------------------------------Eth1/22 Eth100/1/16 Eth100/1/15 Eth100/1/14 Eth100/1/13The next time that you reboot the Fabric Extender, the configured fabric interfaces are pinned to the host interfaces in an ascending order by port number of the fabric interface. If you want to configure the same fixed distribution of host interfaces without restarting the Fabric Extender, enter the fex pinning redistribute command.
To redistribute the host interfaces on the Fabric Extender, perform this task:
Command Purposeswitch# fex pinning redistribute chassis
Redistributes the host connections. The range of the chassis ID is from 100 to 199.
This example shows how to redistribute the host interfaces on a Fabric Extender:
switch# fex pinning redistribute 100
Caution The fex pinning redistribute command disrupts all the host interface ports of the Fabric Extender.
For additional information about configuring the Cisco Nexus B22 Fabric Extender for HP and Cisco Nexus 5000 Series Switches, see the following documentation:
•Cisco Nexus 2000 Series Fabric Extender Software Configuration Guide http://www.cisco.com/en/US/docs/switches/datacenter/nexus2000/sw/configuration/guide/rel_4_0_1a/NX2000CLIConfig.html
•Cisco Nexus 5000 Series NX-OS Software Configuration Guide
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/configuration/guide/cli_rel_4_0_1a/CLIConfigurationGuide.htmlDisplaying Fabric Extender Information
This section describes the show commands that are available to display the configuration and status of the Fabric Extender and includes the following topics:
•Displaying Configuration Information
•Displaying Chassis Management Information
Displaying Configuration Information
To display configuration information about the defined interfaces, perform one of these tasks:
This example shows how to display all the attached Fabric Extender units:
switch(config-fex)# show fexFEX FEX FEX FEXNumber Description State Model Serial------------------------------------------------------------------------100 FEX0100 Online N2K-B22HP-P FOC1516ZZLSswitch(config-fex)#This example shows how to display the detailed status of a specific Fabric Extender:
switch# show fex 100 detail FEX: 100 Description: FEX0100 state: OnlineFEX version: 5.0(3)N2(1) [Switch version: 5.0(3)N2(1)]FEX Interim version: 5.0(3)N2(0.236)Switch Interim version: 5.0(3)N2(0.236)Extender Model: N2K-B22HP-P, Extender Serial: FOC1514256SPart No: 73-13780-05Bay: 2Rack: UnnamedRackEnclosure: 1Z34AB789012Enclosure Serial: USE6401VEXRack Id: Default RUIDCard Id: 145, Mac Addr: e8:b7:48:4b:e8:82, Num Macs: 64Module Sw Gen: 21 [Switch Sw Gen: 21]post level: completepinning-mode: static Max-links: 4Fabric port for control traffic: Eth1/19Fabric interface state:Eth1/19 - Interface Up. State: ActiveEth1/20 - Interface Up. State: ActiveEth1/21 - Interface Up. State: ActiveEth1/22 - Interface Up. State: ActiveFex Port State Fabric PortEth100/1/1 Up Eth1/19Eth100/1/2 Down Eth1/19Eth100/1/3 Down Eth1/19Eth100/1/4 Down Eth1/19Eth100/1/5 Down Eth1/20Eth100/1/6 Down Eth1/20Eth100/1/7 Down Eth1/20Eth100/1/8 Down Eth1/20Eth100/1/9 Up Eth1/21Eth100/1/10 Down Eth1/21Eth100/1/11 Down Eth1/21Eth100/1/12 Down Eth1/21Eth100/1/13 Down Eth1/22Eth100/1/14 Down Eth1/22Eth100/1/15 Down Eth1/22Eth100/1/16 Down Eth1/22Logs:06/22/2011 21:43:50.260429: Module register received06/22/2011 21:43:50.261621: Image Version Mismatch06/22/2011 21:43:50.261906: Registration response sent06/22/2011 21:43:50.262180: Requesting satellite to download image06/22/2011 21:47:36.78886: Deleting route to FEX06/22/2011 21:47:36.83969: Module disconnected06/22/2011 21:47:36.85724: Module Offline06/22/2011 21:53:08.757010: Module register received06/22/2011 21:53:08.758178: Registration response sent06/22/2011 21:53:09.6227: Module Online Sequence06/22/2011 21:53:11.736373: Module Online06/22/2011 22:09:48.190062: Deleting route to FEX06/22/2011 22:09:48.196995: Module disconnected06/22/2011 22:09:48.198227: Deleting route to FEX06/22/2011 22:09:48.203294: Module disconnected06/22/2011 22:09:48.204160: Offlining Module06/22/2011 22:09:48.204977: Module Offline Sequence06/22/2011 22:09:48.527385: Module Offline06/22/2011 22:10:23.644325: Module register received06/22/2011 22:10:23.645444: Registration response sent06/22/2011 22:10:23.864695: Module Online Sequence06/22/2011 22:10:25.289316: Module OnlineThis example shows how to display the Fabric Extender interfaces pinned to a specific switch interface:
switch(config-fex)# show interface ethernet 1/19 fex-intf'Fabric FEXInterface Interfaces---------------------------------------------------Eth1/19 Eth100/1/4 Eth100/1/3 Eth100/1/2 Eth100/1/1This example shows how to display the switch interfaces that are connected to a Fabric Extender uplink:
switch(config-fex)# show interface fex-fabricFabric Fabric Fex FEXFex Port Port State Uplink Model Serial---------------------------------------------------------------100 Eth1/19 Active 1 N2K-B22HP-P FOC1514256S100 Eth1/20 Active 2 N2K-B22HP-P FOC1514256S100 Eth1/21 Active 3 N2K-B22HP-P FOC1514256S100 Eth1/22 Active 4 N2K-B22HP-P FOC1514256Sswitch(config-fex)#
Note The above example shows a Fabric Extender with four uplink connections, only one of which is currently active.
This example shows how to display the SFP+ transceiver and diagnostic optical monitoring (DOM) information for Fabric Extender uplinks:
switch# show interface ethernet 1/40 transceiverEthernet1/40sfp is presentname is CISCO-EXCELIGHTpart number is SPP5101SR-C1revision is Aserial number is ECL120901AVnominal bitrate is 10300 MBits/secLink length supported for 50/125mm fiber is 82 m(s)Link length supported for 62.5/125mm fiber is 26 m(s)cisco id is --cisco extended id number is 4switch# show interface ethernet 1/40 transceiver fex-fabricEthernet1/40sfp is presentname is CISCO-EXCELIGHTpart number is SPP5101SR-C1revision is Aserial number is ECL120601U0nominal bitrate is 10300 MBits/secLink length supported for 50/125mm fiber is 82 m(s)Link length supported for 62.5/125mm fiber is 26 m(s)cisco id is --cisco extended id number is 4
Note The first show command above shows the SFP+ transceiver that is plugged into the parent switch interface. The second show command displays the SFP+ transceiver that is plugged into the uplink port on the Fabric Extender.
Displaying Chassis Management Information
To display configuration information used on the switch supervisor to manage the Fabric Extender, perform one of these tasks:
This example shows how to display the module information about all connected Fabric Extender units:
switch(config-fex)# show module fexFEX Mod Ports Card Type Model Status.--- --- ----- ---------------------------------- ------------------ -----------100 1 16 Fabric Extender 16x10GE + 8x10G Module N2K-B22HP-P presentFEX Mod Sw Hw World-Wide-Name(s) (WWN)--- --- -------------- ------ -----------------------------------------------100 1 5.0(3)N2(1) 0.501 --FEX Mod MAC-Address(es) Serial-Num--- --- -------------------------------------- ----------100 1 e8b7.484b.e880 to e8b7.484b.e88f FOC1514256Sswitch(config-fex)#switch(config-fex)# show module fex 100FEX Mod Ports Card Type Model Status.--- --- ----- ---------------------------------- ------------------ -----------100 1 16 Fabric Extender 16x10GE + 8x10G Module N2K-B22HP-P presentFEX Mod Sw Hw World-Wide-Name(s) (WWN)--- --- -------------- ------ -----------------------------------------------100 1 5.0(3)N2(1) 0.501 --FEX Mod MAC-Address(es) Serial-Num--- --- -------------------------------------- ----------100 1 e8b7.484b.e880 to e8b7.484b.e88f FOC1514256Sswitch(config-fex)#This example shows how to display the inventory information about a specific Fabric Extender unit:
switch(config-fex)# show inventory fex 100NAME: "FEX 100 CHASSIS", DESCR: "N2K-B22HP-P CHASSIS"PID: N2K-B22HP-P , VID: V00 , SN: FOC1516ZZLSNAME: "FEX 100 Module 1", DESCR: "Fabric Extender Module: 16x10GE, 8x10GE Supervisor"PID: N2K-B22HP-P , VID: V00 , SN: FOC1514256Sswitch(config-fex)#This example shows how to display diagnostic test results for a specific Fabric Extender unit:
switch(config-fex)# show diagnostic result fex 100FEX-100: Fabric Extender 16x10GE + 8x10G Module SerialNo : FOC1514256SOverall Diagnostic Result for FEX-100 : OKTest results: (. = Pass, F = Fail, U = Untested)TestPlatform:0) SPROM: ---------------> .1) Inband interface: ---------------> .2) Fan: ---------------> .3) Power Supply: ---------------> .4) Temperature Sensor: ---------------> .Eth 1 2 3 4 5 6 7 8Port -------------------------. . . . . . . .Eth 9 10 11 12 13 14 15 16Port ------------------------. . . . . . . .TestFabricPorts:Fabric 1 2 3 4 5 6 7 8Port -------------------------. . . . . . . .switch(config-fex)#This example shows how to display the environment status for a specific Fabric Extender unit:
switch(config-fex)# show environment fex 100Temperature Fex 100:-----------------------------------------------------------------Module Sensor MajorThresh MinorThres CurTemp Status(Celsius) (Celsius) (Celsius)-----------------------------------------------------------------1 Outlet-1 85 75 39 ok1 Outlet-2 85 75 48 ok1 Inlet-1 85 75 36 ok1 Inlet-2 85 75 27 ok1 Die-1 110 105 55 okswitch(config-fex)#This example shows how to display the SPROM for a specific Fabric Extender unit:
switch(config-fex)# show sprom fex 100 allDISPLAY FEX 100 SUP sprom contentsCommon block:Block Signature : 0xababBlock Version : 3Block Length : 160Block Checksum : 0x1860EEPROM Size : 65535Block Count : 3FRU Major Type : 0x6002FRU Minor Type : 0x0OEM String : Cisco Systems, Inc.Product Number : N2K-B22HP-PSerial Number : FOC1514256SPart Number : 73-13780-05Part Revision : 02Mfg Deviation : 0H/W Version : 0.501Mfg Bits : 0Engineer Use : 0snmpOID : 9.12.3.1.9.78.9.0Power Consump : 625RMA Code : 0-0-0-0CLEI Code : COUCAPKCAAVID : V00Supervisor Module specific block:Block Signature : 0x6002Block Version : 2Block Length : 103Block Checksum : 0x2603Feature Bits : 0x0HW Changes Bits : 0x0Card Index : 11048MAC Addresses : 00-00-00-00-00-00Number of MACs : 0Number of EPLD : 0Port Type-Num : 1-8Sensor #1 : 85,75Sensor #2 : 85,75Sensor #3 : 85,75Sensor #4 : 85,75Sensor #5 : 95,85Sensor #6 : -128,-128Sensor #7 : -128,-128Sensor #8 : -128,-128Max Connector Power: 625Cooling Requirement: 8Ambient Temperature: 40DISPLAY FEX 100 backplane sprom contents:Common block:Block Signature : 0xababBlock Version : 3Block Length : 160Block Checksum : 0x17e8EEPROM Size : 65535Block Count : 5FRU Major Type : 0x6001FRU Minor Type : 0x0OEM String : Cisco Systems, Inc.Product Number : N2K-B22HP-PSerial Number : FOC1516ZZLSPart Number : 68-4133-02Part Revision : 05Mfg Deviation : 0H/W Version : 0.501Mfg Bits : 0Engineer Use : 0snmpOID : 9.12.3.1.3.1058.0.0Power Consump : 0RMA Code : 0-0-0-0CLEI Code : COUCAPKCAAVID : V00Chassis specific block:Block Signature : 0x6001Block Version : 3Block Length : 39Block Checksum : 0x465Feature Bits : 0x0HW Changes Bits : 0x0Stackmib OID : 0MAC Addresses : e8-b7-48-4b-e8-80Number of MACs : 64OEM Enterprise : 0OEM MIB Offset : 0MAX Connector Power: 0WWN software-module specific block:Block Signature : 0x6005Block Version : 1Block Length : 0Block Checksum : 0x66wwn usage bits:00 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00License software-module specific block:Block Signature : 0x6006Block Version : 1Block Length : 16Block Checksum : 0x77lic usage bits:00 00 00 00 00 00 00 00DISPLAY FEX 100 UPLINK sprom contentsCommon block:Block Signature : 0x0Block Version : 0Block Length : 0Block Checksum : 0x0EEPROM Size : 0Block Count : 0FRU Major Type : 0x0FRU Minor Type : 0x0OEM String :Product Number :Serial Number :Part Number :Part Revision :Mfg Deviation :H/W Version : 0.0Mfg Bits : 0Engineer Use : 0snmpOID : 0.0.0.0.0.0.0.0Power Consump : 0RMA Code : 0-0-0-0CLEI Code :VID : V00Supervisor Module specific block:Block Signature : 0x0Block Version : 0Block Length : 0Block Checksum : 0x0Feature Bits : 0x0HW Changes Bits : 0x0Card Index : 0MAC Addresses : 00-00-00-00-00-00Number of MACs : 0Number of EPLD : 0Port Type-Num : 0-0Sensor #1 : 0,0Sensor #2 : 0,0Sensor #3 : 0,0Sensor #4 : 0,0Sensor #5 : 0,0Sensor #6 : 0,0Sensor #7 : 0,0Sensor #8 : 0,0Max Connector Power: 0Cooling Requirement: 0Ambient Temperature: 0switch(config-fex)#switch(config-fex)#switch(config-fex)#switch(config-fex)#switch(config-fex)#switch(config-fex)#Verifying the Configuration
The Onboard Administrator (OA) is the management module used to support and manage the HP BladeSystem c-Class enclosure or the HP Integrity Superdome 2 and all the devices used in the enclosure. The Onboard Administrator (OA) is the management module used to support and manage the HP BladeSystem c-Class and HP Integrity Superdome 2 enclosures along with all the devices used in the enclosure. Once the switch is installed in the interconnect bay, the OA verifies that the switch type matches the mezzanine cards present on the server blades. If there is no mismatch, the OA powers on the switch. If the switch does not power on, check the enclosure and switch status using the OA web interface. For more information and troubleshooting tips, see the HP BladeSystem Onboard Administrator User Guide or the or the HP Integrity Superdome 2 Onboard Administrator User Guide.
To verify the configuration,
1. Locate the LEDs. See Figure 6.
Figure 6 Identifying LEDs
2. Check the LEDs and refer to the indicators described in the following table.
Item Description Indicators1
UID LED—Helps the user locate a specific module in the BladeSystem, such as for replacement.
Off
2
Health LED—Indicates normal operation.
Steady green light
Note You need an OA version of 3.3.
Note For HP Integrity Superdome 2, the minimum F/W bundle is 2.51.102
Additional Information
For more information on the association between the server mezzanine bays and the enclosure interconnect bays, see the setup and installation guide provided with your enclosure. For more information see the HP websites:
•http://www.hp.com/go/bladesystem/interconnects
•http://www.hp.com/go/bladesystem/documentation
•http://www.hp.com/go/Integrity_Servers-docs
The location where you install the mezzanine card determines where you need to install the interconnect modules such as the Cisco Nexus B22 Fabric Extender for HP.
Figure 7 shows the external ports for the Cisco Nexus B22 Fabric Extender for HP.
Figure 7 External Ports
Note For specific information about the Bladesystem enclosure internal port mapping, see the setup and installation guide provided with the enclosure.
Related Documentation
Documentation for Cisco Nexus 5000 Series Switches and Cisco Nexus 2000 Series Fabric Extenders is available at the following URL:
http://www.cisco.com/en/US/products/ps9670/tsd_products_support_series_home.htmlInstallation documentation for the HP BladeSystem is available at:
http://h18004.www1.hp.com/products/blades/components/c-class-tech-installing.htmlDocumentation for HP Integrity Superdome 2:
http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en&cc=us&taskId=101&prodClassId=-1&contentType=SupportManual&docIndexId=64255&prodTypeId=15351&prodSeriesId=4311905
Technical Support
Technical support for the Cisco Nexus B22 Fabric Extender for HP can be obtained from either Cisco or Hewlett Packard. This topic includes the following sections:
For Hewlett Packard Support
For hardware replacement under warranty, contact Hewlett Packard.
In the United States, for contact options see the Contact HP United States webpage. To contact HP by phone:
•Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7 days a week. For continuous quality improvement, calls may be recorded or monitored.
•If you have purchased a Care Pack (service upgrade), call 1-800-633-3600. For more information about Care Packs, refer to the HP website.
In other locations or for the name of the nearest HP authorized reseller, see the Contact HP worldwide (in English) webpage.
For Cisco Support
For configuration or troubleshooting assistance, the Cisco Nexus B22 Fabric Extender for HP is covered under the Cisco support contract of the parent Cisco Nexus switch.
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
©2011 Cisco Systems, Inc. All rights reserved.