HPlogo Communicator e3000 MPE/iX Express 1 Based on Release 7.0 > Chapter 3 New Networking

MPE/iX A-Class and N-Class Console

MPE documents

Complete PDF
Table of Contents
Index

by John Spitzer & Jeff Bandle
Commercial Systems Division

Introduction


The release of MPE on the PA-RISC N-Class and A-Class platforms demonstrates HP's Commercial Systems Division's commitment to supporting the new PCI based I/O architecture for HP e3000 platforms. The change to the PCI I/O architecture affects all devices that are connected to the system. Because this is a new platform for MPE, there are significant changes to the hardware and software used to access and use the system console. This article describes how the new platform affects console commands and operations. Although the hardware and software are changed, you will see minimal changes that affect how the console ports on this platform are used.

Before the MPE operating system is started, all console access is made through connections to the platform's Core I/O card. This article gives a high level overview of the functions present on the Core I/O card and detailed description of the functions used to access the console features.

Console Function Summary


The Core I/O card is a component installed in the N-Class and A-Class systems that contains all the I/O components necessary to configure a bootable system (not including disks and tapes drives and terminals). The core I/O card contains the following functions:

Guardian Service Processor

The Guardian Service Processor (GSP) provides the functionality required for basic console operations to control the hardware before the OS is booted and to provide the connectivity to manage the system. The functions supported by the GSP are similar in nature to those provided by the Access Port (AP) interface on previous platforms. For example, display selftest chassis codes, execute boot commands, determine installed hardware, etc. The GSP has significant additional functionality that significantly improves the security and accessability of the console. By using functions built into the Core I/O card, the N-class and A-class systems can easily be fully managed from any remote location

Serial ports

The three external serial ports perform the same general purposes as on previous platforms.
  • Local console: This port provides a connection for a C1099A terminal. This port provides direct access to the system. The C1099A is the model of terminal that is supported on the console port of the N-Class and A-Class platforms. This terminal supports both the block mode and character mode application that are necessary to configure and manage the system. The local console port is also the default port where console messages are sent. These messages are typically the logon/logoff messages and console requests such as tape requests and spooler status messages. This is configured as ldev 20 on the system.

  • Remote console: This port provides a modem capable port for remote support access. This is the only port on the Core I/O card that supports a modem connection. It is not recommended for this port to be used for general user dial-in access. In most environments, this port is used to provide a remote connection for Predictive support. The supported modem is the Multi-Tech model MT5634ZBA (HP Part No: 0960-1074).

  • UPS port: This port is used solely for support of HP Power Trust Uninterruptable Power Supplies (UPS) connected to the MPE system. These battery power devices are used to ensure a system will stay up during a power failure and that power surges won't damage or destroy the system boards.. The console driver will not allow a user to logon to this port. This behavior is the same as on previous platforms.

The GSP LAN/Console access


This port provides a 10Base-TX connection into the GSP. The system Core I/O card on the N-class and A-class systems contains an imbedded Telnet/TCP/IP networking stack in firmware. Associated with this stack is a 10BT RJ45 networking connectivity port that can be used to perform almost all console functions that are available on the local and remote console ports such as startup and shutdown of the system. There is more detail on the features of this port later in this article. When a telnet connection is established to this port and the user is logged on to the GSP, the user will see a mirrored display of all messages going to the local console port. The user can take write access and perform almost all the system management function that can be performed on the local console.


NOTE: This networking port is NOT the general purpose networking port and can only be used for console access.

GSP LAN Port


This port provides an independent LAN connection to the Core I/O card. This port has its own IP node and telnet server. This port is configured with an IP address, subnet mask and gateway address. When enabled, a connection is established to the port via telnet from any telnet client. The GSP provides the user and password protected logon. This is not a secure telnet connection.

Once a user is logged on to the GSP, the user has the capability to perform almost all of the same console tasks that are available from the local console. This includes full startup and shutdown capability, remote power on/off control, configure and control most GSP operations. The system can be fully managed via a connection to this port. The physical LAN connection to this port is completely independent from the general system LAN and cannot be used to access other MPE functions.

GSP Features


The GSP provides the functionality to locally and remotely manage the system console functions.

Console mirroring

Users of the GSP are categorized with two sets of capabilities.

A console Operator can use the system's console, manage the system when a problem occurs (rebooting it, etc,...), diagnose system failures through GSP logs and allow a pre-configured remote console to connect. This is the usual set of capabilities required to operate and manage a system. A console Administrator has the additional abilities to set up the GSP configuration in order to allow correct system operation and management. This mainly includes configuring login/password and access control and system monitoring features. Once all the configuations are complete the system can be fully operated and managed with the Operator capability only. There are a set of mirroring rules that control what each class of user can do and see while other users are connected at the same time. For example if an operator is the first to log in to the GSP and then an administrator connects, only those commands allowed the operator are available. If an administrator is the first to log on to the GSP and then an operator connects, the operator will have NO mirroring output.


