- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: tcpip stack failure of config utility
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2012 02:15 AM
тАО03-14-2012 02:15 AM
when i run the the tcpip$config utility and select the core environment/interfaces I get this......
HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu
Hostname Details: Configured=eddy, Active=eddy
Configuration options:
%DCL-W-IVCHAR, invalid numeric value - check for invalid digits
\%X|\
and the utility bombs out
i am also seeing these DHCP erros on startup of stack.........
$ @sys$startup:tcpip$startup
%TCPIP-I-INFO, TCP/IP Services startup beginning at 14-MAR-2012 09:06:37.79
%TCPIP-I-NORMAL, timezone information verified
There are one or more processes which did not
terminate when TCP/IP Services was last shutdown.
WARNING - The TCPIP$INET_STARTUP procedure will
now start the TCP/IP Kernel. Subsequent I/O
operations on the following Internet devices,
which are currently assigned and active in your
system, may fail:
BG166:
BG188:
BG216:
BG217:
BG219:
BG220:
BG222:
BG223:
BG224:
You may choose to stop the processes that are
using the above Internet devices. Issue the DCL
command SHOW DEVICE BGn /FULL for each of the
listed devices to identify the processes.
%RUN-S-PROC_ID, identification of created process is 0000045C
%TCPIP-I-SETLOCAL, setting domain and/or local host
%TCPIP-I-STARTCOMM, starting communication
%TCPIP-I-SETPROTP, setting protocol parameters
%TCPIP-I-DEFINTE, defining interfaces
%TCPIP-I-DHCPC_STRD_CLNT, DHCP client started with PID 0000045E
EDDY$DKA2:[SYS0.SYSCOMMON.][SYSEXE]TCPIP$DHCP_CLIENT_CONF.EXE;1: internal error
in DHCP agent
%TCPIP-E-DHCPC_SYSERR, unexpected system error
%TCPIP-E-DHCPCONFERR, DHCP client failed to configure interface IE1
-TCPIP-E-DHCPC_SYSERR, unexpected system error
EDDY$DKA2:[SYS0.SYSCOMMON.][SYSEXE]TCPIP$DHCP_CLIENT_CONF.EXE;1: internal error
in DHCP agent
%TCPIP-E-DHCPC_SYSERR, unexpected system error
%TCPIP-E-DHCPCONFERR, DHCP client failed to configure interface IE2
-TCPIP-E-DHCPC_SYSERR, unexpected system error
EDDY$DKA2:[SYS0.SYSCOMMON.][SYSEXE]TCPIP$DHCP_CLIENT_CONF.EXE;1: internal error
in DHCP agent
%TCPIP-E-DHCPC_SYSERR, unexpected system error
%TCPIP-E-DHCPCONFERR, DHCP client failed to configure interface IE3
-TCPIP-E-DHCPC_SYSERR, unexpected system error
%TCPIP-I-DHCPINTER, interface IE0 configured by DHCP client
-TCPIP-I-INTERIGNORED, interface configuration information ignored
%TCPIP-I-STARTNAME, starting name service
%TCPIP-S-STARTDONE, TCP/IP Kernel startup completed
%TCPIP-I-PROXYLOADED, loaded 1 NFS proxy records
%TCPIP-I-LOADSERV, loading TCPIP server proxy information
%TCPIP-I-SERVLOADED, auxiliary server loaded with 0 proxy records
-TCPIP-I-SERVSKIP, skipped 0 communication proxy records
-TCPIP-I-SERVTOTAL, total of 1 proxy records read
%TCPIP-S-STARTDONE, TCPIP$PROXY startup completed
%TCPIP-S-STARTDONE, TCPIP$PORTMAPPER startup completed
%TCPIP-S-STARTDONE, TCPIP$FTP startup completed
%TCPIP-S-STARTDONE, TCPIP$FTP_CLIENT startup completed
%TCPIP-S-STARTDONE, TCPIP$INET_DRIVER startup completed
%TCPIP-I-NOMAP, no filesystem mapping information available
%TCPIP-S-STARTDONE, TCPIP$NFS startup completed
%TCPIP-S-STARTDONE, TCPIP$NFS_CLIENT startup completed
%TCPIP-S-STARTDONE, TCPIP$PCNFS startup completed
%RUN-S-PROC_ID, identification of created process is 00000468
%TCPIP-S-STARTDONE, TCPIP$PWIP_DRIVER startup completed
%TCPIP-S-STARTDONE, TCPIP$REXEC startup completed
%TCPIP-S-STARTDONE, TCPIP$SMTP startup completed
%TCPIP-S-STARTDONE, TCPIP$SNMP startup completed
%TCPIP-S-STARTDONE, TCPIP$SSH startup completed
%TCPIP-S-STARTDONE, TCPIP$SSH_CLIENT startup completed
%TCPIP-S-STARTDONE, TCPIP$TELNET startup completed
%TCPIP-S-STARTDONE, TCPIP$TFTP startup completed
%TCPIP-S-STARTDONE, TCP/IP Services startup completed at 14-MAR-2012 09:08:10.54
I had manually changed some values in the routing table - no looks like this
TCPIP> show route
DYNAMIC
Type Destination Gateway
AN 0.0.0.0 129.94.185.1
AH 10.205.136.18 129.94.185.1
AH 10.208.193.52 129.94.185.1
AH 80.169.174.212 129.94.185.1
AH 124.4.104.54 129.94.185.1
AH 127.0.0.1 127.0.0.1
AH 128.4.104.0 129.94.185.1
AH 128.4.104.58 129.94.185.1
AH 128.4.105.0 129.94.185.1
AH 128.8.14.126 129.94.185.1
AH 128.8.117.52 129.94.185.1
AH 128.8.127.47 129.94.185.1
AH 128.8.130.2 129.94.185.1
AH 128.8.130.207 129.94.185.1
AH 128.8.135.13 129.94.185.1
AH 128.8.145.108 129.94.185.1
AH 128.8.145.252 129.94.185.1
AH 128.8.176.111 129.94.185.1
AN 129.94.185.0/25 129.94.185.40
AH 129.94.185.13 129.94.185.1
AH 129.94.185.40 129.94.185.1
AH 129.94.185.40 129.94.185.40
AH 129.94.185.46 129.94.185.1
TCPIP>
any help would be greatly appreciated -
Solved! Go to Solution.
- Tags:
- TCPIP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2012 02:21 AM
тАО03-14-2012 02:21 AM
Re: tcpip stack failure of config utility
TCPIP> show host
LOCAL database
Host address Host name
129.94.185.45 CHAS
129.94.185.46 DAVE
129.94.185.40 EDDY
127.0.0.1 LOCALHOST, localhost
%TCPIP-W-NORECORD, information not found
-TCPIP-E-BIND_NOSERVERS, default servers are not available
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2012 04:18 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2012 05:33 AM - edited тАО03-14-2012 06:54 AM
тАО03-14-2012 05:33 AM - edited тАО03-14-2012 06:54 AM
Re: tcpip stack failure of config utility
VMS might well allow DHCP to be configured, but that doesn't mean that DHCP is a good idea with a server (VMS or otherwise), or that a DHCP-acquired dynamically-addressed VMS server box works entirely reliably.
Most servers expect static addresses. (It's possible to do dynamic addresses, but that usually also involves Dynamic DNS (DDNS) or analgous. VMS servers don't usually implement DDNS.)
Shut off the DHCP client.
Assign a static address to this server, outside of any local DHCP pool, and move on.
And correct your DNS server reference in your DHCP server, or static-define that address in VMS:
%TCPIP-W-NORECORD, information not found
-TCPIP-E-BIND_NOSERVERS, default servers are not available
If you go to static DNS and away from DHCP (as I'd recommend), also add the DNS server addresses into the configuration.
What triggered this error:
%DCL-W-IVCHAR, invalid numeric value - check for invalid digits
\%X|\
Isn't clear. But I'd guess there's a mix-up in some of the data and that then possibly (probably?) exposed a bug in the data verification elsewhere within the TCP/IP Services TCPIP$CONFIG tool. We'd need some additional details of the configuration to get to the bottom of that. Alternatively, ring up HP Support and report it to them.
I might also infer you're confused about how ARP and IP routing operates, and certainly how VMS displays that ARP information. (The DHCP stuff leading to What I *think* you're after here would either be a static host definition or acquiring host names via DNS services. Configuring for and DNS services scales far better.
In general: VMS is not a "discoverable" operating system, nor is the TCP/IP Services product. It's far too cryptic for that. It's nowhere near as easy to operate as OS X or Windows. Figuring out how VMS and IP works means reading the documentation and - unfortunately - making various mistakes. This process takes a while; as much as a year or two, maybe longer. I've been at this for longer, and I'm still learning. Formal training, if that's how you prefer to learn, can be helpful here too, as can acquiring a formal support channel. Or having somebody come in and do the baseline set-up and help work through parts of the platform port that you're apparently working on.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2012 07:06 AM
тАО03-14-2012 07:06 AM
Re: tcpip stack failure of config utility
many thanks Hoff,
yes it does seem like a huge learning curve to be expert in the complexities of TCPIP on VMS!
I have rebuild the Operating system v8.4 but still getting the same error on the interface side
eg
Configuration options:
%DCL-W-IVCHAR, invalid numeric value - check for invalid digits
\%X|\
i had copied sysuaf.dat, rightslist.dat and sylogicals.com from the previous system
can something in those be causing this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2012 07:18 AM
тАО03-14-2012 07:18 AM
Re: tcpip stack failure of config utility
HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu
Hostname Details: Configured=eddy, Active=eddy
Configuration options:
0 - Set The Target Node (Current Node: EDDY)
1 - IE0 Menu (EIA0: TwistedPair 100mbps)
2 - 129.94.185.40/25 eddy Configured,Active
3 - IE1 Menu (EIB0: TwistedPair 1000mbps)
4 - IE2 Menu (EIC0: TwistedPair 1000mbps)
5 - IE3 Menu (EID0: TwistedPair 1000mbps)
[E] - Exit menu
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2012 07:48 AM - edited тАО03-14-2012 07:58 AM
тАО03-14-2012 07:48 AM - edited тАО03-14-2012 07:58 AM
Re: tcpip stack failure of config utility
Please invest some time with the OpenVMS manuals and TCP/IP Services manuals, or with some customized OpenVMS training if that's how you prefer to learn, or (and this will be faster) acquire an escalation path. Somebody that understands VMS and IP networking, and particularly with somebody that has the time to dedicate to assisting you in your quest to learn about VMS.
Copying those files is not something I'd recommend when starting out. There's more to the "personality database" of a VMS host than in those few files, and copying those files without some care around the system environment can lead to odd file and directory ownerships, and to access that might be (incorrectly, unexpectedly) allowed, or denied. The complexity here is that copying these files around can and will mostly work, and sometimes all the way into production. But weird and arcane bugs can arise. Here's a related discussion.
For the time being, leave one NIC configured and enabled. Having more than one NIC enabled can (usually will) get into IP subnet routing and/or VLANs, and with whatever the local site is using for its network communications.
And there is a bug in that TCPIP$CONFIG tool (or something odd in the local environment) somewhere here, based on that DCL diagnostic in the earlier posting.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-14-2012 08:20 AM
тАО03-14-2012 08:20 AM
Re: tcpip stack failure of config utility
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-11-2014 08:08 AM
тАО04-11-2014 08:08 AM
Re: tcpip stack failure of config utility
This may occur when the parse style is set to extended. To see your setting issue the following command:
$ show process /parse
Parse Style: Extended
Change the parse style to traditional to see if this corrects the issue:
$ set proc /parse=trad
$ show process /parse
Parse Style: Traditional
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2014 06:30 AM
тАО06-20-2014 06:30 AM
Re: tcpip stack failure of config utility
Just for reference:
Check with SHOW PROC whether there is a valid User Identifier: [x,y] for the user invoking @TCPIP$CONFIG
If there is no Identifier name for the GROUP UIC, this error might happen. User Identifier: [xxx] would be shown in this case.
As a workaround: use a username with a valid User Identifier.
Volker.