Nokia IP100 Series Installation Guide - Check Point

Nokia 

IP100 Series Installation Guide 

Part Number: 45-0445-001 Rev A 

October 2000 

Nokia 

313 Fairchild Drive 

Mountain View, CA 94043-2215 

1-650-625-2000 

info@iprg.nokia.com

COPYRIGHT 

© 2000 Nokia Corporation All rights reserved. 

Rights reserved under the copyright laws of the United States. 

RESTRICTED RIGHTS LEGEND 

Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in 

Technical Data and Computer Software clause at DFARS 252.227-7013. 

IMPORTANT NOTE TO USERS 

This software is provided by Nokia Corporation as is and any express or implied warranties, including, but not limited to, the 

implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall Nokia Corporation be 

liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement 

of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, 

whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, 

even if advised of the possibility of such damage. 

Nokia reserves the right to make changes without further notice to any products herein to improve reliability, function, or design. 

TRADEMARKS 

Nokia is a registered trademark of Nokia Corporation. 

Other products mentioned in this document are trademarks or registered trademarks of their respective holders. 

ii 

IP100 Series Installation Guide

COMPLIANCE STATEMENTS 

This hardware complies with the standards listed in this section. 

Emission Standards 

FCC Part 15 Class B 

EN55022B, EN50082-1 (1977) 

IEC 1000-4-2 

IEC 1000-4-3 

IEC 1000-4-4 

IEC 1000-4-5 

IEC 1000-4-6 

IEC 1000-4-11 

US and Canada 

European Community (CE) 







Safety Standards 

UL1950 

CUL/CSA 22.2 NO 950-M93 

EN60950:1992, A1, A2:1993, A3:1995, A4:1997, All:1998 

EN60950 

US 

Canada 

European Community (CE)/TUV 

Japanese National Deviation 


iii

NOKIA CONTACT INFORMATION 

Corporate Headquarters 

E-mail: info@iprg.nokia.com 

Web Site: www.nokia.com 

Telephone: 1-888-477-4566 or 1-650-625-2000 

Fax: 1-650-691-2170 

Mail Address: Nokia Corporation 


Mountain View, California 94043-2215 

USA 

Regional Contact Information 

Americas Europe Asia-Pacific 

Tel: 1-877-997-9199 Tel: 00800 5543 1816 Tel: +358 9 692 7156 

Outside USA and Canada: +1 512-437-7089 or 1+49 231 754 6011 

E-mail: info.ipnetworking_americas@nokia.com E-mail: info.ipnetworking_emea@nokia.com E-mail:info.ipnetworking_apac@nokia.com 

Nokia Corporation 

Nokia NTC, UK/Heathrow 

313 Fairchild Drive 2 Heathrow Blvd. 


284 Bath Road 

USA Heathrow 

Middlesex UP7 ODQ 

England 

Nokia Customer Support 

Website: 

E-mail: 

http://support.nokia.com 

tac.support@nokia.com 

Americas (except Canada) 

Voice: 1-888-477-9824 or 1-650-625-2525 

Fax: 1-650-625-2903 

Canada 

Voice: 1-888-361-5030 or 1-613-271-6721 

Fax: 1-613-271-8782 

Europe 

Voice: +44 (0) 208-564-8100 

Fax: +44 (0) 208-897-0674 

Asia-Pacific 

Voice: +65-7232999 

Fax: +65-7232897 

iv 


Contents 

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix 

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x 

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi 

About the Nokia IP100 Series NAP. . . . . . . . . . . . . . . xi 

IP100 Series NAP Product Documentation . . . . . . . .xii 

Other Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii 

Voyager Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii 

Conventions Used in This Guide . . . . . . . . . . . . . . . . xiii 

CHAPTER 1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 

Organization of Installation Guide. . . . . . . . . . . . . . . . .2 

Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 

Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 

Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 

Top . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 

Bottom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 

Site Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 

CHAPTER 2 Installing the Hardware . . . . . . . . . . . . . . . . . . . . . . .11 

Placement of IP100 Series NAP . . . . . . . . . . . . . . . . . .12 

By Itself on Desk or Table . . . . . . . . . . . . . . . . . . . . .12 

Stacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 

Wall Mounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 

Connecting the IP100 Series . . . . . . . . . . . . . . . . . . . . .16 

Step 1—Connecting the NAP to a Power Source.16 

Step 2—Connecting a Console . . . . . . . . . . . . . . . . .17 

Step 3—Connecting the NAP to a Network. . . . . .18 


v

Contents 

Using an External Modem . . . . . . . . . . . . . . . . . . . . . . .19 

Step 1—Connecting a Modem . . . . . . . . . . . . . . . . . .19 

Step 2—Configuring a Modem . . . . . . . . . . . . . . . . .20 

Step 3—Setting Modem Command Strings . . . . . .22 

US Robotics 33.6 fax modem . . . . . . . . . . . . . 22 

Best Data 56K data fax modem . . . . . . . . . . . . 24 

CHAPTER 3 Configuring the NAP . . . . . . . . . . . . . . . . . . . . . . . . . 27 

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 

Using System Startup. . . . . . . . . . . . . . . . . . . . . . . . . . . .29 

Step 1—Assigning a Hostname . . . . . . . . . . . . . . . . .29 

Step 2—Assigning a Password. . . . . . . . . . . . . . . . . .30 

Step 3—Selecting a Browser Type . . . . . . . . . . . . . .30 

Step 4—Entering Initial Interface Information . . .31 

Step 5—Confirming the Setup . . . . . . . . . . . . . . . . . .32 

Using Voyager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 

Monitoring IP100 Series Operations . . . . . . . . . . . . . .35 

APPENDIX A Technical Specifications . . . . . . . . . . . . . . . . . . . . . . 37 

Physical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 

Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 

Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39 

Declaration of Conformity . . . . . . . . . . . . . . . . . . . . . . .40 

APPENDIX B Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 

Ethernet Crossover Cable . . . . . . . . . . . . . . . . . . . . . . . .41 

Null-Modem Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 

vi 


Contents 

APPENDIX C Using Boot Manager . . . . . . . . . . . . . . . . . . . . . . . . . 45 

Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 

Viewing Variables and Other System Parameters 48 

printenv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 

showalias . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 

sysinfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 

ls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 

Setting Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 

setenv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 

unsetenv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 

set-defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 

setalias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 

unsetalias . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 

Other Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53 

halt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 

help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 

Booting the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 

Installing IPSO Using the Boot Manager. . . . . . . . . .55 

Protecting the Boot Manager With a Password . . . .56 

Upgrading the Boot Manager . . . . . . . . . . . . . . . . . . . .57 

APPENDIX D Limited Warranty and Terms and Conditions 

of Software License for Nokia Software . . . . . . . . . . . . 59 

APPENDIX E General Public Licensed Software . . . . . . . . . . 65 

APPENDIX F Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 

Access and Login Problems. . . . . . . . . . . . . . . . . . . . . .70 

Unable to log in to Console port. . . . . . . . . . . . . 70 

Receive login prompt, but password 

not accepted . . . . . . . . . . . . . . . . . . . . . . . . 71 


vii

Contents 

No login prompt . . . . . . . . . . . . . . . . . . . . . . . . . 72 

Unable to connect to Voyager using 

network port . . . . . . . . . . . . . . . . . . . . . . . . . 72 

Interface Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74 

Local NAP ports do not appear in 

Voyager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 

No link light appears when you 

connect the port . . . . . . . . . . . . . . . . . . . . . . 74 

Activity light is continuously on . . . . . . . . . . . . . 74 

High collision rate on the hub . . . . . . . . . . . . . . . 75 

Connectivity Problems. . . . . . . . . . . . . . . . . . . . . . . . . . .76 

Unable to ping through the unit . . . . . . . . . . . . . 76 

Routing Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78 

Problems with OSPF. . . . . . . . . . . . . . . . . . . . . . . . . . .79 

OSPF does not operate . . . . . . . . . . . . . . . . . . . . 79 

Problems with RIP. . . . . . . . . . . . . . . . . . . . . . . . . . . . .80 

Problems Exchanging Routes. . . . . . . . . . . . . . . . . . .81 

Problems With Multicast . . . . . . . . . . . . . . . . . . . . . . .82 

Using tcpdump. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84 

Viewing Packets With tcpdump. . . . . . . . . . . . . . . . .84 

tcpdump Command Basics . . . . . . . . . . . . . . . . .84 

tcpdump for a specific interface . . . . . . . . 84 

tcpdump for a specific protocol on 

an interface . . . . . . . . . . . . . . . . . . . . . . . . 85 

tcpdump for an Interface Using a TCP/UDP 

Application Port . . . . . . . . . . . . . . . . 85 

Specifying IP or UDP Port . . . . . . . . . . . . . . . 85 

Filtering Traffic with tcpdump. . . . . . . . . . . . . . .85 

Hiding Specific Types of Traffic . . . . . . . . . . 85 

Viewing a Portion of the Packet . . . . . . . . . . . 86 

Viewing a Specific IP Address . . . . . . . . . . . . 86 

Saving tcpdump Results to Local File . . . . . . . .86 

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 

viii 


Figures 

1-1. Overall view of NAP . . . . . . . . . . . . . . . . . . . . 3 

1-2. Rear panel of NAP . . . . . . . . . . . . . . . . . . . . . 5 

1-3. Top view of NAP . . . . . . . . . . . . . . . . . . . . . . 6 

1-4. Bottom view of NAP . . . . . . . . . . . . . . . . . . . . 7 

2-1. Three NAPs stacked on top of one another 

(rear view) . . . . . . . . . . . . . . . . . . . . . . . . . . 12 

2-2. Wall mounting of NAP . . . . . . . . . . . . . . . . . 14 

2-3. NAP connected to power source . . . . . . . . . . 16 

2-4. Notebook computer connected to NAP . . . . . 17 

2-5. Rear panel of NAP, with network interfaces 

at left . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 

2-6. External modem connected to NAP . . . . . . . 20 

3-1. Screen that appears when first booting 

the NAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 

