VMware Cloud Community
RoscoT
Enthusiast
Enthusiast
Jump to solution

das.isolationaddress question

Hello all,

Just a quick question regarding the use of das.isolationaddress.

If I have two management traffic networks for an ESXi host then the advice is to have one isolation address for each.

Let's say I normally communicate with the host using 192.168.11.51 and the gateway 192.168.11.1 is pingable.

The second management traffic network has a host address of 192.168.22.51 and once again the gateway 192.168.22.1 is pingable.

Would I simply add these advanced settings:

das.isolationaddress0 = 192.168.22.1

das.usedefaultisolationaddress = true

Or in the above example would I need to use das.isolationaddress1 instead of das.isolationaddress0.

Or would it be best to use the following:

das.usedefaultisolationaddress = false

das.isolationaddress0 = 192.168.11.1

das.isolationaddress1 = 192.168.22.1

TIA

Reply
0 Kudos
1 Solution

Accepted Solutions
Sreejesh_D
Virtuoso
Virtuoso
Jump to solution

the second option would be the right choice.

das.usedefaultisolationaddress = false

das.isolationaddress0 = 192.168.11.1

das.isolationaddress1 = 192.168.22.1

Ref: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100211...

View solution in original post

Reply
0 Kudos
5 Replies
Sreejesh_D
Virtuoso
Virtuoso
Jump to solution

the second option would be the right choice.

das.usedefaultisolationaddress = false

das.isolationaddress0 = 192.168.11.1

das.isolationaddress1 = 192.168.22.1

Ref: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100211...

Reply
0 Kudos
RoscoT
Enthusiast
Enthusiast
Jump to solution

Great. Thanks for the response and the link.

Reply
0 Kudos
depping
Leadership
Leadership
Jump to solution

That is not right Yezdi..

You  don't need to set "das.usedefaultisolationaddress" when your gateway is  pingable. Just define the additional address. This is the only thing  you should do:

das.isolationaddress0 = 192.168.22.1

Also wrote an article on this a while ago:

http://www.yellow-bricks.com/2012/05/25/use-dasisolationaddressx/

Sreejesh_D
Virtuoso
Virtuoso
Jump to solution

Im sorry roscot for the wrong information provided and thank you very much Duncan for correcting it.

And thanks for sharing your article, its simply awesome. Clearly explains the need of following advance options. Thank you.

das.usedefaultisolationaddress

das.isolationaddresX

Reply
0 Kudos
RoscoT
Enthusiast
Enthusiast
Jump to solution

Thanks Duncan for the clarification.

The link provided by Yezdi (http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100211...) has an error in it where it says, with respect to das.usedefaultisolationaddress, that "You must set this option if you are setting multiple isolation response addresses."

Your document indicates that you could keep adding das.isolationaddressX values without the need to set das.usedefaultisolationaddress to false so long as the default gateway is pingable. Having read your book and knowing the knowledge that you have in this area I'll go with your analysis! 🙂

Cheers.

Reply
0 Kudos