Cisco Wireless Controller Configuration Guide, Release 8.0 - Initial Setup [Cisco Wireless LAN Controller Software] When you boot up a controller that does not have a configuration, the AutoInstall feature can download a configuration file from a TFTP server and then load the configuration onto the controller automatically.
If you create a configuration file on a controller that is already on the network (or through a Prime Infrastructure filter), place that configuration file on a TFTP server, and configure a DHCP server so that a new controller can get an IP address and TFTP server information, the AutoInstall feature can obtain the configuration file for the new controller automatically. When the controller boots, the AutoInstall process starts. The controller does not take any action until AutoInstall is notified that the configuration wizard has started.
If the wizard has not started, the controller has a valid configuration. Would you like to terminate autoinstall? When the 30-second abort timeout expires, AutoInstall starts the DHCP client. DHCP OPTION 43 for Lightweight Cisco Aironet Access Points Configuration Example. Introduction This document describes how to use DHCP Option 43 and provides sample configurations for DHCP Option 43 for lightweight Cisco Aironet access points (LAPs) for these DHCP servers: Microsoft Windows 2008 Enterprise DHCP ServerCisco IOS® DHCP ServerLinux Internet Systems Consortium (ISC) DHCP ServerCisco Network Registrar DHCP ServerLucent QIP DHCP Server When a Cisco Wireless Unified architecture is deployed, the LAPs can use a vendor-specific DHCP Option 43 to join specific Wireless LAN Controllers (WLCs) when the WLC is in a different subnet than the LAP.
Refer to Wireless LAN Controller and Lightweight Access Point Basic Configuration Example and Lightweight AP (LAP) Registration to a Wireless LAN Controller (WLC) for information on how to configure an access point (AP) to join a WLC. Prerequisites Requirements Cisco recommends that you have knowledge of these topics: Basic knowledge on Cisco Unified Wireles Network (CUWN)Basic knowledge of DHCP Components Used Configure Verify.
Guide c07 728315 (2) IP Addressing: NHRP Configuration Guide - Configuring NHRP [Cisco Cloud Services Router 1000V Series] The developmental phases described in this section are actually DMVPN phases combining mGRE plus NHRP and IPsec.
Phase 2 is important because it provides the functionality needed to support dynamic spoke-to-spoke tunnels. Phase 1 is the hub-and-spoke capability only. This phase will not be discussed here because phase 1 does not support spoke-to-spoke tunnels. Phase 2 adds spoke-to-spoke capability. NHRP gathers the information that it needs to build spoke-to-spoke tunnels by using NHRP resolution request and reply packets that are sent via the spoke-hub-spoke path through the NBMA network. OTV. CCIE in 3 months - Is it possible?: EVC : Flexible Service Mapping. After 2 months of intense network re-designing (mixed with a little bit of vacation days) and following my two previous posts about Flexible Frame Matching and Flexible VLAN Tag Rewrite, i finally found some free time to write a post about the third step in configuring service instances using the EVC framework : Flexible Service Mapping.
Probably the biggest advantage of the EVC framework is the ability to support multiple services per physical port. This means that under a single physical port you can have any of the following mixed together : - 802.1q trunk- 802.1q tunnel- Local connect- Scalable EoMPLS (EoMPLS xconnect)- Multipoint Bridging (L2 bridging)- Multipoint Bridging (VPLS, SVI-based EoMPLS)- L3 termination Besides all of the above, by using the EVC framework you can combine multiple different services from different physical ports, i.e. when using multipoint bridging (aka bridge-domains), in order to put them into the same virtual circuit. Configuring Bridge Domain Interfaces. Bridge domain interface is a logical interface that allows bidirectional flow of traffic between a Layer 2 bridged network and a Layer 3 routed network traffic.
Bridge domain interfaces are identified by the same index as the bridge domain. Each bridge domain represents a Layer 2 broadcast domain. Only one bridge domain interface can be associated with a bridge domain. Bridge domain interface supports the following features: IP termination Layer 3 VPN termination Address Resolution Protocol (ARP), G-ARP, and P-ARP handling MAC address assignment Prior to configuring a bridge domain interface, you must understand the following concepts: Ethernet Virtual Circuit Overview Bridge Domain Interface Encapsulation Assigning a MAC Address Support for IP Protocols Support for IP Forwarding Packet Forwarding Bridge Domain Interface Statistics Ethernet Virtual Circuit Overview An incoming frame can be classified as service instance based on the following criteria: