SEARCH DOCS
info central: your site for Collage technical info
  CASSATT.COM   INFO CENTRAL
ACTIVE RESPONSE 5.1 TOPICS BLUEPRINTS TROUBLESHOOTING DOC INDEX


 

TOC

Step 1: Configure access to the BCMM
Step 2: Configure the BCMM for SNMP
Step 3: Configure switches
Step 4: Configure the BCMM for network booting and DHCP
know how:

IBM Blade Center: Nodes in a Blade Enclosure

Intended for use with Cassatt Active Response Premium Edition and Data Center Edition V5.1.

This article describes how to set up application nodes using an IBM BladeCenter Management Module (BCMM) for utility computing. Complete this step before adding the enclosure and blades to the Cassatt Active Response Controller.

Step 1: Configure access to the BCMM

Follow these steps to configure access to the blade enclosure.

  1. Unplug the BCMM chassis.
  2. Connect a console, keyboard, and mouse to a control node.
  3. Plug in the BCMM chassis.
  4. On the control node, create network access to the BCMM by creating an alias to the default BCMM IP address.

    Prompt Enter Notes
    # ifconfig eth0:bcmm 192.168.70.124 up

    This default IP address is used only during the setup procedure; it will not be the IP address used in Cassatt Active Response after configuration is completed.

  5. Open a web browser and enter the BCMM’s default IP address: 192.168.70.125 as the URL.
  6. Log into the BCMM's web interface.
    Prompt Enter Notes
    Login USERID The default IBM user ID.
    Password PASSW0RD The default IBM password, where the sixth letter is a zero "0" (not the letter "O").
  7. In the left navigation, select I/O Module Tasks > Management in the Bay 1 Section, and set the IP address, subnet mask, and gateway addresses as follows:
    Prompt Enter Notes
    New Static IP Configuration <new_IP_address> The BCMM is a networked component that is not managed by Cassatt Active Response, so you must specify a reserved static IP address from within the subnet you are using for Cassatt Active Response. Static IP addresses are implicitly reserved during Cassatt Active Response installation—by virtue of setting the first available and last available IP addresses in the subnet. You can set the BCMM to an address excluded from that range. Alternatively, you can reserve IP addresses in the Cassatt Active Response Controller in: Networks > Cassatt Active Response Subnet > Properties. For help, see Network Addresses: Calculating Requirements.
  8. Select Save.
  9. On the confirmation screen, select Yes.
  10. On the Current IP Configuration portion of the screen, verify that the new values are correct.
  11. Select Advanced Management in the Bay 1 Section, and set as follows:
    Setting Enter
    Fast POST Disabled
    External ports Enabled
    External management over all ports Disabled
    Preserve new IP configuration on all resets Enabled
  12. Save the changes.
  13. On the I/O Module management screen, select the Advanced Management in the Bay 1 Section and do the following:
    a. Select Restore Defaults.
    b. On the confirmation screen, select Yes.
    c. Select OK.
  14. Repeat steps in this section for additional switches in the BCMM chassis.

top

Step 2: Configure the BCMM for SNMP

Follow these steps to configure the BCMM.

Cassatt Active Response does not require telnet to be enabled; therefore, it can be enabled or disabled.

  1. On the control node, telnet to the BCMM using the reserved IP address you assigned in the previous section.
  2. Log into the BCMM's web interface.
  3. In the left navigation bar, access MM Control > Network Protocols >Simple Network Management Protocol (SNMP) and set as follows.
    Setting
    Enter
    SNMPv3 agent Enabled
    Other settings As you wish.

  4. In the left navigation bar, access MCC Control > Login Profiles.
  5. Click on the login profile that you want to use with Cassatt Active Response (Cassatt recommends that you create a new user profile for SNMP). The link goes to the configuration screen of the specific user profile.  
  6. Click on the Configure SNMPv3 User link at the bottom of the page, and set as follows:
    Setting
    Enter
    Context name Must be blank.
    Authentication name MD5
    Privacy protocol None.
    Privacy password Blank.
    Confirm privacy password Blank.
    Access type Set
    Hostname/IP address for traps 0.0.0.0 (default) or leave as is.
  7. In the left navigation bar, click Restart MM; on the Restart MM page, click the Restart button to save the change.