3-2. System startup browser screen . . . . . . . . . . . . 30 

3-3. System startup interface screen for 

IP110 NAP . . . . . . . . . . . . . . . . . . . . . . . . . . 31 

B-1. Ethernet crossover cable pin connections . . . 41 

B-2. 9-pin to 25-pin null-modem cable . . . . . . . . 43 

B-3. 9-pin to 9-pin null-modem cable . . . . . . . . . 44 


ix

Tables 

2-1. US Robotics AT Commands . . . . . . . . . . . . . 23 

2-2. US Robotics DIP Switches . . . . . . . . . . . . . . 23 

2-3. Best Data AT Commands . . . . . . . . . . . . . . . 25 

A-1. Physical Dimensions of IP100 Series NAP . 37 

A-2. Environmental Characteristics of IP100 Series 

NAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 

A-3. Interface Characteristics of IP100 Series 

NAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 

C-1. Boot Manager Boot Flags . . . . . . . . . . . . . . . 48 

C-2. Boot Manager Argument Defaults . . . . . . . . 54 


x

Preface 

About the Nokia IP100 Series NAP 

The IP100 Series NAP offers the performance and flexibility of Nokia IP 

products in a small package. The small size of the network applications 

platform (NAP) makes it ideal for installation where space is limited. The 

NAP can be placed on a desk or table. It can also be wall mounted. 

This approach provides many benefits: 

• One-step ordering. All interfaces and peripherals are pre-installed 

in a single, integrated unit 

• Quick start-up. All software is pre-installed. 

• Dependability. Nokia supports the entire unit. 

• Compatibility. The IP100 Series maintains compatibility with other 

devices in the Nokia IP family. 

The Nokia IP100 Series NAP is managed using Voyager, the Nokia webbased 

management application. With Voyager, you can manage, monitor, 

and configure the device from any location within the network. 

IP100 Series Installation Guide xi

IP100 Series NAP Product Documentation 

Other Documents 

In addition to this installation guide, the documentation set for this 

product includes Release Notes for IPSO software and Inline Help for 

Voyager, which is displayed within each Voyager page. The 

documentation set also includes the online Voyager Reference Guide. 

Voyager Help 

When using Voyager, to enable inline help: 

• Press the HELP ON button located at the top of the Voyager display. 

The HELP OFF button appears when the help text is active. 

To disable inline help: 

• Click the HELP OFF button. 

To obtain more information about a task or about options, access the 

inline Voyager Reference Guide: 

• Press the DOC button. 

xii 


Conventions Used in This Guide 

Conventions Used in This Guide 

This table shows the meaning of different typefaces used in this 

installation guide. 

Typeface Meaning Examples 

Italic 

An important word or 

phrase such as a link, a 

place to enter data, the 

name of a menu or 

option, a web page or a 

section within a web 

page. 

Also a place where 

different users will 

insert different text in a 

command line. 

Turn Internal Clock off. 

Select the File menu. 

To delete a file, type rm filename. 

Bold Italic 

SMALL CAPS 

Courier 

Courier Bold 

The name of a 

document or a section 

within a document. 

Button to click with 

your pointing device to 

perform a specific 

operation. 

A file or directory 

name. 

Text that the computer 

presents, rather than 

text you enter yourself. 

Literal text that you 

enter yourself, on the 

screen 

This is the Overview chapter. 

Click CONFIG. 

c:/etc/test/stuff.txt 

Hostname? 

Type fwconfig to configure the firewall. 


xiii

WARNING: Shows critical information which, if 

ignored, could cause injuries to you or to other 

people. 

NOTE: A Note calls special attention to important information. 

xiv 


CHAPTER 1 

Overview 

The Nokia IP100 Series of low cost IP network applications platforms 

(NAPs) provides secure network access for small-size to medium-size 

organizations. IP100 Series NAPs are compact and also easy to install, 

configure, and use. 

The Nokia operating system (IPSO) is built into the IP100 Series. The 

series also comes with Voyager, a web-based NAP-management 

application. 

IP100 Series Installation Guide 1

Organization of Installation Guide 

The three chapters of this guide have the following organization: 

• This chapter describes the features of IP100 Series NAPs. 

• Chapter 2 explains how to connect an IP100 NAP to your network. 

• Chapter 3 shows how to configure the NAP. 

Appendices provide the following additional technical information: 

• Appendix A: Technical Specifications 

• Appendix B: Cables 

• Appendix C: Using Boot Manager 

• Appendix D: Warranty and License for Nokia Software 

• Appendix E: General Public Licensed Software 

• Appendix F: Troubleshooting 

WARNING: The IP100 Series NAP has no userreplaceable 

or user-serviceable parts. Only 

authorized service personnel should open the unit. 

2 IP100 Series Installation Guide

Hardware 

Hardware 

Figure 1-1 shows an overall view of an IP100 Series NAP. Later figures 

provide more details about each orientation (top, rear, and so forth). 

Figure 1-1. Overall view of NAP 


Features 

NAPs in the IP100 Series have the following features: 

• Three 10/100 base-T ethernet interfaces (the IP110) 

• Two EIA-232 serial ports 

• A RESET button that generates a system reset. 

• A 5-volt DC (110/220 volt AC) power supply (part number 

NCZ3023FRU) 

• The NAPs can be placed on a table or mounted on the wall 

• Up to three NAPs can be stacked on top of one another. 

For more detailed technical information, see APPENDIX A, Technical 

Specifications. For information about stacking and wall mounting, see 

CHAPTER 2, Installing the Hardware. 

IP100 Series NAPs come with the following: 

• A null-modem cable with DB-9 connectors, for connecting a console 

to the unit. In Chapter 2, see Step 2—Connecting a Console. 

• A power cord appropriate for the country in which the unit was 

purchased. In Chapter 2, see Step 1—Connecting the NAP to a 

Power Source. 

• Two number 10 cross-head screws, with anchors and standoffs, for 

mounting the unit on a wall. 


Features 

Rear Panel 

Figure 1-2 shows the rear panel of an IP100 Series NAP. 

Figure 1-2. Rear panel of NAP 

The rear panel has: 

• RJ-45 shielded connectors for each network interface. Connector 

labels indicate the types of interfaces. 

• Two ports with DB-9 connectors. One (AUX) is for connecting an 

external modem or another NAP to the unit. The other (CONSOLE) is 

for connecting a terminal to the unit. 

• A connector for the power supply. The connector is labeled POWER 

and has a universal power symbol. 

• A reset button. 


Top 

Figure 1-3 shows the top of an IP100 Series NAP. 

Figure 1-3. Top view of NAP 

The three pairs of LEDs at the right of the unit correspond to the three 

network connectors on the rear panel. They are labeled accordingly. The 

top LED (ACTIVE) is yellow and flashes on and off to indicate network 

activity. The bottom LED (LINK) is green when there is a network 

connection. When there is no network connection, the LED does not glow 

at all. 


Features 

The LEDs on the left are labeled FAULT and POWER, with a universal 

power symbol above the LEDs. The POWER LED is green when the unit 

is receiving power. The FAULT LED is red when there is a system failure 

or abnormal condition. 

Bottom 

Figure 1-4 shows the bottom of the NAP. 

Figure 1-4. Bottom view of NAP 


As Figure 1-4 indicates, the bottom of the unit has: 

• Four sets of ventilation slots 

• A rubber cushion at each corner, for placing the unit on a desk or 

table or stacking NAPs on top of one another 

• Two keyhole slots for mounting the unit on a wall 


Site Requirements 

Site Requirements 

Before installing the unit, ensure that the location where you intend to 

place the unit conforms to the environmental specifications listed in 

APPENDIX A, Technical Specifications. 

WARNING: For NAPs intended for shipment outside 

North America, the cord set may be optional. If a 

cord set is not provided, use a power cord rated at 

6A, 250V, maximum 3 meters long, made of HAR 

cordage and IEC fittings approved by the 

country of end use. 

WARNING: There is danger of explosion if the 

battery is incorrectly placed. Replace only with the 

same or equivalent type recommended by the 

manufacturer. Dispose of used batteries according 

to the manufacturer’s instructions. 



CHAPTER 2 

Installing the Hardware 

This chapter describes how to install an IP100 Series NAP and how to 

connect it to a network. It also explains how to connect an external 

modem to the NAP, as an alternative way of accessing the NAP from a 

remote location. 


Placement of IP100 Series NAP 

By Itself on Desk or Table 

You can place an IP100 Series NAP on a desk, table, or other flat surface. 

Stacking 

You can stack up to three NAPs on top of one another (Figure 2-1). 

Figure 2-1. Three NAPs stacked on top of one another (rear view) 



Use the following procedures when stacking IP100 Series NAPs: 

• Do not remove the rubber feet on the bottom of an NAP. They keep 

the NAPs from sliding against each other and ensure proper 

ventilation and stability. 

• Provide sufficient clearance under the NAPs to allow air to move 

through the components. 

WARNING: Do not block any ventilation slots on the 

NAP. Internal components may overheat and be 

damaged. 

Wall Mounting 

You can mount an IP100 Series NAP on a wall by using the two keyholes 

slots on the back of the NAP. When mounting the NAP on a wall, the 

front panel should be at the top and the rear panel at the bottom, with 

connecting cables projecting downward from the rear panel. 

Figure 2-2 shows how to mount the NAP on a wall. 


Figure 2-2. Wall mounting of NAP 

To mount the NAP on a wall follow these procedures: 

1. Make sure you have the packet of mounting screws, anchors, and 

standoffs that come with the NAP. 

2. Decide where to mount the NAP. For easy access mount the NAP at 

eye level and in a position where it is visible, isolated from other wall 

mountings, and level. 

3. Place marks where the two mounting screws should go. The distance 

from the center of one keyhole slot to the center of the other is 7.5 

inches (19.05 cm). 

4. Drill a quarter inch (0.635 cm) hole at each mark, to accommodate 

the number 10 cross-head screws that come with the NAP (along with 

two anchors and two standoffs). 



5. Insert an anchor into each hole. Then place a standoff on the end of 

