HP30003k Associates LogoHP3000/HP 3000 FAQ

Last Updated: Thursday, February 01, 2007 02:38 PM

HP3000 FAQ
MPE/V

HPe3000 FAQ
MPE/XL

HP 3000 FAQ
MPE/iX


How to Connect the HP3000 to the Internet

4.4.2. How to connect

JK

If you have (a) existing Internet connectivity to a Unix/HP-UX/similar system, it is relatively trivial. If not, see related questions. If yes, you want MPE/iX 4.0 or higher, and enable DNS by setting up the proper entries in NET.SYS (RESLVCNF.NET, HOSTS.NET, etc) and enable Ethernet framing and ARP protocols in NMMGR. That's it. Experience and user feedback indicates you are best to "ignore" Probe names for this purpose and stick with ARPA domain names for Internet use.

Point your RESLVCNF nameserver entry to an existing DNS-capable node, and configure a "default neighbor gateway" in NMMGR to the IP address of your router.

This can be done in MPE/V and pre-4.0 MPE/iX but requires manual maintenance of your NSDIR file - these systems do not have DNS resolver clients so you must manually enter every system you wish to connect to.

If you have DTC Manager, the same holds true; use probe names for the DTC-to-host connections, use ARPA names otherwise. (See Telnet FAQ).


4.4.2.1. Configuring a "default gateway in NMMGR"

In NMMGR, select open config, then NS, then unguided config, then go to netxport, then go to NI, select your LAN interface from the list and hit ENTER, select GO TO Internet, select your router (if already there - if not, make up a name for it and hit Add); on the next screen you provide the IP address of the router, and under "IP Network Address" select "@" - IP MAsk (blank), Hops (any number). Hit SAVE DATA, home cursor and type "utility" and hit enter, then select "validate" then "validate netxport". You'll need to either stop/restart the network, or enter

:netcontrol update=internet;net=lan1
                                ^^^^use whatever your LAN interface is called to get the changes to take affect. 

 


Back to FAQ Index Back to 3k Home Page
 
HP3000-L FAQ Collection (c) 3k Associates, Inc. 1996-2006