02-28-2007
I realize it doesn't help you, but I though the ESS 800 was only supported on Solaris 9 and 10.
9 More Discussions You Might Find Interesting
1. Solaris
I Have IBM ESS 800, trying to configure SAN storage using Fiber card. I installed the SDD driver & can see the disks however, when I did
# datapath query device
I have the disks shown in slices
# ./datapath query device
Total Devices : 8
Dev#: 0 Device Name: vpath1a Type:... (0 Replies)
Discussion started by: Remi
0 Replies
2. AIX
Hi,
I have a strange problem. we're trying to connect an IBM pseries, to a Brocade switch, for SAN acess, using a badged emulex card, (IBM FC6239) WE can configure the device to see the fabric. The only problem we have is that the Brocade sees the HBA as storage, and not as a HBA.
We've zoned... (1 Reply)
Discussion started by: praxis22
1 Replies
3. Solaris
Hi,
How can we differentiate a SAN disk with a Solaris local disk?
Please respond.
Thanks (4 Replies)
Discussion started by: balu_solaris
4 Replies
4. Solaris
Hi
I would like to remove SAN luns from system and do not want them even after system reboot,
format
Searching for disks...done
df -kh
I know last 4 partitions are from SAN but there could be more.
Can someone please help me correct steps to remove SAN Luns.
vxdisk list
... (2 Replies)
Discussion started by: upengan78
2 Replies
5. Solaris
Hi,
I have configured our SAN Storage to be connected to our new SUN T5220.
On the SAn it looks all fine
on the server I do not see any connection:
cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c1 scsi-bus connected ... (4 Replies)
Discussion started by: manni2
4 Replies
6. Solaris
My current situation is like this, I have a v440 connected to a netapp central storage 3140 via fiber channel, my OS and oracle is installed in the internal drive of the v440.
What I would like to do is to advertise another LUN in netapp to the v440 and let my v440 boot from it so I can start... (3 Replies)
Discussion started by: q8devilish
3 Replies
7. Solaris
I have a solaris 10 box which does not have internal disks it has just a single dual port HBA card. Storage team has assigned 2 LUNs to the system and i can see it from the probe-scsi-all
/pci@3,700000/SUNW,emlxs@0,1
Device PortID 10100 WWPN 5006016941e0a08d
LUN 0 Disk DGC ... (0 Replies)
Discussion started by: fugitive
0 Replies
8. Solaris
HI All,
What are IPFC(Internet Protocol over Fibre channel) SAN devices.
What all i got from guide is
"Configuring IPFC over host system describes host recognition of IPFC devices and implementation of IP over FC in SAN"
What does above statement actually mean. I would appreciate detailed... (2 Replies)
Discussion started by: ravijanjanam12
2 Replies
9. Solaris
Hi All,
Hopefully you can answer my question.
We are about to move to a new Fibre Channel infrastructure going from Cisco to Brocade switches. Amongst others, we have a number of Solaris 9 hosts which connect to our EVA5000 and EVA8100 array's.
What is involved in moving the Solaris hosts to... (3 Replies)
Discussion started by: eptc
3 Replies
LEARN ABOUT HPUX
hp-mc680x0
machid(1) General Commands Manual machid(1)
NAME
machid: hp9000s200, hp9000s300, hp9000s400, hp9000s500, hp9000s700, hp9000s800, hp-mc680x0, hp-pa, pdp11, u370, u3b, u3b10, u3b2, u3b5, vax
- provide truth value about processor type
SYNOPSIS
DESCRIPTION
The following commands return a true value (exit code 0) if the a processor type matches the command name. Otherwise a false value (exit
code nonzero) is returned. These commands are commonly used within makefiles and shell procedures to improve portability of applications
(see make(1)).
+-----------+-------------------------++--------+--------------------------+
|Command | True for ||Command | True for |
+-----------+-------------------------++--------+--------------------------+
|hp9000s200 | Series 200 ||pdp11 | PDP-11/45 or PDP-11/70 |
|hp9000s300 | Series 300 ||u3b | 3B20 computer |
|hp9000s400 | Series 400 ||u3b2 | 3B2 computer |
|hp9000s500 | Series 500 ||u3b5 | 3B5 computer |
|hp9000s700 | Series 700 ||u3b10 | 3B10 computer |
|hp9000s800 | Series 800 or 700 ||u370 | IBM System/370 computer |
|hp-mc680x0 | Series 200, 300, or 400 ||vax | VAX-11/750 or VAX-11/780 |
|hp-pa | Series 700 or 800 || | |
+-----------+-------------------------++--------+--------------------------+
EXAMPLES
Given a shell script that must behave differently when run on an HP 9000 Series 700 or 800 system, select the correct code segment to be
executed:
WARNINGS
always returns true on both Series 800 and Series 700 systems. Therefore, when using this command in scripts to determine hardware type,
always use both and in the appropriate sequence to ensure correct results (see
machid(1) will no longer provide support for future machines beyond the Series 800 and Series 700 systems. Decisions should be based on
the hardware and software configuration information returned by getconf(1).
SEE ALSO
getconf(1), make(1), sh(1), test(1), true(1).
machid(1)