CNA RMD1 Implementation Guide - Public Support Login - Unisys

ClearPath Network 

Appliance 

RMD1 

Implementation Guide 

Printed in USA 

February 2004 3827 2928–001


Appliance 



© 2004 Unisys Corporation. 

All rights reserved. 

Printed in USA 

February 2004 3827 2928–001 

UNISYS

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information 

described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to 

purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the 

products described in this document are set forth in such agreement. Unisys cannot accept any financial or other 

responsibility that may be the result of your use of the information in this document or software material, including 

direct, special, or consequential damages. 

You should be very careful to ensure that the use of this information and/or software material complies with the laws, 

rules, and regulations of the jurisdictions with respect to which it is used. 

The information contained herein is subject to change without notice. Revisions may be issued to advise of such 

changes and/or additions. 

Notice to U.S. Government End Users: This is commercial computer software or hardware documentation developed at 

private expense. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys standard 

commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract data 

rights clauses. 

Correspondence regarding this publication can be e-mailed to doc@unisys.com. 

Unisys and ClearPath are registered trademarks of Unisys Corporation in the United States and other countries. 

All other brands and products referenced in this document are acknowledged to be the trademarks or registered 

trademarks of their respective holders.


Appliance 



ClearPath 

Network 

Appliance 


Implementation 

Guide 

3827 2928–001 3827 2928–001 

Bend here, peel upwards and apply to spine.

Contents 

Section 1. Introduction 

About This Guide .................................................................................. 1–1 

ClearPath Network Appliance (CNA) Features...................................... 1–1 

An Overview of the Hardware .............................................................. 1–3 

CNA Styles........................................................................... 1–4 

CNA Front View................................................................... 1–5 

CNA Back Views.................................................................. 1–7 

FC-SL LEDs.......................................................................... 1–9 

CNA in a ClearPath System ................................................................ 1–10 

System Configuration Rules ............................................................... 1–11 

CNA Software ..................................................................................... 1–13 

Section 2. Installing the CNA Operating System Image 

Guidelines for Installing the CNA Image............................................... 2–1 

Overview of the Installation Process .................................................... 2–2 

Establishing a NetMeeting Connection to CNA.................................... 2–2 

Installing NetMeeting .......................................................... 2–3 

Working with NetMeeting ................................................... 2–3 

Establishing a Connection to CNA....................................... 2–5 

Installing the CNA Operating System Image ........................................ 2–7 

Performing a CNA Safe Boot............................................... 2–8 

Installing the CNA Image..................................................... 2–9 

Section 3. Configuring the CNA 

Overview of CNA Configuration............................................................ 3–1 

IP Addressing Information for CNA Devices ....................... 3–2 

Configuring a CNA ................................................................................ 3–4 

Configuring Shared Adapter Features................................................. 3–12 

Preparing to Use Port Aggregation.................................... 3–12 

Preparing to Use Ethernet Jumbo Frames........................ 3–13 

Preparing to Use IEEE 802.1Q VLANS.............................. 3–14 

Configuring IEEE 802.1Q VLANs or Port Aggregation........................ 3–15 

Configuring IEEE 802.1Q VLANs....................................... 3–17 

Saving Your Settings ......................................................... 3–18 

Restoring Your Settings..................................................... 3–21 

Assigning the Advanced Features Adapter to the 

MCP .............................................................................. 3–22 

3827 2928–001 iii

Contents 

Section 4. Installing Network Services Software on the CNA 

Preparing to Install Network Services ...................................................4–1 

Network Services Installation Procedure...............................................4–2 

Section 5. Installing ODT and NT-IOP Software 

Installing ODT and IOP Files..................................................................5–1 

Installing Web Enabler..........................................................5–3 

Configuring a CNA for ODT Mode .......................................5–4 

Configuring a Redundant ODT Connection..........................5–5 

Bringing a CNA Into Service ..................................................................5–7 

Section 6. CNA Operations 

ODT Commands ....................................................................................6–1 

Bringing a CNA Up.................................................................................6–2 

Powering a CNA Down..........................................................................6–3 

Resetting a CNA ....................................................................................6–3 

Precautions When Configuring and Using CNA ....................................6–3 

Section 7. Troubleshooting the CNA 

CNA Debug Flow Chart .........................................................................7–2 

CNA Debug Checklist Procedure...........................................................7–3 

Private LAN Ping Procedure ..................................................................7–5 

EVLAN Ping Procedure..........................................................................7–5 

Public LAN Ping Procedure....................................................................7–7 

Event Log Procedure .............................................................................7–8 

Troubleshooting the NetMeeting Procedure.........................................7–9 

Performing a CNA Safe Boot...............................................................7–10 

Log and Dump File Retrieval ...............................................................7–11 

Appendix A. Sample Network Initialization Files 

CNS Initialization File ............................................................................ A–2 

TCP/IP Initialization File......................................................................... A–3 

Index .................................................................................................................. 1 

iv 3827 2928–001

Figures 

1–1. ClearPath Network Appliance (CNA).................................................................. 1–1 

1–2. CNA Front View ................................................................................................. 1–5 

1–3. CNA Back Views ................................................................................................ 1–7 

1–4. NIC Card LEDs ................................................................................................... 1–8 

1–5. FC-SL LEDs ........................................................................................................ 1–9 

1–6. CNA in a ClearPath System ............................................................................. 1–10 

1–7. Typical CNA Configuration ............................................................................... 1–11 

1–8. Complex CNA Configuration ............................................................................ 1–12 

1–9. CNA Software Interfaces ................................................................................. 1–13 

7–1. CNA Debug Flowchart ....................................................................................... 7–2 

3827 2928–001 v

Figures 

vi 3827 2928–001

Tables 

3–1. IP Addresses ...................................................................................................... 3–2 

3827 2928–001 vii

Tables 

viii 3827 2928–001

Section 1 

Introduction 

About This Guide 

This guide describes the RMD1 ClearPath Network Appliance (CNA) on ClearPath Plus 

servers. It also provides the information needed to 

• Install the operating system software on the CNA 

• Configure the operating system software 

• Install Network Services software on the CNA 

• Install operator display terminal (ODT) software on the CNA 

• Operate and troubleshoot the CNA 

ClearPath Network Appliance (CNA) Features 

The RMD1 CNA is a dedicated system housed in a 1U-high rack-mounted unit. It 

provides the operator display terminal (ODT) interface and the communications front end 

for ClearPath Plus servers. Figure 1-1 illustrates the CNA. 

Figure 1–1. ClearPath Network Appliance (CNA) 

3827 2928–001 1–1

Introduction 

The CNA provides the following features: 

• Provides E-mode communications for ClearPath servers. 

• Handles network traffic between the ClearPath host and the network without using 

the existing Windows servers. This removes network communications from the 

existing Windows servers and reduces the cost of network communications. 

• Provides ODT capability. 

• Reduces the possibility of external network attacks on the operating system, thereby 

improving ClearPath system security. 

• Is dedicated to networking and ODT capability and is closed to user applications, 

thereby improving overall reliability. 

• Is a dedicated component that offers both an economic and physical advantage over 

an existing full-featured Windows NT server. 

1–2 3827 2928–001

An Overview of the Hardware 

The CNA uses high-quality PC server components. The major components are 

Introduction 

• Intel-based motherboard supporting 

− Single 2.4-GHz Intel Xeon processor 

− 1 GB of ECC supported SDRAM 

− On-board video controller 

− 10/100/1000 private LAN for system management 

• Two IDE RAID mirrored hard disks 

• CD-ROM drive for loading system software with a data transfer speed of a least 32X 

• Floppy disk drive; 3.5-inch 1.44-MB drive 

• Public LAN Gigabit Ethernet network interface cards (NICs) 

• One fiber optic link from the FiberChannel-SuperLite (FC-SL) card for connecting to 

the host server 

Note: There are no field-replaceable units (FRUs) in the CNA. The FRU for the CNA is 

the entire rack-mounted unit. 

3827 2928–001 1–3

Introduction 

CNA Styles 

The following CNA styles are available: 

• RMD1-GEC (Copper Gigabit Ethernet) 

This style contains: 

− Four 10/100/1000 links from the quad-port NIC for public LAN connections 

− One RJ45 10/100/1000 link from the on-board LAN port for connecting to the 

private (maintenance) LAN 

− One fiber optic link from the FC-SL card for connecting to the ClearPath host 

• RMD1-GEF (Fiber-optic Gigabit Ethernet) 

This style contains: 

− Two fiber-optic Gigabit Ethernet links from the dual-port NIC for public LAN 

connections 

− One RJ45 10/100/1000 link from the on-board LAN port for connecting to the 

private (maintenance) LAN 

− One fiber-optic link from the FC-SL card for connecting to the ClearPath host 

1–4 3827 2928–001

CNA Front View 

Introduction 

Figure 1-2 illustrates a front view of the CNA and identifies the locations of the peripheral 

devices used. The drives, indicators, and power buttons reside behind a lockable bezel. 

M N O P Q 

Figure 1–2. CNA Front View 

A B C D E F G H 

I J K L 

A. Private LAN activity LED – Indicates on-board private (maintenance) LAN 

activity. Green when there is a link. Blinks when there is traffic. 

B. Line 3 (Opt) activity LED – Not used. 

C. Power LED – Green when power is on. 

D. Power button – Momentary switch that turns power on and off. To activate, press 

and release the button; do not hold it down. There is a delay of a few seconds from 

when you release the button to when power actually goes off. Note: There is still 

3827 2928–001 1–5 

090

Introduction 

standby power in the chassis when the power is off. To power off the CNA, you should 

normally: 

1. Log on to the system with NetMeeting. 

2. Shut down from Windows. 

3. If you cannot perform steps 1 and 2, verify that the Fixed Disk Drive Status LED 

(F in the figure) is off for at least 10 seconds, and then press the Power button. 

E. System Status LED – Continuous green when status is normal. Blinking green 

when operating in degraded condition. Continuous amber when there is a hardware 

fault. Blinking amber when there is a hardware warning. Off when CNA is powered off 

or there is no AC power. 

F. Fixed disk drive status LED – Random green when drive is being accessed. 

Yellow when there is a disk fault. 

G. ID LED – Blue when ID button is pressed. 

H. ID button – When pressed, the ID LEDs on the front and back turn blue. This helps 

an operator find the correct CNA in a rack with multiple CNAs. 

I. Video connector – Not used. 

J. NMI button (tool assisted) – Non-maskable interrupt, which forces a dump and 

reboot. Not for normal operation. 

K. USB port – Not used. 

L. Reset button – Momentary switch that resets the box. To reset, you should 

normally: 

1. Log on to the system with NetMeeting. 

2. Shut down from Windows. 

3. If you cannot perform steps 1 and 2, verify that the Fixed Disk Drive Status LED 

(F in the figure) is off for at least 10 seconds, and then press the Reset button. 

M. Floppy activity LED – Green when drive is being accessed. 

N. CD-ROM/DVD activity LED – Green when drive is being accessed. 

O. CD-ROM drive eject button 

P. Manual CD-ROM drive eject button (tool assisted) 

Q. Floppy drive eject button 

1–6 3827 2928–001

CNA Back Views 

Introduction 

At the back of the CNA are the connections to the ClearPath host and to the public and 

private LANs. All other connectors, such as parallel and serial ports, mouse and 

keyboard connectors, and monitor connector should not be used. Figure 1-3 illustrates 

the back view of the Copper Gigabit Ethernet CNA (RMD1-GEC) and the Fiber-Optic 

Gigabit Ethernet CNA (RMD1-GEF). 

RMD1-GEC 

FC-SL Connection 

RMD1-GEF 

FC-SL Connection 

Not Used 

Maintenance LAN 

Connection 

Not Used 

Maintenance LAN 

Connection 

Not Used 

Not Used 

NIC Card 

NIC Card 

Figure 1–3. CNA Back Views 

Public LAN 

Connection 


Connection 

Public LAN connections – Connect the CNA to the public network. The CNA fiberoptic 

