World Wide Web Server-Glenayre

Copyrights
1998 Glenayre Electronics, Inc.
This document is copyrighted with all domestic and international rights reserved.
No part of this document may be reproduced, stored in a retrieval system, or
transmitted, in any form, by any means, without the prior written permission of
Glenayre Electronics, Inc. No patent is assumed with respect to the use of the
information contained in this document.
Trademarks
Glenayre is a registered trademark of Glenayre Electronics, Inc.
All brand names and product names are trademarks or registered trademarks of
their respective companies and are used with the permission of their owners.
Revisions
This document is written and published by Glenayre Atlantas Technical

Publications Department, and every precaution has been taken to ensure its
accuracy. Should you find an error, please contact Technical Publications at the
Atlanta offices of Glenayre Electronics, Inc.
Glenayre Electronics, Inc. assumes no responsibility for errors in this document,

omissions, or their consequences. The information is subject to change without
notice.
Reordering
When purchasing additional copies of this document, please include the following
information:
Part Number: 9110.01068
Revision 1.0
Date of Issue: Aug. 4, 1998
Address all comments and requests regarding this document to:
Glenayre Electronics
Technical Publications Department
11360 Lakefield Drive
Duluth, GA 30097-1508
USA
Tel: (770) 283-1000

Fax: (770) 497-3981
Website: http://www.glenayre.com
WWW Server Reference Manual
DOCUMENT CHANGE RECORD
Revision Release Date Page Number Changes
1.0 Aug. 4, 1998 Original
PN 9110.01068 iii
DOCUMENT CHANGE RECORD
Documentation Change Request Form
Use a copy of this form to report documentation errors and/or suggested

improvements. Please provide the following information, giving as full a
description of the error or recommended improvement as possible.
Date: ____________________
Name of Manual: _______________________________________
Part Number: ____________________
Issue Date: ____________________
Page Number: ___________
Description of error or suggested improvement:
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
Recommended Priority: _______
1 = extremely urgent
Major error in critical information; could result in severe system problems.
2 = moderately urgent
Highly useful but noncritical information is missing or incorrect; the flaw should
not, however, cause major system problems.
3 = not urgent
Relatively minor error which should be addressed with next scheduled
documentation update; this category includes, but is not limited to, minor
typographical and page layout errors.
Change requested by:
__________________________________________________________
(Name)(Company)
________________________
(Phone Number)
Send completed form to:
Glenayre Electronics, Inc.

Technical Publications Department
Duluth, GA 30097-1508
USA
iv REV 1.0 Aug. 4, 1998

TABLE OF CONTENTS
1. GENERAL INFORMATION ................................................................................................................ 1
1.1 Introduction ................................................................................................................................. 1
1.1.1 Intended Audience .......................................................................................................... 1
1.1.2 How to Use this Manual .................................................................................................. 2
1.2 Getting Technical Assistance ..................................................................................................... 3
2. WWW SERVER SYSTEM .................................................................................................................. 5

2.1 General Description .................................................................................................................... 5
2.1.1 WWW Server Interfaces.................................................................................................. 6
2.2 System Components .................................................................................................................. 7
2.2.1 WWW Server .................................................................................................................. 7
2.2.2 Firewall............................................................................................................................ 8
2.2.3 Modular Voice Processor ................................................................................................ 8
2.2.4 Fax Server ...................................................................................................................... 8
2.3 Network Access .......................................................................................................................... 9
2.3.1 TCP/IP Access ................................................................................................................ 9
2.3.2 PSTN Access To the WWW Server ................................................................................ 9
2.3.3 Wireless Access..............................................................................................................9
2.4 Subscriber Features .................................................................................................................10
2.4.1 Initial Connection ..........................................................................................................10
2.4.2 Message Retrieval Service ...........................................................................................10
2.4.3 Message Deletion .........................................................................................................11
2.4.4 Message Forwarding ....................................................................................................11
2.4.5 Guest Features ............................................................................................................. 11
3. WWW SERVER INSTALLATION.....................................................................................................13

3.1 Pre-installation Procedures ......................................................................................................13
3.1.1 Extracting the Install Program from Tape......................................................................15
3.1.2 Extracting the Install Program from CD.........................................................................15
3.2 Installing the WWW Server Software........................................................................................16
3.2.1 Post Installation Procedure ...........................................................................................26
3.3 Program and Processes Configuration Details.........................................................................27
3.3.1 HTTPD Server Process.................................................................................................27
3.3.2 HTML Client (Mailroom) Process ..................................................................................30
3.3.3 Java Client Process ......................................................................................................32
3.3.4 MVP Server Process.....................................................................................................34
3.3.5 CGI Program .................................................................................................................36
3.3.6 SNMP Agent ................................................................................................................. 36
3.4 System Startup Details .............................................................................................................37
3.5 WWW Server Status.................................................................................................................38
3.6 Removing the WWW Server Software......................................................................................39
PN 9110.01068 v
TABLE OF CONTENTS
4. FIREWALL INSTALLATION ............................................................................................................41

4.1 Overview...................................................................................................................................41
4.2 Installing the PIX Firewall .........................................................................................................42
4.2.1 Physical Installation ......................................................................................................42
4.2.2 Software Installation......................................................................................................43
4.3 Testing the Installation..............................................................................................................45
5. MODEM BANK.................................................................................................................................47
5.1 Installing the U.S. Robotics Modem Bank ................................................................................47
5.1.1 Hardware Installation ....................................................................................................47
5.1.2 Modem Bank Card Configuration..................................................................................48
5.1.3 Modem Bank Configuration ..........................................................................................49
5.2 Configuring the NETServer ......................................................................................................50
5.2.1 Input Filter Configuration...............................................................................................50
5.2.2 Address Pool Configuration ..........................................................................................51
5.2.3 User Account Configuration ..........................................................................................52
5.2.4 Modem Port Configuration ............................................................................................53
5.3 Administrative Tools .................................................................................................................55
5.3.1 Viewing DEBUG Messages ..........................................................................................55
5.3.2 IFCONFIG .....................................................................................................................55
5.3.3 PING .............................................................................................................................56
5.3.4 PTRACE .......................................................................................................................56
5.3.5 TRACEROUTE .............................................................................................................56
5.3.6 SHOW ...........................................................................................................................57
5.3.7 TRNKDIAG ...................................................................................................................58
6. HTML CLIENT ..................................................................................................................................61

6.1 Processes for HTML Client.......................................................................................................62
6.2 Installation and Configuration ...................................................................................................62
6.2.1 Platform Requirements .................................................................................................63
6.3 User Operations .......................................................................................................................64
6.3.1 General Usage .............................................................................................................. 64
6.3.2 Accessing the HTML Client...........................................................................................65
6.4 Troubleshooting ........................................................................................................................65
6.4.1 Client Problems.............................................................................................................66
6.4.2 Server Problems ...........................................................................................................67
6.4.3 Advanced Troubleshooting ...........................................................................................68
7. JAVA CLIENT ..................................................................................................................................69

7.1 Processes for Java Client .........................................................................................................69
7.2 Installation and Upgrades .........................................................................................................71
7.2.1 Obtaining Java Client Software.....................................................................................71
7.2.1.1 File Names ......................................................................................................71
7.2.1.2 Software Provided on a CD .............................................................................71
7.2.1.3 Download via HTML Browser ..........................................................................71
7.2.1.4 Download/or Upgrade via Java client ..............................................................73
7.2.2 Hardware and Operating System Minimum Requirements...........................................74
7.2.3 Windows 95/NT Installation...........................................................................................75
7.2.3.1 System Requirements .....................................................................................75
7.2.3.2 Installation Instructions ....................................................................................75
vi REV 1.0 Aug. 4, 1998

7.2.4 Mac OS Installation .......................................................................................................76

7.2.5 SPARC Solaris Installation............................................................................................77
7.3 User Operations .......................................................................................................................78
7.4 System Configuration ...............................................................................................................79
7.4.1 Configuring Client/Server Communications ..................................................................79
7.4.2 Configuration Files ........................................................................................................ 80
7.4.2.1 General Configuration Files.............................................................................80
7.4.2.2 Account Level Configuration Files ...................................................................80
7.4.3 Client Directory Structure ..............................................................................................81
7.5 Java Client Start-up ..................................................................................................................82
7.5.1 Windows 95 ..................................................................................................................82
7.5.2 Windows NT..................................................................................................................82
7.5.3 MacOS ..........................................................................................................................82
7.5.4 Solaris ...........................................................................................................................82
7.6 Troubleshooting ........................................................................................................................83
7.6.1 System Log Dialogue Box.............................................................................................83
7.6.2 Local Fax File Corrupted or Missing .............................................................................84
7.6.3 No Response To User Commands ...............................................................................84
7.6.4 Memory Trace ............................................................................................................... 84
8. MVP SERVER PROCESS................................................................................................................85

8.1 Computer Interface ...................................................................................................................85
8.1.1 Functional Grouping......................................................................................................86
8.1.2 Input Command String Syntax ......................................................................................86
8.1.3 Output Command String Syntax ...................................................................................87
8.1.4 Error Messages............................................................................................................. 87
8.2 Shared Memory and SNMP Agent ...........................................................................................88
8.3 Alarm and Trace Log ................................................................................................................88
8.4 Maintenance Mode ...................................................................................................................89
8.5 File Structure ............................................................................................................................89
9. CGI PROGRAM................................................................................................................................91
9.1 Process Interactions .................................................................................................................91
9.1.1 Interactions with the SNMP Alarm Server.....................................................................91
9.1.2 Interactions with the Fax Server....................................................................................92
9.1.3 Interactions with the MVP Server..................................................................................92
9.1.4 Interactions with the HTML and/or Java Clients...........................................................92
9.2 Data Processing .......................................................................................................................93
9.2.1 Password Validation .....................................................................................................93
9.2.2 Account Validation ........................................................................................................93
9.2.3 Update ..........................................................................................................................94
9.2.4 Delete............................................................................................................................94
9.2.5 Forward .........................................................................................................................94
9.2.6 Modify ...........................................................................................................................95
9.2.7 Download ......................................................................................................................95
9.2.8 Upload...........................................................................................................................95
PN 9110.01068 vii
TABLE OF CONTENTS
9.2.8.1 Uploading a DMS Message.............................................................................95

9.2.8.2 Uploading a Fax ..............................................................................................96
10. SNMP AGENT ..................................................................................................................................97

10.1 SNMP AGENT PROCESS .......................................................................................................97
10.1.1 CGI Stats Shared Memory Area ...................................................................................98
10.1.1.1 cgiStats Table MIB .......................................................................................100
10.1.2 MVP Server Shared Memory Area..............................................................................100
10.1.2.1 runStatus MIB ..............................................................................................100
10.1.2.2 Command Table MIB ...................................................................................101
10.1.3 Alarm Table Shared Memory ......................................................................................101
10.1.3.1 Default Alarm Table .....................................................................................104
10.1.3.2 Alarm Table Utility ........................................................................................106
10.1.3.3 Alarm Table MIB ..........................................................................................107
10.1.4 SNMP Process............................................................................................................108
10.1.4.1 Configuration................................................................................................109
10.1.5 Snmpalarmd Process..................................................................................................109
10.1.5.1 Troubleshooting "snmpalarmd" (Alarm Server)............................................110
10.1.6 MIB..............................................................................................................................111
10.1.6.1 The Resource Group ...................................................................................111
10.1.6.2 MIB-II Group ................................................................................................115
10.1.6.3 The IP Group ...............................................................................................118
10.1.6.4 The ICMP Group ..........................................................................................122
10.1.6.5 The TCP Group............................................................................................124
10.1.6.6 The UDP Group ...........................................................................................126
10.1.6.7 The SNMP Group ........................................................................................126
10.2 Traps ......................................................................................................................................128
10.2.1 wwwSecurityEvent ......................................................................................................128
10.2.2 wwwPMThreshEvent...................................................................................................128
10.2.3 wwwFaultEvent ...........................................................................................................129
10.2.4 wwwStatusChangeEvent ............................................................................................129
10.2.5 wwwConfigChangeEvent ............................................................................................130
10.2.6 wwwResyncStartEvent................................................................................................130
10.2.7 wwwResyncCompleteEvent........................................................................................131
10.2.8 Generic Traps ............................................................................................................. 131
11. TROUBLESHOOTING THE WWW SERVER ................................................................................133

11.1 Processes ...............................................................................................................................133
11.2 Packages ................................................................................................................................134
11.3 Configuration Files..................................................................................................................135
11.4 Log Files .................................................................................................................................136
11.5 Tracking Down Problems .......................................................................................................137
11.5.1 Problems with Communication....................................................................................138
11.5.1.1 Reachability Test .........................................................................................138
11.5.1.2 Test the MVP ...............................................................................................138
11.5.1.3 Test the MvpSrv Process .............................................................................138
11.5.1.4 CGI Debugging ............................................................................................139
11.5.1.5 Problems Talking to the Fax Server.............................................................140
11.6 Computer Interface Procedure Notes .....................................................................................143
11.7 Error Codes ............................................................................................................................147
viii REV 1.0 Aug. 4, 1998

Appendix A SOLARIS 2.6 INSTALL ..............................................................................................153

A.1 Prerequisites...........................................................................................................................153
A.2 Procedure ...............................................................................................................................153
Appendix B GLENAYRE INTEGRATED NETWORK GROUP WEB MIB .....................................157
Appendix C JAVA CUSTOMIZATION ............................................................................................173

C.1 Properties Files.......................................................................................................................173
C.1.1 Messages.properties ...................................................................................................173
C.2 Images ....................................................................................................................................173
C.2.1 Image Determination ...................................................................................................174
C.2.1.1 Required Images174
C.2.1.2 Optional Images174
Appendix D ACRONYMS AND ABBREVIATONS .........................................................................175
INDEX 179
PN 9110.01068 ix
L IST OF F IGURES
Figure 2-1 WWW Server System Diagram.................................................................................................6
Figure 6-1 Processes for HTML Client .....................................................................................................62
Figure 7-1 Processes for Java Client .......................................................................................................69
Figure 7-2 MailRoom Download HTML Page...........................................................................................72
Figure 7-3 MailRoom Windows 95/NT Download Page ...........................................................................72
Figure 7-4 Upgrade Options .....................................................................................................................73
Figure 7-5 Client Directory Structure ........................................................................................................81
Figure 7-6 System Log Dialoque Box.......................................................................................................83
Figure 10-1 SNMP Agent Process .............................................................................................................97
PN 9110.01068 xi
LIST OF TABLES
Table 2-1 WWW Server Components ...................................................................................................... 7
Table 4-1 Inside Addresses ....................................................................................................................42
Table 5-1 T1 Interface Cable Pinouts......................................................................................................48
Table 6-1 Client Problems.......................................................................................................................66
Table 6-2 Server Problems .....................................................................................................................67
Table 8-1 MVP Server specific................................................................................................................86
Table 8-2 MVP Server Originated Error Codes.......................................................................................88
Table 8-3 Config Subdirectory Files .......................................................................................................90
Table 10-1 Statistic Variables ...................................................................................................................98
Table 10-2 cgiStats MIB Object Identifiers .............................................................................................100
Table 10-3 runStatus MIB Object Identifiers ..........................................................................................100
Table 10-4 Command MIB Object Identifiers .........................................................................................101
Table 10-5 Alarm Table Shared Memory ...............................................................................................101
Table 10-6 Alarm Table Index ................................................................................................................102
Table 10-7 Default Alarms ......................................................................................................................104
Table 10-8 Alarm Table MIB ..................................................................................................................107
Table 10-9 The Processes MIB ..............................................................................................................111
Table 10-10 The Memory MIB ................................................................................................................112
Table 10-11 The Disk MIB ......................................................................................................................112
Table 10-12 The Loadaves MIB .............................................................................................................113
Table 10-13 The Version MIB ................................................................................................................114
Table 10-14 The System Group .............................................................................................................115
Table 10-15 The Interfaces Group .........................................................................................................115
Table 10-16 The At Group ......................................................................................................................117
Table 10-17 Basic IP Configuration Parameters ....................................................................................118
Table 10-18 IP Address Table ................................................................................................................118
Table 10-19 IP Routing Table ................................................................................................................119
Table 10-20 Statistic for IP Routing Discards .........................................................................................120
Table 10-21 IP Address Translation Table .............................................................................................120
Table 10-22 IP Statistics ........................................................................................................................120
Table 10-23 Statistics for Incoming ICMP Messages .............................................................................122
Table 10-24 Statistics for Outgoing ICMP Messages .............................................................................123
Table 10-25 TCP Configuration: Basic Parameters ...............................................................................124
PN 9110.01068 xiii
LIST OF TABLES
Table 10-26 TCP Connection Statistics .................................................................................................124

Table 10-27 Segment Counts .................................................................................................................125
Table 10-28 TCP Connection Table .......................................................................................................125
Table 10-29 Incoming and Outgoing UDP Traffic ..................................................................................126
Table 10-30 Information on Current UDP Listeners ...............................................................................126
Table 10-31 Incoming SNMP Traffic Counts ..........................................................................................126
Table 11-1 CIP Input Parameters ...........................................................................................................143
Table 11-2 CIP Output Parameters ........................................................................................................143
Table 11-3 SMSGTYPE .........................................................................................................................144
Table 11-4 MSGSTATE .........................................................................................................................144
Table 11-5 MSGSTATUS (Some values omitted) ..................................................................................144
Table 11-6 SERVICES (Output by usrprofile) ........................................................................................145
Table 11-7 MHANDLING (Output by usrprofile) .....................................................................................145
Table 11-8 ASTATUS (Output by usrprofile) ..........................................................................................146
Table 11-9 MWISTAT (Output by usrprofile) ..........................................................................................146
Table 11-10 Failure Opcodes .................................................................................................................147
Table 11-11 Common External Errors ....................................................................................................148
Table 11-12 Error Codes for "W" ............................................................................................................150
Table D-1 Acronyms and abbreviations.................................................................................................175
xiv REV 1.0 Aug. 4, 1998

GENERAL INFORMATION
1.1 Introduction
This manual contains detailed information about the Glenayre World Wide Web
(WWW) Server. It is a companion manual to the complete product reference set
for the MVP X.6.
Additional manuals in the X.6 product reference set include:

X.6 Features Manual,
X.6 System Administration Manual,
X.6 End User Reference Manuals (available for Emulations 0, 1 and 3),
X.6 Software Reference Manual,
MVP 4240 Hardware Reference Manual, and
MVP 2120 Hardware Reference Manual.
1.1.1 Intended Audience

The WWW Server Reference Manual is written primarily for companies that:
own or operate an MVP X.6,
sell the MVP X.6, such as Value Added Resellers (VARs), or
are potentially interested in Owning, Operating, or Reselling the MVP X.6.
or for individuals such as:

system attendants,
system administrators,
anyone who needs quick access to the general concepts of the WWW Server
features.
The WWW Server Reference Manual is NOT intended for direct use by
subscribers and callers.
The minimum skill level required to use this manual properly is that of a
certified Unix system administrator.
PN 9110.01068 1
GENERAL INFORMATION
1.1.2 How to Use this Manual

This manual is meant to be a general reference tool. For in-depth technical
information on X.6 features, refer to the appropriate companion manual from
the complete Product Reference Set for the Glenayre Modular Voice Processor
(MVP) X.6.
Note This manual does not distinguish between standard and optional
features.
This manual uses a few simplified terms.

A subscriber is a caller with access to a registered MVP account via the Main
Menu. A subscriber has an MVP account I.D. and must know their login
security code (sometimes referred to as a passcode or password) to access
their account,
A caller is any person that connects into someones MVP account via the
MVP Caller Menu,
The term Guest is used to refer to someone performing caller functions via a
graphic interface such as the WWW Server.
A system attendant is a person involved in system administration with
special access privilege, and
A system administrator is a system attendant who has been assigned the
highest level of access privilege.
2 REV 1.0 Aug. 4, 1998

1.2 Getting Technical Assistance

Technical Support is available to all Glenayre customers. Telephone support is
available every weekday between the hours of 8:00 AM and 8:00 PM Eastern
Time (USA). After hours support must be arranged in advance. Emergency
service for down systems only is available 24 hours a day. To get the quickest
response, please follow these guidelines:
Have available all of the information about the system or product you are
experiencing problems with or have questions about. You will be asked to
provide your name, phone number, address, and company name.
If possible try the operation several times to determine that the system
response is identical under identical circumstances. If the problem is not
repeatable, or if the responses are different for each attempt, make a note of
the input process, output results, and differences. If the problem is
completely random, try to repeat the situation until a pattern of cause and
effect can be established. In any case, document all parts of the problem
thoroughly and have your notes in front of you when you call.
If you are calling with a system problem, be at the terminal ready to execute
any instructions given by the technical representative. Have all manuals
and documentation immediately available.
To contact Glenayre Electronics Technical Support, call or write:
Glenayre Electronics, Inc.

Duluth, Georgia 30097
1-800-688-4001
1-770-283-3666
PN 9110.01068 3
WWW SERVER SYSTEM
2.1 General Description

The WWW Server allows subscribers to access their MVP account and conduct, in a
graphical environment, the most common activities that they currently conduct via a
telephone session using Dual Tone Multi-Frequency (DTMF) input. It also allows a
non-subscriber (a Guest) to send a fax or message through the Direct Messaging Service
(DMS) of the MVP to a subscriber via the World Wide Web.
This chapter describes the individual hardware and software components necessary to set
up the WWW Server System. The functionality and responsibility of each component is
described, as well as the interfaces between individual components.
PN 9110.01068 5
WWW SERVER SYSTEM
2.1.1 WWW Server Interfaces

The WWW Server is connected to the other Glenayre components via a TCP/IP
connection. All application-related access to or from the WWW Server is made through
one of the following three methods over this single connection:
HTML Interface: Data is transferred to and from the Remote Client using the Hyper
Text Transfer Protocol (HTTP) over TCP/IP.
MVP Interface: The WWW Server interfaces to the MVP using an enhanced MVP
computer interface.
Fax Server Interface: The WWW Server accesses the Fax Server using standard
UNIX utilities: rsh and rcp.
A block diagram of the WWW Server system is shown below. The system includes an
MVP, an WWW Server, a Fax Server, a Modem Bank, and a Firewall. The Firewall
protects the local Glenayre network against improper access. At this time, the system
supports a single MVP per WWW Server.
Fax Server
Control
& L
Data O
C
A
E1/T1 L
SS7
G
Switch
or
ISUP
Glenayre Terminal Server L
Wireless Network
Other PSTN MVP Modem Bank E
Interface N
(Optional)
A
Y
R
E
WWW Server
modem
PSTN N
E
HTML or T
Java Client W
network O
R
K
TCP/IP Network
FireWall
Figure 2-1 WWW Server System Diagram
6 REV 1.0 Aug. 4, 1998

2.2 System Components
2.2.1 WWW Server

The WWW Server is a UNIX based workstation running the Solaris 2.6 operating
system. The system hosts an Apache 1.2 Web Server (HTTP Daemon), CGI Programs,
File Format Conversion utilities, and HTML Web pages. The Server connects to the
network via Ethernet. The systems networking software is configured to allow access to
the Glenayre MVP, the Fax Server, and a Modem Bank.
Hardware platform requirement
Vendor: Themis Computer
Description: Phoenix Simplex Server USP-1/XXX-200-A-GA
The WWW Server itself is composed of the following components:
Table 2-1 WWW Server Components
Unit Description
1 200 MHz Ultra Sparc processor with 512 Mbyte of DRAM, 1 Mbyte
FLASH, two sbus slots, dual SCSI-II FAST, Dual Ethernet Ports,
Centronics port, two serial channels, Keyboard/Mouse Port, VME 64
Interface, and OBP.
1 Solstlce: On-Line DiskSuit pre-installed.
1 INT0KIT-USP-1.
1 Sbus SCSI/10 Base T Boards
1 NEBS compliant system chassis with dual 8-slot backplane, -48 VDC
power supplier and cooling system.
2 4 GB SCSI-2 Data Disk.
1 4 GB SCSI-2 System Disk.
1 4 mm DAT Tape Drive.
1 CD-ROM Drive.
1 Solaris 2.6 RTU license.
4 Canisters.
1 Alarm Board.
PN 9110.01068 7
WWW SERVER SYSTEM
2.2.2 Firewall
The PIX Firewall by Cisco Systems, Inc. is used to allow specific packets from the
Internet to connect with the servers inside an installation cluster. For the purposes of this
document, an installation cluster consists of at least the following:
An MVP
A FAX Server
A WWW server
A Modem pool
A Firewall
The term inside the cluster will refer to all of the above components except for the outside
port of the Firewall, that is anything that is protected by the Firewall.
2.2.3 Modular Voice Processor

The MVP performs the following functions:
maintain user account information
manage fax, voice, and paging messages
handle message distribution among the user accounts
Use MVP release X.6.2 or later.
2.2.4 Fax Server

The Fax Server stores faxes for the MVP. The MVP controls and routes faxes, but the
actual data files are stored on the Fax Server. The MVP and the WWW Server find the
name and location for a stored or retrieved fax. The path under which fax messages are
stored is determined by an algorithm that uses the path and fax file name combination.
The path and fax file names are provided by the MVP. Use a digital Fax Server release
4.2.1 or later.
8 REV 1.0 Aug. 4, 1998

2.3 Network Access
2.3.1 TCP/IP Access

If an Internet connection is available, the Remote Client can use these services for access.
Using these services has the advantage of higher speeds when downloading new software
or accessing fax data. However, for security purposes the Glenayre network is protected
by a Fire Wall.
2.3.2 PSTN Access To the WWW Server

For PSTN access, a client may initiate a call to the MVP with the called number
corresponding to a WWW Mailbox type in the MVP. Prior to answering the call, the
MVP determines if Modem Resources are available to process the connection. If no
resources are available the MVP responds with a BUSY signal to the incoming call. If
Modem Resources are available, the MVP answers the call and cross-connects the
incoming channel to an alternate stream to reach the Modem Bank. The Modem Bank is
programmed to provide a PPP connection to the WWW Server. For security purposes,
the Modem Bank is configured so that the callers can only connect to the WWW Server.
2.3.3 Wireless Access

In the wireless environment, the bandwidth to the Remote Client may be as low as 2400
bits per second (BPS), but could be increased to 9600 baud in some networks. The
primary concern is this limited bandwidth compared to the amount of data required to be
sent and received. For example, the fax format G3 is a compressed format. A typical fax
page containing 65535 bytes of G3 data, using 2400 baud, would take approximately 218
seconds (3.6 minutes) to receive one fax page.
World Wide Web technology can be employed instead of a more traditional mail scheme.
An MVP-to-WWW Server protocol provides the server access to the MVP database and
messages.
The WWW Server system is designed to allow the Remote Client to use the HTTP
protocol to send/receive fax messages. Each fax message is broken down into individual
pages. The HTTP protocol downloads the fax image to the Remote Client. The fax header
information (which is stored in ASCII) is downloaded first, followed by the fax pages.
This allows a subscriber to view a fax page (i.e., the cover page), prior to the complete
download of the entire fax and thereby uses the limited bandwidth to its full potential.
PN 9110.01068 9
WWW SERVER SYSTEM
2.4 Subscriber Features

There will be two different methods for WWW access. The HTML and Java Clients are
available via a browser. They provide support for both subscriber and Guest access.
Most standard HTML Browsers (i.e., Netscape 2.0x or greater, Internet Explorer 4.0 or
greater) with Javascript can be used. The interface will offer a welcome page which
provides links to the subscriber interface page and the Guest interface page.
The second method of WWW access is through a Java Application called MailRoom,
which provides subscriber access. MailRoom will provide the subscriber with greater
functionality than available with the HTML Client. The MailRoom is an independent
platform supporting Windows 95, Windows NT, Solaris, and MacIntosh.
Both the HTML and the Java Clients offer subscriber access. The subscriber's user
number and password are verified, and the subscriber is able to display a list of current
fax, voice mail, and DMS messages, retrieve specific fax or DMS messages, delete
specific fax, voice mail, or DMS messages. The subscriber can also send pages or faxes
to other subscribers. The subscriber can also send faxes to external phone numbers.
Guest access is possible using the HTML Client in Guest mode. In this case, the Guest
must specify a valid subscriber's account number and request a guest login. While logged
in, a Guest can send Fax or DMS messages to the subscriber's account. However, a Guest
cannot send faxes to external numbers.
2.4.1 Initial Connection

Prior to using the application software, the subscriber must obtain network access to the
WWW Server. The user either already has network connectivity or can dial-in using a
modem using the PPP connection to the WWW Server. The MVP provides the front end
to the Modem Bank through the use of a WWW Mailbox type.
When a subscriber executes the Remote Client, a screen is displayed that welcomes the
caller and asks for a user ID and password.
2.4.2 Message Retrieval Service

Upon retrieval of a new message, the WWW Server sends a message to the MVP to mark
the message as saved. Fax and DMS messages can be sent to the WWW Server. DMS
messages are either numeric or alphanumeric messages. These messages are stored
directly on the MVP.
For Fax message retrieval, the WWW Server obtains the Fax Servers IP address and the
message filename supplied in the account data from the MVP. Then, it obtains the fax
file from the Fax Server, followed by the format conversion to G3-format files and the
standard image GIF format files. In this way, the user is able to clearly see the fax as it is
downloaded from the top down. The subscriber can choose to cancel the download at any
time.
10 REV 1.0 Aug. 4, 1998

During this process, the Remote Client provides the subscriber with the option of
requesting the next-page, requesting a specific page, or requesting any other service
offered by the Fax Server (deletion, forwarding, etc.).
2.4.3 Message Deletion

On screen, the subscriber has the option of deleting any message (including voice
messages). Selecting this option will cause the Fax Server to send a message to the MVP
to delete the selected message.
Any messages placed on the trash folder can be selected for undeletion. A message that
is undeleted will return to its original folder.
Note Undelete is an option for the Java client only.
2.4.4 Message Forwarding

A subscriber can forward a message to another party. In the case of a fax, the Server
sends the fax to a fax machine. The client collects a telephone number to which the
message is to be delivered.
Note Only voice and fax messages can be forwarded.
2.4.5 Guest Features

Guest users are presented with an Options Screen. The Options screen allows a Guest to
send either an alphanumeric DMS Message, a numeric DMS Message, or a Fax Message
to a subscriber.
For DMS Messages, the Guest user fills in the message field, which is range-checked to
ensure that it is within the permissible message lengths for the account. For fax messages,
the Guest user may deliver a cover sheet and/or a postscript fax file. If specified, the
cover sheet is created by the user (typically including From, To, Subject, and Message
Text fields).
PN 9110.01068 11
WWW SERVER INSTALLATION
3.1 Pre-installation Procedures

