1. Manuals
  2. Brands
  3. HP Manuals
  4. Desktop
  5. Bc1500 - BladeSystem - Blade PC
  6. Supplementary manual

HP Bc1500 - BladeSystem - Blade PC Supplementary Manual

Network considerations guide
Hide thumbs Also See for Bc1500 - BladeSystem - Blade PC:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Reference Manual, User Manual
CCI Network Considerations Guide
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Anatomy of the CCI solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
CCI, network speed, and the connection protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
CCI network traffic patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Network reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Network bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Network latency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Connection methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
The HP BladeSystem PC Blade Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Internal Ethernet ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
External Ethernet ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Port speed, duplex, and flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Maximizing network cable reduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Virtual Local Area Network (VLAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Management IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Switch diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Switch management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Embedded Web System interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Link aggregation groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Spanning tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
PVST interoperability mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Disabling the spanning tree PVST Interoperability mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
SNMP and remote monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Configuring the switch to send SNMPv1traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Configuring HP SIM to work with the switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
HP Session Allocation Manager (SAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
HP SAM minimum network requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1

Advertisement

Table of Contents
loading

Related Manuals for HP Bc1500 - BladeSystem - Blade PC

Summary of Contents for HP Bc1500 - BladeSystem - Blade PC

  • Page 1: Table Of Contents

    CCI Network Considerations Guide Introduction ............4 Anatomy of the CCI solution .
  • Page 2 The blade PC allocation process ......... . 20 Blade image management considerations .

  • Page 3: Introduction

    This document provides an overview of the HP BladeSystem PC Blade Switch, as well as an explanation of network terminology, configuration concepts, and examples relevant to the HP CCI solution. This docu- ment is intended for those seeking technical networking knowledge of how CCI is applied to the enter- prise network.

  • Page 4: Anatomy Of The Cci Solution

    The HP PC Blade Switch is a managed Layer 2+ Ethernet switch that provides up to a 41-to-1 reduction in Ethernet network cables and provides network connection redundancy for the HP PC Blade Enclosure. Cable reduction can help to reduce the time required to deploy, manage, and service the HP CCI solu- tion.

  • Page 5: Cci, Network Speed, And The Connection Protocol

    Figure 1 CCI topology CCI, network speed, and the connection protocol Network speed is really all about “how much longer than instantaneous does it take a signal to travel a given route?” Anything more than instantaneous is “latency.” So, the question is how much latency is in a network supporting CCI, and at what point does this latency impact user experience? One of the advantages of CCI over competitive offerings and traditional computer systems is that the remote host does not download files to the local access device.
  • Page 6 to access a blade PC located in the corporate data center to run an email application and manipulate the 10-MB file without download the file to the remote access device. In this case, access to read and edit such a file is achievable within a reasonably expected amount of time. An understanding of the transport software used by CCI is imperative before trying to understand how network latency can impact end users experience.

  • Page 7: Cci Network Traffic Patterns

    CCI network traffic patterns Traditional distributed PCs have historically created peak network traffic at specific times. Traffic tradition- ally peaks within the first 30 minutes of the workday as users log in and large amounts of data move between the datacenter and end users. During this time, MS Exchange data, system hot fixes, etc., traverse the network.

  • Page 8: Network Reliability

    Network reliability Businesses require reliable networks, which are imperative to support solutions that successfully address business needs. In CCI, network failure affects user access to virtualized desktops. Therefore, HP recom- mends that you use redundant design practices to provide multiple network paths to all centralized com- puting resources.

  • Page 9: Connection Methods

    Connection methods CCI end users can connect to their blade PC using a network in a variety of ways: traditional dial-up modems, DSL, cable modems, LANs, etc. General performance with RDC (including CCI and any net- work architecture that uses MS-RDC) is based on response times as characterized in the following table: Response Time Typical Network Type End User Experience...

  • Page 10: The Hp Bladesystem Pc Blade Switch

    • Additional considerations on dial-up modems: Analog modems vary in quality. Higher quality 56kbps modems may produce lower latency than lower quality modems. Because analog modems are designed to retrain their speed depending on line condition, you may need to fine tune modem configuration or seek a more robust method to access the network, such as an xDLS broadband con- nection or dedicated leased-line.

  • Page 11: Internal Ethernet Ports

    Internal Ethernet ports The HP PC Blade switch comes pre-configured with two Virtual LANs, VLAN 1 and VLAN 2. VLAN 1 is assigned to odd numbered ports e1 through e39, which physically connect blade PC NIC A to the switch by way of the passive centerwall assembly.

  • Page 12: Maximizing Network Cable Reduction

    Maximizing network cable reduction For maximum cable reduction, consider using a combination of IEEE 802.1q VLAN Tagging and IEEE 802.3ad Link Aggregation. Using a LAG to carry the network traffic for all necessary VLANs over two physical uplinks for each HP PC Blade Switch can reduce total uplink to as few as 28 Ethernet connec- tions for a 42U rack fully populated with 14 HP PC blade Enclosures for a total of up to 560 network adapters.
  • Page 13 Figure 3 HP PC Blade Switch tray external panel LEDs Item Description Integrated Administrator Health Interconnect Switch Health Reserved for future use Link Activity Status Link Speed Status The HP PC Blade Switch provides the following additional serviceability and diagnostic features: •...

  • Page 14: Switch Management

    Switch management The HP PC Blade Switch is an industry-standard managed Layer 2+ Ethernet switch, meaning users config- ure and manage the switch like other industry-standard Layer 2 Ethernet switches. To aid users during ini- tial deployment, the switch includes a default configuration that is fully operational at initial boot (see Appendix A).

  • Page 15: Link Aggregation Groups

    Navigation Pane Administration Window Figure 4 Browser-based interface for HP PC Blade Switch Link aggregation groups The HP PC Blade Switch complies with IEEE 802.3ad static and dynamic Link Aggregation Groups (LAGs). The switch supports a maximum of eight multi-port trunks with up to eight ports per trunk. IMPORTANT: Because the HP PC Blade Switch has only four physical uplinks, limit Link Aggregation to a maximum of four physical trunk members for uplink ports.

  • Page 16: Pvst Interoperability Mode

    ships with IEEE 802.1s pre-configured to use a special feature called PVST Interop Mode. This feature pro- vides certain advantages specific to the CCI solution. Thorough knowledge of PVST Interop Mode is required prior to designing the switch into an existing production network. For more information on PVST Interop Mode, see “PVST interoperability mode”...

  • Page 17: Disabling The Spanning Tree Pvst Interoperability Mode

    which then assigns the traffic to the appropriate internal MSTP instance. Before transmitting outgoing or uplink packets, the PVST interoperability feature translates the MSTP BPDU back to RSTP. This process allows internal operation with MSTP and external operation with other Per-VLAN spanning tree protocols to eliminate bridging multiple per-VLAN Root instances.

  • Page 18: Snmp And Remote Monitoring

    SNMP and remote monitoring You can monitor the HP PC Blade Switch remotely from an SNMP/RMON network management tool set such as HP Systems Insight Manager (HP SIM) or HP OpenView. Unique integration with HP Systems Insight Manager provides the following additional features: •...
  • Page 19 To verify that the SNMP traps are available and enabled in HP SIM: • In HP SIM, select Options > Events > SNMP Trap Settings. • Verify that the newly registered MIB file RADLAN-MIB.mib is in the Mib Name box. NOTE: By default, the traps in this MIB may not be enabled for trap handling and severity because the level is not configured.

  • Page 20: Hp Session Allocation Manager (Sam)

    Registering the configuration file with HP SIM: Execute the command: mxmib -a RADLAN-MIB.cfg To verify RADLAN-MIB mib was loaded, execute the command: mxmib -l To verify that the SNMP traps are available and enabled in HP SIM: In HP SIM, select Options > Events > SNMP Trap Settings. •...

  • Page 21: The Blade Pc Allocation Process

    The blade PC allocation process The following illustration highlights how HP SAM uses the network to facilitate the user to blade PC alloca- tion process. Other HP SAM activities, such as manual or automated administrative operations to the blade PC, may utilize the network, but are not necessarily covered in this illustration. For more informa- tion, see the HP PC Session Allocation Manager User Guide, part number: 416323-001.

  • Page 22: The Blade Pc Image Pxe Boot Process

    The blade PC image PXE boot process During the blade PC PXE boot process, the PXE server listens to communication between the blade PC and the DHCP server, and then sends its IP address to the blade PC at the right moment. Once the blade PC begins to boot, it knows the IP address to use to communicate with the PXE server.

  • Page 23: General Notes Regarding Solution Components

    • HP Systems Insight Manager • Requires network access to HP blade PC. • Requires network access to SQL database server. • HP Rapid Deployment Pack • Participates in DHCP communication between blade PC NIC A and the DHCP server to facil- itate PXE.

  • Page 24: Cci Network Topology Reference Designs

    CCI network topology reference designs HP designed the HP PC Blade Switch for deployment into a variety of different network topologies. This section presents a set of sample network scenarios listed in order of least to most complex that illustrates HP PC Blade Switch deployment examples within a CCI design.

  • Page 25: Redundant Connectivity With Ieee 802.1D Or 802.1W

    Networking Considerations • You can deploy the HP PC Blade Switch into this scenario without changing the default switch config- uration. • Works with any network infrastructure that not require IEEE 802.1q VLAN Tagging on the HP Blade PC Switch uplinks. If 802.1a VLAN tagging is required, some features of the HP PC Blade will require configuration.

  • Page 26: Flat Network With Per-Vlan Spanning Tree

    This reference design illustrates how you can configure two or more physical connections to redundantly deploy the HP PC Blade Switch. IEEE 802.1q VLAN tagging is in use so that while link E is blocked, link D will carry traffic for both VLANs. If either link A & C or D were to fail, link E would take over. This design’s logic works the same for either IEEE 802.1D or 802.1w.

  • Page 27: Basic Connectivity With Per-Vlan Spanning Tree

    This reference design illustrates how you could deploy the HP PC Blade Switch into a network where 802.1q is not necessary and only one blade PC NIC is used. If either link A & C or D were to fail, link E would take over.

  • Page 28: Redundant Connectivity With Per-Vlan Spanning Tree

    This reference design illustrates how you can deploy the HP PC Blade Switch into a network without ini- tially connecting the switch in a redundant fashion. This “staging” method allows you to quickly deploy switches, giving you time to evaluate the solution. When you want redundancy, you can connect link e44 and e46 (see the next section for an example.) If either link A &...

  • Page 29: Standards Based Redundancy With Ieee 802.1S (Mstp)

    Network Considerations • You can deploy the HP PC Blade Switch into this scenario without making changes to the default con- figuration. • For Cisco networks running PVST/PVST+, links A, B, and C may use either 802.1q or ISL.encapsula- tion. •...

  • Page 30: Vlan Load Balancing With Ieee 802.1S (Mstp)

    • Optionally, you can use IEEE 802.3ad Link Aggregation in various combinations with this sample topology to enhance performance and link level redundancy. If you want to maintain optimum network performance after a network failover occurs, then consider creating two logical LAGs, one with ports e43 & e44, the other with ports e45 & e46. Since a well designed network rarely fails, you could configure the primary forwarding connection to include ports e43 - 44 and either port e45 or e46 to for a single high performance link.

  • Page 31: For More Information

    tree attributes, Instance 1 & 2 for link A, B, D, and E should be blocked at the core and at the HP PC Blade Switch instead of at the aggregation switches. • Optionally, you can use IEEE 802.3ad Link Aggregation in various combinations with this sample topology to enhance performance and link level redundancy.

  • Page 32: Appendix A: Hp Pc Blade Switch Startup-Config Samples

    Resource Description Web address HP ProLiant BL e-Class C-GbE Interconnect Switch http://h20000.www2.hp.com/bc/docs/support/Sup- Menu-driven Interface Reference Guide, part number: portManual/c00594288/c00594288.pdf 322858-001 HP ProLiant BL e-Class C-GbE Interconnect Switch http://h20000.www2.hp.com/bc/docs/support/Sup- User Guide, part number: 263682-002 portManual/c00594291/c00594291.pdf ProLiant BL e-Class C-GbE Interconnect Switch Over- http://h20000.www2.hp.com/bc/docs/support/Sup- view white paper, part number: 16LD-0602A- portManual/c00098518/c00098518.pdf...

  • Page 33: Default (Canned Startup-Config)

    Default (canned startup-config) This sample will perform the following action against a default configuration: • Loading this sample has the same affect as erasing the startup-config, and then restarting the switch. spanning-tree mode mstp spanning-tree mst mstp-rstp interface range ethernet e(1-41) spanning-tree disable exit spanning-tree mst configuration...

  • Page 34: No Stp (Canned Startup-Config)

    No STP (canned startup-config) This sample will perform the following actions against a default configuration: • Disable PVST Interoperability mode • Disable MSTP • Remove VLAN 1 from MSTI 1 • Remove VLAN 2 from MSTI 2 • Remove VLAN 3-4093 from MSTI 15 •...

  • Page 35: Stp/Rstp (Canned Startup-Config)

    STP/RSTP (canned startup-config) This sample will perform the following actions against a default configuration: • Disable PVST Interoperability mode • Disable MSTP • Remove VLAN 1 from MSTI 1 • Remove VLAN 2 from MSTI 2 • Remove VLAN 3-4093 from MSTI 15 •...

  • Page 36: Mstp (Canned Startup-Config)

    MSTP (canned startup-config) This sample will perform the following actions against a default configuration: • Disable PVST Interoperability mode • Remove VLAN 3-4093 from MSTI 15 • Change all MSTI priorities to 32768 • All other values remain in factory default spanning-tree mode mstp interface range ethernet e(1-41) spanning-tree disable...

  • Page 37: Redundant Connectivity With Ieee 802.1D Or 802.1W

    Redundant connectivity with IEEE 802.1D or 802.1w interface range ethernet e(1-41) spanning-tree disable exit spanning-tree mst configuration instance 1 add vlan 101 instance 2 add vlan 102 instance 15 add vlan 3-100,103-4093 name cci revision 1 exit spanning-tree mst 1 priority 61440 spanning-tree mst 2 priority 61440 spanning-tree mst 3 priority 61440 spanning-tree mst 4 priority 61440...

  • Page 38: Flat Network With Per-Vlan Spanning Tree

    NOTE: You can use this example to set IEEE 802.1w functionally by running the following command once the file has been activated on the switch. Enable Configure Spanning-tree mode rstp Save running-config startup-config Flat Network with Per-VLAN Spanning Tree Use the default switch settings. Basic Connectivity with Per-VLAN Spanning Tree Use the default switch settings.

  • Page 39: Standards Based Redundancy With Ieee 802.1S (Mstp)

    Standards Based Redundancy with IEEE 802.1s (MSTP) spanning-tree mode mstp interface range ethernet e(1-41) spanning-tree disable exit spanning-tree mst configuration instance 1 add vlan 101 instance 2 add vlan 102 name cci revision 1 exit interface range ethernet e(43-46) switchport mode trunk exit vlan database vlan 101-102...

  • Page 40: Appendix B: Running The Hp Pc Blade Switch And The C-Gbe Interconnect Switch In A Co-Existing Network

    Appendix B: Running the HP PC Blade Switch and the C-GbE Interconnect Switch in a co-existing network This appendix provides information about adding an HP BladeSystem PC Blade Switch to a network using the C-GbE Interconnect Switch. Both switches can function together on the same network. The HP PC Blade Switch is specifically designed to work with the HP blade PC family of products, but can also work with the older ProLiant e-class Blade Server product family.
  • Page 41 HP BladeSystem PC Blade Switch - HP e-Class GbE Switch Feature Comparison HP BladeSystem PC Blade Switch HP eClass GbE Switch (previous) (current) Form Factor Integrated within Enclosure Integrated within Enclosure Switch Architecture Dual 24 port 10/100 Single 42 port 10/100 Uplink Ports 2x - 2 Gbs Copper 4 Gbs Copper + 4 SFP slots...

  • Page 42: Switch Default Configuration

    HP BladeSystem PC Blade Switch - HP e-Class GbE Switch Feature Comparison HP BladeSystem PC Blade Switch HP eClass GbE Switch (previous) (current) Form Factor Integrated within Enclosure Integrated within Enclosure IP Ping/802.2 Link Test 802.3ad Link Aggregation 802.3x Flow Control (TX &...

  • Page 43: Notes

    Notes • The HP BladeSystem PC Blade Switch is configured by default with a special MSTP feature called PVST Interoperability (Separated Bridges). While this is an extension to MSTP, the switch will also interoperate with IEEE 802.1D and IEEE 802.1W networks with this feature enabled. A thorough understanding of network topology, spanning tree protocol, network redundancy, and failover requirements is needed prior to determining the optimal spanning tree mode and configuration.

  • Page 44: Disabling The Spanning Tree Pvst Interoperability Mode

    Disabling the spanning tree PVST Interoperability mode To disable the feature and run IEEE 802.1s MSTP, 802.1w RSTP, or 802.1d STP, use the following com- mands at the CLI console prompt: enable configure no spanning-tree mst mstp-rstp spanning-tree mst configuration instance 15 remove vlan 3-4093 Please note that you must configure the spanning tree mode, VLAN settings, port configuration, and other relevant switch parameters to match the remaining requirements of the infrastructure.
  • Page 45 © 2006 Hewlett-Packard Development Company, L.P. The information in this document is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services.

This manual is also suitable for:

Cci

Table of Contents