Failure and Event Logging
Dell Networking systems provide multiple options for logging failures and events.
Trace Log
Developers interlace messages with software code to track the execution of a program.
These messages are called trace messages and are primarily used for debugging and to provide lower-level information then event
messages, which system administrators primarily use. Dell Networking OS retains executed trace messages for hardware and software and
stores them in files (logs) on the internal flash.
•
NV Trace Log
— contains line card bootup trace messages that Dell Networking OS never overwrites and is stored in internal flash
under the directory NVTRACE_LOG_DIR.
•
Trace Log
— contains trace messages related to software and hardware events, state, and errors. Trace Logs are stored in internal
flash under the directory TRACE_LOG_DIR.
•
Crash Log
— contains trace messages related to IPC and IRC timeouts and task crashes on line cards and is stored under the directory
CRASH_LOG_DIR.
For more information about trace logs and configuration options, refer to
S-Series Debugging and Diagnostics
.
Core Dumps
A core dump is the contents of RAM a program uses at the time of a software exception and is used to identify the cause of the exception.
There are two types of core dumps: application and kernel.
•
Application core dump is the contents of the memory allocated to a failed application at the time of an exception.
•
Kernel core dump is the central component of an operating system that manages system processors and memory allocation and makes
these facilities available to applications. A kernel core dump is the contents of the memory in use by the kernel at the time of an
exception.
System Log
Event messages provide system administrators diagnostics and auditing information.
Dell Networking OS sends event messages to the internal buffer, all terminal lines, the console, and optionally to a syslog server. For more
information about event messages and configurable options, refer to
.
Hot-Lock Behavior
Dell Networking OS hot-lock features allow you to append and delete their corresponding content addressable memory (CAM) entries
dynamically without disrupting traffic. Existing entries are simply shuffled to accommodate new entries.
Hot-Lock IP ACLs allows you to append rules to and delete rules from an access control list (ACL) that is already written to CAM. This
behavior is enabled by default and is available for both standard and extended ACLs on ingress and egress. For information about
configuring ACLs, refer to
292
High Availability (HA)
Содержание S3048-ON
Страница 1: ...Dell Configuration Guide for the S3048 ON System 9 11 2 5 ...
Страница 137: ...0 Gi 1 1 Gi 1 2 rx Flow N A N A 0 0 No N A N A yes Access Control Lists ACLs 137 ...
Страница 142: ...Figure 10 BFD Three Way Handshake State Changes 142 Bidirectional Forwarding Detection BFD ...
Страница 241: ...Dell Control Plane Policing CoPP 241 ...
Страница 287: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 287 ...
Страница 428: ...Figure 53 Inspecting the LAG Configuration 428 Link Aggregation Control Protocol LACP ...
Страница 429: ...Figure 54 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 429 ...
Страница 432: ...Figure 56 Inspecting a LAG Port on BRAVO Using the show interface Command 432 Link Aggregation Control Protocol LACP ...
Страница 433: ...Figure 57 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 433 ...
Страница 477: ...Figure 73 Configuring Interfaces for MSDP Multicast Source Discovery Protocol MSDP 477 ...
Страница 478: ...Figure 74 Configuring OSPF and BGP for MSDP 478 Multicast Source Discovery Protocol MSDP ...
Страница 479: ...Figure 75 Configuring PIM in Multiple Routing Domains Multicast Source Discovery Protocol MSDP 479 ...
Страница 483: ...Figure 77 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 483 ...
Страница 484: ...Figure 78 MSDP Default Peer Scenario 3 484 Multicast Source Discovery Protocol MSDP ...
Страница 634: ...protocol spanning tree pvst no disable vlan 300 bridge priority 4096 634 Per VLAN Spanning Tree Plus PVST ...
Страница 745: ...Figure 104 Single and Double Tag TPID Match Service Provider Bridging 745 ...
Страница 746: ...Figure 105 Single and Double Tag First byte TPID Match 746 Service Provider Bridging ...