unixadmin.free.fr just another IBM blog and technotes backup

18avr/13

IBM POWER 7 / BULL references

Bull Escala E1-700 / E3-700 (31E/2B ,8231-E2B)
Bull Escala E1-705 (31E/1C, 8231-E1C)
Bull Escala E1-715 (31E/1D, 8231-E1D)
Bull Escala E3-705 (31E/2C, 8231-E2C)
Bull Escala E3-715 (31E/2D, 8231-E2D)
Bull Escala E2-700 / E2-700T (02E/4B, 8202-E4B)
Bull Escala E2-705 / E2-705T (02E/4C, 8202-E4C)
Bull Escala E2-715 / E2-715T (02E/4D, 8202-E4D)
Bull Escala E4-700 / E4-700T (05F/6B, 8205-E6B)
Bull Escala E4-705 (05E/6C, 8205-E6C)
Bull Escala E4-715 (05E/6D, 8205-E6D)
Bull Escala E5-700 (33E/8B, 8233-E8B)
Bull Escala E5-715 (08E/8D, 8408-E8D)
Bull Escala M5-715 (09R/MD, 9109-RMD)
Bull Escala M6-700 (17M/MB, 9117-MMB)
Bull Escala M6-705 (17M/MC, 9117-MMC)
Bull Escala M6-715 (17M/MD, 9117-MMD)
Bull Escala M7-700 (79M/HB, 9179-MHB)
Bull Escala M7-705 (79M/HC, 9179-MHC)
Bull Escala M7-715 (79M/HD, 9179-MHD)
Bull Escala H9-700 (19F/HB, 9119-FHB)

SOURCE: BULL Support

9mar/11

COMPARATIF P5 et P6 SERVEUR IBM / BULL

Model IBM
Reference Proc. Freq Reference Bull
8203-E4A P520 P6 4.2Ghz PL160R (1proc)
8203-E4A P520 P6 4.2Ghz PL160T (1proc)
8203-E4A P520 P6 4.2Ghz PL260R (2proc)
8203-E4A P520 P6 4.2Ghz PL260T (2proc)
8203-E4A P520 P6 4.2Ghz PL460R (4proc)
8203-E4A P520 P6 4.2Ghz PL460T (4proc)
8204-E8A P550 P6 3.5/4.2Ghz PL860R (2,4,6,8 proc)
8204-E8A P550 P6 3.5/4.2Ghz PL860T (2,4,6,8 proc)
9117-MMA P570 P6 3.5/4.2/4.7Ghz PL1660R (216proc)
9119-FHA P595 P6 4.2/5.0 Ghz PL3260R (32 proc)
9119-FHA P595 P6 4.2/5.0 Ghz PL6460R (64 proc)
9110-51A P510Q P5+ 1.65Ghz PL450R-VL+
9110-51A P510Q P5+ 1.9/2.1Ghz PL250R-L+
9110-510 P510 P5 1.5/1.65 GHz PL250R-L
9111-520 P520 P5 1.5/1.65 GHz PL250T, PL250R
9131-52A P520 P5+ 1.65/1.9/2.1 GHz PL250T+, PL250R+
9131-52A P520Q P5+ 1.5/1.65Ghz PL450T-L+, PL450R-L+
9113-550 P550 P5 1.5/1.65 GHz PL450T, PL450R
9133-55A P550 P5+ 1.65/1.9/2.1 GHz PL450T+, PL450R+
9133-55A P550Q P5+ 1.5/1.65 GHz PL850T-L+, PL450R-L+
9115-505 P505 P5 1.5/1.65 GHz PL250R-VL
9115-505 P505 P5+ 1.9/2.1Ghz PL250R-VL+
9115-505 P505 P5+ 1.65Ghz
9116-561 P560 P5+ 1.5/1.8 GHz PL1650R-L+
9117-570 P570 P5 1.5/1.65/1.9 GHz PL850R, PL1650R
9117-570 P570 P5+ 1.9/2.2 GHz PL850R+, PL1650R+
9119-590 P590 P5 1.65Ghz PL3250R
9119-595 P595 P5 1.65/1.9Ghz PL6450R
9119-590 P590 P5+ 2.1Ghz PL3250R+
9119-595 P595 P5+ 2.1/2.3Ghz PL6450R+
2jan/11