Gigabit Ethernet (RMD1-GEF) NIC supports two fiber optic Gigabit Ethernet links. 

The copper Gigabit Ethernet (RMD1-GEC) NIC supports two 10/100/1000 links. There is 

also an additional RJ45 10/100/1000 LAN connection with the RMD1-GEC style. 

Private (maintenance) LAN connection – Only the RJ45 10/100/1000 LAN 

connector is used. It provides the connection to the private LAN. 

3827 2928–001 1–7 

092

Introduction 

NIC Card LEDs 

Figure 1-4 illustrates the LEDs on the two types of NIC cards. 

Copper Gigabit Ethernet 

PORT D 

Fiber-Optic Gigabit Ethernet 

10/100/1000 10/100/1000 10/100/1000 10/100/1000 

ACT/LNK ACT/LNK ACT/LNK ACT/LNK 

ACT/LNK 

ACTLNK B 

PORT C 

1–8 3827 2928–001 

PORT B 

ACTLNK A 

PORT A 

ACT/LNK 

Figure 1–4. NIC Card LEDs 

ACT/LNK LED – Indicates if the port is connected to a valid link partner. Green when 

there is a link; blinks when there is traffic. For the copper NIC only, flashes yellow to 

identify the port when you use the Identify Adapter button through the Intel PROSet 

software. Helps an operator find a specific port. 

10/100/1000 LED – For the copper NIC only. Indicates the speed the port is using, 

where: 

Off = 10 Mbps 

Green = 100 Mbps 

Yellow = 1000 Mbps 

ACT/LNK 

001 

002

FC-SL LEDs 

Figure 1-5 illustrates the LEDs on the FC-SL. 

2Gb 

Introduction 

3827 2928–001 1–9 

ACT 

LINK 

SFP 

Figure 1–5. FC-SL LEDs 

LINK LED – Green LED that indicates if there is a good link (cable connection) between 

the CNA and the host FC-IOP it is connected to. Green when there is a link. 

ACT LED – Yellow LED that blinks when there is traffic; the frequency of the blinking 

varies with the amount of network traffic. If the LED stays on after booting up, this 

indicates that the card has not passed self test or that NNS software is not installed. 

2Gb LED – Blue LED that indicates the speed the port is using, where: 

Off =1 Gbps 

Blue =2 Gbps 

036A

Introduction 

CNA in a ClearPath System 

Figure 1-6 shows where the CNA fits into a ClearPath system, including: 

• Networking Services (NNS), which is part of the CNA 

• CNA connecting to the ClearPath system through an FC-SL card 

• The ODT interface on the CNA 

• Public LAN connections 

CNA uses the motherboard LAN connection for remote management of the CNA box. 

Since CNA is a “headless” system (that is, no monitor or keyboard), it supports a remote 

GUI interface. The remote GUI uses NetMeeting to configure and support the CNA 

system. NetMeeting is installed on the Service Processor and may be installed on the 

optional Windows partition installed in the ClearPath system or on the optional ODW. 

Windows 

Partition 

(Optional) 

MCP 

Partition 

TCP/IP 

LAN 

IPL 

FC-IOP 

FC-IOP 

FC-IOP 

CSE SP 

Switch 

Modem 

ODT 

(optional) 

1–10 3827 2928–001 

LAN 

ODT 

FC-SL 

LAN 

ODT 

FC-SL 

NNS 

NNS 

Figure 1–6. CNA in a ClearPath System 

CNA 

LAN 

LAN 


LAN 

LAN 

040

System Configuration Rules 

The CNA is an integral part of the ClearPath system. 

Introduction 

− The minimum configuration is one CNA per partition 

− A redundant network and ODT configuration has two CNAs per partition, 

connected to a single FC-IOP in the host. 

− A fully redundant configuration has two CNAs per partition, connected to two 

FC-IOPs in the host. 

Figure 1-7 illustrates a typical CNA configuration for a ClearPath system with two 

partitions. It identifies the CNA naming convention (CNA1–CNA4) for each MCP 

partition/power domain and shows the 8-port switches on the private LAN. 

Windows 

Partition 

0 

MCP 

Partition 

0 

MCP 

Partition 

1 

Windows 

Partition 

1 

ODT 

IPL 0 

SP 0 

CNA1 




SP 1 

IPL 1 

ODT 

192.168.222.41 

*1 

192.168.222.1 

192.168.222.151 

192.168.222.153 

192.168.222.154 

192.168.222.152 

192.168.222.2 

*1 

192.168.222.42 

8-port Switch 

Power Domain 0 


8-port Switch 

Figure 1–7. Typical CNA Configuration 

192.168.222.149 or 20 

Note: 

2 MCP Partitions, 2 CNAs per partition 

All IP addresses are 192.168.222.X 

*1 IP address depends on subDIB 

046 

3827 2928–001 1–11

Introduction 

Figure 1-8 illustrates a more complex configuration of a dual domain system. It identifies 

the CNA naming convention (CNA1–CNA24) for each MCP partition/power domain and 

shows the 8-port and 16-port private LAN switches. 

Windows 

Partition 

0 

MCP 

Partition 

0 

MCP 

Partition 

1 

Windows 

Partition 

1 

ODT 

IPL 0 

SP 0 













SP 1 

IPL 1 

ODT 

192.168.222.41 

*1 

192.168.222.1 

192.168.222.151 

192.168.222.2 

*1 

192.168.222.42 

8-port Switch 16-port Switch 

153 

155 

157 

159 

161 

162 

160 

158 

156 

154 

152 



8-port Switch 16-port Switch 













1–12 3827 2928–001 

163 

165 

167 

169 

171 

173 

174 

172 

170 

168 

166 

164 

192.168.222.149 or 20 

Note: 

2 MCP Partitions, 12 CNAs per partition 

All IP addresses are 192.168.222.X 

*1 IP address depends on subDIB 

045 

Figure 1–8. Complex CNA Configuration

CNA Software 

Figure 1-9 shows the software components in a CNA. 

Fibre 

Channel 

(to host) 

Legend: 

FC-SL 

FID 

(driver) 

ODT 

Installer 

LOM = LAN on Motherboard 


Installer 

NIC = Network Interface Card 

NNS =Network Services 

FID = FC-SL Interface Driver 

ODT = Operator Display Terminal 

NT Embedded 

Image 

NNS 

(TCP Offload SA, etc.) 

NNS 

Installer 

Figure 1–9. CNA Software Interfaces 

Introduction 

3827 2928–001 1–13 

LOM 

NIC 

NIC 

NIC 

(GEC 

only) 

NIC 

(GEC 

only) 

Private 

LAN 

Public 

LAN 


LAN 


LAN 


LAN 

The CNA operating system is the Windows NT Embedded Edition and is built using 

Target Designer. Since CNA is a headless system, there is no monitor, keyboard, or 

mouse. The CNA operating system image resides on the RAID disk. 

The NNS networking software is the network interface software between the E-mode 

host and the public LAN. The public LAN NICs include 10/100 Ethernet and Gigabit 

Ethernet and use Windows 4.0 drivers. 

The private LAN interface supports the NetMeeting remote GUI, MCP Call Home, and 

Windows FTP. 

The FC-SL board has its own driver (FID), which is part of the NNS software. 

The ODT also communicates across the private LAN, using NT-IOP. 

047

Introduction 

1–14 3827 2928–001

Section 2 

Installing the CNA Operating System 

Image 

This section provides the information required to install the ClearPath Network Appliance 

(CNA) operating system image. It contains procedures to 

• Establish a NetMeeting connection to CNA 

• Perform a CNA safe boot 

• Install the CNA operating system image on the RAID hard disk 

Guidelines for Installing the CNA Image 

The CNA operating system image contains the Microsoft Windows NT Embedded 

software and the components required for building a bootable system. The image is 

installed at the factory so the CNA system arrives ready for use. You do not need to 

reinstall the CNA image before installing Network Services software (see Section 4). 

However, you may need to reinstall the image if you are 

• Upgrading to a new release level of the CNA image 

• Correcting certain problem conditions, such as a configuration problem. See Section 

7 for information on troubleshooting the CNA. 

The rest of this section provides instructions for reinstalling the CNA operating system 

image. 

3827 2928–001 2–1

Installing the CNA Operating System Image 

Overview of the Installation Process 

To reinstall the CNA image, you need the following: 

• CNA Safe Boot floppy disk 

The CNA Safe Boot disk directs the boot to occur on the CNA_Safe partition on the 

hard disk. This is only required when a new image needs to be stored on the 

CNA_Primary partition. 

• CNA Images CD-ROM 

The CNA Images CD-ROM contains the shipped CNA images. The images are 

located in separate directories, as follows: 

• RMD1_GEC contains the image for the Copper Gigabit Ethernet style CNA. 

• RMD1_GEF contains the image for the fiber-optic Gigabit Ethernet style CNA. 

• The NetMeeting directory contains NetMeeting installation and Readme files. 

When you reinstall the CNA image, the image that corresponds to the hardware style of 

your CNA system is loaded from the Images CD-ROM to the CNA_Primary partition. 

Establishing a NetMeeting Connection to CNA 

Since the CNA is a “headless” system with no monitor, keyboard, or mouse, a remote 

GUI is required to view and monitor the CNA system. The remote GUI runs across the 

secure private maintenance LAN between the CNA and a remote Windows system. The 

remote system uses the Microsoft NetMeeting software to establish a session between 

the two systems. 

The remote system running NetMeeting can be any of the following Windows systems: 

• The ClearPath Service Processor 

• The Windows enterprise server 

• An Operator Display Workstation (ODW) attached to the maintenance LAN 

• A laptop system connected to the private maintenance LAN 

2–2 3827 2928–001

Installing NetMeeting 


NetMeeting is preinstalled on the Service Processor. It is also included in the 

\NetMeeting directory of the CNA CD-ROM. 

If you copy NetMeeting from the CD-ROM, review the Readme help file and follow the 

simple instructions to install it on the remote Windows system. 

Working with NetMeeting 

Note the following when working with NetMeeting: 

• Sometimes NetMeeting will not establish a session with the CNA even though a 

“ping” of the CNA is successful. You can usually fix this problem by closing the 

NetMeeting window and then restarting NetMeeting. 

• Use the correct IP address. 

• The NetMeeting full screen option makes it easier to work with NetMeeting. 

Once the connection is established, the familiar Logon dialog prompt “Press 

Ctrl+Alt+Del to Login” is displayed. Do not press Ctrl+Alt+Del since this key sequence 

is interpreted by your local PC. Instead, click Send Ctrl+Alt+Del from the Control 

menu in the upper left of the NetMeeting screen. The NT logon dialog box appears. 

Once connected to the CNA, you are prompted to enter the UserID/Password. On the 

Remote Desktop Sharing Password screen, enter Administrator for both, and click 

OK. Note that Administrator is case-sensitive and must be entered as shown here: 

3827 2928–001 2–3


Note: If you enter an invalid password four consecutive times, the following error 

message is displayed on the NetMeeting window: 

The Other person didn’t allow you to join the meeting. 

All additional attempts to “place a call” to the CNA device will result in the same 

error message, regardless of the terminal from which the call attempt is made. This 

is a NetMeeting security feature to prevent unauthorized access. When this error 

message is displayed, you must reboot the CNA device to retry the NetMeeting 

login. This will give you four more chances to enter the correct password. 

After successfully logging on, the NT desktop of the CNA appears. 

2–4 3827 2928–001

Establishing a Connection to CNA 


To establish a connection to the CNA using NetMeeting, follow these steps: 

1. Start NetMeeting from the remote Windows system. The NetMeeting - Not in a Call 

screen appears: 

2. Place a new call by clicking the telephone icon, or select Call on the menu bar and 

then click New Call on the drop-down menu. The Place A Call screen appears: 

Note: 

You can create a speed dial entry from the NetMeeting Call menu. Click Create Speed 

Dial in the Create Speed Dial dialog box and then enter the IP address in the Address 

box and where to call from in the Call using box. Then select the appropriate button to 

