Network Learners

All MX security appliances feature a secondary uplink that can be used for load balancing and failover purposes. This article explains how to enable and configure a secondary uplink, load balancing between uplinks, and flow preferences for different types of traffic. Enabling and Configuring WAN 2 Some MX models (MX250, MX400, MX450, MX600) have a dedicated secondary uplink port (WAN 2). To use these ports, a cable just needs to be connected and the IP can be configured on the MX's  local status page . On all other MX models, a LAN port can be repurposed into an Internet port for use as WAN 2. To enable and configure WAN 2 on an MX without a dedicated WAN 2 port: Navigate to the MX's  local status page . Click the  Configure  tab at the top. Under Port 1, 2, or 4 (depending on the MX model), switch the  Role  to  Internet : Configure the WAN port as needed: VLAN tagging  - Assigns a VLAN tag to all traffic sent out of this port. If set to  Don't use VLAN tag

The purpose of this document is to bring together certain points about Domain Name System (DNS) use by Cisco routers. Prerequisites Requirements Readers of this document should have knowledge of these topics: Cisco IOS ®  Command Line Interface (CLI) General DNS behavior Components Used The information in this document is based on these software and hardware versions: Cisco 2500 series routers Cisco IOS software 12.2(24a) The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Conventions For more information on document conventions, refer to the  Cisco Technical Tips Conventions . Setting Up a Router to Use DNS Lookups Your router can be configured to use DNS lookups if you wish to use the  ping  or  traceroute  commands with a host

Connection Monitoring for WAN Failover Table of contents Connection Monitor Overview Connectivity Tests SD-WAN Monitoring Connection Monitor Overview When the primary uplink goes down on an MX Security Appliance, events will appear under  Network-wide >  Monitor > Event log  indicating a change in the primary uplink status. In the example below "uplink: 0" indicates that Internet 1 is being used, while "uplink: 1" indicates that Internet 2 is being used .  In Dashboard the  preferred  primary uplink can be configured, but that only matters when both are functioning. The MX will use the non-preferred uplink as the primary if it is the only one available. The MX monitors all uplinks and when it decides an uplink has no connectivity, will discontinue use of that link. Note : If the MX is using the non-preferred uplink as the primary and the preferred uplink comes back online, the MX will wait about 15 seconds before switching

Introduction This document describes the configuration of device access with Telnet or Secure Shell (SSH) across a Virtual Routing and Forwarding (VRF). Background Information In IP-based computer networks, VRF is a technology that allows multiple instances of a routing table to co-exist within the same router at the same time. Because the routing instances are independent, the same or overlapping IP addresses can be used without any conflict with each other. Network functionality is improved because network paths can be segmented without the requirement of multiple routers. VRF might be implemented in a network device by distinct routing tables known as Forwarding Information Bases (FIBs), one per routing instance. Alternatively, a network device may have the ability to configure different virtual routers, where each one has its own FIB that is not accessible to any other virtual router instance on the same device. Telnet is an application layer protocol used on the Intern