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.
In my 64 bit machine, I am hitting error while installing ydk on a pyats environment. Any help is highly appreciated. Pasting the error below,
(pyats) jkalaise@access-ops-lnx /auto/tftp-access-ops/mgbl/pyats/ydk-gen/gen-api/python/ydk/dist...
Hi community, I have one question regarding the two provisioning methods available.I want to develop an automated staging solution. Configs are generated in advanced andneed to be transferred to new devices along with a new OS (if needed).What techno...
I am trying to generate models from yang file using ydk-go.
Below error seeing
Traceback (most recent call last):
File "./generate.py", line 495, in <module>
output_directory = (generator.generate(option...