Step 3: Configure switches

Follow these steps to configure each switch in the BladeCenter chassis.

Setting Enter
hostname <switch> Must be a unique host name.
spanning-tree mode pvst Removes loops in the network.
spanning-tree portfast bpduguard default Protects against cabling errors. If a spanning tree packet does not arrive on a port that has this feature enabled, the port is disabled.

spanning-tree vlan 1 priority 61440 spanning-tree vlan 2 priority 61440

Set the priority of the spanning tree protocol for the two VLANs that exist on the switch. This is required because the BladeCenter switches should never be the root of the spanning tree.
interface range GigabitEthernet0/17 - 18
switchport access vlan 1
switchport mode access
exit
Creates channel-group 1 for ports 17-18.
interface range Port-channel 1 - 2
switchport access vlan 2
switchport mode access
exit
Explicitly forces the two aggregate links to be part of VLAN 2 and to not send VLAN packets.
no ip http server
exit
Turns off the HTTP server; it is not used and is turned off as a security precaution.
show running-config

Verify switch configuration.

Sample output:

Current configuration : 5247 bytes
!
Version 12.1
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname swbc1
!
username USERID privilege 15 secret 5
$1$wHcM$k2V7ULW2HsnsExS6JSd3a/
ip subnet-zero
!
vtp mode transparent
spanning-tree mode pvst
spanning-tree portfast bpduguard default
no spanning-tree optimize bpdu transmission
spanning-tree extend system-id
spanning-tree vlan 1 priority 61440
spanning-tree vlan 2 priority 61440
!
vlan 2
name operational
!
interface Port-channel1
switchport access vlan 2
switchport trunk native vlan 2
switchport mode access
!
interface Port-channel2
switchport access vlan 2
switchport trunk native vlan 2
switchport mode access
!
interface GigabitEthernet0/1
description blade1
switchport access vlan 2
switchport trunk native vlan 2
switchport trunk allowed vlan 2-4094
switchport mode trunk
spanning-tree portfast trunk
spanning-tree bpdufilter enable
!
interface GigabitEthernet0/2
description blade2
switchport access vlan 2
switchport trunk native vlan 2
switchport trunk allowed vlan 2-4094
switchport mode trunk
spanning-tree portfast trunk
spanning-tree bpdufilter enable

switchport access vlan 2
switchport trunk native vlan 2
switchport trunk allowed vlan 2-4094
switchport mode trunk
spanning-tree portfast trunk
spanning-tree bpdufilter enable

interface GigabitEthernet0/3
description blade3
switchport access vlan 2
switchport trunk native vlan 2
switchport trunk allowed vlan 2-4094
switchport mode trunk
spanning-tree portfast trunk
spanning-tree bpdufilter enable
!
interface GigabitEthernet0/4
description blade4
switchport access vlan 2
switchport trunk native vlan 2
switchport trunk allowed vlan 2-4094
switchport mode trunk
spanning-tree portfast trunk
spanning-tree bpdufilter enable
!
interface GigabitEthernet0/5
description blade5
switchport access vlan 2
switchport trunk native vlan 2
switchport trunk allowed vlan 2-4094
switchport mode trunk
spanning-tree portfast trunk
spanning-tree bpdufilter enable
!
interface GigabitEthernet0/6
description blade6
switchport access vlan 2
switchport trunk native vlan 2
switchport trunk allowed vlan 2-4094
switchport mode trunk
spanning-tree portfast trunk
spanning-tree bpdufilter enable
!
<Ports 7 through 13 output should be the same as shown above for GigabitEthernet0/6>

interface GigabitEthernet0/14
description blade14
switchport access vlan 2
switchport trunk native vlan 2
switchport trunk allowed vlan 2-4094
switchport mode trunk
spanning-tree portfast trunk
spanning-tree bpdufilter enable
!
interface GigabitEthernet0/15
description mgmt1
switchport trunk allowed vlan 1
switchport mode trunk
switchport nonegotiate