NOTE: If the administrator is connected at a port other than at the local console, the local console is not available. The administrator must disconnect to re-allow access to the local console. If necessary, the remotely connected administrator can be forcebly disconnected by pushing a small reset button on the rear of the system on the Core I/O card.

When enabled, and a user connects to the remote port and/or GSP LAN port, the GSP will mirror console activity to connected users. There is always only one user that has the ability to enter commands. All other connected users will see a message telling them they don't have write access. Write access can be obtained by entering the characters ^Ecf (Ctrl-E cf) within 3 seconds.

Password protected access

All access to the GSP can be protected by username and password authentication. The users can also be configured so that they are allowed only one successful logon. If so configured, when they logoff, the GSP administrator must re-enable access if they want to allow access to that user.

Session ldev

The remote serial port can create a session on a separate ldev. For example, if an ldev is configured on the proper path in Sysgen and NMMGR (typically ldev 21) and remote console access is disabled in the GSP, then a user would log on to that ldev, when they connected to the port. In this case, no GSP access is available. If remote console is enabled and the user is mirroring the console on the remote port, the GSP command 'SE' will suspend console mirroring and establish a connection to the configured ldev.

Remote power up/down

From the GSP interface, the user can power up or down the system. This feature is available unless the front panel switch is turned off. The function behaves almost like the user turned off the front panel switch.

Functionality

Local, remote, UPS ports

On the first three physical serial ports, you will see almost no difference in console functionality between the new PCI driver and the HP-PB (NIO) driver that is available on previous platforms. The driver supports the three serial ports for local console, remote modem port and the UPS port.

Unsupported functionality

There are two console features that are no longer supported on the N-class and A-class systems.
  • AutoDial: This driver does not support outgoing AutoDial. This feature was part of the NIO card firmware and, at one time in the past, Predictive Support was the only known product using autodial to initiate calls. Predictive Support is no longer using this method to initiate calls. Instead Predictive is sending all the necessary modem commands via the normal write path.

  • Speed sense: This was also a built-in feature of the HP-PB (NIO) card. We chose to not implement this because: a) it was difficult to do in the driver; b) there is a limited need to have this on the console.

GSP Commands

The purpose and function of many of the GSP commands are similar to the Access Port commands on previous platforms. There is extensive online help text.

Here is a GSP command summary:

 ==== GSP Help ============================================(Administrator)===
 AC  : Alert display Configuration       PC  : Remote Power Control
 AR  : Automatic System Restart config.  PG  : PaGing parameter setup
 CA  : Configure Asynch/serial ports     PS  : Power management module Status
 CL  : Console Log- view console history RS  : Reset System through RST signal
 CO  : COnsole- return to console mode   SDM : Set Display Mode (hex or text)
 CSP : Connect to remote Service Proc.   SE  : SEssion- log into the system
 DC  : Default Configuration             SL  : Show Logs (chassis code buffer)
 DI  : DIsconnect remote or LAN console  SO  : Security Options & access control
 EL  : Enable/disable LAN access         SS  : System Status of proc. modules
 ER  : Enable/disable Remote/modem       TC  : Reset via Transfer of Control
 HE  : Display HElp for menu or command  TE  : TEll- send a msg. to other users
 IT  : Inactivity Timeout settings       VFP : Virtual Front Panel display
 LC  : LAN Configuration                 WHO : Display connected GSP users
 LS  : LAN Status                        XD  : Diagnostics and/or Reset of GSP
 MR  : Modem Reset                       XU  : Upgrade the GSP Firmware
 MS  : Modem Status

Details of selected commands:

Security Options (SO): This command is used to configure GSP users and passwords. The default configuration is no users are configured. All connections to the GSP have administrator capability.The first user configured is created as administrator. Once created, several console mirroring rules will come into play. For example if an administrator is logged on, then an operator capable user can't log on till the administrator disconnects. If an administrator is connected via the GSP LAN port, no access (not even ^B) is allowed on the local console until the administrator disconnects.If the administrator password is lost, then the user configuration in the GSP must be cleared via a rear panel reset button. The user configuration is cleared by pushing the reset button and then responding to a prompt on the local console within 30 seconds. If the prompt is not answered, then the user configuration is retained.GSP users can be configured for DIAL-BACK access. This means that when that user logs on to the GSP through the remote port, the GSP will hang up and dial that user back at a configured phone number.