each screw. Turn the screw so that the screw protrudes one quarter 

inch from the wall. 

6. Hold the NAP so that the screws are in the center of the keyholes. 

Push down on the NAP so each screw is lodged firmly into the top of 

each keyhole slot. 

You can re-orient the face plate so it reads from left to right when facing 

the wall-mounted NAP (rather than being upside down). To do this, use 

the following procedures: 

1. Pull the face plate off the unit. The face place is attached with 

adhesive. 

2. Rotate the face plate 180 degrees 

3. Place the face plate back on the unit. Press firmly so it sticks to the 

unit. 

NOTE: The adhesive on the back of the face plate will form a 

permanent bond between the face plate and the unit approximately 

four months from the date on which the face plate is initially 

attached to the unit. After this point it will be impossible to re-orient 

the face plate. 


Connecting the IP100 Series 

To use an IP100 Series NAP you must: 

Step 1—Connect the NAP to a power source 

Step 2—Connect a console to the NAP 

Step 3—Connect the NAP to a network 

Step 1—Connecting the NAP to a Power Source 

Plug the power cord that comes with the NAP into the 5-volt DC adapter. 

Plug the other end into a 3-wire, grounded power source. Then plug the 

adapter into the POWER socket on the rear panel. The POWER LED on 

the front panel should display green. Figure 2-3 shows the NAP 

connected to a power source. 

Figure 2-3. NAP connected to power source 


Connecting the IP100 Series 

Step 2—Connecting a Console 

Use the null-modem console cable (with DB-9 connectors) that comes 

with the NAP to connect one of the following console devices to the 

CONSOLE port on the rear of the NAP: 

• a standard VT100-compatible terminal 

• a DOS or Windows computer running a terminal emulation program 

such as HyperTerminal 

• a UNIX work station running a terminal emulation program such as 

Kermit 

NOTE: The CONSOLE port on the NAP supports a data terminal 

equipment (DTE) interface with 8 data bits, no parity, and 1 stop bit, 

running at 9600 bps. 

Figure 2-4 shows a notebook computer connected to an IP100 Series NAP 

using the console cable. 

Figure 2-4. Notebook computer connected to NAP 


Step 3—Connecting the NAP to a Network 

The next step is to connect the NAP to a network. Figure 2-5 shows the 

three network interfaces on the rear of the NAP. Plug an RJ-45 cable into 

one of the interfaces. Connect the other end to a network connection. 

Figure 2-5. Rear panel of NAP, with network interfaces at left 


Using an External Modem 


You can connect an external modem to the AUX port on the rear of the 

NAP. This allows you to use a remote console to communicate with the 

IP100 Series NAP when you do not have access to the device via a 

console directly connected to the unit or via a network connection. 

Using an external modem involves three steps: 

Step 1—Connecting a modem to the NAP 

Step 2—Configuring the modem 

Step 3—Setting modem command strings 

The last step depends upon which specific modem you use. 

Step 1—Connecting a Modem 

To connect a modem to the NAP, you will need a straight-through serial 

cable, with a DB-9 connector at one end and a modem-appropriate 

connector at the other end. (For cable specifications, see APPENDIX 

B, Cables.) 

Follow these procedures: 

A. Use the cable to connect the modem to the AUX port on the rear 

panel of the NAP. This port is configured to COM2. 

B. Connect the other end of the cable to the modem, using an 

appropriate connector (DB-9 or DB-25). 

C. Connect one end of a telephone cable to the phone line and the 

other to the modem. Figure 2-6 shows an external modem 

connected to the NAP. 


Figure 2-6. External modem connected to NAP 

Step 2—Configuring a Modem 

Before setting the command strings appropriate to the specific modem 

you have, do the following: 

A. In Voyager, under Network Access and Services, make sure 

Allow COM2 Access is set to Yes. 

B. Locate this file: 

/etc/ttys 

An example of this file is reproduced on the next page. 



# This file was AUTOMATICALLY GENERATED 

# Generated by ttys_xlate on Mon Jul 31 15:36:49 2000 

# 

# DO NOT EDIT 

# 

console none 

unknown off secure 

# 

ttyv0 "/usr/libexec/getty Pc" cons25 on secure 

# Virtual terminals 



ttyv3 "/usr/libexec/getty Pc" cons25 off secure 

# Serial terminals 

ttyd0 "/usr/libexec/getty std.9600" vt100 on secure 

ttyd1 "/usr/libexec/getty modem.9600" unknown on secure 

ttyd2 "/usr/libexec/getty modem.9600" unknown off secure 



# Pseudo terminals 

ttyp0 none network secure 




ttys: unmodified: line 1. 


C. Locate the four lines that start with ttyd. These lines 

(highlighted in the example above) are ttyd1, ttyd2, 

ttyd3, and ttyd4. 

D. In each of the four lines, change 9600 to 38400. 

E. Save and close the file. 

F. To terminate and re-initialize the modem configuration process, 

type: 

kill -1 1 

Step 3—Setting Modem Command Strings 

The next step is to set modem AT command strings. Whether or not you 

need to do this and how to do this depends upon the specific modem you 

have. 

Here we explain how to configure two popular fax modems: the US 

Robotics 33.6 Sportster and the Best Data 56K. Your modem may follow 

one of these patterns. 

US Robotics 33.6 fax modem 

For a US Robotics 33.6 fax modem, follow these procedures: 

A. Use a terminal emulator such as HyperTerminal to enter this AT 

command string. (Do not allow the terminal emulator to 

configure the modem by itself because this may alter some 

needed settings.) 

AT B0 F1 M1 X1 Y0 &A1 &B0 &G0 &H1 &I0 &K1 &M4 

&N6&P0 &R2 &S0 &T5 &U6 &Y1S0=1 &W0 



Table 2-1 shows the meanings of some of these commands. 

Table 2-1. US Robotics AT Commands 

Command Meaning 

Y0 

Load profile 0 from VRAM 

&B 

Set serial port data rate to modem to modem 

connection rate 

&H1, &IO, &R2 Set appropriate flow control 

&N6, &U6 Set connection to 9600 bps 

S0=1 Answer after one ring 

&W0 

Write settings for profile 0 to NVRAM 

B. Set the DIP switches as shown in Table 2-2. 

Table 2-2. US Robotics DIP Switches 

DIP Switch Position Meaning 

1 Down Override DTR 

5 Up Answer incoming calls 

7 Up Load configuration from NVRAM 

instead of using defaults 

8 Down Dumb mode 


Note these points: 

• There is no way to log out the user when the modem disconnects. If 

you disconnect without logging out, the next dial-in user will not have 

to log in. To eliminate this problem, set the autologout parameter 

in the .cshrc file on the NAP to admin. 

• When you first connect to the modem, you might need to press return 

a few times to get a login prompt. 

• If you appear to be experiencing problems with flow control, try 

adding these AT commands: 

&H0 

&R2 

Best Data 56K data fax modem 

For the Best Data fax modem, follow these procedures: 

A. Pass this AT string to the modem: 

AT&F&K4E0Q1S0=1 

After entering this command, you will not see your own typing or 

any response from the modem. 

B. Enter these two strings: 

AT&W0 

AT&Y0 

Table 2-3 shows the meanings of some of these commands. 



Table 2-3. Best Data AT Commands 

Command Meaning 

&F 

Restore values to default settings 

&K4 

Enable XON/XOFF local flow control (computer 

to modem) 

E0 

Disable echo (modem will not display what you 

enter) 

Q1 

Do not return result codes 

S0=1 Answer after 1 ring 

&W0 

Write settings for profile 0 to NVRAM 

&Y0 

Load profile 0 from VRAM 

C. Dial in to the modem. You should get a login prompt. You do not 

need to log out. The session will end if your modem disconnects. 



CHAPTER 3 

Configuring the NAP 

This chapter explains how to configure an IP100 Series NAP. It describes: 

• using the system startup procedure for initial configuration 

• using Voyager to complete the configuration 


Before You Begin 

Before beginning the configuration, be sure you: 

• Connect the NAP to a power source 

• Connect a console to the NAP 

These procedures are explained in CHAPTER 2, Installing the 

Hardware. 

If you are using a computer to perform the initial configuration, you must 

also: 

• Launch a terminal emulation program (such as HyperTerminal) to 

establish communication with the NAP. 

• Use the system startup procedure to begin configuring the NAP. 

System startup is part of the IPSO software that is built into the IP100. 

When you connect with the NAP for the first time, the NAP comes up in 

system startup mode. 

Use system startup to perform the following operations, which are 

explained in the following sections: 

1. Enter a hostname 

2. Enter an administrative password 

3. Enter a browser type 

4. Enter initial interface information 

5. Confirm or change the information you entered 

After completing these steps, use the Voyager web-based configuration 

program to complete configuration of the IP100 Series NAP. 


Using System Startup 


When you first boot up an IP100 Series NAP, the console screen displays 

miscellaneous information (such as memory checks). The following text 

(Figure 3-1) then displays on your screen: 

Syncing disks... done 

Rebooting... 

Verifying DMI Pool Data..... 

1 Bootmgr 

2 IPSO 

Default: 1 

Figure 3-1. Screen that appears when first booting the NAP 

Do nothing when you see this screen. After five seconds the system 

startup procedure automatically starts. 

Step 1—Assigning a Hostname 

System startup first requests a hostname for the NAP. 

At the Hostname? prompt do the following: 

A. Type a hostname. You can use any alphanumeric characters in 

upper or lower case (a-z, 0-9), dashes (–), and dots (.). What you 

type is case sensitive so every time you enter your hostname you 

must enter it in exactly the same way. 

B. Confirm your entry by re-entering it. 


Step 2—Assigning a Password 

There are two types of accounts on the IP100 Series. The admin account 

provides read and write permission. The monitor account provides only 

read permission, which does not allow a user to configure the IP100 

Series NAP. To establish an admin password, do the following: 

A. When system startup asks for a password for the admin account, 

enter a password. (The same rules apply to passwords as to 

hostnames. Passwords must however be at least six characters.) 

B. Confirm your entry by re-entering it. 

