HPlogo Configuring and Managing MPE/iX Internet Services > Chapter 9 HP WebWise MPE/iX Secure Web Server

Preparing HP e3000 for Network Access

MPE documents

Complete PDF
Table of Contents
Glossary
Index

E0802 Edition 6 ♥
E0701 Edition 5
E0400 Edition 4

Before an HP e3000 can act as a web server, it must be available for network access via TCP/IP.

  • Configure TCP/IP on the system.

  • Have a domain name associated with the system's IP address.

Apache communicates on the network using the HTTP Hypertext Transfer Protocol, which in turn, uses TCP/IP. NS Transport (the TCP/IP transport subsystem) is configured on the HP e3000 using NMMGR. In NMMGR, configure the system's IP address and subnet mask in screen NEXTPORT.NI.NIname.PROTOCOL.IP. TCP should be configured with the recommended values shown in Table 9-1., using the NMMGR screen NEXTPORT.GPROT.TCP. Information on TCP/IP parameters is available in the NS 3000/iX NMMGR Screens Reference Manual from http://docs.hp.com/mpeix/all/index.html.

Table 9-1 Recommended TCP/IP Values

TCP/IP Parameters

 Value
Maximum number of connections 20,000
Retransmission Interval Lower Band 1 second
Maximum time to wait for remote response 120 seconds
Initial Retransmission Interval 2 seconds
Maximum Retransmission Interval 2 seconds
Connection Assurance Interval 120 seconds
Maximum Connection Assurance Retransmissions 2

After completing the system's TCP/IP configuration, run:NETCONTROL START from the CI command line and verify that it ran successfully. Also verify that the system can respond over the network by running ping either from an HP e3000 or another system. 

  :run ping.net.sys;info="15.99.200.390"

  64 byte(s) from $0F0DC0CF : icmp seq = 11, time = 2 ms
  64 byte(s) from $0F0DC0CF : icmp seq = 12, time = 3 ms
  64 byte(s) from $0F0DC0CF : icmp seq = 13, time = 2 ms
  < CONTROL-y >



  c:\ping yourserver.com
  Pinging yourserver.com [15.99.200.390] with 32 bytes of data
  Reply from 15.99.200.390: bytes=32 time<10ms TTL=199
  Reply from 15.99.200.390: bytes=32 time<10ms TTL=199
  Reply from 15.99.200.390: bytes=32 time<10ms TTL=199
You will also want a domain name. This is a unique identifier such as "yourserver.abc.com" which is used (instead of the IP address) to direct requests from a browser to a web server. Request a domain name from the administrator of the Domain Name Server (DNS) on your network.

Configure the web server with one or more Domain Name Servers (DNS). These DNS servers will resolve the system's name into its IP address. To configure, edit RESLVCNF.NET.SYS or edit /etc/resolv.conf (which links to RESLVCNF.NET.SYS).

  • Add one or more nameserver lines. Each line should contain the IP address of a valid DNS.

  • Add one domain line that contains the DNS domain name for the domain to which your web server belongs. This domain name should not include the web server's hostname (:NMMGR node name).

  • The DNS server listed on each nameserver line must contain both a valid "A" record and "PTR" record. The content of these records must agree with the actual hostname of the web server and the actual domain name in RESLVCNF.NET.SYS.

For example, if the fully qualified domain name if the web server is yourserver.abe.com: 

  shell/ix> uname -n
  YOURSERVER
  
  shell/ix > cat /etc/resolv.conf
  #domain <domain>
  #nameserver <primary server's IP address>
  #nameserver <secondary server's IP address>
  #
  #
  doamin abc.com
  nameserver 25.33.100.134
  nameserver 25.33.125.172



Major Components

Configuring the Software