User manual HP GBE2C LAYER 2/3 ETHERNET BLADE SWITCH

[. . . ] HP GbE2c Layer 2/3 Ethernet Blade Switch for c-Class BladeSystem User Guide Part Number 440948-001 December 2006 (First Edition) © Copyright 2006 Hewlett-Packard Development Company, L. P. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. [. . . ] Assess the particular server environment to determine any requirements for other considerations. The switch does not affect or determine NIC numeration and the associated mapping of NIC interfaces to switch ports. The numbering of the NICs on the server (for example, NIC 1, NIC 2, NIC 3) is determined by the server type, the server operating system, and which NICs are enabled on the server. NOTE: Port 19 is reserved for connection to the Onboard Administrator module for switch management. This allows a user to enable the functionality of future firmware upgrade releases. Enabling is based on matching ports between the server and the interconnect bay. Before power up, the Onboard Administrator module verifies that the server NIC option matches the switch bay that is selected and enables all ports for the NICs installed. For detailed port mapping information, see the HP BladeSystem enclosure installation poster or the HP BladeSystem enclosure setup and installation guide on the HP website (http://www. hp. com/go/bladesystem/documentation). Default settings The switch ships with a default configuration in which all downlink and uplink ports are enabled and assigned a default VLAN with a VID equal to 1. This default configuration simplifies the initial setup by allowing use of a single uplink cable (from any external Ethernet connector) to connect the server blade enclosure to the network. Assess the particular server environment to determine any requirements for other considerations. The switch does not affect or determine NIC numeration and the associated mapping of NIC interfaces to switch ports. The numbering of the NICs on the server (for example, NIC 1, NIC 2, NIC 3) is determined by the server type, the server operating system, and what NICs are enabled on the server. Installing the switch 16 The Onboard Administrator module controls all port enabling. Enabling is based on matching ports between the server and the interconnect bay. Before power up, the Onboard Administrator module verifies that the server NIC option matches the switch bay that is selected and enables all ports for the NICs installed. NOTE: Port 19 is reserved for connection to the Onboard Administrator module for switch management. This allows a user to enable the functionality of future firmware upgrade releases. For detailed port mapping information, see the HP BladeSystem enclosure installation poster or the HP BladeSystem enclosure setup and installation guide on the HP website (http://www. hp. com/go/bladesystem/documentation). When planning the configuration, consider the default settings for these parameters: · · · · · · · · · · Switch IP settings VLAN settings STP settings Port names and types Port trunking settings Interswitch X-Connect port settings SNMP settings User name and password settings Default access to various management interfaces NTP settings IMPORTANT: See "Runtime switching software default settings (on page 29)" for a complete list of default configuration settings. Switch security When planning the switch configuration, secure access to the management interface by: · · · Creating users with various access levels Enabling or disabling access to various management interfaces to fit the security policy Changing default SNMP community strings for read-only and read-write access User, operator, and administrator access rights To enable better switch management and user accountability, three levels or classes of user access have been implemented on the switch. Levels of access to CLI, Web management functions, and screens increase as needed to perform various switch management tasks. Conceptually, access classes are defined as: · · User interaction with the switch is completely passive. Users can display information that has no security or privacy implications, such as switch statistics and current operational state information. Operators have access to the switch management features used for daily switch operations. [. . . ] Disable the manual proxy settings on the Web browser and let it automatically find Web servers using the IP address. The management network address/mask (if used) does not contain the IP address of the management station. From the serial console interface, be sure that the management network address/mask contains the IP address of the management station. Cannot enable a port in multiple VLANs while configuring VLANS Action: A port is part of only one VLAN unless the port is a tagged port. Be sure that the port is enabled as a tagged port. The switch does not let the user enable two adjacent ports into two different VLANs while assigning the ports to VLANs Action: The ports are two adjacent ports that are bundled in a Port Trunk. [. . . ]