Power Control and Status(PC, PS) Allow the user to switch system power ON or OFF. This is almost like turning the system power off at the front panel switch. This will work as long as the real front panel switch is left in the 'ON' position.

Paging parameters (PG): This feature is able to generate a paging message based on the chassis codes that arrive in the GSP. This requires a modem to be connected to the remote port and to be properly configured. On receipt of the appropriate level of alert, the GSP will dial a configured number to send an alpha-numeric page. Part of the alpha-numeric pager message is the string configured in this command, describing the alert level that caused the page.

Upgrade the GSP Firmware (XU): The upgrade is performed using ftp over the GSP LAN. The command provides a dialog that contains a default IP address and anonymous ftp logon to a server where the upgrade files reside. The user can override this location if the files have been copied to a more local server. This command can only be run from the local console port.

Configuration


This section provides information on how to configure the console terminals and the ldevs in Sysgen and NMMGR

NMMGR Configuration

There is no change in the parameters configured in NMMGR, execpt that Modem Type V22.bis is not supported on the N-Class and A-Class systems

Console terminal Configuration

Some of the terminal configuration parameters are important for proper GSP operation. The C1099A terminals connected to the local and remote console ports should be configured with the following parameter settings: All other terminal paramters not mentioned should be left at the default setting. To get to the configuration menus press the [F10] key then [F8].

  F2 Genrl: Emulation=HPTerm
  F6 Ports: EIA Baud Rate=9600
  EIA Data Forma=8/1/N
  EIA Parity Check=Off
  EIA Xmit=No Protocol
  EIA_Recv=Xon-Xoff(XPC)
  Enhanced=On
  F7 Host: Comm Mode=Character     Local Echo=Off
  F9 Emul: Terminal ID: 70096


NOTE: The HP C1099A terminal is the model that is officially supported on the N-Class and A-Class systems. However, there have been no steps taken to preclude operation with other terminals. For example, the GSP does not check the terminal identification. Use other terminals at your own risk. The 700/9x family of terminals is known to work but have not been certified on this platform.

Sysgen Configuration

The following data shows the details of the information that needs to be added to the IO configuration in Sysgen in order to configure the core I/O serial devices. The ldev 20 configuration is shown. The configuration of the remote session and UPS devices are the same except for the PATH and LDEV paramters. Additionally, the UPS port requires the class HPUPSDEV to be assigned. Note the two new ID's 'PCI_CONSOLE' and 'C1099A' created for these entries.

 io> lp 0/0/4/0
  PATH:  0/0/4/0                                LDEV:
    ID:  PCI_CONSOLE                          TYPE: DA
  PMGR:  PCI_CONSOLE_DAM                     PMGRPRI:     6
  LMGR:                                       MAXIOS:     0
 io> lp 0/0/4/0.0
  PATH:  0/0/4/0.0                              LDEV:   20
    ID:  C1099A                                 TYPE: TERM
  PMGR:  CDM_CONSOLE_DM                      PMGRPRI:     9
  LMGR:  TIO_TLDM                             MAXIOS:     0
 io> ld 20
  LDEV:    20  DEVNAME:                    OUTDEV:       20   MODE:  JAID
    ID: C1099A                             RSIZE:        40   DEVTYPE: TERM
  PATH: 0/0/4/0.0                          MPETYPE:      16   MPESUBTYPE:  0
  CLASS: TERM

I/O paths used for the core I/O serial ports.

The serial ports on the Core I/O card are configured on the following I/O paths:

    0/0/4/0.0 - console; Ldev 20
    0/0/4/0.1 - remote session
    0/0/4/0.2 - UPS device

Modem protocols

CCITT Mode - In this protocol the driver waits for RI before raising DTR. It also requires the modem to assert DSR, RTS and DCD before a connection is established.

Bell Mode - This is sometimes called Bell simple protocol. The driver raises DTR when it can accept a connection. The connection is valid when the driver sees DCD from the modem.

The remote session path must be configured for a modem protocol. The GSP uses the 'drop of modem line' commands to the card to detect session termination.

With this new console functionality, system managers of MPE based N-Class and A-Class systems will be able to use their existing applications on the console, as well as access the console from more remote locations with minimal extra hardware setup. A few simple commands to configure the console networking and remote lan access will be enabled.

Conclusion

The new and retained features of the N-Class and A-Class console provide the ability to fully manage the HP e3000 from local and remote locations with a minimum of additional hardware and no additional software. A few simple commands are all that are required to configure and access these powerful system management capabilities. These features make it easy to manage the system in a wide variety of data center environments.




Chapter 3 New Networking


PCI WAN Sync MUX (Adapter Card and Driver)