Operating System - HP-UX
1830018 Members
2065 Online
109998 Solutions
New Discussion

Re: auto_parms [68] error

 
SOLVED
Go to solution
TrustNo1
Regular Advisor

auto_parms [68] error

After making the change from an ATM , instance [0] to a 100BT , instance [1] primary lan card. At boot, I'm getting the following error;
"Auto_Parms [68] LanDeviceList Subscript must be smaller than 1024k."
I see no direct problems as a result of whatever this is telling me.

Thanks, ~jdk
Dare to Dream
4 REPLIES 4
Sundar_7
Honored Contributor
Solution

Re: auto_parms [68] error


I would suspect some typo in netconf file ?

Post the contents.
Learn What to do ,How to do and more importantly When to do ?
Mark Grant
Honored Contributor

Re: auto_parms [68] error

My first thought would also be a typo in /etc/rc.config.d/netconf but auto_parms is a script so you could look at it and see what it is trying to do at line 68.
Never preceed any demonstration with anything more predictive than "watch this"
Steven E. Protter
Exalted Contributor

Re: auto_parms [68] error

Quick fix:

set_parms command, based on prior posts.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
TrustNo1
Regular Advisor

Re: auto_parms [68] error

Sundara,
Looks like the following entires were in the netconf file twice. Once where they should be, and once at the end of the file.
IP_ADDRESS[1]=xxx.xx.xx.xxx
SUBNET_MASK[1]=255.255.0.0
INTERFACE_NAME[1]=lan1
BROADCAST_ADDRESS[1]="xxx.xx.xx.xx
LANCONFIG_ARGS[1]="ether"

Mark,
Sounded like a good idea!
60 # User input message ids
61 #
62 export APPLY_DHCP_DATA=70
63 export CONTINUE_EXECUTION=71
64
65 #
66 # Error message ids
67 #
68
69 export WARN_HEADER=100
70 export WARN_LEASE_VALID_NOT_UPDATED=101
71 export WARN_NAK_FROM_SERVER=102
72 export WARN_DHCP_GENERAL=103
73 export WARN_DHCP_REJECT=104

Steven,
Yes, that was tempting, and the most logical answer...although in this case, I don't think that would have fixed it, in fact I'm not exactly sure, what it would have said , mabe the same error....

I'll give the fixed file a shot and see what happens.

Thanks All!! , ~jdk
Dare to Dream