spanning-tree cost 100
spanning-tree cost 100

interface GigabitEthernet0/16
description mgmt2
switchport trunk allowed vlan 1
switchport mode trunk
switchport nonegotiate
spanning-tree cost 100
!
interface GigabitEthernet0/17
description extern1
switchport access vlan 2
switchport trunk native vlan 2
switchport mode access
channel-group 1 mode active
!
interface GigabitEthernet0/18
description extern2
switchport access vlan 2
switchport trunk native vlan 2
switchport mode access
channel-group 1 mode active
!
interface GigabitEthernet0/19
description extern3
switchport access vlan 2
switchport trunk native vlan 2
switchport mode access
channel-group 2 mode active
!
interface GigabitEthernet0/20
description extern4
switchport access vlan 2
switchport mode access
switchport trunk native vlan 2
channel-group 2 mode active
!
interface Vlan1
ip address 192.168.72.10 255.255.255.128
no ip route-cache
!
ip default-gateway 192.168.72.1
no ip http server
ip http authentication local
!
snmp-server community public RO
snmp-server community private RW
!
line con 0

line vty 0 4
login localline vty 5 15
login local
!
end


copy running-config startup-config

Save the configuration in the startup config file.

Sample Output:
Destination filename [startup-config]?
Building configuration...
[OK]
sw01#

ping <gateway_IPaddress> Verify access to the gateway, by pinging the gateway; where <gateway_IPaddress> is the IP address for the gateway.

top

Step 4: Configure the BCMM for network booting and DHCP

Follow these steps to configure the BCMM for Cassatt Active Response management.

  1. Verify that the blade servers are installed in the BCMM chassis and are powered off.
  2. Connect the second console to the BCMM chassis.
  3. Open a browser, and enter the default BCMM IP address: 192.168.70.125.
  4. Log into the BCMM web interface.
  5. In the left navigation, access Blade Tasks > Configuration > Boot Sequence and set as follows:
    1. Network - PXE
    2. CD-ROM
    3. Floppy

    "Network" must come before the “Hard drive”option in the boot order or the node will not boot. If you place “Network” first in the boot order, you gain a small optimization in speed for node discovery and in moving nodes to the free pool. If you are operating in a test environment or you expect to need frequent administrative access to the application nodes, you can set the order to Floppy, CD-ROM, Network.


  6. From the list of blade servers, select the name of the first blade server and do the following:
    a. Check the order of the boot sequence to make sure it is set as specified in step 5.
    b. Select Apply to All Blade Servers.
    c. Select Save.
  7. If you want the BCMM to DHCP for its IP address but not autodiscover, go to step 9. If you want the BCMM to autodiscover, continue with the steps in order. If you are using manual discovery, go to skip to step 10.
  8. To set up the BCMM for automatic discovery, access the MM Control > Network Interface > External Network Interface section and verify that Hostname box entry has the following format: MMmac_address_inhex

    Where:
    mac_address_inhex is the default MAC address of the BCMM as shipped from IBM, without any ":", "-", or space characters. (The MMmac_address_inhex Hostname is used by Cassatt for initial automatic discovery and is required). After the BCMM has been discovered, the Hostname text can be changed to meet your requirements.

    Example: If the default MAC address is: 00:0D:50:F5:8A:EA, the valid Hostname entry is: MM000D50F58AEA
  9. Access MM Control > Network Interface in the External Network Interfaces (eth0) section, and set the BCMM to get its IP address via DHCP:

    Setting
    Enter
    DHCP box Enabled - Obtain IP config from DHCP server

  10. Select save.
  11. Under MM Control, select Restart MM.
    If automatic discovery is turned on after restarting the BCMM, Cassatt Active Response will assign an IP for it so you no longer need the alias to the BCMM. To remove the IP alias for the BCMM, log into the control node enter the following command: # ifconfig eth0:bcmm down
top