Step 3—Selecting a Browser Type 

System startup next asks for the type of browser you plan to use (Figure 

3-2): 

You can configure your system in two ways. 

1) Configure an interface and use our Webbased 

Voyager via remote browser 

2) VT100-based Lynx browser 

Please enter a choice [1-2, q]: 

Figure 3-2. System startup browser screen 

Type the number that corresponds to the type of browser you want to use. 

Option 1 (recommended) enables you to configure the NAP using 

Voyager web-based software. Select this option if you can use a web 

browser to access the NAP over a LAN. 



If you select Option 1, go on to the next section, Step 4—Entering 

Initial Interface Information. Skip the rest of the present section. 

Option 2 (Lynx) allows you to use Lynx to configure the NAP. Lynx is a 

text-based browser that runs on the console itself. Lynx is supplied as part 

of the IPSO software. Use Lynx only if you cannot connect to a LAN. 

If you choose to use Lynx, the system startup procedure asks whether you 

want to start Lynx now. 

A. Type Y (yes) to start Lynx. 

B. Choose Config (the default). 

C. Follow the procedures under Step 4 and Step 5 (below). 

NOTE: You can start Lynx at any time by entering lynx at the 

command prompt. 

Step 4—Entering Initial Interface Information 

A. Select the interface you want to use to access Voyager to 

configure the NAP over a LAN. System startup displays the physical 

IDs of the NAP’s interfaces. For the IP110 NAP, the display looks 

something like Figure 3-3: 

Select an interface from the following for 

configuration: 

1)eth-s1p1 

2)eth-s2p1 

3)eth-s3p1 

Enter choice [1-4]: 

Figure 3-3. System startup interface screen for IP110 NAP 


To select an interface, type the number to the left of its physical 

ID. You will use this interface to access Voyager using a web 

browser in order to perform configuration tasks. 

B. Enter the IP address for the interface you selected. The expected 

format for an IP address is nnn.nnn.nnn.nnn. An example might 

be: 

192.168.231.111 

C. Depending upon your network connection, indicate whether to 

use half duplex or full duplex (half duplex is the default). 

D. Also depending upon your network connection, indicate whether 

to set the interface at 10 Mbits/sec (the default) or 100 Mbits/sec. 

Step 5—Confirming the Setup 

Confirm your entries by typing Y to return to the interface selection menu 

in Step 4. On this menu, type 4 to exit system startup. 

Change your entries by typing N to return to the menu in Step 4. When 

you have finished changing entries, confirm your entries. Then exit 

system startup. 


Using Voyager 

Using Voyager 

Now complete the configuration using Voyager: 

1. Open a web browser on the host machine or system you will use to 

complete the configuration or continue using Lynx. 

2. In the Location field (in Netscape Navigator) or the Address field (in 

Microsoft Internet Explorer) or in a comparable field in another web 

browser, enter the IP address of the interface you configured in Step 

4—Entering Initial Interface Information (192.168.231.111, for 

example). Press ENTER or whatever the browser requires you to do to 

activate your entry. 

3. When prompted, enter the admin username and password. Voyager 

automatically starts. 

Once in Voyager, you can enable Voyager inline help by clicking the HELP 

ON button. The Voyager Reference Guide provides information on 

specific tasks. Access the guide by clicking the DOC button. 

NOTE: If the username dialog does not appear, you may not have 

a network connection between the host and the NAP. Confirm the 

information you entered during this initial configuration and check 

that all cables are firmly connected. See APPENDIX 

F, Troubleshooting for troubleshooting information. 

4. Use Voyager to configure the other interfaces you intend to use on the 

NAP. First click the CONFIG button. Then click the Interfaces link. 

Ethernet physical interfaces appear in this form: 

eth-sxpy 

The x (which is highlighted above) is the slot number and the y (also 

highlighted) is the port number, as in s1p1, or slot 1 port 1. 

Click the interface you want to configure. Set the link speed (10 Mbits/sec 

or 100 Mbits/sec) and duplex mode (full or half) of the interface. The 

default ethernet logical IDs include the channel number of the interface 


(eth-sxpyc0). You can set multiple IP addresses for each ethernet port 

by entering new IP addresses and mask lengths. 


Monitoring IP100 Series Operations 

Monitoring IP100 Series Operations 

After you have configured the NAP, use Voyager to monitor its 

operations. 

Click MONITOR from the Voyager home page to access monitoring 

functions. 



APPENDIX A 

Technical Specifications 

Physical 

Table A-1. Physical Dimensions of IP100 Series NAP 

Dimension U.S. Metric 

Height 2.10 in. 5.33 cm 

Width 9.35 in. 23.75 cm 

Depth 8.34 in. 21.18 cm 

Weight 11.3 oz. 317.8 g 



Environmental 

Table A-2. Environmental Characteristics of IP100 Series NAP 

System Dimension Range 

Temperature Operating 5°C to 40°C 

Storage -40°C to 70°C 

Electrical Input Voltage 100-120/200-240 V 

AC 

Frequency 

50/60 Hz 

Amps 

0.9 A max input; 5 A 

max output 

Pressure 

Maximum Operating 

Altitude 

11,500 ft. (3,500 m.) 


Interfaces 

Interfaces 

Table A-3. Interface Characteristics of IP100 Series NAP 

Interface Description Connector 

Ethernet IEEE 802.3 

10BASE-T, 

100BASE-TX 

Unshielded Twisted- 

Pair, Full-Duplex or 

Half-Duplex 

RJ-45 

Aux Serial Com 2 DB-9 

Console Serial Com 1 DB-9 

External Power 

Supply 

5-pin DIN 



Declaration of Conformity 

according to ISO/IEC Guide 22 and EN 45104 

Manufacturer’s Name: 

Manufacturer’s Address: 

Nokia Corporation 



USA 

declares that the product: 

Product Name: 

Model Number: 

Product Options: 

IP110 

IP0110 

All 

Serial Number: 1 to 100,000 

Year First Applied: 2000 

conforms to the following Standards: 

Safety: 

EN60950:1992, A1, A2:1993, A3:1995, A4:1997, All:1998 

EMC: EN55022B, EN50082-1 (1997) 

Supplementary Information: 

“The product complies with the requirements of the Low Voltage Directive 73/23/EEC and 

the EMC Directive 89/336/EEC with Amendment 93/68/EEC.” 

Alan Hutchinson 

Quality Engineer 

Mountain View, California 

October 2000 


APPENDIX B 

Cables 

Ethernet Crossover Cable 

Use an ethernet crossover cable when directly connecting an ethernet port 

on an IP100 Series NAP to an RJ-45 female connector on a host. 

Figure B-1. Ethernet crossover cable pin connections 


Cables 

The RJ-45 is numbered from left to right with the copper tabs facing up 

and toward you. 

NOTE: Use a straight-through cable (rather than an ethernet 

crossover cable) to connect an ethernet port on an IP100 Series 

NAP to an ethernet hub. 


Null-Modem Cable 

Null-Modem Cable 

Use a 9-pin to 25-pin or 9-pin to 9-pin null-modem cable when directly 

connecting a console to the device. Pin connections for these two 

connectors are shown in Figure B-2 (9-pin to 25-pin) and B-3 (9-pin to 9- 

pin). 

Figure B-2. 9-pin to 25-pin null-modem cable 


Cables 

Figure B-3. 9-pin to 9-pin null-modem cable 


APPENDIX C 

Using Boot Manager 

IP100 Series NAPs incorporate a boot manager in one partition of the 

system disk to control the boot-up process. The boot manager performs a 

number of functions: 

• Provides commands that allow you to boot alternate kernels, possibly 

from alternate NAPs 

• Enables you to install new versions of IPSO (the operating system) 

• Examines the system disk 

• Performs various housekeeping tasks 

When you first boot your IP100 Series NAP, the boot manager uses 

default parameters (kernel, boot device, etc.) for the boot process. The 

defaults cause the NAP to bypass the boot manager’s prompt after a fivesecond 

wait. You can change these defaults to reflect your own needs, or 

you can use different parameters in the command line at boot time. The 

boot manager maintains the default values of these parameters in its disk 

partition. You can set these values using boot manager commands. 

This appendix describes boot manager commands. These are UNIX-type 

commands entered from the console. 



Unless you set the autoboot variable to no, the NAP automatically boots 

IPSO after waiting at the boot manager prompt for the number of seconds 

specified by the bootwait variable. See Variables. 


Variables 

Variables 

A number of variables are stored by the boot manager in non-volatile 

memory. You can set and view most variables from the boot manager 

prompt. 

The variables are: 

boot manager revision: This is the version number of the boot manager. 

This variable cannot be set from the command line. 

autoboot: If autoboot is set to no, the NAP stops at the boot manager 

command line during the boot process. 

If autoboot is set to yes, the NAP does not stop at the boot manager 

command line during a boot up. It does wait for the amount of time 

specified in bootwait for input from the keyboard. If input is received, 

the boot manager goes to the command line; otherwise, it proceeds with 

the boot up. 

Default: yes. 

bootwait: This is the amount of time, in seconds, the boot manager waits 

for input during a boot up when autoboot is set to yes. 

Default: five seconds. 

boot-file: This is the name of the file to be used as the operating system 

kernel. 

Default: /image/current/kernel. 

boot-flags: This is the string of flags that is passed to the kernel. 

Default: none. 

boot-device: This is the device from which the boot-file loads. 

Default: wd0. 

Options: wd0 (hard disk). 

Default: The alias disk is set to wd0. 



Boot flags are shown in Table C-1. 

Table C-1. Boot Manager Boot Flags 

Flag Meaning 

-d 

-s 

-v 

Debug Mode: Enters the kernel debugger as soon as 

possible in the kernel initialization. 

Single-User Mode: If the console is marked as insecure, 

the root password must be entered. 

Verbose Mode: Verbose mode is entered during device 

probing and thereafter. 

Viewing Variables and Other System Parameters 

printenv 

Use the printenv command to view the values of variables currently 

stored in the boot manager’s non-volatile memory. The command has the 

