Sponsored Content
Full Discussion: Redhat Virtualization 2.2
Operating Systems Linux Red Hat Redhat Virtualization 2.2 Post 302454580 by arumon on Sunday 19th of September 2010 01:58:32 AM
Old 09-19-2010
Hi,

Thanks for the reply. I am looking for a user/admin only.
I am trying to setup rhev 2.2 and facing issues on the iSCSI storage connectivity. It is able to login to lun connection but not showing as a storage. Any idea?

Regards,
aravind
 

10 More Discussions You Might Find Interesting

1. Virtualization and Cloud Computing

Hardware virtualization

Hello to all In my organization we want to pass to move the systems to an virtualized environment, nevertheless, considering the absence of resources, the idea is to acquire the versers and that the department (I) do the facilities, tests, etc. Wearing out the possible minimal cost in... (1 Reply)
Discussion started by: aalvarez77
1 Replies

2. HP-UX

Virtualization Software

Hello peopel I am interesting in implement a virtualization system on HP-UX v3. I have some Integrity servers with this OS installed but I want to virtualize one of them because I have a problem that has no solution in HP-UX and I have to install RedHat for this reason. Then I don't know what... (1 Reply)
Discussion started by: Lekram
1 Replies

3. Virtualization and Cloud Computing

Virtualization problems

Hi everyone. Last week we have some hardware problems in our Unixware 7 server, and i decided to change this physical machine into a virtual machine. The scenario is: architecture=IA32 bus_types=PCI2.10,ISA,PnP1.0 hostname=tecsup2uw.tecsupaqp.edu hw_provider=Generic AT... (1 Reply)
Discussion started by: danilosevilla
1 Replies

4. HP-UX

Virtualization options for HP-UX 11.31

Hello, I am looking for a virtualization option for HP-UX that will allow VMs to run completely independent of each other with full Operating System capabilities (not a guest OS with limited features/access), with their own IP addresses and dedicated resources that will not interfere with any... (4 Replies)
Discussion started by: bstring
4 Replies

5. Solaris

solaris virtualization

Hi everyone, I have ten servers with solaris (diffrent versions). there is solaris 10, solaris 6 and solaris 8. some are SPARC and some are x86 I would like to move them to one server so they all will be virtual. Is it possible? how? (4 Replies)
Discussion started by: bregtux
4 Replies

6. UNIX for Advanced & Expert Users

Sort command results are different in Redhat 4 vs Redhat 5

Hi, I am having a text file with the following contents ########### File1 ########### some page1.txt text page.txt When I sort this file on Red Hat 5, then I get the following output ########### File1 ########### page1.txt page.txt some (3 Replies)
Discussion started by: sarbjit
3 Replies

7. Linux

Virtualization best practices

Hello admins and gurus I have a controversial topic: now we are investing in a new Linux OS that will hold our Sybase database. The server will virtualized on a VMware server hosted on SAN storage. Now the question is, when we install the database engine is it better - in terms of performance -... (1 Reply)
Discussion started by: abohmeed
1 Replies

8. Virtualization and Cloud Computing

Virtualization on vmware

Got tired of messing around with real hardware old and others.. Decided to spend some $$ for a QUAD-core dual cpu laptop with 8 gig of ram and 1 TB disk space.. running VMware workstation 10 on windows 8.0 , with a pair of solx86 vcs 5.1 cluster and a pair of rhel 6.4 vcs 6.x cluster.. ... (0 Replies)
Discussion started by: ppchu99
0 Replies

9. UNIX for Beginners Questions & Answers

Redhat Virtualization EN error : InitLogger main process terminated with status 1

My server has /var/log/messages with 'init: initLogger main process (608798) terminated with status 1' errors. I researched about the error and also followed the steps from stackexchange : 157059/error-init-ttys0-dev-ttys0-main-process-1612-terminated-with-status-1]linux - ERROR: init: ttyS0... (0 Replies)
Discussion started by: Paras Pandey
0 Replies

