We've been asked why the data/Alarms and data/Events API resources return deviceName in unexpected format.
Instead of device name the value may contain name of the device, IP address, and MAC address.
The problem is that the attribute has inaccurate description; instead of device name the returned value contains the failure source. When an alarm or event is generated, it includes information about the source of the failure. Information is presented using a specific format. For example, performance failures use the format MACAddress:SlotID. Failure sources for other alarms may include the host name, IP address, or other properties.
Failure source format is configurable and may differ for each event category. You can adjust the properties and separators (a colon, dash, or number sign) that are displayed in the alarm's failure source using the following procedure:
Choose Administration > Settings > System Settings, then choose Alarms and Events > Alarms and Events.
In the Failure Source Pattern area, select the alarm category you want to customize.
Adjust the failure source format
To apply your changes, click Save at the bottom of the Alarms and Events settings window.
Starting capture on rx of the second one of dual ports, with -v(verbose - prints to console) or -p(links to wireshark) flags. And it doesnt captures mpls packets. Tried this commands:capture monitor start --rx 1 -vcapture monitor start --rx 1 -pcapt...
I want to call client details such as username, IP, MAC from DNAC controlled switches via API. I am running Version 184.108.40.206.I get an auth token by supplying login credentials via Basic Auth. Then i call /api/v1/host to get a list of all endpoints (i know ...
Hello folks! i am a newbie to python scripting and making rest calls to DNA Center. but i have a task i would like to complete using this new found skill. i would like to pull interface data to determine if a interface has been inac...
Hi All, I have a question about the best way to setup RSTP on a typical Cisco Switch (Typically we use an SG350 managed switch). I Also have a question regarding how RSTP should normally work as we have had some issues with a product crashing the net...
I'm having an issues running traffic out of the specified ports in the configuration yaml file. I am trying to run out of the interfaces as such:
cisco@sre-ubjh2:/opt/trex/v2.91$ cat /etc/trex_cfg_mac.yaml ### Config file generated by dpdk_setup_por...