following form: 

printenv 

For example, 

BOOTMGR[4]> set-defaults 

BOOTMGR[5]> printenv 

Bootmgr Revision: 3.3, base kernel= 

3.3-fcs1 11.24.1999-102644 

autoboot: YES 

bootwait: 5 

boot-file: /image/current/kernel 

boot-flags: 

boot-device: wd0 


Variables 

BOOTMGR [6] 

showalias 

Use the showalias command to view the values of the aliases 

currently stored in the boot manager’s non-volatile memory. The 

command has the following form: 

showalias 

For example, 

BOOTMGR[32]> showalias 

The current aliases list are: 

Alias 0: disk aliased to wd0 

Alias 1: disk0 aliased to wd0 



Alias 4: net1 aliased to eth-s1p1 

Alias 5: net2 aliased to eth-s1p2 

Alias 6: 

Alias 7: 

BOOTMGR[33] 

sysinfo 

Use the sysinfo command to view system information such as CPU 

speed, memory size, and so forth. The command has the following form: 

For example, 

sysinfo 

BOOTMGR[35]> sysinfo 

CPU: 267-MHz K6-2 (586-class CPU) 



Origin = “AuthenticAMD” ID = 0x58c 

Memory: 67108864 (65536K bytes) 

Disk devices: 

IO part 1f0 wdc0: unit 0 (wd0): 

Network Interfaces: 

loop0 slot 0 port 1 channel 0 

speed 0 bps MAC addrss 0:0:0:0:0:0 

tun0 slot 0 port 1 channel 0 

speed 0 bps MAC addrss 0:0:0:0:0:0 

eth-s3p1 slot 3 port 1 channel 0 

speed 10000000 bps MAC addrss 

0:a0:8e:7:1c:c8 



0:a0:8e:7:1c:cc 



0:a0:8e:7:1c:d0 

BOOTMGR [36] 

ls 

Use the ls command to view the contents of directories on the devices in 

your unit. The command has the following form: 

ls device directory 

where device is the device containing the directory you want to look at, 

and directory is the directory on that device. Both device and 

directory are optional. The default directory is /image on the wd0 

device. 


Variables 

For example, 

BOOTMGR[2]> ls wd0 /image/current 

device wd0 Directory /image/current: 

VERSION 

description 

kernel 

bin 

cdrom 

... 

Setting Variables 

setenv 

Use the setenv command to set a particular variable. The command has 

the following form: 

setenv name value 

where name is the name of the variable, and value is the new value you 

want the variable to assume. 

For example, 

BOOTMGR[2]> setenv autoboot yes 

sets the value of autoboot to be yes. 



unsetenv 

Use the unsetenv command to clear a particular variable. The 

command has the following form: 

unsetenv name 

where name is the name of the variable to be cleared. 

For example, 

BOOTMGR[2]> unsetenv boot-file 

clears the boot-file variable. 

NOTE: The autoboot variable is set to no, and the bootwait 

variable is set to zero by this command. 

set-defaults 

Use the set-defaults command to set variables to their factorydefault 

values. The command has the following form: 

set-defaults name 

where name is the name of the variable you want to set to its factory 

default. If you do not specify name, all variables are set to their factory 

defaults. 

For example, 

BOOTMGR[2]> set-defaults autoboot 

sets the value of autoboot to be yes, the factory default. 

setalias 

Use the setalias command to set an alias. The command has the 


setalias name device 


Variables 

where name is the alias name, and device the device for which name is the 

alias. 

For example, 

BOOTMGR[2]> setalias disk wd0 

sets the alias disk to have the value of wd0. 

You can have a maximum of eight aliases set at one time. 

unsetalias 

Use the unsetalias command to clear an alias. The command has the 


unsetalias name 

where name is the name of the alias to be cleared. 

For example, 

BOOTMGR[2]> unsetalias disk 

deletes the disk alias from the list of aliases. 

Other Commands 

halt 

Use the halt command to halt the system. The command has the 


halt 

help 

Use the help command to display a list of the available commands. The 

command has the following forms: 

help or ? 



Booting the System 

The boot command lets you boot up the operating system (IPSO). The 

boot command allows you to set the boot device, boot file, and boot 

flags from the command line. 

The command has the following form: 

boot boot-device boot-file boot-flags 

where boot-device is the storage device from which the operating system 

loads at boot up, and boot-file is the operating system kernel. The bootflags 

control the operation of the command. 

For example, at the boot manager command prompt enter: 

BOOTMGR[0]> boot wd0 /image/current/mykernel 

-vd 

This command boots mykernel from disk wd0 in verbose and debug 

mode. 

You can supply all, any, or none of the arguments. If you do not supply an 

argument, the boot manager uses its default, as shown in Table C-2. 

Table C-2. Boot Manager Argument Defaults 

Argument 

Default 

boot-device 

wd0 (the hard disk) 

boot-file 

/image/current/kernel 

boot-flags 

none 

Boot Manager first searches its non-volatile memory to see if the 

corresponding default argument is specified there. If so, it uses that value; 

if not, it uses these defaults. 


Installing IPSO Using the Boot Manager 

Installing IPSO Using the Boot Manager 

The form of the install command is: 

install 

NOTE: Refer to the appropriate version of release notes for 

complete installation procedures. 

NOTE: A full installation using the install command deletes the 

existing database on the unit. 

To install a new copy of the operating system (IPSO) kernel using the 

boot manager, perform the following steps. 

1. At the boot manager command prompt, enter the following: 

BOOTMGR[0]>install 

If you have used the passwd command to protect this procedure, the 

boot manager asks you for your password before allowing you to 

execute the install command. 

2. Enter the information the install command requests (your 

system’s IP address, the server’s IP address, and other information). 

3. Reboot the NAP. 



Protecting the Boot Manager With a Password 

To prevent accidental or unauthorized access to the hard disk on your 

IP100 Series NAP, you can require that the user enter a password to 

access the install command in boot manager. Use the passwd 

command to set the password. 

NOTE: The password you enter here is the password that gives 

you access to the install command in boot manager, not 

access to IPSO. 

To set a password, perform the following steps: 

1. At the boot manager command prompt, enter the following: 

BOOTMGR[0]> passwd 

The passwd program asks you for your current password. 

2. If the NAP is protected by a password, enter your current password. 

3. The program asks you for the new password. Enter the new 

password.. 

4. The program asks you to re-enter the new password for verification. 

Enter the new password again. 


Upgrading the Boot Manager 

Upgrading the Boot Manager 

The command to upgrade your boot manager has the following form: 

upgrade_bootmgr boot-device boot-file 

where boot-device is the storage device from which the boot manager 

loads at boot up and boot-file is the new boot manager image. The new 

boot manager options are cpipflash, cpvpnflash, 

skipflash, and nkvpnflash. Execute the upgrade_bootmgr 

command from IPSO, not from the boot manager. 

NOTE: Refer to the appropriate version of release notes for 

complete upgrade procedures. 

To upgrade the boot manager, perform the following steps: 

1. Get the upgraded boot manager image from the appropriate Nokia 

customer support site as listed in the Nokia Contact Information 

section at the front of this guide. 

2. At the IPSO command prompt, enter the following: 

/etc/upgrade_bootmgr wd0 /etc/nkipflash 

The command upgrades the boot manager with the new image 

(nkipflash), writing it into the boot manager partition. The 

upgrade takes some time to complete. Please do not interrupt the 

upgrade process. 




APPENDIX D 

Limited Warranty and Terms and 

Conditions of Software License for 

Nokia Software 

THE TERMS AND CONDITIONS SET FORTH ON THIS 

DOCUMENT CONSTITUTE THE ENTIRE AGREEMENT BETWEEN 

Nokia, Inc., A DELAWARE CORPORATION (“NOKIA”), AND 

CUSTOMER IN RESPECT OF THE NOKIA SOFTWARE INCLUDED 

IN THE PRODUCT PACKAGE, INCLUDING ANY 

DOCUMENTATION THERETO (the "SOFTWARE"). NOKIA WILL 

NOT BE BOUND BY ANY TERMS OF ANY PRIOR AGREEMENT 

OR UNDERSTANDING THAT ARE INCONSISTENT WITH THE 

TERMS HEREIN. THE SOFTWARE IS LICENSED ONLY ON THE 

CONDITION THAT THE CUSTOMER ACCEPTS THE TERMS OF 

THIS AGREEMENT. BY OPENING THE PACKAGE AND/OR BY 

MAKING USE OF THE ENCLOSED SOFTWARE YOU AGREE TO 

BE BOUND BY THE TERMS OF THIS AGREEMENT. IF YOU DO 

NOT AGREE TO THE TERMS OF THIS AGREEMENT PLEASE 

IMMEDIATELY RETURN THE SOFTWARE IN THE PRODUCT 

PACKAGE TO THE PLACE YOU PURCHASED IT FOR FULL 

REFUND. 

1. SOFTWARE LICENSE. Unless Customer is an approved Managed 

Service Provider, Nokia grants to Customer a personal, nonexclusive and 

nontransferable license to use the Software in object code form solely as 

embedded in equipment provided by Nokia. If Customer is an approved 


Limited Warranty and Terms and Conditions of Software License for Nokia Software 

Managed Service Provider ("MSP"), Nokia grants a nonexclusive and non 

transferable license to demonstrate the Software to clients and prospective 

clients in order to market MSP's managed services and to use the Software to 

provide managed services provided that each copy of the Software is used 

solely on behalf of and for the benefit of a single client on the single piece of 

equipment provided by Nokia. An MSP may discontinue use of the Software 

on behalf of one client and use the Software to provide managed services to 

another single client. 

Customer may make one (1) archival copy of the Software provided 

Customer affixes to such copy all copyright, confidentiality and 

proprietary notices that appear on the original. Customer shall not 

otherwise, in whole or in part, copy the Software or documentation; 

modify the Software or create derivative works thereof; reverse 

compile or reverse assemble all or any portion of the Software; rent, 

lease, distribute, sell, or use for time-sharing purposes, the Software; 

