CNA RMD1 Implementation Guide - Public Support Login - Unisys
CNA RMD1 Implementation Guide - Public Support Login - Unisys
CNA RMD1 Implementation Guide - Public Support Login - Unisys
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
ClearPath Network<br />
Appliance<br />
<strong>RMD1</strong><br />
<strong>Implementation</strong> <strong>Guide</strong><br />
Printed in USA<br />
February 2004 3827 2928–001
ClearPath Network<br />
Appliance<br />
<strong>RMD1</strong><br />
<strong>Implementation</strong> <strong>Guide</strong><br />
© 2004 <strong>Unisys</strong> Corporation.<br />
All rights reserved.<br />
Printed in USA<br />
February 2004 3827 2928–001<br />
UNISYS
NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information<br />
described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to<br />
purchase or lease equipment or to license software. The only warranties made by <strong>Unisys</strong>, if any, with respect to the<br />
products described in this document are set forth in such agreement. <strong>Unisys</strong> cannot accept any financial or other<br />
responsibility that may be the result of your use of the information in this document or software material, including<br />
direct, special, or consequential damages.<br />
You should be very careful to ensure that the use of this information and/or software material complies with the laws,<br />
rules, and regulations of the jurisdictions with respect to which it is used.<br />
The information contained herein is subject to change without notice. Revisions may be issued to advise of such<br />
changes and/or additions.<br />
Notice to U.S. Government End Users: This is commercial computer software or hardware documentation developed at<br />
private expense. Use, reproduction, or disclosure by the Government is subject to the terms of <strong>Unisys</strong> standard<br />
commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract data<br />
rights clauses.<br />
Correspondence regarding this publication can be e-mailed to doc@unisys.com.<br />
<strong>Unisys</strong> and ClearPath are registered trademarks of <strong>Unisys</strong> Corporation in the United States and other countries.<br />
All other brands and products referenced in this document are acknowledged to be the trademarks or registered<br />
trademarks of their respective holders.
ClearPath Network<br />
Appliance<br />
<strong>RMD1</strong><br />
<strong>Implementation</strong> <strong>Guide</strong><br />
ClearPath<br />
Network<br />
Appliance<br />
<strong>RMD1</strong><br />
<strong>Implementation</strong><br />
<strong>Guide</strong><br />
3827 2928–001 3827 2928–001<br />
Bend here, peel upwards and apply to spine.
Contents<br />
Section 1. Introduction<br />
About This <strong>Guide</strong> .................................................................................. 1–1<br />
ClearPath Network Appliance (<strong>CNA</strong>) Features...................................... 1–1<br />
An Overview of the Hardware .............................................................. 1–3<br />
<strong>CNA</strong> Styles........................................................................... 1–4<br />
<strong>CNA</strong> Front View................................................................... 1–5<br />
<strong>CNA</strong> Back Views.................................................................. 1–7<br />
FC-SL LEDs.......................................................................... 1–9<br />
<strong>CNA</strong> in a ClearPath System ................................................................ 1–10<br />
System Configuration Rules ............................................................... 1–11<br />
<strong>CNA</strong> Software ..................................................................................... 1–13<br />
Section 2. Installing the <strong>CNA</strong> Operating System Image<br />
<strong>Guide</strong>lines for Installing the <strong>CNA</strong> Image............................................... 2–1<br />
Overview of the Installation Process .................................................... 2–2<br />
Establishing a NetMeeting Connection to <strong>CNA</strong>.................................... 2–2<br />
Installing NetMeeting .......................................................... 2–3<br />
Working with NetMeeting ................................................... 2–3<br />
Establishing a Connection to <strong>CNA</strong>....................................... 2–5<br />
Installing the <strong>CNA</strong> Operating System Image ........................................ 2–7<br />
Performing a <strong>CNA</strong> Safe Boot............................................... 2–8<br />
Installing the <strong>CNA</strong> Image..................................................... 2–9<br />
Section 3. Configuring the <strong>CNA</strong><br />
Overview of <strong>CNA</strong> Configuration............................................................ 3–1<br />
IP Addressing Information for <strong>CNA</strong> Devices ....................... 3–2<br />
Configuring a <strong>CNA</strong> ................................................................................ 3–4<br />
Configuring Shared Adapter Features................................................. 3–12<br />
Preparing to Use Port Aggregation.................................... 3–12<br />
Preparing to Use Ethernet Jumbo Frames........................ 3–13<br />
Preparing to Use IEEE 802.1Q VLANS.............................. 3–14<br />
Configuring IEEE 802.1Q VLANs or Port Aggregation........................ 3–15<br />
Configuring IEEE 802.1Q VLANs....................................... 3–17<br />
Saving Your Settings ......................................................... 3–18<br />
Restoring Your Settings..................................................... 3–21<br />
Assigning the Advanced Features Adapter to the<br />
MCP .............................................................................. 3–22<br />
3827 2928–001 iii
Contents<br />
Section 4. Installing Network Services Software on the <strong>CNA</strong><br />
Preparing to Install Network Services ...................................................4–1<br />
Network Services Installation Procedure...............................................4–2<br />
Section 5. Installing ODT and NT-IOP Software<br />
Installing ODT and IOP Files..................................................................5–1<br />
Installing Web Enabler..........................................................5–3<br />
Configuring a <strong>CNA</strong> for ODT Mode .......................................5–4<br />
Configuring a Redundant ODT Connection..........................5–5<br />
Bringing a <strong>CNA</strong> Into Service ..................................................................5–7<br />
Section 6. <strong>CNA</strong> Operations<br />
ODT Commands ....................................................................................6–1<br />
Bringing a <strong>CNA</strong> Up.................................................................................6–2<br />
Powering a <strong>CNA</strong> Down..........................................................................6–3<br />
Resetting a <strong>CNA</strong> ....................................................................................6–3<br />
Precautions When Configuring and Using <strong>CNA</strong> ....................................6–3<br />
Section 7. Troubleshooting the <strong>CNA</strong><br />
<strong>CNA</strong> Debug Flow Chart .........................................................................7–2<br />
<strong>CNA</strong> Debug Checklist Procedure...........................................................7–3<br />
Private LAN Ping Procedure ..................................................................7–5<br />
EVLAN Ping Procedure..........................................................................7–5<br />
<strong>Public</strong> LAN Ping Procedure....................................................................7–7<br />
Event Log Procedure .............................................................................7–8<br />
Troubleshooting the NetMeeting Procedure.........................................7–9<br />
Performing a <strong>CNA</strong> Safe Boot...............................................................7–10<br />
Log and Dump File Retrieval ...............................................................7–11<br />
Appendix A. Sample Network Initialization Files<br />
CNS Initialization File ............................................................................ A–2<br />
TCP/IP Initialization File......................................................................... A–3<br />
Index .................................................................................................................. 1<br />
iv 3827 2928–001
Figures<br />
1–1. ClearPath Network Appliance (<strong>CNA</strong>).................................................................. 1–1<br />
1–2. <strong>CNA</strong> Front View ................................................................................................. 1–5<br />
1–3. <strong>CNA</strong> Back Views ................................................................................................ 1–7<br />
1–4. NIC Card LEDs ................................................................................................... 1–8<br />
1–5. FC-SL LEDs ........................................................................................................ 1–9<br />
1–6. <strong>CNA</strong> in a ClearPath System ............................................................................. 1–10<br />
1–7. Typical <strong>CNA</strong> Configuration ............................................................................... 1–11<br />
1–8. Complex <strong>CNA</strong> Configuration ............................................................................ 1–12<br />
1–9. <strong>CNA</strong> Software Interfaces ................................................................................. 1–13<br />
7–1. <strong>CNA</strong> Debug Flowchart ....................................................................................... 7–2<br />
3827 2928–001 v
Figures<br />
vi 3827 2928–001
Tables<br />
3–1. IP Addresses ...................................................................................................... 3–2<br />
3827 2928–001 vii
Tables<br />
viii 3827 2928–001
Section 1<br />
Introduction<br />
About This <strong>Guide</strong><br />
This guide describes the <strong>RMD1</strong> ClearPath Network Appliance (<strong>CNA</strong>) on ClearPath Plus<br />
servers. It also provides the information needed to<br />
• Install the operating system software on the <strong>CNA</strong><br />
• Configure the operating system software<br />
• Install Network Services software on the <strong>CNA</strong><br />
• Install operator display terminal (ODT) software on the <strong>CNA</strong><br />
• Operate and troubleshoot the <strong>CNA</strong><br />
ClearPath Network Appliance (<strong>CNA</strong>) Features<br />
The <strong>RMD1</strong> <strong>CNA</strong> is a dedicated system housed in a 1U-high rack-mounted unit. It<br />
provides the operator display terminal (ODT) interface and the communications front end<br />
for ClearPath Plus servers. Figure 1-1 illustrates the <strong>CNA</strong>.<br />
Figure 1–1. ClearPath Network Appliance (<strong>CNA</strong>)<br />
3827 2928–001 1–1
Introduction<br />
The <strong>CNA</strong> provides the following features:<br />
• Provides E-mode communications for ClearPath servers.<br />
• Handles network traffic between the ClearPath host and the network without using<br />
the existing Windows servers. This removes network communications from the<br />
existing Windows servers and reduces the cost of network communications.<br />
• Provides ODT capability.<br />
• Reduces the possibility of external network attacks on the operating system, thereby<br />
improving ClearPath system security.<br />
• Is dedicated to networking and ODT capability and is closed to user applications,<br />
thereby improving overall reliability.<br />
• Is a dedicated component that offers both an economic and physical advantage over<br />
an existing full-featured Windows NT server.<br />
1–2 3827 2928–001
An Overview of the Hardware<br />
The <strong>CNA</strong> uses high-quality PC server components. The major components are<br />
Introduction<br />
• Intel-based motherboard supporting<br />
− Single 2.4-GHz Intel Xeon processor<br />
− 1 GB of ECC supported SDRAM<br />
− On-board video controller<br />
− 10/100/1000 private LAN for system management<br />
• Two IDE RAID mirrored hard disks<br />
• CD-ROM drive for loading system software with a data transfer speed of a least 32X<br />
• Floppy disk drive; 3.5-inch 1.44-MB drive<br />
• <strong>Public</strong> LAN Gigabit Ethernet network interface cards (NICs)<br />
• One fiber optic link from the FiberChannel-SuperLite (FC-SL) card for connecting to<br />
the host server<br />
Note: There are no field-replaceable units (FRUs) in the <strong>CNA</strong>. The FRU for the <strong>CNA</strong> is<br />
the entire rack-mounted unit.<br />
3827 2928–001 1–3
Introduction<br />
<strong>CNA</strong> Styles<br />
The following <strong>CNA</strong> styles are available:<br />
• <strong>RMD1</strong>-GEC (Copper Gigabit Ethernet)<br />
This style contains:<br />
− Four 10/100/1000 links from the quad-port NIC for public LAN connections<br />
− One RJ45 10/100/1000 link from the on-board LAN port for connecting to the<br />
private (maintenance) LAN<br />
− One fiber optic link from the FC-SL card for connecting to the ClearPath host<br />
• <strong>RMD1</strong>-GEF (Fiber-optic Gigabit Ethernet)<br />
This style contains:<br />
− Two fiber-optic Gigabit Ethernet links from the dual-port NIC for public LAN<br />
connections<br />
− One RJ45 10/100/1000 link from the on-board LAN port for connecting to the<br />
private (maintenance) LAN<br />
− One fiber-optic link from the FC-SL card for connecting to the ClearPath host<br />
1–4 3827 2928–001
<strong>CNA</strong> Front View<br />
Introduction<br />
Figure 1-2 illustrates a front view of the <strong>CNA</strong> and identifies the locations of the peripheral<br />
devices used. The drives, indicators, and power buttons reside behind a lockable bezel.<br />
M N O P Q<br />
Figure 1–2. <strong>CNA</strong> Front View<br />
A B C D E F G H<br />
I J K L<br />
A. Private LAN activity LED – Indicates on-board private (maintenance) LAN<br />
activity. Green when there is a link. Blinks when there is traffic.<br />
B. Line 3 (Opt) activity LED – Not used.<br />
C. Power LED – Green when power is on.<br />
D. Power button – Momentary switch that turns power on and off. To activate, press<br />
and release the button; do not hold it down. There is a delay of a few seconds from<br />
when you release the button to when power actually goes off. Note: There is still<br />
3827 2928–001 1–5<br />
090
Introduction<br />
standby power in the chassis when the power is off. To power off the <strong>CNA</strong>, you should<br />
normally:<br />
1. Log on to the system with NetMeeting.<br />
2. Shut down from Windows.<br />
3. If you cannot perform steps 1 and 2, verify that the Fixed Disk Drive Status LED<br />
(F in the figure) is off for at least 10 seconds, and then press the Power button.<br />
E. System Status LED – Continuous green when status is normal. Blinking green<br />
when operating in degraded condition. Continuous amber when there is a hardware<br />
fault. Blinking amber when there is a hardware warning. Off when <strong>CNA</strong> is powered off<br />
or there is no AC power.<br />
F. Fixed disk drive status LED – Random green when drive is being accessed.<br />
Yellow when there is a disk fault.<br />
G. ID LED – Blue when ID button is pressed.<br />
H. ID button – When pressed, the ID LEDs on the front and back turn blue. This helps<br />
an operator find the correct <strong>CNA</strong> in a rack with multiple <strong>CNA</strong>s.<br />
I. Video connector – Not used.<br />
J. NMI button (tool assisted) – Non-maskable interrupt, which forces a dump and<br />
reboot. Not for normal operation.<br />
K. USB port – Not used.<br />
L. Reset button – Momentary switch that resets the box. To reset, you should<br />
normally:<br />
1. Log on to the system with NetMeeting.<br />
2. Shut down from Windows.<br />
3. If you cannot perform steps 1 and 2, verify that the Fixed Disk Drive Status LED<br />
(F in the figure) is off for at least 10 seconds, and then press the Reset button.<br />
M. Floppy activity LED – Green when drive is being accessed.<br />
N. CD-ROM/DVD activity LED – Green when drive is being accessed.<br />
O. CD-ROM drive eject button<br />
P. Manual CD-ROM drive eject button (tool assisted)<br />
Q. Floppy drive eject button<br />
1–6 3827 2928–001
<strong>CNA</strong> Back Views<br />
Introduction<br />
At the back of the <strong>CNA</strong> are the connections to the ClearPath host and to the public and<br />
private LANs. All other connectors, such as parallel and serial ports, mouse and<br />
keyboard connectors, and monitor connector should not be used. Figure 1-3 illustrates<br />
the back view of the Copper Gigabit Ethernet <strong>CNA</strong> (<strong>RMD1</strong>-GEC) and the Fiber-Optic<br />
Gigabit Ethernet <strong>CNA</strong> (<strong>RMD1</strong>-GEF).<br />
<strong>RMD1</strong>-GEC<br />
FC-SL Connection<br />
<strong>RMD1</strong>-GEF<br />
FC-SL Connection<br />
Not Used<br />
Maintenance LAN<br />
Connection<br />
Not Used<br />
Maintenance LAN<br />
Connection<br />
Not Used<br />
Not Used<br />
NIC Card<br />
NIC Card<br />
Figure 1–3. <strong>CNA</strong> Back Views<br />
<strong>Public</strong> LAN<br />
Connection<br />
<strong>Public</strong> LAN<br />
Connection<br />
<strong>Public</strong> LAN connections – Connect the <strong>CNA</strong> to the public network. The <strong>CNA</strong> fiberoptic<br />
Gigabit Ethernet (<strong>RMD1</strong>-GEF) NIC supports two fiber optic Gigabit Ethernet links.<br />
The copper Gigabit Ethernet (<strong>RMD1</strong>-GEC) NIC supports two 10/100/1000 links. There is<br />
also an additional RJ45 10/100/1000 LAN connection with the <strong>RMD1</strong>-GEC style.<br />
Private (maintenance) LAN connection – Only the RJ45 10/100/1000 LAN<br />
connector is used. It provides the connection to the private LAN.<br />
3827 2928–001 1–7<br />
092
Introduction<br />
NIC Card LEDs<br />
Figure 1-4 illustrates the LEDs on the two types of NIC cards.<br />
Copper Gigabit Ethernet<br />
PORT D<br />
Fiber-Optic Gigabit Ethernet<br />
10/100/1000 10/100/1000 10/100/1000 10/100/1000<br />
ACT/LNK ACT/LNK ACT/LNK ACT/LNK<br />
ACT/LNK<br />
ACTLNK B<br />
PORT C<br />
1–8 3827 2928–001<br />
PORT B<br />
ACTLNK A<br />
PORT A<br />
ACT/LNK<br />
Figure 1–4. NIC Card LEDs<br />
ACT/LNK LED – Indicates if the port is connected to a valid link partner. Green when<br />
there is a link; blinks when there is traffic. For the copper NIC only, flashes yellow to<br />
identify the port when you use the Identify Adapter button through the Intel PROSet<br />
software. Helps an operator find a specific port.<br />
10/100/1000 LED – For the copper NIC only. Indicates the speed the port is using,<br />
where:<br />
Off = 10 Mbps<br />
Green = 100 Mbps<br />
Yellow = 1000 Mbps<br />
ACT/LNK<br />
001<br />
002
FC-SL LEDs<br />
Figure 1-5 illustrates the LEDs on the FC-SL.<br />
2Gb<br />
Introduction<br />
3827 2928–001 1–9<br />
ACT<br />
LINK<br />
SFP<br />
Figure 1–5. FC-SL LEDs<br />
LINK LED – Green LED that indicates if there is a good link (cable connection) between<br />
the <strong>CNA</strong> and the host FC-IOP it is connected to. Green when there is a link.<br />
ACT LED – Yellow LED that blinks when there is traffic; the frequency of the blinking<br />
varies with the amount of network traffic. If the LED stays on after booting up, this<br />
indicates that the card has not passed self test or that NNS software is not installed.<br />
2Gb LED – Blue LED that indicates the speed the port is using, where:<br />
Off =1 Gbps<br />
Blue =2 Gbps<br />
036A
Introduction<br />
<strong>CNA</strong> in a ClearPath System<br />
Figure 1-6 shows where the <strong>CNA</strong> fits into a ClearPath system, including:<br />
• Networking Services (NNS), which is part of the <strong>CNA</strong><br />
• <strong>CNA</strong> connecting to the ClearPath system through an FC-SL card<br />
• The ODT interface on the <strong>CNA</strong><br />
• <strong>Public</strong> LAN connections<br />
<strong>CNA</strong> uses the motherboard LAN connection for remote management of the <strong>CNA</strong> box.<br />
Since <strong>CNA</strong> is a “headless” system (that is, no monitor or keyboard), it supports a remote<br />
GUI interface. The remote GUI uses NetMeeting to configure and support the <strong>CNA</strong><br />
system. NetMeeting is installed on the Service Processor and may be installed on the<br />
optional Windows partition installed in the ClearPath system or on the optional ODW.<br />
Windows<br />
Partition<br />
(Optional)<br />
MCP<br />
Partition<br />
TCP/IP<br />
LAN<br />
IPL<br />
FC-IOP<br />
FC-IOP<br />
FC-IOP<br />
CSE SP<br />
Switch<br />
Modem<br />
ODT<br />
(optional)<br />
1–10 3827 2928–001<br />
LAN<br />
ODT<br />
FC-SL<br />
LAN<br />
ODT<br />
FC-SL<br />
NNS<br />
NNS<br />
Figure 1–6. <strong>CNA</strong> in a ClearPath System<br />
<strong>CNA</strong><br />
LAN<br />
LAN<br />
<strong>CNA</strong><br />
LAN<br />
LAN<br />
040
System Configuration Rules<br />
The <strong>CNA</strong> is an integral part of the ClearPath system.<br />
Introduction<br />
− The minimum configuration is one <strong>CNA</strong> per partition<br />
− A redundant network and ODT configuration has two <strong>CNA</strong>s per partition,<br />
connected to a single FC-IOP in the host.<br />
− A fully redundant configuration has two <strong>CNA</strong>s per partition, connected to two<br />
FC-IOPs in the host.<br />
Figure 1-7 illustrates a typical <strong>CNA</strong> configuration for a ClearPath system with two<br />
partitions. It identifies the <strong>CNA</strong> naming convention (<strong>CNA</strong>1–<strong>CNA</strong>4) for each MCP<br />
partition/power domain and shows the 8-port switches on the private LAN.<br />
Windows<br />
Partition<br />
0<br />
MCP<br />
Partition<br />
0<br />
MCP<br />
Partition<br />
1<br />
Windows<br />
Partition<br />
1<br />
ODT<br />
IPL 0<br />
SP 0<br />
<strong>CNA</strong>1<br />
<strong>CNA</strong>3<br />
<strong>CNA</strong>4<br />
<strong>CNA</strong>2<br />
SP 1<br />
IPL 1<br />
ODT<br />
192.168.222.41<br />
*1<br />
192.168.222.1<br />
192.168.222.151<br />
192.168.222.153<br />
192.168.222.154<br />
192.168.222.152<br />
192.168.222.2<br />
*1<br />
192.168.222.42<br />
8-port Switch<br />
Power Domain 0<br />
Power Domain 1<br />
8-port Switch<br />
Figure 1–7. Typical <strong>CNA</strong> Configuration<br />
192.168.222.149 or 20<br />
Note:<br />
2 MCP Partitions, 2 <strong>CNA</strong>s per partition<br />
All IP addresses are 192.168.222.X<br />
*1 IP address depends on subDIB<br />
046<br />
3827 2928–001 1–11
Introduction<br />
Figure 1-8 illustrates a more complex configuration of a dual domain system. It identifies<br />
the <strong>CNA</strong> naming convention (<strong>CNA</strong>1–<strong>CNA</strong>24) for each MCP partition/power domain and<br />
shows the 8-port and 16-port private LAN switches.<br />
Windows<br />
Partition<br />
0<br />
MCP<br />
Partition<br />
0<br />
MCP<br />
Partition<br />
1<br />
Windows<br />
Partition<br />
1<br />
ODT<br />
IPL 0<br />
SP 0<br />
<strong>CNA</strong>1<br />
<strong>CNA</strong>3<br />
<strong>CNA</strong>5<br />
<strong>CNA</strong>7<br />
<strong>CNA</strong>9<br />
<strong>CNA</strong>11<br />
<strong>CNA</strong>12<br />
<strong>CNA</strong>10<br />
<strong>CNA</strong>8<br />
<strong>CNA</strong>6<br />
<strong>CNA</strong>4<br />
<strong>CNA</strong>2<br />
SP 1<br />
IPL 1<br />
ODT<br />
192.168.222.41<br />
*1<br />
192.168.222.1<br />
192.168.222.151<br />
192.168.222.2<br />
*1<br />
192.168.222.42<br />
8-port Switch 16-port Switch<br />
153<br />
155<br />
157<br />
159<br />
161<br />
162<br />
160<br />
158<br />
156<br />
154<br />
152<br />
Power Domain 0<br />
Power Domain 1<br />
8-port Switch 16-port Switch<br />
<strong>CNA</strong>13<br />
<strong>CNA</strong>15<br />
<strong>CNA</strong>17<br />
<strong>CNA</strong>19<br />
<strong>CNA</strong>21<br />
<strong>CNA</strong>23<br />
<strong>CNA</strong>24<br />
<strong>CNA</strong>22<br />
<strong>CNA</strong>20<br />
<strong>CNA</strong>18<br />
<strong>CNA</strong>16<br />
<strong>CNA</strong>14<br />
1–12 3827 2928–001<br />
163<br />
165<br />
167<br />
169<br />
171<br />
173<br />
174<br />
172<br />
170<br />
168<br />
166<br />
164<br />
192.168.222.149 or 20<br />
Note:<br />
2 MCP Partitions, 12 <strong>CNA</strong>s per partition<br />
All IP addresses are 192.168.222.X<br />
*1 IP address depends on subDIB<br />
045<br />
Figure 1–8. Complex <strong>CNA</strong> Configuration
<strong>CNA</strong> Software<br />
Figure 1-9 shows the software components in a <strong>CNA</strong>.<br />
Fibre<br />
Channel<br />
(to host)<br />
Legend:<br />
FC-SL<br />
FID<br />
(driver)<br />
ODT<br />
Installer<br />
LOM = LAN on Motherboard<br />
<strong>CNA</strong><br />
Installer<br />
NIC = Network Interface Card<br />
NNS =Network Services<br />
FID = FC-SL Interface Driver<br />
ODT = Operator Display Terminal<br />
NT Embedded<br />
Image<br />
NNS<br />
(TCP Offload SA, etc.)<br />
NNS<br />
Installer<br />
Figure 1–9. <strong>CNA</strong> Software Interfaces<br />
Introduction<br />
3827 2928–001 1–13<br />
LOM<br />
NIC<br />
NIC<br />
NIC<br />
(GEC<br />
only)<br />
NIC<br />
(GEC<br />
only)<br />
Private<br />
LAN<br />
<strong>Public</strong><br />
LAN<br />
<strong>Public</strong><br />
LAN<br />
<strong>Public</strong><br />
LAN<br />
<strong>Public</strong><br />
LAN<br />
The <strong>CNA</strong> operating system is the Windows NT Embedded Edition and is built using<br />
Target Designer. Since <strong>CNA</strong> is a headless system, there is no monitor, keyboard, or<br />
mouse. The <strong>CNA</strong> operating system image resides on the RAID disk.<br />
The NNS networking software is the network interface software between the E-mode<br />
host and the public LAN. The public LAN NICs include 10/100 Ethernet and Gigabit<br />
Ethernet and use Windows 4.0 drivers.<br />
The private LAN interface supports the NetMeeting remote GUI, MCP Call Home, and<br />
Windows FTP.<br />
The FC-SL board has its own driver (FID), which is part of the NNS software.<br />
The ODT also communicates across the private LAN, using NT-IOP.<br />
047
Introduction<br />
1–14 3827 2928–001
Section 2<br />
Installing the <strong>CNA</strong> Operating System<br />
Image<br />
This section provides the information required to install the ClearPath Network Appliance<br />
(<strong>CNA</strong>) operating system image. It contains procedures to<br />
• Establish a NetMeeting connection to <strong>CNA</strong><br />
• Perform a <strong>CNA</strong> safe boot<br />
• Install the <strong>CNA</strong> operating system image on the RAID hard disk<br />
<strong>Guide</strong>lines for Installing the <strong>CNA</strong> Image<br />
The <strong>CNA</strong> operating system image contains the Microsoft Windows NT Embedded<br />
software and the components required for building a bootable system. The image is<br />
installed at the factory so the <strong>CNA</strong> system arrives ready for use. You do not need to<br />
reinstall the <strong>CNA</strong> image before installing Network Services software (see Section 4).<br />
However, you may need to reinstall the image if you are<br />
• Upgrading to a new release level of the <strong>CNA</strong> image<br />
• Correcting certain problem conditions, such as a configuration problem. See Section<br />
7 for information on troubleshooting the <strong>CNA</strong>.<br />
The rest of this section provides instructions for reinstalling the <strong>CNA</strong> operating system<br />
image.<br />
3827 2928–001 2–1
Installing the <strong>CNA</strong> Operating System Image<br />
Overview of the Installation Process<br />
To reinstall the <strong>CNA</strong> image, you need the following:<br />
• <strong>CNA</strong> Safe Boot floppy disk<br />
The <strong>CNA</strong> Safe Boot disk directs the boot to occur on the <strong>CNA</strong>_Safe partition on the<br />
hard disk. This is only required when a new image needs to be stored on the<br />
<strong>CNA</strong>_Primary partition.<br />
• <strong>CNA</strong> Images CD-ROM<br />
The <strong>CNA</strong> Images CD-ROM contains the shipped <strong>CNA</strong> images. The images are<br />
located in separate directories, as follows:<br />
• <strong>RMD1</strong>_GEC contains the image for the Copper Gigabit Ethernet style <strong>CNA</strong>.<br />
• <strong>RMD1</strong>_GEF contains the image for the fiber-optic Gigabit Ethernet style <strong>CNA</strong>.<br />
• The NetMeeting directory contains NetMeeting installation and Readme files.<br />
When you reinstall the <strong>CNA</strong> image, the image that corresponds to the hardware style of<br />
your <strong>CNA</strong> system is loaded from the Images CD-ROM to the <strong>CNA</strong>_Primary partition.<br />
Establishing a NetMeeting Connection to <strong>CNA</strong><br />
Since the <strong>CNA</strong> is a “headless” system with no monitor, keyboard, or mouse, a remote<br />
GUI is required to view and monitor the <strong>CNA</strong> system. The remote GUI runs across the<br />
secure private maintenance LAN between the <strong>CNA</strong> and a remote Windows system. The<br />
remote system uses the Microsoft NetMeeting software to establish a session between<br />
the two systems.<br />
The remote system running NetMeeting can be any of the following Windows systems:<br />
• The ClearPath Service Processor<br />
• The Windows enterprise server<br />
• An Operator Display Workstation (ODW) attached to the maintenance LAN<br />
• A laptop system connected to the private maintenance LAN<br />
2–2 3827 2928–001
Installing NetMeeting<br />
Installing the <strong>CNA</strong> Operating System Image<br />
NetMeeting is preinstalled on the Service Processor. It is also included in the<br />
\NetMeeting directory of the <strong>CNA</strong> CD-ROM.<br />
If you copy NetMeeting from the CD-ROM, review the Readme help file and follow the<br />
simple instructions to install it on the remote Windows system.<br />
Working with NetMeeting<br />
Note the following when working with NetMeeting:<br />
• Sometimes NetMeeting will not establish a session with the <strong>CNA</strong> even though a<br />
“ping” of the <strong>CNA</strong> is successful. You can usually fix this problem by closing the<br />
NetMeeting window and then restarting NetMeeting.<br />
• Use the correct IP address.<br />
• The NetMeeting full screen option makes it easier to work with NetMeeting.<br />
Once the connection is established, the familiar Logon dialog prompt “Press<br />
Ctrl+Alt+Del to <strong>Login</strong>” is displayed. Do not press Ctrl+Alt+Del since this key sequence<br />
is interpreted by your local PC. Instead, click Send Ctrl+Alt+Del from the Control<br />
menu in the upper left of the NetMeeting screen. The NT logon dialog box appears.<br />
Once connected to the <strong>CNA</strong>, you are prompted to enter the UserID/Password. On the<br />
Remote Desktop Sharing Password screen, enter Administrator for both, and click<br />
OK. Note that Administrator is case-sensitive and must be entered as shown here:<br />
3827 2928–001 2–3
Installing the <strong>CNA</strong> Operating System Image<br />
Note: If you enter an invalid password four consecutive times, the following error<br />
message is displayed on the NetMeeting window:<br />
The Other person didn’t allow you to join the meeting.<br />
All additional attempts to “place a call” to the <strong>CNA</strong> device will result in the same<br />
error message, regardless of the terminal from which the call attempt is made. This<br />
is a NetMeeting security feature to prevent unauthorized access. When this error<br />
message is displayed, you must reboot the <strong>CNA</strong> device to retry the NetMeeting<br />
login. This will give you four more chances to enter the correct password.<br />
After successfully logging on, the NT desktop of the <strong>CNA</strong> appears.<br />
2–4 3827 2928–001
Establishing a Connection to <strong>CNA</strong><br />
Installing the <strong>CNA</strong> Operating System Image<br />
To establish a connection to the <strong>CNA</strong> using NetMeeting, follow these steps:<br />
1. Start NetMeeting from the remote Windows system. The NetMeeting - Not in a Call<br />
screen appears:<br />
2. Place a new call by clicking the telephone icon, or select Call on the menu bar and<br />
then click New Call on the drop-down menu. The Place A Call screen appears:<br />
Note:<br />
You can create a speed dial entry from the NetMeeting Call menu. Click Create Speed<br />
Dial in the Create Speed Dial dialog box and then enter the IP address in the Address<br />
box and where to call from in the Call using box. Then select the appropriate button to<br />
add this entry to a Speed Dial list or to save it on your desktop.<br />
3827 2928–001 2–5
Installing the <strong>CNA</strong> Operating System Image<br />
3. On this screen:<br />
a. Enter the IP address of the <strong>CNA</strong> in the To: box. Use the IP address configured<br />
at the factory or refer to Table 3-1 for the correct address. Note that the IP<br />
address for each <strong>CNA</strong> is also on the label on the back of the <strong>CNA</strong>.<br />
If this is an image installation, use the IP address on the boot floppy disk label<br />
(192.168.222.150).<br />
b. Select Require security for this call (data only) and click Call.<br />
4. From the Remote Desktop Sharing Password screen (shown earlier in this section),<br />
log onto the <strong>CNA</strong> by entering Administrator in the User and Password fields and<br />
clicking OK.<br />
The NT desktop of the <strong>CNA</strong> is displayed. You can now install the <strong>CNA</strong> operating<br />
system image.<br />
2–6 3827 2928–001
Installing the <strong>CNA</strong> Operating System Image<br />
Installing the <strong>CNA</strong> Operating System Image<br />
The working operating system image (Windows NT Embedded) is preinstalled on a new<br />
<strong>CNA</strong>. However, under certain problem conditions or for upgrades, you may need to<br />
reinstall the software. (See Section 7 for <strong>CNA</strong> troubleshooting procedures.)<br />
When reinstalling a new <strong>CNA</strong> operating system image or repairing a defective image,<br />
certain configuration settings can be lost. The following settings are automatically saved<br />
for you to the D drive (and, optionally, on a floppy) by the <strong>CNA</strong>cfg.exe utility:<br />
• User/password<br />
• IP address of the private (maintenance) LAN<br />
• The <strong>CNA</strong> computer name<br />
• Other LAN settings including Jumbo Frames configuration on Gigabit Ethernet<br />
appliances<br />
You should save these configuration settings on a floppy disk since the settings will be<br />
reset to their factory defaults once you have reloaded the operating system image.<br />
After saving these configuration settings, perform the installation steps in the next<br />
subsection to reinstall the operating system image. You will need the following media:<br />
• <strong>CNA</strong> Safe Boot floppy disk<br />
• <strong>CNA</strong> Images CD-ROM<br />
• ClearPath Network Services installation CD-ROM<br />
3827 2928–001 2–7
Installing the <strong>CNA</strong> Operating System Image<br />
Performing a <strong>CNA</strong> Safe Boot<br />
The first step in installing a working <strong>CNA</strong> image is to boot the system from the<br />
<strong>CNA</strong>_Safe image on the hard disk as follows:<br />
1. Insert the <strong>CNA</strong>_Safe Boot floppy disk. The boot disk contains a Boot.ini file that<br />
re-directs the boot process to the <strong>CNA</strong>_Safe directory on the hard disk.<br />
2. Power on or restart the <strong>CNA</strong>.<br />
The system boots from the <strong>CNA</strong>_Safe Image on the hard drive. There is no visual<br />
indication of boot completion—wait for all drive activity to finish (about 3 to 5<br />
minutes).<br />
3. If the boot is successful, start NetMeeting to establish the connection and log on to<br />
the <strong>CNA</strong> (see “Establishing a NetMeeting Connection to <strong>CNA</strong>” in Section 2 of this<br />
guide).<br />
Your Windows system must be attached to the private LAN and configured to<br />
connect to the reserved IP address (192.168.222.150) specified on the label of the<br />
boot floppy. This is always the address of the <strong>CNA</strong> when you boot from the hard<br />
disk. This means that you can only have one device booted from the <strong>CNA</strong>_Safe<br />
Image at a time. Otherwise, you would have duplicate IP addresses on the private<br />
LAN if you booted more than one <strong>CNA</strong> from the <strong>CNA</strong>_Safe directory on the hard<br />
disk. Under normal circumstances, you should not change this address.<br />
Note: Sometimes NetMeeting will not establish a session with the <strong>CNA</strong> even<br />
though a Ping of <strong>CNA</strong> is successful. You can usually resolve this by closing the<br />
NetMeeting window and restarting NetMeeting.<br />
4. When the Remote Desktop Sharing Password dialog box appears, enter<br />
Administrator in the User and Password boxes and click OK to log on to the <strong>CNA</strong>.<br />
2–8 3827 2928–001
Installing the <strong>CNA</strong> Image<br />
Installing the <strong>CNA</strong> Operating System Image<br />
On completion of the <strong>CNA</strong> safe boot, the <strong>CNA</strong> desktop screen appears. If you are<br />
not logged on to the <strong>CNA</strong>, the Workstation Locked message box appears on the<br />
desktop.<br />
Logging on to the <strong>CNA</strong><br />
1. On the Contol menu, click Send Ctrl+Alt+Del. The Unlock Workstation dialog<br />
box appears.<br />
2. Enter the usercode/password to log on to the <strong>CNA</strong> (Administrator), and then click<br />
OK.<br />
Installing the Image<br />
1. On the <strong>CNA</strong> desktop screen, double-click the Install_Primary icon to begin the <strong>CNA</strong><br />
Installer.<br />
The ClearPath Network Appliance Installer screen appears.<br />
2. Click Install to continue.<br />
A message box appears warning you that the installer will reformat the primary<br />
partition.<br />
3. Choose Yes. Choosing No returns you to the previous screen.<br />
A <strong>CNA</strong> Installation message box appears directing you to insert the <strong>CNA</strong> Installation<br />
CD-ROM in the <strong>CNA</strong> CD-ROM drive.<br />
Note: You will not see this message if the CD-ROM is already in the drive.<br />
3827 2928–001 2–9
Installing the <strong>CNA</strong> Operating System Image<br />
4. Insert the <strong>CNA</strong> CD-ROM and click OK.<br />
The following Windows NT Format disk screen (for drive C) appears:<br />
5. Do not change any entries. Select the Quick Format check box and click Start. A<br />
message is displayed warning you that all data on the C disk will be erased.<br />
6. Click OK to begin formatting the primary partition. A Format Complete dialog box<br />
appears when the formatting is complete.<br />
7. Click OK. The Format C:\ screen reappears.<br />
2–10 3827 2928–001
8. Click Close to return to the installer.<br />
The following Copying screen appears:<br />
Installing the <strong>CNA</strong> Operating System Image<br />
Setup.exe copies the appropriate source image from the <strong>CNA</strong> CD-ROM to the<br />
primary partition. The progress bar proceeds on a file-by-file basis. The process of<br />
copying the operating system image takes about 5 minutes.<br />
Note: The Install, Restart, and Cancel buttons on the <strong>CNA</strong> Installer window are<br />
hidden so that you cannot accidentally interrupt the loading process.<br />
If the file transfer is successful, a ClearPath Network Appliance Installer Finish<br />
screen appears telling you that the Installation is complete.<br />
9. Remove the floppy disk and CD-ROM from the drives as directed, and click Finish to<br />
restart the <strong>CNA</strong> system from the <strong>CNA</strong> hard disk. The desktop window of the target<br />
system closes automatically when the <strong>CNA</strong> reboots.<br />
10. Wait until the reboot finishes (the LED for the hard disk should stop flashing), and<br />
then reestablish a NetMeeting connection as described under “Establishing a<br />
NetMeeting Connection to <strong>CNA</strong>” using the address 192.168.222.150.<br />
The Remote Desktop Sharing Password box appears again.<br />
11. Log on to the <strong>CNA</strong> again using Administrator for the User and Password, and<br />
click OK.<br />
You are now ready to configure the system.<br />
3827 2928–001 2–11
Installing the <strong>CNA</strong> Operating System Image<br />
2–12 3827 2928–001
Section 3<br />
Configuring the <strong>CNA</strong><br />
This section describes how to<br />
• Configure a <strong>CNA</strong><br />
• Configure network adapters for IEEE 802.1Q VLANs or Port Aggregation<br />
Overview of <strong>CNA</strong> Configuration<br />
<strong>CNA</strong> is initially configured in the factory. The operating system image default<br />
configuration is the following:<br />
• Private LAN IP address = 192.168.222.150<br />
• Username/password = Administrator/Administrator<br />
• Computer name = <strong>CNA</strong><br />
Refer to Table 3-1 for IP addressing information for the <strong>CNA</strong> devices.<br />
Do You Need to Configure <strong>CNA</strong>?<br />
A configuration tool, <strong>CNA</strong>cfg.exe, is provided to enable you to configure <strong>CNA</strong> after<br />
installing a new image or to change the default values of the <strong>CNA</strong> private LAN IP<br />
address, password, and computer name. <strong>Unisys</strong> support personnel may also use the<br />
configuration tool to install a new <strong>CNA</strong>, add additional <strong>CNA</strong>s to an existing ClearPath<br />
server, or configure public NIC attributes. Each <strong>CNA</strong> needs to be configured as<br />
described in “Configuring <strong>CNA</strong>” later in this section.<br />
If you are installing a new image, the <strong>CNA</strong> Configuration dialog box is displayed<br />
immediately after you boot. Follow the instructions in “Configuring a <strong>CNA</strong>” later in this<br />
section.<br />
If you are not installing a new image, changing the default values, or adding new <strong>CNA</strong>s<br />
to an existing system, you can skip the configuration procedures in this section. Proceed<br />
to the next section, “Installing Network Services on the <strong>CNA</strong>.”<br />
3827 2928–001 3–1
Configuring the <strong>CNA</strong><br />
IP Addressing Information for <strong>CNA</strong> Devices<br />
<strong>CNA</strong><br />
Device<br />
ID<br />
Table 3-1 provides the IP addressing information for <strong>CNA</strong> devices. Refer to this table<br />
when you are configuring a <strong>CNA</strong> or installing Network Services software on a <strong>CNA</strong>.<br />
Note: The MCP public IP addresses in this table are examples only. You must<br />
configure these addresses in MCP TCP/IP initialization files using your public LAN<br />
addresses.<br />
NP<br />
ID<br />
Unit<br />
No.<br />
Private<br />
LAN<br />
IP Address<br />
<strong>CNA</strong>1 8001 192.168.222.151<br />
<strong>CNA</strong>2 8002 192.168.222.152<br />
<strong>CNA</strong>3 8003 192.168.222.153<br />
<strong>CNA</strong>4 8004 192.168.222.154<br />
<strong>CNA</strong>5 8005 192.168.222.155<br />
<strong>CNA</strong>6 8006 192.168.222.156<br />
<strong>CNA</strong>7 8007 192.168.222.157<br />
<strong>CNA</strong>8 8008 192.168.222.158<br />
<strong>CNA</strong>9 8009 192.168.222.159<br />
<strong>CNA</strong>10 8010 192.168.222.160<br />
<strong>CNA</strong>11 8011 192.168.222.161<br />
<strong>CNA</strong>12 8012 192.168.222.162<br />
Table 3–1. IP Addresses<br />
MCP Private<br />
LAN<br />
Address<br />
MCP <strong>Public</strong><br />
IP Addresses<br />
192.168.222.121 192.168.237.50<br />
192.168.237.51<br />
192.168.237.52<br />
192.168.237.53<br />
<strong>CNA</strong> EVLAN<br />
IP Address<br />
MCP EVLAN<br />
IP Address<br />
192.168.16.102 192.168.16.101<br />
192.168.222.122 192.168.237.54… 192.168.16.106 192.168.16.105<br />
192.168.222.123 192.168.237.58… 192.168.16.110 192.168.16.109<br />
192.168.222.124 192.168.237.62… 192.168.16.114 192.168.16.113<br />
192.168.222.125 192.168.237.66… 192.168.16.118 192.168.16.117<br />
192.168.222.126 192.168.237.70… 192.168.16.122 192.168.16.121<br />
192.168.222.127 192.168.237.74… 192.168.16.126 192.168.16.125<br />
192.168.222.128 192.168.237.78… 192.168.16.130 192.168.16.129<br />
192.168.222.129 192.168.237.82… 192.168.16.134 192.168.16.133<br />
192.168.222.130 192.168.237.86… 192.168.16.138 192.168.16.137<br />
192.168.222.131 192.168.237.90… 192.168.16.142 192.168.16.141<br />
192.168.222.132 192.168.237.94… 192.168.16.146 192.168.16.145<br />
3–2 3827 2928–001
<strong>CNA</strong><br />
Device<br />
ID<br />
NP<br />
ID<br />
Unit<br />
No.<br />
Private<br />
LAN<br />
IP Address<br />
<strong>CNA</strong>13 8013 192.168.222.163<br />
<strong>CNA</strong>14 8014 192.168.222.164<br />
<strong>CNA</strong>15 8015 192.168.222.165<br />
<strong>CNA</strong>16 8016 192.168.222.166<br />
<strong>CNA</strong>17 8017 192.168.222.167<br />
<strong>CNA</strong>18 8018 192.168.222.168<br />
<strong>CNA</strong>19 8019 192.168.222.169<br />
<strong>CNA</strong>20 8020 192.168.222.170<br />
<strong>CNA</strong>21 8021 192.168.222.171<br />
<strong>CNA</strong>22 8022 192.168.222.172<br />
<strong>CNA</strong>23 8023 192.168.222.173<br />
<strong>CNA</strong>24 8024 192.168.222.174<br />
Table 3–1. IP Addresses<br />
MCP Private<br />
LAN<br />
Address<br />
MCP <strong>Public</strong><br />
IP Addresses<br />
Configuring the <strong>CNA</strong><br />
<strong>CNA</strong> EVLAN<br />
IP Address<br />
MCP EVLAN<br />
IP Address<br />
192.168.222.133 192.168.237.98… 192.168.16.150 192.168.16.149<br />
192.168.222.134 192.168.237.102… 192.168.16.154 192.168.16.153<br />
192.168.222.135 192.168.237.106… 192.168.16.158 192.168.16.157<br />
192.168.222.136 192.168.237.110… 192.168.16.162 192.168.16.161<br />
192.168.222.137 192.168.237.114… 192.168.16.166 192.168.16.165<br />
192.168.222.138 192.168.237.118… 192.168.16.170 192.168.16.169<br />
192.168.222.139 192.168.237.122… 192.168.16.174 192.168.16.173<br />
192.168.222.140 192.168.237.126… 192.168.16.178 192.168.16.177<br />
192.168.222.141 192.168.237.130… 192.168.16.182 192.168.16.181<br />
192.168.222.142 192.168.237.134… 192.168.16.186 192.168.16.185<br />
192.168.222.143 192.168.237.138… 192.168.16.190 192.168.16.189<br />
192.168.222.144 192.168.237.142<br />
192.168.237.143<br />
192.168.237.144<br />
192.168.237.145<br />
192.168.16.194 192.168.16.193<br />
3827 2928–001 3–3
Configuring the <strong>CNA</strong><br />
Configuring a <strong>CNA</strong><br />
If you have just completed installing the <strong>CNA</strong> operating system image, the <strong>CNA</strong><br />
configuration tool, <strong>CNA</strong>cfg.exe, starts automatically. This only occurs after the first time<br />
you boot the <strong>CNA</strong>.<br />
If you are not logged on to the <strong>CNA</strong>, the Workstation Locked message box appears. Do<br />
the following:<br />
1. Select Control on the toolbar.<br />
2. Click Send Ctrl+Alt+Del and click the mouse button. The Unlock Workstation dialog<br />
box appears.<br />
3. Enter the Usercode/Password (Administrator), and then click OK.<br />
To start the <strong>CNA</strong> configuration tool, do the following:<br />
1. Double-click the configuration tool icon, <strong>CNA</strong>cfg.exe. The <strong>CNA</strong> Configuration dialog<br />
box appears.<br />
If the <strong>CNA</strong> server device number is not present, a value of “0” appears in the <strong>CNA</strong><br />
Server Device Number box.<br />
2. Enter the correct value for the <strong>CNA</strong> server device number (in this example, 4 was<br />
entered).<br />
<strong>CNA</strong>cfg.exe attempts to determine the name of the private LAN network interface<br />
card. If the name is not correct, select the correct name from the drop-down list and<br />
click Next.<br />
3–4 3827 2928–001
The following screen appears:<br />
Configuring the <strong>CNA</strong><br />
If this is a new installation (as we are assuming in this procedure), the <strong>CNA</strong>cfg4.ini<br />
file does not exist.<br />
3. Click Next to continue. Note that you can also enter a path or click Browse.<br />
• You can browse to the location of the <strong>CNA</strong>cfg.ini files and read the <strong>CNA</strong>cfgx.ini<br />
file to recover your previous settings (x is the <strong>CNA</strong> device number).<br />
• If this is an operating system image re-installation on a device you used<br />
previously, the <strong>CNA</strong>cfgx.ini file is stored on hard disk (D:\Cnacfg\<strong>CNA</strong>cfgx).<br />
3827 2928–001 3–5
Configuring the <strong>CNA</strong><br />
4. The next screen that appears is used to either display or enter the private LAN IP<br />
address. The address range is from 192.168.222.151 through 192.168.222.174.<br />
• In this example, the device number for the <strong>CNA</strong> you are installing is 4. The<br />
private IP address is 192.168.222.154, as shown on the screen.<br />
Table 3-1 contains a complete list of default values.<br />
• Click Next to continue.<br />
Note: If this is a new private LAN IP address, we recommend that you change the<br />
IP address sticker on the back of the box. IP address stickers are included in the<br />
<strong>CNA</strong> “overpack box.”<br />
3–6 3827 2928–001
Configuring the <strong>CNA</strong><br />
5. The next screen is used to fill in the Computer Name of the <strong>CNA</strong>. The Computer<br />
Name is listed under the <strong>CNA</strong> Device ID column in Table 3-1.<br />
Enter a value (in this example, <strong>CNA</strong>4) and click Next.<br />
The following change password screen appears:<br />
3827 2928–001 3–7
Configuring the <strong>CNA</strong><br />
6. Follow the instructions on the screen to enter your new password. Click Next.<br />
If you are using a <strong>CNA</strong>cfgx.ini file, the new password will not be filled in from the<br />
file. To restore your old password manually, read the <strong>CNA</strong>cfg.ini file and enter the<br />
password using the previous screen. Otherwise, enter a new password to replace<br />
the default.<br />
If you do not type an entry for a new password, the existing password will not be<br />
changed. The password must be a non-empty string for the Appliance Crash Dump<br />
facility to operate correctly.<br />
Notes:<br />
• This screen is the only tool that should be used to change the password for<br />
the Administrator. The <strong>CNA</strong> configuration tool makes changes to the two<br />
places where the password must be changed. If you change the password<br />
through Windows User Manager, you will be unable to log on to the <strong>CNA</strong>.<br />
The only way to recover the <strong>CNA</strong> in this case is to reinstall the operating<br />
system image.<br />
• The <strong>CNA</strong> recovery disk contains the password for the <strong>CNA</strong>, which is<br />
sensitive data. Keep the disk in a safe place.<br />
If your <strong>CNA</strong> system contains Gigabit Ethernet network interface cards (NICs), the<br />
following screen appears:<br />
3–8 3827 2928–001
Configuring the <strong>CNA</strong><br />
7. If you have network interface cards (NICs) that support Ethernet Jumbo Frames,<br />
select the desired frame size and click Next. For more information, see “Preparing<br />
to Use Ethernet Jumbo Frames” later in this section.<br />
8. The following Date/Time Properties screen appears. Enter the correct date and time<br />
and click OK.<br />
3827 2928–001 3–9
Configuring the <strong>CNA</strong><br />
9. The following <strong>CNA</strong> Configuration summary screen is displayed enabling you to go<br />
back and reenter any values you want to change.<br />
Note: The <strong>CNA</strong> Configuration summary screen also requests a location in which to<br />
save the .ini file, which may be on the <strong>CNA</strong> boot floppy disk or any other floppy disk.<br />
10. On the <strong>CNA</strong> Configuration summary screen, enter a path or browse to the save<br />
location and Click Next.<br />
The configuration data obtained from step 4 is written to a text file called<br />
<strong>CNA</strong>cfgx.ini (where x is the <strong>CNA</strong> device number). A second copy is always written to<br />
the D:\<strong>CNA</strong>CFG\<strong>CNA</strong>cfgx.ini file on the hard drive.<br />
You can use this file later to supply the defaults in case you need to replace the disk<br />
image.<br />
3–10 3827 2928–001
The following screen is displayed.<br />
Configuring the <strong>CNA</strong><br />
11. Click Finish. If the only data you changed is the administrative password, the<br />
program exits immediately. Otherwise, the program prompts you to reboot the<br />
system to activate the new information.<br />
If you changed the <strong>CNA</strong> device number, the dialog asks you to install or re-install the<br />
NNS (Network Services) software. Insert the NNS disk, click Finish, and proceed to<br />
install Network Services as described in Section 4, “Installing Network Services<br />
Software on the <strong>CNA</strong>.” Reboot the system when the Network Services installation<br />
finishes.<br />
3827 2928–001 3–11
Configuring the <strong>CNA</strong><br />
Configuring Shared Adapter Features<br />
The following subsections describe general guidelines you should observe when<br />
preparing to use the following shared adapter options:<br />
• Port Aggregation<br />
• Ethernet Jumbo Frames<br />
• IEEE 802.1Q VLANs<br />
Ethernet Jumbo Frames are configured on the <strong>CNA</strong> by using the <strong>CNA</strong> configuration<br />
wizard (see “Configuring <strong>CNA</strong>”).<br />
See “Configuring IEEE 802.1Q VLANs or Port Aggregation” later in this section for<br />
procedures to configure 802.1Q VLANs or Port Aggregation.<br />
Preparing to Use Port Aggregation<br />
Network Services Shared Adapter software supports port aggregation, an optional<br />
feature offered on Fast Ethernet and Gigabit Ethernet adapters. Port aggregation<br />
increases the effective network throughput by distributing Fast Ethernet traffic across<br />
multiple adapters. System and user programs “see” a single virtual port capable of<br />
operating at some factor in excess of 100 Mbps.<br />
Port Aggregation can only be used when <strong>CNA</strong> is connected to a switch or router which<br />
supports Port Aggregation and is configured for it.<br />
Use the Port Aggregation software (as described in the Intel adapter documentation)<br />
before running Network Services Setup to share the virtual Port Aggregation adapter<br />
created. Setup will offer this virtual adapter to be selected as a shared adapter. The<br />
physical adapters assigned to the port aggregation may also appear in the list offered by<br />
Setup for shared adapter selection and should not be chosen.<br />
If you have Fast Ethernet or Gigabit Ethernet adapters already configured as shared<br />
adapters that you intend to use in Port Aggregation, you must first run the Network<br />
Services Setup program to “un-share” these adapters (that is, disable MCP access).<br />
Also, if you have configured a Port Aggregation adapter as a shared adapter and you<br />
intend to remove the port aggregation, you must first run Network Services Setup to unshare<br />
the Port Aggregation adapter.<br />
For further information on configuring Port Aggregation, see “Configuring IEEE 802.1Q<br />
VLANs or Port Aggregation” later in this section.<br />
3–12 3827 2928–001
Preparing to Use Ethernet Jumbo Frames<br />
Configuring the <strong>CNA</strong><br />
In some applications, Jumbo Frames improve server throughput and reduce the CPU<br />
cycles used for networking. This improvement is achieved by reducing the number of<br />
frames an application must process. This is particularly true for applications that use<br />
large message sizes such as file transfers.<br />
Jumbo Frames can only be used if the remote system and the connecting network<br />
equipment (switches, routers) also support Jumbo Frames. Jumbo Frames are not<br />
supported on Fast Ethernet NICs.<br />
You can use Jumbo Frames with TCP/IP, Heritage Network Services (BNA), and BNA<br />
over IP (BIP). In addition to the application message size, the performance benefits vary<br />
depending on which of these protocols you are using. The performance gains are<br />
particularly significant with BNA and BIP. With TCP/IP, these gains are less pronounced<br />
or null (depending on the direction). This is due to TCP/IP Offload, which moves<br />
processing cycles from the MCP to the Windows environment.<br />
Jumbo Frames are supported over <strong>CNA</strong> Gigabit Ethernet connections. Note that you<br />
must configure Jumbo Frames on both the <strong>CNA</strong> and the MCP.<br />
On the <strong>CNA</strong>, use <strong>CNA</strong>cfg to select the Jumbo Frames option (see step 7 of “Configuring<br />
<strong>CNA</strong>” earlier in this section).<br />
On the MCP side, set the following attributes to desired values for applicable lines<br />
(connection groups) and devices (connections):<br />
• Max Input Message Size (MIMS)<br />
• Max Output Message Size (MOMS)<br />
• Max Input Message Size Limit (MIMSL)<br />
• Max Output Message Size Limit (MOMSL)<br />
The recommended frame size for Jumbo Frames is 9014, including the MAC header, but<br />
excluding the Cyclic Redundancy Check (CRC). Configure this value in the NIC driver,<br />
and translate it to the following MIMS/MOMS/MIMSL/MOMSL values:<br />
• 9000 for the connection group<br />
• 9000 or 8996 for TCP/IP and Heritage Network Services/BIP connections,<br />
respectively<br />
Communications between a jumbo-capable and a jumbo-incapable end system is<br />
generally not a problem. A common frame size is negotiated between the systems<br />
when they establish a dialog. This applies to TCP/IP, Heritage Network Services (BNA),<br />
and BIP protocols. It is not true for connectionless protocols such as UDP and ICMP,<br />
since they are datagram-based and do not negotiate a connection.<br />
If no router is in the path, each system transmits frames sized up to the system MTU<br />
value. Any frames larger than 1,500 bytes are dropped if they are not supported by the<br />
receiver. The only potential issue occurs with the ICMP protocol—“pings” that are<br />
larger than 1,500 bytes will fail.<br />
A useful technique in mixed networks is to logically segregate jumbo frame traffic from<br />
standard traffic by using IEEE 802.1Q Virtual LANS (VLANS).<br />
3827 2928–001 3–13
Configuring the <strong>CNA</strong><br />
Preparing to Use IEEE 802.1Q VLANS<br />
IEEE 802.1Q VLANs add a 4-byte tag to the packet header, identifying the VLAN for that<br />
packet. If the ClearPath server is a member of only one VLAN on a given adapter port,<br />
tagging is not necessary on that port. The VLAN is configured at the LAN switch port<br />
only. No VLAN should be configured on the ClearPath server.<br />
If the ClearPath server is to be a member of multiple VLANs over the same adapter port,<br />
then both the LAN switch and the ClearPath server must be configured. The switch<br />
connected to the ClearPath system must support IEEE 802.1Q tagging.<br />
• At the switch, tagging should be enabled, and all VLAN ID assignments made at the<br />
specific port. Follow any other vendor-specific instructions.<br />
• On the ClearPath server, VLAN IDs are assigned using the Windows Driver utility<br />
(Intel ProSet II). The VLAN IDs assigned to the NIC should match those assigned to<br />
the switch ports to which the NIC is connected.<br />
• For each VLAN defined, Windows creates a new “adapter” and assigns it a new<br />
adapter number.<br />
• At the ClearPath operator interface, a connection group must be defined for each<br />
VLAN.<br />
The following are additional rules and notes for configuring VLANs on a ClearPath server:<br />
• Assign the VLANs to the switch ports first.<br />
• Before assigning VLANs to the NIC card, run NNS setup to unshare the physical<br />
adapter.<br />
• DHCP will be enabled when VLAN is assigned; assign a fixed IP address for each<br />
VLAN adapter as required (this address is not used once the adapter is assigned to<br />
the MCP for its use).<br />
• Save your configuration settings as described in “Saving Your Settings” later in this<br />
section.<br />
• Each VLAN added will appear in the list of adapters that NNS can share.<br />
• Rerun NNS setup to share the virtual adapters.<br />
3–14 3827 2928–001
Configuring IEEE 802.1Q VLANs or Port<br />
Aggregation<br />
Configuring the <strong>CNA</strong><br />
Configure IEEE 802.1Q VLANs and Adapter Teaming (Intel’s feature that includes Port<br />
Aggregation) through the Intel PROSet II utility in Control Panel.<br />
Adapter Fault Tolerance (AFT) teams are used for resiliency at the NIC level. Fast<br />
EtherChannel/Link Aggregation is used to provide additional bandwidth beyond that<br />
available with a single adapter. Fast EtherChannel/Link Aggregation can be used to<br />
provide resiliency at the NIC level as well, when used with network switches that<br />
support this function.<br />
Creating a Team<br />
To configure adapters as part of a team<br />
1. Click Action.<br />
2. Select Add to Team.<br />
3. Click Create New Team.<br />
3827 2928–001 3–15
Configuring the <strong>CNA</strong><br />
4. Follow the Teaming Wizard through the selection of adapters to add to the team.<br />
Note that the Adapter labels in the above screen show Line # n, where n is a number<br />
from 1 to 4. The Line # n description indicates which NIC in the <strong>CNA</strong> device is being<br />
selected. The Line # n description matches the LINE 1 2 3 4 label under the PCI<br />
slots on the back of your <strong>CNA</strong> device. Do not include the adapter labeled “<strong>CNA</strong><br />
Management Adapter do NOT change settings” in any adapter teams.<br />
3–16 3827 2928–001
Configuring IEEE 802.1Q VLANs<br />
To configure IEEE 802.1Q VLANs<br />
1. Click Action and select Add VLAN.<br />
2. Enter the VLAN number and a name for that VLAN.<br />
Configuring the <strong>CNA</strong><br />
VLANs can be assigned on individual NICs and on adapter teams. It is extremely<br />
rare that you would need to configure 802.1Q VLANS on the adapter labeled “<strong>CNA</strong><br />
Management Adapter do NOT change settings.” <strong>Unisys</strong> recommends that you do<br />
not configure 802.1Q VLANs on this adapter.<br />
3827 2928–001 3–17
Configuring the <strong>CNA</strong><br />
Saving Your Settings<br />
Your settings are saved in PROSet when you click OK. <strong>Unisys</strong> recommends that you<br />
save your settings as follows:<br />
1. Click Tools.<br />
2. Click Save/Restore Configuration.<br />
3. Click OK. The PROSet Save/Restore box appears.<br />
3–18 3827 2928–001
Configuring the <strong>CNA</strong><br />
4. Click Save and point the utility to a floppy disk that you will use to store this<br />
configuration information. This enables you to store your adapter configuration on<br />
removable media so that it can be restored in the future if you reinstall the <strong>CNA</strong><br />
image or if you need to replace the <strong>CNA</strong> device.<br />
When you click OK on the main PROSet II screen, the Network Control Panel is<br />
initiated to recalculate the networking bindings for your devices. Depending on the<br />
features you selected, you may be prompted to configure new IP addresses for<br />
those devices.<br />
3827 2928–001 3–19
Configuring the <strong>CNA</strong><br />
5. Enter an IP address as shown in the following screen, even though you will not be<br />
using this adapter team for Windows TCP/IP access. The address must be entered<br />
for the adapter to be created properly. Network Services Setup breaks the binding<br />
between Windows TCP/IP and the new adapter when you assign the adapter for the<br />
MCP access. You can reboot when prompted to do so.<br />
3–20 3827 2928–001
Restoring Your Settings<br />
Configuring the <strong>CNA</strong><br />
To restore your settings in PROSet, use Control Panel to start the PROSet II applet:<br />
1. Click Tools.<br />
2. Click Save/Restore Configuration.<br />
3. Click Restore.<br />
4. Enter the path to your floppy disk containing the configuration of this device, and<br />
select the configuration file.<br />
5. Once the configuration is restored, click OK on the main PROSet II screen.<br />
The Network Control Panel is initiated to recalculate the networking bindings for your<br />
devices. You may be prompted to configure new IP addresses for those devices.<br />
Enter an IP address, even though you will not be using this adapter team for<br />
Windows TCP/IP access. The address must be entered for the adapter to be created<br />
properly. Network Services Setup breaks the binding between Windows TCP/IP and<br />
the new adapter when you assign the adapter for the MCP access. You can reboot<br />
when prompted to do so.<br />
3827 2928–001 3–21
Configuring the <strong>CNA</strong><br />
Assigning the Advanced Features Adapter to the MCP<br />
Proceed to Section 4, “Installing Network Services Software on the <strong>CNA</strong>.” If you have<br />
configured advanced networking features on the <strong>CNA</strong> device, you must select the<br />
adapters for MCP use manually.<br />
Note that all of the adapters in the <strong>CNA</strong> device are listed on the Select Adapter Cards<br />
for MCP Server Access screen. If you have configured an adapter in a team or if you<br />
have configured 802.1Q VLANs on an adapter, do not select the base adapter for MCP<br />
Server Access. Selecting both the base adapter and the Intel Advanced Network<br />
Services adapter for MCP Server Access may lead to unexpected results once the<br />
system starts networking.<br />
3–22 3827 2928–001
Section 4<br />
Installing Network Services Software<br />
on the <strong>CNA</strong><br />
This section provides the information required to install Network Services software on<br />
the ClearPath Network Appliance (<strong>CNA</strong>).<br />
If this is a new system installation and the <strong>CNA</strong>s were installed at the factory, Network<br />
Services should also have been installed at the factory. Proceed to “Bringing a <strong>CNA</strong> into<br />
Service” at the end of this section.<br />
If you are installing a new <strong>CNA</strong> on an existing MCP server, or adding additional <strong>CNA</strong>s to<br />
an existing server, you must install the Network Services software from the Network<br />
Services CD-ROM.<br />
You can upgrade Network Services software on a <strong>CNA</strong> from a remote ClearPath system<br />
by using the REMOTEINSTALL command. Note that the ClearPath system must be<br />
connected to the <strong>CNA</strong> device through Network Services. For details on using the<br />
REMOTEINSTALL command, see the Network Services <strong>Implementation</strong> <strong>Guide</strong>.<br />
Preparing to Install Network Services<br />
You can install Network Services on the <strong>CNA</strong> the same way as on other platforms. You<br />
can do either of the following:<br />
• Place the Network Services CD-ROM media in the CD-ROM drive and run SETUP by<br />
clicking Start and Run.<br />
• Map a network drive to the INSTALLS share on the MCP server (this assumes that<br />
Network Services is installed on the MCP server).<br />
You must execute Network Services Setup through a NetMeeting session. (See<br />
“Establishing a NetMeeting Connection to <strong>CNA</strong>” in Section 2 for instructions on using<br />
NetMeeting.)<br />
The Network Services Installation procedure requests information about the Network<br />
Services configuration. Table 3-1 lists the preconfigured values for each component that<br />
you need for the installation.<br />
3827 2928–001 4–1
Installing Network Services Software on the <strong>CNA</strong><br />
Network Services Installation Procedure<br />
If this is an upgrade or reconfiguration reinstall, perform the following steps to install<br />
Network Services on the <strong>CNA</strong>. If this is a “first time” install following a reload of the<br />
operating system, steps 1 through 5 should have already been done.<br />
1. Log on to a Windows server as Administrator.<br />
2. Run NetMeeting to attach to the <strong>CNA</strong>. You must select Require Security For This<br />
Call if you did not previously default Outgoing Calls to be secure as explained in<br />
“Establishing a NetMeeting Connection to <strong>CNA</strong>” in Section 2.<br />
The following Remote Desktop Sharing Password screen appears.<br />
3. Enter Administrator (or whichever values you have established if this is not an<br />
initial installation) in the User and the Password boxes and click OK.<br />
4–2 3827 2928–001
Installing Network Services Software on the <strong>CNA</strong><br />
When you enter the user and password, you are connected to the <strong>CNA</strong> and the<br />
Workstation Locked message screen may appear on the desktop:<br />
Caution<br />
Once the connection is established, the message “Press Ctrl+Alt+Del to<br />
unlock this workstation” is displayed. Do not press Ctrl-Alt-Del since this<br />
key sequence is interpreted by your local PC. Continue with the following<br />
instructions instead.<br />
4. From the Control Menu, click Send Ctrl+Alt+Del.<br />
The Unlock Workstation screen appears.<br />
5. Enter Administrator as the password (or the password value you have established<br />
if this is not an initial installation) and press Enter or click OK.<br />
The <strong>CNA</strong> desktop screen appears (not shown here).<br />
3827 2928–001 4–3
Installing Network Services Software on the <strong>CNA</strong><br />
6. Insert the release media Network Services Installation CD-ROM in the <strong>CNA</strong> CD-<br />
ROM drive. Click Start and Run to start the Setup.exe program.<br />
The Network Services splash screen appears with the Setup startup meter running<br />
as the InstallShield Wizard is initialized.<br />
7. The Welcome screen (not shown) appears, showing the version of Network Services<br />
you are installing. Click Next.<br />
8. The View Readme File screen appears (not shown), giving you the option of viewing<br />
the Readme text file from the Network Services CD-ROM. This file contains any<br />
last-minute changes and information about Network Services that did not make it<br />
into the printed documentation. Always review this information for each release<br />
level. Click Next.<br />
The Choose Destination Location screen appears.<br />
4–4 3827 2928–001
9. Accept the default destination folder and click Next.<br />
Installing Network Services Software on the <strong>CNA</strong><br />
The Start Copying Files screen appears showing the settings that the setup utility<br />
has determined or received from the user. Note that the platform type is <strong>CNA</strong>.<br />
3827 2928–001 4–5
Installing Network Services Software on the <strong>CNA</strong><br />
10. Click Next.<br />
The Setup program copies the Network Services software to the <strong>CNA</strong> hard disk and<br />
then installs the necessary service and driver files.<br />
The Configuration of Shared Adapter Cards screen appears.<br />
Your entry on this screen depends on whether you have configured advanced<br />
networking features such as IEEE 802.1Q VLANs or Adapter Teaming (Port<br />
Aggregation).<br />
11. Do one of the following:<br />
• If you have not configured these features, accept the default selection of Keep<br />
the current selection of Shared Adapters and click Next. Setup uses the default<br />
adapter selections for the <strong>CNA</strong> and displays them in the Review Shared Adapter<br />
Card Selections screen. Skip to step 15.<br />
• If you have configured advanced networking features as described in<br />
“Configuring IEEE 802.1Q VLANs or Port Aggregation” in Section 3, click Yes to<br />
Proceed to update selection of Shared Adapters and click Next. The Select<br />
Adapter Cards for MCP Server Access screen is displayed:<br />
4–6 3827 2928–001
12. Select each check box and click Properties.<br />
The Adapter Properties screen appears.<br />
Installing Network Services Software on the <strong>CNA</strong><br />
3827 2928–001 4–7
Installing Network Services Software on the <strong>CNA</strong><br />
13. Enter the CNS Line ID for each adapter and click OK. Note that if you do not accept<br />
the defaults in step 11, you will have to determine which adapter goes with which<br />
line.<br />
The Select Adapter Cards for MCP Server Access screen appears again.<br />
14. Once you have assigned the CNS Line ID for all three adapters, click Next.<br />
4–8 3827 2928–001
Installing Network Services Software on the <strong>CNA</strong><br />
When you have selected the adapter cards that will be used by the MCP, the<br />
following screen displays a summary of your shared adapter choices and allows you<br />
to go back to make appropriate changes. You should see all the Intel Pro adapters<br />
listed in the Exclusive use by MCP Server for network connections section.<br />
Note: To ensure the security of the <strong>CNA</strong>, adapters on the public LAN cannot be<br />
shared between the MCP and Windows in the <strong>CNA</strong>. The LAN on the motherboard<br />
attached to the private LAN will be shared between the MCP and Windows on the<br />
<strong>CNA</strong> for use by the MCP Call Home facility. This is selected automatically.<br />
15. Click Next.<br />
3827 2928–001 4–9
Installing Network Services Software on the <strong>CNA</strong><br />
The Specify Windows Server Environment screen appears.<br />
The Server box is prefilled with the <strong>CNA</strong> device server number that you provided<br />
earlier, unless you have changed it. The value provided in this box is used to<br />
determine the values for the NP ID unit number and for the VLAN IP address of the<br />
<strong>CNA</strong>.<br />
16. Click Next.<br />
4–10 3827 2928–001
The Network Services Properties screen appears.<br />
Installing Network Services Software on the <strong>CNA</strong><br />
The NP Unit Number box is prefilled with the value from Table 3-1.<br />
17. This value is the NP unit number that Network Services reports for the <strong>CNA</strong>. It does<br />
not have to match the channel number, but the convention for <strong>CNA</strong> devices is to<br />
make the channel/port number match the NP unit number.<br />
Click Next to accept the value or enter another value in the box and then click Next.<br />
3827 2928–001 4–11
Installing Network Services Software on the <strong>CNA</strong><br />
The Choose Configuration Options screen appears.<br />
18. In almost all cases, accept the default values (selected).<br />
Click Next.<br />
Note: If you want to change the VLAN IP addresses for the MCP and/or the <strong>CNA</strong>,<br />
clear the Assume default IP Addresses for Network Services check box and click<br />
Next.<br />
4–12 3827 2928–001
The MCP Host Name screen appears.<br />
19. Fill in the name of your MCP host and click Next.<br />
Installing Network Services Software on the <strong>CNA</strong><br />
Note: This is the only field that does not contain a default value during the initial<br />
installation of Network Services on a <strong>CNA</strong>. The value shown here is used to force<br />
the <strong>CNA</strong> to use the VLAN path to communicate with the MCP.<br />
3827 2928–001 4–13
Installing Network Services Software on the <strong>CNA</strong><br />
The Review Configuration Option Selections screen appears.<br />
20. Review all your configuration options. If OK, click Next.<br />
4–14 3827 2928–001
Installing Network Services Software on the <strong>CNA</strong><br />
The Setup program starts the Network applet (to automatically complete the<br />
configuration of Network Services), waits for it to terminate, and then displays the<br />
Setup Complete screen.<br />
21. Remove the installation CD at this time. Select Yes, I want to restart my computer<br />
now and click Finish.<br />
Your NetMeeting session will terminate. Reestablish NetMeeting using the IP<br />
address for your <strong>CNA</strong> device. It will take about three minutes to reestablish the<br />
session.<br />
Proceed to Section 5, “Installing ODT and IOP Files.”<br />
3827 2928–001 4–15
Installing Network Services Software on the <strong>CNA</strong><br />
4–16 3827 2928–001
Section 5<br />
Installing ODT and NT-IOP Software<br />
This section explains how to install the following files from the I/O Firmware CD-ROM<br />
(referred to as the IOCD) to the ClearPath Network Appliance (<strong>CNA</strong>).<br />
• Operator display terminal (ODT) software – the ODT software that enables a PC<br />
connected to the <strong>CNA</strong> private LAN to emulate an MCP ODT<br />
• NT-IOP software – the software files installed on the <strong>CNA</strong> that provide ODT<br />
connectivity for the ClearPath system<br />
If you are installing a <strong>CNA</strong> on an existing ClearPath system, you must install the Network<br />
Services software as described in Section 4 of this guide before installing the ODT<br />
software. You should install the contents of the IOCD on your <strong>CNA</strong> devices immediately<br />
after installing the Network Services software.<br />
If this is a new system installation and the <strong>CNA</strong> devices were installed at the factory, the<br />
IOCD software should also have been installed at the factory.<br />
Installing ODT and IOP Files<br />
1. Check the status of the <strong>CNA</strong> and the ODT by entering the following:<br />
OL PORT <br />
2. Reserve the <strong>CNA</strong> by entering the following:<br />
UR PORT <br />
Accept any Waiting Entry messages associated with the device.<br />
3. If the NT-IOP is defined in the partition profile of the MCP, save it by entering the<br />
following:<br />
SV IOP <br />
Accept any Waiting Entry messages associated with the device.<br />
4. Establish a NetMeeting session to the <strong>CNA</strong> unit. Refer to “Establishing a<br />
NetMeeting Connection to <strong>CNA</strong>” in Section 2.<br />
5. If you are updating NT-IOP software, reboot the <strong>CNA</strong> unit; otherwise, go to step 7.<br />
6. If you rebooted in step 5, reestablish a NetMeeting session to the <strong>CNA</strong> unit.<br />
7. Insert the IOCD in the <strong>CNA</strong>.<br />
3827 2928–001 5–1
Installing ODT and NT-IOP Software<br />
8. Run Setup.exe on the CD-ROM by doing one of the following:<br />
• From Windows Explorer, navigate to the Installer folder and double-click<br />
Setup.exe.<br />
• On the Run screen, enter F:\Installer\Setup.exe as shown on the following<br />
screen and click OK (assuming F: is the drive letter for your CD drive).<br />
9. When the Welcome screen appears, click Next.<br />
10. The Installation Options screen is displayed. On this screen, the NT-IOP /ODT and<br />
the FC-IOP firmware boxes are both checked by default if the <strong>CNA</strong> device is number<br />
1, 2, 3, or 4. The FC-IOP firmware box is checked by default for all other <strong>CNA</strong><br />
devices. If the ODT installation is required for <strong>CNA</strong> devices of any other number, the<br />
NT-IOP/ODT box must be checked manually. On this screen:<br />
• If you are installing code on <strong>CNA</strong>1, <strong>CNA</strong>2, <strong>CNA</strong>3, and <strong>CNA</strong>4, select both<br />
boxes (the NT-IOP and ODT software and the FC-IOP firmware boxes).<br />
• If ODT functionality is required for other <strong>CNA</strong>s, select the NT-IOP and ODT<br />
software box only.<br />
11. Click Next. The Installer begins to copy files to the <strong>CNA</strong>. If there is a version level<br />
mismatch between the Network Services code and the ODT software, an error<br />
message appears.<br />
12. When the installation is complete, click Finish on the Setup Complete screen.<br />
5–2 3827 2928–001
Installing Web Enabler<br />
Installing ODT and NT-IOP Software<br />
You must install and configure Web Enabler on the PC that is being used as the ODT for<br />
the MCP. The PC being used as the ODT must have a LAN card installed and be<br />
connected to the private LAN in the <strong>CNA</strong>.<br />
Perform the following steps to install Web Enabler:<br />
1. Install the IOCD in the PC to be used for ODT capabilities, and navigate to the<br />
:\Installer\Web Enabler folder. Select the appropriate Web Enabler<br />
version to install:<br />
• If you are running MCP 8.0, double-click Install80.exe<br />
There will be several more screen prompts. Read and follow the prompts until the<br />
Choose Java Virtual Machine screen appears.<br />
2. From the Choose Java Virtual Machine screen, select Install Sun Java VM specifically<br />
for this Application and click Next.<br />
Note: Different Java VMs support different print drivers.<br />
3. From the Choose Install Set screen, select Full Install and click Install.<br />
Web Enabler will install on the PC; wait until you see the Install Complete screen.<br />
4. From the Install Complete screen, click Done.<br />
3827 2928–001 5–3
Installing ODT and NT-IOP Software<br />
Configuring a <strong>CNA</strong> for ODT Mode<br />
Perform the following steps to configure Web Enabler :<br />
1. From the Desktop, bring up Web Enabler by doing the following:<br />
a. Click Start.<br />
b. Choose Programs.<br />
c. Choose Web Enabler for ClearPath MCP.<br />
d. Click Web Enabler.<br />
2. On the Web Enabler for ClearPath MCP screen:<br />
a. Select File.<br />
b. From the File menu, select Properties.<br />
c. From the Properties screen, select the Advanced tab.<br />
3. From the Advanced tab, perform the following steps to enable the ODT feature:<br />
a. Verify that the following are selected:<br />
• Attempt to connect at startup<br />
• Disconnect on log off<br />
• Attempt to Reconnect when Disconnected<br />
b. Scroll down to Server Name and enter the Private LAN IP address of the <strong>CNA</strong><br />
that is going to provide the ODT feature.<br />
For example, Server Name: 192.168.222.151 if <strong>CNA</strong>1 is being configured<br />
to provide ODT capabilities.<br />
Note: The IP addresses can be found in Table 3-1.<br />
c. Scroll down to Socket Number and verify that its default value equals 3001.<br />
• Socket numbers are assigned by adding the Single Line Control (SC) Logical<br />
Unit Number (LUN) to 3001. For example, if the SC LUN number for an ODT<br />
is zero (0), then its socket number would be 3001.<br />
Note: This numbering convention continues for all SCs defined.<br />
d. Scroll down to the ODT Section and ensure that Enable ODT Mode is selected.<br />
If not, click the box to enable it.<br />
e. Click Apply to save the settings or click OK to save and close the Properties<br />
screen.<br />
After clicking OK, the MCP screen appears if the following conditions exist:<br />
• NT-IOP is configured.<br />
• A partition profile that has the ODT is selected.<br />
• The MCP is running.<br />
5–4 3827 2928–001
Configuring a Redundant ODT Connection<br />
Installing ODT and NT-IOP Software<br />
The following procedures describe how to configure a redundant ODT connection to a<br />
second <strong>CNA</strong> for two types of configurations, redundant configurations with path<br />
preservation and redundant configurations without path preservation. For further details<br />
on configuring paths to redundant ODTs, see the Configuration Editor help.<br />
Note: By convention, we recommend designating the <strong>CNA</strong> with the lower NT-IOP<br />
number as the redundant connection.<br />
1. From the Desktop, bring up Web Enabler by doing the following:<br />
a. Click Start.<br />
b. Choose Programs.<br />
c. Choose Web Enabler for ClearPath MCP.<br />
d. Click Web Enabler.<br />
2. On the Web Enabler for ClearPath MCP screen<br />
a. Select File.<br />
b. From the File menu, select Properties.<br />
c. From the Properties screen, select the Advanced tab.<br />
3. From the Advanced tab, select Use redundant connection<br />
When selected, the display is automatically expanded and requires inputs in the<br />
Server Name and Socket Number fields. You fill in these fields differently,<br />
depending on if you want to preserve the path to the redundant ODT or not, based<br />
on how you configured redundancy in the partition profile with the Configuration<br />
Editor.<br />
Do one of the following:<br />
Path Preservation<br />
If you have a redundant configuration with path preservation, perform the following<br />
steps. Note that the primary and backup socket numbers you specify in Web<br />
Enabler should be identical and the primary and backup IP addresses should be<br />
different.<br />
a. In the Server Name field, enter the server name of the <strong>CNA</strong> device or the IP<br />
address of the <strong>CNA</strong> associated with the lower NT-IOP number.<br />
b. In the Socket Number field, enter the socket number of the (system console<br />
or ODT) that will be used for redundancy. This should be the same number<br />
for both ODTs.<br />
3827 2928–001 5–5
Installing ODT and NT-IOP Software<br />
No Path Preservation<br />
If you have a redundant configuration without path preservation, note the following<br />
before configuring a redundant ODT:<br />
• The primary and backup IP addresses should be different.<br />
• The primary and backup socket numbers should be different.<br />
• With this configuration, only one ODT can be active at a time.<br />
• If there is a failure, the operator should manually select the redundant ODT<br />
by specifying Connect Number 2 from the Advanced tab.<br />
• Do not specify Attempt to Reconnect When Disconnected in the Connection<br />
section.<br />
To configure a redundant ODT, perform the following steps:<br />
a. In the Server Name field, enter the server name of the <strong>CNA</strong> device or the IP<br />
address associated with the lower NT-IOP number.<br />
b. In the Socket Number field, enter the socket number of the system console<br />
or ODT that will be used for redundancy. This number should be different<br />
for each ODT.<br />
4. Click Apply to save the settings or click OK to save and close the Properties screen.<br />
5–6 3827 2928–001
Bringing a <strong>CNA</strong> Into Service<br />
Perform the following steps for each <strong>CNA</strong> in the configuration.<br />
Installing ODT and NT-IOP Software<br />
1. Use the UR – PORT command to make the port usable for the NP.<br />
Note: Odd <strong>CNA</strong> numbers are for first/single MCP partition in ClearPath systems.<br />
Even <strong>CNA</strong> numbers are for a second MCP partition.<br />
8001 for the first <strong>CNA</strong>,<br />
8002 for the second <strong>CNA</strong> (if applicable),<br />
8003 for the third <strong>CNA</strong> (if applicable),...<br />
8024 for the 24th <strong>CNA</strong> (if applicable)<br />
2. After completing network configuration procedures, initialize the network provider on<br />
the host.<br />
3827 2928–001 5–7
Installing ODT and NT-IOP Software<br />
5–8 3827 2928–001
Section 6<br />
<strong>CNA</strong> Operations<br />
In normal operation, you can manage a <strong>CNA</strong> from your ClearPath system using ODT<br />
commands. You do not need to access a <strong>CNA</strong> from NetMeeting unless you are<br />
installing and configuring software or viewing the Event Log when troubleshooting the<br />
<strong>CNA</strong>.<br />
This section describes the ODT commands you use during normal <strong>CNA</strong> operation and<br />
also provides precautions you should observe when using NetMeeting.<br />
ODT Commands<br />
The following commands are used during <strong>CNA</strong> operation:<br />
OL PORT <br />
Displays the status of the port in question.<br />
UR PORT <br />
UR - PORT <br />
The Unit Reserved command reserves and unreserves a channel; is<br />
the channel number to be enabled or disabled.<br />
NW NP or<br />
NW NP <br />
Displays either summary information for all network processors (NPs) for the local<br />
host or detailed information about a specific NP.<br />
Note: This command should be used in place of the PER NP command. PER NP<br />
does not report on <strong>CNA</strong>-attached devices.<br />
NW DUMP NP <br />
Causes the NNS probes and the Windows System and Application Event logs to be<br />
written to the rotating disk on the <strong>CNA</strong> device. This command does not reinitialize<br />
the NP.<br />
3827 2928–001 6–1
<strong>CNA</strong> Operations<br />
NW CONN <br />
Determines the status of a connection group in the <strong>CNA</strong> or a component connection<br />
of a connection group.<br />
NW TCPIP PING <br />
Verifies that communication is available between two hosts.<br />
NW TCPIP PING from <br />
Verifies that communication is available. You specify the source of the PING<br />
command as well as the destination.<br />
RY IOP <br />
Brings the NT-IOP online.<br />
SV IOP <br />
Makes units inaccessible to the system. Saved units can be returned to the system<br />
with the RY (Ready) command.<br />
Bringing a <strong>CNA</strong> Up<br />
To bring a <strong>CNA</strong> up (boot the device)<br />
1. Push the power switch on the front of the <strong>CNA</strong> and release. The Power LED should<br />
light after 1 to 2 minutes.<br />
2. Bring the <strong>CNA</strong> into service by entering the following:<br />
UR- PORT (unreserves the channel)<br />
Normally, it is unnecessary to reset the <strong>CNA</strong>. The <strong>CNA</strong> has a watchdog timer that<br />
automatically reboots the system if there is a software hang. If the <strong>CNA</strong> is resetting, this<br />
is indicated by activity of the fixed disk drive status LED.<br />
If a <strong>CNA</strong> seems to be non-operational, refer to Section 7, “Troubleshooting the <strong>CNA</strong>.”<br />
Boot completion can be determined by pinging the private LAN IP address. Check that<br />
the unit is ready and that you can ping the EVLAN (refer to “EVLAN Ping Procedure” in<br />
Section 7).<br />
If you are unable to ping the EVLAN, reset the <strong>CNA</strong>. To reset the <strong>CNA</strong>, check that the<br />
fixed disk drive status LED is off, and then press the Reset switch on the front of the<br />
<strong>CNA</strong>.<br />
6–2 3827 2928–001
Powering a <strong>CNA</strong> Down<br />
To power down a <strong>CNA</strong>, do the following:<br />
<strong>CNA</strong> Operations<br />
1. Open a NetMeeting session to the <strong>CNA</strong> as described in Section 2, “Establishing a<br />
NetMeeting Connection to <strong>CNA</strong>.”<br />
2. From the Desktop, click Start and then Shutdown.<br />
3. When you see the CD-ROM Activity LED start to flash, press the power button on<br />
the front of the <strong>CNA</strong> (this prevents the <strong>CNA</strong> from restarting automatically). Note that<br />
the Power button has a 3 second delay. Press and release the button, then wait.<br />
We do not recommend powering the <strong>CNA</strong> directly with the Power button without first<br />
shutting the <strong>CNA</strong> down through Windows. However, if you cannot perform steps 1 and<br />
2, verify that the Fixed Disk Drive Status LED is off for at least 10 seconds, then press<br />
the Power button.<br />
Resetting a <strong>CNA</strong><br />
To reset a <strong>CNA</strong>, do the following:<br />
1. Open a NetMeeting session to the <strong>CNA</strong> as described in “Establishing a Connection<br />
to <strong>CNA</strong>” in Section 2 of this guide.<br />
2. From the Desktop, click Start and then ShutDown. <strong>CNA</strong> will automatically reset and<br />
then restart.<br />
If you are unable to open a NetMeeting session to <strong>CNA</strong>:<br />
1. Verify that the fixed disk drive status LED is off for at least 10 seconds.<br />
2. Press the Reset button on the front panel.<br />
Precautions When Configuring and Using <strong>CNA</strong><br />
Except for actions described in this document, do not use NetMeeting to configure the<br />
operating system, its peripherals, or its applications. If you change the system<br />
configuration, you may experience performance or security problems. An incorrect<br />
configuration could make the <strong>CNA</strong> inoperable and require you to reinstall the <strong>CNA</strong> image.<br />
Do not try to install software on the <strong>CNA</strong> other than the software described in this guide.<br />
<strong>CNA</strong> is an appliance that is designed to run a single application.<br />
Note that the <strong>CNA</strong> image is a minimal version of Windows NT. Windows help files and<br />
many executables have been removed from <strong>CNA</strong>, and many Start button commands are<br />
inoperable.<br />
3827 2928–001 6–3
<strong>CNA</strong> Operations<br />
6–4 3827 2928–001
Section 7<br />
Troubleshooting the <strong>CNA</strong><br />
This section describes the ClearPath Network Appliance (<strong>CNA</strong>) troubleshooting<br />
procedures. When using this section, you may want to refer to the illustrations of the<br />
front and back of the <strong>CNA</strong> device in Section 1 of this guide.<br />
As part of the troubleshooting sequence of procedures, this section contains separate<br />
procedures to<br />
• Ping a private LAN<br />
• Ping an EVLAN<br />
• Ping a public LAN<br />
• Access the <strong>CNA</strong> Event Log<br />
• Establish a NetMeeting connection to the <strong>CNA</strong><br />
• Perform a <strong>CNA</strong> safe boot<br />
• Retrieve log and dump files<br />
3827 2928–001 7–1
Troubleshooting the <strong>CNA</strong><br />
<strong>CNA</strong> Debug Flow Chart<br />
Use the following debug checklist procedure, illustrated in Figure 7-1, to troubleshoot<br />
problems with the <strong>CNA</strong>. Each decision point in the Debug Flowchart provides you with a<br />
specific area of the <strong>CNA</strong> to check; if that area is working correctly, the flowchart<br />
progresses to subsequent areas to check. As you reach a decision point, refer to the<br />
Debug Checklist Procedure in the next subsection for a description of what is to be<br />
tested and the procedures to test it.<br />
Note that the minimum field-replaceable unit (FRU) for the <strong>CNA</strong> is the entire <strong>CNA</strong>. There<br />
are no replaceable components within the <strong>CNA</strong>.<br />
Start<br />
Power?<br />
Yes<br />
LAN LED<br />
Yes<br />
Private LAN<br />
Ping<br />
NetMeeting<br />
to <strong>CNA</strong><br />
Response<br />
Event Log OK<br />
EVLAN Ping<br />
<strong>Public</strong> LAN<br />
Ping<br />
Done<br />
View <strong>CNA</strong> desktop<br />
All Services OK<br />
Response<br />
Response<br />
None Debug<br />
Checklist<br />
Never Lights Debug<br />
Checklist<br />
No Response<br />
Debug Checklist,<br />
then <strong>CNA</strong>_Safe Boot<br />
Reinstall Image<br />
No Response Debug<br />
Checklist<br />
Errors Reported<br />
Debug<br />
Checklist<br />
No Response Debug<br />
Checklist<br />
No Response Debug<br />
Checklist<br />
Figure 7–1. <strong>CNA</strong> Debug Flowchart<br />
7–2 3827 2928–001<br />
021
<strong>CNA</strong> Debug Checklist Procedure<br />
Troubleshooting the <strong>CNA</strong><br />
1. Look at the private LAN activity LED (Figure 1-2). This LED should blink whenever<br />
there is traffic on the private maintenance LAN. If this LED is not blinking, do the<br />
following:<br />
• Make sure that the maintenance hub is powered on.<br />
• Make sure that you are pinging the correct private LAN IP address. Refer to the<br />
following private LAN ping step for the correct IP address.<br />
2. Issue a private LAN ping following the instructions in the “Private LAN Ping<br />
Procedure” later in this section.<br />
3. Using the private LAN IP address, try to establish a NetMeeting connection to the<br />
<strong>CNA</strong>. Follow the instructions in Section 2 under “Establishing a NetMeeting<br />
Connection to <strong>CNA</strong>.” If the NetMeeting connection attempt succeeds, go to step 4<br />
of this procedure. If it fails, go to step 9.<br />
4. Examine the Event Log next for error information and warnings associated with <strong>CNA</strong><br />
problems. See “Event Log Procedure” later in this section.<br />
If the entries in the event log seem valid but nothing obvious is displayed or the<br />
description is inadequate, dump the <strong>CNA</strong>. Use an MCP NW command similar to the<br />
following example:<br />
NW DUMP NP 8001<br />
Follow the instructions in the subsection titled “Initiating a Dump” in Section 6 of<br />
the Network Services <strong>Implementation</strong> <strong>Guide</strong> (4198 6670) to retrieve the dump<br />
information.<br />
5. Test for active communications between the MCP and the <strong>CNA</strong> by issuing an<br />
EVLAN ping from the MCP to the <strong>CNA</strong>. Follow the instructions in the “EVLAN Ping<br />
Procedure” included later in this section. If the ping fails, go to step 7 of this<br />
procedure.<br />
6. If communication is active between the MCP and the <strong>CNA</strong>, determine whether<br />
external communication is working by issuing a public LAN ping. Follow the<br />
instructions in the “<strong>Public</strong> LAN Ping Procedure” later in this section.<br />
The public LAN ping is a variant of the PING command that enables you to specify<br />
the source of the PING command as well as the destination. This test verifies that<br />
Network Services is configured correctly and that the Network Interfaces are<br />
operational and visible to the host.<br />
If all pings succeed, communication with your <strong>CNA</strong> is working properly. If the pings<br />
fail, see step 7 of this procedure.<br />
3827 2928–001 7–3
Troubleshooting the <strong>CNA</strong><br />
7. If the EVLAN ping or the public LAN ping fails, cycle the <strong>CNA</strong> to determine if<br />
rebooting fully recovers the <strong>CNA</strong> and Network Services. Use the following<br />
procedure:<br />
a. Reserve the host interface by issuing the following UR PORT command:<br />
UR PORT <br />
b. Restart/reset the <strong>CNA</strong>. NetMeeting to the <strong>CNA</strong>, then Start, Shutdown, Restart.<br />
c. Wait about 5 minutes for the <strong>CNA</strong> to come back online. You can do a private<br />
LAN ping to validate that the <strong>CNA</strong> has booted.<br />
8. If the procedure in step 7 does not work, follow the procedure “Performing a <strong>CNA</strong><br />
Safe Boot” later in this section to reboot from the hard disk rather than the flash<br />
disk.<br />
9. Check the Event Log for errors. See “Event Log Procedure” later in this section.<br />
10. Reinstall the <strong>CNA</strong> operating system image. Follow the instructions given in Section<br />
2 in the subsection titled “Installing the <strong>CNA</strong> Operating System Image.”<br />
11. Check the Event Log again for errors. (See the “Event Log Procedure“ later in this<br />
section.) If this looks OK, continue with the following steps.<br />
12. Reconfigure the <strong>CNA</strong> following the instructions given in the subsection “Configuring<br />
<strong>CNA</strong>” in Section 3.<br />
13. Reload the Network Services software following the instructions given in Section 4<br />
“Installing Network Services Software on the <strong>CNA</strong>.”<br />
If you cannot complete the preceding steps, see your <strong>Unisys</strong> customer service<br />
representative (CSR), as you may need to replace your <strong>CNA</strong>.<br />
7–4 3827 2928–001
Private LAN Ping Procedure<br />
Perform the following steps to ping the private LAN:<br />
Troubleshooting the <strong>CNA</strong><br />
1. Open a Command prompt from the Windows server or Service Processor.<br />
2. Enter the command<br />
PING 192.168.222.1xx<br />
where x is 50 + the device ID of the <strong>CNA</strong> you are pinging. A successful ping should<br />
return the following:<br />
Reply from 192.168.222.1xx<br />
3. If the ping fails, check the following:<br />
a. Make sure you are pinging the correct IP address for the particular <strong>CNA</strong> by<br />
checking the <strong>CNA</strong>cfgX.ini file or asking your administrator.<br />
b. Make sure that the Windows server IP address is in the same subnet as the<br />
<strong>CNA</strong>. If not, change the IP address of the server or move to a different server.<br />
c. If the results of substeps a and b are OK, you may have a software failure.<br />
Follow the procedure “Performing a <strong>CNA</strong> Safe Boot” procedure later in this<br />
section.<br />
EVLAN Ping Procedure<br />
Perform the following steps to ping an EVLAN:<br />
1. From the MCP ODT, issue a Ping command similar to the following example:<br />
NW TCPIP PING 192.168.16.102<br />
Note: The IP address of the device you are trying to reach must match the<br />
<strong>CNA</strong> EVLAN IP address. Refer to Table 3-1 for default values.<br />
The following screen shows the results of a successful EVLAN Ping command:<br />
3827 2928–001 7–5
Troubleshooting the <strong>CNA</strong><br />
2. If the EVLAN ping is unsuccessful, issue a networking command similar to the<br />
following command to determine if the network processor is available:<br />
NW NP 8001<br />
3. If the response to this command is “NOT AVAILABLE” or “UNKNOWN NP,” check<br />
whether the port is reserved by issuing the following OL PORT command:<br />
OL PORT <br />
4. If the port is reserved, issue the following UR– PORT command and then try the ping<br />
again.<br />
UR- <br />
If this command fails, call <strong>Unisys</strong> support.<br />
If the response to the UR command is “INVALID UNIT NUMBER,” contact your<br />
<strong>Unisys</strong> customer service representative to modify the PCD.<br />
5. If the NW NP command returned a response “available,” issue the following<br />
command to determine if the connection group and the component connection are<br />
open:<br />
NW CONN ...<br />
If they are not open, update your host init files.<br />
7–6 3827 2928–001
<strong>Public</strong> LAN Ping Procedure<br />
Troubleshooting the <strong>CNA</strong><br />
Perform the following steps from the MCP ODT to complete a public LAN ping<br />
procedure:<br />
1. For each line, issue the following PING command:<br />
NW TCPIP PING FROM <br />
where is the IP address of a public LAN device and<br />
is the IP address of a line on the <strong>CNA</strong> device.<br />
The following screen shows the results of a successful public LAN ping. In the<br />
system used for this test, 192.62.181.103 is the IP address of line 3 of the <strong>CNA</strong> and<br />
192.62.181.250 is the IP address of an external device on the public LAN.<br />
2. If this ping operation fails, do the following:<br />
a. Make sure that the public LAN cable is attached and that the LINK LED for that<br />
line is on.<br />
b. Ping the gateway IP address.<br />
3. If you cannot ping the gateway, contact <strong>Unisys</strong> support.<br />
3827 2928–001 7–7
Troubleshooting the <strong>CNA</strong><br />
Event Log Procedure<br />
Perform the following steps to access the <strong>CNA</strong> Event Log:<br />
1. Establish a NetMeeting session to the <strong>CNA</strong> under test. (Follow the instructions in<br />
Section 2 of this document under “Establishing a NetMeeting Connection to <strong>CNA</strong>.”)<br />
2. Click the Start button on the toolbar.<br />
3. Point to Programs, then to Administrative Tools (Common), then click Event Viewer.<br />
4. Click and examine the Event Viewer Application Log and the Event Viewer System<br />
Log. These logs display entries that you can check for error information.<br />
5. Point to the log entry that you want to look at and select it. Focus on the Yellow<br />
Warning indicators that contain warning information, and the Red lights that contain<br />
error information.<br />
6. Double-click to display the details of the Event Log entry you selected.<br />
7–8 3827 2928–001
Troubleshooting the NetMeeting Procedure<br />
Troubleshooting the <strong>CNA</strong><br />
Use the following procedure if you are having trouble establishing a NetMeeting<br />
connection to the <strong>CNA</strong>:<br />
1. Cycle (terminate and restart) NetMeeting.<br />
If the attempt to establish a NetMeeting connection fails during the <strong>CNA</strong> Safe Boot<br />
procedure, call your <strong>Unisys</strong> customer service representative.<br />
If the attempt fails during the normal operation, go to the procedure “Performing a<br />
<strong>CNA</strong> Safe Boot.”<br />
2. If NetMeeting displays the error “NetMeeting was unable to place a secure call…,”<br />
the <strong>CNA</strong> may still be in the process of booting. Wait 5 minutes and try again.<br />
Either reinstall NetMeeting or install NetMeeting 3.01 Service Pack 1.<br />
3. If NetMeeting displays the Windows NT logon screen but you cannot log on to the<br />
<strong>CNA</strong>, make sure that the Administrator password for the <strong>CNA</strong> is correct. If it is not,<br />
see your system administrator for the correct password. The password is in the<br />
<strong>CNA</strong>cfgx.ini file if you saved it to a floppy disk when you installed the <strong>CNA</strong>.<br />
If you cannot find or determine the password, you will have to reload the operating<br />
system image. Refer to the instructions in Section 2 in the subsection titled<br />
“Installing the <strong>CNA</strong> Operating System Image.”<br />
Note: If you enter an invalid password four consecutive times, the following error<br />
message appears on the NetMeeting window:<br />
The Other person didn’t allow you to join the meeting.<br />
All additional attempts to “place a call” to the <strong>CNA</strong> device will result in the same<br />
error message, regardless of the terminal from which the call attempt is made. This<br />
is a NetMeeting security feature to prevent unauthorized access. When this error<br />
message is displayed, you must reboot the <strong>CNA</strong> device to retry the NetMeeting<br />
logon. This will give you four more chances to enter the correct password.<br />
3827 2928–001 7–9
Troubleshooting the <strong>CNA</strong><br />
Performing a <strong>CNA</strong> Safe Boot<br />
The <strong>CNA</strong> Safe Boot enables you to verify the operation of the LAN interfaces as well as<br />
the RAID hard disks. It is also the first step you perform when installing the <strong>CNA</strong><br />
operating system image. Use the following procedure to perform a <strong>CNA</strong> Safe Boot:<br />
1. Insert the <strong>CNA</strong>_Safe Boot floppy disk. The boot disk contains a Boot.ini file that<br />
re-directs the boot process to the <strong>CNA</strong>_Safe directory on the hard disk.<br />
2. Power on or restart the <strong>CNA</strong>.<br />
The system boots from the <strong>CNA</strong>_Safe Image on the hard drive. There is no visual<br />
indication of boot completion—wait for all drive activity to finish (about 3 to 5<br />
minutes).<br />
3. If the boot is successful, start NetMeeting to establish the connection and log on to<br />
the <strong>CNA</strong> (see “Establishing a NetMeeting Connection to <strong>CNA</strong>” in Section 2 of this<br />
guide).<br />
Your Windows system must be attached to the private LAN and configured to<br />
connect to the reserved IP address (192.168.222.150) specified on the label of the<br />
boot floppy. This is always the address of the <strong>CNA</strong> when you boot from the hard<br />
disk. This means that you can only have one device booted from the <strong>CNA</strong>_Safe<br />
Image at a time. Otherwise, you would have duplicate IP addresses on the private<br />
LAN if you booted more than one <strong>CNA</strong> from the <strong>CNA</strong>_Safe directory on the hard<br />
disk. Under normal circumstances, you should not change this address.<br />
Note: Sometimes NetMeeting will not establish a session with the <strong>CNA</strong> even<br />
though a ping of <strong>CNA</strong> is successful. You can usually resolve this by closing the<br />
NetMeeting window and restarting NetMeeting.<br />
4. When the Remote Desktop Sharing Password dialog box appears, enter<br />
Administrator in the User and Password boxes and click OK to log on to the <strong>CNA</strong>.<br />
7–10 3827 2928–001
Log and Dump File Retrieval<br />
Troubleshooting the <strong>CNA</strong><br />
<strong>CNA</strong>, and NNS have log and dump files that are created when they fail. These files are<br />
retrieved and submitted as part of a trouble report. The following files are created:<br />
• <strong>CNA</strong> Dump file. For example: 19Jun01_1719.DMP. This file is a standard Windows<br />
NT dump file.<br />
• NNS Dump File. For example: NNSDMP00.TXT.<br />
• Event Log Files. For example: CNPSYS1.EVT is a Windows System Event Log and<br />
CNPAPP1.EVT is a Windows Application Log.<br />
There are four different ways to retrieve these files:<br />
• File transfer (FTP) from the MCP host<br />
• A DOS FTP entered from a Windows server<br />
• A browser FTP entered from a Windows server<br />
• From a NetMeeting session<br />
Each method is described below.<br />
File Transfer (FTP) from the MCP Host<br />
The FTP is initiated from the MCP host. This is a file transfer from <strong>CNA</strong> to the MCP host<br />
across EVLAN (FC-SL).<br />
From the MCP host, the following sequence establishes the FTP session:<br />
1. Make sure that the EVLAN TCP/IP connection is opened. (The connection may be<br />
AUTOINIT=FALSE or the port may be reserved.)<br />
2. From a CANDE session on the MCP host (using the ODT or a terminal), do the<br />
following:<br />
a. Type U FTP<br />
b. Type OPEN <br />
See Table 3-1 to find the EVLAN IP address of the <strong>CNA</strong>.<br />
c. You will be prompted to enter a username.<br />
Enter Administrator<br />
3827 2928–001 7–11
Troubleshooting the <strong>CNA</strong><br />
d. You will be prompted to enter a password.<br />
Check with the System Administrator for the <strong>CNA</strong> password.<br />
The FTP session will be established and ready to copy data to/from the MCP. Use the<br />
GET command to copy a file from the <strong>CNA</strong> to the host drive.<br />
DOS FTP Entered from a Windows Server<br />
A DOS FTP from a Windows server is a file transfer from <strong>CNA</strong> to the Windows server<br />
across the private LAN.<br />
From the Windows server command line, type FTP using the <strong>CNA</strong><br />
private LAN IP address. This initiates an anonymous FTP with <strong>CNA</strong>.<br />
Browser FTP from a Windows Server<br />
Similar to the DOS FTP, this is also a file transfer from <strong>CNA</strong> to the Windows server<br />
across the private LAN.<br />
From Internet Explorer, type FTP:// as shown in the Address field on the<br />
following screen.<br />
7–12 3827 2928–001
Troubleshooting the <strong>CNA</strong><br />
From a NetMeeting Session<br />
This is the standard NetMeeting session between <strong>CNA</strong> and the Windows server. Once<br />
in NetMeeting, the dump and log files are located in the <strong>CNA</strong>_Dump partition. The<br />
<strong>CNA</strong>_Dump partition is usually drive E (see the following screen for an example).<br />
From NetMeeting, you can map a network drive to an MCP drive. This will enable you to<br />
copy the files to the MCP over EVLAN.<br />
NetMeeting is the only mechanism available for removing files from the <strong>CNA</strong>_Dump<br />
partition.<br />
3827 2928–001 7–13
Troubleshooting the <strong>CNA</strong><br />
7–14 3827 2928–001
Appendix A<br />
Sample Network Initialization Files<br />
This appendix provides examples of ClearPath CNS and TCP/IP initialization files that<br />
have to be updated to use the ClearPath Network Appliance (<strong>CNA</strong>) in an online MCP<br />
environment. You can find sample CNS and TCP/IP initialization files for ClearPath<br />
systems with shared adapter support on the Network System Software NETSYSTEM<br />
release media.<br />
The following CNS initialization files define the commands preconfigured for ClearPath<br />
systems with shared adapters. Note that xxxxx is the appropriate ClearPath system<br />
identifier.<br />
For MCP Release 8.0:<br />
• INIT/SAMPLE/CLEARPATH/xxxxx/CPMCP1/CNS<br />
• INIT/SAMPLE/CLEARPATH/xxxxx/CPMCP2/CNS<br />
The following TCP/IP initialization files define the TCP/IP commands preconfigured for<br />
ClearPath systems with shared adapters:<br />
For MCP Release 8.0:<br />
• INIT/SAMPLE/CLEARPATH/xxxxx/CPMCP1/TCPIP<br />
• INIT/SAMPLE/CLEARPATH/xxxxx/CPMCP2/TCPIP<br />
Where: xxxxx is the appropriate ClearPath system identifier<br />
3827 2928–001 A–1
Sample Network Initialization Files<br />
CNS Initialization File<br />
The Connection Group definitions for CNS define the ICPDeviceID and Adapter Type for<br />
all adapters. The ICPDeviceID is set to a value of 8001 to 8024, depending on the<br />
Device ID of the <strong>CNA</strong>. The Adapter Type identifies the public LAN adapters as either the<br />
10/100 LAN adapter or the Gigabit Ethernet adapter.<br />
The following Connection Group example identifies the device as <strong>CNA</strong>1 (ICPDEVICEID =<br />
8001) and lines 1 and 2 as 10/100/1000 LAN adapters (Adapter Type = GIGABIT).<br />
NW ADD CONNECTIONGROUP CG_ICP_80010%<br />
% Connection Group Information<br />
( TYPE = LAN%<br />
, ICPDEVICEID = 8001%<br />
, LINEMODULEID = 1%<br />
, LINEID = 0%<br />
, LOCALADDRESS = 08000B008001%<br />
, MAXINPUTMESSAGESIZELIMIT = 4352%<br />
, MAXOUTPUTMESSAGESIZELIMIT = 4352%<br />
, MAXINPUTMESSAGESIZE = 4352%<br />
, MAXOUTPUTMESSAGESIZE = 4352%<br />
)%<br />
;%<br />
NW ADD CONNECTIONGROUP CG_ICP_80011%<br />
% Connection Group Information<br />
( TYPE = LAN%<br />
, ICPDEVICEID = 8001%<br />
, LINEMODULEID = 1%<br />
, LINEID = 1%<br />
, LOCALADDRESS = *DEFAULT%<br />
, ADAPTERTYPE = GIGABIT%<br />
)%<br />
;%<br />
A–2 3827 2928–001
TCP/IP Initialization File<br />
Sample Network Initialization Files<br />
The information in the TCP/IP initialization file consists of the following:<br />
• A TCPIDENTITY statement for each active line.<br />
• A MAPPING statement to associate the Windows VLAN IP address with the name<br />
of the <strong>CNA</strong> device.<br />
NW TCPIP TCPIPIDENTITY %<br />
IPADDRESS = 192.168.16.101 NP 8001 MASK 255.255.255.252 LINEID 0;%<br />
% %<br />
NW TCPIP TCPIPIDENTITY %<br />
IPADDRESS = 192.168.237.200 NP 8001 MASK 255.255.255.0 LINEID 1 %<br />
% %<br />
NW TCPIP TCPIPIDENTITY %<br />
IPADDRESS = 192.168.237.201 NP 8001 MASK 255.255.255.0 LINEID 2; %<br />
% %<br />
NW TCPIP TCPIPIDENTITY %<br />
PADDRESS = 192.168.237.202 NP 8001 MASK 255.255.255.0 LINEID 3; %<br />
% %<br />
NW TCPIP TCPIPIDENTITY %<br />
IPADDRESS = 192.168.237.203 NP 8001 MASK 255.255.255.0 LINEID 4; %<br />
% %<br />
NW TCPIP MAPPING + <strong>CNA</strong>2 %<br />
192.168.16.102 %<br />
• Component Connection definitions for each line that has a TCPIDENTITY.<br />
NW ADD CONNECTION TO CG_ICP_80010%<br />
80010_TCPIP_80010%<br />
% Connection Information %<br />
( NETWORKLAYERENTITY = IP%<br />
, CLASS = CLASS_1%<br />
, FRAMETRACE = FALSE%<br />
, RETRYLIMITXID = 10%<br />
, MAXINPUTMESSAGESIZELIMIT = 4352%<br />
, MAXOUTPUTMESSAGESIZELIMIT = 4352%<br />
, MAXINPUTMESSAGESIZE = 4352%<br />
, MAXOUTPUTMESSAGESIZE = 4352%<br />
)%<br />
;%<br />
NW ADD CONNECTION TO CG_ICP_80011%<br />
80011_TCPIP_80011%<br />
% Connection Information %<br />
( NETWORKLAYERENTITY = IP%<br />
, REMOTEADDRESS = 000000000000%<br />
, CLASS = ETHIP%<br />
, FRAMETRACE = FALSE%<br />
, RETRYLIMITXID = 10%<br />
)%<br />
;%<br />
3827 2928–001 A–3
Sample Network Initialization Files<br />
A–4 3827 2928–001
Index<br />
A<br />
Adapter Teaming<br />
configuring, 3-15<br />
B<br />
back view<br />
<strong>CNA</strong>, 1-7<br />
booting the <strong>CNA</strong>, 6-2<br />
bringing <strong>CNA</strong> down, 6-3<br />
bringing <strong>CNA</strong> into service the first time, 5-7<br />
bringing <strong>CNA</strong> up, 6-2<br />
C<br />
CD-ROM<br />
<strong>CNA</strong> Images CD, 2-2<br />
CD-ROM drive<br />
use in <strong>CNA</strong>, 1-3<br />
CD-ROM/DVD activity LED, 1-6<br />
ClearPath Network Appliance<br />
defined, 1-1<br />
front view, 1-5<br />
troubleshooting, 7-1<br />
<strong>CNA</strong><br />
back view, 1-7<br />
bringing down, 6-3<br />
bringing into service the first time, 5-7<br />
bringing up, 6-2<br />
configuring, 3-1<br />
defined, 1-1<br />
embedded software, 2-1<br />
features, 1-2<br />
front view, 1-5<br />
How it fits in ClearPath system, 1-10<br />
image, 2-1<br />
installation steps, operating system<br />
image, 2-8, 7-10<br />
installing image, 2-2<br />
installing Network Services on, 4-2<br />
installing operating system image, 2-7<br />
operating system image installation<br />
steps, 2-8, 7-10<br />
operating with ODT commands, 6-1<br />
service strategy, 7-2<br />
software components, 1-13<br />
styles, 1-4<br />
troubleshooting, 7-1<br />
Event Log procedure, accessing, 7-8<br />
EVLAN Ping procedure, 7-5<br />
Private LAN Ping procedure,<br />
accessing, 7-5<br />
<strong>Public</strong> LAN Ping procedure,<br />
accessing, 7-7<br />
<strong>CNA</strong> complex configuration, 1-12<br />
<strong>CNA</strong> EVLAN IP Addresses, 3-2<br />
<strong>CNA</strong> Images CD-ROM, 2-2<br />
<strong>CNA</strong> Safe Boot floppy disk, 2-2<br />
CNS initialization file (sample), A-1<br />
commands<br />
ODT, 6-1<br />
configuration rules, 1-11<br />
configuring <strong>CNA</strong>, 3-1<br />
configuring for ODT mode<br />
Web Enabler, 5-4<br />
3827 2928–001 Index–1<br />
D<br />
debug<br />
flow chart, 7-2<br />
procedure, 7-2<br />
dump files<br />
retrieving <strong>CNA</strong>, NT-IOP, and NNS<br />
files, 7-11<br />
E<br />
Ethernet Jumbo Frames, preparing to<br />
use, 3-13<br />
Event Log procedure, accessing steps, 7-8<br />
EVLAN Ping procedure, 7-5
Index<br />
F<br />
FC-SL card, 1-3<br />
features<br />
<strong>CNA</strong>, 1-2<br />
FiberChannel-SuperLite (FC-SL), 1-3<br />
FID, 1-13<br />
field replaceable units<br />
<strong>CNA</strong>, 1-3<br />
Fixed disk drive status LED, 1-6<br />
Floppy activity drive, 1-6<br />
floppy disk<br />
use in <strong>CNA</strong>, 1-3<br />
front view<br />
<strong>CNA</strong>, 1-5<br />
H<br />
hard disk<br />
use in <strong>CNA</strong>, 1-3<br />
I<br />
ID button, 1-6<br />
ID LED, 1-6<br />
IEEE 802.1Q VLANS, preparing to use, 3-14<br />
image<br />
guidelines for installing, 2-1<br />
initialization files<br />
CNS and TCP/IP, A-1<br />
installing<br />
<strong>CNA</strong> operating system image, 2-7, 2-8,<br />
7-10<br />
Network Services on the <strong>CNA</strong>, 4-2<br />
installing <strong>CNA</strong><br />
installing the <strong>CNA</strong> image, 2-2<br />
installing NT-IOP software, 5-1<br />
installing ODT software, 5-1<br />
installing Web Enabler, 5-3<br />
IOCD<br />
I/O Firmware CD-ROM, 5-1<br />
IP Addresses<br />
<strong>CNA</strong> VLAN, 3-2<br />
defined, Table 3-1, 3-2<br />
MCP Private LAN, 3-2<br />
MCP <strong>Public</strong> IP Addresses, 3-2<br />
MCP VLAN, 3-2<br />
on boot floppy, 2-6<br />
Private LAN, 3-2<br />
Index–2 3827 2928–001<br />
J<br />
Jumbo Frames, preparing to use, 3-13<br />
L<br />
Line 3 activity LED, 1-5<br />
LOM, 1-13<br />
M<br />
maintenance LAN activity LED, 1-5<br />
MCP EVLAN IP Addresses, 3-2<br />
MCP <strong>Public</strong> IP Addresses, 3-2<br />
N<br />
NetMeeting<br />
establishing a connection to <strong>CNA</strong>, 2-5<br />
installing, 2-3<br />
precautions when using, 6-3<br />
troubleshooting, 7-9<br />
using, 2-5<br />
working with, 2-3<br />
Network Services<br />
installing, 4-1<br />
Network Services installation<br />
Adapter Properties screen, 4-7<br />
Choose Configuration Options screen, 4-12<br />
Choose Destination Location screen, 4-4<br />
Configuration of Shared Adapter Cards<br />
screen, 4-6<br />
MCP Host Name screen, 4-13<br />
Network Services Properties screen, 4-11<br />
Review Configuration Option Selections<br />
screen, 4-14<br />
Review Shared Adapter Card Selections<br />
screen, 4-9<br />
Select Adapter Cards for MCP Server<br />
Access screen, 4-7, 4-8<br />
Setup Complete screen, 4-15<br />
Specify Windows Server Environment<br />
screen, 4-10<br />
Start Copying Files screen, 4-5<br />
NMI button, 1-6<br />
NNS, 1-13<br />
NT-IOP software<br />
installing, 5-1
O<br />
ODT commands, 6-1<br />
ODT software<br />
installing, 5-1<br />
operating system image<br />
installing on <strong>CNA</strong>, 2-7<br />
P<br />
partitions<br />
<strong>CNA</strong>_Primary partition, 2-2<br />
<strong>CNA</strong>_Safe partition, 2-2<br />
password, 3-4<br />
initial, 2-3<br />
screen used for changing, 3-8<br />
peripheral devices<br />
locations in <strong>CNA</strong>, 1-5<br />
Ping procedure<br />
EVLAN, 7-5<br />
Private LAN, 7-5<br />
<strong>Public</strong> LAN, 7-7<br />
port aggregation (shared adapters)<br />
preparing for, 3-12<br />
Power button, 1-6<br />
Power LED, 1-5<br />
powering down <strong>CNA</strong>, 6-3<br />
powering on <strong>CNA</strong>, 6-2<br />
preparing to use Ethernet<br />
JumboFrames, 3-13<br />
preparing to use IEEE 802.1Q VLANS, 3-14<br />
private LAN activity LED, 1-5<br />
Private LAN IP Addresses, 3-2<br />
Private LAN Ping procedure, 7-5<br />
public LAN activity LED, 1-5<br />
<strong>Public</strong> LAN Ping procedure, accessing<br />
steps, 7-7<br />
R<br />
RAID hard disk<br />
use in <strong>CNA</strong>, 1-3<br />
Reset button, 1-6<br />
retrieving dump files<br />
<strong>CNA</strong>, NT-IOP, and NNS files, 7-11<br />
Index<br />
3827 2928–001 Index–3<br />
S<br />
safe boot, 2-8, 7-9<br />
performing, 7-10<br />
screens<br />
Adapter Properties (for Network Services<br />
software), 4-7<br />
Choose Configuration Options(for Network<br />
Services software), 4-12<br />
Choose Destination Location (for Network<br />
Services software), 4-4<br />
<strong>CNA</strong> Configuration - change password, 3-7<br />
<strong>CNA</strong> Configuration - configuration<br />
summary, 3-10<br />
<strong>CNA</strong> Configuration - enter computer<br />
name, 3-7<br />
<strong>CNA</strong> Configuration - enter path to<br />
<strong>CNA</strong>cfg4.ini, 3-5<br />
<strong>CNA</strong> Configuration - enter private LAN IP<br />
address, 3-6<br />
<strong>CNA</strong> Configuration - Ethernet support, 3-8<br />
<strong>CNA</strong> Configuration dialog box, 3-4<br />
Configuration of Shared Adapter Cards (for<br />
Network Services software), 4-6<br />
configuring IEEE 802.1Q VLANs, 3-17<br />
Date/Time Properties - configuration<br />
screen, 3-9<br />
Format disk screen, 2-10<br />
Installation Options screen for installing<br />
ODT software, 5-2<br />
Intel(R) PROSet II - configuring adapters as<br />
part of a team, 3-15, 3-16<br />
Intel(R) PROSet II - configuring IEEE<br />
802.1Q VLANs, 3-17<br />
Intel(R) PROSet II - recalculate networking<br />
bindings, 3-21<br />
Intel(R) PROSet II - Save/Restore<br />
settings, 3-19<br />
Intel(R) PROSet II - saving settings, 3-18<br />
MCP Host Name (for Network Services<br />
software), 4-13<br />
NetMeeting - Not in a Call screen, 2-5<br />
NetMeeting - Remote Desktop Sharing<br />
Password screen, 2-3<br />
Network Services Properties(for Network<br />
Services software), 4-11<br />
Place a Call dialog box, 2-5<br />
Remote Desktop Sharing Password, 4-2<br />
Review Configuration Option Selections<br />
(for Network Services<br />
software), 4-14
Index<br />
Review Shared Adapter Card Selections<br />
(for Network Services<br />
software), 4-9<br />
Select Adapter Cards for MCP Server<br />
Access (for Network Services<br />
software), 4-7<br />
Setup Complete (for Network Services<br />
software), 4-15<br />
Specify Windows Server Environment(for<br />
Network Services software), 4-10<br />
Start Copying Files (for Network Services<br />
software), 4-5<br />
service strategy<br />
<strong>CNA</strong>, 7-2<br />
shared adapters<br />
keep current selection, 4-6<br />
software block diagram, 1-13<br />
software installation<br />
installing <strong>CNA</strong> image, 2-2<br />
styles<br />
<strong>CNA</strong>, 1-4<br />
System block diagram, 1-10<br />
System Status LED, 1-6<br />
T<br />
TCP/IP initialization file (sample), A-1<br />
troubleshooting<br />
<strong>CNA</strong>, 7-1<br />
Event Log procedure, accessing, 7-8<br />
EVLAN Ping procedure, accessing, 7-5<br />
Private LAN Ping procedure,<br />
accessing, 7-5<br />
<strong>Public</strong> LAN Ping procedure,<br />
accessing, 7-7<br />
NetMeeting Procedure, 7-9<br />
steps for, 7-2<br />
typical <strong>CNA</strong> configuration, 1-11<br />
W<br />
Web Enabler<br />
configuring for ODT mode, 5-4<br />
installing, 5-3<br />
Index–4 3827 2928–001
*38272928-001*<br />
38272928– 001