Displays cluster bridge state information
URI | Description |
---|---|
<base_URI>/operational-state/cluster-member-bd-state | Displays cluster bridge state information. |
Only GET operation is supported. Use of the Resource-Depth request header is recommended.
The following example shows the complete cURL command and server response for the
cluster-member-bd-state
GET operation.
http://host:80/rest/operational-state/cluster-member-bd-state
curl -H "Accept: application/vnd.operational-state.resource+xml" -H "Resource-Depth: 6" -u "lab:Tester**" http://10.20.229.40:80/rest/operational-state/cluster-member-bd-state
<data xmlns="http://brocade.com/ns/rest" xmlns:y="http://brocade.com/ns/rest" y:self="/rest/operational-state"> <cluster-member-bd-state xmlns="urn:brocade.com:mgmt:brocade-mct-operational" y:self="/rest/operational-state/ cluster-member-bd-state"> <num-bds>1100</num-bds> <bd-vxlan-info y:self="/rest/operational-state/cluster-member-bd-state/bd-vxlan-info/700"> <bd-id>700</bd-id> <vni>4796</vni> <fw-state>true</fw-state> </bd-vxlan-info> <bd-vxlan-info y:self="/rest/operational-state/cluster-member-bd-state/bd-vxlan-info/701"> <bd-id>701</bd-id> <vni>4797</vni> <fw-state>true</fw-state> </bd-vxlan-info> <bd-vxlan-info y:self="/rest/operational-state/cluster-member-bd-state/bd-vxlan-info/702"> <bd-id>702</bd-id> <vni>4798</vni> <fw-state>true</fw-state> </bd-vxlan-info> <bd-vxlan-info y:self="/rest/operational-state/cluster-member-bd-state/bd-vxlan-info/703"> <bd-id>703</bd-id> <vni>4799</vni> <fw-state>true</fw-state> </bd-vxlan-info> <bd-vxlan-info y:self="/rest/operational-state/cluster-member-bd-state/bd-vxlan-info/704"> <bd-id>704</bd-id> <vni>4800</vni> <fw-state>true</fw-state> </bd-vxlan-info> <bd-vxlan-info y:self="/rest/operational-state/cluster-member-bd-state/bd-vxlan-info/705"> <bd-id>705</bd-id> <vni>4801</vni> <fw-state>true</fw-state> </bd-vxlan-info> <bd-vxlan-info y:self="/rest/operational-state/cluster-member-bd-state/bd-vxlan-info/706"> <bd-id>706</bd-id> <vni>4802</vni> <fw-state>true</fw-state> </bd-vxlan-info> <bd-vxlan-info y:self="/rest/operational-state/cluster-member-bd-state/bd-vxlan-info/707"> <bd-id>707</bd-id> <vni>4803</vni> <fw-state>true</fw-state> </bd-vxlan-info> <bd-vxlan-info y:self="/rest/operational-state/cluster-member-bd-state/bd-vxlan-info/708"> <bd-id>708</bd-id> <vni>4804</vni> <fw-state>true</fw-state> </bd-vxlan-info> <bd-vxlan-info y:self="/rest/operational-state/cluster-member-bd-state/bd-vxlan-info/709"> <bd-id>709</bd-id> <vni>4805</vni> <fw-state>true</fw-state> </bd-vxlan-info> <bd-vxlan-info y:self="/rest/operational-state/cluster-member-bd-state/bd-vxlan-info/710"> <bd-id>710</bd-id> <vni>4806</vni> <fw-state>true</fw-state> </bd-vxlan-info> <bd-vxlan-info y:self="/rest/operational-state/cluster-member-bd-state/bd-vxlan-info/711"> <bd-id>711</bd-id> <vni>4807</vni> <fw-state>true</fw-state> </bd-vxlan-info> <bd-vxlan-info y:self="/rest/operational-state/cluster-member-bd-state/bd-vxlan-info/712"> <bd-id>712</bd-id> <vni>4808</vni> <fw-state>true</fw-state> </bd-vxlan-info> ... </cluster-member-bd-state> </data>
Release version | History |
---|---|
18r.2.00 | This API call was introduced. |