or use or allow the Software to be used for the direct benefit of any 

third party. Any fixes, updates or new releases of the Software, which 

may be made available to Customer, shall be deemed part of the 

"Software," subject to the restrictions and limitations contained in this 

license. 

2. PROPRIETARY RIGHTS. All right, title and interest in and to the 

Software and documentation, and any copies thereof provided by 

Nokia or which may be made by Customer, are and shall remain the 

exclusive property of Nokia or Nokia’s licensors (Nokia and its 

licensors are collectively referred to as “Software Owners”). Each 

Software Owner shall have the right to enforce this Agreement 

against the Customer as to such Software Owner’s Software. 

3. LIMITED WARRANTY. 

3.1 Software Warranty. Nokia warrants that the Software will 

substantially conform to the published specifications for a period of 

ninety (90) days, plus a thirty (30) day transit allowance, from the 

date of shipment. If the Software is found to contain a substantial 

nonconformance, Nokia’s sole obligation under this warranty shall 

be, at Nokia’s option: (a) to correct, or provide a "work around" for 

any material programming error or defect in the Software, or (b) to 

refund to Licensee the purchase price paid and this Agreement shall 

terminate. 


3.2 Warranty Services. In the event of a warranted problem with 

respect to the Software, Customer shall call its reseller for warranty 

services. All repair services are provided by Nokia's authorized 

reseller from whom the Customer has purchased the product on 

which the Software is imbedded. 

3.3 Exclusions. The above warranty does not apply if the Software 

or the equipment on which it resides (1) has been altered, except as 

authorized by Nokia, (2) has not been installed, operated, repaired or 

maintained in accordance with any installation, handling, 

maintenance or operating instructions supplied by Nokia, (3) has been 

subjected to unusual physical or electrical stress, misuse, negligence 

or accident, (4) has been used in ultra-hazardous activities, or (5) has 

been used in such a way that Nokia cannot reasonably reproduce the 

Software error. Furthermore, the above warranty does not apply to 

any portion of the product supplied by a third party. In no event does 

Nokia warrant that the Software is error-free or that the Customer will 

be able to operate it without problems or service interruptions. 

3.4 DISCLAIMER. THE WARRANTY ABOVE IS IN LIEU OF, 

AND NOKIA DISCLAIMS, ALL OTHER WARRANTIES AND 

CONDITIONS, EXPRESSED OR IMPLIED, INCLUDING THOSE 

OF MERCHANTABILITY, FITNESS FOR A PARTICULAR 

PURPOSE, QUALITY, NON-INFRINGEMENT, NON- 

INTERRUPTION OF USE, FREEDOM FROM BUGS OR 

OTHERWISE. NO DEALER OR RESELLER IS AUTHORIZED 

TO MAKE ANY MODIFICATIONS, EXTENSIONS, OR 

ADDITIONS TO THIS WARRANTY. NOKIA SPECIFICALLY 

DISCLAIMS ANY WARRANTY FOR THIRD PARTY 

SOFTWARE SUPPLIED WITH THE PRODUCT. 

4. LIMITATION OF LIABILITY. IN NO EVENT WILL NOKIA, 

ITS SUPPLIERS OR RESELLERS BE LIABLE UNDER ANY 

CONTRACT, NEGLIGENCE, STRICT LIABILITY, TORT OR 

OTHER THEORY FOR DIRECT, SPECIAL, CONSEQUENTIAL, 

INCIDENTAL OR INDIRECT DAMAGES (INCLUDING 

WITHOUT LIMITATION LOSS OF PROFIT OR DATA), 

WHETHER OR NOT THEY BEEN ADVISED OF THE 

POSSIBILITY OF SUCH LOSS. IN THE EVENT THAT ANY 

EXCLUSION CONTAINED HEREIN SHALL BEHELD TO BE 



INVALID FOR ANY REASON AND NOKIA BECOMES LIABLE 

FOR LOSS OR DAMAGE THAT MAY LAWFULLY BE LIMITED, 

SUCH LIABILITY SHALL BE LIMITED TO THE PURCHASE 

PRICE. THESE LIMITATIONS SHALL APPLY 

NOTWITHSTANDING ANY FAILURE OF ESSENTIAL 

PURPOSE OF ANY LIMITED REMEDY. SOME STATES DO NOT 

ALLOW THE LIMITATION OR EXCLUSION OF CERTAIN 

LIABILITIES OR DAMAGES, SO THE ABOVE LIMITATION OR 

EXCLUSION MAY NOT APPLY TO CUSTOMER BY LAW. 

5. EXPORT RESTRICTIONS. Customer shall not export or transmit, 

directly or indirectly, the Software or any technical data (including 

processes and services) received from Nokia, nor the direct product 

thereof, outside of the United States without prior authorization of the 

U.S. Government if such authorization is required. Customer shall 

obtain all licenses, permits and approvals required by any 

government. Customer agrees to comply with all export laws, rules, 

policies, procedures, restrictions and regulations of the Department of 

Commerce or other United States or foreign agency or authority, and 

not to export, or allow the export or reexport of any goods in violation 

of any such restrictions, laws or regulations. Customer will indemnify 

and hold harmless Nokia for any violation or alleged violation by 

Customer of such laws, rules, policies, procedures, restrictions or 

regulations. 

6. CONFIDENTIAL INFORMATION. Customer agrees that aspects 

of the Software and documentation, including the specific design and 

structure of individual programs and the composition of the whole, 

constitute trade secrets and/or copyrighted material of Nokia. 

Customer shall not itself, nor shall Customer permit others to, 

disclose, provide, or otherwise make available such trade secrets or 

copyrighted material in any form to any third party without the prior 

consent of Nokia. Customer agrees to implement reasonable security 

measures to protect such trade secrets and copyrighted material. The 

obligations of confidentiality shall not apply to information, which 

has entered the public domain except where such entry is the result of 

Customer’s breach of this Agreement. 


7. FORCE MAJEURE. Nokia shall not be liable for any delay or 

failure in performance whatsoever due to reasons beyond its 

reasonable control. 

8. TERM AND TERMINATION. This Agreement is effective until 

terminated. The license to the Software granted by Nokia will 

terminate upon any attempt by Customer to transfer or assign the 

Software, this Agreement or any rights or obligations hereunder 

without Nokia’s prior written consent. In addition, Nokia may 

terminate this Agreement effective fifteen (15) days following the 

giving of written notice to Customer upon the occurrence of 

Customer's failure to perform any of its existing or future obligations 

hereunder if such breach shall remain uncured. Upon termination, 

Customer shall cease all use of the Software and shall destroy or 

return to Nokia the original(s) and all copies of the Software and 

documentation made or furnished hereunder. Customer may 

terminate the License at any time by destroying all copies of the 

Software and documentation. The provisions of Sections 2, 4, 6, 9, 

and 10 shall survive any termination. 

9. APPLICABLE LAW. This Agreement shall be governed by and 

construed in accordance with the laws of the State of California and 

the United States without regard to conflicts of laws provisions 

thereof and without regard to the United Nations Convention on 

Contracts for the International Sale of Goods. To the extent permitted 

by law, the parties waive any and all rights, privileges and obligations 

which may derive from any codification of the body of law generally 

referred to as the "Uniform Commercial Code". 

10. MISCELLANEOUS. No waiver of rights under this Agreement by 

either party shall constitute a subsequent waiver of this or any other 

right under this Agreement. In the event that any of the terms of this 

Agreement become or are declared to be illegal by any Court of 

competent jurisdiction, such term(s) shall be null and void and shall 

be deemed deleted from this Agreement. All remaining terms of this 

Agreement shall remain in full force and effect. In the event of a 

breach of this Agreement, the breaching party shall pay to the other 



party any reasonable attorneys’ fees and other costs and expenses 

incurred by the non-breaching party in connection with the 

enforcement of any provisions of this Agreement. 

If the Software is licensed to a U.S. Governmental user, the following 

shall apply. The Software and documentation licensed in this 

agreement are “commercial items” and are deemed to be “commercial 

computer software” and “commercial computer software 

documentation.” Consistent with the Federal Acquisition Guidelines 

and related laws, any use modification, reproduction, release, 

performance, display, or disclosure of such commercial software or 

commercial software documentation by the US. Government shall be 

governed solely by the terms of this Agreement and shall be 

prohibited except to the extent expressly permitted by the terms of 

this Agreement. 


APPENDIX E 

General Public Licensed Software 

Nokia, Inc. offers to provide machine-readable source code on industrystandard 

media to the recipient of the Nokia, Inc. modified READLINE 

and GDB code for a period of three (3) years from the date of Nokia, 

Inc.’s distribution of READLINE and GDB, or until January 1, 2003, 

whichever is longer. Alternatively, the Nokia, Inc. modified source code 

may be downloaded from ftp://ftp.iprg.nokia.com/pub/GNU/. All 

requests for code on media shall be accompanied by: 

• address of requester 

• a check for $25 payable to Nokia, Inc. 

Address all such requests to: 

Director of Customer Support 

Nokia, Inc. 

313 Fairchild Drive, 


All other General Public Licensed files that accompany READLINE and 

GDB are available at the above-mentioned ftp site or on media by request 

as stated above. 



GNU GENERAL PUBLIC LICENSE 

Version 2, June 1991 

Copyright (C) 1989, 1991 Free Software Foundation, Inc. 

59 Temple Place - Suite 330, Boston, MA 02111-1307, USA 

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not 

allowed. 

Preamble 

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU 

General Public License is intended to guarantee your freedom to share and change free software--to make sure the 

software is free for all its users. This General Public License applies to most of the Free Software Foundation's 

software and to any other program whose authors commit to using it. (Some other Free Software Foundation 

software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too. 

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to 

make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), 

that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new 

free programs; and that you know you can do these things. 

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to 

surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the 

software, or if you modify it. 

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all 

the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show 

them these terms so they know their rights. 

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you 

legal permission to copy, distribute and/or modify the software. 

Also, for each author's protection and ours, we want to make certain that everyone understands that there is no 

warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to 

