Iscsi Discovery no Portal found Post: 302870153

8 More Discussions You Might Find Interesting

1. Solaris

disk discovery

when I "ls /dev/dsk/ ", I can see c0t0d0 and c0t2d0; but when I use format command, I can only see c0t0d0 available; why this happens? how many disk do I have on the machine? (I do not know that)

2. Shell Programming and Scripting

I am trying to make a bash script to scan subnets to see what hosts are available. Is it correct that you can not make the ping command time out less than a second? The script below works, but can take up to 255 seconds which is a bit long :( Is there a way to solve this using bash only? <code>...

3. UNIX for Advanced & Expert Users

portal development

i am trying to develop a portal kind of thing where all the scripts will reside in unix.in our company we areusing Solaris.My requirement is to develop a portal which can be accessed from any where inside the oragnisation.If some one types a address 3.256.63.56/xxx.html the page should open.There...

4. UNIX for Dummies Questions & Answers

How to change ethernet cable of iscsi initiator (iscsi client)?

how to change ethernet cable of iscsi initiator (iscsi client)

5. UNIX for Dummies Questions & Answers

Network Topology Discovery

Hello All! New Unix admin here, with a bit of a problem I can't seem to get a straight answer to.. I've been tasked with mapping out the topology (with IPs/Hostnames) of networks...remotely. So, I have SSH access to firewalls, but that's about as far as I can get - how would I go about...

6. AIX

Discovery LPAR from HMC

Hi All, i would like to know if it's possible to know all the IP Addresses of all LPAR's interfaces from HMC (without connect into LPAR). And if i can know also the "Application" hostname of LPAR from HMC. Thanks in advance. Bye Mario

7. AIX

Discovery/Mount new disk

Hi all, i must add a new disk on a LPAR. I've done all the HMC and VIOS Procedure to create a virtual host with disk and assign it to lpar. I don't remember how i must do on the lpar to see this disk. (i use lvm not veritas). Thanks in advance and sorry for my english. Bye Mario

8. Infrastructure Monitoring

Discovery Tools.

Hi Folks, realise that this forum might not be the exact match for this question, so feel free to put it somewhere more apropriate. I'm currently involved in a project that has gone somewhat pear shaped, just to keep this all short the situation is as follows. I was brought in to manage a...

LEARN ABOUT SUSE

ocf_heartbeat_iscsi

OCF_HEARTBEAT_ISCSI(7)						OCF resource agents					    OCF_HEARTBEAT_ISCSI(7)

NAME

       ocf_heartbeat_iscsi - Manages a local iSCSI initiator and its connections to iSCSI targets

SYNOPSIS

       iscsi [start | stop | status | monitor | validate-all | methods | meta-data]

DESCRIPTION

       OCF Resource Agent for iSCSI. Add (start) or remove (stop) iSCSI targets.

SUPPORTED PARAMETERS

       portal
	   The iSCSI portal address in the form: {ip_address|hostname}[":"port] (required, string, no default)

       target
	   The iSCSI target IQN. (required, string, no default)

       discovery_type
	   Target discovery type. Check the open-iscsi documentation for supported discovery types. (optional, string, default sendtargets)

       iscsiadm
	   open-iscsi administration utility binary. (optional, string, default iscsiadm)

       udev
	   If the next resource depends on the udev creating a device then we wait until it is finished. On a normally loaded host this should be
	   done quickly, but you may be unlucky. If you are not using udev set this to "no", otherwise we will spin in a loop until a timeout
	   occurs. (optional, string, default yes)

SUPPORTED ACTIONS

       This resource agent supports the following actions (operations):

       start
	   Starts the resource. Suggested minimum timeout: 120.

       stop
	   Stops the resource. Suggested minimum timeout: 120.

       status
	   Performs a status check. Suggested minimum timeout: 30.

       monitor
	   Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 120.

       validate-all
	   Performs a validation of the resource configuration. Suggested minimum timeout: 5.

       methods
	   Suggested minimum timeout: 5.

       meta-data
	   Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5.

EXAMPLE

       The following is an example configuration for a iscsi resource using the crm(8) shell:

	   primitive example_iscsi ocf:heartbeat:iscsi 
	     params 
	       portal=string 
	       target=string 
	     op monitor depth="0" timeout="30" interval="120"

SEE ALSO

       http://www.linux-ha.org/wiki/iscsi_(resource_agent)

AUTHOR

       Linux-HA contributors (see the resource agent source for information about individual authors)

resource-agents 1.0.3						    07/05/2010						    OCF_HEARTBEAT_ISCSI(7)