add this entry to a Speed Dial list or to save it on your desktop. 

3827 2928–001 2–5


3. On this screen: 

a. Enter the IP address of the CNA in the To: box. Use the IP address configured 

at the factory or refer to Table 3-1 for the correct address. Note that the IP 

address for each CNA is also on the label on the back of the CNA. 

If this is an image installation, use the IP address on the boot floppy disk label 

(192.168.222.150). 

b. Select Require security for this call (data only) and click Call. 

4. From the Remote Desktop Sharing Password screen (shown earlier in this section), 

log onto the CNA by entering Administrator in the User and Password fields and 

clicking OK. 

The NT desktop of the CNA is displayed. You can now install the CNA operating 

system image. 

2–6 3827 2928–001



The working operating system image (Windows NT Embedded) is preinstalled on a new 

CNA. However, under certain problem conditions or for upgrades, you may need to 

reinstall the software. (See Section 7 for CNA troubleshooting procedures.) 

When reinstalling a new CNA operating system image or repairing a defective image, 

certain configuration settings can be lost. The following settings are automatically saved 

for you to the D drive (and, optionally, on a floppy) by the CNAcfg.exe utility: 

• User/password 

• IP address of the private (maintenance) LAN 

• The CNA computer name 

• Other LAN settings including Jumbo Frames configuration on Gigabit Ethernet 

appliances 

You should save these configuration settings on a floppy disk since the settings will be 

reset to their factory defaults once you have reloaded the operating system image. 

After saving these configuration settings, perform the installation steps in the next 

subsection to reinstall the operating system image. You will need the following media: 

• CNA Safe Boot floppy disk 

• CNA Images CD-ROM 

• ClearPath Network Services installation CD-ROM 

3827 2928–001 2–7


Performing a CNA Safe Boot 

The first step in installing a working CNA image is to boot the system from the 

CNA_Safe image on the hard disk as follows: 

1. Insert the CNA_Safe Boot floppy disk. The boot disk contains a Boot.ini file that 

re-directs the boot process to the CNA_Safe directory on the hard disk. 

2. Power on or restart the CNA. 

The system boots from the CNA_Safe Image on the hard drive. There is no visual 

indication of boot completion—wait for all drive activity to finish (about 3 to 5 

minutes). 

3. If the boot is successful, start NetMeeting to establish the connection and log on to 

the CNA (see “Establishing a NetMeeting Connection to CNA” in Section 2 of this 

guide). 

Your Windows system must be attached to the private LAN and configured to 

connect to the reserved IP address (192.168.222.150) specified on the label of the 

boot floppy. This is always the address of the CNA when you boot from the hard 

disk. This means that you can only have one device booted from the CNA_Safe 

Image at a time. Otherwise, you would have duplicate IP addresses on the private 

LAN if you booted more than one CNA from the CNA_Safe directory on the hard 

disk. Under normal circumstances, you should not change this address. 

Note: Sometimes NetMeeting will not establish a session with the CNA even 

though a Ping of CNA is successful. You can usually resolve this by closing the 

NetMeeting window and restarting NetMeeting. 

4. When the Remote Desktop Sharing Password dialog box appears, enter 

Administrator in the User and Password boxes and click OK to log on to the CNA. 

2–8 3827 2928–001

Installing the CNA Image 


On completion of the CNA safe boot, the CNA desktop screen appears. If you are 

not logged on to the CNA, the Workstation Locked message box appears on the 

desktop. 

Logging on to the CNA 

1. On the Contol menu, click Send Ctrl+Alt+Del. The Unlock Workstation dialog 

box appears. 

2. Enter the usercode/password to log on to the CNA (Administrator), and then click 

OK. 

Installing the Image 

1. On the CNA desktop screen, double-click the Install_Primary icon to begin the CNA 

Installer. 

The ClearPath Network Appliance Installer screen appears. 

2. Click Install to continue. 

A message box appears warning you that the installer will reformat the primary 

partition. 

3. Choose Yes. Choosing No returns you to the previous screen. 

A CNA Installation message box appears directing you to insert the CNA Installation 

CD-ROM in the CNA CD-ROM drive. 

Note: You will not see this message if the CD-ROM is already in the drive. 

3827 2928–001 2–9


4. Insert the CNA CD-ROM and click OK. 

The following Windows NT Format disk screen (for drive C) appears: 

5. Do not change any entries. Select the Quick Format check box and click Start. A 

message is displayed warning you that all data on the C disk will be erased. 

6. Click OK to begin formatting the primary partition. A Format Complete dialog box 

appears when the formatting is complete. 

7. Click OK. The Format C:\ screen reappears. 

2–10 3827 2928–001

8. Click Close to return to the installer. 

The following Copying screen appears: 


Setup.exe copies the appropriate source image from the CNA CD-ROM to the 

primary partition. The progress bar proceeds on a file-by-file basis. The process of 

copying the operating system image takes about 5 minutes. 

Note: The Install, Restart, and Cancel buttons on the CNA Installer window are 

hidden so that you cannot accidentally interrupt the loading process. 

If the file transfer is successful, a ClearPath Network Appliance Installer Finish 

screen appears telling you that the Installation is complete. 

9. Remove the floppy disk and CD-ROM from the drives as directed, and click Finish to 

restart the CNA system from the CNA hard disk. The desktop window of the target 

system closes automatically when the CNA reboots. 

10. Wait until the reboot finishes (the LED for the hard disk should stop flashing), and 

then reestablish a NetMeeting connection as described under “Establishing a 

NetMeeting Connection to CNA” using the address 192.168.222.150. 

The Remote Desktop Sharing Password box appears again. 

11. Log on to the CNA again using Administrator for the User and Password, and 

click OK. 

You are now ready to configure the system. 

3827 2928–001 2–11


2–12 3827 2928–001

Section 3 

Configuring the CNA 

This section describes how to 

• Configure a CNA 

• Configure network adapters for IEEE 802.1Q VLANs or Port Aggregation 

Overview of CNA Configuration 

CNA is initially configured in the factory. The operating system image default 

configuration is the following: 

• Private LAN IP address = 192.168.222.150 

• Username/password = Administrator/Administrator 

• Computer name = CNA 

Refer to Table 3-1 for IP addressing information for the CNA devices. 

Do You Need to Configure CNA? 

A configuration tool, CNAcfg.exe, is provided to enable you to configure CNA after 

installing a new image or to change the default values of the CNA private LAN IP 

address, password, and computer name. Unisys support personnel may also use the 

configuration tool to install a new CNA, add additional CNAs to an existing ClearPath 

server, or configure public NIC attributes. Each CNA needs to be configured as 

described in “Configuring CNA” later in this section. 

If you are installing a new image, the CNA Configuration dialog box is displayed 

immediately after you boot. Follow the instructions in “Configuring a CNA” later in this 

section. 

If you are not installing a new image, changing the default values, or adding new CNAs 

to an existing system, you can skip the configuration procedures in this section. Proceed 

to the next section, “Installing Network Services on the CNA.” 

3827 2928–001 3–1


IP Addressing Information for CNA Devices 


Device 

ID 

Table 3-1 provides the IP addressing information for CNA devices. Refer to this table 

when you are configuring a CNA or installing Network Services software on a CNA. 

Note: The MCP public IP addresses in this table are examples only. You must 

configure these addresses in MCP TCP/IP initialization files using your public LAN 

addresses. 

NP 

ID 

Unit 

No. 

Private 

LAN 

IP Address 

CNA1 8001 192.168.222.151 












Table 3–1. IP Addresses 

MCP Private 

LAN 

Address 

MCP Public 

IP Addresses 

192.168.222.121 192.168.237.50 

192.168.237.51 

192.168.237.52 

192.168.237.53 

CNA EVLAN 

IP Address 

MCP EVLAN 

IP Address 

192.168.16.102 192.168.16.101 

192.168.222.122 192.168.237.54… 192.168.16.106 192.168.16.105 

192.168.222.123 192.168.237.58… 192.168.16.110 192.168.16.109 

192.168.222.124 192.168.237.62… 192.168.16.114 192.168.16.113 

192.168.222.125 192.168.237.66… 192.168.16.118 192.168.16.117 

192.168.222.126 192.168.237.70… 192.168.16.122 192.168.16.121 

192.168.222.127 192.168.237.74… 192.168.16.126 192.168.16.125 

192.168.222.128 192.168.237.78… 192.168.16.130 192.168.16.129 

192.168.222.129 192.168.237.82… 192.168.16.134 192.168.16.133 

192.168.222.130 192.168.237.86… 192.168.16.138 192.168.16.137 

192.168.222.131 192.168.237.90… 192.168.16.142 192.168.16.141 

192.168.222.132 192.168.237.94… 192.168.16.146 192.168.16.145 

3–2 3827 2928–001


Device 

ID 

NP 

ID 

Unit 

No. 

Private 

LAN 

IP Address 













Table 3–1. IP Addresses 

MCP Private 

LAN 

Address 

MCP Public 

IP Addresses 


CNA EVLAN 

IP Address 

MCP EVLAN 

IP Address 

192.168.222.133 192.168.237.98… 192.168.16.150 192.168.16.149 

192.168.222.134 192.168.237.102… 192.168.16.154 192.168.16.153 

192.168.222.135 192.168.237.106… 192.168.16.158 192.168.16.157 

192.168.222.136 192.168.237.110… 192.168.16.162 192.168.16.161 

192.168.222.137 192.168.237.114… 192.168.16.166 192.168.16.165 

192.168.222.138 192.168.237.118… 192.168.16.170 192.168.16.169 

192.168.222.139 192.168.237.122… 192.168.16.174 192.168.16.173 

192.168.222.140 192.168.237.126… 192.168.16.178 192.168.16.177 

192.168.222.141 192.168.237.130… 192.168.16.182 192.168.16.181 

192.168.222.142 192.168.237.134… 192.168.16.186 192.168.16.185 

192.168.222.143 192.168.237.138… 192.168.16.190 192.168.16.189 

192.168.222.144 192.168.237.142 

192.168.237.143 

192.168.237.144 

192.168.237.145 

192.168.16.194 192.168.16.193 

3827 2928–001 3–3


Configuring a CNA 

If you have just completed installing the CNA operating system image, the CNA 

configuration tool, CNAcfg.exe, starts automatically. This only occurs after the first time 

you boot the CNA. 

If you are not logged on to the CNA, the Workstation Locked message box appears. Do 

the following: 

1. Select Control on the toolbar. 

2. Click Send Ctrl+Alt+Del and click the mouse button. The Unlock Workstation dialog 

box appears. 

3. Enter the Usercode/Password (Administrator), and then click OK. 

To start the CNA configuration tool, do the following: 

1. Double-click the configuration tool icon, CNAcfg.exe. The CNA Configuration dialog 

box appears. 

If the CNA server device number is not present, a value of “0” appears in the CNA 

Server Device Number box. 

2. Enter the correct value for the CNA server device number (in this example, 4 was 

entered). 

CNAcfg.exe attempts to determine the name of the private LAN network interface 

card. If the name is not correct, select the correct name from the drop-down list and 

click Next. 

3–4 3827 2928–001

The following screen appears: 


If this is a new installation (as we are assuming in this procedure), the CNAcfg4.ini 

file does not exist. 

3. Click Next to continue. Note that you can also enter a path or click Browse. 

• You can browse to the location of the CNAcfg.ini files and read the CNAcfgx.ini 

file to recover your previous settings (x is the CNA device number). 

• If this is an operating system image re-installation on a device you used 

previously, the CNAcfgx.ini file is stored on hard disk (D:\Cnacfg\CNAcfgx). 

3827 2928–001 3–5


4. The next screen that appears is used to either display or enter the private LAN IP 

address. The address range is from 192.168.222.151 through 192.168.222.174. 

• In this example, the device number for the CNA you are installing is 4. The 

private IP address is 192.168.222.154, as shown on the screen. 

Table 3-1 contains a complete list of default values. 

• Click Next to continue. 

Note: If this is a new private LAN IP address, we recommend that you change the 

