Seeking description or table listing hidden kernel variables

[A. Earl Jackson]

Recently I posted a question in the hp usenet regarding an IP problem that I had with subnet. The resolution of the problem required alterning a variable for the lack of better terms labeled "check_bcast_addr" using the absolute debugger. I found at tutorial on the absolute debugger here at HP's web site. But what I really would like to see is a listing or table of these variables such as "check_bcast_addr" to see what these respresent and if there are others that may for example effect the backplane addressing or other issues. I would appreciate opening a dialog with someone who could point me to a reference that might house a description of these variables, default values and what would happen if the vaiable changes or whatever. Thanks to all that respond.

[Duncan Edmonstone]

Was this a HP-UX 9 or 10 system by any chance? A lot of these 'hidden' kernel parameters relating to the behaviour of the TCP/IP stack are now handled through the 'ndd' command in HP-UX11.x and 'nettune' in HP-UX10.20

HTH

Duncan

[A. Earl Jackson]

I am using an HP744 132L VME machine running HP-UX 10.2. The problem that I am having is in the backplane addressing. It seems that the addressing on the backplane is fixed and can't be changed. Since I had to adjust the check_bcast_addr hidden variable to correct the IP addressing problem, I felt that there may be hidden variables with the backplane preventing me from changing the backplane addressing as well.

[Duncan Edmonstone]

Earl,

I'm not sure I follow you here... are you talking about hardware paths as shown in an ioscan? Can you be more specific about what your problem is.

HTH

DUncan

[harry d brown jr]

The problem with "messing" with "hidden" kernel parameters is that you could easily "toast" your machine. You should contact HP directly and ask for third level support where they can guide you through the issues. If you take it upon yourself you will probably end up rebuilding your system. Make sure you take a good tape_make_recovery.

live free or die
harry

[A. Earl Jackson]

HP 744's come in two types. The first type is a standard embedded computer card that runs under HP-UX while the second type is the RT version that uses HP-RT as its operating environment. Communication between these cards is achieved by means of the VME backplane. I have never setup communications via a VME bus before. Although, I believe that communications is similar to setting up an Ethernet connection. The backplane does have an IP addressing similar to that of the Ethernet. It appears that the backplane IP is fixed. When I try to reset the IP address and reboot the system then the IP returns to its orginial setting. So, of course, thinking that if the check_bcast_addr is a hidden variable that corrected an irregular setnet setting then a variable may exist that fixes the backplane addressing as well. So, my began my effort to seek out all the hidden variables, definitions of each variable, their defualts to learn the hidden secrets of the HPUX operating system.

I know that tinkering with the hidden variables is somewhat dangerous. However, I am not concerned with screwing up this machine. I have made complete as well as changed backups since I began setting this machine up.

[Duncan Edmonstone]

Well you've got me there Earl - I confess to knowing zip about Versa Module Eurocard buses. I presume you have looked at the documentation here:

http://www.hp.com/products1/vmesystems/support/doc_vme/

And particularly chapter 9 of this document on backplane networking:

http://www.hp.com/products1/vmesystems/support/doc_vme/A4412-90022.pdf

Cheers

Duncan

[Jay Gaffney_4]

Heres and old cheat sheet I used when working with 744's. This sheet was for 10.20, 11.x might be different, i.e. VME isn't on the Core OS CD's but is ( or was ) a download from HP.

Note that the patch numbers may be different now... and of course YMMV, #include

Please consult the manual "VME Services for HP-UX 10 and 11". An online
version of this manual is located at: http://www.hp.com/products1/vmesystems/support/doc_vme/

The document number is A4412-90022, and it is in Adobe Acrobat format.
Please reference chapters 7 - "Installing VME Devices", 8 - "Configuring
VME Devices" and 9 - "Backplane Networking at 10.20 and later releases".

To install VME-Services, the basic step to be taken are -
1) If it is not already on your system, install VME-Services software from
Core O/S CD-ROMs

To check if VME-Services are installed
# swlist VME-Services

You should see output such as
# Initializing...
# Contacting target "host"...
#
# Target: host:/
#
# VME-Services B.10.20
HP-UX VME Services
VME-Services.VME-BPN B.10.20 VME
Backplane Networking
VME-Services.VME-KRN B.10.20
VME Services and Configuration Program
VME-Services.VMEC-ENG-A-MAN B.10.20

If you see the above output, you have VME-Services installed.

2) Install VME Services Patch PHKL_18872 and VME Configuration Patch
PHCO_11715

3) Add vme2 (and bpn, if necessary for backplane networking) to the
kernel using SAM and reboot.

4) Edit your vme.CFG configuration file to specify your configuration
information. Syntax of vme.CFG can be check with vme_config(1M),
example

# vme_config -c vme.CFG

Correct any error before continuing. See VME-Service documentation
for details.

5) Use vme_config(1M) to set the appropriote CPU number for this board,
example

# vme_config -N 0

for slot 1 controller board.

6) Run vme_config(1M) to save the configuration in EEPROM,
example

# vme_config -f vme.CFG

7) If necessary for backplane networking, run bp_config(1M) to update
EEPROM with backplane information, example

# bp_config -f vme.CFG

8) Edit /etc/rc.config.d/netconf to enable backplane networking at boot up,
example

# LAN stuff
INTERFACE_NAME[0]=lan0
IP_ADDRESS[0]=32.0.0.1
SUBNET_MASK[0]=255.255.254.0
BROADCAST_ADDRESS[0]=""
LANCONFIG_ARGS[0]="ether"
DHCP_ENABLE[0]=0

# bpn stuff
INTERFACE_NAME[1]=bp0
IP_ADDRESS[1]=192.0.0.1
SUBNET_MASK[1]=255.255.254.0
BROADCAST_ADDRESS[1]=""

Please note that your setting for IP addresses and subnet masks will most
likely be different. At least I hope so!

9) Reboot

10) Run VME successfully! When the system boots up, you will notice
that the red light is no longer on. This indicates that
VME-Services is installed