Each N1 Provisioning Server control plane component must be assigned IP addresses within a single subnet. Each chassis SSC controller must be IP-accessible from the control plane server and the subnet. For added security, the subnet to which you assign the components should be an internal subnet and not an external subnet:
Internal subnets are used to create IP address namespaces for I-Fabric CPU devices that do not require network connectivity outside the corporate network (for example, to the Internet) via an external router. Internal subnets are defined based on an internal corporate IT convention to prevent namespace collisions between various internal subnets. Check your internal subnet namespace scheme for availability of internal subnet addresses for use within the I-Fabric. Enter these subnets as internal subnets during installation.
External subnets are assigned by an outside entity to a corporate network when I-Fabric CPU devices require connectivity outside the corporate network. If your I-Fabric is connected to an external router and you want the CPU devices in a farm to access the Internet, check your external subnet namespace scheme for availability of external subnet addresses for use within an I-Fabric. Enter these subnets as external subnets during installation.
If you choose to use a different IP addressing structure, make note of the IP address assignments for each component. You are prompted for the IP addresses of the components during installation.
The following tables provide suggested IP address assignments for the N1 Provisioning Server and optional separate N1 image server, and the chassis components. The subnet addressing scheme 10.5.141.xx is only used as an example in the following tables.
Refer to the Solaris 8 Administration Guide for the procedure for setting server IP addresses.
Refer to the Sun Fire B1600 Blade System Chassis Switch Administration Guides for the procedure for setting chassis component IP addresses.
Machine |
IP Assignment |
---|---|
Cisco control plane switch |
10.5.141.10 |
Combined N1 Provisioning Server and Image Server (control plane server) |
Port eri0: 10.5.141.18 |
Stand-alone N1 Provisioning Server (control plane server) |
Port eri0: 10.5.141.18 |
Stand-alone N1 Image Server |
Port eri0: 10.5.141.20 Port eri1: 10.5.141.22 |
The SSC login and password for each chassis system switch and system controller must be identical for all SSCs in all chassis. For procedures describing how to set the SSC switch and controller logins and passwords, see the Sun FireTM B1600 Blade System Chassis Administration Guide
Table 3–4 Blade System Chassis Component IP Address Assignments
Component |
Chassis 1 |
Chassis 2 |
Chassis 3 |
Chassis N |
---|---|---|---|---|
Virtual IP (VIP) |
10.5.141.50 |
10.5.141.55 |
10.5.141.60 |
Prior Chassis VIP address +5 |
System Controller 0 (SSC0) |
10.5.141.51 |
10.5.141.56 |
10.5.141.61 |
Prior Chassis SSC0 address +5 |
System Controller 1 (SSC1) |
10.5.141.52 |
10.5.141.57 |
10.5.141.62 |
Prior Chassis SSC1 address +5 |
Switch 0 (SW0) |
10.5.141.53 |
10.5.141.58 |
10.5.141.63 |
Prior Chassis SW0 address +5 |
Switch 1 (SW1) |
10.5.141.54 |
10.5.141.59 |
10.5.141.64 |
Prior Chassis SW1 address +5 |
Set the IP address, netmask, and gateway for each chassis SSC switch according to your control subnet as described in the following procedure.
Use telnet to access the chassis SSC.
To set up the SSC, type setupsc.
The following messages appear.
Entering Interactive setup mode. Use Ctrl-z to exit & save. Use Ctrl-c to abort Do you want to configure the enabled interfaces [y]? |
Type y to configure the SSC.
You are prompted in succession for each SSC configuration value. The default values are shown in brackets ([]).
The default values for the SSC IP address, netmask, and gateway are as follows.
Enter the SC IP address [10.5.132.65]: Enter the SC IP netmask [255.255.255.0]: Enter the SC IP gateway [10.5.132.1]: |
Type the address if your chosen address is different, or press Enter to accept the default.