IP address sticker on the back of the box. IP address stickers are included in the 

CNA “overpack box.” 

3–6 3827 2928–001


5. The next screen is used to fill in the Computer Name of the CNA. The Computer 

Name is listed under the CNA Device ID column in Table 3-1. 

Enter a value (in this example, CNA4) and click Next. 

The following change password screen appears: 

3827 2928–001 3–7


6. Follow the instructions on the screen to enter your new password. Click Next. 

If you are using a CNAcfgx.ini file, the new password will not be filled in from the 

file. To restore your old password manually, read the CNAcfg.ini file and enter the 

password using the previous screen. Otherwise, enter a new password to replace 

the default. 

If you do not type an entry for a new password, the existing password will not be 

changed. The password must be a non-empty string for the Appliance Crash Dump 

facility to operate correctly. 

Notes: 

• This screen is the only tool that should be used to change the password for 

the Administrator. The CNA configuration tool makes changes to the two 

places where the password must be changed. If you change the password 

through Windows User Manager, you will be unable to log on to the CNA. 

The only way to recover the CNA in this case is to reinstall the operating 

system image. 

• The CNA recovery disk contains the password for the CNA, which is 

sensitive data. Keep the disk in a safe place. 

If your CNA system contains Gigabit Ethernet network interface cards (NICs), the 

following screen appears: 

3–8 3827 2928–001


7. If you have network interface cards (NICs) that support Ethernet Jumbo Frames, 

select the desired frame size and click Next. For more information, see “Preparing 

to Use Ethernet Jumbo Frames” later in this section. 

8. The following Date/Time Properties screen appears. Enter the correct date and time 

and click OK. 

3827 2928–001 3–9


9. The following CNA Configuration summary screen is displayed enabling you to go 

back and reenter any values you want to change. 

Note: The CNA Configuration summary screen also requests a location in which to 

save the .ini file, which may be on the CNA boot floppy disk or any other floppy disk. 

10. On the CNA Configuration summary screen, enter a path or browse to the save 

location and Click Next. 

The configuration data obtained from step 4 is written to a text file called 

CNAcfgx.ini (where x is the CNA device number). A second copy is always written to 

the D:\CNACFG\CNAcfgx.ini file on the hard drive. 

You can use this file later to supply the defaults in case you need to replace the disk 

image. 

3–10 3827 2928–001

The following screen is displayed. 


11. Click Finish. If the only data you changed is the administrative password, the 

program exits immediately. Otherwise, the program prompts you to reboot the 

system to activate the new information. 

If you changed the CNA device number, the dialog asks you to install or re-install the 

NNS (Network Services) software. Insert the NNS disk, click Finish, and proceed to 

install Network Services as described in Section 4, “Installing Network Services 

Software on the CNA.” Reboot the system when the Network Services installation 

finishes. 

3827 2928–001 3–11


Configuring Shared Adapter Features 

The following subsections describe general guidelines you should observe when 

preparing to use the following shared adapter options: 

• Port Aggregation 

• Ethernet Jumbo Frames 

• IEEE 802.1Q VLANs 

Ethernet Jumbo Frames are configured on the CNA by using the CNA configuration 

wizard (see “Configuring CNA”). 

See “Configuring IEEE 802.1Q VLANs or Port Aggregation” later in this section for 

procedures to configure 802.1Q VLANs or Port Aggregation. 

Preparing to Use Port Aggregation 

Network Services Shared Adapter software supports port aggregation, an optional 

feature offered on Fast Ethernet and Gigabit Ethernet adapters. Port aggregation 

increases the effective network throughput by distributing Fast Ethernet traffic across 

multiple adapters. System and user programs “see” a single virtual port capable of 

operating at some factor in excess of 100 Mbps. 

Port Aggregation can only be used when CNA is connected to a switch or router which 

supports Port Aggregation and is configured for it. 

Use the Port Aggregation software (as described in the Intel adapter documentation) 

before running Network Services Setup to share the virtual Port Aggregation adapter 

created. Setup will offer this virtual adapter to be selected as a shared adapter. The 

physical adapters assigned to the port aggregation may also appear in the list offered by 

Setup for shared adapter selection and should not be chosen. 

If you have Fast Ethernet or Gigabit Ethernet adapters already configured as shared 

adapters that you intend to use in Port Aggregation, you must first run the Network 

Services Setup program to “un-share” these adapters (that is, disable MCP access). 

Also, if you have configured a Port Aggregation adapter as a shared adapter and you 

intend to remove the port aggregation, you must first run Network Services Setup to unshare 

the Port Aggregation adapter. 

For further information on configuring Port Aggregation, see “Configuring IEEE 802.1Q 

VLANs or Port Aggregation” later in this section. 

3–12 3827 2928–001

Preparing to Use Ethernet Jumbo Frames 


In some applications, Jumbo Frames improve server throughput and reduce the CPU 

cycles used for networking. This improvement is achieved by reducing the number of 

frames an application must process. This is particularly true for applications that use 

large message sizes such as file transfers. 

Jumbo Frames can only be used if the remote system and the connecting network 

equipment (switches, routers) also support Jumbo Frames. Jumbo Frames are not 

supported on Fast Ethernet NICs. 

You can use Jumbo Frames with TCP/IP, Heritage Network Services (BNA), and BNA 

over IP (BIP). In addition to the application message size, the performance benefits vary 

depending on which of these protocols you are using. The performance gains are 

particularly significant with BNA and BIP. With TCP/IP, these gains are less pronounced 

or null (depending on the direction). This is due to TCP/IP Offload, which moves 

processing cycles from the MCP to the Windows environment. 

Jumbo Frames are supported over CNA Gigabit Ethernet connections. Note that you 

must configure Jumbo Frames on both the CNA and the MCP. 

On the CNA, use CNAcfg to select the Jumbo Frames option (see step 7 of “Configuring 

CNA” earlier in this section). 

On the MCP side, set the following attributes to desired values for applicable lines 

(connection groups) and devices (connections): 

• Max Input Message Size (MIMS) 

• Max Output Message Size (MOMS) 

• Max Input Message Size Limit (MIMSL) 

• Max Output Message Size Limit (MOMSL) 

The recommended frame size for Jumbo Frames is 9014, including the MAC header, but 

excluding the Cyclic Redundancy Check (CRC). Configure this value in the NIC driver, 

and translate it to the following MIMS/MOMS/MIMSL/MOMSL values: 

• 9000 for the connection group 

• 9000 or 8996 for TCP/IP and Heritage Network Services/BIP connections, 

respectively 

Communications between a jumbo-capable and a jumbo-incapable end system is 

generally not a problem. A common frame size is negotiated between the systems 

when they establish a dialog. This applies to TCP/IP, Heritage Network Services (BNA), 

and BIP protocols. It is not true for connectionless protocols such as UDP and ICMP, 

since they are datagram-based and do not negotiate a connection. 

If no router is in the path, each system transmits frames sized up to the system MTU 

value. Any frames larger than 1,500 bytes are dropped if they are not supported by the 

receiver. The only potential issue occurs with the ICMP protocol—“pings” that are 

larger than 1,500 bytes will fail. 

A useful technique in mixed networks is to logically segregate jumbo frame traffic from 

standard traffic by using IEEE 802.1Q Virtual LANS (VLANS). 

3827 2928–001 3–13


Preparing to Use IEEE 802.1Q VLANS 

IEEE 802.1Q VLANs add a 4-byte tag to the packet header, identifying the VLAN for that 

packet. If the ClearPath server is a member of only one VLAN on a given adapter port, 

tagging is not necessary on that port. The VLAN is configured at the LAN switch port 

only. No VLAN should be configured on the ClearPath server. 

If the ClearPath server is to be a member of multiple VLANs over the same adapter port, 

then both the LAN switch and the ClearPath server must be configured. The switch 

connected to the ClearPath system must support IEEE 802.1Q tagging. 

• At the switch, tagging should be enabled, and all VLAN ID assignments made at the 

specific port. Follow any other vendor-specific instructions. 

• On the ClearPath server, VLAN IDs are assigned using the Windows Driver utility 

(Intel ProSet II). The VLAN IDs assigned to the NIC should match those assigned to 

the switch ports to which the NIC is connected. 

• For each VLAN defined, Windows creates a new “adapter” and assigns it a new 

adapter number. 

• At the ClearPath operator interface, a connection group must be defined for each 

VLAN. 

The following are additional rules and notes for configuring VLANs on a ClearPath server: 

• Assign the VLANs to the switch ports first. 

• Before assigning VLANs to the NIC card, run NNS setup to unshare the physical 

adapter. 

• DHCP will be enabled when VLAN is assigned; assign a fixed IP address for each 

VLAN adapter as required (this address is not used once the adapter is assigned to 

the MCP for its use). 

• Save your configuration settings as described in “Saving Your Settings” later in this 

section. 

• Each VLAN added will appear in the list of adapters that NNS can share. 

• Rerun NNS setup to share the virtual adapters. 

3–14 3827 2928–001

Configuring IEEE 802.1Q VLANs or Port 

Aggregation 


Configure IEEE 802.1Q VLANs and Adapter Teaming (Intel’s feature that includes Port 

Aggregation) through the Intel PROSet II utility in Control Panel. 

Adapter Fault Tolerance (AFT) teams are used for resiliency at the NIC level. Fast 

EtherChannel/Link Aggregation is used to provide additional bandwidth beyond that 

available with a single adapter. Fast EtherChannel/Link Aggregation can be used to 

provide resiliency at the NIC level as well, when used with network switches that 

support this function. 

Creating a Team 

To configure adapters as part of a team 

1. Click Action. 

2. Select Add to Team. 

3. Click Create New Team. 

3827 2928–001 3–15


4. Follow the Teaming Wizard through the selection of adapters to add to the team. 

Note that the Adapter labels in the above screen show Line # n, where n is a number 

from 1 to 4. The Line # n description indicates which NIC in the CNA device is being 

selected. The Line # n description matches the LINE 1 2 3 4 label under the PCI 

slots on the back of your CNA device. Do not include the adapter labeled “CNA 

Management Adapter do NOT change settings” in any adapter teams. 

3–16 3827 2928–001

Configuring IEEE 802.1Q VLANs 

To configure IEEE 802.1Q VLANs 

1. Click Action and select Add VLAN. 

2. Enter the VLAN number and a name for that VLAN. 


VLANs can be assigned on individual NICs and on adapter teams. It is extremely 

rare that you would need to configure 802.1Q VLANS on the adapter labeled “CNA 

Management Adapter do NOT change settings.” Unisys recommends that you do 

not configure 802.1Q VLANs on this adapter. 

3827 2928–001 3–17


Saving Your Settings 

Your settings are saved in PROSet when you click OK. Unisys recommends that you 

save your settings as follows: 

1. Click Tools. 

2. Click Save/Restore Configuration. 

3. Click OK. The PROSet Save/Restore box appears. 

3–18 3827 2928–001


4. Click Save and point the utility to a floppy disk that you will use to store this 

configuration information. This enables you to store your adapter configuration on 

removable media so that it can be restored in the future if you reinstall the CNA 

image or if you need to replace the CNA device. 

When you click OK on the main PROSet II screen, the Network Control Panel is 

initiated to recalculate the networking bindings for your devices. Depending on the 

features you selected, you may be prompted to configure new IP addresses for 

those devices. 

3827 2928–001 3–19


5. Enter an IP address as shown in the following screen, even though you will not be 

using this adapter team for Windows TCP/IP access. The address must be entered 

for the adapter to be created properly. Network Services Setup breaks the binding 

between Windows TCP/IP and the new adapter when you assign the adapter for the 

MCP access. You can reboot when prompted to do so. 

3–20 3827 2928–001

Restoring Your Settings 


To restore your settings in PROSet, use Control Panel to start the PROSet II applet: 

1. Click Tools. 

2. Click Save/Restore Configuration. 

3. Click Restore. 

4. Enter the path to your floppy disk containing the configuration of this device, and 

select the configuration file. 

