Tony Asleson
2014-05-16 20:41:04 UTC
Hi Gris,
I'm trying to figure out how we can get the following information
exposed in our library.
* User wants to know what type of transports are available( FC, iSCSI,
etc.)
* User wants to know the specifics of each transport(s)
- what the WWPNs are of each of the FC ports
- what the IP address(es), port number(s) and IQNs for iSCSI
Basically the information that the initiator side would find useful when
getting connected to the target side.
Looking at the the block services book, the target port subprofile seems
promising, and I am finding some of what I seek. For example I have
found port numbers and IQN's, but I haven't found out what IP addresses
they are served up on.
Can you help take a look at this? I know your SMI-S knowledge has
surpassed mine, especially with your work on pools and interop support.
Thanks,
Tony
I'm trying to figure out how we can get the following information
exposed in our library.
* User wants to know what type of transports are available( FC, iSCSI,
etc.)
* User wants to know the specifics of each transport(s)
- what the WWPNs are of each of the FC ports
- what the IP address(es), port number(s) and IQNs for iSCSI
Basically the information that the initiator side would find useful when
getting connected to the target side.
Looking at the the block services book, the target port subprofile seems
promising, and I am finding some of what I seek. For example I have
found port numbers and IQN's, but I haven't found out what IP addresses
they are served up on.
Can you help take a look at this? I know your SMI-S knowledge has
surpassed mine, especially with your work on pools and interop support.
Thanks,
Tony