Displays VLAN and VxLAN information
| URI | Description |
|---|---|
| <base_URI>/operational-state/cluster-member-vlan-state | Displays VLAN and VxLAN 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-vlan-state GET operation.
http://host:80/rest/operational-state/cluster-member-vlan-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-vlan-state
<data xmlns="http://brocade.com/ns/rest" xmlns:y="http://brocade.com/ns/rest" y:self="/rest/operational-state">
<cluster-member-vlan-state xmlns="urn:brocade.com:mgmt:brocade-mct-operational" y:self="/rest/operational-state/
cluster-member-vlan-state">
<num-vlans>61</num-vlans>
<vlan-vxlan-info y:self="/rest/operational-state/cluster-member-vlan-state/vlan-vxlan-info/1">
<vlan-id>1</vlan-id>
<vni>1</vni>
<fw-state>true</fw-state>
</vlan-vxlan-info>
<vlan-vxlan-info y:self="/rest/operational-state/cluster-member-vlan-state/vlan-vxlan-info/456">
<vlan-id>456</vlan-id>
<vni>456</vni>
<fw-state>true</fw-state>
</vlan-vxlan-info>
<vlan-vxlan-info y:self="/rest/operational-state/cluster-member-vlan-state/vlan-vxlan-info/471">
<vlan-id>471</vlan-id>
<vni>471</vni>
<fw-state>true</fw-state>
</vlan-vxlan-info>
<vlan-vxlan-info y:self="/rest/operational-state/cluster-member-vlan-state/vlan-vxlan-info/472">
<vlan-id>472</vlan-id>
<vni>472</vni>
<fw-state>true</fw-state>
</vlan-vxlan-info>
<vlan-vxlan-info y:self="/rest/operational-state/cluster-member-vlan-state/vlan-vxlan-info/473">
<vlan-id>473</vlan-id>
<vni>473</vni>
<fw-state>true</fw-state>
</vlan-vxlan-info>
<vlan-vxlan-info y:self="/rest/operational-state/cluster-member-vlan-state/vlan-vxlan-info/474">
<vlan-id>474</vlan-id>
<vni>474</vni>
<fw-state>true</fw-state>
</vlan-vxlan-info>
<vlan-vxlan-info y:self="/rest/operational-state/cluster-member-vlan-state/vlan-vxlan-info/475">
<vlan-id>475</vlan-id>
<vni>475</vni>
<fw-state>true</fw-state>
</vlan-vxlan-info>
<vlan-vxlan-info y:self="/rest/operational-state/cluster-member-vlan-state/vlan-vxlan-info/3100">
<vlan-id>3100</vlan-id>
<vni>3100</vni>
<fw-state>true</fw-state>
</vlan-vxlan-info>
<vlan-vxlan-info y:self="/rest/operational-state/cluster-member-vlan-state/vlan-vxlan-info/3101">
<vlan-id>3101</vlan-id>
<vni>3101</vni>
<fw-state>true</fw-state>
</vlan-vxlan-info>
<vlan-vxlan-info y:self="/rest/operational-state/cluster-member-vlan-state/vlan-vxlan-info/3102">
<vlan-id>3102</vlan-id>
<vni>3102</vni>
<fw-state>true</fw-state>
</vlan-vxlan-info>
<vlan-vxlan-info y:self="/rest/operational-state/cluster-member-vlan-state/vlan-vxlan-info/3103">
<vlan-id>3103</vlan-id>
<vni>3103</vni>
<fw-state>true</fw-state>
</vlan-vxlan-info>
<vlan-vxlan-info y:self="/rest/operational-state/cluster-member-vlan-state/vlan-vxlan-info/3104">
<vlan-id>3104</vlan-id>
<vni>3104</vni>
<fw-state>true</fw-state>
</vlan-vxlan-info>
...
</cluster-member-vlan-state>
</data>
| Release version | History |
|---|---|
| 18r.2.00 | This API call was introduced. |