Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 252940

iSCSI Discovery

$
0
0

Hi.

 

I am wondering if it is possible to avoid iSCSI target autodiscovery.

 

I have two NICs (iSCSI Dependent NICs) configured as iSCSI initiators.

The NICs were manually configured with two targets in static discovery each:

 

NIC1 Subnet A >> Controller A Port1 Subnet A

NIC1 Subnet A >> Controller B Port1 Subnet A

NIC2 Subnet B >> Controller A Port1 Subnet B

NIC2 Subnet B >> Controller B Port1 Subnet B

 

Pretty straightforward for everyone who has done this before.

Everything works fine, but I since each controller has two IP Addresses, the IP addresses for the the wrong subnets show up in the target list automatically.

For example, a short while after configuring the static targets has above, NIC1 will have this config:

 

NIC1 Subnet A >> Controller A Port1 Subnet A

NIC1 Subnet A >> Controller A Port2 Subnet B (this will result in a login error)

NIC1 Subnet A >> Controller B Port1 Subnet A

NIC1 Subnet A >> Controller B Port2 Subnet B (this will result in a login error)

 

I thought that by configuring static discovery instead of dynamic, the system would not add the remaing portals automatically, but is does.

The end result is not dramatic, but it's still anoying to see the 4 iSCSI login errors everytime we run a rescan.

 

Thanks, PDA.


Viewing all articles
Browse latest Browse all 252940

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>