5. Once the configuration is restored, click OK on the main PROSet II screen. 

The Network Control Panel is initiated to recalculate the networking bindings for your 

devices. You may be prompted to configure new IP addresses for those devices. 

Enter an IP address, even though you will not be using this adapter team for 

Windows TCP/IP access. The address must be entered for the adapter to be created 

properly. Network Services Setup breaks the binding between Windows TCP/IP and 

the new adapter when you assign the adapter for the MCP access. You can reboot 

when prompted to do so. 

3827 2928–001 3–21


Assigning the Advanced Features Adapter to the MCP 

Proceed to Section 4, “Installing Network Services Software on the CNA.” If you have 

configured advanced networking features on the CNA device, you must select the 

adapters for MCP use manually. 

Note that all of the adapters in the CNA device are listed on the Select Adapter Cards 

for MCP Server Access screen. If you have configured an adapter in a team or if you 

have configured 802.1Q VLANs on an adapter, do not select the base adapter for MCP 

Server Access. Selecting both the base adapter and the Intel Advanced Network 

Services adapter for MCP Server Access may lead to unexpected results once the 

system starts networking. 

3–22 3827 2928–001

Section 4 

Installing Network Services Software 

on the CNA 

This section provides the information required to install Network Services software on 

the ClearPath Network Appliance (CNA). 

If this is a new system installation and the CNAs were installed at the factory, Network 

Services should also have been installed at the factory. Proceed to “Bringing a CNA into 

Service” at the end of this section. 

If you are installing a new CNA on an existing MCP server, or adding additional CNAs to 

an existing server, you must install the Network Services software from the Network 

Services CD-ROM. 

You can upgrade Network Services software on a CNA from a remote ClearPath system 

by using the REMOTEINSTALL command. Note that the ClearPath system must be 

connected to the CNA device through Network Services. For details on using the 

REMOTEINSTALL command, see the Network Services Implementation Guide. 

Preparing to Install Network Services 

You can install Network Services on the CNA the same way as on other platforms. You 

can do either of the following: 

• Place the Network Services CD-ROM media in the CD-ROM drive and run SETUP by 

clicking Start and Run. 

• Map a network drive to the INSTALLS share on the MCP server (this assumes that 

Network Services is installed on the MCP server). 

You must execute Network Services Setup through a NetMeeting session. (See 

“Establishing a NetMeeting Connection to CNA” in Section 2 for instructions on using 

NetMeeting.) 

The Network Services Installation procedure requests information about the Network 

Services configuration. Table 3-1 lists the preconfigured values for each component that 

you need for the installation. 

3827 2928–001 4–1

Installing Network Services Software on the CNA 

Network Services Installation Procedure 

If this is an upgrade or reconfiguration reinstall, perform the following steps to install 

Network Services on the CNA. If this is a “first time” install following a reload of the 

operating system, steps 1 through 5 should have already been done. 

1. Log on to a Windows server as Administrator. 

2. Run NetMeeting to attach to the CNA. You must select Require Security For This 

Call if you did not previously default Outgoing Calls to be secure as explained in 

“Establishing a NetMeeting Connection to CNA” in Section 2. 

The following Remote Desktop Sharing Password screen appears. 

3. Enter Administrator (or whichever values you have established if this is not an 

initial installation) in the User and the Password boxes and click OK. 

4–2 3827 2928–001


When you enter the user and password, you are connected to the CNA and the 

Workstation Locked message screen may appear on the desktop: 

Caution 

Once the connection is established, the message “Press Ctrl+Alt+Del to 

unlock this workstation” is displayed. Do not press Ctrl-Alt-Del since this 

key sequence is interpreted by your local PC. Continue with the following 

instructions instead. 

4. From the Control Menu, click Send Ctrl+Alt+Del. 

The Unlock Workstation screen appears. 

5. Enter Administrator as the password (or the password value you have established 

if this is not an initial installation) and press Enter or click OK. 

The CNA desktop screen appears (not shown here). 

3827 2928–001 4–3


6. Insert the release media Network Services Installation CD-ROM in the CNA CD- 

ROM drive. Click Start and Run to start the Setup.exe program. 

The Network Services splash screen appears with the Setup startup meter running 

as the InstallShield Wizard is initialized. 

7. The Welcome screen (not shown) appears, showing the version of Network Services 

you are installing. Click Next. 

8. The View Readme File screen appears (not shown), giving you the option of viewing 

the Readme text file from the Network Services CD-ROM. This file contains any 

last-minute changes and information about Network Services that did not make it 

into the printed documentation. Always review this information for each release 

level. Click Next. 

The Choose Destination Location screen appears. 

4–4 3827 2928–001

9. Accept the default destination folder and click Next. 


The Start Copying Files screen appears showing the settings that the setup utility 

has determined or received from the user. Note that the platform type is CNA. 

3827 2928–001 4–5


10. Click Next. 

The Setup program copies the Network Services software to the CNA hard disk and 

then installs the necessary service and driver files. 

The Configuration of Shared Adapter Cards screen appears. 

Your entry on this screen depends on whether you have configured advanced 

networking features such as IEEE 802.1Q VLANs or Adapter Teaming (Port 

Aggregation). 

11. Do one of the following: 

• If you have not configured these features, accept the default selection of Keep 

the current selection of Shared Adapters and click Next. Setup uses the default 

adapter selections for the CNA and displays them in the Review Shared Adapter 

Card Selections screen. Skip to step 15. 

• If you have configured advanced networking features as described in 

“Configuring IEEE 802.1Q VLANs or Port Aggregation” in Section 3, click Yes to 

Proceed to update selection of Shared Adapters and click Next. The Select 

Adapter Cards for MCP Server Access screen is displayed: 

4–6 3827 2928–001

12. Select each check box and click Properties. 

The Adapter Properties screen appears. 


3827 2928–001 4–7


13. Enter the CNS Line ID for each adapter and click OK. Note that if you do not accept 

the defaults in step 11, you will have to determine which adapter goes with which 

line. 

The Select Adapter Cards for MCP Server Access screen appears again. 

14. Once you have assigned the CNS Line ID for all three adapters, click Next. 

4–8 3827 2928–001


When you have selected the adapter cards that will be used by the MCP, the 

following screen displays a summary of your shared adapter choices and allows you 

to go back to make appropriate changes. You should see all the Intel Pro adapters 

listed in the Exclusive use by MCP Server for network connections section. 

Note: To ensure the security of the CNA, adapters on the public LAN cannot be 

shared between the MCP and Windows in the CNA. The LAN on the motherboard 

attached to the private LAN will be shared between the MCP and Windows on the 

CNA for use by the MCP Call Home facility. This is selected automatically. 


3827 2928–001 4–9


The Specify Windows Server Environment screen appears. 

The Server box is prefilled with the CNA device server number that you provided 

earlier, unless you have changed it. The value provided in this box is used to 

determine the values for the NP ID unit number and for the VLAN IP address of the 

CNA. 


4–10 3827 2928–001

The Network Services Properties screen appears. 


The NP Unit Number box is prefilled with the value from Table 3-1. 

17. This value is the NP unit number that Network Services reports for the CNA. It does 

not have to match the channel number, but the convention for CNA devices is to 

make the channel/port number match the NP unit number. 

Click Next to accept the value or enter another value in the box and then click Next. 

3827 2928–001 4–11


The Choose Configuration Options screen appears. 

18. In almost all cases, accept the default values (selected). 

Click Next. 

Note: If you want to change the VLAN IP addresses for the MCP and/or the CNA, 

clear the Assume default IP Addresses for Network Services check box and click 

Next. 

4–12 3827 2928–001

The MCP Host Name screen appears. 

19. Fill in the name of your MCP host and click Next. 


Note: This is the only field that does not contain a default value during the initial 

installation of Network Services on a CNA. The value shown here is used to force 

the CNA to use the VLAN path to communicate with the MCP. 

3827 2928–001 4–13


The Review Configuration Option Selections screen appears. 

20. Review all your configuration options. If OK, click Next. 

4–14 3827 2928–001


The Setup program starts the Network applet (to automatically complete the 

configuration of Network Services), waits for it to terminate, and then displays the 

Setup Complete screen. 

21. Remove the installation CD at this time. Select Yes, I want to restart my computer 

now and click Finish. 

Your NetMeeting session will terminate. Reestablish NetMeeting using the IP 

address for your CNA device. It will take about three minutes to reestablish the 

session. 

Proceed to Section 5, “Installing ODT and IOP Files.” 

3827 2928–001 4–15


4–16 3827 2928–001

Section 5 

Installing ODT and NT-IOP Software 

This section explains how to install the following files from the I/O Firmware CD-ROM 

(referred to as the IOCD) to the ClearPath Network Appliance (CNA). 

• Operator display terminal (ODT) software – the ODT software that enables a PC 

connected to the CNA private LAN to emulate an MCP ODT 

• NT-IOP software – the software files installed on the CNA that provide ODT 

connectivity for the ClearPath system 

If you are installing a CNA on an existing ClearPath system, you must install the Network 

Services software as described in Section 4 of this guide before installing the ODT 

software. You should install the contents of the IOCD on your CNA devices immediately 

after installing the Network Services software. 

If this is a new system installation and the CNA devices were installed at the factory, the 

IOCD software should also have been installed at the factory. 

Installing ODT and IOP Files 

1. Check the status of the CNA and the ODT by entering the following: 

OL PORT 

2. Reserve the CNA by entering the following: 

UR PORT 

Accept any Waiting Entry messages associated with the device. 

3. If the NT-IOP is defined in the partition profile of the MCP, save it by entering the 

following: 

SV IOP 

Accept any Waiting Entry messages associated with the device. 

4. Establish a NetMeeting session to the CNA unit. Refer to “Establishing a 

NetMeeting Connection to CNA” in Section 2. 

5. If you are updating NT-IOP software, reboot the CNA unit; otherwise, go to step 7. 

6. If you rebooted in step 5, reestablish a NetMeeting session to the CNA unit. 

7. Insert the IOCD in the CNA. 

3827 2928–001 5–1


8. Run Setup.exe on the CD-ROM by doing one of the following: 

• From Windows Explorer, navigate to the Installer folder and double-click 

Setup.exe. 

• On the Run screen, enter F:\Installer\Setup.exe as shown on the following 

screen and click OK (assuming F: is the drive letter for your CD drive). 

9. When the Welcome screen appears, click Next. 

10. The Installation Options screen is displayed. On this screen, the NT-IOP /ODT and 

the FC-IOP firmware boxes are both checked by default if the CNA device is number 

1, 2, 3, or 4. The FC-IOP firmware box is checked by default for all other CNA 

devices. If the ODT installation is required for CNA devices of any other number, the 

NT-IOP/ODT box must be checked manually. On this screen: 

• If you are installing code on CNA1, CNA2, CNA3, and CNA4, select both 

boxes (the NT-IOP and ODT software and the FC-IOP firmware boxes). 

• If ODT functionality is required for other CNAs, select the NT-IOP and ODT 

software box only. 

11. Click Next. The Installer begins to copy files to the CNA. If there is a version level 

mismatch between the Network Services code and the ODT software, an error 

message appears. 

12. When the installation is complete, click Finish on the Setup Complete screen. 

5–2 3827 2928–001

Installing Web Enabler 


You must install and configure Web Enabler on the PC that is being used as the ODT for 

the MCP. The PC being used as the ODT must have a LAN card installed and be 

connected to the private LAN in the CNA. 

Perform the following steps to install Web Enabler: 

1. Install the IOCD in the PC to be used for ODT capabilities, and navigate to the 

:\Installer\Web Enabler folder. Select the appropriate Web Enabler 

version to install: 

• If you are running MCP 8.0, double-click Install80.exe 

There will be several more screen prompts. Read and follow the prompts until the 

Choose Java Virtual Machine screen appears. 

2. From the Choose Java Virtual Machine screen, select Install Sun Java VM specifically 

for this Application and click Next. 

Note: Different Java VMs support different print drivers. 