1. Make sure that Solaris software is installed. See Appendix A on page 153 for
details.
2. Make sure that enough hard disk space is available by running:
df b /opt
This will produce an output something like this
Filesystem avail
/dev/dsk/c0t0d0s5 87776
Make sure that the number listed under avail is 512000 (500 Mb) or better. If it
is not then you need to arrange to have more space in /opt. In the sample output
above, you would not have enough space to install.
3. If you would like to use an attendant that is specific to the web interface on the
MVP and you have not yet created this attendant, do so now.
4. See what the ciin_term flag on the MVP is set to. To do this, login to the
console of the MVP and run flags. The second line of data will look like this:
ciin_term EOF
If this has no value, then set the value to some string. You will need to know this
string during the configuration process for the MVP Server software. If you
change the value, be sure to edit /batch/autoexec.b and add the following
line:
set_flag ciin_term EOF
where EOF is the string that you entered in the flags program. This will make
sure that this flag is reset whenever the MVP reboots.
PN 9110.01068 13
5. Make sure that the /syspar/config file contains a setting for ipaddress
faxserver like this:
ipaddress faxserver:127.0.0.1
where the IP address that you enter is the address of the Fax Server attached to
this MVP.
6. You need to have an account on the Fax Server that is attached to the MVP. This
account should be accessible from the nobody account on the WWW Server.
Create this account now if you do not already have one. It is recommended that
you use a fairly unprivileged account. It must have access to the fax images held
in /usr2/fax and be able to write to /var/tmp.
7. Once the account is created, make a .rhosts file in its home (for example,
/usr/nobody). This file should have Read Only permissions, be owned by
root, and have the following line:
<webserver> nobody
where <webserver> represents the name of the WWW Server computer.
You can test that this is setup properly by following these steps:
su
enter root password
su nobody
rlogin faxserver -l account
Where faxserver is the name or address of your Fax Server computer, and
account is the name of the account that was just created. If you are logged in
without being asked for a password, then everything is setup properly. If not,
verify the permissions on the .rhosts file; it should be Read Only. Verify that
the file is in the accounts home directory. Verify that the webserver entry in the
file is correct. Test the name resolution by running ping webserver.
8. At the prompt, type:
TERM=vt100
export TERM
9. Edit the /etc/services file and add the following lines:
omc_ci 6020/tcp
Mailroom 9595/tcp
snmpalarm 7777/udp
10. Edit the /etc/syslog.conf file and add the following lines at the end. Use
the tab key on the keyboard for the term [tab].
local5.debug [tab] /opt/omcrel/v1.0.1/logs/omcsrv.log
local0.debug [tab] /var/log/snmptraps.log
local6.debug [tab] /opt/webserv/logs/debug
11. Issue the touch command to create the above 3 files:
touch /opt/omcrel/v1.0.1/logs/omcsrv.log
touch /var/log/snmptraps.log
touch /opt/webserv/logs/debug
14 REV 1.0 Aug. 4, 1998

3.1.1 Extracting the Install Program from Tape

The tape contains at least two files. The first file is the www_install program.
The second file is the distribution media itself, usually named webserv.tar.Z.
Run the following commands as root:
cd /tmp
tar -xf /dev/rmt/0
ls -l www_install
If the file does not have rwxrwxrwx permissions, then type:

chmod 777 www_install
If your tape drive is not on the machine that you wish to be your WWW Server,
then simply copy the files from the tape, using ftp, rcp, a nfs mount or some
other method, to the WWW Server computer.
3.1.2 Extracting the Install Program from CD

The CD contains at least two files. The first file is the www_install program.
The second file is the distribution media itself, usually named webserv.tar.Z.
Run the following commands as root:
cd /tmp
tar -xf /cdrom/cdrom0/webserv.tar
Is -l www_install
If the file does not have rwxrwxrwx permissions, then type:

chmod 777 www_install
PN 9110.01068 15
3.2 Installing the WWW Server Software

To begin the installation program, type in the following command:
./www_install
Once the program starts, you will be greeted with the installation banner and
asked if this is an install or uninstall.
*****************************************************************************
*****************************************************************************
G L E N A Y R E E L E C T R O N I C S
Web Server Installation Program
*****************************************************************************
*****************************************************************************
For context sensitive help at any prompt, type '?'. Default values are
displayed in '[]' in each prompt.
What type of operation to perform?

Install
Uninstall
At the prompt, enter 1 and press Enter. You will then be prompted to specify
the location of the media (tape or CD). If you enter a file name that can not be
found, you will be re-prompted for the media.
Installation media [webserv.tar.Z]?

Extracting media...
/
The installation program will now make sure that there is at least 500 MB free on
the /opt partition. If there is not, then the installation program will inform you
of the space shortage and exit. If this happens, try to make some more space in
/opt and run the installation program again.
At this point you are ready to begin installing the software onto the system. The
basic components to the WWW Server are installed in this order:
The Apache HTTP Server,
The Iona Orbix Server and interface repository,
The Glenayre WWW Server itself,
The Glenayre MVP Server, and
The Glenayre SNMP Servers
Installing HTTPD...
HTTPD Port [80]?
HTTPD Server Name [<hostname>]?
HTTPD Servers [5]?
HTTPD Administrator [root@<hostname>]?
HTTPD installation complete
16 REV 1.0 Aug. 4, 1998

Your responses to the prompts are used to configure the HTTP Server software.
The reference to <hostname> will display the hostname of the computer where
you are installing the software. For more details on HTTP Server configuration,
see Section 3.3 on page 27.
Next, you will install the Orbix software. If Orbix is already installed on your
system then the installation program will not attempt to install a new one. Orbix
is installed using Sun Microsystems pkgadd program. The WWW Server
software is expecting Orbix to be installed in /opt/Orbix_2.0. You will also
need a license key for the Orbix software.
Note The Orbix license key is provided by Glenayre. It must be entered

exactly as provided, or the install procedure must be restarted. For this
reason, we recommend that if you receive the key by e-mail, you
should copy (Ctrl-C) and paste (Ctrl-V) the key into the required field.
Make sure you have the license key before proceeding.
When prompted by pkgadd to continue with the installation always reply with
y. When asked to make this your default installation, reply with y.
Installing ORBIX
Processing package instance <ORBXc20> from </tmp/orbix.img>
Orbix2.0 Common Objects

(sparc) 2.0 for SunPro SPARCompiler C++ 4.0 on Solaris 2.x
Iona Technologies, Ltd.
Please select a directory for installation of Orbix 2.0 common objects.

Here is a list of your partitions and the free space in each of them:
/ (/dev/dsk/c0t0d0s0 ): 927230 blocks 237797 files

/usr (/dev/dsk/c0t0d0s4 ): 390580 blocks 266117 files
/proc (/proc ): 0 blocks 7926 files
/dev/fd (fd ): 0 blocks 0 files
/var (/dev/dsk/c0t0d0s3 ): 1406560 blocks 359781 files
/home (/dev/dsk/c0t0d0s6 ): 865790 blocks 239110 files
/opt (/dev/dsk/c0t0d0s5 ): 2543974 blocks 369251 files
/tmp (swap ): 1579200 blocks 84783 files
/net (-hosts ): 0 blocks 0 files
/xfn (-xfn ): 0 blocks 0 files
/vol (webserv2:vold(pid236)): 0 blocks -1 files
Where should Orbix be installed? [/opt/Orbix_2.0] [?,q]
Press Enter to accept the default, or type in /opt/Orbix_2.0 for the Orbix
installation directory
PN 9110.01068 17
The selected base directory </opt/Orbix_2.0> must exist before

installation is attempted.
Do you want this directory created now [y,n,?,q]
Type in y to create the directory. If you do not see this message then
/opt/Orbix_2.0 must already exist.
Using </opt/Orbix_2.0> as the package base directory.

## Processing package information.
## Processing system information.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
The following files are already installed on the system and are being
used by another package:
* /opt/Orbix_2.0 <attribute change only>
* - conflict with a file which does not belong to any package.
Do you want to install these conflicting files [y,n,?,q]
Type in y to accept the change.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user

permission during the process of installing this package.
Do you want to continue with the installation of <ORBXc20> [y,n,?]
Type in y to run the scripts.
Installing Orbix2.0 Common Objects as <ORBXc20>
## Executing preinstall script.

Installation of Orbix 2.0 common objects
## Installing part 1 of 1.
/opt/Orbix_2.0/FAQ
/opt/Orbix_2.0/INSTALL_NOTES
/opt/Orbix_2.0/Interfaces/IR/AttrDf.idl
/opt/Orbix_2.0/Interfaces/IR/AttrDf.sa
/opt/Orbix_2.0/Interfaces/IR/ConstDf.idl
/opt/Orbix_2.0/Interfaces/IR/ConstDf.sa
/opt/Orbix_2.0/Interfaces/IR/Contd.idl
/opt/Orbix_2.0/Interfaces/IR/Contd.sa
/opt/Orbix_2.0/Interfaces/IR/Contr.idl
/opt/Orbix_2.0/Interfaces/IR/Contr.sa
/opt/Orbix_2.0/Interfaces/IR/ExcDf.idl
/opt/Orbix_2.0/Interfaces/IR/ExcDf.sa
/opt/Orbix_2.0/Interfaces/IR/IRDfs.idl
/opt/Orbix_2.0/Interfaces/IR/IRDfs.sa
/opt/Orbix_2.0/Interfaces/IR/InterDf.idl
/opt/Orbix_2.0/Interfaces/IR/InterDf.sa
/opt/Orbix_2.0/Interfaces/IR/ModDf.idl
/opt/Orbix_2.0/Interfaces/IR/ModDf.sa
/opt/Orbix_2.0/Interfaces/IR/OperDf.idl
/opt/Orbix_2.0/Interfaces/IR/OperDf.sa
/opt/Orbix_2.0/Interfaces/IR/ParmDf.idl
/opt/Orbix_2.0/Interfaces/IR/ParmDf.sa
18 REV 1.0 Aug. 4, 1998

/opt/Orbix_2.0/Interfaces/IR/Rep.idl
/opt/Orbix_2.0/Interfaces/IR/Rep.sa
/opt/Orbix_2.0/Interfaces/IR/TypDf.idl
/opt/Orbix_2.0/Interfaces/IR/TypDf.sa
/opt/Orbix_2.0/README
/opt/Orbix_2.0/README.ver
/opt/Orbix_2.0/RELEASE_NOTES
/opt/Orbix_2.0/bin/IR
/opt/Orbix_2.0/bin/catit
/opt/Orbix_2.0/bin/chmodit
/opt/Orbix_2.0/bin/chownit
/opt/Orbix_2.0/bin/grouphosts
/opt/Orbix_2.0/bin/install_licence
/opt/Orbix_2.0/bin/killit
/opt/Orbix_2.0/bin/lsit
/opt/Orbix_2.0/bin/mkdirit
/opt/Orbix_2.0/bin/orbix13to20_ImpRep
/opt/Orbix_2.0/bin/orbixd
/opt/Orbix_2.0/bin/pingit
/opt/Orbix_2.0/bin/psit
/opt/Orbix_2.0/bin/putit
/opt/Orbix_2.0/bin/rmdirit
/opt/Orbix_2.0/bin/rmit
/opt/Orbix_2.0/bin/servergroups
/opt/Orbix_2.0/bin/serverhosts
/opt/Orbix_2.0/man/man1/catit.1
/opt/Orbix_2.0/man/man1/chmodit.1
/opt/Orbix_2.0/man/man1/chownit.1
/opt/Orbix_2.0/man/man1/grouphosts.1
/opt/Orbix_2.0/man/man1/idl.1
/opt/Orbix_2.0/man/man1/ir.1
/opt/Orbix_2.0/man/man1/killit.1
/opt/Orbix_2.0/man/man1/lsit.1
/opt/Orbix_2.0/man/man1/mkdirit.1
/opt/Orbix_2.0/man/man1/orbixd.1
/opt/Orbix_2.0/man/man1/pingit.1
/opt/Orbix_2.0/man/man1/psit.1
/opt/Orbix_2.0/man/man1/putit.1
/opt/Orbix_2.0/man/man1/rmdirit.1
/opt/Orbix_2.0/man/man1/rmit.1
/opt/Orbix_2.0/man/man1/servergroups.1
/opt/Orbix_2.0/man/man1/serverhosts.1
[ verifying class <common> ]
[ verifying class <config> ]
## Executing postinstall script.
Please Enter your IONA licence authorization code
Enter your Orbix license key now. The license key is formatted as follows:
XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX
Note The Orbix license key is provided by Glenayre. It must be entered

exactly as provided, or the install procedure must be restarted. For this
reason, we recommend that if you receive the key by e-mail, you
should copy (Ctrl-C) and paste (Ctrl-V) the key into the required field.
PN 9110.01068 19
----------------------------------------------------------------------
Okay, the Orbix common objects have now been installed.
Now, you must install one or both of the remaining Orbix packages.
----------------------------------------------------------------------
Installation of <ORBXc20> was successful.
Processing package instance <ORBXo20> from </tmp/orbix.img>
Orbix2.0 OMG CORBA2.0 C++ Mapping objects

(sparc) 2.0 for SunPro SPARCompiler C++ 4.0 on Solaris 2.x
Iona Technologies, Ltd.
The Orbix 2.0 OMG CORBA 2.0 C++ Mapping Objects will be
installed in the directory /opt/Orbix_2.0/corba2
If you intend to use Orbix to communicate with anything outside your

own subnet, you will need to supply your subnet's domain name.
If your machines all have fully-qualified hostnames, reply with the
value "null".
What is your domain name? []
If you do not see this message then pkgadd has been able to determine your
domain name. If you do not have a domain name, enter null.
Using </opt/Orbix_2.0> as the package base directory.

## Processing package information.
## Processing system information.
2 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user

permission during the process of installing this package.
Do you want to continue with the installation of <ORBXo20> [y,n,?]
20 REV 1.0 Aug. 4, 1998

Type in y to run the scripts.
Installing Orbix2.0 OMG CORBA2.0 C++ Mapping objects as <ORBXo20>
## Executing preinstall script.

Installation of Orbix 2.0 (CORBA2 C++ mapping)
## Installing part 1 of 1.
/etc/Orbix.cfg
/opt/Orbix_2.0/corba2/demos/orbixsol2s4.mk
/opt/Orbix_2.0/corba2/demos <implied directory>
[ verifying class <config> ]
/opt/Orbix_2.0/corba2/bin/idl
[ verifying class <binaries> ]
/opt/Orbix_2.0/corba2/lib/ErrorMsgs
/opt/Orbix_2.0/corba2/lib/libIRclt.a
/opt/Orbix_2.0/corba2/lib/libIRclt.so
/opt/Orbix_2.0/corba2/lib/libITclt.a
/opt/Orbix_2.0/corba2/lib/libITclt.so
/opt/Orbix_2.0/corba2/lib/libITini.a
/opt/Orbix_2.0/corba2/lib/libITini.so
/opt/Orbix_2.0/corba2/lib/libITsrv.a
/opt/Orbix_2.0/corba2/lib/libITsrv.so
/opt/Orbix_2.0/corba2/lib/libiiop.a
/opt/Orbix_2.0/corba2/lib/libiiop.so
[ verifying class <libraries> ]
/opt/Orbix_2.0/corba2/include/AttrDf.hh
/opt/Orbix_2.0/corba2/include/CORBA.h
/opt/Orbix_2.0/corba2/include/ConstDf.hh
/opt/Orbix_2.0/corba2/include/Contd.hh
/opt/Orbix_2.0/corba2/include/Contr.hh
/opt/Orbix_2.0/corba2/include/ExcDf.hh
/opt/Orbix_2.0/corba2/include/IR.h
/opt/Orbix_2.0/corba2/include/IRDfs.hh
/opt/Orbix_2.0/corba2/include/InterDf.hh
/opt/Orbix_2.0/corba2/include/ModDf.hh
/opt/Orbix_2.0/corba2/include/OperDf.hh
/opt/Orbix_2.0/corba2/include/ParmDf.hh
/opt/Orbix_2.0/corba2/include/Rep.hh
/opt/Orbix_2.0/corba2/include/TypDf.hh
/opt/Orbix_2.0/corba2/include/corba/any.h
/opt/Orbix_2.0/corba2/include/corba/boa.h
/opt/Orbix_2.0/corba2/include/corba/c2assist.h
/opt/Orbix_2.0/corba2/include/corba/environ.h
/opt/Orbix_2.0/corba2/include/corba/except.h
/opt/Orbix_2.0/corba2/include/corba/excepts.h
/opt/Orbix_2.0/corba2/include/corba/expermnt.h
/opt/Orbix_2.0/corba2/include/corba/features.h
/opt/Orbix_2.0/corba2/include/corba/initServ.h
/opt/Orbix_2.0/corba2/include/corba/it_seqs.hh
/opt/Orbix_2.0/corba2/include/corba/object.h
/opt/Orbix_2.0/corba2/include/corba/orb.h
/opt/Orbix_2.0/corba2/include/corba/postcorb.h
/opt/Orbix_2.0/corba2/include/corba/precorb.h
/opt/Orbix_2.0/corba2/include/corba/prelim.h
/opt/Orbix_2.0/corba2/include/corba/pseudo.h
/opt/Orbix_2.0/corba2/include/corba/request.h
/opt/Orbix_2.0/corba2/include/corba/sysexcep.h
/opt/Orbix_2.0/corba2/include/corba/typecode.h
/opt/Orbix_2.0/corba2/include/daemon.hh
/opt/Orbix_2.0/corba2/include/idl/AttrDf.idl
/opt/Orbix_2.0/corba2/include/idl/ConstDf.idl
/opt/Orbix_2.0/corba2/include/idl/Contd.idl
/opt/Orbix_2.0/corba2/include/idl/Contr.idl
/opt/Orbix_2.0/corba2/include/idl/ExcDf.idl
/opt/Orbix_2.0/corba2/include/idl/IRDfs.idl
/opt/Orbix_2.0/corba2/include/idl/InterDf.idl
/opt/Orbix_2.0/corba2/include/idl/ModDf.idl
/opt/Orbix_2.0/corba2/include/idl/OperDf.idl
/opt/Orbix_2.0/corba2/include/idl/ParmDf.idl
/opt/Orbix_2.0/corba2/include/idl/Rep.idl
PN 9110.01068 21
/opt/Orbix_2.0/corba2/include/idl/TypDf.idl
/opt/Orbix_2.0/corba2/include/idl/daemon.idl
[ verifying class <includes> ]
/opt/Orbix_2.0/corba2/demos/Makefile
/opt/Orbix_2.0/corba2/demos/README
/opt/Orbix_2.0/corba2/demos/Xwin/Makefile
/opt/Orbix_2.0/corba2/demos/Xwin/README
/opt/Orbix_2.0/corba2/demos/Xwin/client.cc
/opt/Orbix_2.0/corba2/demos/Xwin/label.cc
/opt/Orbix_2.0/corba2/demos/Xwin/label.h
/opt/Orbix_2.0/corba2/demos/Xwin/label.idl
/opt/Orbix_2.0/corba2/demos/Xwin/xtorbix.cc
/opt/Orbix_2.0/corba2/demos/Xwin/xtorbix.h
/opt/Orbix_2.0/corba2/demos/any_demo/Client.cc
/opt/Orbix_2.0/corba2/demos/any_demo/Makefile
/opt/Orbix_2.0/corba2/demos/any_demo/README
/opt/Orbix_2.0/corba2/demos/any_demo/Server.cc
/opt/Orbix_2.0/corba2/demos/any_demo/Server.h
/opt/Orbix_2.0/corba2/demos/any_demo/Srv_Main.cc
/opt/Orbix_2.0/corba2/demos/any_demo/test1.idl
/opt/Orbix_2.0/corba2/demos/caching/Bank_Srv.cc
/opt/Orbix_2.0/corba2/demos/caching/Bank_Srv.h
/opt/Orbix_2.0/corba2/demos/caching/Child.cc
/opt/Orbix_2.0/corba2/demos/caching/Client.cc
/opt/Orbix_2.0/corba2/demos/caching/Makefile
/opt/Orbix_2.0/corba2/demos/caching/README
/opt/Orbix_2.0/corba2/demos/caching/Smart_Ac.cc
/opt/Orbix_2.0/corba2/demos/caching/Smart_Ac.h
/opt/Orbix_2.0/corba2/demos/caching/Srv_Main.cc
/opt/Orbix_2.0/corba2/demos/caching/caching.idl
/opt/Orbix_2.0/corba2/demos/colocate/BANK.idl
/opt/Orbix_2.0/corba2/demos/colocate/Bank_Srv.cc
/opt/Orbix_2.0/corba2/demos/colocate/Bank_Srv.h
/opt/Orbix_2.0/corba2/demos/colocate/Client.cc
/opt/Orbix_2.0/corba2/demos/colocate/Makefile
/opt/Orbix_2.0/corba2/demos/colocate/README
/opt/Orbix_2.0/corba2/demos/dii_demo/Client.cc
/opt/Orbix_2.0/corba2/demos/dii_demo/Makefile
/opt/Orbix_2.0/corba2/demos/dii_demo/README
/opt/Orbix_2.0/corba2/demos/encrypt/Client.cc
/opt/Orbix_2.0/corba2/demos/encrypt/Makefile
/opt/Orbix_2.0/corba2/demos/encrypt/README
/opt/Orbix_2.0/corba2/demos/encrypt/Server.cc
/opt/Orbix_2.0/corba2/demos/encrypt/Server.h
/opt/Orbix_2.0/corba2/demos/encrypt/enc.idl
/opt/Orbix_2.0/corba2/demos/encrypt/srv_main.cc
/opt/Orbix_2.0/corba2/demos/encrypt/trans.cc
/opt/Orbix_2.0/corba2/demos/encrypt/trans.h
/opt/Orbix_2.0/corba2/demos/filters/Client.cc
/opt/Orbix_2.0/corba2/demos/filters/Makefile
/opt/Orbix_2.0/corba2/demos/filters/ProcFilt.h
/opt/Orbix_2.0/corba2/demos/filters/README
/opt/Orbix_2.0/corba2/demos/filters/Server.cc
/opt/Orbix_2.0/corba2/demos/filters/Server.h
/opt/Orbix_2.0/corba2/demos/filters/Srv_Main.cc
/opt/Orbix_2.0/corba2/demos/filters/filter.idl
/opt/Orbix_2.0/corba2/demos/grid/Client.cc
/opt/Orbix_2.0/corba2/demos/grid/Makefile
/opt/Orbix_2.0/corba2/demos/grid/README
/opt/Orbix_2.0/corba2/demos/grid/Srv_Main.cc
/opt/Orbix_2.0/corba2/demos/grid/grid.idl
/opt/Orbix_2.0/corba2/demos/grid/grid_i.cc
/opt/Orbix_2.0/corba2/demos/grid/grid_i.h
/opt/Orbix_2.0/corba2/demos/grid_tie/Client.cc
/opt/Orbix_2.0/corba2/demos/grid_tie/Makefile
/opt/Orbix_2.0/corba2/demos/grid_tie/README
/opt/Orbix_2.0/corba2/demos/grid_tie/Srv_Main.cc
/opt/Orbix_2.0/corba2/demos/grid_tie/grid.idl
/opt/Orbix_2.0/corba2/demos/grid_tie/grid_i.cc
/opt/Orbix_2.0/corba2/demos/grid_tie/grid_i.h
/opt/Orbix_2.0/corba2/demos/idl_demo/BANK.idl
22 REV 1.0 Aug. 4, 1998

/opt/Orbix_2.0/corba2/demos/idl_demo/Bank_Srv.cc
/opt/Orbix_2.0/corba2/demos/idl_demo/Bank_Srv.h
/opt/Orbix_2.0/corba2/demos/idl_demo/Client.cc
/opt/Orbix_2.0/corba2/demos/idl_demo/Makefile
/opt/Orbix_2.0/corba2/demos/idl_demo/README
/opt/Orbix_2.0/corba2/demos/idl_demo/Srv_Main.cc
/opt/Orbix_2.0/corba2/demos/ir_demo/BANK.idl
/opt/Orbix_2.0/corba2/demos/ir_demo/Bank_Srv.cc
/opt/Orbix_2.0/corba2/demos/ir_demo/Bank_Srv.h
/opt/Orbix_2.0/corba2/demos/ir_demo/Client.cc
/opt/Orbix_2.0/corba2/demos/ir_demo/Makefile
/opt/Orbix_2.0/corba2/demos/ir_demo/README
/opt/Orbix_2.0/corba2/demos/ir_demo/Srv_Main.cc
/opt/Orbix_2.0/corba2/demos/opaque/Makefile
/opt/Orbix_2.0/corba2/demos/opaque/README
/opt/Orbix_2.0/corba2/demos/opaque/client.cc
/opt/Orbix_2.0/corba2/demos/opaque/gentor.cc
/opt/Orbix_2.0/corba2/demos/opaque/gentor.h
/opt/Orbix_2.0/corba2/demos/opaque/opaq.idl
/opt/Orbix_2.0/corba2/demos/opaque/opaq_i.cc
/opt/Orbix_2.0/corba2/demos/opaque/opaq_i.h
/opt/Orbix_2.0/corba2/demos/opaque/opaqserv.cc
/opt/Orbix_2.0/corba2/demos/opaque/opaqserv.h
/opt/Orbix_2.0/corba2/demos/opaque/server.cc
/opt/Orbix_2.0/corba2/demos/per_mast/BANK.idl
/opt/Orbix_2.0/corba2/demos/per_mast/Makefile
/opt/Orbix_2.0/corba2/demos/per_mast/README
/opt/Orbix_2.0/corba2/demos/per_mast/banksrv.cc
/opt/Orbix_2.0/corba2/demos/per_mast/banksrv.h
/opt/Orbix_2.0/corba2/demos/per_mast/clientc.cc
/opt/Orbix_2.0/corba2/demos/per_mast/demo-cli.cc
/opt/Orbix_2.0/corba2/demos/per_mast/hEntity.h
/opt/Orbix_2.0/corba2/demos/per_mast/hashTbl.cc
/opt/Orbix_2.0/corba2/demos/per_mast/hashTbl.h
/opt/Orbix_2.0/corba2/demos/per_mast/loader.cc
/opt/Orbix_2.0/corba2/demos/per_mast/loader.h
/opt/Orbix_2.0/corba2/demos/per_mast/server.cc
/opt/Orbix_2.0/corba2/demos/per_mult/BANK.idl
/opt/Orbix_2.0/corba2/demos/per_mult/Makefile
/opt/Orbix_2.0/corba2/demos/per_mult/README
/opt/Orbix_2.0/corba2/demos/per_mult/banksrv.cc
/opt/Orbix_2.0/corba2/demos/per_mult/banksrv.h
/opt/Orbix_2.0/corba2/demos/per_mult/clientc.cc
/opt/Orbix_2.0/corba2/demos/per_mult/demo-cli.cc
/opt/Orbix_2.0/corba2/demos/per_mult/loader.cc
/opt/Orbix_2.0/corba2/demos/per_mult/loader.h
/opt/Orbix_2.0/corba2/demos/per_mult/server.cc
/opt/Orbix_2.0/corba2/demos/per_simp/BANK.idl
/opt/Orbix_2.0/corba2/demos/per_simp/Makefile
/opt/Orbix_2.0/corba2/demos/per_simp/README
/opt/Orbix_2.0/corba2/demos/per_simp/banksrv.cc
/opt/Orbix_2.0/corba2/demos/per_simp/banksrv.h
/opt/Orbix_2.0/corba2/demos/per_simp/clientc.cc
/opt/Orbix_2.0/corba2/demos/per_simp/demo-cli.cc
/opt/Orbix_2.0/corba2/demos/per_simp/loader.cc
/opt/Orbix_2.0/corba2/demos/per_simp/loader.h
/opt/Orbix_2.0/corba2/demos/per_simp/server.cc
/opt/Orbix_2.0/corba2/demos/threads/Makefile
/opt/Orbix_2.0/corba2/demos/threads/README
/opt/Orbix_2.0/corba2/demos/timer/Makefile
/opt/Orbix_2.0/corba2/demos/timer/README
/opt/Orbix_2.0/corba2/demos/timer/perf.idl
/opt/Orbix_2.0/corba2/demos/timer/perfclnt.cc
/opt/Orbix_2.0/corba2/demos/timer/perfsrv.cc
/opt/Orbix_2.0/corba2/demos/timer/perfsrv.h
/opt/Orbix_2.0/corba2/demos/timer/server.cc
[ verifying class <demos> ]
## Executing postinstall script.
Do you want this to be your default installation (y,n)? [y]:
PN 9110.01068 23
Type in y to make this the default installation.
----------------------------------------------------------------------
There has been a minor change to the format of the Implementation
Repository directory structure for Orbix 2.0.
Please refer to the RELEASE_NOTES for details.
----------------------------------------------------------------------
Okay, the new CORBA2 mapping component is now installed.
SOME STANDARD INSTALLATION WARNINGS:

------------------------------------
* The Orbix daemon, when run, will use the port number
specified by IT_DAEMON_PORT. To alter this, set IT_DAEMON_PORT
to an appropriate value in your environment, or edit the
value (currently 1570) in the configuration file, Orbix.cfg.
* The library files were not installed in a directory that the

linker (ld) looks in by default. You must specify the Orbix lib
directory to the -L option on the compiler command line
when linking with these libraries.
* When compiling Orbix applications you will need to specify

the Orbix include directory to the -I flag on the compiler command
line so that the C preprocessor can find the correct header files.
* The shared library files were not installed in a directory that

Sun's dynamic linker, ld.so, looks in by default. You must include
the Orbix lib directory in the list of directories
specified in the LD_LIBRARY_PATH variable.
* You'll need to run "/usr/lib/makewhatis" to update the

manual system's index file "windex", so man(1) can find the
Orbix manual pages.
* Your users may need to set the environment variable MANPATH

so it includes the Orbix manual pages in its search path.
Alternatively, you could create soft links in the system
manual directories pointing to the Orbix manual pages.
Notes for this release are available in the file "/opt/Orbix_2.0/RELEASE_NOTES"
----------------------------------------------------------------------
Now cd to /opt/Orbix_2.0/corba2/demos, read the README, and run a "make".
----------------------------------------------------------------------
Installation of <ORBXo20> was successful.

ORBIX installation complete
If you had trouble installing the Orbix software and would like to reinstall just
this part at a later time, you can run:
pkgadd d /tmp/orbix.img ORBXc20 ORBXo20
If you need to remove just the Orbix software, you can run:
pkgrm n ORBXc20 ORBXo20
24 REV 1.0 Aug. 4, 1998

Next, the CGI (or WWW Server) software installation will proceed.
Installing CGI
What account should be used on the fax server [ ]?
CGI installation complete
At the prompt, enter an account that exists on the Fax Server computer that you
intend to use. This account should have been set up in the pre-installation
procedures (see steps 5 and 6 of the Pre-installation Procedures on page 13 and
the example below).
Example
Installing CGI
What account should be used on the fax server [nobody]?
CGI installation complete
Now for the final step, the MVP Server software will be installed.
Installing MVP Server

What is the host name of the MVP [ ]?
What is the computer interface port number [1234]?
What is the www attendant name [service]?
What is the www attendant password [ ]?
What is the EOF string from the MVP [EOF]?
Enter a short description of this MVP [ ]?
MVP Server installation complete
} Use valid data from your MVP.
Installing SNMP
What is the trap community [wwwuser]?
What is the trap sink [host name of webserver]?
Editing /opt/snmp/lib/snmp/snmpd.conf
SNMP installation complete
} Enter the host name where the
traps should be sent.
--- You may want to save the /tmp/wwwinstall.log

file before rebooting the system ---
--- You must reboot the system to complete the

installation ---
--- Installation Complete ---
The trap community is the name of your SNMP management scheme. If you
dont know what to change it to, press enter and the trap community will be set
to wwwuser.
The trap sink is the host name where the traps should be sent. If you dont know
what to change it to, press enter and the traps will be sent to the WWW Server
itself.
The installation program assumes that you will be talking with a single MVP.
Your replies to these prompts are used to edit the MVP Server configuration
files. For more details on MVP Server configuration, see Section 3.3 on page 27.
PN 9110.01068 25
When the --- Installation Complete --- message appears, the

procedure is finished. You can browse through the configuration and startup
files to double check that everything was setup correctly. See Section 3.3 on page
27 and Section 3.4 on page 37 for details of what to look for.
Note A log file of the install session is kept in /tmp/www_install.log.

If you would like to keep this file, move it out of /tmp before the next
reboot.
3.2.1 Post Installation Procedure

In order to start the system, you can simply reboot the computer with the
shutdown command:
/usr/sbin/shutdown g0 y i6
26 REV 1.0 Aug. 4, 1998

3.3 Program and Processes Configuration Details

All of the configuration files described in this section should have been setup
automatically by the installation program. These details are listed for the
purposes of troubleshooting and reconfiguration if necessary. Also refer to the
individual sections in this manual covering the various WWW Server
components and processes.
3.3.1 HTTPD Server Process

