Connection Port Naming (N1 Provisioning Server 3.1, Blades Edition, Installation Guide)

N1 Provisioning Server 3.1, Blades Edition, Installation Guide

Connection Port Naming

The following table shows the port naming used in the following sections for the servers, switches, and chassis SSC devices.

Table 3–2 Device Port Naming


Logical Port Name	Role
`eri0`	Control plane server connection to the control plane switch for the Service Processor (SP), control plane database (CPDB), and Control Center (CC) provisioning command transfer. Note – In a single chassis-single SSC installation with no external switch, `eri0` connects to the `NETMGT` port of the SSC.
`eri1`	Control plane server connection to the local intranet. The Control Center Management PC is usually connected to the local intranet.
`ce0/skge0`	Control plane server gigabit connection to the data plane switch for operating system image flash and JumpStart installations for server blades
`NETMGT`	Chassis switch and system controller connection to the control plane switch for provisioning command transfer.
`NETP0`	Chassis switch and system controller gigabit connection to the data plane switch for operating system image flash and JumpStart installations for server blades
`NETP1`	Chassis switch and system controller gigabit connection to a separate image server if an external data plane switch is not used.
`NETP1` through `NETP6`	Unused chassis switch and system controller connections.
`NETP7`	Uplink when the installation does not have a data plane switch. See Figure 3–3.

The Wiring Mark-up Language (WML) file contains the logical port name. The table shows only the physical name for each type of connection. Gigabit Ethernet connections are recorded in WML as eth0, eth1, or ethN.
The gigabit Ethernet card is designated ce0/skge0, and can be either the Sun GigaSwift card (ce) or the SysKonnect card (skge0). If you select a card made by another vendor this designation might change. Control plane servers can also have a Gigabit Ethernet card.