topic Re: RP8400 - Onboard Lan Config in Operating System - HP-UX

RP8400 - Onboard Lan Config

Trina M. Clapperton — Mon, 02 Mar 2009 21:22:52 GMT

Hi - I'm not seeing the Onboard lan from ioscan. It shows as a 1G port at the rear of the server, I see the link light on connecting it the lan. But not seeing from "ioscan -fnC lan" or "lanscan".

Any ideas ? Does this port need to be enabled somehow ?

Re: RP8400 - Onboard Lan Config

smatador — Mon, 02 Mar 2009 21:49:46 GMT

Hi,
On box like rp8400, you have MP lan. This is the lan console.
To configure the MP, you first need to configure the IP address of the MP LAN and to do this you will need to configure it with a serial cable plug in console.
Once you are at the console, you configure lan in CM (command mode) , then LC (lan config) Once you set this IP address and default gateways, you can use MP LAN port as your lan console.
The unix does not see a lan interface.

Re: RP8400 - Onboard Lan Config

Matti_Kurkela — Mon, 02 Mar 2009 22:05:57 GMT

A rp8400 is a nPar-capable server. That means the server may have been "split" electronically into two or more servers within the same chassis. vPar software allows to do the same at the software level. If either nPar or vPar partitioning is in use, one LAN interface can belong to only one partition at a time. The LAN could even be left outside the configuration of all partitions, if someone expected to create yet another partition in the near future.

To know the partitioning status of your machine, run the commands "parstatus" (for hardware-level nPar) and "vparstatus (for vPars).
Note: if vPar software is not installed, the vparstatus command will fail. By that, you know vPar partitioning is not in use.

