8.8.2 Packet Tracer - Compare CLI and SDN Controller Network Management

Network Management: CLI vs. Software Defined Networking

Overview of Network Configuration

• The discussion begins with a comparison between managing networks via command line interface (CLI) and using a software-defined networking (SDN) controller.

• The network topology includes three routers, switches, PCs, and a server, emphasizing the importance of understanding both management methods in practical scenarios.

Network Setup Details

• Routers are configured to use OSPF version 2; SSH access is enabled on all devices with the username "Cisco" and password "cisco123!".

• R3 serves as the DHCP server for the local area network (LAN), while R1 has no hosts connected but does have a server on its LAN.

Device Verification Process

• Users can verify connectivity by pinging devices from PCs; for example, PC4 can ping the server at IP address 192.168.101.100.

• The process involves checking various IP configurations across different devices to ensure they can communicate effectively within the network.

Accessing Devices via SSH

• To gather information about device software versions, users must manually access each device through SSH from an admin PC.

• An example command sequence is provided for accessing SWR3 switch using SSH with proper credentials and IP address.

Documenting Software Versions

• After logging into SWR3, users should execute commands to filter output related to installed software versions and document this information accurately.

• The goal is to collect software version data from all nine network devices including SWL1, SWN2, SWR1 through SWR4, R1, R2, and R3.

Continuing Documentation Across Devices

• Users are instructed to connect to additional switches like SWR4 using their respective IP addresses while maintaining consistent documentation practices.

• Each device's output should be copied into a text file for record keeping; this includes details such as device names alongside their software versions.

This structured approach ensures that key insights regarding network management techniques are captured efficiently while providing clear timestamps for reference.

SSH Configuration and Network Controller Setup

Initial SSH Access

• Establishing SSH connection to Cisco device at IP address 192.168.2.2, entering the password for access.

• Accessing switch SW1 using the IP address 192.168.1.12, logging in with username and password for configuration tasks.

Device Information Retrieval

• Copying output from SW1 to gather information on nine devices connected within the network setup before exiting all SSH sessions.

Introduction to Software Defined Networking (SDN)

• Discusses how traditional automation tools like bash scripts or SNMP have evolved with SDN, enhancing network management capabilities through tools like Pocket Racer as a simulation of an SDN controller.

• Instructions provided on accessing help content within Pocket Racer to learn about configuring devices and understanding network controllers better.

Configuring Network Controllers

• Detailed steps on adding a network controller in Packet Tracer, including placing it near SW1 and ensuring proper naming conventions are followed (e.g., PD-controller 0).

• Connection setup involves using straight-through copper cables between the controller and switches, specifying interface configurations accurately for connectivity purposes.

Gateway and Interface Settings

• Setting gateway addresses for the PD controller (192.168.101) along with subnet mask configurations to ensure proper routing within the network environment.

• Verifying server status settings in preferences to enable external access for REST APIs associated with network controllers, ensuring that they are correctly configured before proceeding further into setup processes.

Finalizing Controller Configuration

• Ensuring that server status is listening on port 58000 after enabling it; this is crucial for Python script connectivity checks later on during testing phases of the project setup.

• Instructions provided for pinging the controller's IP address from an admin PC command prompt to verify successful communication before registering a new user account via web browser interface at that IP address (192.168.101254).

Setup and Configuration of SDN Controller

Initial Setup

• The setup process begins with logging in using the username "Cisco" and password "cisco123!".

• Users can customize their login credentials as desired.

Interface Overview

• Expanding the window is recommended to view the entire interface of the SDN controller effectively.

Discovering Network Topology

• The SDN controller utilizes Cisco Discovery Protocol (CDP) to automatically discover nine network devices and five host devices within the topology.

Adding Credentials for Device Access

• To access network devices, users must add credentials through the graphical user interface by navigating to provisioning options.

• New credentials are created with username "Cisco" and password "cisco123!", leaving enable password blank, while a description like "admin credentials" is added.

Device Discovery Process

Credential Storage

• The newly created command line interface credentials are stored on the controller for future automation tasks.

Initiating Device Discovery

• Users can initiate a new discovery process by entering device names and IP addresses, such as swl1 with IP 181.68.112.

Monitoring Discovery Status

• The status of device discovery will show as 'in progress', allowing users to either wait or fast forward time in Packet Tracer.

Viewing Discovered Devices

Network Device Information

• Users can view all discovered network devices listed under CDP, confirming that nine devices have been identified.

Detailed Device Insights

• Clicking on any device's icon reveals detailed information collected during discovery, including software versions and interface counts.

Dashboard Overview

Dashboard Metrics

• Returning to the dashboard provides insights into managed network devices, showing metrics like reachability via ping and overall management percentages.

Host Connectivity Information

• The dashboard also displays details about hosts connected to various network devices, including their MAC addresses (Layer 2 info), IP addresses (Layer 3 info), and connectivity status.

Topology Visualization

Dynamic Topology Creation

• The controller dynamically generates a visual representation of the topology similar to what is seen in Packet Tracer’s main window.

Path Tracing Functionality

• Users can utilize path tracing features by entering source and destination IP addresses to analyze connectivity across the network.

Network Configuration and Automation Overview

Understanding Network Path and Device Layers

• The root report displays all hops from source to destination, highlighting that only Layer 3 device information is included. Layer 2 devices, such as switches, are not shown.

• Utilizing an SDN controller allows for the configuration of global network settings and policies across all devices with a single action.

Configuring DNS, NTP, and Syslog Services

• The example server's DNS service is enabled with one record for www.example.com, pointing to IP 181.68.101.100.

• The syslog service is also confirmed to be enabled on the example server.

• NTP (Network Time Protocol) is configured and enabled on the example server.

Setting Global Policies

• In the admin menu under policy settings, options for configuring scope and policies are available; specifically focusing on DNS settings.

• The domain name example.com is set along with its corresponding DNS server IP address 181.68.101.100.

Verifying Configuration Changes

• After saving configurations for DNS, NTP, and syslog services, it’s essential to verify that all information has been correctly saved before pushing configurations.

• A successful push of all network settings confirms that changes have been applied across devices running iOS XC operating systems.

Testing Network Settings

• Functionality limitations are noted; global settings apply only to routers running specific IOS versions.

• Accessing R1's command line interface allows verification of DNS settings using commands like show run pipe begin IP domain.

Monitoring Time Synchronization and Logging

• To ensure time synchronization via NTP, check if R1's time matches the current time; use commands like show ntp associations.

• Verify logging configuration by checking syslog server details through commands like show run include login.

Interface Management and Syslog Review

• Manage interfaces in global configuration mode by shutting down and re-enabling them to test logging functionality.

• Review logged messages in the syslog service on the example server to confirm that they match those seen in the command line interface.

This structured overview captures key insights from the transcript while providing timestamps for easy reference back to specific sections of content discussed.

OSPF Process Configuration and Status

Understanding OSPF Messages and Protocol Status

• The speaker discusses the process of double-clicking to view all messages related to the OSPF (Open Shortest Path First) protocol, indicating that it is crucial for monitoring network status.

• It is noted that when changes are made, the line protocol should remain "up," which signifies a successful configuration and operational state of the interface.

• The mention of an OSPF message being configured via console suggests a hands-on approach to managing network protocols directly through command-line interfaces.

• The phrase "very nice" implies satisfaction with the current setup or functionality, hinting at positive outcomes from recent configurations.