You can use the NETCONF/YANG interface to fulfill customer requests.
To enable Status Information, Alarm Information, and Event Information, configure the NETCONF server on the controller using
this command.
netconf-yang
Note
|
The Cisco Catalyst 9800 wireless controller supports only RSA keys for the trustpoint used by the ncsshd process. EC keys
are not supported; using them causes the ncsshd process to crash and prevents you from using NETCONF.
|
The netconf-yang command enables notifications, configuration access, and operation access (OAM) through NETCONF/YANG. For details about the
NETCONF/YANG, refer to the NETCONF Protocol chapter of the Programmability Configuration Guide at https://www.cisco.com/c/en/us/support/ios-nx-os-software/ios-xe-17/products-installation-and-configuration-guides-list.html
For the Status Information Received Synchronously type, NETCONF exports these items:
All the data for the items listed above is already available as the controller operational data exported through NETCONF.
The examples below explain where the data items listed are available.
This command is used in the controller:
wireless tag site village_name_1The site tags can be retrieved by NETCONF using the get-config operation.
Example output for Name of the Village:
<site-cfg-data xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-wireless-site-cfg">
[...]
<site-tag-configs>
<site-tag-config>
<site-tag-name>village_name_1</site-tag-name>
<description>custom user site tag for a village</description>
</site-tag-config>
[...]
</site-tag-configs>
The operational data for the controller lists all connected (joined) APs and their corresponding site tags. Each output entry
includes detailed information about the access point and its site tag. The relevant fields and controller show commands are
presented here:
Example output of AP per Village:
<data>
<access-point-oper-data xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-wireless-access-point-oper">
[...]
<radio-oper-data>
<wtp-mac>00:1b:0c:00:02:00</wtp-mac> #show ap dot11 {24ghz|5ghz} summary "MAC Address"
<radio-slot-id>0</radio-slot-id> #show ap dot11 {24ghz|5ghz} summary "Slot"
<ap-mac>00:1b:0c:00:02:00</ap-mac>
<slot-id>0</slot-id>
<radio-type>1</radio-type> # 1 - 2.4GHz, 2 - 5GHz
<admin-state>enabled</admin-state> #show ap dot11 {24ghz|5ghz} summary "Admin State"
<oper-state>radio-up</oper-state> #show ap dot11 {24ghz|5ghz} summary "Oper State"
[...]
[...]
<capwap-data>
<wtp-mac>00:1b:0c:00:02:00</wtp-mac> #show ap summary "Radio MAC"
<ap-operation-state>registered</ap-operation-state> #show ap summary "State"
<ip-addr>10.102.140.10</ip-addr> #show ap summary "IP Address"
[...]
<admin-state>1</admin-state> #show ap status "Status", 1 - Enabled, 2 - Disabled
<location>default-location </location> #show ap summary "Location"
<country-code>CH </country-code>
<name>AP_A-1</name> #show ap summary "AP Name"
[...]
<tag-info>
[...]
<site-tag>
<site-tag-name>village_name_1</site-tag-name> #show ap name AP_A-1 config general "Site Tag Name"
[...]
</site-tag>
[...]
The operational data of the controller contains information about all connected wireless clients. This includes detailed device-related
information, such as MAC address, IP address, state, and access point name.
Example output of the Number of clients currently online and logged in each village and each AP:
<data>
<client-oper-data xmlns="http://cisco.com/ns/yang/Cisco-IOS-XE-wireless-client-oper">
<common-oper-data>
<client-mac>00:00:1a:04:00:02</client-mac> #show wireless client summary "MAC Address"
<ap-name>AP_A-1</ap-name> #show wireless client summary "AP Name"
[...]
<co-state>client-status-run</co-state> #show wireless client summary "State"
Feedback