The Apache HTTP Server is used for communications between the HTML
and/or Java Client and the WWW Server. This section describes the
configuration of the HTTP Server. For more details, the book "Apache The
Definitive Guide," by Ben Laurie & Peter Laurie, published by OReilly &
Associates is an excellent reference.
/opt/webserv/conf/access.conf
The only parameter that is set in this file is the directory at the very top.
This should be set to /opt/webserv/htdocs.
/opt/webserv/conf/httpd.conf
Most of the configuration parameters for the HTTP Server are in this file.
Below is a brief description of their use:
ServerType The value of standalone indicates that a single

server will start and spawn off numerous children
to handle the incoming requests.
Port This sets the port number to which the Server will
listen for connections.
HostnameLookups If this is on, then every incoming connection is

reverse-DNS resolved. This means that, starting
with the IP number, the Server will lookup the
name of the client by consulting the DNS system
on the Internet. If this is off, then the IP address is
used instead.
User The user name to run httpd as.
Group The group name to run httpd as.
BrowserMatch This is used to disable KeepAlive requests from the

Netscape browser. This is done because of a bug
in Netscape.
ServerAdmin Gives the clients browser an email address for

automatic replies.
PN 9110.01068 27
ServerRoot This is where the subdirectories conf and logs can

be found.
ErrorLog Sets the name of the file to which the server will
write errors.
TransferLog Sets the name of the file to which the server will
log the incoming requests.
PidFile Apache will write the process id of httpd into this

file.
ScoreBoardFile File used to store internal server process informa-

tion.
ServerName Specifies the hostname of the server when creat-

ing redirection URLs.
Timeout This sets the maximum time, in seconds, that the

server will wait for the receipt of a request and
then its completion block by block. This is not the
transfer time, just the round trip of a single block.
KeepAlive This is the maximum number of requests that a

user can do in a single connection. The mailroom
application only handles one (1) request per con-
nection at this time.
MaxKeepAliveRequests The maximum number of requests to allow dur-

ing a persistent connection session.
KeepAliveTimeout How long to wait for the next request (in seconds).
MinSpareServers At least this many child servers will be kept alive

by the Server.
MaxSpareServers No more than this number of child servers will be

left idle.
StartServers The number of child servers to be created at

startup.
MaxClients This directive limits the number of requests that

will be dealt with simultaneously.
MaxRequestsPerChild Each child process of the Server will handle a

number of requests and then be restarted.
28 REV 1.0 Aug. 4, 1998

/opt/webserv/conf/srm.conf
The srm.conf file defines the files on the host that the Server has access to.
DocumentRoot This is the directory out of which html documents

will be served.
Alias /icons/ Tell the server that all references to /icons/

should be read from /opt/webserv/icons/
ScriptAlias Controls which directories contain server scripts.
PN 9110.01068 29
3.3.2 HTML Client (Mailroom) Process

The HTML client (a.k.a. Mailroom) is installed automatically with the CGI
package. This is the component that allows for the HTML interface. Refer also to
the section titled HTML CLIENT on page 61. The primary configuration file for
this server is in:
/opt/webserv/conf/Mailroom. v vconf
This file consists of a series of NAME=VALUE pairs as follows:
cgiPath URL path to CGI program used in FORM decla-

ration.
cmdLineInf Boolean for Command Line Interface.
contact Email address of Mailroom administrator.
customDir URL path to directory for customizable HTML

files and images.
debug Boolean for debug mode
helpPath URL path to directory where help files reside.
htmlPort Port number for HTML socket (socket to

mailroom_pipe cgi program.)
imagePath URL path to directory where image files reside.
logo URL path to GIF or JPG file to be used as the logo

on each page.
logoLink URL of page to which logo should be linked.
logoText Text for the ALT field of the logo IMG tag.
MvpPath Path to program used to interface with the MVP

(currently CGI).
sessionTimeout Seconds of inactivity until Session times out. (Us-

er is required to re-authenticate before resuming
session.)
sessionExpire Seconds of inactivity until Session expires.
30 REV 1.0 Aug. 4, 1998

The other point of configuration for the HTML Client is the mailroom.cgi script.
This file is in:
/opt/webserv/cgi-bin/glenayre/mailroom.cgi
There are three environment variables specified in this script, they are:
SERVER_HOST_PORT This is the TCP port number to use. This should

match the htmlPort variable defined in Mail-
room.conf and should match the Mailroom ser-
vice as defined in /etc/services.
SERVER_HOST_ADDR The IP address of the server. This is typically set

to localhost 127.0.0.1
LOG_DIR Directory where the log files are kept.
PN 9110.01068 31
3.3.3 Java Client Process

Server configuration consists of three different settings. These settings are
shared across clients if more than one client account uses the program locally.
Although these settings are also accessible from within the Java client, they are
not user specific.
For access to configuration outside of the Java client, run the Server program.
From within the Java client, these settings are accessible from the User
Preferences menu, then the Advanced Configuration submenu.
Server IP Address This is the TCP/IP address for the server.
Port Address This is the port on the server where the CGI is
listening, typically 80.
Socket Timeout (seconds) The timeout is how long the client waits for com-
munication response from the server before tim-
ing out.
Server Configuration
Server.ser There is one configuration file that all clients on a

particular computer share: the server file. This
file specifies the IP address, port number, and
timeout setting for the WWW Server.
Users List
Users.ser The system maintains a Users file that keeps an

ordered list of all the users who have been on the
system from this client. This is used for recalling
users when entering the Logon screen at start-up
of the program.
System Log File
Logger.ser This file contains the user preference for the sys-
tem log that specifies whether system logging is
to a file (log.txt) or to the screen.
Version File
Version.ser This file identifies the version of the Java client

including the version number and date.
Configuration File
Config.ser This file contains the user preferences and any

other configurable type of data. Also the users
last Update request time is saved in this file.
32 REV 1.0 Aug. 4, 1998

User Profile File
Profile.ser This file contains the User Profile information that

is retrieved from the MVP. The Profile informa-
tion in this file is updated, after each Update
request.
Folders File
Folders.ser This file contains the Message Directory informa-

tion that was retrieved from the MVP. This file
also contains the folder directory information for
all Folders on the clients system. The information
in this file and the actual folder directory structure
are updated after each Update request.
PN 9110.01068 33
3.3.4 MVP Server Process

The MVP Server process is used to communicate between the WWW Server
software and the MVP itself.
/opt/omcrel/v1.0.1/config/omcenv
OMC_BASEDIR This is set to /opt/omcrel/v1.0.1 to reflect the

base directory for the MVP Server installation.
/opt/omcrel/v1.0.1/config/pu.tbl
This file contains one line for each MVP that the system will communicate
with. At this time there is only one MVP per Server. Each line contains nine
colon (:) separated values.
MVP Hostname The symbolic name of the MVP for this line in the
file.
MVP Port Specifies the computer interface port for this

MVP. The default is 1234.
Attendant Attendant name to be used for all WWW interac-

tions to the MVP.
Password The password for the attendant.
EOF When all results have been sent from the MVP, it
can be configured to send an end of data string.
This field tells MVP Server what that string is. The
default is EOF.
Type For the purposes of the web interface to the MVP,

this will always be MVP_CI.
Attach Zero or one flag indicating whether or not the

MVP Server should make a connection to this
MVP. For a single MVP system, this should al-
ways be one.
Max connections This is the maximum number of connections that

will be opened between the MVP Server and this
MVP. When connections are idle they are closed.
The most connections that the MVP can support
is 8, however using all 8 is not recommended.
Description Some descriptive text for this MVP.
34 REV 1.0 Aug. 4, 1998

/opt/omcrel/v1.0.1/config/range.tbl
This file describes what range of subscriber ids go to which MVP. Each line
in this file describes a range of addresses and maps it to an MVP. There are
5 fields delimited by white spaces.
MVP Hostname This must match with an MVP hostname in the

pu.tbl file.
Type For the purposes of the web interface, this will

always be MVP_CI.
Start The first number in the subscriber id range.
End The last number in the subscriber id range.
Description Some descriptive text for this range.
PN 9110.01068 35
3.3.5 CGI Program

The CGI program uses only a single configuration file. The file is arranged in
NAME=VALUE pairs, one per line.
/opt/webserv/conf/cgi.conf
To get a list of currently supported values, enter the following:

cd /opt/webserv/cgi-bin/glenayre
./CGI -x
You should see output similar to this:
CGI_SMK = 51509
STATS_SMK = 51510
MVP_CONTROL_PORT = 1234
MVP_PIPE_PORT = 5999
MAXPAGERLEN = 22
MAXTSILEN = 22
MVP_IP_ADDRESS = "157.230.163.67"
FAXSERV_IP_ADDRESS = "157.230.162.107"
MVP_EOF = "+ EOF"
LOCALHOST = "127.0.0.1"
MVP_FS = "/"
* LOGFILE_NAME = "/export/home/mike/FAXServer.log"
* PIPE_LOGFILE = "/usr/local/etc/apache/logs/MVPPipe.log"
* DOC_DIRECTORY = "/usr/local/etc/apache/htdocs"
BASE_FAX_DIR = "/usr2/fax"
* COVER_SHEET_TEMPLATES = "/export/home/mike/cs_templates"
TEMPLATE_FIELD_MARKER = "FAXTemplateField"
* FAXUSER = "faxdemo"
* BINDIR = "/usr/local/bin"
The values preceded by an asterisk (*) indicate that they have been changed from
the default. Currently, the only way to change the default values is to add a line
to the configuration file. At this time, some of these variables are not used, and
will not be needed. Currently, these are MVP_PIPE_PORT, MVP_IP_ADDRESS,
FAXSERV_IP_ADDRESS, and PIPE_LOGFILE.
3.3.6 SNMP Agent

All of the SNMP files that are installed on the system are under the /opt/snmp
path. The configuration files are in /opt/snmp/lib/snmp:
snmpd.conf Configuration file for the SNMP agent. The

trapsink and trapcommunity variables are
configured at installation time.
alarmtab.conf This file holds the alarm table definition.

Note: There should be no reason to edit this file.
Also see Section 10. on page 97.
36 REV 1.0 Aug. 4, 1998

3.4 System Startup Details

All startup files for the webserv and its supporting software are in /etc/rc2.d.
S996orbixd
This script is responsible for starting the ORBIX Daemon and interface
repository. The environment variable OBINDIR at the top should be set to
/opt/Orbix_2.0/bin.
S997omcmainsrv
This script is responsible for adding the MVP Server orb to the ORBIX
interface repository. The environment variable OBINDIR at the top should
be set to /opt/Orbix_2.0/bin. The environment variable BASEDIR
should be set to /opt/omcrel/v1.0.1.
S999webserver
This script is responsible for starting the Apache HTTPD Server. The envi-
ronment variable HTTPD_DIR at the top should be set to /opt/webserv.
S99snmp
This script is responsible for starting both the snmpd and snmpalarmd
processes.
S998cgi
This script is responsible for starting the Mailroom Server process.
PN 9110.01068 37
3.5 WWW Server Status

Run the /opt/webserv/bin/webstatus shell program to check the WWW
Server status after the installation. This program verifies if the processes
described in Section 3.4 on page 37 are running. It also checks the reachability of
the MVP.
The output should be similar to the following:
**********************************************************************
MVP Web Server Status
PROCESSES:
----------
Num HTTP servers: 10
Num CGI processes: 0
MVP server: Running [pid=244] production
Mailroom server: Running [pid=263]
SNMP server: Running [pid=306]
Alarm server: Running [pid=296]
FILES (Kbytes):
---------------
HTTP Logs: 1180 [154496 free on /opt]
HTTP Documents: 140646 [154496 free on /opt]
OMC Logs: 51641 [154496 free on /opt]
System Logs: 10 [399940 free on /var]
MVPs:
-----
epa4: Alive
DEFINED SERVICES:
-----------------
omc_ci: 6020/tcp
Mailroom: 9595/tcp
snmpalarm: 7777/udp
DIRECTORY PERMISSIONS:
----------------------
/opt/webserv/logs: is ok
/opt/webserv/htdocs: is ok
IPC STATUS:
-----------
Web server shmem: OK [id=2]
Web server semaphore: OK [id=0]
Alarm server shmem: OK [id=3]
MVP server shmem: OK [id=1]
**********************************************************************
38 REV 1.0 Aug. 4, 1998

3.6 Removing the WWW Server Software

To remove the WWW Server software, first become root and run the
installation program:
su
./www_install
You will see the welcome banner and the first prompt.
*****************************************************************************
*****************************************************************************
G L E N A Y R E E L E C T R O N I C S
Web Server Installation Program
*****************************************************************************
*****************************************************************************
For context sensitive help at any prompt, type '?'. Default values are
displayed in '[]' in each prompt.
What type of operation to perform?

Install
Uninstall
Enter 2 to begin the software removal process. To make sure that you really want
to remove the software, you will be prompted to confirm your selection.
Data will be erased, are you sure [n]?
To continue, enter y at the prompt.
Uninstalling HTTPD
HTTPD uninstallation complete
Uninstalling ORBIX
<some messages from pkgrm>
ORBIX uninstallation complete
Uninstalling CGI
CGI Uninstallation complete
Uninstalling MVP Server

MVP Server uninstallation complete
--- Uninstallation Complete ---
At this point the software has been erased from the system.
PN 9110.01068 39
FIREWALL INSTALLATION
4.1 Overview
This document serves as an extension to the documentation available from Cisco
Systems, Inc. For further reference on installation and configuration please see
the following documents which should be shipped with your CISCO PIX
Firewall:
PIX520DC Installation Guide, Version 4.0, Cisco Systems, Inc., Customer
Order Number DOC-PIX520DC-IG=, Text Part Number 78-4224-01.
PIX Firewall Series Configuration Guide, Version 4.0, Cisco Systems, Inc.,
Customer Order Number DOC-PIXFW-CG=, Text Part Number
78-4222-01.
The PIX Firewall by Cisco Systems, Inc. is used to allow specific packets from the
Internet to connect with the servers inside an installation cluster. For the
purposes of this document, an installation cluster consists of at least the
following:
An MVP
A FAX Server
A WWW server
A Modem pool
A Firewall
The term inside the cluster will refer to all of the above components except for the
outside port of the Firewall, that is anything that is protected by the Firewall.
A set of standardized IP addresses has been assigned for each computer inside
the cluster. These addresses are from the standard range of addresses for private
networking, and thus will never be assigned by the NIC (RFC 1597). The inside
addresses are specified on the next page.
PN 9110.01068 41
Table 4-1 Inside Addresses
IP Address Computer
192.168.160.1 Inside address of the Firewall
192.168.160.10 Address of the WWW Server
192.168.160.20 Address of the Fax Server
192.168.160.30 Address of the MVP
192.168.160.40 Address of the modem pool, net server card
192.168.160.50 Address of the modem pool, total control card.
The WWW Server is the only computer that should be accessible from outside
the Firewall. The Server only allows HTML traffic from the Internet through the
Firewall. The only exceptions to this are administrative connections from a
specific outside server.
4.2 Installing the PIX Firewall
4.2.1 Physical Installation

The PIX Firewall is very easy to install. The notes regarding the physical
installation are derived from the Cisco Systems, Inc. document Installing the
PIX520DC.
1. Remove the PIX unit from the box and mount in the rack with the rest of the
computers with the cluster.
2. Connect the PIX to the 48V DC power supply.
3. Using the null-modem cable supplied with the PIX, connect the port marked
Console to a PC or dumb terminal. Set the line configuration to 9600 baud, 8
data bits, no parity, and 1 stop bit (9600, 8N1).
4. Turn on the PIX and watch the boot messages. You should end up at a
pixfirewall> prompt.
5. Connect the 10baseT cable from the DC hub that contains the rest of the cluster
to the port marked Inside on the PIX. NOTE: This needs to be a cross-over
cable.
6. Connect the 10baseT cable from your Internet router to the port marked
Outside on the PIX. NOTE: This also needs to be a cross-over cable.
42 REV 1.0 Aug. 4, 1998

4.2.2 Software Installation
Note Before you begin this section, you need to have a range of NIC
registered IP addresses for the PIX to use for outbound connections.
Also, you need to have a NIC registered address for the outside port
of the Firewall and for the WWW Server.
The notes in this section are derived from the Cisco Systems, Inc. document PIX
Firewall Series Configuration Guide.
1. From the pixfirewall> prompt, type enable. When asked for a password,
press Enter. A new enable password will be set up later. Your prompt should
now look like:
pixfirewall#
2. From enabled mode type config terminal. This instructs the PIX to
configure itself from the terminal. Your prompt should now look like:
pixfirewall(config)#
3. Enter the following commands:
interface ethernet inside auto
Indicates that you are using an automatic speed detecting ethernet card on
the inside port.
interface ethernet outside auto
Indicates that you are using an automatic speed detecting ethernet card on
the outside port.
ip address inside 192.168.160.1 255.255.255.0
Sets the IP address for the inside ethernet port.

ip address outside ip_address netmask
Sets the IP address for the outside ethernet port.

route outside 0.0.0.0 0.0.0.0 router_ip_address hops
Assigns the default external router. Note that we will leave the internal router
undefined.
static nic_address_for_web_server 192.168.160.10
Defines a static external address for the WWW Server. This will be used with
the conduit command next to allow HTML access.
conduit nic_address_for_web_server 80 tcp 0 0
Allows TCP connections bound for port 80 (HTML) on the WWW Server,
and which can originate from anywhere to get through the Firewall.
PN 9110.01068 43
global 1 first_address_in_pool-last_address_in_pool
Allocates the global address pool. These addresses are used for temporary
outbound connections.
nat 1 0
Allows all outbound connections to pass through the Firewall with address
translation. The PIX will map the actual inside address to an address in the
global pool.
write memory
Saves all of these changes to memory.

^z
Exits from configuration mode and return to privileged (enabled) mode.

4. You can change the enable password with the enable password command.
The password must be no more than 16 characters long and will be converted to
all lower case. The syntax is:
enable password new_password
5. You can allow the PIX to be administered from a computer inside the Firewall
with the telnet command. This command tells the PIX to allow a telnet
session from the specified IP address to connect to the PIX itself. The user will
be prompted for a password before they are allowed access. The syntax is:
telnet inside_IP_address netmask
6. A similar command to telnet is http. This tells the PIX to allow a web
browser client to connect to the PIX as an administrator. You can do the same
things from the http as you can from the telnet session the only difference is
how the data is presented. The syntax of the http command is the same as for
telnet:
http inside_IP_address netmask
7. To change the telnet or http password for external administration use the
passwd command. The password can be no more than 15 characters and will
be converted to all lower case. The syntax is:
passwd password
8. You can use the commands show telnet and show http to view the current
IP addresses which are allowed access. The commands no telnet
IP_address netmask and no http IP_address netmask can be used to
remove an IP address from the list.
9. To allow a computer outside the Firewall to connect to a computer inside the
Firewall for administrative purposes, use the static and conduit
commands. First of all there has to be a static address mapping from the outside
NIC registered IP address to the inside private address. To see if a static
mapping has already been setup, use the show static command. If it has not,
then add one with this syntax:
static global_ip local_ip [max_conns] [em_limit]
44 REV 1.0 Aug. 4, 1998

10. Next, create a conduit using that static address. The conduit specifies who can
connect with which protocol and to which port. The syntax of the conduit
command is as follows:
conduit global_ip port [tcp|udp] orig_ip_address [netmask]
where orig_ip_address and netmask refer to the computer originating the

connection.
4.3 Testing the Installation

Once the PIX is installed and all of the inside computers have been configured
with their assigned IP addresses, it is time to test the installation. Do these tests
in order; if one does not work then the steps listed after it will probably not work
either.
1. From a computer inside the Firewall, ping the inside address of the Firewall
itself (192.168.160.1). If you cannot then the problem is with the internal
network setup. Check the configuration on the computer that you are pinging
from.
2. Ping a computer inside the Firewall from another computer inside the Firewall.
If that fails then the problem is with the individual computer configurations.
Make sure that the computers are configured with the correct IP address and
netmask. Make sure that the default router is set to the inside address of the
Firewall.
3. Ping the outside IP address from a computer outside the Firewall.
4. Ping a computer inside the Firewall from a computer outside the Firewall.
5. Ping the WWW Server (using its static outside address) from a computer
outside the Firewall.
6. Connect to the WWW Server from a computer outside the Firewall.
7. If you have allowed administrative access to an inside computer from the
Internet, validate that you can telnet to the inside computer using its static
outside address.
8. If you have allowed an inside computer access to the PIX for administration,
verify that you can telnet or connect with a web browser from that computer to
the Firewall.
PN 9110.01068 45
MODEM BANK
5.1 Installing the U.S. Robotics Modem Bank
5.1.1 Hardware Installation

The Modem Bank will arrive on site complete with card components already
installed. Below is a list of reference information concerning the Modem Bank:
1. Cards used in the Modem bank will include
one Dual T1 interface board in slot 1
multiple four-port modem cards
one Network Server Card (NSC) in slot 16
one Network Manager Card (NMC) in slot 17
two Redundant Power Supply Cards
2. The Modem Bank operates on -48 VDC input
3. The optimal rack installation is described as follows:
Managed temperature control, 25o C (74o F)
Each chassis installed approximately a 1U gap (approximately 1.71
inches) from the next chassis to allow adequate ventilation.
Mid-mount brackets must be used if you wish to adhere to the Bellcore
Standard on Earthquakes NEBS TR-NWT-000063, Sections 5.5.7 and 5.5.9,
Issue 5.
4. Initial configuration of the modem bank requires the RS-232 interface cables
(which ship with the Modem Bank) and the following adapters which do not
ship with the Modem Bank:
DB25 female to DB25 male NULL modem adapter
Possibly a 9 pin to 25 pin serial port adapter to interface to a PC COM port.
5. T1 connectivity makes use of the Dual T1 interface card in Slot 1 and takes up
the first four modem ports. The first T1 time slot is equivalent to modem port 5
on the NETServer. Modem port 5 corresponds to the first modem in slot 2.
PN 9110.01068 47
MODEM BANK
6. The MVP communications to the Modem Bank is addressed through a

modified LDI (SMLDI) card. A modified LDI (SMLDI) translator board is also
used off the backplane and acts as the T1 interface connection to the Modem
Bank.
7. The T1 interface cable(s) are as follows:
Table 5-1 T1 Interface Cable Pinouts
Terminal Server Modem MVP MVP DB-15

RJ-45 Bank
Pin 1 RX Ring TX Ring Pin 9
Pin 2 RX Tip TX Tip Pin 1
Pin 4 TX Ring RX Ring Pin 11
Pin 5 TX Tip RX Tip Pin 3
8. The connection to the network is established by a 10 base T connection behind

the NETServer Card in slot 16 and the Network Management Card in slot 17.
9. The LDI (SMLDI) Card is to be installed as normal.
For more details on the hardware installation, see the document Total Control
CHASSIS 35A/45A and 70A/130A Ac and DC HARDWARE INSTALL GUIDE.
5.1.2 Modem Bank Card Configuration

1. Use the serial port cable and necessary adapters to configure the NMC card in
slot 17 with the appropriate IP address and subnet mask as determined by the
network administrator.
IP address: (i.e., 157.230.161.160)
SUBNET MASK: (i.e., 255.255.255.0)
Be sure to store these configurations after setting them using menu option 9.
Otherwise, the setting are lost after a reboot.
2. Use the serial port cable and necessary adapters to configure the Netserver card
in slot 16. First login as !root using the enter key as the default password. Set up
the appropriate IP address and netmask (i.e., set net0 address, set net0
netmask).
Set the password as personnel (using the set password command). Set the
gateway to the same address as the IP address of the netserver (i.e., using the set
gateway command). Be sure to save all settings (i.e., save all command) and reset
the Netserver card (i.e., reboot command) after completing the configuration.
48 REV 1.0 Aug. 4, 1998

3. Use the serial port cable and necessary adapters to configure the T1 interface
card in slot 1. First, set the system clock reference list to derive the system clock
from the T1 spans with the local reference as the lowest priority (i.e., the
configuration menu).
Set the T1 line configuration with Framing Mode SF and Line Coding AMI (i.e.,
the line configuration menu). Set the Signaling as E&M type II with immediate
trunk seize and no expected address (i.e., the Call Parameter menu). Most
importantly, be sure to save the configuration to NVRAM and reset the card to
ensure the settings are retained (i.e., Configuration menu).
5.1.3 Modem Bank Configuration

Below is the step-by-step procedure to configure the Modem bank for PPP
connection with Total Control:
1. Start Total Control Manager.
2. Open the desired Modem Bank.
3. Select the modems to be configured by clicking the desired modems.
4. The LEDs for the selected modems should turn blue.
5. Click the configure button.
6. Select Line Interface Options.
7. Change Line Interface Source to t1Tdm.
8. Save these changes by clicking set.
9. Select DTE Interface Settings.
10. Select Default DTE Interface Settings.
11. Change Default DTE Data Format to bit8NoParity.
12. Change DTE Interface Source to packetBus.
13. Save these changes by clicking set.
14. Save the changes to NVRAM.
15. Perform a software reset.
PN 9110.01068 49
MODEM BANK
5.2 Configuring the NETServer

To configure the NETServer, you must first login as !root via Telnet or the
console. Once logged in, the first thing to do is to check the software revision by
typing version. This will produce output similar to
U.S. Robotics
Total Control (tm) NETServer Card V.34/ISDN with Frame Relay V3.4.23
Build date: Mar 6 1997
Build time: 10:12:26
Network Interface Card: Ethernet & Frame Relay Combination (26)
ISDN Interface Card : MUNICH32 (4)
Packet Bus Circuit : Enhanced
Licensed for 60 ports.
The V3.4.23 at the end of the second line is the software revision of the
NETServer card. The commands in this document are correct for version 3.4.23.
5.2.1 Input Filter Configuration

Setup the input filter first since it does not depend on any other tables being
configured. We will create a filter with one rule that allows any outside address
to contact the web server address on port 80. Note that port 80 is the destination
port on the web server, not the origination port on the remote computer. Any
traffic not going to the web server on port 80 will be dropped.
1. add filter www.in
2. set filter www.in 1 permit 0.0.0.0/0 web server IP/32 tcp
dst eq 80
3. save all
Line 1 allocates a new empty filter named www.in.
Line 2 fills in rule #1 for input filter www.in. The rule is read as follows:
permit 0.0.0.0/0 <web server IP>/32 Allow any outside address to connect
to the WWW Server. The /32 means
that all 32 bits of the web servers IP
address must match the destination of
the incoming packet.
tcp dst eq 80 This is a further specification of the first part of the rule. This
means that only TCP traffic is allowed by this rule and that the
destination of any packet must be port 80.
Line 3 writes the configuration to disk.
50 REV 1.0 Aug. 4, 1998

The show table filter command will list all of the filters that are defined on the
NETServer. To view the rules for an individual filter, type show filter filter
name. For the case of www.in, this will display:
- IP rules -
1 permit 0.0.0.0/0 <web server IP>/32 tcp dst eq 80
5.2.2 Address Pool Configuration

Since the dial-in users are assigned IP addresses by the modem pool, the range
of IP addresses to choose from must be defined on the netserver. The addresses
must be contiguous and the pool should be as large as the number of modems
setup for PPP dial-in access.
1. set assigned first address in range
2. set limit 1-512
3. save all
Line 1 tells the netserver the first IP address in the address pool range.
Line 2 tells the netserver how many addresses are in the address range.
The show global command will display the address pool information among
other system wide settings:

Assigned Address: <first address in range>
Assigned Pool Size: <range size>

PN 9110.01068 51
MODEM BANK
5.2.3 User Account Configuration

Next, create an account for the dial-in users. As an example, we will create an
account named webuser with a password of resubew (thats webuser spelled
backwards.)
1. add netuser webuser password resubew
2. set user webuser netmask 255.255.255.255
3. set user webuser compression on
4. set user webuser address assigned
5. set user webuser ifilter www.in
6. set user webuser routing on
7. set user webuser protocol ppp
8. save all
Line 1 creates a new user account and assigns it a password.
Line 2 sets the netmask for this user. A netmask of all 1s (255.255.255.255)
tells the NETServer that this is a PPP account.
Line 3 turns on Van Jacobson compression.
Line 4 tells the NETServer to pick an address from the address pool and assign
to the remote computer.
Line 5 sets the default inbound packet filter for this user. We will leave the
outbound packet filter blank.
Line 6 turns on routing for this user.
Line 7 sets the protocol for this dial in user to PPP.
The show table users command will list every user that is configured on the
NETServer. For example:
Name Type Address/Host Service RIP

-------- ---------------- ------------------- ---------- ---
webuser Netuser Assigned ffffffff Yes
The show user username command will show the configuration for the named
account. For example, show user webuser will result in:
Username: webuser Type: Dial-in Network User

Address: Assigned Netmask: 255.255.255.255
Protocol: PPP Options: Broadcast, Listen, Compression
MTU: 1500 Async Map: 00000000
52 REV 1.0 Aug. 4, 1998

5.2.4 Modem Port Configuration

Configure the modem ports on the modem pool. First determine which ports are
going to be used for PPP access. Remember that the first modem will be
numbered s5 since ports 1 through 4 are used for the T1 interface.
Once the set of ports has been identified, type the following commands for each
port. The notation of s# has been used in place of the actual modem port
identifier (e.g. s5.)
1. set modem s# active
2. set s# network dialin
3. set s# databits 8
4. set s# parity none
5. set s# stopbits 1
6. set s# idletime 60
7. set s# security on
8. set s# autolog
9. set s# ifilter www.in
10. save all
11. reset s#
Line 1 turns on control for this modem port.
Line 2 sets the type of this modem to network dial in.
Line 3 5 sets the databits, parity, and stopbits to 8-N-1.
Line 6 sets the maximum idle time for this port. If no data is transferred for
longer than 60 minutes, the connection will be dropped.
Line 7 turns on security for this port. This means that the NETServer will hang
up on any users who are not in the users table.
Line 8 turns off the autolog feature for this port.
Line 9 assigns the inbound packet filter for this port.
Line 11 resets this modem port.
PN 9110.01068 53
MODEM BANK
The command show s# will show the configuration for the port s#. For example,
show s5 will result in:
----------------------- Current Status - Port S5 --------------------

Status: IDLE
Input: 0 Parity Errors: 0
Output: 0 Framing Errors: 0
Pending: 0 Overrun Errors: 0
Active Configuration Default Configuration

