i can't configure "logging event spanning-tree" on a specific port under IOS 12.2.(58) SE2 (all other "logging events" are possible), under 12.2 (55) it is possible. Is it now a known bug or a default value? Regards, Sebastian I have this problem too Labels: Other Switching ...
These parent-child relationships can generate a treelike or waterfall diagram that shows the entire flow measured by a trace. Indeed,distributed tracing toolstypically display spans in a timeline or dependency graph. Each span appears as a bar, labeled with its average duration. Viewing all...
· Abrupt power failure—During testing, computers logging to Citadel databases are subjected to abrupt power loss scenarios. Citadel attempts to recover from all known corruptions that this procedure causes. However, when power is terminated unexpectedly, an unpredictable amount of data might be lost...
Date and time of the message or event. This information appears only if the service timestamps log [datetime | log] global configuration command is configured. For more information, see the "Enabling and Disabling Time Stamps on Log Messages" section. facility The facili...
Use thelogging event power-inline-statusinterface configuration command to enable and to disable logging of Power over Ethernet (PoE) events on specific PoE-capable ports. Logging on these ports is enabled by default. To disable logging to the console, use theno logging co...
The nodetree.*, pid.cdih, and stridm.cdin files contain important information about the structure of the database. The mssql.* files contain historical alarm information. Citadel creates the mssql.*files the first time alarm or event data is written to the database....
Text string containing detailed information about the event being reported. This example shows a partial switch system message: 00:00:46: %LINK-3-UPDOWN: Interface Port-channel1, changed state to up 00:00:47: %LINK-3-UPDOWN: Interface GigabitEthernet0/1, changed state t...
(also denoted as volume metadata entry446) of a dense tree444managed by that volume layer instance, and (iii) records a change to metadata of the selected hash table in the extent store layer log355. Illustratively, the volume layer instance selects dense tree444aspanning an offset range440...
(also denoted as volume metadata entry600) of a dense tree700managed by that volume layer instance, and (iii) records a change to extent metadata of the selected hash table in the extent store layer log355. Illustratively, the volume layer instance selects dense tree700aspanning an offset ...
Illustratively, the volume layer instance selects dense tree 444a spanning an offset range 440a of the volume 445 that encompasses the offset range of the write request. As noted, the volume 445 (e.g., an offset space of the volume) is partitioned into multiple regions (e.g., allotted...