Resetting the managed system to a nonpartitioned configuration

You can use the Hardware Management Console (HMC) and the Advanced System Management Interface (ASMI) to erase all of your logical partitions and reset the managed system to a nonpartitioned configuration. When you reset the managed system, all of the physical hardware resources are assigned to a single logical partition. This allows you to use the managed system as if it were a single, nonpartitioned server.
Attention: By resetting a partitioned managed system to a nonpartitioned configuration, you will lose all of your logical partition configuration data. However, resetting the managed system does not erase the operating systems and data from disk units on that managed system.

Before you reset the managed system, ensure that the hardware placement in the managed system supports a nonpartitioned configuration. If the hardware placement in the managed system does not support a nonpartitioned configuration, you must move the hardware so that the hardware placement supports a nonpartitioned configuration. For more information about how to place the hardware in your managed system to support a nonpartitioned configuration, contact your marketing representative or business partner.

Also, if you plan to use an operating system that is already installed on one of the logical partitions on the managed system (instead of reinstalling the operating system after you reset the managed system), consider how the console used by that operating system will change when you reset the managed system. If the operating system that you want to use is AIX®, log into AIX and enable the login prompt for the virtual serial port vty0 using either the System Management Interface Tool (SMIT) or the chdev command. You can then reset the managed system, use a physical serial console to log into AIX, and use SMIT or the chcons command to change the console device to the console device you want to use.

You must have an ASMI login profile with an administrator authority level.

Parts of this procedure must be performed at your HMC (not connected remotely). Ensure that you have physical access to the HMC before you begin.

To reset a managed system with logical partitions to a nonpartitioned configuration using the HMC, follow these steps:

Shut down all logical partitions on your managed system using operating system procedures. For more information about shutting down logical partitions using operating system procedures, see the following information:
For logical partitions running AIX, see Shutting down AIX logical partitions.
For logical partitions running IBM® i, see Shutting down IBM i logical partitions.
For logical partitions running Linux®, see Shutting down Linux logical partitions.
For logical partitions running Virtual I/O Server, see Shutting down Virtual I/O Server logical partitions using the HMC.

If the managed system powered off automatically when you shut down the last logical partition, power on the managed system to the Standby state. Complete the following:

- In the navigation pane of your HMC, open Systems Management and click Servers.
- In the work pane, select the managed system, click the Tasks button, and click Operations > Power On.
- Select the power-on mode of Partition Standby and click OK.
- Wait until the work pane displays a Standby state for the managed system.
- Initialize the profile data on the HMC. Complete the following:
- In the work pane, select the managed system, click the Tasks button, and click Configuration > Manage Partition Data > Initialize.
- Click Yes to confirm.
- Clear the logical partition configuration data on the managed system. Complete the following at your HMC (not connected remotely):
- In the navigation pane, click HMC Management.
- In the work pane, click Open Restricted Shell Terminal.
- Type the command:

lpcfgop -m managed_system_name -o clear

- where managed_system_name is the name of the managed system as it is displayed in the work pane.
- Enter 1 to confirm. This step takes several seconds to complete.

Optional: If you no longer intend to manage the system using the HMC, remove the connection between the HMC and the managed system. To remove the connection between the HMC and the managed system, complete the following:
- In the work pane, select the managed system, click the Tasks button, and click Connections > Reset or Remove Connection.
- Select Remove connection and click OK.
- Access the Advanced System Management Interface (ASMI) using a Web browser on a PC. If you do not already have a PC that is set up to access the ASMI on the managed system, you need to set up the PC at this point. For instructions, see Accessing the ASMI using a Web browser.
- On the ASMI Welcome pane, log in using the admin user ID (enter admin into User ID, enter the admin password into Password, and click Log In).
- In the navigation pane, expand Power/Restart Control and click Power On/Off System.
- Set Boot to server firmware to Running.
- Click Save settings and power off.
- Click Power On/Off System periodically to refresh the window. Repeat this step until Current system power state: Off is displayed in the navigation pane.
- Click Save settings and power on.
- Wait for the managed system to restart. It can take several minutes for the managed system and operating system to restart completely.