3. From the Choose Install Set screen, select Full Install and click Install. 

Web Enabler will install on the PC; wait until you see the Install Complete screen. 

4. From the Install Complete screen, click Done. 

3827 2928–001 5–3


Configuring a CNA for ODT Mode 

Perform the following steps to configure Web Enabler : 

1. From the Desktop, bring up Web Enabler by doing the following: 

a. Click Start. 

b. Choose Programs. 

c. Choose Web Enabler for ClearPath MCP. 

d. Click Web Enabler. 

2. On the Web Enabler for ClearPath MCP screen: 

a. Select File. 

b. From the File menu, select Properties. 

c. From the Properties screen, select the Advanced tab. 

3. From the Advanced tab, perform the following steps to enable the ODT feature: 

a. Verify that the following are selected: 

• Attempt to connect at startup 

• Disconnect on log off 

• Attempt to Reconnect when Disconnected 

b. Scroll down to Server Name and enter the Private LAN IP address of the CNA 

that is going to provide the ODT feature. 

For example, Server Name: 192.168.222.151 if CNA1 is being configured 

to provide ODT capabilities. 

Note: The IP addresses can be found in Table 3-1. 

c. Scroll down to Socket Number and verify that its default value equals 3001. 

• Socket numbers are assigned by adding the Single Line Control (SC) Logical 

Unit Number (LUN) to 3001. For example, if the SC LUN number for an ODT 

is zero (0), then its socket number would be 3001. 

Note: This numbering convention continues for all SCs defined. 

d. Scroll down to the ODT Section and ensure that Enable ODT Mode is selected. 

If not, click the box to enable it. 

e. Click Apply to save the settings or click OK to save and close the Properties 

screen. 

After clicking OK, the MCP screen appears if the following conditions exist: 

• NT-IOP is configured. 

• A partition profile that has the ODT is selected. 

• The MCP is running. 

5–4 3827 2928–001

Configuring a Redundant ODT Connection 


The following procedures describe how to configure a redundant ODT connection to a 

second CNA for two types of configurations, redundant configurations with path 

preservation and redundant configurations without path preservation. For further details 

on configuring paths to redundant ODTs, see the Configuration Editor help. 

Note: By convention, we recommend designating the CNA with the lower NT-IOP 

number as the redundant connection. 

1. From the Desktop, bring up Web Enabler by doing the following: 

a. Click Start. 

b. Choose Programs. 

c. Choose Web Enabler for ClearPath MCP. 

d. Click Web Enabler. 

2. On the Web Enabler for ClearPath MCP screen 

a. Select File. 

b. From the File menu, select Properties. 

c. From the Properties screen, select the Advanced tab. 

3. From the Advanced tab, select Use redundant connection 

When selected, the display is automatically expanded and requires inputs in the 

Server Name and Socket Number fields. You fill in these fields differently, 

depending on if you want to preserve the path to the redundant ODT or not, based 

on how you configured redundancy in the partition profile with the Configuration 

Editor. 

Do one of the following: 

Path Preservation 

If you have a redundant configuration with path preservation, perform the following 

steps. Note that the primary and backup socket numbers you specify in Web 

Enabler should be identical and the primary and backup IP addresses should be 

different. 

a. In the Server Name field, enter the server name of the CNA device or the IP 

address of the CNA associated with the lower NT-IOP number. 

b. In the Socket Number field, enter the socket number of the (system console 

or ODT) that will be used for redundancy. This should be the same number 

for both ODTs. 

3827 2928–001 5–5


No Path Preservation 

If you have a redundant configuration without path preservation, note the following 

before configuring a redundant ODT: 

• The primary and backup IP addresses should be different. 

• The primary and backup socket numbers should be different. 

• With this configuration, only one ODT can be active at a time. 

• If there is a failure, the operator should manually select the redundant ODT 

by specifying Connect Number 2 from the Advanced tab. 

• Do not specify Attempt to Reconnect When Disconnected in the Connection 

section. 

To configure a redundant ODT, perform the following steps: 

a. In the Server Name field, enter the server name of the CNA device or the IP 

address associated with the lower NT-IOP number. 

b. In the Socket Number field, enter the socket number of the system console 

or ODT that will be used for redundancy. This number should be different 

for each ODT. 

4. Click Apply to save the settings or click OK to save and close the Properties screen. 

5–6 3827 2928–001

Bringing a CNA Into Service 

Perform the following steps for each CNA in the configuration. 


1. Use the UR – PORT command to make the port usable for the NP. 

Note: Odd CNA numbers are for first/single MCP partition in ClearPath systems. 

Even CNA numbers are for a second MCP partition. 

8001 for the first CNA, 

8002 for the second CNA (if applicable), 

8003 for the third CNA (if applicable),... 

8024 for the 24th CNA (if applicable) 

2. After completing network configuration procedures, initialize the network provider on 

the host. 

3827 2928–001 5–7


5–8 3827 2928–001

Section 6 

CNA Operations 

In normal operation, you can manage a CNA from your ClearPath system using ODT 

commands. You do not need to access a CNA from NetMeeting unless you are 

installing and configuring software or viewing the Event Log when troubleshooting the 


This section describes the ODT commands you use during normal CNA operation and 

also provides precautions you should observe when using NetMeeting. 

ODT Commands 

The following commands are used during CNA operation: 

OL PORT 

Displays the status of the port in question. 

UR PORT 

UR - PORT 

The Unit Reserved command reserves and unreserves a channel; is 

the channel number to be enabled or disabled. 

NW NP or 

NW NP 

Displays either summary information for all network processors (NPs) for the local 

host or detailed information about a specific NP. 

Note: This command should be used in place of the PER NP command. PER NP 

does not report on CNA-attached devices. 

NW DUMP NP 

Causes the NNS probes and the Windows System and Application Event logs to be 

written to the rotating disk on the CNA device. This command does not reinitialize 

the NP. 

3827 2928–001 6–1


NW CONN 

Determines the status of a connection group in the CNA or a component connection 

of a connection group. 

NW TCPIP PING 

Verifies that communication is available between two hosts. 

NW TCPIP PING from 

Verifies that communication is available. You specify the source of the PING 

command as well as the destination. 

RY IOP 

Brings the NT-IOP online. 

SV IOP 

Makes units inaccessible to the system. Saved units can be returned to the system 

with the RY (Ready) command. 

Bringing a CNA Up 

To bring a CNA up (boot the device) 

1. Push the power switch on the front of the CNA and release. The Power LED should 

light after 1 to 2 minutes. 

2. Bring the CNA into service by entering the following: 

UR- PORT (unreserves the channel) 

Normally, it is unnecessary to reset the CNA. The CNA has a watchdog timer that 

automatically reboots the system if there is a software hang. If the CNA is resetting, this 

is indicated by activity of the fixed disk drive status LED. 

If a CNA seems to be non-operational, refer to Section 7, “Troubleshooting the CNA.” 

Boot completion can be determined by pinging the private LAN IP address. Check that 

the unit is ready and that you can ping the EVLAN (refer to “EVLAN Ping Procedure” in 

Section 7). 

If you are unable to ping the EVLAN, reset the CNA. To reset the CNA, check that the 

fixed disk drive status LED is off, and then press the Reset switch on the front of the 


6–2 3827 2928–001

Powering a CNA Down 

To power down a CNA, do the following: 


1. Open a NetMeeting session to the CNA as described in Section 2, “Establishing a 

NetMeeting Connection to CNA.” 

2. From the Desktop, click Start and then Shutdown. 

3. When you see the CD-ROM Activity LED start to flash, press the power button on 

the front of the CNA (this prevents the CNA from restarting automatically). Note that 

the Power button has a 3 second delay. Press and release the button, then wait. 

We do not recommend powering the CNA directly with the Power button without first 

shutting the CNA down through Windows. However, if you cannot perform steps 1 and 

2, verify that the Fixed Disk Drive Status LED is off for at least 10 seconds, then press 

the Power button. 

Resetting a CNA 

To reset a CNA, do the following: 

1. Open a NetMeeting session to the CNA as described in “Establishing a Connection 

to CNA” in Section 2 of this guide. 

2. From the Desktop, click Start and then ShutDown. CNA will automatically reset and 

then restart. 

If you are unable to open a NetMeeting session to CNA: 

1. Verify that the fixed disk drive status LED is off for at least 10 seconds. 

2. Press the Reset button on the front panel. 

Precautions When Configuring and Using CNA 

Except for actions described in this document, do not use NetMeeting to configure the 

operating system, its peripherals, or its applications. If you change the system 

configuration, you may experience performance or security problems. An incorrect 

configuration could make the CNA inoperable and require you to reinstall the CNA image. 

Do not try to install software on the CNA other than the software described in this guide. 

CNA is an appliance that is designed to run a single application. 

Note that the CNA image is a minimal version of Windows NT. Windows help files and 

many executables have been removed from CNA, and many Start button commands are 

inoperable. 

3827 2928–001 6–3


6–4 3827 2928–001

Section 7 

Troubleshooting the CNA 

This section describes the ClearPath Network Appliance (CNA) troubleshooting 

procedures. When using this section, you may want to refer to the illustrations of the 

front and back of the CNA device in Section 1 of this guide. 

As part of the troubleshooting sequence of procedures, this section contains separate 

procedures to 

• Ping a private LAN 

• Ping an EVLAN 

• Ping a public LAN 

• Access the CNA Event Log 

• Establish a NetMeeting connection to the CNA 

• Perform a CNA safe boot 

• Retrieve log and dump files 

3827 2928–001 7–1


CNA Debug Flow Chart 

Use the following debug checklist procedure, illustrated in Figure 7-1, to troubleshoot 

problems with the CNA. Each decision point in the Debug Flowchart provides you with a 

specific area of the CNA to check; if that area is working correctly, the flowchart 

progresses to subsequent areas to check. As you reach a decision point, refer to the 

Debug Checklist Procedure in the next subsection for a description of what is to be 

tested and the procedures to test it. 

Note that the minimum field-replaceable unit (FRU) for the CNA is the entire CNA. There 

are no replaceable components within the CNA. 

Start 

Power? 

Yes 

LAN LED 

Yes 

Private LAN 

Ping 

NetMeeting 

to CNA 

Response 

Event Log OK 

EVLAN Ping 


Ping 

Done 

View CNA desktop 

All Services OK 

Response 

Response 

None Debug 

Checklist 

Never Lights Debug 

Checklist 

No Response 

Debug Checklist, 

then CNA_Safe Boot 

Reinstall Image 

No Response Debug 

Checklist 

Errors Reported 

Debug 

Checklist 


Checklist 


Checklist 

Figure 7–1. CNA Debug Flowchart 

7–2 3827 2928–001 

021

CNA Debug Checklist Procedure 


1. Look at the private LAN activity LED (Figure 1-2). This LED should blink whenever 

there is traffic on the private maintenance LAN. If this LED is not blinking, do the 

following: 

• Make sure that the maintenance hub is powered on. 

• Make sure that you are pinging the correct private LAN IP address. Refer to the 

following private LAN ping step for the correct IP address. 

2. Issue a private LAN ping following the instructions in the “Private LAN Ping 

Procedure” later in this section. 

3. Using the private LAN IP address, try to establish a NetMeeting connection to the 

CNA. Follow the instructions in Section 2 under “Establishing a NetMeeting 

Connection to CNA.” If the NetMeeting connection attempt succeeds, go to step 4 

of this procedure. If it fails, go to step 9. 

4. Examine the Event Log next for error information and warnings associated with CNA 

problems. See “Event Log Procedure” later in this section. 

If the entries in the event log seem valid but nothing obvious is displayed or the 

description is inadequate, dump the CNA. Use an MCP NW command similar to the 

following example: 

NW DUMP NP 8001 

Follow the instructions in the subsection titled “Initiating a Dump” in Section 6 of 

the Network Services Implementation Guide (4198 6670) to retrieve the dump 

information. 

5. Test for active communications between the MCP and the CNA by issuing an 

EVLAN ping from the MCP to the CNA. Follow the instructions in the “EVLAN Ping 

