Configuration Fundamentals
In this section:
- Management port overviewThe management port is an out-of-band (OOB) port that customers can use to manage their devices without interfering with the in-band ports. The management port is widely used to download images and configurations, for Telnet sessions and for Web management.
- Consideration for Accessing Factory Default Device
- Web Management Interface
- Automation with Ansible
- Management VRFsVirtual routing and forwarding (VRF) allows routers to maintain multiple routing tables and forwarding tables on the same router. A management VRF can be configured to control the flow of management traffic as described in this section.
- Additional OOB management configuration options
- System clock
- Basic System Parameter Configuration
- Displaying and modifying system parameter default settings
- Forwarding Profiles
- Basic port parameter configuration
- Replacing a primary IPv4 address automatically
- Ethernet loopbackThe Ethernet loopback functionality provides a means to gauge the network continuity and performance of an Ethernet port.
- Disabling the automatic learning of MAC addresses
- Changing the MAC age time and disabling MAC address learning
- Clearing MAC address entries
- Defining MAC address filters
- Monitoring MAC address movement
- Overview of Breakout Ports
- Configuring the CLI Banner
- Automatic execution of commands in batchesThe batch and execute functionality provides two separate but mutually inclusive features that help to automate execution of a group of CLI commands in batches at a scheduled time, count, and interval.
- CLI command historyCLI commands executed on the device from any console, Telnet, or SSH sessions are stored in the warm memory.
- Displaying a console message when an incoming Telnet session is detected
- Cut-through switching
- Jumbo frame support
- Wake-on-LAN support across VLANsWake-on-LAN (WOL) is an industry standard technology that allows you to turn on dormant PCs (WOL client) remotely.
- Terminal loggingMany customers do not have a console port connected to the units and therefore cannot monitor any debug or error messages that are shown on the console. For example, in a stacking environment where the console and management port is connected only to an active unit, the user cannot access or monitor any debug or error messages generated on the system from the member units, standby units, or PE units.
- Log Manager The Log Manager infrastructure provides the capability to log the application log files in a centralized repository. The centralized repository can be accessed for viewing the log files (to aid in taking appropriate troubleshooting actions). By default, all logs are enabled and the log files are categorized based on module, sub-module, and severity levels. Each entry in a log file has important information, including module, sub-module, severity level, unit number, and timestamp.