« WRQ's Reflection goes deeper into coffers | Main | Beefy servers link VMware and MPE futures »

September 16, 2014

Advice on uptime, net gateways and sockets

Is there a way to use the 3000's networking to check how long your system has been up?

James Hofmeister replies:

If you have SNMP running, a query to check system uptime is:

: snmpget ector.atl.hp.com public system.sysUpTime.0
Name: system.sysUpTime.0
Timeticks: (418638300) 48 days, 10:53:03

I get no awards for 48 days uptime, but I use my machines to duplicate, beta test and verify repair of customer network problems.

Is there a way to scan all the ports on my HP 3000 Series 996: How many are being used, and how many are available?

Mark Bixby replies:

SOCKINFO.NET.SYS can tell you which programs have opened which sockets.

NETTOOL.NET.SYS STATUS,TCPSTAT and STATUS,UDPSTAT can also give you useful information about sockets, particularly STATUS,TCPSTAT and CONNTABLE.

Or you can run an external tool and do a port scan against your 3000.  This is not recommended during production hours, since such port cans can sometimes confuse network applications.

When I try to configure a  on our MPE/iX 7.5 system, I get the following error when I try to validate my new NMMGR gateway configuration.

Searching for subsystem validation routine VALIDATENETXPOR
---> VALIDATION OF NETXPORT SUBSYSTEM STARTED  <---
*** VALIDATE ERROR --> PATHNAME : NETXPORT.NI.LAN1.INTERNET
CONFIGURED GATEWAYS (1) MUST BE <= IPU MAX GATES (0). (VALERR 32)
---> VALIDATION OF NETXPORT SUBSYSTEM FINISHED <---

There are no other gateways configured so the CONFIGURED GATEWAYS (1) value look okay to me — so how can I increase the IPU MAX GATES value?

James Hofmeister replies:

In MPE/iX 5.5 and 6.0 (unpatched) the limit was 14 gateways. This was increased to 255 gateways with patches, and was included in base 6.5 and 7.x.

The fact that validate says “IPU MAX GATES (0)” would indicate to me that you have corruption of your configuration file in “at least” the field that holds this value.

I would suggest that you want to first keep a copy of this config file, then purge NMCONFIG.PUB.SYS and then rebuild your configuration with guided config.

Note:  You could do a copy subtree of the NETXPORT.PROT.IPU field from NMAUX1.PUB.SYS to NMCONFIG.PUB.SYS to update this field — but at this point I would expect problems in this config file with more than just this one field.

06:27 PM in Hidden Value | Permalink

Bookmark and Share

Use our search engine to find 20 years
of HP 3000 news and articles

Comments

Comments

The comments to this entry are closed.