know that what they have is not the original, so that any problems introduced by others will not reflect on the 

original authors' reputations. 

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that 

redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To 

prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. 

The precise terms and conditions for copying, distribution and modification follow. 

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 

This License applies to any program or other work which contains a notice placed by the copyright holder saying it 

may be distributed under the terms of this General Public License. The "Program", below, refers to any such 

program or work, and a "work based on the Program" means either the Program or any derivative work under 

copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications 

and/or translated into another language. (Hereinafter, translation is included without limitation in the term 

"modification".) Each licensee is addressed as "you". 

Activities other than copying, distribution and modification are not covered by this License; they are outside its 

scope. The act of running the Program is not restricted, and the output from the Program is covered only if its 

contents constitute a work based on the Program (independent of having been made by running the Program). 

Whether that is true depends on what the Program does. 

1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, 

provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and 

disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and 

give any other recipients of the Program a copy of this License along with the Program. 

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty 

protection in exchange for a fee. 


GNU GENERAL PUBLIC LICENSE 

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the 

Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you 

also meet all of these conditions: 

*a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of 

any change. 

*b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the 

Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. 

*c) If the modified program normally reads commands interactively when run, you must cause it, when started 

running for such interactive use in the most ordinary way, to print or display an announcement including an 

appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and 

that users may redistribute the program under these conditions, and telling the user how to view a copy of this 

License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your 

work based on the Program is not required to print an announcement.) 

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from 

the Program, and can be reasonably considered independent and separate works in themselves, then this License, 

and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the 

same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the 

terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every 

part regardless of who wrote it. 

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, 

the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. 

In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on 

the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this 

License. 

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable 

form under the terms of Sections 1 and 2 above provided that you also do one of the following: 

*a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under 

the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, 

*b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than 

your cost of physically performing source distribution, a complete machine-readable copy of the corresponding 

source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software 

interchange; or, 

*c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This 

alternative is allowed only for noncommercial distribution and only if you received the program in object code or 

executable form with such an offer, in accord with Subsection b above.) 

The source code for a work means the preferred form of the work for making modifications to it. For an executable 

work, complete source code means all the source code for all modules it contains, plus any associated interface 

definition files, plus the scripts used to control compilation and installation of the executable. However, as a special 

exception, the source code distributed need not include anything that is normally distributed (in either source or 

binary form) with the major components (compiler, kernel, and so on) of the operating system on which the 

executable runs, unless that component itself accompanies the executable. 

If distribution of executable or object code is made by offering access to copy from a designated place, then offering 

equivalent access to copy the source code from the same place counts as distribution of the source code, even though 

third parties are not compelled to copy the source along with the object code. 

4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. 

Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically 

terminate your rights under this License. However, parties who have received copies, or rights, from you under this 

License will not have their licenses terminated so long as such parties remain in full compliance. 

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you 

permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do 

not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), 

you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or 

modifying the Program or works based on it. 



6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives 

a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. 

You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not 

responsible for enforcing compliance by third parties to this License. 

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited 

to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the 

conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as 

to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a 

consequence you may not distribute the Program at all. For example, if a patent license would not permit royaltyfree 

redistribution of the Program by all those who receive copies directly or indirectly through you, then the only 

way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. 

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the 

section is intended to apply and the section as a whole is intended to apply in other circumstances. 

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest 

validity of any such claims; this section has the sole purpose of protecting the integrity of the free software 

distribution system, which is implemented by public license practices. Many people have made generous 

contributions to the wide range of software distributed through that system in reliance on consistent application of 

that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other 

system and a licensee cannot impose that choice. 

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted 

interfaces, the original copyright holder who places the Program under this License may add an explicit 

geographical distribution limitation excluding those countries, so that distribution is permitted only in or among 

countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this 

License. 

9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time 

to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new 

problems or concerns. 

Each version is given a distinguishing version number. If the Program specifies a version number of this License 

which applies to it and "any later version", you have the option of following the terms and conditions either of that 

version or of any later version published by the Free Software Foundation. If the Program does not specify a version 

number of this License, you may choose any version ever published by the Free Software Foundation. 

10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are 

different, write to the author to ask for permission. For software which is copyrighted by the Free Software 

Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be 

guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the 

sharing and reuse of software generally. 

NO WARRANTY 

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE 

PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED 

IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" 

WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT 

LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 

PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH 

YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY 

SERVICING, REPAIR OR CORRECTION. 

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY 

COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE 

PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, 

SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY 

TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING 

RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF 

THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER 

PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 

END OF TERMS AND CONDITIONS 


APPENDIX F 

Troubleshooting 

This appendix lists problems you might encounter with an IP100 Series 

NAP, potential causes for these problems, and possible solutions. 

The last section of this appendix provides information about using the 

tcpdump program in troubleshooting. 

The material is organized in terms of broad problem areas, with specific 

problems (and categories of problems) listed within each area. Often there 

is more than one possible cause and solution for a problem. Sometimes 

you may need to contact Nokia Customer Support. For information on 

how to do so, see NOKIA CONTACT INFORMATION on page iv. 

The four broad problem areas covered in this appendix are: 

• Access and login problems 

• Interface problems 

• Connectivity problems 

• Routing problems 



Access and Login Problems 

Problem 

Unable to log in to Console port 

Possible Cause 

The console is incorrectly connected to the unit. 

Possible Solution 

For instructions on creating and configuring a console connection, in 

Chapter 2, see Step 2—Connecting a Console on page 17. 


The console is not connected to the unit with a null-modem cable. 


Make sure that you are using a null-modem cable. See APPENDIX 

B, Cables. 


The terminal settings are incorrect. 


Make sure that the terminal settings are: 8 data, 1 stop, no parity, 9600 

bps, no flow control. 


The unit or file system is defective. 




Contact Nokia Customer Support. 


The database is corrupted. 



Problem 

Receive login prompt, but password 

not accepted 


You have entered the wrong password. 


Enter a correct password. 

You can find the procedure for changing the admin password in the 

Nokia Knowledge Base by contacting Nokia Customer Support. 


Return the database to the default settings and then run through the 

system-startup procedure again. (The system-startup procedure is 

described in CHAPTER 3, Configuring the NAP.) 

1. Log into the NAP as admin with Voyager. 

2. Under Configuration Database Management (Config|System 

Configuration|Manage Configuration Sets), you see an option to 

create a new default configuration. 



3. Create the new default configuration. 

Problem 

No login prompt 


The unit is defective. 



Troubleshooting Tips 

Use the full installation procedure to install a new system. The new 

system completely replaces the contents of the drive. This may be 

needed to restore or reload an NAP. This procedure erases the database 

on the NAP. Contact Nokia Customer Support. 

Problem 

Unable to connect to Voyager using 

network port 


You are using the wrong network cable. 


Use a crossover ethernet cable if you are connecting directly to the PC. 

Use a straight-through cable if you are connecting to a hub. See 

APPENDIX B, Cables. 




The port is not enabled. 


View the port in lynx through the console port and verify that the 

interface is configured as active and up. 


The host port configuration is incorrect. 


Check host ethernet port settings. Verify that IP address and netmask 

settings are correct for the unit’s configuration. 


The link speed is wrong. 


Verify that the port on the host and the port on the IP100 Series NAP 

are set for the same speed (10 Mbps/100 Mbps). A solid data/activity 

LED on a port indicates a speed mismatch. 


The duplex setting is wrong. 


Correct the duplex setting (Full/Half). Hubs use half duplex. Switches 

use full duplex. 



Interface Problems 

Problem 

Local NAP ports do not appear in 

Voyager 


Your NAP may be defective. 



Problem 

No link light appears when you 

connect the port 


You may have used the wrong cable. 


Use a crossover cable between the IP100 Series NAP and a host, and a 

straight-through cable between the NAP and a hub. 

Problem 

Activity light is continuously on 


The port speed may be incorrect. 


Interface Problems 


Make sure that the speeds on each end of the ethernet connection are 

the same (10 Mbps or 100 Mbps). 


The port is not enabled. 


Make sure that the interface is configured as active in Voyager’s 

Interface page. 

Problem 

High collision rate on the hub 


There is a problem with one or more connections. 


To localize the problem, disconnect the network cables one at a time 

until you identify the source of the problem. Then troubleshoot further. 



Connectivity Problems 

Problem 

Unable to ping through the unit 


Localize the problem by issuing pings to various network interfaces on 

the IP100 Series NAP. Use tcpdump to trace packets leaving or 

entering a port. (See Viewing Packets With tcpdump for further 

information.) 


The interfaces are not enabled. 


Ensure that all interfaces are active and up, as described in CHAPTER 

3, Configuring the NAP. 


No route exists to the network. 


Check the routing table in Voyager to see if a route exists to the 

network where the interface is located. If no route exists, see Routing 

Problems, below. 


The routing information for the attached NAP is incorrect. 


Connectivity Problems 


Correct the routing information. 


The default routing information for the attached NAP is incorrect. 


Correct the default routing information. 


The ARP table contains incorrect information. 


Use Voyager to correct the information in the ARP table: 

1. Click CONFIG. 

2. Click the ARP link in the Interfaces section. 

3. Click the Display or Remove Dynamic ARP Entries link. 

4. Click the Delete box for the entry you want to delete. 

5. Click APPLY. 



Routing Problems 


There are several useful tools to help you troubleshoot routing 

problems. The Monitor page in Voyager displays routing statistics and 

errors. The iclid command also displays this information. 

NOTE: Adding a ? after any command provides additional 

command information. 

hostname[admin]# iclid 

host name | IP address> 

host name | IP address>? 

exit get help quit show 

host name | IP address> 

hostname | IP address> show ? 

addressiprpmemoryrip 

bgp inbound-filtermfcroute 

bootpgwinterfaceospfversion 

dvmrp iphelperredistributionvrrp 

igmp krtresource 

hostname | IP address> show route ? 

aggregatebgpigrpospf 

staticall directinactive 

rip summary 

hostname | IP address> show route ospf 

Codes:C - connected, S - static, I - IGRP, 

