Application Integration
cancel
Showing results for 
Search instead for 
Did you mean: 

Nimble REST API: Get info about iSCSI and FC settings

SOLVED
Go to solution
mijn7
Occasional Contributor

Nimble REST API: Get info about iSCSI and FC settings

How I can get information about FC and iSCSI adapters on Nimble strorage by REST API?

In UI this settings are accessible in Administration->Network Configuration.

I'am interesrted in WWNN and WWPN for each FC adapter.

Nimble_FC_Empty.png

and IP address for iSCSI data traffic.

Nimble_iSCSI_Empty.png

Thanks!

3 REPLIES
N/A

Re: Nimble REST API: Get info about iSCSI and FC settings

I have found the documentation suite for the REST API suite on InfoSight.  Proceed with your normal login, click on the upper right "cloud" icon (downloads).  Then under the "Nimble OS" tab, select release 2.3.9 and the available documents will list just below.  You will see the "API Reference".  It will download "pubs_api_reverence_2.3.zip".  The specific information you seek is under "Object Sets > initiators > Read" and you will find the details.  Note:  I do not see WWNN only WWPN.  Hope this helps.

mijn7
Occasional Contributor
Solution

Re: Nimble REST API: Get info about iSCSI and FC settings

Initiators is quite the opposite for what I want.

In documentation for this objects set:

Manage initiators in initiator groups. An initiator group has a set of initiators that can be configured as part of your ACL to access a specific volume through group membership.

So, it returns IQNs and WWNs for initiators groups that I added to Nimble f.e ESX, Windows server etc.

But I want information about Nimble adapters. IP addresses for iSCSI data and WWN for FC.

I found this informaion in Nimble Storage Command Line throught SSH.  Commands "fc --list" and "ip --list" return desired information.

Nimble OS $ fc --list

Array: helXXXX

------+-----+-------+------+----+-----------------------+-----------------------

Name   Ctrlr Admin   Fabric Link WWNN                    WWPN

             Status

------+-----+-------+------+----+-----------------------+-----------------------

fc1.1  A     online  yes    8G   56:c9:ce:90:XX:XX:XX:XX 56:c9:ce:90:XX:XX:XX:XX

fc2.1  A     online  no     -    56:c9:ce:90:XX:XX:XX:XX 56:c9:ce:90:XX:XX:XX:XX

fc1.1  B     online  yes    8G   56:c9:ce:90:XX:XX:XX:XX 56:c9:ce:90:XX:XX:XX:XX

fc2.1  B     online  no     -    56:c9:ce:90:XX:XX:XX:XX 56:c9:ce:90:XX:XX:XX:XX

Nimble OS $ ip --list

---------------+---------+------+----------+---------------+--------------------

IP Address      NIC       Status Type       Array           Controller

---------------+---------+------+----------+---------------+--------------------

172.XX.XX.XX   eth1      up     management HELXXX       B

172.XX.XX.XX   eth1      up     discovery  HELXXX        B

172.XX.XX.XX   eth1      up     support    HELXXX        B

172.XX.XX.XX   tg1       up     discovery  HELXXX        B

172.XX.XX.XX   tg1       up     data       HELXXX        B

172.XX.XX.XX   eth1      up     support    HELXXX        A

jcates98
Trusted Contributor

Re: Re: Nimble REST API: Get info about iSCSI and FC settings

There was no API access to this information in NimbleOS 2.3, however it has been added in NimbleOS 3.  See the API reference for full detail, but for the Fibre Channel target, you could use the new fibre_channel_interfaces API.  In the following example, I'm using the "fields" query within the API URI itself to restrict output to just the fields I want to see:

URI: https://<MYARRAY>:5392/v1/fibre_channel_interfaces/detail?fields=controller_name,name,wwnn,wwpn,online

Response:

{

    "data":  [

                 {

                     "controller_name":  "A",

                     "name":  "fc5.1",

                     "wwnn":  "56:c9:ce:90:5d:ba:40:00",

                     "wwpn":  "56:c9:ce:90:5d:ba:40:01",

                     "online":  "true"

                 },

                 {

                     "controller_name":  "A",

                     "name":  "fc6.1",

                     "wwnn":  "56:c9:ce:90:5d:ba:40:00",

                     "wwpn":  "56:c9:ce:90:5d:ba:40:02",

                     "online":  "true"

                 },

                 {

                     "controller_name":  "B",

                     "name":  "fc5.1",

                     "wwnn":  "56:c9:ce:90:5d:ba:40:00",

                     "wwpn":  "56:c9:ce:90:5d:ba:40:03",

                     "online":  "true"

                 },

                 {

                     "controller_name":  "B",

                     "name":  "fc6.1",

                     "wwnn":  "56:c9:ce:90:5d:ba:40:00",

                     "wwpn":  "56:c9:ce:90:5d:ba:40:04",

                     "online":  "true"

                 }

             ],

    "startRow":  0,

    "endRow":  4,

    "totalRows":  4

}

For iSCSI, you can use the new subnets API.