-------------------- ---------------------
Port Type: Netwrk Netwrk (Dial In) (Security)
Login Service: Netdata@6005 Netdata@6005
Device Service: Telnet@6005 Telnet@6005
Modem Stat: READY ACTIVE
Databits: 8 8
Stopbits: 1 1
Parity: none none
Flow Control: None None*
Modem Control: on on
HDLC Framing: PPP in NETServer PPP in NETServer
SLIP Framing: SLIP in NETServer SLIP in NETServer
Remote Host: 0.0.0.0 0.0.0.0
Interface: Unassigned (SLIP,Listen (SLIP,Quiet)
Mtu: 0 1500
Pkt Filters: In:www.in Out:
Modem Presence: Modem is present
Init Script: (None)
Init When?: Never
Login Prompt: $hostname login:
Idle Timeout: 60 min 0 sec
Dial Group: 0
TAP type: OFF OFF
54 REV 1.0 Aug. 4, 1998

5.3 Administrative Tools

The NETServer provides several administrative tools to monitor the system
status at any given time. Some of those commands are listed hereafter.
5.3.1 Viewing DEBUG Messages

The debug command is useful for viewing information which is usually
discarded by the NETServer. The debug command is especially useful to
determine:
Why a dial-in user is failing to connect.
Whether the user is negotiating PAP or CHAP.
What a users final IP address and netmask are.
Any negotiation error codes such as duplicate IP address.
To view debug messages type the following:

set console
set debug code
where code is one of 0x51 for IP and/or IPX connection messages, or 0x71 for
PPP negotiation messages.
WARNING! Unless explicitly told to do so by U.S. Robotics support,

NEVER enter any debug codes other than the three shown
in this section.
When you are finished viewing debug messages, type the following:
set debug 0x00
reset console
5.3.2 IFCONFIG
Use ifconfig to display or reconfigure the current configuration of an
interface. Any changes made in this way only affect the interface while it is
active. When reset, the configuration will revert to its default values.
To view a port or other interfaces active configuration, use the following

command:
ifconfig interface
If you do not specify an interface then all interfaces will be listed. To change
an interface, use the following command:
ifconfig interface option new setting
where interface can be Net0, ptp1, ptp2, etc. The point-to-point
connections must be established in order to be configurable.
PN 9110.01068 55
MODEM BANK
5.3.3 PING
This command verifies that the NETServer can communicate with other devices
on the network. Type:
ping IP address
where IP address is the IP address or name of the device on the network you
want to contact.
5.3.4 PTRACE
This command allows you to monitor network traffic at the packet level. Type
the following:
ptrace filter name
If you type the command without specifying a packet filter, ptrace will be
disabled.
This does not function as an inbound or outbound packet filter since it does not
cause any packets to be dropped. It simply reports any packets that meet the
filter criteria.
When accessing the NETServer by a Telnet session, filter out the administrative
Telnet packets. Otherwise ptrace will report packets from the administrators
own ptrace output, causing a large amount of unusable packet tracing
information to be displayed.
The following is an example filter for PTRACE:

1. deny 0.0.0.0/0 0.0.0.0/0 tcp src eq 23
2. deny 0.0.0.0/0 0.0.0.0/0 tcp dst eq 23
3. permit 0.0.0.0/0 0.0.0.0/0
This example filters out all Telnet packets while allowing all IP traffic to be seen
for the purpose of debugging.
5.3.5 TRACEROUTE
This command is used to determine any routers or hosts that packets route
through en route to the specified IP address. Use the following command:
traceroute IP address
56 REV 1.0 Aug. 4, 1998

5.3.6 SHOW
The show command is used to view the NETServers current configuration and
its routing activity. The command has the following options:
show
all All S ports
arp <interface> IP address resolution data
filter <filter name> A packet filter
flash A summary of flash memory
global Global configuration
init_script <script name> A modem initialization string
ipxroutes The ipxroutes table
isdnservice *ISDN service profiles
isdncallmap *ISDN call mapping table
location <location name> A location table entry
memory DRAM memory usage
netconns Active connections
net0 LAN port configuration
netstat Network statistics
netuser <user name> The specified user
routes or routing The IP routes table
sap SAP interfaces
s<port number> The specified port
sessions Current dial-in sessions
table filter Filter table summary
table hosts Hosts table summary
table location Location table summary
table netmask The netmasks table
table snmp Snmp table summary
table user User table summary
vpn The Virtual Private Network Connections being serviced
tunnel Shows the VPN tunnels on a Specific CBA
user <user name> The specified user
<wan0|wan1> *V.35 port configuration
<wan0|wan1> dlci *Frame relay static DLCIs
<wan0|wan1> mib errors Frame relay error MIB
<wan0|wan1> mib interface *Frame relay interface MIB
<wan0|wan1> mib pvc *Frame relay virtual circuit MIB
* NETServer PRI only
The show commands most commonly used for troubleshooting are arp, flash,
memory, netconns, netstat, sap and sessions.
PN 9110.01068 57
MODEM BANK
5.3.7 TRNKDIAG
Trnkdiag is a utility that may be run from an MVP console. You will need to
know which TSC board you have connected from the MVP to the U.S. Robotics
Modem Bank. TSC 0 is on shelf A and TSC 1 is on shelf B.
This utility also numbers the T1 time slots using zero based numbering. For the
first T1 interface card on a shelf, the first time slot is 0 and the last T1 time slot is
23. The second T1 interface card on a shelf uses time slots 32 to 56.
In the example below, setting the signaling bit on time slot 0 to 0xf causes the
Modem Bank to set its signaling to 0xf and results in the amber light on the
second card from the left in the Modem Bank to illuminate. This indicates that
the T1 connection from the MVP to the WWW Server is active. Afterwards, the
time slot 0 signal should be restored to zero before going to the next channel. In
the event of difficulties, the Modem Bank T1 configuration provides error counts
and signal monitoring abilities for troubleshooting purposes. The LDI diagnostic
port provides similar error counts.
58 REV 1.0 Aug. 4, 1998

For example,
MVP> trnkdiag
Which tsc board do you wish to test?
0
Trunk Diagnostic Utility: <"quit"> to Exit.
TSC Main Menu Functions
t - trunk functions
b - voice buffer functions
i - digital interface functions
d - dialout functions
c - central functions
s - trunk run status
x - 8980 test
v - version number
p - Get Process Data
e - escape to debug mode
quit - Exit trnkdiag
? i
Digital Interface Functions Menu
d - send a command to digital interface
t - toggle digital interface print flag
l - read back ldi card signaling
w - write ldi channel signaling
? w
channel#-> 0
Signaling Nibble-> 0xf
alt chan 0 sending f
? l
RX Signaling, TX Signaling
0 0 0 0 0 0 0 0 f 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

? l
RX Signaling, TX Signaling
f 0 0 0 0 0 0 0 f 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
PN 9110.01068 59
HTML CLIENT
This chapter describes the installation, upgrading, configuration, start-up, and

troubleshooting of the HTML client (a.k.a. Mailroom). The HTML Client
provides support for both subscriber and guest access. Links to the subscriber
and guest interface pages are provided through a "welcome page". For further
details about the HTML client, refer to the programs on-line help.
Note that the HTML client consists of both the HTML browser located on the
users platform and the HTML Client software located on the WWW Server
platform. Most standard HTML browsers (Netscape 2.0x or greater, Internet
Explorer 4.0 or greater, etc.) with Javascript can be used. While the user only
interfaces directly with the HTML browser, problems with the Server software
can affect the client usage. Refer to Section 11. on page 133 for information on
troubleshooting the Server software.
PN 9110.01068 61
HTML CLIENT
6.1 Processes for HTML Client

The supporting processes for HTML clients via Web browsers and their
interfaces are depicted in the following diagram. As shown in the diagram
below, there are two programs added for HTML client support. When the HTTP
server receives a request, it executes the mailroom.cgi program instead of the
CGI. The mailroom-pipe program channels the request through a TCP socket to
the HTML Server.
Mailroom HTTP Mailroom-

HTTP CGI
HTML Client Server pipe
via Browser Process HTTP server invokes
the mailroom.cgi. Process
The mailroom.cgi
channels the request
through a socket to
the Mailroom HTML
server.
TCP socket
TCP socket MVP TCP socket

Server MVP
Process
Mailroom
HTML CGI CGI
Server Process rsh, rcp FAX
Process Server
The CGI interfaces with
The Mailroom server parses the MVP through the MVP
the input from the browser Process and accesses files
and formats it as a CGI request. on the Fax Server.
It creates new HTML output
based on the CGI's response.
WWW Server Platform
Figure 6-1 Processes for HTML Client
6.2 Installation and Configuration

The HTML clients installation and configuration are covered as part of the
previous chapter. See Section 3. on page 13 for installation and configuration
instructions.
The HTML client operates through the World Wide Web. Users should be using
a recommended or accepted browser. It is assumed that the user knows how to
operate the browser. The installation and configuration of the HTML browser as
well as general problems with its usage should be referred to the browsers User
Manual, Web page, or Technical Support Service.For help operating the
browser, refer to the browsers User Manual, on-line help, Web page, or
Technical Support Service.
62 REV 1.0 Aug. 4, 1998

6.2.1 Platform Requirements

The HTML client should work with most popular browsers on most platforms.
The browser must support the following options:
JavaScript JavaScript must be enabled.
Targets Browser must support the targeting of windows from within
Anchors and Forms.
HTML 3.x Browsers supporting either the HTML 3.0 draft specification or
the 3.2 final specification should be sufficient to run the HTML client.
The following browsers are fully compatible with the HTML client:
Netscape Navigator 3.x, 4.x, or greater on any platform. (The Macintosh
versions have a tendency to display very narrow text fields, but have a full
range of functionality.)
Microsoft Internet Explorer (MSIE) 4.0 or greater on any platform.
The following browser will work with the HTML client with some reduced
cosmetic capabilities:
Netscape Navigator 2.x on any platform.
MSIE 3.x Users should upgrade to either MSIE 4.x or Netscape Navigator
4.x, both of which are free.
The following browsers are known to have serious problems running the HTML
client and should be avoided:
Hot Java Users should switch to one of the recommended browsers for
HTML client sessions.
Mosaic Users should switch to one of the recommended browsers for
HTML client sessions.
PN 9110.01068 63
HTML CLIENT
6.3 User Operations
6.3.1 General Usage

Standard elements of each User Interface screen are the Masthead consisting of a
Title Bar, a red horizontal rule running the width of the page, and below the rule,
a Status Bar, and Help Manual Icon.
Title Bar
Each User Interface screen in the HTML client features a Title Bar underscored
with a red horizontal rule running the width of the page. The Title Bar displays
the title for the current screen.
Status Bar
Underneath the red horizontal rule is a Status Bar indicating the status of the
current operation. Always consult the Status Bar first if an operation does not
produce the expected results. The status is mirrored on the browsers status bar
which is usually on the bottom frame of the browser window.
Help Manual Icon
To the right of the Status Bar is the Help Manual Icon. Clicking the Help Manual
Icon will display the on-line help for the current screen in a separate Help
Window.
To perform any operation represented on the screen by an icon, simply click the
icon with the mouse.
Ordinarily, the first input field is automatically selected when a screen is initially
displayed. It is usually possible to tab to the next field or button and press the
Enter key to perform the action for the currently selected button.
Note Some older browsers may not support tabbing to the next field or
button. When using one of these browsers, it is necessary to use the
mouse to select the field or click the button. Consider upgrading your
browser!
64 REV 1.0 Aug. 4, 1998

6.3.2 Accessing the HTML Client

The HTML client can be accessed by entering its URL in the browsers location
field and hitting the Enter key. This location should be book-marked for future
reference. The HTML client should respond with the Welcome screen. The
Welcome screen allows the user to click an HTML link in order to:
Access the Login screen for subscriber logins.
Access the Guest Login screen to login as a guest of a subscriber.
Access the on-line Help manual.
See the on-line Help manual for detailed operating instructions.
6.4 Troubleshooting
When operating the HTML client, problems can occur on both the client and
server platforms. Client problems may be related to an unsupported browser,
improper browser settings, or faulty network connection. The servers problems
may be more likely due to improper installation, erroneous configuration
settings, or lack of file permissions.
See Section 11.7 on page 147 for error codes and general troubleshooting
information.
The following tables should help in diagnosing and curing common problems
on the client and server.
PN 9110.01068 65
HTML CLIENT
6.4.1 Client Problems

Table 6-1 Client Problems
Symptom Possible Causes
Browser responds to efforts to connect to The IP address or domain name is incorrect. Check the IP
HTML client with a dialog stating that it address or DNS name in the location or bookmark.
is unable to locate the server.
Browser times out with a message such The HTTP server is not operating or is not correctly
as: There was no response. The server configured. Follow the instructions in Section 3. on page 13
could be down or is not responding. for installing, configuring and starting the HTTP server.
User receives the message, File Not The WWW Server cannot locate the mailroom.cgi file.
found The requested URL was not Verify that:
found on this server, when attempting the user has entered the correct URL.
to connect to the HTML clients server. the mailroom.cgi file is correctly installed.
the WWW Server can access and run the
mailroom.cgi program.
User receives the message, Mailroom The mailroom.cgi program is unable to interface with
CGI Error *** ERROR: client can't the HTML clients server. This is most likely because
connect to server, when attempting to HTML client is not running. Perform the following checks:
connect to the HTML clients server. use ps ef | grep com.glenayre.mailroom to
make sure that the HTML client is running.
make sure that SERVER_HOST_PORT and
SERVER_HOST_ADDR are set correctly in the
mailroom.cgi script.
Make sure that htmlPort is set correctly in the
Mailroom.conf file.
Be certain that the HTML client is using the correct
Mailroom.conf file. It will use the Mailroom.conf
file under /opt/webserv/conf unless another one is
provided as a command line argument.
Users Login screen just hangs (and is The HTML clients server is not receiving a response from
eventually timed-out by the browser) the CGI program. Make sure that the Mailroom.conf
when attempting to login. file has the correct MvpPath setting.
Buttons, widgets, icons, etc. appear in the This problem has been noted with Netscape 4.0.4 on a
wrong positions on the screen after Windows NT PC using large fonts. While the exact cause
resizing or scrolling the browser. is not known, the screen can be corrected by clicking the
refresh button. This problem might also occur with
unsupported browsers such as HotJava or MSIE 3.0. The
solution in these cases is to upgrade to a supported
browser (see Section 6.2.1 on page 63).
FAXs, help pages, and alphanumeric Browser does not support targeting of windows. Upgrade
messages appear in the main HTML client to one of the supported browsers (see Section 6.2.1 on page
browser window, while the auxiliary 63).
windows intended for them remains
empty.
66 REV 1.0 Aug. 4, 1998

6.4.2 Server Problems

Table 6-2 Server Problems
Symptom Possible Causes
The HTML Client fails to start. This problem is probably due to one of the following
conditions:
Java is improperly installed. See installation
instructions for the JDK or JRE.
The user starting the remote clients server lacks read
permissions for the HTML client class files.
The HTML client class was not found. The command
to start the remote client server must reference it by its
full package name,
com.glenayre.mailroom.server.Mailroom.
The HTML Client starts, but immediately This is probably due to one of the following conditions:
exits. The Mailroom.conf file was not present in the
/opt/webserv/conf directory.
User running the HTML client lacks read permissions
in the /opt/webserv/conf directory.
In the configuration file, Mailroom.conf,
cmdLineInf is set to true, but the HTML client is being
started in the background. Either run the HTML client
as a foreground process or set cmdLineInf to false in
the configuration file.
User running the HTML client lacks write permissions
in the /opt/webserv/logs directory.
If none of these conditions is true, examine the mr.log file
in the /opt/webserv/logs directory for error messages.
Otherwise, a thorough review of the configuration file
settings and the HTML client file locations and
permissions is in order.
PN 9110.01068 67
HTML CLIENT
6.4.3 Advanced Troubleshooting

The HTML Client (a.k.a. Mailroom) software may be run in debug mode for
advanced troubleshooting. The following procedures should only be attempted
by knowledgeable technical personnel:
1. Switch user to root and kill any existing Mailroom Hprocess. The following
examples are indicative of the commands you might use:
su
Password:
ps -ef | grep "jre com.glenayre.mailroom"
nobody 1595 1504 0 09:50:51 ? 0:01 /opt/webserv/jre1.1.5/b
in/jre com.glenayre.mailroom.server.M
root 17235 17234 0 11:07:39 pts/1 0:00 grep "jre
com.glenayre.mailroom"
kill 1595
2. Change to the /opt/webserv directory and switch to user nobody:
cd /opt/webserv
su nobody
3. To run the HTML Client in interactive debug mode run the run_debug script:
./run_debug
4. You will be able to view requests to and responses from the MVP Servers CGI
program.
5. To stop the HTML Client enter stop:
stop
6. To restart the HTML Client in its normal background mode switch back to root
and run the run_mailroom script as nobody:
exit
su nobody -c "/opt/webserv/run_mailroom"
68 REV 1.0 Aug. 4, 1998

JAVA CLIENT
The Java client is a program that provides subscribers with access to their MVP
accounts via a TCP/IP network connection and uses the HTTP protocol. The
Java client provides the remote user with functionality similar to what is
currently available via a telephone session using DTMF input. The Java client
resides on the users platform.
Also see Section C on page 173.
7.1 Processes for Java Client

The supporting processes for the Java client program and their interfaces are
depicted in the following diagram.
MailRoom HTTP
HTTP
Java Server
client The Common Gateway Process
Interface is the interface
between the HTTP server
The User invokes the and a CGI program.
MailRoom Java client
via an application icon.
CGI
TCP socket MVP TCP socket
Server MVP
Process
The CGI interfaces with The MVP Server

the MVP through the MVP CGI provides a synchronized
Server and accesses files Process interface to the MVP.
on the FAX Server.
rsh, rcp FAX

Server
WWW Server Platform
Figure 7-1 Processes for Java Client
PN 9110.01068 69
JAVA CLIENT
The Java client establishes a connection with the HTTP server normally listening
at the standard port 80. When the HTTP server receives a request, it executes the
CGI program. The CGI programs on the WWW Server will process these
requests via the MVP and the FAX server. The WWW Server will respond with
a message that may be as simple as a confirmation of the operation performed or
as complicated as the return of a FAX message as a byte stream. Any client
request may cause the CGI program to generate an operation failure response
that will include the specific reason the operation failed.
The CGI program gets its input from the HTTP server via environment variables
and data streams. The standard input stream (stdin) is used by the HTTP server
to pass streamed data to the CGI program. The CGI program decodes input from
the client and interfaces with MVP through the MVP Server process using TCP
socket interface. The CGI program also access files on the FAX server via rcp and
rsh utilities.
Before the CGI program can send data to its client, it must send a response
header that identifies the type of data it is sending with a Multipurpose Internet
Multimedia Extensions (MIME) content type. Output of the CGI program is sent
to the HTTP server and then the client via the standard output stream.
The HTTP server closes the connection after the response is sent.
70 REV 1.0 Aug. 4, 1998

7.2 Installation and Upgrades
7.2.1 Obtaining Java Client Software

A subscriber can obtain the Java client software three ways:
Compact Disk (CD)
download via HTML browser
download via Java client. (Incremental upgrades are available on-line only.)
7.2.1.1 File Names
For each platform, there are two files containing the Java client software. One
contains the Java Runtime Environment (JRE or MRJ) and the other does not.
Both contain full release of Java client software. The actual file names used differ
depending on the source (CD or download) and the version number.
7.2.1.2 Software Provided on a CD
The Java client distribution CD contains software and installation instructions

for each supported OS platforms. The volume information of the CD is:
mailroom_nn_nn_nn
where, nn_nn_nn is the software release version number.
The CD has three subdirectories:

\win
\mac
\sparc
Each subdirectory has a plain-text instruction file on installing Java client called:
install.txt
You can view this file from the CD.
7.2.1.3 Download via HTML Browser
After receiving an URL for the Java MailRoom Download page, a subscriber can
download the Java MailRoom software using a WWW Browser. The Uniform
Resource Locator (URL) is the common format of address objects on the World
Wide Web. Your URL should look like:
http://www.X/java_client/download.html
where X is the host name or IP address of your web server.
PN 9110.01068 71
JAVA CLIENT
The following figures illustrate the options that are available at different stages
of the download. These figures are for demonstration purposes only (using
Netscape browser to download Windows 95/NT version of software).
The URL for the Java client download page provides a link for each supported
OS: Windows 95/NT, MAC, and Solaris SPARC. See Figure 7-2 and Figure 7-3 as
follows.
Figure 7-2 MailRoom Download HTML Page
Figure 7-3 MailRoom Windows 95/NT Download Page
72 REV 1.0 Aug. 4, 1998

7.2.1.4 Download/or Upgrade via Java client
Subscribers whose computer already has the Java client installed can download
the Java client software at logon. A message box informs the subscriber at logon
if the version currently installed is older than what is available on the server. The
message indicates the users version, whats new in the upgrade, and present
on-line upgrade options. See Figure 7-4 below.
Figure 7-4 Upgrade Options
As shown in Figure 7-4, you may select one of the following upgrade options:
Incremental - normally the preferred option since it has a minimum size.
Incremental with Java - preferred when a newer version of Java is available.
Full - replaces the entire program.
Full with Java - replaces the entire program and the Java software.
Incremental upgrades automatically install themselves while full upgrades

require manual installation. For manual installation see Section 7.2.3 on page 75,
Section 7.2.4 on page 76, and Section 7.2.5 on page 77.
When the new release of Java client requires a newer version of Java, then only
the upgrade options with Java are available.
PN 9110.01068 73
JAVA CLIENT
7.2.2 Hardware and Operating System Minimum Requirements

All clients must have TCP/IP access to the server either via local networking or
via dialup networking. All clients must have a minimum of 4 megabytes of disk
space for the program. This is in addition to the space required for the Java
software.
Windows 95
Memory: at least 32 Mb
Windows NT
Memory: at least 32 Mb
NT 4.0 or greater
Macintosh
Memory: at least 32 Mb Physical, and appropriate Virtual Memory settings
MacOS 8.0 or greater
MRJ 2.0 (Mac OS Runtime for Java) or greater
Sun Solaris
Solaris 2.6
74 REV 1.0 Aug. 4, 1998

7.2.3 Windows 95/NT Installation

If you obtain your download file via the HTML browser, the filenames will be
different from what is described below. Therefore substitute the filenames that
refer to your download files.
7.2.3.1 System Requirements
The following requirements must be met to install the Java client on Windows 95
or NT.
The Java client works with Intel or Intel-compatible based PC systems with
80486 and Pentium or better microprocessors. Windows 95 or NT 4.0 is
required with a minimum of 32 MB of built-in RAM and 30 MB of free disk
space.
JRE 1.1 or JDK1.1 (Java client is compliant with Sun's JDK 1.1).
PPP or intranet/internet connection to the target server.
CD-ROM drive is required for CD installation.
7.2.3.2 Installation Instructions
1. Insert the CD into the CD-ROM drive.

2. Launch Windows/NT Explorer.
3. Click the name mailroom_nn_nn_nn.
4. Navigate to the \win subdirectory and double-click your choice of the
following self-extracting files:
win_fj.exe contains the Java client and Java Runtime Environment. This
file is for a first-time user of Java client software whose computer does not
have JRE installed.
win_f.exe contains the Java client release only. This file is for users who
already have JRE installed.
5. Follow the on-line instructions. By default the unzipped files will be placed in
the c:\MailRoom directory. If desired, you can specify a different path during
installation.
6. If you've selected and installed the file win_fj.exe, double-click the file
jre115-win32.exe in the c:\MailRoom directory (or where you have
installed the Java client) to install the JRE1.1.5.
7. Right-click the file MailRoom95.bat and click Create Shortcut from the
right-click menu.
8. For Windows NT users, right-click the shortcut just created and set its
properties on the Shortcut tab to Run as Minimized.
9. For Windows 95 users, right-click the shortcut just created and set its properties
on the Program tab to Run as Minimized. Also enable the Close on exit
parameter.
10. Double-click the shortcut to start the Java client.
PN 9110.01068 75
JAVA CLIENT
7.2.4 Mac OS Installation
The following requirements must be met to install the Java client on MAC OS.
Java client works with Macintosh or Macintosh-compatible systems with
68040 or PowerPC microprocessors. System 8.0 or later is required with a
minimum of 32 MB of built-in RAM and 40 MB of free disk space.
Systems with 68040 microprocessors must have 32-bit addressing turned
on. This can be done by using the Memory control panel.
Virtual memory must be enabled and set to at least 1.5 times the physical
memory.
MRJ 2.0 (Java client is compliant with Sun's JDK 1.1)
Stuffit software properly installed.
Note MRJ 2.0 is included with Mac OS 8.1, so there is no need to download
it if you already have the Mac OS 8.1 distribution CD.
1. Make sure Stuffit software is properly installed (it is on the Mac OS CD).
2. Insert the CD into the CD-ROM drive and view the contents of the CD via the
CD strip.
3. Navigate to the /win subdirectory and double-click your choice of the
following self-extracting files:
mac_fj.hqx contains the Java client release and Mac Runtime for Java
(MRJ 2.0). This is for a first-time users of Java client software whose
computer does not have MRJ 2.0 installed.
mac_f.hqx contains the Java client release. This is for users who already
have MRJ 2.0 installed.
The following steps use mac_f.hqx as an example. Use mac_fj.hqx instead if

you need MRJ.
4. Drag mac_f.hqx to the desktop. This will create a copy of mac_f.hqx on the
desktop.
5. Expand the file on the desktop via the Magic menu or drag the file and drop it
on the Expander icon. This will create a MailRoom folder on the desktop.
6. Move and/or rename the MailRoom folder onto your hard disk.
76 REV 1.0 Aug. 4, 1998

7. If you have selected the Java client with MRJ option (mac_fj.hqx),
double-click the MRJ icon inside the MailRoom folder from the previous step to
install MRJ. Select the "easy install" option while installing the MRJ.
8. You may clean intermediate files from the desktop by dragging
MailRoom.sea, mac_f.hqx, or mac_fj.hqx to the trash can.
9. Double-click the Java client icon inside the MailRoom folder to start the Java
client.
7.2.5 SPARC Solaris Installation
The following requirements must be met to install the Java client on MAC OS.
Java client works with Sun Solaris SPARC systems. Solaris 2.5 or later is
required with a minimum of 128 MB of built-in RAM and 30 MB of free disk
space.
JRE 1.1 or JDK1.1 (Java client is compliant with Sun's JDK 1.1).
1. Insert the CD into the CD-ROM drive.

2. Open a terminal session.
3. Execute the following command to verify the CD-ROM drive and CD are
working properly:
ls -l /cdrom/cdrom0/sparc
The following file names should be listed in the output from the command
install.txt sparc_f.z sparc_fj.z.
sparc_fj.z contains the Java client software and the Java Runtime
Environment. This file is for first-time users of the Java client software
whose computer does not have JRE installed. First-time users are strongly
encouraged to install from this file.
sparc_f.z contains Java client software only. This file is for users who
already have JRE installed. If you use this file, you must set up your own
shell program to run Java client. A sample.sh program is included in the
tar file as an example. If you do not have JRE installed, use sparc_fj.z
instead.
PN 9110.01068 77
JAVA CLIENT
The following steps use sparc_fj.z as an example. Use saprc_f.z instead if

you dont need JRE.
4. Make a subdirectory for installing the Java client (if you do not have one
already) and navigate to that directory.
5. Copy and rename the file:
cp /cdrom/cdrom0/sparc/sparc_fj.z sparc_fj.Z
6. Uncompress the file:
uncompress sparc_fj.Z
7. Un-tar the file as follows:
tar -xf sparc_fj
8. Setup the DISPLAY environment variable. Consult with your system
administrator if necessary.
9. Run MailRoom.sh (those who install sparc_f.z should use sample.sh as
an example to setup their own MailRoom.sh)
7.3 User Operations

All user operations include extensive on-line help. Context sensitive help is
available when the program is running. The user can always access on-line help
through either the help menu or the help button. For instructions on how to start
the program, see Section 7.5 on page 82.
78 REV 1.0 Aug. 4, 1998

7.4 System Configuration
7.4.1 Configuring Client/Server Communications

The server configuration can be reached separately from the main program via
the Logon screen. Server configuration consists of three different settings. These
settings are shared across clients if more than one client account uses the
program locally. Although these settings are also accessible from within the Java
client, they are not user specific.
For access to configuration outside of the Java client, run the Server program.
From within the Java client, these settings are accessible from the User
Preferences menu, then the Advanced Configuration submenu.
Server IP Address
This is the TCP/IP address for the server.
Note Because the TCP/IP address defaults to 0.0.0.0, it must be set prior to
logon.
Port Address
This is the port on the server where the CGI is listening, typically 80.
Socket Timeout (seconds)
The timeout is how long the client waits for communication response from the
server before timing out.
PN 9110.01068 79
JAVA CLIENT
7.4.2 Configuration Files

All configuration related files are stored in the Java serialized format and have
ser for the filename extension. The system maintains general configuration
files at the program root directory level and account configuration files within
each client account directory.
7.4.2.1 General Configuration Files
Server Configuration, Server.ser
There is one configuration file that all clients on a particular computer share: the
server file. This file specifies the IP address, port number, and timeout setting
for the WWW Server.
Users List, Users.ser
The system maintains a Users file that keeps an ordered list of all the users who
have been on the system from this client. This is used for recalling users when
entering the Logon screen at start-up of the program.
System Log File, Logger.ser
This file contains the user preference for the system log that specifies whether
system logging is to a file (log.txt) or to the screen.
Version File, Version.ser
This file identifies the version of the Java client including the version number
and date.
7.4.2.2 Account Level Configuration Files
Configuration File, Config.ser
This file contains the user preferences and any other configurable type of data.
Also the users last Update request time is saved in this file.
User Profile File, Profile.ser
This file contains the User Profile information that is retrieved from the MVP.
The Profile information in this file is updated, after each Update request.
Folders File, Folders.ser
This file contains the Message Directory information that was retrieved from the
MVP. This file also contains the folder directory information for all Folders on
the clients system. The information in this file and the actual folder directory
structure are updated after each Update request.
80 REV 1.0 Aug. 4, 1998

7.4.3 Client Directory Structure

There are various files that are stored and maintained locally on the Clients
system for each user. There are the configuration files and the folder
subdirectories for each of the folders on a clients system. These subdirectories
contain the corresponding messages for that folder, which have been
downloaded to the local computer. The following diagram depicts the directory
structure on a clients system.
Client Main Directory
Server Configuration File
Users List File
Version File
Logger File
n n n
User A User B User C
Config File Config File Config File
Profile File Profile File Profile File
Folders File Folders File Folders File
InBox Directory InBox Directory InBox Directory

Message File Message File Message File

n n n n n n n n n
OutBox Directory OutBox Directory OutBox Directory


n n n n n n n n n
Archive Directory Archive Directory Archive Directory


n n n n n n n n n
Trash Directory Trash Directory Trash Directory


n n n n n n n n n
n n n n n n n n n
Figure 7-5 Client Directory Structure
PN 9110.01068 81
JAVA CLIENT
7.5 Java Client Start-up

Start-up of the Java client is different for each operating system. However, once
the program has begun, operation of the Java client is identical for every
operating system. This section covers the start-up procedure particular to the
supported operating systems. For more information, refer to the Java clients
on-line help.
7.5.1 Windows 95
1. Change directory to the c:\MailRoom subdirectory (or where you have
installed the Java client).
2. Double click the Java client shortcut to start the Java client.
7.5.2 Windows NT
1. Change directory to the c:\MailRoom subdirectory (or where you have
installed the Java client).
2. Double click the MailRoomNT.PIF to start the Java client.
7.5.3 MacOS
1. Double click the Java client icon inside the MailRoom Folder.
7.5.4 Solaris
1. Change directory (cd) to the subdirectory where the Java client is installed.
2. Run MailRoom.sh.
82 REV 1.0 Aug. 4, 1998

7.6 Troubleshooting
For information on diagnosing the WWW Server, see Section 11.7 on page 147.
7.6.1 System Log Dialogue Box

The Java Client produces debugging information during execution. This
information outputs to either a file (log.txt) or to standard output. The output
destination is user configurable through the "system log" menu item available
from the Logon Window or the Main Menu. Below is a sample of the System Log
Dialoque Box invoked from the Logon Window.
Note In order to view the standard output destination, you must start-up
the Mailroom with the debug setup.
Figure 7-6 System Log Dialoque Box
Note Glenayre Engineering personnel will help you decipher the system log
information once it has been printed out or is available on screen.
PN 9110.01068 83
JAVA CLIENT
7.6.2 Local Fax File Corrupted or Missing

You can perform the function Mark as Not Retrieved on this fax, then retrieve
it again from the server. If the problem persists, then the original file may be
corrupted on the server itself.
7.6.3 No Response To User Commands

Interaction with the server has an associated timeout. When the Java client
makes a request to the server, the Java client waits this long before deciding the
server is unable to respond in a timely fashion. As a result of waiting on a
timeout, it may appear that the program is not performing the user-specified
function. This timeout setting is configurable from the User Preferences Menu,
then the Advanced Configuration submenu.
7.6.4 Memory Trace

This diagnostic tool enables monitoring memory usage of the Java client. It is
accessible from the Help menus and can be invoked before Logon.
84 REV 1.0 Aug. 4, 1998

MVP SERVER PROCESS
This chapter describes the software components necessary to implement the

MVP Server process of the WWW Server. The MVP Server process provides
synchronized interface to the MVP system. It also maintains a shared memory
area for SNMP MIB variables. The functionality and responsibility of each
component is described, as well as the interfaces between individual
components.
8.1 Computer Interface

The MVP Server process interfaces with the MVP via its computer interface
which is described in Section 11.6 on page 143. The MVP itself provides to its client
a computer interface very similar to that of the MVP Server.
The MVP Server computer interface is accessed via a standard TCP/IP session.
The address of the MVP Server is defined in the /etc/hosts file, and the
service name is defined in /etc/services file as omc_ci/tcp. The service
port number is configured by the network administrator. If the service name and
port number are missing, port number 6020 can used as a default.
Access to the computer interface may be made via a Telnet session to the same
address and port number.
When first connected to the computer interface, a logon in the form of a plus sign
(+) is sent, indicating connection has been made, and the computer interface is
waiting for commands. Once commands have been received and processed the
computer interface prompts with another plus sign.
PN 9110.01068 85
MVP SERVER PROCESS
8.1.1 Functional Grouping

The MVP Server Computer Interface is grouped as follows:
Table 8-1 MVP Server specific
Command Definition
get Get the value of the named MVP Server variable which can
be:
TRACE - the trace level. The exact syntax is:
get /TRACE/
RUNMODE - the runmode (production or
maintenance).
CLIENTS - the number of clients current being served.
set Set the value of the named MVP Server variable which can
be:
TRACE - the trace level. For example
set /TRACE=5/
RUNMODE - the runmode. For example
set /RUNMODE=maintenance/
listmvp List the system information of the MVP connected.
MVP CIP
See Section 11.6 on page 143 in the Appendix for details.
8.1.2 Input Command String Syntax

The MVP Server computer interface port is used to provide full duplex
communications with an external computer system. Communications are
handled using predefined command strings.
The general form of a command string is as follows:

command /KEYWORD1=value1/ KEYWORD2=value2/ ...
.../(carriage return)
The command name is entered in lower case and is the first entry in the
command string. Keyword values are entered with a leading slash (/), the
keyword name in UPPER case, "=", and the value. The last keyword is followed
by a slash and a carriage return. Keywords must be entered with enough letters
to be unambiguous - e.g., "PASSWORD" can be entered as "PASS", but not "P".
86 REV 1.0 Aug. 4, 1998

To create the computer interface message packet, follow the order below:
1. Command in lower-case letters.
2. One space.
3. Forward slash (/).
4. Keyword name in capital letters.
5. Equal sign (=).
6. Keyword value.
7. Forward slash (/).
8. As many keyword names, then "/", then values, then "/" as needed for the
command operation.
9. Terminating Carriage Return.
8.1.3 Output Command String Syntax

The server, upon receiving a command from the client, will attempt to process
the command and send back the appropriate response. Each response message
is terminated by the ASCII string /EOT/ indicating completion of the response.
The general form of the response string is as follows:

/KEYWORD1=value1/KEWORD2=value2/... .../EOT/
8.1.4 Error Messages

The general form of the error response string is as follows:
/STAT=XXXXX/EOT/
After a command has been entered into the MVP Server, it will respond with
information and attach the system message EOT/ to the end of the response. If
the system message "EOT/" is proceeded by "STAT=XXXXX/" (where XXXXX is
a 5-hex digit error code), then the command was NOT executed successfully.
Error messages originated from MVP are divided into two types: internal and
execution. Internal errors are prepended with 1 and execution errors are
prepended with 2. A complete list of the "error message numbers" generated
from MVP is described in Section 11.6 on page 143.
PN 9110.01068 87
MVP SERVER PROCESS
The following is a list of MVP Server originated error codes:
Table 8-2 MVP Server Originated Error Codes
Code # Error Message
0x3FFFF Syntax errors.
0x3FFFE No more network resources.
0x3FFFD No more client resources.
0x3FFFC Missing PUID or HOSTNAME.
0x3FFFB No database.
0x3F001 In maintenance mode.
0x30999 MVP CIP time out.
0x1xxxx See Section 11.6 on page 143 for details.
0x2xxxx See Section 11.6 on page 143 for details.
8.2 Shared Memory and SNMP Agent

A block of shared memory is updated by the MVP Server process for SNMP
Agent support. It provides the MVP Server process version number, the time (in
hundredths of a second) since the MVP Server was last started, the number of
concurrent clients, the maximum concurrent clients served, the trace level, the
run mode, and the end of TCP packet delimiter string. It also provides specific
information about each computer interface command it supports. These
includes command name, usage count, and error count for each command.
8.3 Alarm and Trace Log

The MVP Server process logs "trace log" entries using syslog local5 facility.
The log file name is set in the /etc/syslog.conf file.
By default, trace is set to level 3. The trace level can be modified through the
MVP Server computers set command (see Table 8-1 on page 86), or via the trace
utility.
The trace feature can also be disabled entirely by using the trace utility
program (located in /opt/omcrel/v1.0.1/server/directory). The trace
program syntax is as follows:
trace[-t 0|1] -s :serverName -u userName -p password -h
hostname [-d level]
88 REV 1.0 Aug. 4, 1998

Use the following command as an example to disable the trace feature:

#cd /opt/omcrel/v1.0.1/server
#trace -t 0 -s :MvpSrv -u omcadm -p password -h zodiac
The MVP Server process also logs alarm messages to the snmpalarmd process
via UDP messages. See Section 10. on page 97 for more information about the
snmpalarmd process.
8.4 Maintenance Mode

By default, the MVP Server process runs in "production" mode where
commands are synchronized and related to MVP. The process can be
temporarily set to maintenance mode where commands will not be sent to
MVP. In this case the client will be informed about its run mode being in
maintenance.
To set the MVP Server in maintenance mode, use the command as follows.
To set the MVP Server in production mode, use the command as follows.
set /RUNMODE=production/
8.5 File Structure

By default the MVP Server related files is located in the following directories:
/opt/omcrel/v1.0.1/config/
/opt/omcrel/v1.0.1/server/
/opt/omcrel/v1.0.1/logs/
The omcsrv.log in the logs subdirectory contains trace log. This file can get
very big over time. A routine clean-up is required.
The MvpSrv in the server subdirectory provides a synchronized interface to its

clients by relaying the actual computer interface commands to and from the
MVP. The trace utility is to manage trace log activity. See Section 8.3 on page 88
for more details.
PN 9110.01068 89
MVP SERVER PROCESS
The following table lists and describes files contained in the config subdirectory.
Table 8-3 Config Subdirectory Files
File Description
omc.conf General configuration file for the MVP Server software. Every line in this file is
commented out since the defaults are appropriate.
omcenv Environment variables needed by the MVP Server software.
omcuser.tbl The data in this file is not used but the file is required to exist.
pu.tbl This file contains the MVP name that the MVP Server software will connect with.
Each field in each line is separated by a colon (:). The meaning of each field is
described below:
1. host name of a MVP
2. MVP computer interface port
3. attendant
4. password
5. CI_INTERM as defined in autoexec.b
6. machine type-> always MVP_CI
7. attach-> default is 1
8. number of computer interface sessions - default is 4.
9. comments
Example:
mvp1:1234:service:personnel:EOF:MVP_CI:1:4:Atlanta2
range.tbl For the MVP described in the pu.tbl define a range of user IDs that map to that
MVP. The MVP range will be [0-9999999999999999].
Example 1: One MVP system
# Host Type Start End Description
mvp1 MVP_CI 0 9999999999999999 Text description
90 REV 1.0 Aug. 4, 1998

CGI PROGRAM
The MVP Web CGI program (hereinafter referred to as CGI) provides

communications with the MVP and Fax Server. It also maintains a shared
memory area for SNMP MIB variables. This chapter is broken down into sections
concerning process interactions, data storage, and data processing.
9.1 Process Interactions

The WWW Server does not consist of just one program and so CGI must be able
to interact with a variety of other tasks. Among these tasks are the SNMP Alarm
Server for indicating errors, a Fax Server or set of Fax Servers for storing and
retrieving fax messages, the MVP Server process or interacting with an MVP and
the HTML and/or Java Client.
9.1.1 Interactions with the SNMP Alarm Server

The CGI interacts with SNMP Alarm Server in order to notify the MVP Server of
errors or maintenance events that occur on the WWW Server. Primarily, any
time that an error code is generated from the CGI back to the client, at least one
message is sent to the Alarm Server with specific details as to what caused the
error. Messages are sent to the Alarm Server by opening a UDP connection on
the well known port snmpalarm (7777).
PN 9110.01068 91
CGI PROGRAM
9.1.2 Interactions with the Fax Server

If the commands being sent from the Remote Client require that a fax message
be uploaded or downloaded, then the CGI must interact with the Fax Server that
holds the fax message.
In the case of an upload request, the MVP informs CGI of the IP address of the
Fax Server to use to hold the data and the name of the file to place on the Fax
Server. Once this information is available, the file is placed on the Fax Server
with the rcp command. The Fax Server must then be told that it has a new file
so that it can recalculate its storage capacity. This is done using a rsh command
to the Fax Server telling it to execute the /usr/fax/bin/mod_usage
command. This updates the capacity variables held by the Fax Server and is
reflected to the MVP. To confirm the change run view_cap from the MVP
console.
In the case of a download request, the opposite occurs. Given a message ID that
exists on the MVP, ask the MVP for the IP address of the Fax Server that holds
the data, and the name of the file on that computer. Once this data is returned,
the file is transferred with the rcp command from the Fax Server to a temporary
location on the WWW Server.
9.1.3 Interactions with the MVP Server

The MVP Server is the single line of communication between the CGI and the
computer interface of the MVP. When necessary, the CGI opens a TCP socket to
the MVP Server on service port omc_ci (6020). The data for the computer
interface request is written from the CGI to the MVP Server, which in turn relays
that data to the MVP itself. CGI waits until a reply is received from the MVP
Server or until a (configurable) timeout interval expires. The data is then parsed
for error messages, and if none exist, the data is parsed into fields based on the
type of the request.
9.1.4 Interactions with the HTML and/or Java Clients

The HTML and/or Java Clients is the originator of all processing through the
WWW Server. They first contact the HTTP server running on the WWW Server
using a TCP socket to the standard HTTP port (80) and request that the CGI task
be started. From this point the CGI program communicates with the HTML
and/or Java Clients using stdin and stdout commands which have been
redirected by the HTTP server before starting the CGI program.
The HTML and/or Java Clients send the data for a single command code and
wait for the reply. Presently CGI is stateless, so each individual command
represents the life-span of a single CGI task. After the command is completed,
the CGI program exits.
92 REV 1.0 Aug. 4, 1998

9.2 Data Processing

At this time, the CGI is capable of handling the following requests: password
validation, account validation, update, delete, forward, download, upload, and
modify.
9.2.1 Password Validation

Password validation is used by the clients to determine if the user ID and
password given by the user are indeed valid on the MVP.
Among the parameters given is the number of previous failed attempts. If the
number of failed attempts surpasses a user definable threshold, then the CGI
begins to delay its reply to the client. This delay is also user definable, but is
cumulative with the number of failed attempts beyond the threshold.
For example, if the attempt threshold is set to 10, and if the delay is set to 5, then
each attempt up to 10 will experience a 5 second delay. On the eleventh failed
attempt, the CGI waits 10 seconds before sending the failure response. On the
twelfth failed attempt, the CGI waits 15 seconds, 20 seconds on the thirteenth,
and so on.
Also, if a user ID or password is specified which is obviously incorrect (i.e.

contains non-numeric information), the CGI does not send the request to the
MVP but acts as though a failure was generated.
Once the user is validated, the user profile information is retrieved by calling the
usrprofile function on the MVP.
9.2.2 Account Validation

The Account validation process is similar to the password validation above, but
is used in the case of a Guest mode login. Only the account ID is verified with the
MVP. Password validation delays to not occur with this function since no
passwords are given.
Once the Guest user is validated, the user profile information is retrieved by
calling the usrprofile function on the MVP.
PN 9110.01068 93
CGI PROGRAM
9.2.3 Update
The update request is used to return the listing of messages in the subscribers
mailbox. The Remote Client specifies the time stamp of the last successful update
that it performed. The MVP returns the time stamp of the last time a message
changed in the account. If these two time stamps differ, the message directory is
retrieved.
The time stamp information from the MVP is returned by the usrprofile
command. If the time stamps do not match, or if the client specifies that the CGI
should force the update, the directory is retrieved with the msgdir function on
the MVP.
The directory request may be further refined by specifying a subset of messages

to retrieve. For example, only retrieve message information for DMS
alphanumeric and numeric messages.
Note The client may also specify that only a specific number of messages
are returned. The messages returned by the MVP are not sorted in any way.
9.2.4 Delete
The delete request removes a specific message from the MVP, and if necessary
from the Fax Server as well. Messages are specified by the message ID and
dictated time of the message. If the message ID exists, but has a different dictated
time, the MVP assumes that the message was previously deleted and that the
message ID has been recycled, causing an error code to be returned. The
msgdelete command on the MVP is used to perform the delete function.
Note The delete function is performed through future actions on the MVP,
and on a busy system some slight delays may be observed.
9.2.5 Forward
Voice and fax messages may be forwarded from the MVP. The request from the
Remote Client includes a list of user IDs and external phone numbers to send the
message to. For each entry in the list, the msgforward function on the MVP is
called. Any forwarding requests that fail, are noted by storing the actual error
code from the MVP and the user ID or external phone number. When completed,
a list of all error codes generated, if any, is returned to the client.
94 REV 1.0 Aug. 4, 1998

9.2.6 Modify
The modify command is used to change the state of an existing message. The
only state change allowed is from new to saved. The MVP function msgmodify
is used to make this change.
9.2.7 Download
The CGI allows the retrieval of a fax message by the client. The data for the fax
message resides on the Fax Server. The first step in the download process is to
determine the IP address of the Fax Server holding the data, and the location of
the file on the server. The msgget function on the MVP returns this information.
Once that data is available, the file is transferred off of the Fax Server using rcp
and placed into a temporary location on the WWW Server. This file is in
BrookTrout G3 format and must first be converted into a single G3 file for each
page in the message. The utility program bttog3 is used to accomplish this.
Once the G3 file exists for each page, the requested must be converted to GIF
format. The utility program g3togif is used for this. The GIF file is validated
for integrity, and is then transmitted back to the Remote Client. When completed
all of the temporary files are removed from the WWW Server.
9.2.8 Upload
The upload command is used to handle the creation of fax and DMS messages
on the MVP. Common to all types of upload requests is the list of user IDs and
external numbers to receive the new message. Beyond that, the functionality is
different based on the type of message being created.
9.2.8.1 Uploading a DMS Message
DMS messages require that all of the recipients have user IDs. For each user ID
given, the CGI uses msgdep to deposit a message into the account(s) specified.
Like the forward command, if any error is encountered while processing the
list of user IDs, the errors and IDs are noted.
PN 9110.01068 95
CGI PROGRAM
9.2.8.2 Uploading a Fax
A fax message is sent from the Remote Client as a PostScript file. This file may
or may not be accompanied by information to fill out a cover sheet template. The
first operation in the uploading of a fax message is to convert the PostScript file
into a set of G3 files, one for each page. Also, if the cover sheet information is
specified, an additional G3 file is created with the cover sheet image. The
GhostScript program is used for the PostScript-to-G3 conversions.
Next, all of the G3 files must be packed into a single BrookTrout G3 file. This is
done with the g3tobt utility. At this point, we have the file in the exact format
that the Fax Server is expecting.
Now, the msgdep function on the MVP is used to create a new message in the
users account, and to return the IP address of the Fax Server to hold the
message, and the file name to be created on the Fax Server. This message is
deposited into the users account and is stored in a special in prep state. In this
state the message does not count against usage statistics and does not show up
in any directory. The file is now transferred to the Fax Server with the rcp
command. Upon a successful transfer has been completed, the rsh command is
used to execute the mod_usage program. This program instructs the Fax Server
to evaluate the new file and update its capacity numbers.
The CGI then reads the list of recipients and executes a forward command
using msgforward. The error list processing for the forward command is used
for error handling in this part of the upload.
Finally, when all recipients have been forwarded the fax message, the original
in prep message is deleted using msgdelete.
96 REV 1.0 Aug. 4, 1998

SNMP AGENT
Note Knowledge of the SNMP Protocal is required to be able to interpret

and apply the information contained in this chapter.
10.1 SNMP AGENT PROCESS

The SNMP Agent feature of the WWW Server implements and supports MIB
variables as defined in Appendix B on page 157. It includes MIB-II groups system,
interfaces, at, ip, icmp, tcp, udp, and snmp variables. It also supports MVP Server
application specific variables including alarm, statistics, and status. Application
specific variables are kept in three shared memory areas as described in the
following diagram. The five basic SNMP operations, get-request,
get-next-request, set-request, get-response, and trap are supported.
READ MVP Server

SNMP V1 Snmpd Stats
Process WRITE &
Status
READ
&
WRITE CGI WRITE
Stats
SNMP
Manager MVP
Alarm
& Server
Table
Trap daemon Process
READ CGI
&
WRITE D
UP
TRAPS Snmpalarmd UPD

Process
WWW Server Platform
Figure 10-1 SNMP Agent Process
PN 9110.01068 97
SNMP AGENT
10.1.1 CGI Stats Shared Memory Area

The following statistics are maintained in shared memory so that SNMP agents
and other programs can access them.
Table 10-1 Statistic Variables
Statistic Variable Name Description
PasswordFailures Total failed login attempts
bytesFromMvp Total bytes transferred from the MVP
dmsUploadSuccess Total DMS messages uploaded
dmsUploadFailure Total DMS message uploads that

failed
g3ToGif Successful BrookTrout G3 to GIF

conversions
g3ToGifFail Failed G3 to GIF conversions
psToG3 Successful postscript to Brooktrout

G3 conversions. A failure during this
step is most likely due to the fact that
the user uploaded an invalid file type.
There is nothing on the client to
discourage them from doing so.
PsToG3Fail Number of failures during a

postscript to Brooktrout G3
conversion
faxUploadSuccess Number of FAX uploads which

completely succeeded.
TotalUserLogins Total number of successful user

logins
faxUploadFail Number of FAX uploads which failed

for any reason.
TotalGuestLogins Total number of successful guest

logins
pagesIn Pages successfully uploaded
pagesOut Pages successfully downloaded
bytesIn Bytes of successful upload data
bytesOut Bytes of successful download data
smallestIn Smallest postscript file uploaded (in

bytes)
smallestOut Smallest GIF page downloaded (in

bytes)
98 REV 1.0 Aug. 4, 1998

Table 10-1 Statistic Variables (Continued)
Statistic Variable Name Description
largestIn Largest postscript file uploaded (in

bytes)
largestOut Largest GIF page downloaded (in

bytes)
pageDownloadFail Number of single page download

failures
faxServerNotAvailable Total failed attempts to establish a

TCP connection with the FAX server.
MvpServerNotAvailable Total failed attempts to establish a

TCP connection with the MVP server.
Avg10UploadBps Average data rate (bps) of the last 10

uploads.
Avg100UploadBps Average data rate (bps) of the last 100

uploads.
Avg10DownloadBps Average data rate (bps) of the last 10

downloads.
Avg100DownloadBps Average data rate (bps) of the last 100

downloads.
Avg10UploadConversionTime Average number of seconds required

to convert and store an uploaded file
after all bits have been successfully
received from the client. Average is
computed on the last 10 uploads.
Avg100UploadConversionTime Average number of seconds required

to convert and store an uploaded file
after all bits have been successfully
received from the client. Average is
computed on the last 100 uploads.
Avg10DownloadConversionTime Average number of seconds required

to retrieve and convert a page for
downloading. Time required to send
the file to the client is not included in
this average. Average is computed on
the last 10 downloads.
Avg100DownloadConversionTime Average number of seconds required

to retrieve and convert a page for
downloading. Time required to send
the file to the client is not included in
this average. Average is computed on
the last 100 downloads.
PN 9110.01068 99
SNMP AGENT
10.1.1.1 cgiStats Table MIB

Table 10-2 cgiStats MIB Object Identifiers
Object Identifier Syntax Access Definition
cgiStatsIndex INTEGER read-only The cigStats index.

1.3.6.1.4.1.161.11.1.2.200.2.2.1
cgiStatsName DisplayString read-only The text description of the variable

name for this entry.
1.3.6.1.4.1.161.11.1.2.200.2.2.2
cgiStatsValue INTEGER read-only The value of the variable for this

1.3.6.1.4.1.161.11.1.2.200.2.2.3 entry.
10.1.2 MVP Server Shared Memory Area

This block of shared memory is updated by the MVP Server process. It provides
the MVP Server process version number, the time (in hundredths of a second)
since the MVP Server was last started, the number of concurrent clients,
maximum concurrent clients served, trace level, run mode, and end of TCP
packet delimiter string. It also provides specific information about each
computer interface command it supports. These includes command name, usage
count, and error count of each command. These variables are listed in the
following sections.
10.1.2.1 runStatus MIB

Table 10-3 runStatus MIB Object Identifiers
wwwDescr DisplayString read-only MVP server description & version

number.
1.3.6.1.4.1.161.11.1.2.200.1.1 (SIZE (0..80))
wwwUpTime TimeTicks read-only The time (in hundredths of a second)

since the MVP server of was last
1.3.6.1.4.1.161.11.1.2.200.1.2
re-initialized.
wwwClients Gauge read-only The number of concurrent clients

MVP server is serving.
1.3.6.1.4.1.161.11.1.2.200.1.3
wwwClientsPeak Gauge read-only The maximum concurrent clients the

1.3.6.1.4.1.161.11.1.2.200.1.4 MVP server served.
wwwTraceLevel Gauge(3..7) read-write The trace level of the MVP server.

1.3.6.1.4.1.161.11.1.2.200.1.5
wwwRunMode DisplayString read-only The MVP server run mode either

1.3.6.1.4.1.161.11.1.2.200.1.6 production or maintenance.
(SIZE (8..11))
100 REV 1.0 Aug. 4, 1998

10.1.2.2 Command Table MIB

Table 10-4 Command MIB Object Identifiers
wwwCommandIndex INTEGER read-only The MVP server command index for

this entry.
1.3.6.1.4.1.161.11.1.2.200.1.7.2.1
wwwCommandName DisplayString read-only The MVP server command name for

this entry.
1.3.6.1.4.1.161.11.1.2.200.1.7.2.2
wwwCommandAccess INTEGER read-only The number of times the named

command is accessed (used).
1.3.6.1.4.1.161.11.1.2.200.1.7.2.3
wwwCommandError INTEGER read-only The number of times the named

1.3.6.1.4.1.161.11.1.2.200.1.7.2.4 command results in error.
10.1.3 Alarm Table Shared Memory

The WWW Server has an alarm table which identifies every alarm message. The
snmpalarmd process receives alarm messages sent by either CGI, or MVP Server
process. The alarm table will be generated using a text editor such as the unix vi.
The alarm table file name is /opt/snmp/lib/snmp/alarmtab.conf by
default. This file will be loaded automatically at startup and can be loaded at
runtime with SIGHUP. The format of the alarm table is shown below. This table
will use incrementing ID numbers with the first being 1. The ID will be used as
a direct index into this table, and a sanity check will be made to make sure the
ID matches the indexed alarm.
Table 10-5 Alarm Table Shared Memory
ID ACTID Status Level Cat subcat Desc
2 Bytes 2 Bytes 1 Byte 1 Byte 1 Byte 1 Byte 26 Bytes
PN 9110.01068 101
SNMP AGENT
Table 10-6 Alarm Table Index
Field Description
ID The alarm Message ID which will be passed to the alarm task through the alrm_msg function call.
This will be used to reference the alarm call to the entry in the table.
This field will use incrementing ID numbers with the first being 1.
ACTID The Activation ID of the alarm message. This field will be assigned in the table, and may or may not
be unique to a given ID. The Activation ID is used to link a set of alarms. Example: Three different
alarms may have the same Activation ID, One may set the alarm with a minor level, another with a
major level, and a third would clear the alarm. This ID is used to link a set of alarms together as a
group.
The activation ID is used to group together multiple entries in the alarm table so that alarms that are
functionally closely coupled can be cleared as a group.
1 - MVP Server Listener failure

2 - Command from CGI to MVP server failed
3 - Command from MVP server to CGI failed
4 - MVP Server received internal MVP error
5 - MVP Server received external MVP error
6 - MVP Server connection to MVP control port
7 - Command from Client failed
8 - CGI connecting to MVP Server
9 - Message failure on upload request
10 - Cover sheet informational status
11 - CGI IPC system calls failure
12 - write to temp file on Web server failure
13 - read from temp file on Web server failure
14 - Identification failure from the Fax Server
15 - Parse table error
16 - GIF file error
17 - Spawned shell task failure
18 - Recipient list error
19 - Cover sheet configuration file failure
20 - Invalid cover sheet parameters
21 - MVP Server in wrong operational mode
22 - MVP Server service lookup failure by CGI
23 - MVP Server library call failure
24 - request queue failure
25 - MVP Server security violation
26 - MVP Server started
27 - CGI has a TCP read/write failure
28 - Connect to MVP status
29 - Client connection threshold
102 REV 1.0 Aug. 4, 1998

Table 10-6 Alarm Table Index (Continued)
Field Description
Status The Status of a given alarm. This will be a bit defined variable with the following meaning.
0x00 = No alarm active

0x01 = Alarm Active.
0x10 = Do not store in history file (i.e. Do not write to disk)
0x20 = Inhibit all SNMP trap generation.
0x40 = Inhibit this alarm completely.
0x80 = Do not resend alarm if alarm currently active.
Level The alarm level or change state assigned to this alarm. The valid levels are:
6 - no_severity (informational only; Activation ID is always 0)
5 - cleared
4 - warning
3 - minor
2 - major
1 - critical
If Subcat field is status change type then this field means.
0 - Not Ready
1 - In-Service
2 - Out-of-Service
If Subcat field is configuration change type then this field means.
0 - Enabled
1 - Disabled
2 - Initializing
Category The category of the alarm.

1 - MVP Server
2 - CGI
3 - HTTP Server
4 - SNMP Agent
5 - Memory
6 - Disk Space
7 - File System
8 - External Interfaces
9 - Cache Server
PN 9110.01068 103
SNMP AGENT
Table 10-6 Alarm Table Index (Continued)
Field Description
Subcat The sub-category of the alarm message. This will define which SNMP trap type to use when send-
ing this to the MVP Server. See Section 10.2 on page 128 for further information on trap types.
1 - Security Violation Trap.
2 - PM Threshold Trap.
3 - Fault Management Alarm Trap.
4 - Status Change Event Trap.
5 - Configuration Change Event Trap.
6 - Resync Start Type.
7 - Resync Complete Type.
250 - Cold Start Type (Generic 0).
251 - Warm Start Type (Generic 1).
254 - Authentication Failure Type (Generic 4).
Desc A description of the alarm message. This is an ASCII field which is used to identify the alarm in the
alarm table file. This is not the exact text of the alarm message.
10.1.3.1 Default Alarm Table
Initial values in the /opt/snmp/lib/snmp/alarmtab.conf configuration

file.
Table 10-7 Default Alarms
ID A S L C S Description
C t e a u
T t v t b
I u e c
D s l a
t
1 1 0x0 1 1 3 Unable to listen for connections from CGI
2 0 0x40 6 1 4 CGI Socket connection opened
3 2 0x80 2 1 3 Unable to read MVP command from CGI
4 3 0x80 2 1 3 Unable to read MVP response
5 0 0x40 6 1 4 CGI socket connection closed as expected
6 4 0x80 3 2 3 MVP Server received internal MVP error
7 5 0x80 3 2 3 MVP Server received external MVP error
8 6 0x0 2 1 3 MVP Server can not connect to MVP control port
9 6 0x40 6 1 4 Connected to MVP control port successfully
10 7 0x80 3 2 3 Unrecognized command code from client
104 REV 1.0 Aug. 4, 1998

Table 10-7 Default Alarms (Continued)
C t e a u
T t v t b
I u e c
D s l a
t
11 3 0x80 3 2 3 CGI unable to read MVP response from MVP server
12 7 0x80 3 2 3 Improperly formatted command from client
13 8 0x80 3 2 3 Unable to open socket to MVP Server
14 9 0x80 3 2 3 Invalid message type with upload request
15 0 0x40 6 2 4 Provides cover sheet name
16 9 0x80 3 2 3 Attempted to upload to FAX server - Invalid response
17 11 0x80 2 2 3 Unable to obtain mutual exclusion semaphore
18 12 0x80 2 2 3 Unable to write temporary postscript on web server
19 13 0x80 2 2 3 Unable to read pages temporary file on web server
20 14 0x80 3 2 3 Incorrect FAX ID returned by FAX server
21 13 0x80 2 2 3 Unable to read temporary GIF file on web server
22 15 0x80 3 2 3 Unexpected end of parse table
23 16 0x80 3 2 3 GIF file not properly created
24 17 0x80 3 2 3 Spawned shell task failed
25 18 0x80 3 2 3 Recipient list from client is invalid
26 19 0x80 3 2 3 Unable to read cover sheet configuration file
27 12 0x80 2 2 3 Unable to create temporary sed command file
28 20 0x80 3 2 3 Invalid cover sheet parameters from client
29 2 0x80 2 2 3 Write to MVP server failed
30 21 0x80 2 2 3 MVP Server is in maintenance mode
31 22 0x80 2 2 3 Could not look up service 'omc_ci'
50 0 *0x0 5 8 5 Manually clearing alarm
51 23 0x0 3 1 3 Library function call failure
52 24 0x0 2 1 3 Failed building request queue
53 25 0x0 4 1 1 MVP server security violation
54 0 0x0 6 1 4 MVP server started
55 27 0x0 3 1 3 WriteTCP() failed
PN 9110.01068 105
SNMP AGENT
Table 10-7 Default Alarms (Continued)
C t e a u
T t v t b
I u e c
D s l a
t
56 27 0x0 3 1 3 ReadTCP() failed
57 0 0x0 6 1 4 Connected to MVP
58 0 0x0 6 1 4 Connecting to MVP
59 0 0x0 6 1 4 Socket inactive time out
60 0 0x0 6 1 5 Trace level change 3..7
61 0 0x0 4 1 5 Run mode change
62 29 0x0 3 1 2 Reached maximum client connections
63 29 0x0 4 1 2 Reached 85% of maximum client connections
64 0 0x0 6 1 4 Connected to client
65 0 0x0 6 1 4 Disconnected client
* ACT_ID is filled in at run time. Initial value set to 0.
10.1.3.2 Alarm Table Utility
The /opt/snmp/bin/showtab utility allows user access and manages the

alarm table. The syntax for the utility is as described below.
usage: showtab [-AadC] [-c act_id]
-A : list all alarms [Default action]
-a : list only active alarms
-d : list only defined alarms
-C : clear all active alarms
-c act_id : clear alarms with given activation id
106 REV 1.0 Aug. 4, 1998

10.1.3.3 Alarm Table MIB

Table 10-8 Alarm Table MIB
wAlarmId INTEGER read-only A unique number assigned to an

alarm.
1.3.6.1.4.1.161.11.1.2.200.1.3.3.1
wAlarmActId INTEGER read-only Associate wAlarmId together.

1.3.6.1.4.1.161.11.1.2.200.1.3.3.2
wAlarmStatus INTEGER read-only The current status of the

wAlarmId.
1.3.6.1.4.1.161.11.1.2.200.1.3.3.3
wAlarmSeverity INTEGER read-only critical (1), major (2), minor (3),

1.3.6.1.4.1.161.11.1.2.200.1.3.3.4
warning (4), cleared (5),
informational (6)
wAlarmCat INTEGER read-only wAlarmId category:

1.3.6.1.4.1.161.11.1.2.200.1.3.3.5 1 - MVP Server
2 - CGI
3 - HTTP Server
4 - SNMP Agent
5 - Memory
6 - Disk Space
7 - File System
8 - External Interfaces
9 - Cache Server
wAlarmSubCat INTEGER read-only An indication of the type of

enterprise specific trap generated
1.3.6.1.4.1.161.11.1.2.200.1.3.3.6
for this alarm:
1 - Security Violation
2 - PM Threshold Trap
3 - Fault Management Alarm Trap
4 - Status Change Event Trap
5 - Configuration Change Event
Trap
6 - Resync Start Trap
7 - Resync Complete Trap
wAlarmDescription DisplayString read-only A generic description of the alarm.

1.3.6.1.4.1.161.11.1.2.200.1.3.3.7
PN 9110.01068 107
SNMP AGENT
Table 10-8 Alarm Table MIB (Continued)
wAlarmText DisplayString read-only The alarm message.

1.3.6.1.4.1.161.11.1.2.200.1.3.3.8
wAlarmCfgStatus INTEGER read-only 0 - Enabled

1.3.6.1.4.1.161.11.1.2.200.1.3.3.9 1 - Disabled
2 - Initializing
wAlarmIndex DisplayString read-only This field is reserved.

1.3.6.1.4.1.161.11.1.2.200.1.3.3.10
wAlarmTime DisplayString read-only The time of the alarm message

expressed as
1.3.6.1.4.1.161.11.1.2.200.1.3.3.11
YYYYMMDDHHMMSS
wAlarmRunStatus DisplayString read-only 0 - Not Ready

1.3.6.1.4.1.161.11.1.2.200.1.3.3.12 1 - In Service
2 - Out of Service
10.1.4 SNMP Process

On receiving an SNMP packet, the agent will validate the community string. A
community string valid for both set and get PDUs is defined. If this string is not
configured or does not match, the set operation will be disallowed. A second
community string with the default value of public allows GetRequest and
GetNextRequest PDUs. If the second string is configured to be empty, then any
community string may be used for getting variables.
Additional screening of the SNMP packets based on IP address can be

accomplished by having the appropriate entries in the /etc/host.allow and
/etc/host.deny tables.
The snmpd Daemon process reads specific variables from three blocks of shared
memory. These three blocks of shared memory are used for the alarms, statistics,
and status functions.
The SNMP agent listens on UDP port number 161 (default standard) for packets
containing an SNMP operation code, a community string, and a protocol data
unit containing a list of MIB variable bindings. The agent performs the requested
operation on the MIB variables and composes a reply packet containing the
variable binding lists which include the current values of the variables and sends
it back to the manager.
As the MVP Web Server reboots, the snmpd is automatically loaded and it
generates a Cold Start trap.
108 REV 1.0 Aug. 4, 1998

The snmpalarmd process generates an unsolicited SNMP trap packet which

contains a variable binding list which reference MIB variables. The packet is sent
to UDP port 162 (default standard) of a management station.
10.1.4.1 Configuration
The SNMP agent is to be installed in the /opt/snmp directory. The man pages
for the snmpd process and snmpd.conf are located in the /opt/snmp/man
directory.
10.1.5 Snmpalarmd Process

When an alarm call is received by the snmpalarmd process, the ID of the alarm
is used to index into the table to find the other parameters associated with this
alarm. An SNMP trap to the trap destination host (transink) will be generated
for every alarm received, and every alarm will be logged in the alarm history file.
If the alarm level is critical, major, or minor, then the alarm status will be set to
active. If another alarm is received which has a level of cleared then the alarm
task will search the table for every alarm with the same activation ID and clear
the active state. This clearing alarm will also be logged and an SNMP trap
generated.
The subcat field in the alarm file will determine the type of SNMP trap which
will be sent for that event. See Section B on page 157 for additional information on
trap types.
The snmpalarmd process is loaded at boot time. The program may take the
following arguments:
-c <string> trap community string, default value is
public.
-t <host> trap destination host, default value is
localhost.
-p <port> trap destination port, default value is 162.
-f <alarmtab> alarm table, default value is
/opt/snmp/lib/snmp/alarmtab.conf.
-h <hist> history file name, default value is
/var/log/alarmhist.
The /opt/snmp/bin/showtab program can be used to display the alarm table

in memory, to display all active alarms in the WWW Server. This utility will also
have the capability of clearing an active alarm from the command line. If this
utility is used to clear an alarm from the command line then a clear alarm trap
will be sent to the SNMP and an alarm will be logged in the alarm history file
with the alarm text Alarm Manually Cleared.
PN 9110.01068 109
SNMP AGENT
10.1.5.1 Troubleshooting "snmpalarmd" (Alarm Server)
Files/Programs Involved
/opt/snmp/bin/showtab - a simple maintenance program for the
shared memory alarm table
/opt/snmp/etc/snmpalarmd - the alarm server; normally runs as root:
snmpalarmd -t trapsink_host -c community_string
/var/adm/messages - syslogd log file for server's error and status change
messages
/var/log/alarm.hist - alarm history log file: the first character on each
line is a subcategory (for ease of filtering)
/opt/snmp/lib/snmp/alarmtab.conf - the configuration file for the
initial settings of the shared memory alarm table.
/etc/services - should have an entry snmpalarm 7777/UDP for the
server's service port.
/etc/rc2.d/S997snmp - rc file start script
ipcs -m command - should display a shared memory segment with IPC
key 0x00007777 after snmpalarmd starts
Retrieving Server's Error and Status Change Messages
The "snmpalarmd" server uses the syslog mechanism to log its error and status
change messages.
Edit or "tail -f" the /var/adm/messages file.
Ensure the Server is Running
Run ps -ef | grep snmpalarmd.
The normal configuration of the alarm server will contain a line that resembles
this one:
root 6355 1 0 18:31:29 ? 0:00 snmpalarmd -t zodiac -c wwwuser
Reloading the Configuration File
Run ps -ef | grep snmpalarmd to determine the Process ID of the alarm

server.
Perform a kill -1 on the server's process ID. Note that if the shared memory
alarm table contains active alarms, the server will not overwrite the shared
memory table with entries from the configuration file:
/opt/snmp/lib/snmp/alarmtab.conf
110 REV 1.0 Aug. 4, 1998

10.1.6 MIB
The MVP MIB supports full MIB-II group. In addition to the MIB-II group it has
the following additional entries:
runStatus
cmdStats
cgiStats
wwwAlarms
resources
The details of runStatus, cmdStats, cgiStats and wwwAlarms are given in Table
10-3, Table 10-4, Table 10-2, and Table 10-8, respectively. The details of resources
is given below.
10.1.6.1 The Resource Group
At present there are 5 entries under this group:

processes
memory
disk
loadaves
version
Table 10-9 The Processes MIB
processIndex INTEGER read-only Reference index for each observed

process
1.3.6.1.4.1.161.11.1.2.200.4.1.1
processNames DisplayString read-only The table of process names we are

counting.
1.3.6.1.4.1.161.11.1.2.200.4.1.2 (SIZE(0..255))
processMin INTEGER read-only The minimum number of processes

that should be running. An error
1.3.6.1.4.1.161.11.1.2.200.4.1.3
flag is generated if the number of
running processes is less than the
minimum.
processMax INTEGER read-only The maximum number of processes

that should be running. An error
1.3.6.1.4.1.161.11.1.2.200.4.1.4
flag is generated if the number of
running processes is more than the
maximum.
processCount INTEGER read-only The number of current processes

running with the name in question.
1.3.6.1.4.1.161.11.1.2.200.4.1.5
PN 9110.01068 111
SNMP AGENT
Table 10-9 The Processes MIB (Continued)
processErrorFlag INTEGER read-only An error flag to indicate trouble

with a process. It goes to 1 if there is
1.3.6.1.4.1.161.11.1.2.200.4.1.100
an error, 0 if no error.
processErrorMessage DisplayString read-only An error message description of the

problem (if one exists).
1.3.6.1.4.1.161.11.1.2.200.4.1.101 (SIZE (0..255))
processErrFix INTEGER read-write Setting this to 1 will try to fix the

problem if possible.
1.3.6.1.4.1.161.11.1.2.200.4.1.102
Table 10-10 The Memory MIB
memTotalSwap INTEGER read-only Total swap size (kbytes)

1.3.6.1.4.1.161.11.1.2.200.4.4.1
memAvailSwap INTEGER read-only Available swap space (kbytes)

1.3.6.1.4.1.161.11.1.2.200.4.4.2
memTotalReal INTEGER read-only Total real/physical memory

(kbytes)
1.3.6.1.4.1.161.11.1.2.200.4.4.3
memAvailReal INTEGER read-only Available real/physical memory

(kbytes)
1.3.6.1.4.1.161.11.1.2.200.4.4.4
Table 10-11 The Disk MIB
diskIndex INTEGER read-only Reference index for disk MIB.

1.3.6.1.4.1.161.11.1.2.200.4.6.1
diskPath DisplayString read-only Path where disk is mounted.

1.3.6.1.4.1.161.11.1.2.200.4.6.2
doslDevice DisplayString read-only Device path.

1.3.6.1.4.1.161.11.1.2.200.4.6.3
diskMinimum INTEGER read-only Minimum space required for the

disk.
1.3.6.1.4.1.161.11.1.2.200.4.6.4
diskTotal INTEGER read-only Total disk size (kbytes)

1.3.6.1.4.1.161.11.1.2.200.4.6.5
112 REV 1.0 Aug. 4, 1998

Table 10-11 The Disk MIB (Continued)
diskAvail INTEGER read-only Available disk space.

1.3.6.1.4.1.161.11.1.2.200.4.6.6
diskUsed INTEGER read-only Used space on disk.

1.3.6.1.4.1.161.11.1.2.200.4.6.7
diskPercent INTEGER read-only Percentage of space used on disk.

1.3.6.1.4.1.161.11.1.2.200.4.6.8
diskErrorFlag INTEGER read-only Error flag signaling disk is over

minimum required space.
1.3.6.1.4.1.161.11.1.2.200.4.6.100
diskErrorMsg DisplayString read-write A text description of what caused
the error flag to be set.
1.3.6.1.4.1.161.11.1.2.200.4.6.101
Table 10-12 The Loadaves MIB
loadaveIndex INTEGER read-only Reference index for loadaverage.

1.3.6.1.4.1.161.11.1.2.200.4.7.1
loadaveNames DisplayString read-only The list of load average names we

are counting.
1.3.6.1.4.1.161.11.1.2.200.4.7.2
loadaveLoad DisplayString read-only 1, 5 and 10 min load averages.

1.3.6.1.4.1.161.11.1.2.200.4.7.3
loadaveConfig DisplayString read-only The watch point for loadaverages to

signal an error.
1.3.6.1.4.1.161.11.1.2.200.4.7.4
loadaveErrorFlag INTEGER read-only An error flag to indicate trouble

with the loadave. It goes to 1 if there
1.3.6.1.4.1.161.11.1.2.200.4.7.5
is an error, 0 if no error.
loadaveErrorMsg DisplayString read-only A text description of what caused

the error flag to be set.
1.3.6.1.4.1.161.11.1.2.200.4.7.6
PN 9110.01068 113
SNMP AGENT
Table 10-13 The Version MIB
versionIndex INTEGER read-only Index to MIB (always 1).

1.3.6.1.4.1.161.11.1.2.200.4.100.1
versionTag DisplayString read-only CVS tag keyword.

1.3.6.1.4.1.161.11.1.2.200.4.100.2
versionDate DisplayString read-only Date string from RCS keyword.

1.3.6.1.4.1.161.11.1.2.200.4.100.3
versionCDate DisplayString read-only Date string from ctime().

1.3.6.1.4.1.161.11.1.2.200.4.100.4
versionIdent DisplayString Id string from RCS keyword.

1.3.6.1.4.1.161.11.1.2.200.4.100.5
versionClearCache INTEGER read-write Set 1 to clear the exec cache, if

enabled.
1.3.6.1.4.1.161.11.1.2.200.4.100.6
versionUpdateConfig INTEGER read-write Set 1 to read the config file(s).

1.3.6.1.4.1.161.11.1.2.200.4.100.7
114 REV 1.0 Aug. 4, 1998

10.1.6.2 MIB-II Group

Table 10-14 The System Group
sysDescr DisplayString read-only A text description, which should

include information about the
1.3.6.1.2.1.1.1 (SIZE (0..255))
hardware, operating system, and
networking software.
sysObjectID Object Identifier read-only An authoritative identifier assigned to

this product by its vendor.
1.3.6.1.2.1.1.2
sysUpTime TimeTicks read-only The time (in hundredths of a seconds)

since the network management
1.3.6.1.2.1.1.3
portion of the system was last
reinitialized.
sysContact Display String read-write A person responsible for the node,

along with information such as a
1.3.6.1.2.1.1.4 (SIZE (0..255))
phone number.
sysName DisplayString read-write An administratively assigned name

(usually the TCP/IP domain name).
1.3.6.1.2.1.1.5 (SIZE (0..255))
sysLocation DisplayString read-write The physical location of the device.

1.3.6.1.2.1.1.6 (SIZE (0..255))
sysServices INTEGER read-only A coded number that indicated the

layer(s) for which this node performs
1.3.6.1.2.1.1.7 (0..127)
services.
Table 10-15 The Interfaces Group
Object Identifier Syntax Access Description
ifIndex INTEGER read-only Unique index for this entry.

1.3.6.1.2.1.2.2.1.1
- Index
ifDescr Display String read-only Text describing the interface: e.g.,

product name, manufacturer,
1.3.6.1.2.1.2.2.1.2
hardware version.
ifType INTEGER read-only The type of network interface.

1.3.6.1.2.1.2.2.1.3
ifMtu INTEGER read-only The size (in octets) of the largest

protocol data unit that can be sent or
1.3.6.1.2.1.2.2.1.4
received on the interface.
PN 9110.01068 115
SNMP AGENT
Table 10-15 The Interfaces Group (Continued)
ifSpeed Gauge read-only Estimate of current bandwidth in bits

per second. If value is constant or
1.3.6.1.2.1.2.2.1.5
cannot be measured, nominal
bandwidth is used.
ifPhysAddress PhysAddress read-only If applicable, a physical address such

as an Ethernet MAC address, a phone
1.3.6.1.2.1.2.2.1.6
number, or a Packet Data Net
address. Where not relevant, a
0-length octet string.
ifAdminStatus INTEGER read-write Desired interface state.

up(1), down(2),
1.3.6.1.2.1.2.2.1.7
Testing(3)
ifOperStatus INTEGER read-only The current actual operating state.

1.3.6.1.2.1.2.2.1.8 up(1), down(2),
testing(3)
ifLastChange TimeTicks read-only The value of sysUpTime when the

(hundredths of interface entered its current
1.3.6.1.2.1.2.2.1.9
seconds) operational state (0 if the current state
was entered before last initialization
of management entity).
ifInOctets Counter read-only The total number of octets received on

the interface, framing octets.
1.3.6.1.2.1.2.2.1.10
ifInUcastPkts Counter read-only The number of unicast packets

delivered to an appropriate protocol.
1.3.6.1.2.1.2.2.1.11
ifInNUcastPkts Counter read-only The number of non-unicast (i.e.,

broadcast or multicast) packets
1.3.6.1.2.1.2.2.1.12
delivered to an appropriate protocol.
ifInDiscards Counter read-only The number of inbound packets

discarded although no errors were
1.3.6.1.2.1.2.2.1.13
found (e.g., because of lack of buffer
memory).
ifInErrors Counter read-only The number of inbound packets

discarded because they contained
1.3.6.1.2.1.2.2.1.14
errors.
ifInUnknownProtos Counter read-only The number of inbound packets

discarded because they were directed
1.3.6.1.2.1.2.2.1.15
to an unknown or unsupported
protocol.
ifOutOctets Counter read-only The total number of transmitted

octets, including framing octets.
1.3.6.1.2.1.2.2.1.16
116 REV 1.0 Aug. 4, 1998

Table 10-15 The Interfaces Group (Continued)
ifOutUcastPkts Counter read-only The total number of unicast packets

whose transmission to a single
1.3.6.1.2.1.2.2.1.17
address was requested.
ifOutNucastPkts Counter read-only The total number of packets whose

transmission to a multicast or
1.3.6.1.2.1.2.2.1.18
broadcast address was requested.
ifOutDiscards Counter read-only The number of outbound packets that

were free of error, but were discarded
1.3.6.1.2.1.2.2.1.19
(e.g., to free up memory).
ifOutErrors Counter read-only Number of outbound packets

discarded because of errors.
1.3.6.1.2.1.2.2.1.20
ifOutQLen Gauge read-only Number of packets in the outbound

queue.
1.3.6.1.2.1.2.2.1.21
ifSpecific Object Identifier read-only The identifier for a MIB that contains
additional definitions that relate to
1.3.6.1.2.1.2.2.1.22
this interface type.
Table 10-16 The At Group
atIfIndex INTEGER read-write The index of this interface.

1.3.6.1.2.1.3.1.1.1
Index
atPhyAddress Phys.Address read-write The Physical address. If the value is

null, then this entry is not in use.
1.3.6.1.2.1.3.1.1.2
atNetAddress Network read-write The Network Address (e.g., IP

Address Address) corresponding to the
1.3.6.1.2.1.3.1.1.3
physical address.
Index
PN 9110.01068 117
SNMP AGENT
10.1.6.3 The IP Group

Table 10-17 Basic IP Configuration Parameters
ipForwarding INTEGER read-write Indicates whether the system will

route datagrams.
1.3.6.1.2.1.4.1 forwarding (1),
not-
forwarding(2)
ipDefaultTTL INTEGER read-write Default Time-To-Live value, used

when an application does not specify
1.3.6.1.2.1.4.2
a value.
Table 10-18 IP Address Table
ipAdEntAdr IpAddress read-only The 32-bit (4-byte) IP address for this

entry.
1.3.6.1.21.4.20.1.1
- Index
ipAdEntIfIndex INTEGER read-only The corresponding network interface

(ifIndex).
1.3.6.1.21.420.1.2
ipAdEntNetMask IpAddress read-only The subnet mask for this IP address.
1.3.6.1.2.1.4.20.1.3
ipAdEntBcastAddr INTEGER read-only Indication of the broadcast format for

the interface. 1 for the all 1s standard,
1.3.6.1.2.1.4.20.1.4.
0 for all 0s format.
ipAdEntReasmMaxSize INTEGER read-only The biggest datagram that can be

reassembled from fragments received
1.3.6.1.2.1.4.20.1.5
at this interface.
118 REV 1.0 Aug. 4, 1998

Table 10-19 IP Routing Table
ipRouteDest IpAddress read-write A destination IP address. 0.0.0.0 is

used for a default entry.
1.3.6.1.2.1.4.21.1.1
- Index
ipRouteIfIndex INTEGER read-write The index of the interface (ifIndex)

through which traffic to this
1.3.6.1.2.1.4.21.1.1
destination should be transmitted.
ipRouteMetric1 INTEGER read-write The primary routing metric for this

route. Its meaning depends on the
1.3.6.1.2.1.4.21.1.3
routing protocol (see the
ipRouteProto variable).
ipRouteMetric2 INTEGER read-write Another routing metric.

1.3.6.1.2.1.4.21.1.4

1.3.6.1.2.1.4.21.1.6

1.3.6.1.2.1.4.21.1.6
ipRouteNextHop IpAddress read-write The IP address of the next hop of this

route.
1.3.61.2.1.4.21.1.7
ipRouteType INTEGER read-write The status or type of the route.

1.3.6.1.2.1.4.21.1.8 other(1),
Invalid(2)
direct(3),
indirect(4)
ipRouteProto INTEGER read-only The protocol by which the route was

learned.
1.3.6.1.2.1.4.21.1.9
ipRouteAge INTEGER read-write Number of seconds since last update

or validation of this route.
1.3.6.1.2.1.4.21.1.10
ipRouteMask IpAddress read-write Routing mask for the entry. Some

newer protocols carry this
1.3.6.1.2.1.4.21.1.11
information.
ipRouteMetric5 INTEGER read-write Yet another route metric.

1.3.6.1.2.1.4.21.1.12
ipRouteInfo Object Identifier read-only A pointer to more MIB variables for

the protocol. If not specified, the
1.3.6.1.2.1.4.21.1.13
value should be {0 0}.
PN 9110.01068 119
SNMP AGENT
Table 10-20 Statistic for IP Routing Discards
ipRoutingDiscards Counter read-only The number of valid routing entries

1.3.6.1.2.1.4.23 that were discarded-possible to free
up memory.
Table 10-21 IP Address Translation Table
ipNetToMediaIfIndex INTEGER read-write The index of this interface.

1.3.6.1.2.1.4.22.1.1
- Index
ipNetToMedia Phy read-write A Physical address of the interface.

1.3.6.1.2.1.4.22.1.2
Address
ipNetToMediaNetAddress IpAddress read-write The IP Address

1.3.6.1.2.1.4.22.1.3
- Index
ipNetToMediaType INTEGER read-write How the entry was learned. Also, use
invalid to delete the entry.
1`.3.6.1.2.14.22.1.4 other(1),
invalid(2),
dynamic(3),
static(4)
Table 10-22 IP Statistics
ipInReceives Counter read-only Total number of incoming datagrams.

1.3.6.1.2.1.4.3
ipInHdrErrors Counter read-only Input datagrams discarded due to

1.3.6.1.2.1.4.4 header errors (bad checksums,
version number mismatch, format
errors, time-to-live exceeded, bad IP
options, etc.
ipInAddrErrors Counter read-only Input datagrams discarded because

1.3.6.1.2.1.4.5 the destination IP address was not
valid here.
120 REV 1.0 Aug. 4, 1998

Table 10-22 IP Statistics (Continued)
ipGoteFsyshtsmd Counter read-only Number of incoming datagrams for

1.36.1.2.1.4.6 which forwarding was attempted.
ipInUnknownProtos Counter read-only Datagrams addressed to this system

1.3.6.1.2.1.4.7 whose protocol was unknown or
unsupported.
ipInDiscards Counter read-only Correct datagrams that were

1.3.6.1.2.14.8 discarded anyway, possibly because
of lack of buffer memory.
ipInDelivers Counter read-only The number of IP datagrams

1.3.6.1.21.4.9 delivered to local protocols.
ipOutRequests Counter read-only Total number of IP datagrams

1.3.6.1.2.1.4.10 delivered to local protocols.
ipOutDiscards Counter read-only Outputs datagrams discarded

1.3.6.1.2.1.4.11 although there was no error (but
possibly a lack of buffer space).
ipOutNoRoutes Counter read-only Output datagrams discarded because

1.3.6.1.2.1.4.12 no route can be found.
ipReasmTimeout INTEGER read-only The Maximum number of seconds

1.3.6.1.2.1.4.13 that received fragments are held for
reassembly.
ipReasmReqds Counter read-only The number of IP fragments received

which needed to be reassembled.
1.3.6.1.2.1.4.14
ipReasmOKs Counter read-only The number of IP datagrams

successfully reassembled.
1.3.6.1.2.1.4.15
ipReasmFails Counter read-only The number of times that reassembly

1.3.6.1.2.1.4.16 failed.
ipFragOKs Counter read-only Number of successfully fragmented

1.3.6.1.2.1.4.17 datagrams.
ipFragFails Counter read-only Number of IP datagrams discarded

1.3.6.1.2.1.4.18 because they needed to be
fragmented but could not be.
ipFragCreates Counter read-only Number of IP datagram fragments

1.3.6.1.2.1.4.19 created.
PN 9110.01068 121
SNMP AGENT
10.1.6.4 The ICMP Group

Table 10-23 Statistics for Incoming ICMP Messages
icmpInMsgs Counter read-only Total number of incoming ICMP

1.3.6.1.2.1.5.1 messages.
icmpInErrors Counter read-only Number of incoming ICMP messages

1.3.6.1.2.1.5.2 that contained errors (e.g., bad
checksum, length, type).
icmpInDestUnreachs Counter read-only Number of incoming ICMP

1.3.6.1.2.1.5.3 Destination Unreachable messages.
icmpInTimeExcds Counter read-only Number of incoming ICMP Time

1.3.6.1.2.1.5.4 Exceeded messages. These signal
expired Time-To-Lives and timeouts
on reassembly of fragments.
icmpInParmProbs Counter read-only Number of incoming ICMP

1.36.1.2.1.5.5 Parameter Problem messages (most
often relate to problems in optional IP
header fields).
icmpInSrcQuenchs Counter read-only Number of incoming ICMP Source

1.3.6.1.2.1.5.6 Quench messages.
icmpInRedirects Counter read-only Number of incoming ICMP Redirect

1.3.6.1.2.1.5.7 messages. A host should update its
routing table based on the Redirect
information.
icmpInEchos Counter read-only Number of incoming ICMP Echo

1.3.6.1.2.1.5.8 request messages
icmpInEchoReps Counter read-only Number of ICMP Echo Reply

1.3.6.1.2.1.5.9 messages received.
icmpInTimestamps Counter read-only Number of incoming ICMP

1.3.6.1.2.1.5.10 Timestamp request received.
icmpInTimestampsReps Counter read-only Number of incoming ICMP

1.3.6.1.2.1.5.11 Timestamp Reply messages received.
icmpInAddrMasks Counter read-only Number of incoming ICMP Address

1.3.6.1.2.1.5.12 Mask Requests received.
icmpInAddrMaskReps Counter read-only Number of incoming ICMP Address

1.3.6.1.2.1.5.13 Mask Reply messages received.
122 REV 1.0 Aug. 4, 1998

Table 10-24 Statistics for Outgoing ICMP Messages
icmpOutMsgs Counter read-only Total number of ICMP messages that

1.3.6.1.2.1.5.14 the entity attempted to send.
icmpOutErrors Counter read-only Number of failed attempts to send

1.3.6.1.2.15.15 ICMP messages due to problems such
as lack of buffer space.
icmpOutDestUnreachs Counter read-only Number of ICMP messages sent to

1.3.6.1.2.1.5.16 report unreachable destinations.
icmpOutTime Excds Counter read-only Number of ICMP messages sent to

1.3.6.1.2.1.5.17 report Time Exceeded.
icmpOutParmProbs Counter read-only Number of ICMP messages sent to

1.3.6.1.2.1.5.18 report a Parameter Problem.
icmpOutSrcQuenchs Counter read-only Number of ICMP Source Quench

1.3.6.1.2.1.5.19 messages sent.
icmpOutRedirects Counter read-only For a router, the number of ICMP

1.3.6.1.2.1.5.20 Redirect messages sent. (Hosts do not
send Redirects.)
icmpOutEchos Counter read-only Number of ICMP Echo Request

1.3.6.1.2.1.5.21 Messages sent
icmpOutEchoReps Counter read-only Number of ICMP Echo Reply

1.3.6.1.2.1.5.22 messages sent.
icmpOutTimestamps Counter read-only Number of ICMP Timestamp Request

1.3.6.1.2.1.5.23 messages sent.
icmpOutTimestampsReps Counter read-only Number of ICMP

1.3.6.1.2.1.5.24
Timestamp Reply messages sent.
icmpOutAddrMasks Counter read-only Number of ICMP Address Mask

Request messages sent.
1.3.6.1.2.1.5.25
icmpOutAddrMaskReps Counter read-only Number of ICMP Address Mask

1.3.6.1.2.1.5.26 Reply messages sent.
PN 9110.01068 123
SNMP AGENT
10.1.6.5 The TCP Group

Table 10-25 TCP Configuration: Basic Parameters
Object Identifier SynTax Access Description
tcpRtoAlgorithm INTEGER read-only The algorithm used to compute the

1.3.6.1.2.1.6.1 retransmission timeout.
other(1),
constant(2),
rsre(3),
vanj(4)
tcpRtoMin INTEGER read-only Minimum lower bound in

1.3.6.1.2.1.6.2 milliseconds on the retransmission
timeout. Its meaning depends on the
algorithm.
tcpRtoMax INTEGER read-only Maximum upper bound in

1.3.6.1.2.1.6.3 milliseconds allowed for a
retransmission timeout (Rto). Its
meaning depends on the algorithm.
tcpMaxConn INTEGER read-only A limit on the maximum number of

1.3.6.1.2.1.6.4 concurrent TCP connections. -1
means that it is dynamically
determined.
Table 10-26 TCP Connection Statistics
Object Identifier SynTax Access Description
tcpActiveOpens Counter read-only The number of outgoing connection

1.3.6.1.2.1.6.5 requests from this system.
tcpPassiveOpens Counter read-only The number of incoming connection

1.3.6.1.2.1.6.6 requests to this system.
tcpAttemptFails Counter read-only The number of failed connection

1.3.6.1.2.1.6.7 requests - incoming and outgoing.
tcpEstabresets Counter read-only The number of established or

1.3.6.1.2.1.6.8 gracefully closing connections that
have been terminated abruptly.
tcpCurrEstab Gauge read-only The number of TCP connections that

1.3.6.1.2.1.6.9 are in either ESTABLISHED or
CLOSE-WAIT state.
124 REV 1.0 Aug. 4, 1998

Table 10-27 Segment Counts
tcpInSegs Counter read-only Total number of segments received,

1.3.6.1.2.1.6.10 including those received in error.
tcpOutSegs Counter read-only Total number of segments sent,

1.3.6.1.2.1.6.11 excluding those containing only
retransmitted octets.
tcpRetrans Counter read-only Total number of segments containing

1.3.6.1.2.1.6.12 retransmitted data.
tcpInErrs Counter read-only Total number of segments received

1.3.6.1.2.1.6.14 with errors.
tcpOutRsts Counter read-only Total number of TCP segments sent

1.3.6.1.2.1.6.15 with the reset flag set to 1.
Table 10-28 TCP Connection Table
tcpConnState INTEGER read-write The current state for the connection.

1.3.6.1.2.1.6.13.1.1
tcpConnLocalAddress IpAddress read-only The local port number for this TCP
1.3.6.1.2.1.613.1.3 connection.
-Index
tcpConnRemAddress IpAddress read-only The remote IP address for this TCP

1.3.6.1.2.1.6.13.1.4 connection.
tcpConnRemPort INTEGER read-only The remote port number for this TCP
1.3.6.1.2.1.6.13.1.5 connection.
(0.65535)
-Index
PN 9110.01068 125
SNMP AGENT
10.1.6.6 The UDP Group

Table 10-29 Incoming and Outgoing UDP Traffic
udpInDatagrams Counter read-only Total number of UDP datagrams

1.3.6.1.2.1.7.1 delivered to UDP applications.
udpNoPorts Counter read-only Total number of received UDP

1.3.6.1.2.1.7.2 datagrams for which there was no
application at the destination port.
udpInErros Counter read-only Number of UDP datagrams that

1.3.6.1.2.1.7.3 could not be delivered fore some
other reason-e.g., a bad checksum or
insufficient memory resources.
Table 10-30 Information on Current UDP Listeners
udpLocalAddress IpAddress read-only The local IP address for this UDP

1.3.6.1.2.1.7.5.1.1 listener.
-Index
udpLocalPort INTEGER read-only The local port number for this UDP
1.3.6.1.2.1.7.5.1.2 listener.
(0.65535)
-Index
10.1.6.7 The SNMP Group

Table 10-31 Incoming SNMP Traffic Counts
snmpInPkts Counter read-only Total number of incoming SNMP

1.3.6.1.2.1.11.1 messages delivered by the transport
service.
snmpInBadVersions Counter read-only Number of incoming messages with

1.3.6.1.2.1.11.3 an unsupported version.
snmpInBadCommunityNames Counter read-only Number of incoming messages with

1.3.6.1.2.1.11.4 an unknown community name.
snmpInBadCommunityUses Counter read-only Number of incoming messages

1.3.6.1.2.1.11.5 requesting an operation not
supported for the community name.
snmpInASNParseErrs Counter read-only Number of times message decoding

1.3.6.1.2.1.111.6 failed.
126 REV 1.0 Aug. 4, 1998

Table 10-31 Incoming SNMP Traffic Counts (Continued)
snmpInTooBigs Counter read-only Number of incoming messages with

1.3.6.1.2.1.11.8 an error-status field of too big. This
means that the response would not fit
into the largest permissible message
allowed between this agent and
manager.
snmpInNoSuchNames Counter read-only Number of incoming messages with

1.3.6.1.2.1.11.9 an error-status field of
noSuchName. This means that a
requested object is not supported by
the agent.
snmpInBadValues Counter read-only Number of incoming messages with

1.3.6.1.2.1.11.10 an error-status field of badValue.
This means that a value in a
corresponding outgoing set-request
had a bad data type, incorrect length,
or inappropriate value.
snmpInReadOnlys Counter read-only Number of incoming messages with

1.3.6.1.2.1.11.11 an error-status field of readOnly.
This signals that there is a local
implementation error because an
inappropriate set-request was sent.
snmpInGenErrs Counter read-only Number of incoming messages with

1.3.6.1.2.1.11.12 an error-status field of genErr,
which means an error different from
those listed above.
PN 9110.01068 127
SNMP AGENT
10.2 Traps
Currently, the following traps are MVP specific traps which can be generated by
the SNMP agent.
10.2.1 wwwSecurityEvent
VARIABLES
wAlarmId
wAlarmActId
wAlarmCat
wAlarmSeverity
wAlarmIndex
wAlarmTime
wAlarmDescription
wAlarmText
This trap indicates that a security violation has been detected by the WWW. The
value of wAlarmSeverity will always be set to 6 (informational) and the value of
wAlarmActId will always be set to 0.
10.2.2 wwwPMThreshEvent
VARIABLES
wAlarmId
wAlarmActId
wAlarmCat
wAlarmSeverity
wAlarmIndex
wAlarmTime
wAlarmDescription
wAlarmText
This trap indicates that the WWW has transitioned through a resource threshold,
which potentially could result in a degradation of service or the loss of data.
128 REV 1.0 Aug. 4, 1998

10.2.3 wwwFaultEvent
VARIABLES
wAlarmId
wAlarmActId
wAlarmCat
wAlarmSeverity
wAlarmIndex
wAlarmTime
wAlarmDescription
wAlarmText
This trap indicates that the WWW has encountered a fault in either hardware or
software operation. The category field should be examined for the subsystem
affected.
10.2.4 wwwStatusChangeEvent
VARIABLES
wAlarmId
wAlarmActId
wAlarmCat
wAlarmSeverity
wAlarmIndex
wAlarmTime
wAlarmDescription
wAlarmText
wAlarmRunStatus
This trap indicates a change in the operational state of the WWW Server. The
value of wAlarmSeverity will always be set to 6 (informational) and the value of
wAlarmActId will always be 0.
PN 9110.01068 129
SNMP AGENT
10.2.5 wwwConfigChangeEvent
VARIABLES
wAlarmId
wAlarmActId
wAlarmCat
wAlarmSeverity
wAlarmIndex
wAlarmTime
wAlarmDescription
wAlarmText
wAlarmCfgStatus
This trap indicates that the WWW Server has had its configuration changed or
reloaded. The value of wAlarmSeverity will always be set to 6 (informational)
and the value of wAlarmActId will always be set to 0.
10.2.6 wwwResyncStartEvent
VARIABLES
wAlarmId
wAlarmActId
wAlarmCat
wAlarmSeverity
wAlarmIndex
wAlarmTime
wAlarmDescription
wAlarmText
This trap indicates that a WWW Server has begun resending outstanding trap
alarms. The value of wAlarmSeverity will always be set to 6 (informational) and
the value of wAlarmActId will always be 0.
130 REV 1.0 Aug. 4, 1998

10.2.7 wwwResyncCompleteEvent
VARIABLES
wAlarmId
wAlarmActId
wAlarmCat
wAlarmSeverity
wAlarmIndex
wAlarmTime
wAlarmDescription
wAlarmText
This trap indicates that a WWW Server has finished resending outstanding trap
alarms. The value of wAlarmSeverity will always be set to 6 (informational) and
the value of wAlarmActId will always be 0.
10.2.8 Generic Traps

Cold Start Trap (Generic 0)
Warm Start Trap (Generic 1)
Authentication Trap (Generic 4)
PN 9110.01068 131
TROUBLESHOOTING THE WWW SERVER
11.1 Processes
The Glenayre WWW Server consists of several programs operating together in a
conduit of information starting from the MVP and ending with the Remote
Client. The major components of this conduit are as follows:
httpd The Apache HTTP server software. This is the

front line of interface with the WWW Server com-
puter and the remote client. The client connects
with an httpd server and request that the CGI
program be started or that a session on the Mail-
room program be started. All of these servers run
as the user nobody, although this is configurable
through the User option in httpd.conf.
CGI This is the main WWW Server program. This is

where the actual computer interface commands to
the MVP are created. Both the JAVA and HTML
only versions of the client pass through this pro-
gram at some point. Since this is spawned by
httpd, it runs as user nobody, or whoever the
httpd is configured to run as.
snmpalarmd The SNMP alarm server is who listens for messag-

es from CGI and others and keeps up with the
state of an alarm table. If necessary a SNMP TRAP
is broadcast from this server. This server is run as
root and is started when the computer boots.
snmpd The SNMP agent of the WWW Server. The server

is run as root and is started when the computer
boots.
PN 9110.01068 133
faxserver_stats This is run once at the boot time of the computer.

If given a parameter of create it creates a shared
memory segment and a semaphore. All of the
statistics that are kept by the WWW Server are
stored in this shared memory segment. To view
the contents of the shared memory, run this with
a parameter of dump. While the initial instance
should be run as root, anyone can run the dump
option from the command line.
MvpSrv This CORBA ORB is the server who relays the

actual computer interface commands to and from
the MVP. This is run as root and is started when
the computer boots.
Mailroom The Mailroom HTML server application is a

JAVA program that dynamically generates the
HTML pages for the HTML client. It is accessed
by the mailroom.cgi program in cgi-bin. It is
the mailroom.cgi that is started by the remote
web browser. This application is run as root and
is started when the computer boots. See Section 6.4
on page 65 for diagnostic information.
11.2 Packages
The WWW Server does not exist by itself. It relies on several supporting
packages to be in place. Here is a detail of those packages.
Orbix The Iona Orbix CORBA runtime system is in-

stalled with the WWW Server. This is necessary
for the MvpSrv process to run. The files for this
software are installed under /opt/Orbix_2.0.
JAVA The JAVA Runtime Environment (JRE) version

1.1.5 is installed with the WWW Server. This is
used by the Mailroom server application. The files
for this software are installed under /opt/web-
serv/jre1.1.5.
Oracle Some Oracle runtime libraries are required by the

MvpSrv process. These libraries are installed in
/opt/oracle.
MVP Server This is the package that contains the MvpSrv

itself. These files are installed under
/opt/omcrel.
134 REV 1.0 Aug. 4, 1998

GhostScript For uploads, the GhostScript package is used to

convert PostScript files to Group 3 fax (G3) files.
The GhostScript application lives in
/opt/webserv/bin.
BrookTrout Since the Glenayre fax server uses BrookTrout

hardware, it is necessary to convert the G3 files to
a BrookTrout G3 format. Also, it is necessary to
convert the BrookTrout G3 format back into stan-
dard G3 files. The conversion software to do this
resides on the fax server itself for now. We have
begun work to port these conversions to Solaris
so that they can be run on the WWW Server itself.
11.3 Configuration Files

There are two main configuration directories, each containing several
configuration files. The directories are as follows. For more details on any given
file, see Section 3. on page 13.
/opt/omcrel/v1.0.1/config/
omc.conf General configuration file for the MVP Server

process. Every line in this file is commented out
since the defaults are appropriate.
omcenv Environment variables needed by the MVP Server

process.
omcuser.tbl The data in this file is not used but the file is
required to exist.
pu.tbl This file contains the MVP that the MVP Server
process will connect with.
range.tbl For the MVP described in the pu.tbl define a

range of user IDs that map to the MVP. The range
is [0-9999999999999999].
/opt/webserv/conf/
Mailroom.conf Configuration parameters used by the Mailroom

HTML server for HTML client access only.
debug.conf Debug configuration parameters for the Mail-

room HTML server.
access.conf Used by the HTTP server to designate access priv-

ileges.
PN 9110.01068 135
alarmtab SNMP alarm table definition as used by snm-

palarmd.
cgi.conf Configuration file for the CGI process. The set-

tings in this file override the default settings com-
piled into the CGI program. To view the current
settings (merged with the cgi.conf file) run
CGI x. Entries that have an asterisk (*) in the left
hand column have been replaced with a value
from this file those without the asterisk are the
default. Values with an env in the left hand mar-
gin are exported to the environment for any sub-
tasks that are spawned.
httpd.conf This is the main configuration file for the HTTP

server.
mime.types A mapping of file extensions to client-types.
srm.conf Space resource manager file used by HTTP. This

allows you to define what space users of the
WWW Server will be able to see. Note that access
to these spaces is controlled in access.conf.
snmpd.conf Configuration file for the SNMP server process.
11.4 Log Files

Over time these log files may grow to be very large. The Unix based chronlog
utility periodically monitors the file size and creates backup files as required.
/opt/omcrel/v.1.0.1/logs
omcsrv.log This file keeps track of the data being passed

through the MvpSrv program. Each CI request
and its response can be viewed in this file.
/opt/webserv/logs/
access_log Each connection and request that the HTTP server

listens to is logged in this file. The log includes the
originating IP address, the date and time of the
connection, and the request.
error_log Errors noted by the HTTP server are kept in this

file. Each line contains the date and time of the
error and a description of what the error is.
httpd.pid This is the process ID of the top level HTTP server.

Use this PID if you want to reset the HTTP servers.
136 REV 1.0 Aug. 4, 1998

Issue this command from the shell:

kill HUP `cat httpd.pid`
mr.log The Mailroom server program will log excep-

tions, major errors, and events of note.
/var/log
alarm.hist This is a log of each alarm that is noted by the

snmpalarmd. Each line contains an alarm num-
ber, the date and time of the alarm, an alarm level
indicator (major, minor, ), and a description of
the alarm.
snmpd.log Log of the SNMP servers activities.
snmptraps.log Log of the snmp.d processors activities.
11.5 Tracking Down Problems

Problems are usually of one of two types, either a problem in the flow of
communication between the MVP and the Remote Client, or a problem in the
communication between the WWW Server and the Fax Server.
The flow of information between the MVP server and the Remote Client starts
on the MVPs computer interface port (1234). From there it goes to the MvpSrv
running on the WWW Server. It outputs the information to the CGI task that will
writes it back to the Remote Client.
To diagnose a problem in the MVP-to-Client communication, use the usrprofile

CI function as a test. The syntax is:
usrprofile /ATTEND=attendant_id/PASSW=attendant_password/
USERID= account_number/ACCTPW=account_password/
All of these characters run together; the only space is between the usrprofile
and the first slash.
PN 9110.01068 137
11.5.1 Problems with Communication
11.5.1.1 Reachability Test
This test will confirm that there is reachability from the WWW Server to the MVP
and to the Fax server.
1. Issue this command from the WWW Server shell:
/usr/sbin/ping host name of MVP
/usr/sbin/ping host name of Fax server
11.5.1.2 Test the MVP
This test will check whether the MVP is working properly.

1. Telnet to the MVP on port 1234. Issue this command from the shell:
telnet mvp 1234
2. When presented with the + prompt, enter the test command. You should see
several lines of output.
3. If you see an error, make sure that you entered the command correctly. Check
spelling, case, no spaces, proper ID, and password. If all of these are correct
then the MVP is the cause of the problem. Record the error number and either
look it up below or call for support.
11.5.1.3 Test the MvpSrv Process
This test will check whether the MvpSrv is working properly.

telnet webserver_name omc_ci
This will connect with the port that the MvpSrv is listening to. You should see
the following message:
Trying 157.230.162.231...
Connected to zodiac.glenatl.glenayre.com.
Escape character is '^]'.
MVP Server Computer Interface V1.00
followed by a + prompt just like on the MVP. If you do not, then the MvpSrv is
not running properly.
2. Issue this command from the shell:
ps ef | grep MvpSrv
If you do not see a listing for the server then it is not running. If you do see an
entry, then perhaps it is not listening properly.
138 REV 1.0 Aug. 4, 1998

3. Grep for the "omc_ci" string:

grep omc_ci /etc/services
If it is not defined, then add the following entry to the end of /etc/services:
omc_ci 6020/tcp
4. Try the telnet again. If it is still not working, then try resetting the MvpSrv. The
easiest way to do this is to reboot the computer.
5. Note that the MvpSrv has two modes of running, production and maintenance.
To set the production mode, issue the telnet command as described above and
type:
6. To set the maintenance mode, issue the telnet command as described above and
type:
set /RUNMODE=production/
7. To view the current state, type:
get /RUNMODE/
11.5.1.4 CGI Debugging
This test will check whether the CGI program has been installed properly and set
up with the desired configuration parameter.
CGI x
The output should look like this:
CGI_SMK = 51509
STATS_SMK = 41510
MAXPAGERLEN = 200
MAXTSILEN = 22
* DEBUG_FLAG = 80
SECURITY_SLEEP_TIME = 5
SECURITY_FAIL_COUNT = 3
MVP_EOF = "+ EOF"
LOCALHOST = "127.0.0.1"
MVP_FS = "/"
DOC_DIRECTORY = "/opt/webserv/htdocs"
COVER_SHEET_TEMPLATES = "/opt/webserv/cs_templates"
* FAXUSER = "nobody"
BINDIR = "/opt/webserv/bin"
env LD_LIBRARY_PATH = "/usr/openwin/lib"
2. To view the contents of the cgi.conf, issue the following command:

cat /opt/webserv/conf/cgi.conf
PN 9110.01068 139
Output from the above command may look as follows:
FAXUSER=nobody
DEBUG_FLAG=0x80
3. To change any of these variables, edit the /opt/webserv/conf/cgi.conf

file to add or modify the desired variables.
Two of these variables are referred to often: FAXUSER, and DEBUG_FLAG

which are described below. The rest are not commonly used and are not
described here.
4. The DEBUG_FLAG sets the debug level. Issue the following command for
information on how to set up the debug level.
CGI -h
-i[nteractive] ... Prompt me on the command line for input

-d[ebug] ......... Enable debug messages.
flags are a hex bit field of:
0x001 - Print function entry messages
0x002 - Print function parameters
0x004 - Print upload file conversions
0x008 - Print download file conversions
0x010 - Commands sent to the MVP
0x020 - Parser messages
0x040 - Highlight messages to client
0x080 - Show spawned task command lines & return codes
-h[elp] -? ....... Print this message
-rm .............. Do not remove temporary files
-x ............... Dump config & context info
The debug information is logged to the /opt/webserv/logs/debug file.

5. The FAXUSER variable is the user name on the fax server for allowing fax
access from the WWW Server. See the next section for more details.
11.5.1.5 Problems Talking to the Fax Server
This test will check whether the fax server is functioning properly.
1. Test whether the CGI program can gain access to the fax server. On the WWW
Server, switch user to root:
su -
Password:
Sun Microsystems Inc. SunOS 5.6 Generic August 1997
2. As root, switch user to nobody:
su - nobody
3. Change to the CGI program's directory:
140 REV 1.0 Aug. 4, 1998

4. From there, make sure that you can connect to the fax server without being
challenged for a password. You can find the account the that is used on the fax
server by executing CGI with the -x option:
CGI -x
CGI_SMK = 51509
STATS_SMK = 41510
MAXPAGERLEN = 200
MAXTSILEN = 22
DEBUG_FLAG = 0
SECURITY_SLEEP_TIME = 5
SECURITY_FAIL_COUNT = 3
MVP_EOF = "+ EOF"
LOCALHOST = "127.0.0.1"
MVP_FS = "/"
* DOC_DIRECTORY = "/usr/local/etc/apache/htdocs"
* COVER_SHEET_TEMPLATES = "/export/home/mike/cs_templates"
* FAXUSER = "faxdemo"
BINDIR = "/opt/webserv/bin"
* env LD_LIBRARY_PATH = "/usr/openwin/bin"
5. The parameter FAXUSER is the user name that is used on the fax server. Issue
the following command for this faxuser:
rlogin faxserver_ip -l faxuser
If you are asked for a password then the faxuser account is not properly
configured.
6. If the faxuser account is not properly configured, login to the fax server and
look at the .rhosts file in faxuser's home directory:
ls -al .rhosts
-rw-r--r-- 1 root sys 86 Mar 26 17:35 .rhosts
Make sure the file is owned by root and readable by faxuser.

7. Display the contents of the .rhosts file:
cat .rhosts
webserv bpitts
webserv nobody
webserv gsmith
Make sure there is a line in the file containing the name of the WWW Server
(webserv in the example) followed by nobody or whomever the CGI program
is running as.
PN 9110.01068 141
8. Make sure the /etc/hosts file on the fax server contains an entry for the
WWW Server:
cat /etc/hosts
127.0.0.1 localhost
101.102.13.104 webserv webserv.mysite.mycompany.com
If not, edit the /etc/hosts file to add an entry for the WWW Server. Then try
to rlogin from the WWW Server (see step 5) again.
9. If the CGI is not gaining access to the fax server, perhaps the disk is full. The
/var/tmp directory is used for transient files and the /usr2/fax directory is
used for the actual fax files. To check the space run:
df -kB /var/tmp /usr2/fax
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/root 4190889378641 381224810% /var/tmp
/dev/root 4190889378641 381224810% /usr2/fax
10. Examine the output. If the file systems are out of space then see if you can clear
any files. You can probably only clear files in /var/tmp.
If everything is running fine with the fax server but you still cannot transfer files,
make sure that the permissions on the /opt/webserv/htdocs directory is
world writable:
11. On the WWW Server list the /opt/webserv directory with the -l option and
note the htdocs permissions:
ls -l /opt/webserv
...
drwxrwxrwx 6 ftan staff 512 Apr 27 14:22 htdocs
...
The permissions for htdocs should be drwxrwxrwx.
142 REV 1.0 Aug. 4, 1998

11.6 Computer Interface Procedure Notes

These are input parameters expected for each CIP used by the WWW Server.
Table 11-1 CIP Input Parameters
Procedure Input Parameters (bold = required)
msgdir ATTEND PASSW USERID ACCTPW MSGSTATE

SMSGTYPE CNTN CLIENT
msgget ATTEND PASSW USERID ACCTPW MSGID DICTIME

CLIENT
msgdelete ATTEND PASSW USERID ACCTPW MSGID DICTIME

CLIENT
msgforward ATTEND PASSW USERID ACCTPW MSGID DICTIME

FORWARD CLIENT
msgdep ATTEND PASSW USERID SMSGTYPE MSGSTATUS

CALLBACK MSGLENGTH MSGDATA MSGSTATE
FAXINFO CLIENT
msgmodify ATTEND PASSW USERID ACCTPW MSGID DICTIME

MSGSTATE CLIENT
usrprofile ATTEND PASSW USERID ACCTPW CLIENT
tstpasswd ATTEND PASSW USERID ACCTPW CLIENT
These are output parameters generated for each CIP used by the WWW Server.
The parameters listed in order of output.
Table 11-2 CIP Output Parameters
Procedure Output Parameters
msgdir MSGSTATE MSGSTATUS SMSGTYPE CALLBACK

MSGLENGTH MSGTIME MSGDATE MSGID MSGHOST
FAXID FAXHOST MSGSENDER MSGSEQNO DMSSEQ
FAXINFO DICTIME MSGDATA
msgget MSGSTATE MSGSTATUS SMSGTYPE CALLBACK

MSGTIME MSGDATE FAXID FAXHOST FAXINFO
MSGLENGTH MSGID MSGHOST MSGSENDER
MSGSEQNO DMSSEQ DICTIME MSGDATA
msgdelete USERID MSGID
msgforward USERID MSGID
msgdep USERID MSGID FAXID FAXHOST DICTIME
msgmodify USERID MSGID
PN 9110.01068 143
Table 11-2 CIP Output Parameters (Continued)
Procedure Output Parameters
usrprofile USERID LANGUAGE USERTYPE FORWARDING

MHANDLING UTAG ACCTNUM NUMMSGS ASTATUS
NUMFAX MWISTAT NEWMSGS OLDMSGS INPREP
SERVICES TIMEZONE ACCTMOD VOICEMOD
FAXMOD DATAMOD MINALEN MAXALEN MINNLEN
MAXNLEN PCNT AFULLCNT PAGECLASS
tstpasswd USERID
Several of the parameters are fields of bit flags. What follows is a definition of
what the bit flags represent for each such field.
Table 11-3 SMSGTYPE
Flag Value
1 DMS Alpha
2 DMS Numeric
4 Voice
8 Fax
Table 11-4 MSGSTATE
Flag Value
1 New, Heard
2 New, Unheard
4 Saved
8 In Preparation
Table 11-5 MSGSTATUS (Some values omitted)
Flag Value
0 Normal
1 Confidential
8 Non-delivery Notification
16 Urgent
144 REV 1.0 Aug. 4, 1998

Table 11-6 SERVICES (Output by usrprofile)
Item Description
0x0001 Voice mail services enabled
0x0002 DMS numeric services enabled
0x0004 Alpha services enabled
0x0008 Email services enabled
0x0010 WWW services enabled
0x0020 Follow Me Messaging enabled
0x0040 Restrict CLI on outdials.
0x0080 Message blocking enabled
0x0100 Message blocking activated
0x0200 Follow Me Messaging Capability enabled
0x0400 unused
0x0800 unused
0x1000 unused
0x2000 unused
0x4000 unused
0x8000 Fax services enabled. (Not visible; configurable only

through the software)
Table 11-7 MHANDLING (Output by usrprofile)
Item Description
0x01 Disconnect after last message for auto-step
0x02 Tutorial
0x04 Simplified Playback
0x08 Return to Voice Dial after last auto-step message.
0x10 LIFO playback (else FIFO
0x20 Disable received from header
0x40 Auto-step playback (retrieval only)
PN 9110.01068 145
Table 11-8 ASTATUS (Output by usrprofile)
Item Description
0x001 Auto Attendant
0x002 Suspend record
0x008 Malicious call trace
0x020 Announce & disconnect caller
0x040 Announce & transfer to operator
0x060 Announce & Re-id to next mailbox
0x100 Dispatch service
0x200 Not billable on MFCR2 link
0x800 Time Dependent Greetings Enable
0x1000 Voice Dial Enable
Table 11-9 MWISTAT (Output by usrprofile)
Item Description
0x01 MWI on
0x02 Urgent only MWI
0x04 Urgent outside time window
0x08 Enable repeats for successful MWI
0x10 Enable repeats for successful external delivery
0x20 Notify on each new message
146 REV 1.0 Aug. 4, 1998

11.7 Error Codes

The error codes that are sent to the client have the following format:
<Failure Opcode><Error Type><Error Code>
Failure opcode is one of the following:
Table 11-10 Failure Opcodes
Code Description
00 General Failure
01 Bad ID or Password
02 Error reading message or account
03 Sanity check failure on MVP
04 Error allocating memory on MVP
05 Find failed on MVP
06 Dictated time mismatch
07 Update failed
08 Forward to self error (no longer valid)
09 Message deposit failed
10 Message deposit error
11 Class of service error
12 Message modification failed
13 MVP not responding
14 Fax server not responding
15 Conversion failed
16 Timeout
17 Connection to the MVP failed
18 The MVP (MvpSrv) is in maintenance mode
19 Service (omc_ci) not found
There are three types of errors that can be returned to the client, MVP Computer
Interface Internal errors, MVP Computer Interface External errors, and WWW
Server Errors. These types are represented by the letters I, E and W
respectively.
The error code field is a four digit hexadecimal number. The number in this field
will mean different things depending on the error type.
PN 9110.01068 147
Error types of Internal indicate that something is incorrect with the MVP or
WWW Server at a low level. Users should not be able to cause internal errors. If
you get one of these, call for support.
Error types of External can be caused by a users input or actions. Common

values that may be generated for these are as follows:
Table 11-11 Common External Errors
Value Procedure Description
4528 all The client type (HTML or JAVA) is not enabled

on this MVP.
453f all Invalid password for the user account.
4415 msgdir Error reading message or account record.
442c msgdir Internal sanity check failure.
4439 msgdir Error allocating memory.
4611 msgget Unable to locate the specified message in user

account.
4615 msgget Error reading message or account record.
462c msgget The dictated time does not match the message, or
an internal sanity check failure has occurred.
4639 msgget Error allocating memory.
4641 msgget Cannot get fax message because the fax server is
down.
4711 msgdelete Unable to locate the specified message in user

account.
4715 msgdelete Error reading message or account record.
4718 msgdelete Error updating account record.
472c msgdelete The dictated time given does not match the
message.
4734 msgdelete Bad user ID on a multi-user mailbox.
4739 msgdelete Error updating account record.
4741 msgdelete Cannot delete fax message because the fax server
is down.
4815 msgforward Error reading message or account record.
482c msgforward The dictated time given does not match the
message.
4839 msgforward Error allocating memory.
148 REV 1.0 Aug. 4, 1998

Table 11-11 Common External Errors (Continued)
Value Procedure Description
4841 msgforward Cannot forward fax message because the fax

server is down.
4842 msgforward Unable to forward fax message to a FULL

mailbox.
4915 msgdep Error reading message or account record.
4918 msgdep Error updating account record.
4919 msgdep Deposit failed.
4928 msgdep The client type (HTML or JAVA) is not enabled

on this MVP.
492c msgdep The given message type cannot be deposited in

this way.
4933 msgdep COS does not allow fax messages.
4939 msgdep Error allocating memory.
4941 msgdep Unable to deposit fax message because the fax

server is down.
4942 msgdep Unable to deposit message because target

mailbox is full.
4943 msgdep Unable to deposit fax message because the fax

server is at capacity.
4a11 msgmodify Unable to locate specified message in user

account.
4a15 msgmodify Error reading message or account record.
4a19 msgmodify Message modification failed.
4a2c msgmodify The dictated time given does not match the
message.
4a39 msgmodify Error allocating memory.
PN 9110.01068 149
For error types of W, the error codes are as follows:
Table 11-12 Error Codes for "W"
Value Description
0001 Catch all error code for an unspecified error during file
conversions, ether upload or download.
0002 Too much time has elapsed while waiting for a reply from the
MVP.
0003 We were unable to either create a socket to use in

communicating with the MVP or we were unable to connect to
the MVP with the socket.
0004 An error has occurred while creating a cover sheet for this
upload.
0005 Cannot determine the type of file to upload, the msgtype

parameter is not one of TYPE_POSTFIX, TYPE_G3,
TYPE_VOICE, TYPE_ALPHA, TYPE_NUM.
0006 An error has occurred while parsing data from either the MVP
or the mailroom client.
0007 We were unable to spawn a sub process
0008 The ghostscript task encountered an error while processing a

postscript file.
0009 An error occurred while converting portable bitmap (PBM) files

to G3.
000a We were unable to remove the portable bitmap files after they
were converted to G3.
000b A remote copy (RCP) command to or from the fax server has
failed.
000c An error occurred while converting G3 files to BrookTrout info

packet format.
000d We were unable to create the final directory on the fax server for
the BrookTrout file.
000e We were unable to move the converted BrookTrout file to its

final directory.
000f Received an invalid list of recipients to an upload or forward

command.
0010 The service omc_ci is not defined in the /etc/services file on

the WWW Server.
0011 The faxid field returned by the MVP is invalid (less than 6
characters).
0012 During a download, the ipstrip task encountered an error.
150 REV 1.0 Aug. 4, 1998

Table 11-12 Error Codes for "W" (Continued)
Value Description
0013 Unable to remove transient files from the /faxdemo directory

on the fax server.
0014 An error occurred while converting a G3 file to a GIF image.
0015 Unable to remove transient G3 file after converting it to a GIF

image.
0016 Unable to open the GIF image for verification of GIF format or
for transmission to the mailroom client.
0017 We were unable to remove the GIF image after transmission to

the mailroom client.
0018 An error occurred while creating the PostScript file during an

upload.
0019 The psii2fax task encountered an error while converting a

PostScript file to a TIFF image.
001a Unable to determine the number of pages in a PostScript file

during an upload.
001b The page count was determined to be less than 1 or more than
300.
001c The cover sheet name given does not have a .conf file in the
templates directory.
001d Unable to create a sed file. This is used to replace the strings in
the template with the actual strings specified by the user.
001e An invalid number of string parameters has been sent from the
client for the cover sheet.
001f The sed task has failed.
PN 9110.01068 151
SOLARIS 2.6 INSTALL
A.1 Prerequisites
Verify you have the Solaris 2.6 hardware media disk.

Verify your IPs, subnet mask, gateway and node names for the WWW
Server.
A.2 Procedure
1. Power up the WWW Server and press the abort button. After the powerup self
test completes, the WWW Server will display an "ok" prompt.
2. Put the Solaris media disk in the CD-ROM and type:
boot cdrom
3. Answer the following questions when prompted.
What type of terminal are you using?
Select option 3, DEC vt100.

Host Name:
Enter the desired name for the WWW Server.
For example, MVP1WS1
(this stands for MVP #1 WWW Server #1)

Networked:
Enter yes.
IP Address:xxx.xxx.xxx.xxx
Enter the IP assigned for the WWW Server.
PN 9110.01068 153
SOLARIS 2.6 INSTALL
Name Service:
Select other
System part of a Subnet:
Enter yes.
Netmask:
Enter the mask assigned. For example, 255.255.255.0

Time Zone:
Select the appropriate time zone.

Date and Time:
Set the correct time and date.

System Type:
Select standalone
Software:
Accept the default. For example, End user support 230.00 MB

Disks:
Select the default Boot drive.

For example, c0t0d0 (XXXX MB) Boot drive XXXX MB
Preserve Data:
Select overwrite
Auto Layout File System:
Select yes
Select which directories get their own slices:
Select the following:
/ (root)
swap
opt
154 REV 1.0 Aug. 4, 1998

4. Next you need to customize the layout. Reduce the size of the /export/home
directory so that you can increase the size of the /opt directory to 500 MB.
Note If the layout is not customized Orbix will not fit in the /opt directory.
Mount Remote File Systems:
Select no
Reboot:
Select yes. The system will reboot after Solaris is loaded.

Key in the password as Root:
Enter the root password here. By default root (lower case) unless the
customer has requested something different.
Do you wish to use the autopower down feature?
Select no
Do you wish to be asked again about the autopower down
feature?
Select no
5. At this point the Solaris 2.6 load is complete and the system will reboot. After
the reboot is complete, create a user and modify several network related files as
described below.
6. Login as root with a password of root
7. Create a new user:
adduser service
passwd service
8. You will be asked to enter a password for the user service.
Enter personnel
You will be asked to confirm the password.
Enter personnel
9. Set your terminal type and modify Networking files:
TERM vt100;export TERM
cd /etc
vi defaultrouter
10. Enter the IP of the gateway:
vi netmasks
PN 9110.01068 155
SOLARIS 2.6 INSTALL
11. Find the line that contains the Network # and the mask. Change the Network #
so the the first 2 octets equal the gateways #'s and the last 2 octets are 0's.
XXX.XXX.0.0 XXX.XXX.XXX.XXX
network # subnet mask
For example, if your gateway is 192.128.21.1, then your network number

would be 192.128.0.0
vi hostname.le0
This is the nodename of the 1st WWW Server IP.
For example, MVP1WS1.

vi hostname.le1
This is the nodename of the 2nd WWW Server IP.
For example, MVP1WS2.

vi hosts
127.0.0.1 localhost
1st WWW Server IP nodename loghost
2nd WWW Server IP nodename
faxserver IP nodename
MVP IP nodename
12. To remove the cdrom from the drive type:
eject cdrom
13. Reboot the WWW Server. After the boot completes, the WWW Server will be
ready for the Orbix load.
/usr/sbin/shutdown -g0 -i6 -y
156 REV 1.0 Aug. 4, 1998

GLENAYRE INTEGRATED NETWORK

GROUP WEB MIB
For more information concerning MIBs, refer to Requests For Comments (RFCs) documents
on the Internet at http://www.iana.org
See the following documents:
RFC 1212: Concise MIB Definitions (March, 1991)

- Improves on the definition techniques defined in RFC 1155.
RFC 1213: Management Information Base for Network Management of

TCP/IP-based Internets: MIB-II (March, 1991)
- Lists over 100 variables that hold the configuration, status, and
statistical information that are most needed in order to manage a
system that operates in a TCP/IP network.
ING-WEB-MIB DEFINITIONS ::= BEGIN
IMPORTS
enterprises, Counter
FROM RFC1155-SMI
OBJECT-TYPE
FROM RFC-1212
TRAP-TYPE
FROM RFC-1215;
DisplayString ::= OCTET STRING

-- groups in ING-WEB-MIB
motorola OBJECT IDENTIFIER ::= { enterprises 161 }

satcom OBJECT IDENTIFIER ::= { motorola 11 }
iridium OBJECT IDENTIFIER ::= { satcom 1 }
gw OBJECT IDENTIFIER ::= { iridium 2 }
www OBJECT IDENTIFIER ::= { gw 200 }
runStatus OBJECT IDENTIFIER ::= { www 1 }
cmdStats OBJECT IDENTIFIER ::= { runStatus 7 }
cgiStats OBJECT IDENTIFIER ::= { www 2 }
wwwAlarms OBJECT IDENTIFIER ::= { www 3 }
resources OBJECT IDENTIFIER ::= { www 4 }
-- processes OBJECT IDENTIFIER ::= { resources 1 }
-- extensible OBJECT IDENTIFIER ::= { resources 3 }
memory OBJECT IDENTIFIER ::= { resources 4 }
-- lockd OBJECT IDENTIFIER ::= { resources 5 }
disk OBJECT IDENTIFIER ::= { resources 6 }
-- loadaves OBJECT IDENTIFIER ::= { resources 7 }
-- version OBJECT IDENTIFIER ::= { resources 100 }
PN 9110.01068 157
GLENAYRE INTEGRATED NETWORK GROUP WEB MIB
-- These are the returned values of the agent type.

-- returned to: .iso.org.dod.internet.mgmt.mib-2.system.sysObjectID.0
mvpWebAgent OBJECT IDENTIFIER ::= { resources 250 }

hpux9 OBJECT IDENTIFIER ::= { mvpWebAgent 1 }
hpux10 OBJECT IDENTIFIER ::= { mvpWebAgent 6 }
sunos4 OBJECT IDENTIFIER ::= { mvpWebAgent 2 }
solaris OBJECT IDENTIFIER ::= { mvpWebAgent 3 }
osf OBJECT IDENTIFIER ::= { mvpWebAgent 4 }
ultrix OBJECT IDENTIFIER ::= { mvpWebAgent 5 }
netbsd1 OBJECT IDENTIFIER ::= { mvpWebAgent 7 }
freebsd2 OBJECT IDENTIFIER ::= { mvpWebAgent 8 }
irix OBJECT IDENTIFIER ::= { mvpWebAgent 9 }
unknown OBJECT IDENTIFIER ::= { mvpWebAgent 255 }
-- the runStatus group
-- Implementation of the alarms group is mandatory for all

-- systems. If an agent is not configured to have a value
-- for any of these variables, a string of length 0 is
-- returned.
wwwDescr OBJECT-TYPE
SYNTAX DisplayString (SIZE (0..80))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"MVP server description & version number."
::= {runStatus 1}
wwwUpTime OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The time (in hundredths of a second) since the
the MVP server of the system was last
re-initialized."
::= {runStatus 2}
wwwClients OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Number of concurrent clients MVP server is serving."
::={runStatus 3}
wwwClientsPeak OBJECT-TYPE
SYNTAX Gauge
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Number of maxmum concurrent clients MVP server served."
::={runStatus 4}
wwwTraceLevel OBJECT-TYPE
SYNTAX Gauge (3..7)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"MVP server trace level 3 .. 7"
::= {runStatus 5}
wwwRunMode OBJECT-TYPE
SYNTAXDisplayString (SIZE (8..11))
ACCESS read-write
STATUS mandatory
DESCRIPTION
" MVP server run mode which can be production, maintenance"
::= {runStatus 6}
158 REV 1.0 Aug. 4, 1998

-- the cmdStats group
-- Implementation of the resource group is mandatory for all

-- returned.
wwwCommandNumber OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Number of MVP server commands."
::= { cmdStats 1 }
wwwCommandTable OBJECT-TYPE
SYNTAX SEQUENCE OF OmcCommandEntry
ACCESS not-accessible
STATUS mandatory
DESCRIPTION
"A table consisting of all MVP server commands, their names,
access and error counts."
::= {cmdStats 2}
wwwCommandEntry OBJECT-TYPE
SYNTAX OmcCommandEntry
STATUS mandatory
DESCRIPTION
"The command information corresponding to one MVP command"
INDEX{wwwCommandIndex}
::= {wwwCommandTable 1}
OmcCommandEntry ::= SEQUENCE {

wwwCommandIndex INTEGER,
wwwCommandName DisplayString (SIZE (0..25)),
wwwCommandAccess INTEGER,
wwwCommandError INTEGER
}
wwwCommandIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A unique number which identifies a command to the MVP server"
::= {wwwCommandEntry 1}
wwwCommandName OBJECT-TYPE
SYNTAX DisplayString
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A unique name which identifies a command to the MVP server"
wwwCommandAccess OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Number of a given command accepted by MVP server"
PN 9110.01068 159
wwwCommandError OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Number of a given command accepted by MVP server
and resulted in error."
-- the cgiStats group
-- Implementation of the resource group is mandatory for all

-- returned.
cgiStatsNumber OBJECT-TYPE
SYNTAX INTEGER
STATUS mandatory
DESCRIPTION
"Number of cgi stats variables."
::= { cgiStats 1 }
cgiStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF cgiStatsEntry
STATUS mandatory
DESCRIPTION
"A table consisting of all cgi stats variables, their names,
values."
::= {cgiStats 2}
cgiStatsEntry OBJECT-TYPE
SYNTAX CgiStatsEntry
STATUS mandatory
DESCRIPTION
"The information corresponding to each cgi stats variable."
INDEX{cgiStatsIndex}
::= {cgiStatsTable 1}
CgiStatsEntry ::= SEQUENCE {

cgiStatsIndex INTEGER,
cgiStatsName DisplayString (SIZE (0..32)),
cgiStatsValue INTEGER
}
cgiStatsIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A unique number which identifies a cgi stats variable."
::= {cgiStatsEntry 1}
cgiStatsName OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A unique name which identifies a cgi stats variable."
cgiStatsValue OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Value of a cgi stats variable."
160 REV 1.0 Aug. 4, 1998

-- the alarms group
-- Implementation of the alarms group is mandatory for all

-- returned.
-- the Alarm table
-- The Alarm table contains information on the MVPs

-- alarms, including current machine status as seen by the MVP.
-- It is through the status that a manager can clear or
-- inhibit MVP alarms.
wwwSendActiveAlarms OBJECT-TYPE
SYNTAX INTEGER (0..1)
ACCESS read-write
STATUS mandatory
DESCRIPTION
"A Value of 1 results in the WWW re-sending alarm
traps for all Active Alarms whose severity is any
value other than 5 (Cleared) or 6 (Informational types).
When the WWW is finished sending these traps it will
reset this value to 0"
::= { wwwAlarms 1 }
wwwAlarmNumber OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"WWW alarm table size (number of entries)."
::= {wwwAlarms 2}
wwwAlarmTable OBJECT-TYPE
SYNTAX SEQUENCE OF WwwAlarmEntry
STATUS mandatory
DESCRIPTION
"A Table consisting of all WWW alarmIds, their
definitions and current status"
::= {wwwAlarms 3}
wwwAlarmEntry OBJECT-TYPE
SYNTAX WwwAlarmEntry
STATUS mandatory
DESCRIPTION
"The alarm information corresponding to one WWW alarmId"
INDEX {wAlarmId}
::= {wwwAlarmTable 1}
WwwAlarmEntry ::= SEQUENCE {

wAlarmId INTEGER,
wAlarmActId INTEGER,
wAlarmStatus INTEGER,
wAlarmSeverity INTEGER,
wAlarmCat INTEGER,
wAlarmSubCat INTEGER,
wAlarmDescription DisplayString (SIZE (0..255)),
wAlarmText DisplayString (SIZE (0..255)),
wAlarmCfgStatus INTEGER,
wAlarmIndex DisplayString (SIZE (0..255)),
wAlarmTime DisplayString (SIZE (0..255)),
wAlarmRunStatus INTEGER
}
PN 9110.01068 161
wAlarmId OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A unique number which identifies which point in the
software at which this alarm trap was generated.
All numbers which are the same will have been generated
at the same point in the software and will designate
the same error condition although the object of
that error condition may vary. While the error
condition is the same the parameters of this
condition may not be, for example a write error
condition to drive 1 will have the same alarmId
as a write error to drive 2."
::= { wwwAlarmEntry 1 }
wAlarmActId OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The activationID serves to associate alarmIds.
For example a threshold high alarm may have a alarmId
of 100. The same condition may have a threshold normal
event with an alarmId of 101. Since the threshold
normal event is intended to clear the threshold high
event both events will be associated by having the
same activationID. The activationID ties these
two events together. The alarmSeverity associated
with the most recent event overrides any alarmSeverity
previously reported with this activationID."
wAlarmStatus OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"The current status of the alarmId. This will be
used within the WWW to determine if a given alarm has
been set for the wwwSendActiveAlarms command. If
this value is 1 then the alarm is still active and
should be resent provided its wAlarmSeverity value
does not equal 6"
wAlarmSeverity OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"
warning (4)
minor (3)
major (2)
critical (1)
cleared (5)
informational (6)
Alarms of level 6 will always have an activationId
of 0, and hence do not need to be cleared nor resent
for the wwwSendActiveAlarms command."
162 REV 1.0 Aug. 4, 1998

wAlarmCat OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"An indication of the category of the wAlarmId
type defined as
MVP Server (1)
CGI (2)
HTTP Server (3)
SNMP Agent (4)
Memory (5)
Disk Space (6)
File System (7)
External Interfaces (8)
Cache Server (9)"
wAlarmSubCat OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"An indication of the type of enterpriseSpecific trap
generated for this alarm
Security Violation(1)
PM Threshold Trap(2)
Fault Management Alarm Trap(3)
Status Change Event Trap(4)
Configuration Change Event Trap(5)
Resync Start Trap(6)
Resync Complete Trap(7)"
wAlarmDescription OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A generic description of the alarm type (generic
for wAlarmId)"
wAlarmText OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The exact alarm message, complete with parameters,
as it appears in the WWW history file."
wAlarmCfgStatus OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"
Enabled(0)
Disabled(1)
Initializing(2)
"
PN 9110.01068 163
wAlarmIndex OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
" This field is reserved, an string constant=n/a."
wAlarmTime OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The time of the alarm expressed as YYYYMMDDHHMMSS"
wAlarmRunStatus OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"
Not Ready(0)
In Service(1)
Out of Service(2)
"
processes OBJECT-TYPE
SYNTAX Processes
STATUS mandatory
DESCRIPTION
"A set of information on running programs/daemons."
INDEX { processIndex }
::= { resources 1 }
Processes ::= SEQUENCE {

processIndex INTEGER,
processNames DisplayString,
processMin INTEGER,
processMax INTEGER,
processCount INTEGER,
processErrorFlag INTEGER,
processErrMessage DisplayString,
processErrFix INTEGER
}
processIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Reference Index for each observed process."
::= { processes 1 }
processNames OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The table of process names were Counting."
::= { processes 2 }
164 REV 1.0 Aug. 4, 1998

processMin OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The minimum number of processes that should be
running. An error flag is generated if the number of
running processes is < the minimum."
::= { processes 3 }
processMax OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The maximum number of processes that should be
running. An error flag is generated if the number of
running processes is > the maximum."
::= { processes 4 }
processCount OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of current processes running with the name
in question."
::= { processes 5 }
processErrorFlag OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A Error flag to indicate trouble with a process. It
goes to 1 if there is an error, 0 if no error."
::= { processes 100 }
processErrMessage OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"An error message describing the problem (if one exists)."
processErrFix OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Setting this to one will try to fix the problem if possible."
memTotalSwap OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total Swap Size."
::= { memory 1 }
memAvailSwap OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Available Swap Space."
::= { memory 2 }
PN 9110.01068 165
memTotalReal OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total Real/Physical Memory Size."
::= { memory 3 }
memAvailReal OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Available Real/Physical Memory Space."
::= { memory 4 }
Disk ::= SEQUENCE {

diskIndex INTEGER,
diskPath DisplayString,
diskDevice DisplayString,
diskMinimum INTEGER,
diskTotal INTEGER,
diskAvail INTEGER,
diskUsed INTEGER,
diskPercent INTEGER,
diskErrorFlag INTEGER,
diskErrorMsg DisplayString
}
diskIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Reference number for the Disk Mib."
::= { disk 1 }
diskPath OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Path where disk is mounted."
::= { disk 2 }
diskDevice OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Device path"
::= { disk 3 }
diskMinimum OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Minimum space required for the disk."
::= { disk 4 }
diskTotal OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Total Disk Size (kbytes)"
::= { disk 5 }
166 REV 1.0 Aug. 4, 1998

diskAvail OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Available disk Space"
::= { disk 6 }
diskUsed OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Used Space on Disk"
::= { disk 7 }
diskPercent OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Percentage of space used on disk"
::= { disk 8 }
diskErrorFlag OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Error flag signaling disk is over minimum required space"
::= { disk 100 }
diskErrorMsg OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A text description of what caused the error flag to be set."
::= { disk 101 }
loadaves OBJECT-TYPE
SYNTAX Loadaves
STATUS mandatory
DESCRIPTION
"Load average information."
INDEX { loadaveIndex }
::= { resources 7 }
Loadaves ::= SEQUENCE {

loadaveIndex INTEGER,
loadaveNames DisplayString,
loadaveLoad DisplayString,
loadaveConfig DisplayString,
loadaveErrorFlag INTEGER,
loadaveErrMessage DisplayString
loadaveIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Reference Index for each observed loadave."
::= { loadaves 1 }
loadaveNames OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The list of loadave names were Counting."
::= { loadaves 2 }
PN 9110.01068 167
loadaveLoad OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The 1,5 and 10 minute load averages."
::= { loadaves 3 }
loadaveConfig OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The watch point for loadaverages to signal an error."
::= { loadaves 4 }
loadaveErrorFlag OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A Error flag to indicate trouble with a loadave. It
::= { loadaves 100 }
loadaveErrMessage OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
::= { loadaves 101 }
version OBJECT-TYPE
SYNTAX Version
STATUS mandatory
DESCRIPTION
"ece-snmpd version info."
INDEX { versionIndex }
::= { resources 100 }
Version ::= SEQUENCE {

versionIndex INTEGER,
versionTag DisplayString,
versionDate DisplayString,
versionCDate DisplayString,
versionIdent DisplayString,
versionClearCache INTEGER,
versionUpdateConfig INTEGER
}
versionIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Index to mib (always 1)"
::= { version 1 }
versionTag OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"CVS tag keyword"
::= { version 2 }
168 REV 1.0 Aug. 4, 1998

versionDate OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Date string from RCS keyword"
::= { version 3 }
versionCDate OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Date string from ctime() "
::= { version 4 }
versionIdent OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Id string from RCS keyword"
::= { version 5 }
versionClearCache OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Set to 1 to clear the exec cache, if enabled"
::= { version 10 }
versionUpdateConfig OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Set to 1 to read-read the config file(s)."
::= { version 11 }
versionRestartAgent OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"Set to 1 to restart the agent."
::= { version 12 }
snmperrs OBJECT-TYPE
SYNTAX Snmperrs
STATUS mandatory
DESCRIPTION
"A place for the agent to report problems."
INDEX { snmperrIndex }
::= { resources 101 }
Snmperrs ::= SEQUENCE {

snmperrIndex INTEGER,
snmperrNames DisplayString,
snmperrErrorFlag INTEGER,
snmperrErrMessage DisplayString
}
snmperrIndex OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Reference Index for each observed snmperr."
::= { snmperrs 1 }
PN 9110.01068 169
snmperrNames OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
"snmp"
::= { snmperrs 2 }
snmperrErrorFlag OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
DESCRIPTION
"A Error flag to indicate trouble with the agent. It
::= { snmperrs 100 }
snmperrErrMessage OBJECT-TYPE
ACCESS read-only
STATUS mandatory
DESCRIPTION
::= { snmperrs 101 }
-- Trap Definitions
wwwSecurityEvent TRAP-TYPE
ENTERPRISE www
VARIABLES {
wAlarmId,
wAlarmActId,
wAlarmCat,
wAlarmSeverity,
wAlarmIndex,
wAlarmTime,
wAlarmDescription,
wAlarmText
}
DESCRIPTION
"This trap indicates that a security violation has been
detected by the WWW. The value of wAlarmSeverity will
always be set to 6, (informational) and the value of
wAlarmAct ID will always be 0"
::= 1
wwwPMThreshEvent TRAP-TYPE
ENTERPRISE www
VARIABLES {
wAlarmId,
wAlarmActId,
wAlarmCat,
wAlarmSeverity,
wAlarmIndex,
wAlarmTime,
wAlarmDescription,
wAlarmText
}
DESCRIPTION
"This trap indicates that the WWW has transitioned through
a resource threshold, which potentially could result in a
degredation of service or the loss of data."
::= 2
wwwFaultEvent TRAP-TYPE
ENTERPRISE www
VARIABLES {
wAlarmId,
wAlarmActId,
wAlarmCat,
wAlarmSeverity,
wAlarmIndex,
170 REV 1.0 Aug. 4, 1998

wAlarmTime,
wAlarmDescription,
wAlarmText
}
DESCRIPTION
"This trap indicates that the WWW has encountered a fault in
either hardware or software operation. The category field
should be examined for the subsystem affected. "
::= 3
wwwStatusChangeEvent TRAP-TYPE
ENTERPRISE www
VARIABLES {
wAlarmId,
wAlarmActId,
wAlarmCat,
wAlarmSeverity,
wAlarmIndex,
wAlarmTime,
wAlarmDescription,
wAlarmText,
wAlarmRunStatus
}
DESCRIPTION
"This trap indicates a change in the operational state of the
WWW. The value of wAlarmSeverity will always be set to 6,
(informational) and the value of wAlarmAct ID will
always be 0"
::= 4
wwwConfigChangeEvent TRAP-TYPE
ENTERPRISE www
VARIABLES {
wAlarmId,
wAlarmActId,
wAlarmCat,
wAlarmSeverity,
wAlarmIndex,
wAlarmTime,
wAlarmDescription,
wAlarmText,
wAlarmCfgStatus
}
DESCRIPTION
"This trap indicates that the WWW has had its configuration
changed or reloaded. The value of wAlarmSeverity will
always be set to 6, (informational) and the value of
wAlarmAct ID will always be 0"
::= 5
wwwResyncStartEvent TRAP-TYPE
ENTERPRISE www
VARIABLES {
wAlarmTime,
wAlarmDescription,
wAlarmText
}
DESCRIPTION
"This trap indicates that a WWW has begun resending outstanding
trap alarms. The value of ventEntSeverity will always be set
to 6, (informational) and the value of wAlarmActId
will always be 0"
::= 6
PN 9110.01068 171
wwwResyncCompleteEvent TRAP-TYPE
ENTERPRISE www
VARIABLES {
wAlarmId,
wAlarmActId,
wAlarmCat,
wAlarmSeverity,
wAlarmIndex,
wAlarmTime,
wAlarmDescription,
wAlarmText
}
DESCRIPTION
"This trap indicates that a WWW has finished resending outstanding
trap alarms. The value of wAlarmSeverity will always be set
to 6, (informational) and the value of wAlarmActId
will always be 0"
::= 7
END
172 REV 1.0 Aug. 4, 1998

JAVA CUSTOMIZATION
Customizing the Java Client consists of changing properties files or images.
These changes are typically made on a per Glenayre customer basis, not on a per
subscriber basis.
C.1 Properties Files
Properties files exist in order to customize information in the Java client,

particularly text. Property entries in a properties file are of the form
property=value. At present, the only properties file is
Messages.properties.
C.1.1 Messages.properties
This file resides at the application base directory. It consists of two text
properties for the Logon screen:
Logon.windowTitle -- Property sets the text for the title bar of the Logon
window.
Logon.largeCenteredText -- Property sets the large centered text of
the Logon window.
C.2 Images
The supported image format is GIF. Default images reside in the images
directory under the application base directory. Custom images reside in the
custom directory under the images directory. All images that are part of the
Java client reside in these directories.
PN 9110.01068 173
JAVA CUSTOMIZATION
C.2.1 Image Determination

During execution, the Java client first checks the custom directory for any
particular image. If the image cannot be located in the custom directory, the
Java client searches for the image in the images directory.
C.2.1.1 Required Images
All required images have an entry in the images directory. Most application
images are required images. Placing an alternative image of the same name in
the custom directory customizes that image.
C.2.1.2 Optional Images
Certain images are not supplied in the images directory although these optional
images are search for by image determination. If they are present at all, these
optional images reside only in the custom directory. Currently, the optional
images in the Java client are all part of Logon and are the following:
leftBottomLogon.gif, middleLogon.gif, and
rightBottomLogon.gif.
174 REV 1.0 Aug. 4, 1998

ACRONYMS AND ABBREVIATONS

Table D-1 Acronyms and abbreviations
Term Definition
ASCII American Standard Code for Information Interchange
CGI Common Gateway Interface
CIP Computer Interface Protocol
DMS Direct Messaging Service
DNS Domain Name Services
DTMF Dual Tone Multi Frequency
ECC Enhanced Call Completion
G3 Group 3 Fax
GBS Gateway Business System
GE Geo-political Entity
GIF Graphics Interchange Format version 87a CompuServe

Incorporated
GSM Global System for Mobile Communication
HLR Home Location Register
HTML HyperText Markup Language
HTTP Hyper Text Transfer Protocol
ISDN Integrated Services Digital Network
ISU IRIDIUM Subscriber Unit
ISUP ISDN User Part
ITU International Telecommunication Union
JRE Java Runtime Environment
LAC Location Area Code
PN 9110.01068 175
ACRONYMS AND ABBREVIATONS
LAI Location Area Identity
LAN Local Area Network
LDA Logical Delivery Area
LDI Local Digital Interface
MAP Mobile Application Part
MDA Message Delivery Area
MIB Management Information Base
MIME Multipurpose Internet Multimedia Extensions (MIME) is

the specification commonly used for Internet mail. It is
defined in RFC 1521.
MRJ Macintosh OS Runtime for Java (MRJ) is a software

package that includes Apples implementation of the Java
Virtual Machine (VM) and related libraries. It is based on
software created by the JavaSoft business unit of Sun
Microsystems, Inc. and implements a specific version of
Suns Java specification.
MS Mobile Station
MSC Mobile Switching Center
MSCid MSC identity
MSISDN Mobile Subscriber Integrated Service Digital Network
MTC Message Termination Controller
MTD Message Termination Device
MTLI Messaging/Telephony Location Interworking
MVP Modular Voice Processor
PPP Point-to-Point Protocol
PSTN Public Switched Telephone Network
RCP Remote Copy Program
RSH Remote Shell Program
SMDR Simple Message Detail Record (Synonymous with CDR)
SMS Short Message Service
SNMP Simple Network Management Protocol
SNTP Simple Network Time Protocol
SS7 Signaling System number 7
SSS Switching subsystem
TAP Telocator Alphanumeric Input Protocol
176 REV 1.0 Aug. 4, 1998

TNPP Telocator Network Paging Protocol
TCP/IP Transmission Control Protocol / Internet Protocol
UDP User Datagram Protocol
URL The Uniform Resource Locator (URL) is the common

format of address objects on the World Wide Web. It is
described in RFC 1630.
WWW World Wide Web
PN 9110.01068 177
INDEX
A Forward 94
Account validation 93 Forward Message 11
Address Pool 51
Alarm Table Index 102 G
Alarm Table MIB 107 Generic Traps 131
Alarm Table Shared Memory 101 get 86
Alarm Table Utility 106 Guest Features 11
ASTATUS 146
At Group 117 H
Authentication Trap 131 Hardware platform 7
HTML Client 61
C HTML Interface 6
cgiStats 100 HTTP configuration 27
CIP Input Parameters 143
CIP Output Parameters 143 I
Client 92 ICMP Group 122
Client Directory Structure 81 ifconfig 55
Cold Start Trap 131 Incoming and Outgoing UDP Traffic 126
Command Table 101 Incoming ICMP Messages 122
Common External Errors 148 Incoming SNMP Traffic Counts 126
Config Subdirectory Files 90 input filter 50
Config.ser 80 Inside Addresses 42
Current UDP Listeners 126 install
firewall 42
D HTML client 62
debug 55 Java client 71
Default Alarms 104 remote client server 30
delete request 94 web server 16
Directory Structure 81 Interfaces Group 115
Disk MIB 112 IP Address Table 118
DMS 95 IP Address Translation 120
download process 95 IP Configuration Parameters 118
IP Group 118
E IP Routing Discards 120
error codes 147 IP Routing Table 119
Error Codes for "W" 150 IP Statistics 120
External Errors 148
J
F Java Client 69
Failure Opcodes 147 Java client processes 69
FAX Server and CGI 92 JavaScript 63
fax server description 8
Firewall 8, 41 L
Folders.ser 80 listmvp 86
PN 9110.01068 179
Loadaves MIB 113 RFC 157

log files 136 runStatus 100
Logger.ser 80
S
M Segment Counts 125
MailRoom HTML processes 62 Server IP Address 79
Maintenance Mode 89 SERVICES 145
Mark as Not Retrieved 84 set 86
Memory MIB 112 show command 57
Memory Tree 84 SMSGTYPE 144
Message Deletion / Undelete 11 SNMP 97
message retrieval 10 SNMP Agent 108
MHANDLING 145 SNMP Alarm Server 91
MIB 111 SNMP Group 126
MIB Definitions 157 SNMP Traffic Counts 126
MIB-II Group 115 Snmpalarmd 109
Microsoft Internet Explorer 63 Socket Timeout 79
Minimum Requirements 74 Solaris 153
Modem Bank 47 Statistic Variables 98
modem ports 53 System Group 115
modify command 95
MSGSTATUS 144 T
MSIE 63 T1 Interface Cable Pinouts 48
MVP Interface 6 TCP Configuration 124
MVP Server 34, 92 TCP Connection Statistics 124
MVP server process 85 TCP Connection Table 125
MVP Server shared memory 100 TCP Group 124
MVP Web Server Components 7 Trace Log 88
MVP Web Server Interfaces 6 traceroute 56
MvpSrv 138 traps 128
MWISTAT 146 Trnkdiag 58
N U
Netscape Navigator 63 UDP Group 126
NETServer configuration 50 UDP Listeners 126
No Response 84 UDP Traffic 126
uninstall 39
O update request 94
omcsrv.log 89 upload command 95
Orbix 17 Upload FAX 96
Outgoing ICMP Messages 123 User Account 52
Users.ser 80
P usrprofile 137
Password validation 93
ping 56, 138 V
PIX 45 Version MIB 114
Port Address 79 Version.ser 80
Processes MIB 111
Profile.ser 80 W
PSTN access 9 Warm Start Trap 131
ptrace 56 WEB MIB 157
wwwConfigChangeEvent 130
R wwwFaultEvent 129
Resource Group 111 wwwPMThreshEvent 128
PN 9110.01068 180
wwwResyncCompleteEvent 131
wwwResyncStartEvent 130
wwwSecurityEvent 128
wwwStatusChangeEvent 129
PN 9110.01068 181
Quality Statement
Our priority is our customer. We are committed

to listen to our customer, understand our
customer's needs and to respond with the highest
quality products, services and support. We
believe this commitment is not only the
responsibility of management, but it is our
individual responsibility as employees.

World Wide Web Server-Glenayre

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

World Wide Web Server-Glenayre

Загружено:

Авторское право:

Доступные форматы

Copyrights

1998 Glenayre Electronics, Inc.

Glenayre is a registered trademark of Glenayre Electronics, Inc.

This document is written and published by Glenayre Atlantas Technical

Glenayre Electronics, Inc. assumes no responsibility for errors in this document,

Address all comments and requests regarding this document to:

Tel: (770) 283-1000

DOCUMENT CHANGE RECORD

Revision Release Date Page Number Changes

1.0 Aug. 4, 1998 Original

Documentation Change Request Form

Use a copy of this form to report documentation errors and/or suggested

Description of error or suggested improvement:

Recommended Priority: _______

Change requested by:

Send completed form to:

Glenayre Electronics, Inc.

iv REV 1.0 Aug. 4, 1998

2. WWW SERVER SYSTEM .................................................................................................................. 5

3. WWW SERVER INSTALLATION.....................................................................................................13

4. FIREWALL INSTALLATION ............................................................................................................41

6. HTML CLIENT ..................................................................................................................................61

7. JAVA CLIENT ..................................................................................................................................69

vi REV 1.0 Aug. 4, 1998

7.2.4 Mac OS Installation .......................................................................................................76

8. MVP SERVER PROCESS................................................................................................................85

9.2.8.1 Uploading a DMS Message.............................................................................95

10. SNMP AGENT ..................................................................................................................................97

11. TROUBLESHOOTING THE WWW SERVER ................................................................................133

viii REV 1.0 Aug. 4, 1998

Appendix A SOLARIS 2.6 INSTALL ..............................................................................................153

Appendix B GLENAYRE INTEGRATED NETWORK GROUP WEB MIB .....................................157

Appendix C JAVA CUSTOMIZATION ............................................................................................173

Appendix D ACRONYMS AND ABBREVIATONS .........................................................................175

Table 10-26 TCP Connection Statistics .................................................................................................124

xiv REV 1.0 Aug. 4, 1998

Additional manuals in the X.6 product reference set include:

1.1.1 Intended Audience

or for individuals such as:

1.1.2 How to Use this Manual

This manual uses a few simplified terms.

2 REV 1.0 Aug. 4, 1998

1.2 Getting Technical Assistance

To contact Glenayre Electronics Technical Support, call or write:

Glenayre Electronics, Inc.

WWW SERVER SYSTEM

2.1 General Description

2.1.1 WWW Server Interfaces

Figure 2-1 WWW Server System Diagram

6 REV 1.0 Aug. 4, 1998

2.2 System Components

2.2.1 WWW Server

Hardware platform requirement

Vendor: Themis Computer

Description: Phoenix Simplex Server USP-1/XXX-200-A-GA

The WWW Server itself is composed of the following components:

Table 2-1 WWW Server Components

1 Solstlce: On-Line DiskSuit pre-installed.

1 Sbus SCSI/10 Base T Boards

2 4 GB SCSI-2 Data Disk.

1 4 GB SCSI-2 System Disk.

1 4 mm DAT Tape Drive.

2.2.3 Modular Voice Processor

Use MVP release X.6.2 or later.