R - RIP, B - BGP,O - OSPF, E - OSPF external, 

A - Aggregate,K - Kernel Remnant,H - Hidden 

S - Suppressed 



Here is an example of screen output: 

O 172.16/16 via 10.1.1.225, eth-sp4plcO, 

cost 3, age 3111 

Several trace options are also available. These can be enabled in Routing 

Options in the Routing Configuration section in Voyager. When you 

enable a trace, the output appears in /var/tmp/ipsrd.log. 

Problems with OSPF 


Use tcpdump to view routing information. To display routing updates 

for specific interlaces, use this command: 

tcpdump -i logical interface name proto ospf 

(See Viewing Packets With tcpdump for more information about using 

the tcpdump command.) 

Under Routing Options in the Routing Configuration section in 

Voyager, you can also enable several types of trace options for OSPF. 

These traces are logged in /var/tmp/ipsrd.log. 

Problem 

OSPF does not operate 


OSPF is not configured. 


Verify that OSPF is properly configured for all interfaces that are 

involved in OSPF routing. For more information, view Configuring 

OSPF from the Configuring Routing page (press the DOC button) in 

Voyager. 



OSPF hello and dead timers are not the same on each interface for a 

given link. 


Verify that the settings at the end of each link are identical. 


The attached NAPs do not support OSPF. 


Ensure that the attached NAPs support OSPF. If the attached NAP 

does not support OSPF, configure it with a protocol that the NAP 

supports and exchange routes with OSPF or set a default or static 

route. 

Problems with RIP 


Use tcpdump to view routing information. Use this command to 

display routing updates for a specific interface: 

tcpdump -i logical interface name proto rip 

(See Viewing Packets With tcpdump for more information on using the 

tcpdump command.) 


Voyager, you can enable several types of trace options for RIP. These 

traces are logged in /var/tmp/ipsrd.log. 


Inconsistent subnet masks are in use on the network. 




RIP version 1 must use consistent subnet masks. If you need to use 

inconsistent subnet masks, change to RIP version 2 or OSPF. 


The number of networks exceeds the limit for RIP, which is 16 

networks. 


Verify that your network topology does not exceed this limit. 

Problems Exchanging Routes 


Always enter a metric value if you are exporting routes from OSPF to 

RIP. 


Exchanging routes is not configured correctly. 


Exchanging routes involves several configuration steps. Follow the 

tasks in the Voyager Reference Guide (click DOC) to ensure that all 

steps are followed. 



Problems With Multicast 


Use tcpdump to view packets. To display packets for a specific 

interface, use this command: 

tcpdump -i logical interface name proto igmp 

(See Viewing Packets With tcpdump for more information on using the 

tcpdump command.) 


Voyager, you can enable several types of trace options for DVMRP. 

These traces are logged into /var/tmp/ipsrd.log. 


You do not have IP connectivity. 


Verify that you have IP connectivity; ping various hosts on each 

network. See Connectivity Problems. 


DVMRP is not enabled on the interfaces. 


Verify that DVMRP is enabled on the interfaces in use. 


Packets exceed TTL on clients. 




Verify that the client is set up for the proper TTL number. Many clients 

are set to receive local traffic only one hop away. 



Using tcpdump 


Use this command to display packets for a specific interface: 

tcpdump -1 logical interface name proto igmp 

(See Viewing Packets With tcpdump for more information on how to 

use the tcpdump command.) 

Viewing Packets With tcpdump 

tcpdump is a program provided with the IPSO software. You can use it 

to view traffic on a network. Some features and commands used with 

tcpdump are outlined in this section; for more information, see the man 

page for tcpdump. 

NOTE: CONTROL-C stops tcpdump. Substitute either physical or 

logical interface names for interface, as appropriate. 

tcpdump Command Basics 

tcpdump for a specific interface 

tcpdump -i logical interface name 

The following example shows slot 1 port 1 on a NAP: 

tcpdump -i eth-s1p1c0 


Using tcpdump 

tcpdump for a specific protocol on an interface 

tcpdump -i logical interface name proto protocol 

The following example command shows OSPF traffic: 

tcpdump -i eth-s2p3c0 proto ospf 

The following example command shows IGRP traffic: 

tcpdump -i eth-s2p1c0 proto igrp 

tcpdump for an Interface Using a TCP/UDP Application Port 

tcpdump -i logical interface name port TCP/UDP 

application port 

The following example command shows telnet traffic: 

tcpdump -i eth-s1p1c0 port telnet 

The following example command also shows telnet traffic: 

tcpdump -i eth-s1p1c0 port 23 

Specifying IP or UDP Port 

tcpdump -i logical interface name TCP/ 

UDP application port 

The following example shows all BOOTP/DHCP traffic: 

tcpdump -i eth-s2p1c0 udp port 68 

Filtering Traffic with tcpdump 

Hiding Specific Types of Traffic 

tcpdump -i logical interface name not 

TCP/UDP application port 



The following example hides WWW traffic for the interface: 

tcpdump -i eth-s1p1c0 not port 80 

Viewing a Portion of the Packet 

tcpdump -i logical interface name -s packet size -vv 

The following example shows 320 bytes of the packet: 

tcpdump -i eth-s1p1c0 -s 320 -vv 

Viewing a Specific IP Address 

tcpdump -i logical interface name host IP address 

The following example shows only packets with IP address 10.10.10.1: 

tcpdump -i eth-s3p1c0 host 10.10.10.1 

Saving tcpdump Results to Local File 

Generate a trace file by using tcpdump with the -w flag. This stores 

the packets in a local file for later viewing with tcpdump. Use this 

feature when you want to send a copy of the tcpdump results to Nokia 

Customer Support. 

The -w flag copies the first 68 bytes of every packet, unless you 

increase the capture size. 

For users running without data encryption, passwords are stored in the 

file. 

NOTE: The file grows very quickly on a busy network. We 

recommend creating this file in the /var partition. 


Using tcpdump 

The following example does not display packets: 

tcpdump -i eth-s1p1c0 -w /var/tmp/tracefile 

Press CONTROL–C to end the capture and print the number of packets 

captured. 

The following example shows all RIP traffic for that interface: 

tcpdump -i eth-s1p1c0 -s 320 -vv port 520 

NOTE: Port 520 is also the port used by the UNIX daemon process 

on “routed” UNIX workstations. 




Index 

A 

address 

IP 33 

AT command string 

US Robotics 22 

Best modem 24 

AUX port 19 

B 

Best Data 56K data fax modem 24 

boot manager 45 

booting the system 54 

installing IPSO 47, 55 

password protection 56 

setting and viewing variables 54 

upgrade 57 

variables 47 

bottom 7 

browser 30 

text-based 31 

web-based 30 

C 

cable 

ethernet crossover 41 

null-modem 20, 43 

serial 17 

COM2 19 

compliance standards 

emission 3 

safety 3 

telecom 3 

configuring modem 20 

confirm 

setup 32 

connection 

console 17, 18, 19, 20, 22, 28 

modem 19 

power source 16 

console 

UNIX 17 

conventions 

bold italic xiii 

courier xiii 

courier bold xiii 

note xiv 

small caps xiii 

warning xiv, 2 

D 

DB-25 connector 19 

DB-9 connector 19 

Declaration of Conformity 40 

depth of unit 37 


desk placement 12 

DIP switches 


documentation 

Voyager 

inline help xii 

reference guide xii 

E 

enter 

browser type 30 

hostname 29 

passwords 30 

F 

face plate 

re-orientation 15 

H 

height of unit 37 

hostname 29 

enter 29 

I 

iclid 

troubleshooting 78 

interface 

AUX 5 

console 5 

duplex 32 

ethernet 33 

physical designation 33 

initial information 31 

specifications 39 

selecting 31, 32 

speed 32 

IP address 33 

IPSO 1 

system startup 28 

K 

keyholes 8, 13 

knowledge base 


L 

labels 

LAN 5 

LED 6 

license 59 

logical designation 33 

Lynx 31, 33 

starting 31 

M 

maximum altitude pressure of unit 38 

Microsoft Internet Explorer 30, 33 

modem 19 

Best Data 24 

command strings 22 

configuring 20 


mounting 8 

N 

NAP monitoring 35 

Netscape Navigator 30, 33 

P 

part number 

power supply 4 

password 30 

enter 33 

types 30 

pcdump 69 

placement of unit 12 

desk 12 

stacked 12 

table 12 

power cord 4 

power supply 

connector 5 

problems 

access, login 70 

no login prompt 72 

receive login prompt, password not accepted 71 

unable to connect to Voyager using network port 72 

unable to log in to console port 70 

connectivity 76 

unable to ping 76 

interface 74 

activity light continuously on 74 

high collision rate 75 

local ports do not appear in Voyager 74 

no link light 74 

routing 78 


exchanging routes 81 

multicast 82 

OSPF 79 

does not operate 79 

RIP 80 

R 

rear panel 5 

re-orienting face plate 15 

reset button 5 

rubber cushion 8 

S 

serial cable 4, 19 

setup 

confirm 32 

software license 59 

general public 65 

space requirements 13 

specifications 37 

environmental 38 

electrical 38 

pressure 38 

temperature 38 

interface 

aux 39 

console 39 

ethernet 39 

physical 37 

depth 37 

height 37 

width 37 

stacking unit 13 

system startup 28 

browser type 30 

password 30 

storage 38 


iclid 78 

knowledge base 71 

ttys file 20 

U 

US Robotics 33.6 fax modem 22 

username 

enter 33 

pop-up menu 33 

V 

ventilation slots 8 

Voyager xii, 1 

open 33 

Voyager Reference Guide 33 

W 

wall mounting unit 13 

WAN 30 

warranty 59 

width of unit 37 

T 

tcpdump 84 

commands 84 

filtering traffic 85 

saving results 86 

viewing packets 84 

viewing portion of packet 86 

viewing specific IP address 86 

technical specifications 37 

temperature 

operating 38

Nokia IP100 Series Installation Guide - Check Point

Create successful ePaper yourself

Delete template?

Save as template?