Thanks JohnF. I understand that SEA is a Layer 2 bridge between the physical and the virtual interface. But in this case , only ent1 has a I/P. So, without the I/p how is the trafiic send from ent0 or ent2 ?
It will never work with the IP address on ENT1! I have no idea where ent1 is, is this on the VIO server, on the client LPAR? If it is on the client LPAR is it a physical adapter on a multi port card? If it is on the client LPAR but not a pysical port then there must be a second virtual adapter defined on the VIO server as logically ent0 on the client LPAR should (SHOULD) be connected to the first virtual adapter on the VIO (ENT7). You need to confirm exactly where ent1 is because at the moment I cannot comment on why ent1 has an IP address on it!
I have a script running remotely using viosvrcmd command on hmc to back up the VIO servers. these are the steps involved
1. Mount the NFS directory on to the VIO server
2. run backupios command
3. un mount the directory
I am stuck up in the 3rd step. I am not able to unmount the nfs... (6 Replies)
Hi,
I want to know wheather partition size for installation of vio client can be specified on vio server
example
If I am installing vio server on blade with 2*300gb hard disk,after that I want to create 2 vio client (AIX Operating system) wheather I can specify hard disk size while... (1 Reply)
Hi Guys,
I'm working on building a new 595 machine.. I'm try to achieve high availability for the VIO clients using 2 VIO servers, The ethernet part is satisfied using SEA failover, Now how do I achieve redundancy for the disks, its the servers internal disk attached to the scsi cards...
... (2 Replies)
I have same lun (hdisk3) assigned to 2 vios server (dual vio server) and this is mapped to the client lpar. I have sddpcm on the VIO.
On the VIOA, the attributes for fscsi1 and fscsi3 are set to fast_fail and dyntrk is set to yes
Now, if I do a lqueryvg -Atp on the hdisk3, I get a "DISK... (4 Replies)
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Hi,
I am facing an issue in vio server. When I run
bosboot -ad /dev/hdisk0
I am getting an error
trustchk: Verification of attributes failed: /usr/sbin/bootinfo
: accessauths
regards,
vjm
Please use code tags next time for your code and data. (8 Replies)
Hi,
So I downloaded this kernel source and was able to build it successfully.
But I want to add this SDK source code inside, can anyone help me how to do this? Note that the SDK source can be built by itself.
I added the SDK in the main Makefile:
init-y := init/
#added SDK... (0 Replies)
We've got two datacenters and in every datacenter 2 VIOs.
The VIO manages the I/O of the LPARs. So: Is it possible to reboot the VIO without shuting down an LPAR:wall: (4 Replies)
Hi Team,
My new build configuration always looking for the files from the build where i copied from.
please help me to resolve this.
I am using Visual studio 2008.It has Qt 4.8. plugins,qml,C++ development
I created new debug_new build configuration with additional preprocessor from the... (1 Reply)
Discussion started by: SA_Palani
1 Replies
LEARN ABOUT ULTRIX
scsi
SCSI(4) Kernel Interfaces Manual SCSI(4)Name
SCSI - Small Computer System Interconnect
Description
The ULTRIX system interfaces to disk and tape devices through the Small Computer System Interconnect (SCSI). Initial ULTRIX SCSI support
is limited to the Digital-supplied mass storage devices. The following devices are fully supported on the ULTRIX system:
o Winchester disks: RZ22, RZ23, RZ23L, RZ24, RZ55, RZ56, RZ57, RX23, RX26, RX33
o Magnetic tapes: TZ30, TZK50, TLZ04, TSZ05, TKZ08, TZK10
o Optical disks: RRD40, RRD42
Under the ULTRIX operating system, a SCSI device is referred to by its logical name. Logical names take the following form:
nn#
The nn argument is the two-character name; the number sign (#) represents the unit number. The two character names for SCSI devices are:
rz - RZ22, RZ23, RZ23L, RZ24, RZ55, RZ56, RZ57, RX23, RX26, RX33, RRD40, RRD42 disks
tz - TZ30, TZK50, TLZ04, TSZ05, TKZ08, and TZK10 tapes
The unit number is a combination of the SCSI bus number, either 0, 1, ... and the device's target ID number. The unit number is eight
times the bus number plus the target ID. For example, an RZ23 disk at target ID 3 on bus 0 would be referred to as rz3; a TZK50 tape at
target ID 5 on the second SCSI bus would be referred to as 13.
The SCSI bus has eight possible target device IDs. By default, one is allocated to the system. This allows for a maximum of seven target
devices connected to a SCSI bus.
Restrictions
The ULTRIX SCSI device driver does not operate with optical disks, other than the Digital-supplied devices.
The SCSI driver attempts to support on a best effort basis, non-Digital-supplied winchester disks and magnetic tapes.
The following notes apply to the driver's handling of non-Digital-supplied disks:
o These disks are assigned a device type of RZxx, instead of RZ22, RZ23, RZ23L, RZ55, RZ56, RZ57, RX23, RX26, or RX33. The RZxx disks
follow the same logical device naming scheme as the Digital-supplied disks.
o During the autoconfigure phase of the system startup, the driver prints the contents of the SCSI vendor ID, product ID, and the
revision level fields of the inquiry data return by the SCSI device.
o RZxx disks are assigned a default partition table. The default table can be modified by editing the sz_rzxx_sizes[8] entry in the
file The utility can also be used to modify the partition table on a RZxx disk.
o The only logical unit number (LUN) supported for each target ID is 0.
See Alsorz(4), tz(4), chpt(8)SCSI(4)