10. UNIX for Advanced & Expert Users

Solaris Virtualization

Hello All, To start with, I am not an expert of solaris and VMs. Unfortunately, I can't find a direct or understandable (at least to me) answer to my question online. So please, excuse me if my question will sound dumb to you. :o We have 2 remaining solaris 8 servers are on sparc... (9 Replies)
Discussion started by: forextrafun
9 Replies
TARGETS(5)						      BSD File Formats Manual							TARGETS(5)

NAME
targets -- configuration file for iSCSI targets SYNOPSIS
targets DESCRIPTION
The targets file describes the iSCSI storage which is presented to iSCSI initiators by the iscsi-target(8) service. A description of the iSCSI protocol can be found in Internet Small Computer Systems Interface RFC 3720. Each line in the file (other than comment lines that begin with a '#') specifies an extent, a device (made up of extents or other devices), or a target to present to the initiator. Each definition, an extent, a device, and a target, is specified on a single whitespace delimited line. The extent definition specifies a piece of storage that will be used as storage, and presented to initiators. It is the basic definition for an iSCSI target. Each target must contain at least one extent definition. The first field in the definition is the extent name, which must begin with the word ``extent'' and be followed by a number. The next field is the file or NetBSD device which will be used as persistent storage. The next field is the offset (in bytes) of the start of the extent. This field is usually 0. The fourth field in the definition is the size of the extent. The basic unit is bytes, and the shorthand KB, MB, GB, and TB can be used for kilobytes (1024 bytes), megabytes (1024 kilobytes), gigabytes (1024 megabytes), and terabytes (1024 gigabytes) respectively. It is possible to use the word ``size'' to use the full size of the pre-existing regular file given in the extent name. The device definition specifies a LUN or device, and is made up of extents and other devices. It is possible to create hierarchies of devices using the device definition. The first field in the definition is the device name, which must begin with the word ``device'' and be followed by a number. The next field is the type of resilience that is to be provided by the device. For simple devices, RAID0 suffices. Greater resilience can be gained by using the RAID1 resilience field. Following the resilience field is a list of extents or other devices. Large devices can be created by using multiple RAID0 extents, in which case each extent will be concatenated. Resilient devices can be cre- ated by using multiple RAID1 devices or extents, in which case data will be written to each of the devices or extents in turn. If RAID1 resilience is used, all the extents or sub-devices must be the same size. Please note that RAID1 recovery is not yet supported by the iscsi-target(8) utility. An extent or sub-device may only be used once. The target definition specifies an iSCSI target, which is presented to the iSCSI initiator. Multiple targets can be specified. The first field in the definition is the target name, which must begin with either of the words ``target'' or ``lun'' and be followed by a number. Optionally, if a target is followed by an ``='' sign and some text, the text is taken to be that of the iSCSI Qualified Name of the target. This IQN is used by the initiator to connect to the appropriate target. The next field is a selector for whether the storage should be pre- sented as writable, or merely as read-only storage. The field of ``rw'' denotes read-write storage, whilst ``ro'' denotes read-only storage. The next field is the device or extent name that will be used as persistent storage for this target. The fourth field is a slash-notation netmask which will be used, during the discovery phase, to control the network addresses to which targets will be presented. The magic val- ues ``any'' and ``all'' will expand to be the same as ``0/0''. If an attempt is made to discover a target which is not allowed by the net- mask, a warning will be issued using syslog(3) to make administrators aware of this attempt. The administrator can still use tcp wrapper functionality, as found in hosts_access(5) and hosts.deny(5) to allow or deny discovery attempts from initiators as well as using the inbuilt netmask functionality. FILES
/etc/iscsi/targets the list of exported storage targets SEE ALSO
syslog(3), hosts.deny(5), hosts_access(5), iscsi-target(8) HISTORY
The targets file first appeared in NetBSD 4.0. BSD
December 18, 2007 BSD
All times are GMT -4. The time now is 04:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy