In a system with redundant Service Processors, the standby Service Processor does not communicate with the domains. In the event of a failover, the newly active Service Processor assumes the IP address of the
DSCP includes its own security measures that prohibit a compromised domain from compromising other domains or the Service Processor.
The DSCP should only be configured when there are no domains running. If you change the DSCP configuration while a domain is active, you have to power off the domain before the Service Processor can communicate with it. Refer to Chapter 4 for more information on domains.
In a typical DSCP configuration, you enter a network address and netmask using the setdscp command. The system then configures the Service Processor IP address and any domain IP addresses according to this formula: the Service Processor gets an IP address that is the network address +1; and each domain gets an IP address that is the Service Processor IP address, + the domain ID, +1. For example, if you enter 10.1.1.0 for the network address, and 255.255.255.0 for the netmask, the showdscp command displays output similar to the following:
XSCF> showdscp
DSCP Configuration:
Network: 10.1.1.0
Netmask: 255.255.255.0
Location Address
XSCF 10.1.1.1 Domain #00 10.1.1.2 Domain #01 10.1.1.3 Domain #02 10.1.1.4 Domain #03 10.1.1.5
...
This scenario minimizes the range of IP addresses needed for DSCP.
XSCF Network InterfacesThe XSCF network configurable settings include the IP address for the active Service Processor, IP address for the standby Service Processor, gateway address, netmask, and network route.
Chapter 3 System Configuration | 19 |