Procedure” included later in this section. If the ping fails, go to step 7 of this 

procedure. 

6. If communication is active between the MCP and the CNA, determine whether 

external communication is working by issuing a public LAN ping. Follow the 

instructions in the “Public LAN Ping Procedure” later in this section. 

The public LAN ping is a variant of the PING command that enables you to specify 

the source of the PING command as well as the destination. This test verifies that 

Network Services is configured correctly and that the Network Interfaces are 

operational and visible to the host. 

If all pings succeed, communication with your CNA is working properly. If the pings 

fail, see step 7 of this procedure. 

3827 2928–001 7–3


7. If the EVLAN ping or the public LAN ping fails, cycle the CNA to determine if 

rebooting fully recovers the CNA and Network Services. Use the following 

procedure: 

a. Reserve the host interface by issuing the following UR PORT command: 

UR PORT 

b. Restart/reset the CNA. NetMeeting to the CNA, then Start, Shutdown, Restart. 

c. Wait about 5 minutes for the CNA to come back online. You can do a private 

LAN ping to validate that the CNA has booted. 

8. If the procedure in step 7 does not work, follow the procedure “Performing a CNA 

Safe Boot” later in this section to reboot from the hard disk rather than the flash 

disk. 

9. Check the Event Log for errors. See “Event Log Procedure” later in this section. 

10. Reinstall the CNA operating system image. Follow the instructions given in Section 

2 in the subsection titled “Installing the CNA Operating System Image.” 

11. Check the Event Log again for errors. (See the “Event Log Procedure“ later in this 

section.) If this looks OK, continue with the following steps. 

12. Reconfigure the CNA following the instructions given in the subsection “Configuring 

CNA” in Section 3. 

13. Reload the Network Services software following the instructions given in Section 4 

“Installing Network Services Software on the CNA.” 

If you cannot complete the preceding steps, see your Unisys customer service 

representative (CSR), as you may need to replace your CNA. 

7–4 3827 2928–001

Private LAN Ping Procedure 

Perform the following steps to ping the private LAN: 


1. Open a Command prompt from the Windows server or Service Processor. 

2. Enter the command 

PING 192.168.222.1xx 

where x is 50 + the device ID of the CNA you are pinging. A successful ping should 

return the following: 

Reply from 192.168.222.1xx 

3. If the ping fails, check the following: 

a. Make sure you are pinging the correct IP address for the particular CNA by 

checking the CNAcfgX.ini file or asking your administrator. 

b. Make sure that the Windows server IP address is in the same subnet as the 

CNA. If not, change the IP address of the server or move to a different server. 

c. If the results of substeps a and b are OK, you may have a software failure. 

Follow the procedure “Performing a CNA Safe Boot” procedure later in this 

section. 

EVLAN Ping Procedure 

Perform the following steps to ping an EVLAN: 

1. From the MCP ODT, issue a Ping command similar to the following example: 

NW TCPIP PING 192.168.16.102 

Note: The IP address of the device you are trying to reach must match the 

CNA EVLAN IP address. Refer to Table 3-1 for default values. 

The following screen shows the results of a successful EVLAN Ping command: 

3827 2928–001 7–5


2. If the EVLAN ping is unsuccessful, issue a networking command similar to the 

following command to determine if the network processor is available: 

NW NP 8001 

3. If the response to this command is “NOT AVAILABLE” or “UNKNOWN NP,” check 

whether the port is reserved by issuing the following OL PORT command: 

OL PORT 

4. If the port is reserved, issue the following UR– PORT command and then try the ping 

again. 

UR- 

If this command fails, call Unisys support. 

If the response to the UR command is “INVALID UNIT NUMBER,” contact your 

Unisys customer service representative to modify the PCD. 

5. If the NW NP command returned a response “available,” issue the following 

command to determine if the connection group and the component connection are 

open: 

NW CONN ... 

If they are not open, update your host init files. 

7–6 3827 2928–001

Public LAN Ping Procedure 


Perform the following steps from the MCP ODT to complete a public LAN ping 

procedure: 

1. For each line, issue the following PING command: 

NW TCPIP PING FROM 

where is the IP address of a public LAN device and 

is the IP address of a line on the CNA device. 

The following screen shows the results of a successful public LAN ping. In the 

system used for this test, 192.62.181.103 is the IP address of line 3 of the CNA and 

192.62.181.250 is the IP address of an external device on the public LAN. 

2. If this ping operation fails, do the following: 

a. Make sure that the public LAN cable is attached and that the LINK LED for that 

line is on. 

b. Ping the gateway IP address. 

3. If you cannot ping the gateway, contact Unisys support. 

3827 2928–001 7–7


Event Log Procedure 

Perform the following steps to access the CNA Event Log: 

1. Establish a NetMeeting session to the CNA under test. (Follow the instructions in 

Section 2 of this document under “Establishing a NetMeeting Connection to CNA.”) 

2. Click the Start button on the toolbar. 

3. Point to Programs, then to Administrative Tools (Common), then click Event Viewer. 

4. Click and examine the Event Viewer Application Log and the Event Viewer System 

Log. These logs display entries that you can check for error information. 

5. Point to the log entry that you want to look at and select it. Focus on the Yellow 

Warning indicators that contain warning information, and the Red lights that contain 

error information. 

6. Double-click to display the details of the Event Log entry you selected. 

7–8 3827 2928–001

Troubleshooting the NetMeeting Procedure 


Use the following procedure if you are having trouble establishing a NetMeeting 

connection to the CNA: 

1. Cycle (terminate and restart) NetMeeting. 

If the attempt to establish a NetMeeting connection fails during the CNA Safe Boot 

procedure, call your Unisys customer service representative. 

If the attempt fails during the normal operation, go to the procedure “Performing a 

CNA Safe Boot.” 

2. If NetMeeting displays the error “NetMeeting was unable to place a secure call…,” 

the CNA may still be in the process of booting. Wait 5 minutes and try again. 

Either reinstall NetMeeting or install NetMeeting 3.01 Service Pack 1. 

3. If NetMeeting displays the Windows NT logon screen but you cannot log on to the 

CNA, make sure that the Administrator password for the CNA is correct. If it is not, 

see your system administrator for the correct password. The password is in the 

CNAcfgx.ini file if you saved it to a floppy disk when you installed the CNA. 

If you cannot find or determine the password, you will have to reload the operating 

system image. Refer to the instructions in Section 2 in the subsection titled 

“Installing the CNA Operating System Image.” 

Note: If you enter an invalid password four consecutive times, the following error 

message appears on the NetMeeting window: 

The Other person didn’t allow you to join the meeting. 

All additional attempts to “place a call” to the CNA device will result in the same 

error message, regardless of the terminal from which the call attempt is made. This 

is a NetMeeting security feature to prevent unauthorized access. When this error 

message is displayed, you must reboot the CNA device to retry the NetMeeting 

logon. This will give you four more chances to enter the correct password. 

3827 2928–001 7–9


Performing a CNA Safe Boot 

The CNA Safe Boot enables you to verify the operation of the LAN interfaces as well as 

the RAID hard disks. It is also the first step you perform when installing the CNA 

operating system image. Use the following procedure to perform a CNA Safe Boot: 

1. Insert the CNA_Safe Boot floppy disk. The boot disk contains a Boot.ini file that 

re-directs the boot process to the CNA_Safe directory on the hard disk. 

2. Power on or restart the CNA. 

The system boots from the CNA_Safe Image on the hard drive. There is no visual 

indication of boot completion—wait for all drive activity to finish (about 3 to 5 

minutes). 

3. If the boot is successful, start NetMeeting to establish the connection and log on to 

the CNA (see “Establishing a NetMeeting Connection to CNA” in Section 2 of this 

guide). 

Your Windows system must be attached to the private LAN and configured to 

connect to the reserved IP address (192.168.222.150) specified on the label of the 

boot floppy. This is always the address of the CNA when you boot from the hard 

disk. This means that you can only have one device booted from the CNA_Safe 

Image at a time. Otherwise, you would have duplicate IP addresses on the private 

LAN if you booted more than one CNA from the CNA_Safe directory on the hard 

disk. Under normal circumstances, you should not change this address. 

Note: Sometimes NetMeeting will not establish a session with the CNA even 

though a ping of CNA is successful. You can usually resolve this by closing the 

NetMeeting window and restarting NetMeeting. 

4. When the Remote Desktop Sharing Password dialog box appears, enter 

Administrator in the User and Password boxes and click OK to log on to the CNA. 

7–10 3827 2928–001

Log and Dump File Retrieval 


CNA, and NNS have log and dump files that are created when they fail. These files are 

retrieved and submitted as part of a trouble report. The following files are created: 

• CNA Dump file. For example: 19Jun01_1719.DMP. This file is a standard Windows 

NT dump file. 

• NNS Dump File. For example: NNSDMP00.TXT. 

• Event Log Files. For example: CNPSYS1.EVT is a Windows System Event Log and 

CNPAPP1.EVT is a Windows Application Log. 

There are four different ways to retrieve these files: 

• File transfer (FTP) from the MCP host 

• A DOS FTP entered from a Windows server 

• A browser FTP entered from a Windows server 

• From a NetMeeting session 

Each method is described below. 

File Transfer (FTP) from the MCP Host 

The FTP is initiated from the MCP host. This is a file transfer from CNA to the MCP host 

across EVLAN (FC-SL). 

From the MCP host, the following sequence establishes the FTP session: 

1. Make sure that the EVLAN TCP/IP connection is opened. (The connection may be 

AUTOINIT=FALSE or the port may be reserved.) 

2. From a CANDE session on the MCP host (using the ODT or a terminal), do the 

following: 

a. Type U FTP 

b. Type OPEN 

See Table 3-1 to find the EVLAN IP address of the CNA. 

c. You will be prompted to enter a username. 

Enter Administrator 

3827 2928–001 7–11


d. You will be prompted to enter a password. 

Check with the System Administrator for the CNA password. 

The FTP session will be established and ready to copy data to/from the MCP. Use the 

GET command to copy a file from the CNA to the host drive. 

DOS FTP Entered from a Windows Server 

A DOS FTP from a Windows server is a file transfer from CNA to the Windows server 

across the private LAN. 

From the Windows server command line, type FTP using the CNA 

private LAN IP address. This initiates an anonymous FTP with CNA. 

Browser FTP from a Windows Server 

Similar to the DOS FTP, this is also a file transfer from CNA to the Windows server 

across the private LAN. 

From Internet Explorer, type FTP:// as shown in the Address field on the 

following screen. 

7–12 3827 2928–001


From a NetMeeting Session 

This is the standard NetMeeting session between CNA and the Windows server. Once 

in NetMeeting, the dump and log files are located in the CNA_Dump partition. The 

CNA_Dump partition is usually drive E (see the following screen for an example). 

From NetMeeting, you can map a network drive to an MCP drive. This will enable you to 

copy the files to the MCP over EVLAN. 

NetMeeting is the only mechanism available for removing files from the CNA_Dump 

partition. 

3827 2928–001 7–13


7–14 3827 2928–001

Appendix A 

Sample Network Initialization Files 

This appendix provides examples of ClearPath CNS and TCP/IP initialization files that 

have to be updated to use the ClearPath Network Appliance (CNA) in an online MCP 

environment. You can find sample CNS and TCP/IP initialization files for ClearPath 

systems with shared adapter support on the Network System Software NETSYSTEM 

release media. 

The following CNS initialization files define the commands preconfigured for ClearPath 

systems with shared adapters. Note that xxxxx is the appropriate ClearPath system 

identifier. 

For MCP Release 8.0: 

• INIT/SAMPLE/CLEARPATH/xxxxx/CPMCP1/CNS 

• INIT/SAMPLE/CLEARPATH/xxxxx/CPMCP2/CNS 

The following TCP/IP initialization files define the TCP/IP commands preconfigured for 

ClearPath systems with shared adapters: 

For MCP Release 8.0: 