But if the parstatus command fails, you cannot necessarily assume nPar is not used: in that case, you must access the MP and check the system configuration from there. (This might happen if someone has transferred the OS installation from a non-partitioned server to rp8400 using Ignite and hasn't installed the nPar tools after that.)

After checking the partitioning configuration, we might have a better idea of what is going on...

MK

Re: RP8400 - Onboard Lan Config

melvyn burnard — Tue, 03 Mar 2009 13:06:33 GMT

so are you referring to the System Lan on th eMP, or the MP Lan on the MP card?

If it is the MP lan then the OS cannot see this port, only the System Lan

Re: RP8400 - Onboard Lan Config

Trina M. Clapperton — Tue, 03 Mar 2009 15:02:14 GMT

Matt - I am referring to the other LAN port - not the one for the MP Console.

Re: RP8400 - Onboard Lan Config

Torsten. — Tue, 03 Mar 2009 15:04:03 GMT

Can you please post

# ioscan -fn
# parstatus

Re: RP8400 - Onboard Lan Config

Trina M. Clapperton — Tue, 03 Mar 2009 15:11:13 GMT

I attached the ioscan output with the opening of the thread. See parstatus below. Thanks.

The total number of Partitions Present : 1

[Cabinet]
Cabinet I/O Bulk Power Backplane
Fans Fans Supplies Power Boards
OK/ OK/ OK/ OK/
Cab Failed/ Failed/ Failed/ FAILED/
Num Cabinet Type N Status N Status N Status N Status GSP
=== ============ ========= ========= ========== ============ ======
0 S16K-A 21/ 0/ N+ 6/ 0/ N+ 6/ 0/ N+ N/A active

Notes: N+ = There are one or more spare items (fans/power supplies).
N = The number of items meets but does not exceed the need.
N- = There are insufficient items to meet the need.
? = The adequacy of the cooling system/power supplies is unknown.

[Cell]
CPU Memory Use
OK/ (GB) Core On
Hardware Actual Deconf/ OK/ Cell Next Par
Location Usage Max Deconf Connected To Capable Boot Num
========== ============ ======= ========= =================== ======= ==== ===
cab0,cell0 active core 4/0/4 16.0/ 0.0 cab0,bay0,chassis0 yes yes 0
cab0,cell1 active base 4/0/4 12.0/ 0.0 cab0,bay0,chassis1 yes yes 0
cab0,cell2 active base 4/0/4 12.0/ 0.0 - no yes 0
cab0,cell3 active base 4/0/4 10.0/ 0.0 - no yes 0

[Chassis]
Core Connected Par
Hardware Location Usage IO To Num
=================== ============ ==== ========== ===
cab0,bay0,chassis0 active yes cab0,cell0 0
cab0,bay0,chassis1 active yes cab0,cell1 0

[Partition]
Par # of # of I/O
Num Status Cells Chassis Core cell Partition Name (first 30 chars)
=== ============ ===== ======== ========== ===============================
0 active 4 2 cab0,cell0 Partition 0

Re: RP8400 - Onboard Lan Config

Torsten. — Tue, 03 Mar 2009 15:20:09 GMT

I can't find an "ioscan -fn", sorry.

Re: RP8400 - Onboard Lan Config

Shahul — Tue, 03 Mar 2009 15:28:58 GMT

Hi,

You should see two Gig bit ports if you only have one partition in the chassis. I can see two ports on all of my RP8400 box. Check you the gelan/igelan drivers, also try if it is visible in lanscan.

Good luck
Shahul

Re: RP8400 - Onboard Lan Config

Trina M. Clapperton — Tue, 03 Mar 2009 15:31:58 GMT

ioscan -fn:

Class I H/W Path Driver S/W State H/W Type Description
==============================================================================
root 0 root CLAIMED BUS_NEXUS
cell 0 0 cell CLAIMED BUS_NEXUS
ioa 0 0/0 sba CLAIMED BUS_NEXUS System Bus Adapter (804)
ba 0 0/0/1 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 1 0/0/1/0/0 PCItoPCI CLAIMED BUS_NEXUS PCItoPCI Bridge
ext_bus 8 0/0/1/0/0/4/0 c720 CLAIMED INTERFACE SCSI C896 Ultra2 Wide LVD
target 0 0/0/1/0/0/4/0.7 tgt CLAIMED DEVICE
ctl 6 0/0/1/0/0/4/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c8t7d0
ext_bus 9 0/0/1/0/0/4/1 c720 CLAIMED INTERFACE SCSI C896 Ultra2 Wide LVD
target 1 0/0/1/0/0/4/1.1 tgt CLAIMED DEVICE
tape 1 0/0/1/0/0/4/1.1.0 stape CLAIMED DEVICE HP C5683A
/dev/rmt/1m /dev/rmt/1mnb /dev/rmt/c9t1d0BESTn /dev/rmt/c9t1d0DDSb
/dev/rmt/1mb /dev/rmt/c9t1d0BEST /dev/rmt/c9t1d0BESTnb /dev/rmt/c9t1d0DDSn
/dev/rmt/1mn /dev/rmt/c9t1d0BESTb /dev/rmt/c9t1d0DDS /dev/rmt/c9t1d0DDSnb
target 2 0/0/1/0/0/4/1.7 tgt CLAIMED DEVICE
ctl 7 0/0/1/0/0/4/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c9t7d0
lan 2 0/0/1/0/0/6/0 btlan CLAIMED INTERFACE HP A5838A PCI 100Base-TX/SCSI COMBO
/dev/diag/lan2 /dev/ether2 /dev/lan2
lan 3 0/0/1/0/0/7/0 btlan CLAIMED INTERFACE HP A5838A PCI 100Base-TX/SCSI COMBO

ba 2 0/0/10 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (782)
ba 3 0/0/10/0/0 PCItoPCI CLAIMED BUS_NEXUS PCItoPCI Bridge
fc 0 0/0/10/0/0/4/0 fcd CLAIMED INTERFACE HP A9784-60001 PCI/PCI-X Fibre Channel FC/GigE Combo Adapter (FC Port 1)
/dev/fcd0
fcp 0 0/0/10/0/0/4/0.1 fcd_fcp CLAIMED INTERFACE FCP Domain
ext_bus 4 0/0/10/0/0/4/0.1.0.0.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
target 3 0/0/10/0/0/4/0.1.0.0.0.0 tgt CLAIMED DEVICE
disk 3 0/0/10/0/0/4/0.1.0.0.0.0.0 sdisk CLAIMED DEVICE NETAPP LUN
/dev/dsk/c4t0d0 /dev/rdsk/c4t0d0
disk 4 0/0/10/0/0/4/0.1.0.0.0.0.1 sdisk CLAIMED DEVICE NETAPP LUN
/dev/dsk/c4t0d1 /dev/rdsk/c4t0d1
disk 5 0/0/10/0/0/4/0.1.0.0.0.0.2 sdisk CLAIMED DEVICE NETAPP LUN
/dev/dsk/c4t0d2 /dev/rdsk/c4t0d2

ext_bus 7 0/0/10/0/0/4/0.1.1.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
target 17 0/0/10/0/0/4/0.1.1.255.0.0 tgt CLAIMED DEVICE
ctl 5 0/0/10/0/0/4/0.1.1.255.0.0.0 sctl CLAIMED DEVICE NETAPP LUN
/dev/rscsi/c7t0d0
lan 1 0/0/10/0/0/6/0 igelan CLAIMED INTERFACE HP A9784-60001 PCI/PCI-X 1000Base-T FC/GigE Combo Adapter
memory 0 0/5 memory CLAIMED MEMORY Memory
processor 0 0/10 processor CLAIMED PROCESSOR Processor
processor 1 0/11 processor CLAIMED PROCESSOR Processor
cell 1 1 cell CLAIMED BUS_NEXUS
ioa 1 1/0 sba CLAIMED BUS_NEXUS System Bus Adapter (804)
memory 1 1/5 memory CLAIMED MEMORY Memory
cell 2 2 cell CLAIMED BUS_NEXUS
memory 2 2/5 memory CLAIMED MEMORY Memory
processor 2 2/10 processor CLAIMED PROCESSOR Processor
processor 3 2/11 processor CLAIMED PROCESSOR Processor
processor 4 2/12 processor CLAIMED PROCESSOR Processor
processor 5 2/13 processor CLAIMED PROCESSOR Processor
cell 3 3 cell CLAIMED BUS_NEXUS
memory 3 3/5 memory CLAIMED MEMORY Memory
processor 6 3/10 processor CLAIMED PROCESSOR Processor
processor 7 3/11 processor CLAIMED PROCESSOR Processor
processor 8 3/12 processor CLAIMED PROCESSOR Processor
processor 9 3/13 processor CLAIMED PROCESSOR Processor

Re: RP8400 - Onboard Lan Config

Trina M. Clapperton — Tue, 03 Mar 2009 15:32:56 GMT

lanscan:

Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
0/0/1/0/0/6/0 0x00306E2DCA7C 2 UP lan2 snap2 1 ETHER Yes 119
0/0/1/0/0/7/0 0x00306E2DCA7D 3 UP lan3 snap3 2 ETHER Yes 119
0/0/10/0/0/6/0 0x00306EF2F8FD 1 UP lan1 snap1 3 ETHER Yes 119

Re: RP8400 - Onboard Lan Config

Torsten. — Tue, 03 Mar 2009 15:45:37 GMT

IMHO this must be a vPar, because of this "short" ioscan output.

Please try

# vparstatus -v

Re: RP8400 - Onboard Lan Config

Torsten. — Tue, 03 Mar 2009 15:51:33 GMT

Your ioscan lists only 2 LBAs, 0/0/1 and 0/0/10. This is slot 8 and slot 2 of I/O chassis connected to cell 0.

Because of this it must be a vPar.