The Access Port is located on the Multifunction I/O
card. The Integrated Access Port is designed for use with PA-RISC HP-PB
I/O base systems to provide a minimal level of remote supportability for
the systems. The Access Port gives the console operator the ability to
read system status and to generate system resets through the console
terminal instead of through the system's front panel display and
switches. It also provides the ability to connect a second console in
parallel with the local console terminal. This "mirrored" console port
is connected to a modem through which the second or remote console is
attached. This provides the same system support functionality to a
remote terminal as is available to a console operator sitting next to
the system.
Series 9X7 Novas have two unique serial hardware ports
found on the MultiFuntion I/O Card (MFIO). The Local Console (LDEV 20)
and the Session Port (LDEV 21). This card is found in slot 14 and it's
part number is A1703-60003. Hardware Path for the Console is 56.0 and
Session Port is 56.1.
The local system console will be directly connected on
Access Port 0 via a 3 meter cable. One end has a 6-pin circular DIN
connector, and the other end has a 25 pin male connector. The modem port
(Access Port 1) is a 25-pin connector and can be used for remote
support as a mirrored console or as a separate user session port.
Access Ports Modes
Terminals connected to the Access Ports may be in one of three operating modes:
Session Mode – LDEV 21 only (perform a 'SHOWME')
Session mode is defined as a direct connection from
the terminal to the host system with the Access Port monitoring but not
acting on any characters transmitted between the terminal and the host.
Console Mode – LDEV 20 only (perform a 'SHOWME')
Console mode is defined as a connection in which the
Access Port monitors the data being transferred and will take special
action on some characters.
Control Mode – CM> prompt after Control-B in Local / Remote Console Mode
Control mode is defined as a mode in which the terminal is in communication
with the Access Port only.
System Console - LDEV 20 or
Access Port 0 (Console) gives the local console operator the ability to
read system status and to generate system resets through the console
terminal instead of through the system's front panel display and
switches. This Port requires no special configuration and does not
support modem connections.
LDEV 21 or Access Port 1
(Remote Modem) has two separate hardware modes requiring configuration.
The normal default is as a Session Port capable of systems sessions
where it is considered to be LDEV 21. Session (LDEV 21) configuration is
done through a special NMMGR field labeled "Go To User Port". This is
necessary as the hardware function is separate from DTC's. Changes to
the User Port do not take effect until you do a start norecovery.
It takes two separate steps to setup Remote Console / Session Port.
Step One
To setup Port 1 as a Session Port for Modems it will
first be necessary to examine LDEV 21. Check whether LDEV 21 is
currently configured and available.
:showdev 21 <enter>
LDEV AVAIL OWNERSHIP VOLID DEN ASSOCIATION
21 A AVAIL
:sysgen <enter>
sysgen> io <enter>
io> ld 21 lists current configuration of LDEV 21
LDEV: 21 DEVNAME: OUTDEV: 21 MODE: JAID
ID: A1703-60003-CONSOLE-TERMINAL RSIZE: 40 DEVTYPE: TERM
PATH: 56/56.1 MPETYPE 16 MPESUBTYPE: 0
CLASS: TERM
Exit sysgen then enter NMMGR
:NMMGR <enter>
Open Configuration <F1>
DTS <F1>
User Port <F4> Configure the LDEV 21 User Port as shown in the
following screen:
HP SUPPORT MODEM PORT SCREEN
This screen lets you configure parameters that affect
the operation of the modem port used by HP support personnel.
When you have entered all the configuration values for
the Support Modem Port, press the Save Data key then press the Prior
Screen key to return to the Host Configuration Screen.
PARAMETERS
Logical Device
The logical device (ldev) number you want to associate
with the port. This ldev number must be the same as the ldev number
configured for the second serial port (Port 1) on the HP-PB SCSI/Console
LAN card. It is normally set to 21.
Line speed
Enter the line speed, in bits per second. Use one of
the supported speeds (300, 1200, 2400, 9600, or 19200 bps). I recommend
9600 Modem type
0 Specifies that modems will not be part of the connection. (Normal Default!!!)
1 Specifies that a US modem will be part of the connection. Use this type!!
2 Specifies that a European modem will be part of the connection.
Parity
Enter the type of parity that will be used if parity is to be enabled. Choices
are None, Even, Odd, 0's, or 1's. Use None as this will allow you to do
binary file transfers.
Save Data key
Saves the data on the current screen. Does not validate the configuration file.
Validate your changes if you made any then reboot the
system. Perform "START NORECOVERY" as is normal for adding or changing a
LDEV. This will then enable LDEV 21 to behave like a modem connection.
Step Two
It is now necessary to configure the "ACCESS PORT" to
match your LDEV 21 (Session Port) configuration. This is unique only to
the remote console port and is where we deviate from the typical DTC
port. To configure the ACCESS PORT you need to be on the system console
where you can execute a CONTROL-B to get the CM> prompt.
CM>HELP <enter>
HP A1703 Access Port Revision 1.0 - 3135
CA - Configure system remote support modem port.
CO - Enter console mode.
CS - Copy screen from local console to remote console.
DI - Disconnect line to remote console terminal.
DR - Disable access by a remote console terminal (enable session access).
DS - Disable display of system status line during console mode.
ER - Enable access by a remote console terminal (disable session access).
ES - Enable display of system status line during console mode.
HE - Display this screen.
**LR - Lock remote (disables all modem modes – in/out).
RS - Stop all processing, initiate SPU selftest, load software from load
device if enabled for autoboot.
SE - Transfer remote terminal from console/control to session mode.
TA - Initiate Access Port selftest.
TC - Transfer processor execution to operating system specific routine.
TE - Send message between the local and remote console terminals.
**UR - Unlock remote (enables modem for remote console, session and dial
out modes).
**Important Note: Do Not Use LR/UR Commands unless modem is
Ideal or HP Support Modem. Non-Ideal or Non-HP Modems will lock-up and you will
need to power cycle modem!
CM>CA <enter>
Current remote support modem port configuration:
Bit rate: 2400 bits/sec
Protocol: Bell
System identification:
Do you wish to change the configuration? (Y/[N]): Y <enter>
Enter your change. <CR> retains the current value.
Current bit rate is 2400 bits/sec. Select the new bit rate.
(0=300, 1=1200, 2=2400, 3=4800, 4=9600, 5=19200): 4 <enter>
Current Protocol is Bell. Select the new protocol.
(0=CCITT, 1=Bell, 2=CCITT_BIS): 1 <enter> (North America uses BELL)
Multifunction I/O PCA Modem Line Behavior (For those who like to know more)
CCITT Mode AP protocol 0 This Works – But don't use it;
the port may disconnect the modem occasionally (See Note* below)
This protocol is known as HP-UX CCITT. The card waits
for RI before raising DTR. It also raises RTS when it raises DTR. If DSR
does not come up within 25 seconds, DTR goes back down. The connection
also depends on CTS and DCD. DCD can drop for up to 400ms before the
connection will drop. CTS must stay high always. Once CTS drops, the
connection starts to drop. A new connection cannot occur until DSR, DCD
and CTS all drop. FS can be programmed to either state via the CA
command.
Bell Mode AP protocol 1 Use this protocol in North America (Does not
support Hardware Handshake)
This is sometimes called Bell simple protocol. It raises DTR when it can
accept a connection. The connection is valid when it sees DCD.
It drives RTS whatever it was when Remote is enabled (usually, RTS is low) and
does not look at DSR or CTS. When a disconnect is done, DCD must drop before
a new connection can be made (i.e. it will not raise DTR until DCD drops).
"If your remote modem is configured for RTS/CTS Flow Control; it will appear
to be hung because RTS is always low"
CCITT_BIS Mode AP protocol 2
This protocol is CCITT V.22bis. It requires the
special cable A1703-63006 which is just like the 92219Q cable with the
exception that pin 9 on the computer end is routed to pin 12 (RS) rather
than pin 22 (RI). DTR is raised whenever a connection is allowed. RTS
follows DSR. A connection is established when DSR is high. CTS can drop
for an indefinite amount of time without dropping the connection. The
card will not send data to the modem when CTS is low. DCD can drop for
up to 400ms before the connection is dropped. Once the connection is
dropped, DSR, DCD and CTS must all go low before a new connection can be
made. RS controls what speed the card sends to the modem. If RS is
high, the programmed baud rate is used. If RS is low, half of the
programmed baud rate is used. If you use the 92219Q cable, the baud rate
will most certainly be half the programmed baud rate, since RI will
almost always be down. FS can be programmed to either state via the CA
command.
*NOTE : CCITT versus BELL:
These protocols are for the local country phone switch
systems. You should stick to the one that your local country requires.
For North America users, the access port should be configured as BELL.
If someone connects from somewhere like Germany where CCITT is used,
Bell will work just fine because at the North America end, the phone
company switch will use BELL protocols.
Current System identification:
New system identification (limited to 1 to 23 displayable characters or
space for none): HP957SX <enter>
New configuration (takes effect at next remote connection):
Bit rate: 9600 bits/sec
Protocol: Bell
System identification: HP957SX CM> ER <enter>
Current remote console access configuration:
Remote CS: Disabled
Mode: Multiple
Password:
Password faults: 03
Do you wish to change the configuration? (Y/[N]): Y <enter>
Enter your changes. <CR> retains the current value.
Remote CS command: Disabled
Select the new setting (E=enabled, D=disabled): E <enter>
Current mode: Multiple
Select the new setting (S=single, M=multiple): M <enter>
Current password:
New password (1 to 18 displayable characters or space if no password is to
be required): TEST <enter>
CAUTION!!! – Always enable
for a password. This prevents the console status line from appearing
upon a remote console connection. The status line has escape sequences
included that can cause your terminal to beep with every update. Very
annoying.
Current password fault limit: 03
New number of password faults(Range: 0-99 or space. Space or 0 for
unlimited password faults): 3 <enter>
New remote console access configuration:
Remote CS: Enabled
Mode: Multiple
Password: TEST
Password faults: 03
Remote console access is now enabled.
CM> UR <enter>
Remote Console answer mode is now unlocked.
This function enables DTR to the modem so the modem
will autoanswer. It is not necessary to spoof(fake) DTR by setting DTR
always enabled on the modem itself.
You have now completed all the necessary steps to allow a remote modem to be
connected for remote console operation. If you want to disable the remote
console to allow session modes use the 'DR' command. To lockout the
modem but keep it in remote console mode use 'LR' lock remote command.
To return to the system prompt do a:
CM> CO <enter>
"It is strongly recommended you use the same Baud Rate
for both Remote Console and Session modes." Sample Remote Console
Session
ATDT4474899
CARRIER 9600 ß Carrier Connection Bit Rate between modems
PROTOCOL: LAP-M <--- Type of carrier modulation protocol (i.e. V.42) in use
COMPRESSION: V.42BIS <--- Advanced compression in use
CONNECT 9600/ARQ <--- error correct in use
LAB HP957SX <--- Access Port System Identification Banner
ENTER PASSWORD:
@
Remote console connected. <control-break sent here>
CAUTION - If your connection looks something like this:
CONNECT 9600/ARQ
Ì Á > ~ f > xÌ x`f f `fxÁfÁ̽̽Ì~± x ½
Check your Access Port Configuration 'CA' for Protocol type; make
sure it is Bell and not CCITT_BIS
Otherwise you have conflicting compression
modes or the remote modem is not setup with the correct Bit Rate (Baud)
for the CA setting. Remember, the Access Port cannot speed sense nor
can it program the modem without a special routine.
BURN5.5P4:HELLO MANAGER.SYS
CPU=5. Connect=1002. WED, FEB 16, 2000, 9:18 AM.
9:18/#S10/63/LOGOFF ON LDEV #20.
9:18/#S12/63/LOGON FOR: "MANAGER.SYS,PUB" ON LDEV #20.
HP3000 Release: C.55.00 User Version: C.55.00 WED, FEB 16, 2000, 9:18 AM
MPE/iX HP31900 C.05.08 Copyright Hewlett-Packard 1987. All rights reserved.
BURN5.5P4:SHOWME
USER: #S12,MANAGER.SYS,PUB (NOT IN BREAK)
RELEASE: C.55.00 MPE/iX HP31900 C.05.08 USER VERSION: C.55.00
CURRENT: WED, FEB 16, 2000, 9:18 AM
LOGON: WED, FEB 16, 2000, 9:18 AM
CPU SECONDS: 0 CONNECT MINUTES: 1
$STDIN LDEV: 20 $STDLIST LDEV: 20 <--- Notice we are actually LDEV 20
<control-b sent here>
BURN5.5P4:@
CM> ß We are now in Access Port Control Mode CM> ca
Current remote support modem port configuration:
Bit rate: 9600 bits/sec ß LDEV 20 Bit Rate
Protocol: Bell ß Type of modem protocol in use
System identification: LAB HP957SX ß Login Banner
Do you wish to change the configuration? (Y/[N]): n
CM> se ß entering session mode from control mode
MPE/iX:hello manager.sys
HP3000 Release: C.55.00 User Version: C.55.00 WED, FEB 16, 2000, 9:42 AM
MPE/iX HP31900 C.05.08 Copyright Hewlett-Packard 1987. All rights reserved.
BURN5.5P4:showme
USER: #S14,MANAGER.SYS,PUB (NOT IN BREAK)
RELEASE: C.55.00 MPE/iX HP31900 C.05.08 USER VERSION: C.55.00
CURRENT: WED, FEB 16, 2000, 9:42 AM
LOGON: WED, FEB 16, 2000, 9:42 AM
CPU SECONDS: 0 CONNECT MINUTES: 1
$STDIN LDEV: 21 $STDLIST LDEV: 21 <---- Notice that in Session Mode we are LDEV 21