• INIT/SAMPLE/CLEARPATH/xxxxx/CPMCP1/TCPIP 

• INIT/SAMPLE/CLEARPATH/xxxxx/CPMCP2/TCPIP 

Where: xxxxx is the appropriate ClearPath system identifier 

3827 2928–001 A–1


CNS Initialization File 

The Connection Group definitions for CNS define the ICPDeviceID and Adapter Type for 

all adapters. The ICPDeviceID is set to a value of 8001 to 8024, depending on the 

Device ID of the CNA. The Adapter Type identifies the public LAN adapters as either the 

10/100 LAN adapter or the Gigabit Ethernet adapter. 

The following Connection Group example identifies the device as CNA1 (ICPDEVICEID = 

8001) and lines 1 and 2 as 10/100/1000 LAN adapters (Adapter Type = GIGABIT). 

NW ADD CONNECTIONGROUP CG_ICP_80010% 

% Connection Group Information 

( TYPE = LAN% 

, ICPDEVICEID = 8001% 

, LINEMODULEID = 1% 

, LINEID = 0% 

, LOCALADDRESS = 08000B008001% 

, MAXINPUTMESSAGESIZELIMIT = 4352% 

, MAXOUTPUTMESSAGESIZELIMIT = 4352% 

, MAXINPUTMESSAGESIZE = 4352% 

, MAXOUTPUTMESSAGESIZE = 4352% 

)% 

;% 

NW ADD CONNECTIONGROUP CG_ICP_80011% 

% Connection Group Information 

( TYPE = LAN% 

, ICPDEVICEID = 8001% 

, LINEMODULEID = 1% 

, LINEID = 1% 

, LOCALADDRESS = *DEFAULT% 

, ADAPTERTYPE = GIGABIT% 

)% 

;% 

A–2 3827 2928–001

TCP/IP Initialization File 


The information in the TCP/IP initialization file consists of the following: 

• A TCPIDENTITY statement for each active line. 

• A MAPPING statement to associate the Windows VLAN IP address with the name 

of the CNA device. 

NW TCPIP TCPIPIDENTITY % 

IPADDRESS = 192.168.16.101 NP 8001 MASK 255.255.255.252 LINEID 0;% 

% % 


IPADDRESS = 192.168.237.200 NP 8001 MASK 255.255.255.0 LINEID 1 % 

% % 


IPADDRESS = 192.168.237.201 NP 8001 MASK 255.255.255.0 LINEID 2; % 

% % 


PADDRESS = 192.168.237.202 NP 8001 MASK 255.255.255.0 LINEID 3; % 

% % 


IPADDRESS = 192.168.237.203 NP 8001 MASK 255.255.255.0 LINEID 4; % 

% % 

NW TCPIP MAPPING + CNA2 % 

192.168.16.102 % 

• Component Connection definitions for each line that has a TCPIDENTITY. 

NW ADD CONNECTION TO CG_ICP_80010% 

80010_TCPIP_80010% 

% Connection Information % 

( NETWORKLAYERENTITY = IP% 

, CLASS = CLASS_1% 

, FRAMETRACE = FALSE% 

, RETRYLIMITXID = 10% 

, MAXINPUTMESSAGESIZELIMIT = 4352% 

, MAXOUTPUTMESSAGESIZELIMIT = 4352% 

, MAXINPUTMESSAGESIZE = 4352% 

, MAXOUTPUTMESSAGESIZE = 4352% 

)% 

;% 

NW ADD CONNECTION TO CG_ICP_80011% 

80011_TCPIP_80011% 

% Connection Information % 

( NETWORKLAYERENTITY = IP% 

, REMOTEADDRESS = 000000000000% 

, CLASS = ETHIP% 

, FRAMETRACE = FALSE% 

, RETRYLIMITXID = 10% 

)% 

;% 

3827 2928–001 A–3


A–4 3827 2928–001

Index 

A 

Adapter Teaming 

configuring, 3-15 

B 

back view 

CNA, 1-7 

booting the CNA, 6-2 

bringing CNA down, 6-3 

bringing CNA into service the first time, 5-7 

bringing CNA up, 6-2 

C 

CD-ROM 

CNA Images CD, 2-2 

CD-ROM drive 

use in CNA, 1-3 

CD-ROM/DVD activity LED, 1-6 

ClearPath Network Appliance 

defined, 1-1 

front view, 1-5 

troubleshooting, 7-1 


back view, 1-7 

bringing down, 6-3 

bringing into service the first time, 5-7 

bringing up, 6-2 

configuring, 3-1 

defined, 1-1 

embedded software, 2-1 

features, 1-2 

front view, 1-5 

How it fits in ClearPath system, 1-10 

image, 2-1 

installation steps, operating system 

image, 2-8, 7-10 

installing image, 2-2 

installing Network Services on, 4-2 

installing operating system image, 2-7 

operating system image installation 

steps, 2-8, 7-10 

operating with ODT commands, 6-1 

service strategy, 7-2 

software components, 1-13 

styles, 1-4 


Event Log procedure, accessing, 7-8 

EVLAN Ping procedure, 7-5 

Private LAN Ping procedure, 

accessing, 7-5 

Public LAN Ping procedure, 


CNA complex configuration, 1-12 

CNA EVLAN IP Addresses, 3-2 

CNA Images CD-ROM, 2-2 

CNA Safe Boot floppy disk, 2-2 

CNS initialization file (sample), A-1 

commands 

ODT, 6-1 

configuration rules, 1-11 

configuring CNA, 3-1 

configuring for ODT mode 

Web Enabler, 5-4 

3827 2928–001 Index–1 

D 

debug 

flow chart, 7-2 

procedure, 7-2 

dump files 

retrieving CNA, NT-IOP, and NNS 

files, 7-11 

E 

Ethernet Jumbo Frames, preparing to 

use, 3-13 

Event Log procedure, accessing steps, 7-8 

EVLAN Ping procedure, 7-5

Index 

F 

FC-SL card, 1-3 

features 


FiberChannel-SuperLite (FC-SL), 1-3 

FID, 1-13 

field replaceable units 


Fixed disk drive status LED, 1-6 

Floppy activity drive, 1-6 

floppy disk 


front view 


H 

hard disk 


I 

ID button, 1-6 

ID LED, 1-6 

IEEE 802.1Q VLANS, preparing to use, 3-14 

image 

guidelines for installing, 2-1 

initialization files 

CNS and TCP/IP, A-1 

installing 

CNA operating system image, 2-7, 2-8, 

7-10 

Network Services on the CNA, 4-2 

installing CNA 

installing the CNA image, 2-2 

installing NT-IOP software, 5-1 

installing ODT software, 5-1 

installing Web Enabler, 5-3 

IOCD 

I/O Firmware CD-ROM, 5-1 

IP Addresses 

CNA VLAN, 3-2 

defined, Table 3-1, 3-2 

MCP Private LAN, 3-2 

MCP Public IP Addresses, 3-2 

MCP VLAN, 3-2 

on boot floppy, 2-6 

Private LAN, 3-2 

Index–2 3827 2928–001 

J 

Jumbo Frames, preparing to use, 3-13 

L 

Line 3 activity LED, 1-5 

LOM, 1-13 

M 

maintenance LAN activity LED, 1-5 

MCP EVLAN IP Addresses, 3-2 

MCP Public IP Addresses, 3-2 

N 

NetMeeting 

establishing a connection to CNA, 2-5 

installing, 2-3 

precautions when using, 6-3 


using, 2-5 

working with, 2-3 

Network Services 


Network Services installation 

Adapter Properties screen, 4-7 

Choose Configuration Options screen, 4-12 

Choose Destination Location screen, 4-4 

Configuration of Shared Adapter Cards 

screen, 4-6 

MCP Host Name screen, 4-13 

Network Services Properties screen, 4-11 

Review Configuration Option Selections 

screen, 4-14 

Review Shared Adapter Card Selections 

screen, 4-9 

Select Adapter Cards for MCP Server 

Access screen, 4-7, 4-8 

Setup Complete screen, 4-15 

Specify Windows Server Environment 

screen, 4-10 

Start Copying Files screen, 4-5 

NMI button, 1-6 

NNS, 1-13 

NT-IOP software 

installing, 5-1

O 

ODT commands, 6-1 

ODT software 


operating system image 

installing on CNA, 2-7 

P 

partitions 

CNA_Primary partition, 2-2 

CNA_Safe partition, 2-2 

password, 3-4 

initial, 2-3 

screen used for changing, 3-8 

peripheral devices 

locations in CNA, 1-5 

Ping procedure 

EVLAN, 7-5 

Private LAN, 7-5 

Public LAN, 7-7 

port aggregation (shared adapters) 

preparing for, 3-12 

Power button, 1-6 

Power LED, 1-5 

powering down CNA, 6-3 

powering on CNA, 6-2 

preparing to use Ethernet 

JumboFrames, 3-13 

preparing to use IEEE 802.1Q VLANS, 3-14 

private LAN activity LED, 1-5 

Private LAN IP Addresses, 3-2 

Private LAN Ping procedure, 7-5 

public LAN activity LED, 1-5 

Public LAN Ping procedure, accessing 

steps, 7-7 

R 

RAID hard disk 


Reset button, 1-6 

retrieving dump files 

CNA, NT-IOP, and NNS files, 7-11 

Index 

3827 2928–001 Index–3 

S 

safe boot, 2-8, 7-9 

performing, 7-10 

screens 

Adapter Properties (for Network Services 

software), 4-7 

Choose Configuration Options(for Network 

Services software), 4-12 

Choose Destination Location (for Network 


CNA Configuration - change password, 3-7 

CNA Configuration - configuration 

summary, 3-10 

CNA Configuration - enter computer 

name, 3-7 

CNA Configuration - enter path to 

CNAcfg4.ini, 3-5 

CNA Configuration - enter private LAN IP 

address, 3-6 

CNA Configuration - Ethernet support, 3-8 

CNA Configuration dialog box, 3-4 

Configuration of Shared Adapter Cards (for 

Network Services software), 4-6 

configuring IEEE 802.1Q VLANs, 3-17 

Date/Time Properties - configuration 

screen, 3-9 

Format disk screen, 2-10 

Installation Options screen for installing 

ODT software, 5-2 

Intel(R) PROSet II - configuring adapters as 

part of a team, 3-15, 3-16 

Intel(R) PROSet II - configuring IEEE 

802.1Q VLANs, 3-17 

Intel(R) PROSet II - recalculate networking 

bindings, 3-21 

Intel(R) PROSet II - Save/Restore 

settings, 3-19 

Intel(R) PROSet II - saving settings, 3-18 

MCP Host Name (for Network Services 


NetMeeting - Not in a Call screen, 2-5 

NetMeeting - Remote Desktop Sharing 

Password screen, 2-3 

Network Services Properties(for Network 


Place a Call dialog box, 2-5 

Remote Desktop Sharing Password, 4-2 

Review Configuration Option Selections 

(for Network Services 

software), 4-14

Index 

Review Shared Adapter Card Selections 

(for Network Services 


Select Adapter Cards for MCP Server 

Access (for Network Services 


Setup Complete (for Network Services 


Specify Windows Server Environment(for 

Network Services software), 4-10 

Start Copying Files (for Network Services 


service strategy 


shared adapters 

keep current selection, 4-6 

software block diagram, 1-13 

software installation 

installing CNA image, 2-2 

styles 


System block diagram, 1-10 

System Status LED, 1-6 

T 

TCP/IP initialization file (sample), A-1 

troubleshooting 


Event Log procedure, accessing, 7-8 

EVLAN Ping procedure, accessing, 7-5 

Private LAN Ping procedure, 


Public LAN Ping procedure, 


NetMeeting Procedure, 7-9 

steps for, 7-2 

typical CNA configuration, 1-11 

W 

Web Enabler 

configuring for ODT mode, 5-4 


Index–4 3827 2928–001

*38272928-001* 

38272928– 001

CNA RMD1 Implementation Guide - Public Support Login - Unisys

Create successful ePaper yourself

Delete template?

Save as template?