Difference between connection lan HPUX9.07 and HPUX11

[Christophe MESTDACH]

Hello,

Excuse me for my english but i'm French.

My company bought 140 machines HP B2600 9000/785 to replace old machines functioning under HP UX 9.07.

All the machines do not have the same role : some work as server and others as clients. I must initially install the server under HPUX 11 and inter-connect server HPUX 11 with the clients under HPUX9.07

Connection network used on the machines HP-UX 9.07 is a connection Ethernet 802.3.

1 - It is possible to inter-connect on the network a machine under HPUX11 and a machine under HPUX9.07 ?

2 - Under HP-UX 11, I must choose between a connection lan0 Ethernet and snap0 802.3.
Which is the difference between these 2 connections, because I thought that a connection 802.3 was an Ethernet connection?

3 - Can I inter-connect a machine (client) under HP-UX 9.07 (connection lan0 802.3) with a machine (server) under HP_UX 11 (connection lan0 Ethernet)?

Thanks

[Michael Steele_2]

11.00 has many, many configuration differences. Using the "...set_parms initial..." -or- "...set_parms ip_address..." command is your most effective utility for configuring your servers since it will automatically load hostname, ip, gateway, nis server, ntp server, etc. Refer to the /usr/newconfig/etc/rc.config.d/netconf file for defaults in 11.00 now.

All major system configurable parameters are found in /etc/rc.config.d.

/etc/init.d has been moved to /sbin/init.d. Become familier with how init.d interacts with /sbin/rc#.d startup and shutdown scripts and the parameters in /etc/rc.config.d.

11.00 will talk to 9.07. These are OSI "open systems" requirements. So become familiar with the differences, which will be information and not really practical as time goes on.

Here are some files and commands to bear in mind:

/etc/rc.config.d/netconf (* man

Logical interfaces allow multiple IP addresses per card. This is known as "...IP multiplexing..."

IP/IEEE802.3 requires SNAP encapsulation and a separate logical interface.

SNAP = Sub-Network Access Protocol (SNAP) encapsulation.

SNAP is what makes IP multiplexing possible.

Use the "...ndd..." utility for examining and modifying system-wide LAN transport parameters.

"...ndd..." is a very important nework utility. Refer to the /etc/re.config.d/nddconf file. Learn this syntax:

ndd -get /dev/ip
for example:
ndd -get /dev/ip ip_ire_ge_probe

Also,

ndd -set /dev/ip ip_ire_gw_probe 0

New PPP software replaces PPL to provide both PPP and SLIP connections.

Here are obsolete Features and there new alternatives:

lanconfig (functionality included in ifconfig/lanadmin).

ifalias (functionality included in ifconfig).

nettune (functionality included in ndd).

ppl (replaced by pppd).

No longer a BSD TCP/IP stack

[Steven E. Protter]

This is business, not politcs.

Best way to go is to set up an Ignite image server. You can create a general workstation image under 11 and distribute it to work stations by booting off the Ignite server. That's a great way to manage OS/Patches or a major upgrade.

As far as ability to interact and connect, that is certainly possible, I've heard of plenty of shops that still use mixed environments. The problem with running 9.07 is the lack of support from HP.

There are security issues not dealt with and patches you're not going to get.

Direct answers to your questions:

1) Yes
2) You are right.
3) Yes

SEP

[Tim D Fulford]

Hi

The quick answer to your main question is yes, 9.07 should be able to work (in a networking sense any way) with 11.00

All the above advice is good. The only thing I would like to add is...

o In HP-UX 11.00 you can use MULTIPLE IPs on the same interface. e.g.
lan0 - 172.164.2.3
lan0:1 - 172.164.57.12
It is possible to have different netmasks on the same interface, but there are obvious limitations as far as bridge groups etc are concerned.

Tim

[Ajit Natarajan]

In general, a client in HP-UX 9.x should be able to run with a server in HP-UX 11.x and vice versa. Note that HP-UX 9.x is obsolete, may not be Y2K compliant, and its use is discouraged.

Let me explain the difference between lan and snap. The difference is encapsulation.

Any frame on an Ethernet network contains the following components:

An Ethernet MAC header
Optionally, an LLC header
Payload
CRC

MAC - medium access layer
LLC - logical link control
CRC - cyclic redundancy check, something like a checksum

An example of payload is an IP packet.

In the case of lan (also called Ethertype), the Ethernet MAC header contains the following components:

destination MAC address
source MAC address
type

Each MAC address is 6 bytes long and type is 2 bytes long. Type specifies the packet type that follows. For example, IP payload has type 0x800.

For lan, there is no LLC header.

In the case of SNAP, the MAC header has the following format:

destination MAC address
source MAC address
length

Length is the length of the payload in bytes. Since the size of an Ethernet payload cannot exceed 1500 bytes, length has to be <= 1500. (Jumboframes are handled differently.)

The SNAP LLC header consists of:

DSAP = 0xaa
SSAP = 0xaa
control = 3
organization ID = 0x0 0x0 0x0
PID

PID is the same as the type field in lan.

lan is distinguished from SNAP by looking at the two byte field immediately after the source MAC address: if the field is <= 1500, it is SNAP, otherwise it is lan.

Configuring an interface as lanx (where x is the PPA - physical point of attachment - also called instance number - see lanscan(1M)) will result in that interface using lan encapsulation on outbound.

Configuring an interface as snapx will result in that interface using SNAP encapsulation on outbound.

In either case, the interface can process either encapsulation on inbound.

There is a third type of encapsulation called 802.3 SAP which I won't go into further detail here.

Whether you configure an interface to use lan or SNAP encapsulation depends on the remote side and the encapsulations it will understand. In general, using lan encapsulation is safest.

Thanks.

Ajit
HP Gigabit Ethernet