CCNA ESSENTIALS ULTRA CHEAT SHEET

 

🧠 ✨ CCNA Ultra Cheat Sheet – Final Assault Edition ✨

IPv4 Subnetting

• Network = IP AND mask

• Broadcast = next block - 1

• Host count = 2^(host bits) - 2

• Key block sizes:

  • /30 = 4

  • /29 = 8

  • /28 = 16

  • /27 = 32

  • /26 = 64

  • /24 = 256

  • /23 = 512

---

IPv6

• GUA: 2000::/3

• LLA: FE80::/10

• ULA: FD00::/8

• EUI-64 = flip 7th bit

• NDP: RS/RA (gateway), NS/NA (MAC)

• SLAAC = no DHCPv6

---

OSPF

• Cost = ref BW / int BW (default 100 Mbps)

• DR/BDR on broadcast

• RID = highest loopback

• LSA types:

  • 1 Router

  • 2 Network

  • 3 Inter-area

  • 5 External

• Inject default: default-information originate

---

VLANs

• Access: switchport mode access

• Trunk: switchport mode trunk

• Allowed: switchport trunk allowed vlan

• Native = VLAN 1

• DTP: desirable/auto

---

STP/RSTP

• Root = lowest priority → lowest MAC

• Default priority = 32768

• RSTP states: discarding / learning / forwarding

• Port roles: root, designated, alternate

• Edge = PortFast

---

ACLs

• Standard → near destination

• Extended → near source

• Wildcards are inverse masks

• ip access-group X in/out

• Implicit deny at end

---

NAT/PAT

• PAT = overload

• Static NAT = 1:1

• Inside/outside must be marked

  • ip nat inside

  • ip nat outside

• Show translations: show ip nat translations

---

Wireless

• WPA2/3 = AES/CCMP

• Authentication: EAP-TLS (cert), PEAP (username/pass)

• Bands: 2.4 GHz = overlap

• Lightweight AP = CAPWAP

---

SDN / APIs

• REST = JSON over HTTP

• CRUD verbs: GET / POST / PUT / PATCH / DELETE

• DNA-C northbound = REST

• Resource = last noun in URL

REST, JSON and CRUD

 
Understanding REST and JSON 

REST-Based APIs

Applications use application programming interfaces (APIs) to communicate. To do so,

one program can learn the variables and data structures used by another program, making

logic choices based on those values, changing the values of those variables, creating new

variables, and deleting variables. APIs allow programs running on different computers to

work cooperatively, exchanging data to achieve some goal.

In an API software world, some applications create an API, with many other applications

using (consuming) the API. Software developers add APIs to their software so other application

software can make use of the first application’s features.

When writing an application, the developer will write some code, but often the developer

may do a lot of work by looking for APIs that can provide the data and functions, reducing

the amount of new code that must be written. As a result, much of modern software development

centers on understanding and learning new APIs, along with the available libraries

(prebuilt software that can be used to accomplish tasks rather than writing the equivalent

from scratch).

Several types of APIs exist, each with a different set of conventions to meet different needs.

The CCNA blueprint mentions one type of API—REpresentational State Transfer

(REST)—because of its popularity as a type of API in networking automation applications.

This first major section of the chapter takes a closer look at REST-based APIs.

REST-Based (RESTful) APIs

REST APIs follow a set of foundational rules about what makes a REST API and what does

not. First, from a literal perspective, REST APIs include the six attributes defined a few

decades back by its creator, Roy Fielding. (You can find a good summary at https://

restfulapi.net). Those six attributes are

 Client/server architecture

 Stateless operation

 Clear statement of cacheable/uncacheable

 Uniform interface

 Layered

 Code-on-demand

The first three of these attributes get at the heart of how a REST API works. You can more

easily see these first three features at work with networking REST APIs, so the next few

paragraphs further explain those first three points.

Client/Server Architecture

Like many applications, REST applications use a client/server architectural model. First, an

application developer creates a REST API, and that application, when executing, acts as a REST

server. Any other application can make a REST API call (the REST client) by executing some

code that causes a request to flow from the client to the server. 

1. The REST client on the left executes a REST API call, which generates a message sent

to the REST server.

2. The REST server on the right has API code that considers the request and decides how

to reply.

3. The REST server sends back the response message with the appropriate data variables.

REST & JSON (CCNA-Level)

1) REST — What You MUST Know

REST = Representational State Transfer

It’s a style of API (not a protocol) used for network automation.

REST works over:

• HTTP or HTTPS (almost always HTTPS)

REST uses standard HTTP verbs:

HTTP Verb	CRUD Action	Used For
GET	Read	Retrieve data
POST	Create	Add new data
PUT	Replace	Replace an entire object
PATCH	Modify	Partial update
DELETE	Delete	Remove data

CCNA commonly tests:
GET retrieves information.
POST creates something new.

---

2) REST Uses URLs (Endpoints)

Example endpoint:

https://dna-center/api/v1/network-device

REST endpoints point to:

• a resource

• or a collection of resources

You don’t need to memorize how DNA-C structures them.
You just need to understand the concept.

---

3) Authentication — CCNA angle

Almost always:

✔ Token-based (Bearer tokens)
✔ Provided after a login request
✔ Then included in headers for future calls

You might see:

X-Auth-Token: 9vk392kj-3829ac

---

⭐ 4) JSON (JavaScript Object Notation)

REST APIs commonly send/receive JSON.

You MUST be able to recognize a valid JSON structure.

JSON basics:

• Key-value pairs

• Keys in quotes

• Values can be strings, numbers, booleans, arrays, objects

• Commas between entries

• Entire structure wrapped in { } for an object or [ ] for a list

Example:

{
  "hostname": "SW1",
  "ip": "10.1.1.10",
  "vlans": [10, 20, 30],
  "enabled": true
}

The exam may ask:

• What type is “vlans”? → Array

• What type is “enabled”? → Boolean

• What delimiter surrounds JSON objects? → { }

---

5) JSON Array vs Object (Guaranteed Question)

Object = key-value pairs

Surrounded by curly braces:

{ "hostname": "SW1" }

Array = ordered list

Surrounded by square brackets:

[10, 20, 30]

---

⭐ 6) Describing Data Structure (Blueprint Verb: DESCRIBE)

You must understand:

• JSON = structured, machine-readable

• Human-readable

• Used for network automation

• Passed inside REST API messages

NO CLI required.

---

⭐ 7) REST vs SOAP

CCNA loves this compare:

REST	SOAP
Lightweight	Heavy
Human readable	Verbose, XML-only
JSON or XML	XML only
Uses HTTP verbs	Uses its own RPC-style calls
Modern automation	Legacy systems

REST wins for automation — that’s the exam message.

Software-Defined Networking (SDN)

 In Software-Defined Networking (SDN), the controller is responsible for coordinating the Virtual Tenant Networks (VTNs). Multi-tenancy is one of the advantageous features provided by SDN when compared to traditional networks. With multi-tenancy, multiple entities can run their services and applications separately and independently while consuming the same network infrastructure resources.

The network devices stream telemetry data to the controller. This telemetry data is analyzed by the controller or third-party application so that anomalies can be detected and so that security threats can be proactively avoided.

The northbound application programmable interface (API) is responsible for providing extensibility. The northbound API enables third-party applications to connect to the SDN controller. These applications are usually used for orchestration.

The southbound API is used by the controller to manage the network devices.

---

If you want, I can turn this into a CCNA-ready SDN summary sheet, or quiz you on these mappings.

You said:

a CCNA-ready SDN summary sheet

ChatGPT said:

Here you go, Lou — a clean, exam-ready SDN Summary Sheet, written exactly in the style Wendell Odom expects you to know for CCNA 200-301 v1.1.

No fluff. No CCNP detail. Pure CCNA-level mastery.

---

CCNA SDN Summary Sheet

(Software-Defined Networking – Exam-Level Essentials)

---

1. SDN Architectural Layers (3-Tier Model)

A. Application Layer

• Contains orchestration tools, analytics platforms, automation tools, security applications.

• Communicates downward to the controller via northbound APIs.

• Purpose: Define intent, push policies, request services.

B. Control Layer (Controller)

• The central brain of SDN.

• Maintains global network view (topology, policies, paths).

• Makes forwarding decisions (“intent → configuration”).

• Coordinates Virtual Tenant Networks (VTNs).

• Communicates:

  • Upward via northbound API

  • Downward via southbound API

C. Infrastructure Layer (Data Plane)

• Physical or virtual network devices: switches, routers, APs, firewalls.

• Forward traffic (data plane).

• Stream telemetry to the controller.

• Enforce configuration received from the controller.

---

2. SDN APIs — Know These Cold

Northbound API

• Controller → Applications (orchestration layer).

• Purpose: Extensibility.

• Common form: REST API, JSON/HTTPS.

• Enables apps to:

  • Read topology

  • Push security policies

  • Create automation workflows

  • Integrate 3rd-party platforms

Southbound API

• Controller → Network devices.

• Purpose: Deliver configuration + gather operational data.

• Examples:

  • OpenFlow (CCNA favorite term)

  • NETCONF/YANG

  • gNMI / gRPC (telemetry)

---

3. SDN Benefits (CCNA-Level Talking Points)

• Centralized control plane
  Controller holds full network intelligence.

• Automation and programmability
  Intent → configuration without touching each device.

• Consistent policy enforcement
  One central source of truth.

• Multi-tenancy
  VTNs allow separate logical networks over shared hardware.

• Real-time telemetry
  Devices stream data for:

  • Security analysis

  • Troubleshooting

  • Predictive maintenance

---

4. Key CCNA Exam Definitions

Term	CCNA Definition
SDN	Decoupling control plane from data plane; controlled by a central controller
Controller	Software platform with global view; coordinates VTNs; programs devices
Northbound API	Interface enabling applications to communicate with controller; provides extensibility
Southbound API	Interface enabling controller to send config to devices; manages network elements
Telemetry	Real-time data streamed from devices to controller
VTN (Virtual Tenant Network)	Logical network segmentation for multi-tenancy
OpenFlow	Southbound protocol used to program forwarding tables
Programmability	Ability to automate management via APIs

---

5. CCNA Exam Traps to Watch For

1. “Which API provides extensibility?”

✔ Northbound API

2. “Which component streams telemetry?”

✔ Network devices

3. “Which component orchestrates VTNs?”

✔ Controller

4. “Which component actually forwards packets?”

✔ Infrastructure layer (network devices)

5. “Which protocol is associated with SDN southbound APIs?”

✔ OpenFlow (CCNA’s favorite)

6. “Is SDN about data-plane centralization?”

❌ No.
✔ Control plane gets centralized.
✔ Data plane remains distributed.

---

6. Memorization Mini-Chart (High-Speed Recall)

SDN Flow of Intent

App → (Northbound API) → Controller → (Southbound API) → Devices → Traffic Forwarding

---

7. One-Sentence Summary for Exam Memory

“Apps talk down to the controller via northbound APIs, the controller programs devices via southbound APIs, and devices forward packets while streaming telemetry back.”

Bits, Bytes, and Hex

 

⭐ PART 1 — Bits, Nibbles, Bytes (The Foundations)

Bit

• A 0 or 1

• Smallest unit of data.

Example:
1 or 0

---

Nibble

• 4 bits

• Can represent values 0–15 decimal

• Hex digit maps perfectly to a nibble, which is why hex exists in networking.

Example:

Binary: 1010
Decimal: 10
Hex: A

---

Byte

• 8 bits = 2 nibbles

• Can represent 0–255 decimal

Example:

Binary:   11001100
Nibbles:  1100 1100
Hex:      CC
Decimal:  204

---

⭐ PART 2 — Why Networking Loves Hex

Hex is just a human-friendly way to write binary.

• 1 hex digit = 4 bits

• 2 hex digits = 1 byte (8 bits)

This makes it ideal for:

• MAC addresses (48 bits)

• IPv6 addresses (128 bits)

• TCP/IP headers (lots of 16-bit and 32-bit fields)

---

⭐ PART 3 — MAC Addresses (48 bits, always hex)

A MAC address is 48 bits = 6 bytes = 12 hex digits.

Example MAC:

AA-BB-CC-11-22-33

Let’s decode the first byte:

First byte: AA

Hex	Binary
A	1010
A	1010

So AA in binary:

1010 1010

The entire MAC in binary:

AA      BB      CC      11      22      33
1010 1010 1011 1011 1100 1100 0001 0001 0010 0010 0011 0011

Important MAC-level bits:

The first byte contains two special bits:

Bit	Meaning
LSB of first byte	Unicast (0) / Multicast (1)
2nd LSB	Globally unique (0) / Locally administered (1)

Example:
AA = 10101010

• LSB = 0 → Unicast

• Next bit = 1 → Locally administered MAC

---

⭐ PART 4 — IPv4 Addresses

(32 bits = 4 bytes = 8 hex digits)

Example IPv4 address:

192.168.1.10

Break into bytes:

• 192 → 11000000 → C0

• 168 → 10101000 → A8

• 1 → 00000001 → 01

• 10 → 00001010 → 0A

IPv4 in hex:

C0 A8 01 0A

IPv4 in binary (all 32 bits):

11000000 10101000 00000001 00001010

Why useful?
This is exactly how routers see IPs in memory and packet headers.

---

⭐ PART 5 — IPv6 Addresses

(128 bits = 16 bytes = 32 hex digits)

Example IPv6:

2001:0db8:85a3:0000:0000:8a2e:0370:7334

Each group is 16 bits (2 bytes):

• 2001 in binary =
  0010 0000 0000 0001

IPv6 in full binary representation is a 128-bit monster, but hex makes it readable.

---

⭐ PART 6 — Example: IP Header Fields in Binary/Hex

Let’s decode the first 4 bytes of an IPv4 header:

Hex dump:

45 00 00 54

Breakdown:

Byte 1 — Version + IHL

45 hex = 0100 0101 binary

• Version = 0100 = 4

• IHL = 0101 = 5 × 4 bytes = 20-byte header

Byte 2 — DSCP/ECN

00 hex = 0000 0000

• DSCP = 000000

• ECN = 00

Bytes 3–4 — Total Length

00 54 hex → 0x0054 → 84 bytes

---

⭐ PART 7 — ARP Packet Example (MAC + IP in binary/hex)

Example ARP request (simplified):

Sender MAC: AA-BB-CC-11-22-33
Sender IP: 192.168.1.10

Sender IP in hex:

C0 A8 01 0A

ARP field dump (simplified):

AA BB CC 11 22 33  C0 A8 01 0A

Binary:

[48 bits MAC]        [32 bits IP]
10101010 10111011... 11000000 10101000 00000001 00001010

---

⭐ PART 8 — TCP Header Example (16-bit and 32-bit fields)

TCP Source Port: 443

• Decimal: 443

• Hex: 01BB

• Binary: 0000 0001 1011 1011

Sequence number (32 bits):
Example: 0xABCD1234 → 128-bit hex notation becomes useful.

---

⭐ PART 9 — Hex is Everywhere in Protocols

• VLAN tags: 0x8100

• EtherType fields:

  • IPv4 = 0x0800

  • IPv6 = 0x86DD

  • ARP = 0x0806

• TCP flags are individual bits inside a byte

• STP BPDUs have fields like:

  • Root Priority: 0x8000

  • Bridge ID uses MAC + priority (combination of hex + binary)

---

⭐ PART 10 — Quick Conversion Table (for your brain)

Hex → Binary

Hex	Binary
0	0000
1	0001
2	0010
3	0011
4	0100
5	0101
6	0110
7	0111
8	1000
9	1001
A	1010
B	1011
C	1100
D	1101
E	1110
F	1111

Cisco Application Centric Infrastructure (ACI)

Application Centric Infrastructure (ACI).

Interestingly, many SDN offerings began with research that discarded many of the old

networking paradigms in an attempt to create something new and better. For instance,

OpenFlow came to be from the Stanford University Clean Slate research project that had

researchers reimagining (among other things) device architectures. Cisco took a similar

research path, but Cisco’s work happened to arise from different groups, each focused on

different parts of the network: data center, campus, and WAN. That research resulted in

Cisco’s current SDN offerings of ACI in the data center: Software-Defined Access (Cisco

SD-Access) in the enterprise campus and Software-Defined WAN (Cisco SD-WAN) in the

enterprise WAN.

When reimagining networking for the data center, the designers of ACI focused on the

applications that run in a data center and what they need. As a result, they built networking

concepts around application architectures. Cisco made the network infrastructure become

application centric, hence the name of the Cisco data center SDN solution: Application

Centric Infrastructure (ACI).

For example, Cisco looked at the data center world beyond networking and saw lots of

automation and control. As discussed in Chapter 20, “Cloud Architecture,” virtualization

software routinely starts, moves, and stops VMs. Additionally, cloud software enables self service

for customers so they can enable and disable highly elastic services as implemented

with VMs and containers in a data center. From a networking perspective, some of those

VMs need to communicate, but some do not. And those VMs can move based on the needs

of the virtualization and cloud systems.

ACI set about to create data center networking with the flexibility and automation built

into the operational model. Old data center networking models with a lot of per-physical interface

configuration on switches and routers were just poor models for the rapid pace

of change and automated nature of modern data centers. This section looks at some of the

detail of ACI to give you a sense of how ACI creates a powerful and flexible network to

support a modern data center in which VMs and containers are created, run, move, and are

stopped dynamically as a matter of routine.

ACI Physical Design: Spine and Leaf

The Cisco ACI uses a specific physical switch topology called spine and leaf. While the

other parts of a network might need to allow for many different physical topologies, the data

center could be made standard and consistent. But what particular standard and consistent

topology? Cisco decided on the spine and leaf design, also called a Clos network after one

of its creators.

With ACI, the physical network has a number of spine switches and a number of leaf

switches, as shown in Figure 21-9. The figure shows the links between switches, which can

be single links or multiple parallel links. Of note in this design (assuming a single-site design):

 Each leaf switch must connect to every spine switch.

 Each spine switch must connect to every leaf switch.

 Leaf switches cannot connect to each other.

 Spine switches cannot connect to each other.

 Endpoints connect only to the leaf switches.

Securing Wireless Networks — Full Definitions & Explanations

 

📌 1. Core Terms

WEP — Wired Equivalent Privacy (⚠️ Broken & obsolete)

• Original 802.11 security method.

• Used RC4, a weak stream cipher.

• Key sizes: 40-bit and 104-bit.

• Vulnerabilities:

  • IV reuse → keys crackable within minutes.

  • No strong integrity check.

• Never used today, not on CCNA exams except historically.

---

PSK — Pre-Shared Key (WPA/WPA2/WPA3-Personal)

• Authentication mode using a shared passphrase.

• Used in home / small business networks.

• Key becomes a Pairwise Master Key (PMK).

• Vulnerability:

  • Anyone with the PSK can decrypt other users’ traffic (WPA2).

• WPA3 fixes this with SAE.

---

TKIP — Temporal Key Integrity Protocol (WPA1 only)

• Introduced as a quick fix for WEP.

• Still uses RC4, but:

  • Per-packet key mixing.

  • Sequence counter to prevent replay.

  • MIC ("Michael") added.

• Allowed old WEP hardware to upgrade to WPA.

• Considered deprecated.

---

MIC — Message Integrity Code (in TKIP)

• Also called “Michael.”

• Prevents packet tampering.

• Still weak by modern standards.

• Required in WPA/TKIP networks.

---

AES — Advanced Encryption Standard

• Industry-standard encryption used across WPA2/3.

• Strong 128-bit block cipher.

• Used with:

  • CCMP (WPA2)

  • GCMP (WPA3 / 802.11ac)

---

📡 2. EAP (Extensible Authentication Protocol) & Frameworks

EAP — Extensible Authentication Protocol

• A framework for authentication, not a single method.

• Commonly used with 802.1X (Enterprise Wi-Fi).

• Allows:

  • certificates (EAP-TLS)

  • usernames/passwords (PEAP)

  • tunneled credentials (FAST)

• APs don’t authenticate users — the RADIUS server does.

---

EAP-FAST — Flexible Authentication via Secure Tunneling

• Cisco-developed replacement for LEAP.

• Uses a PAC (Protected Access Credential) instead of certificates.

• Designed to avoid tunnel vulnerabilities in PEAP/LEAP.

• Good for environments where PKI is hard to deploy.

---

EAP-TLS — EAP Transport Layer Security (🔒 Strongest method)

• Uses client + server certificates.

• Provides:

  • Mutual authentication.

  • Strong encryption.

  • No passwords to steal.

• Considered the gold standard for Enterprise Wi-Fi (WPA2-Enterprise, WPA3-Enterprise).

---

LEAP — Lightweight EAP (⚠️ Insecure/obsolete)

• Cisco proprietary.

• Used MS-CHAPv2 for authentication → broken.

• No longer used; replaced by EAP-FAST and modern methods.

---

PEAP — Protected EAP

• Uses a TLS tunnel first.

• Credentials (username/password) exchanged inside the tunnel.

• Supported everywhere.

• Used by:

  • Windows NPS

  • Microsoft RADIUS servers

• More secure than LEAP, weaker than certificate-based EAP-TLS.

---

🛡️ 3. WPA Generations (Wi-Fi Alliance)

WPA (Wi-Fi Protected Access — 2003)

• Quick replacement for WEP.

• Security components:

  • TKIP

  • MIC

  • 802.1X (Enterprise) or PSK (Personal)

• Now deprecated.

---

WPA2 (2004–2018)

• Uses AES with CCMP as the security standard.

• Still most common today.

• Modes:

  • WPA2-Personal (PSK)

  • WPA2-Enterprise (802.1X/EAP)

---

WPA3 (2018–present)

• Current generation.

• Enhancements:

  • SAE replaces PSK → stronger Personal mode.

  • Mandatory Protected Management Frames (PMF).

  • Enterprise mode supports 192-bit security suite (GCMP-256).

• Best protection against offline dictionary attacks.

---

🔐 4. Cipher Suites

CCMP — Counter Mode with Cipher Block Chaining Message Authentication Code Protocol

• Encryption component used with AES.

• Security provided:

  • Confidentiality → AES-128

  • Integrity → CBC-MAC

  • Replay protection

• The standard encryption method for WPA2.

---

GCMP — Galois/Counter Mode Protocol

• Newer, more efficient cipher used in:

  • 802.11ac Wave 2

  • WPA3-Enterprise (192-bit version)

• Security provided:

  • Confidentiality → AES-GCM

  • Integrity → Galois Message Authentication Code.

• Faster and more efficient than CCMP.

---

📌 One-Sentence Summary Table

Term	Meaning	Modern Status
WEP	Original security (RC4)	❌ Broken
PSK	Shared password method	✔️ Used (WPA2/WPA3-Personal)
TKIP	WPA1 encryption fix	❌ Deprecated
MIC/Michael	TKIP integrity check	❌ Weak
AES	Encryption algorithm	✔️ Current standard
EAP	Authentication framework	✔️ Core of Enterprise Wi-Fi
EAP-FAST	Cisco PAC-based EAP	✔️ Legacy but acceptable
EAP-TLS	Cert-based EAP (strongest)	✔️ Best practice
LEAP	Cisco MS-CHAPv2 EAP	❌ Broken
PEAP	TLS tunnel + password auth	✔️ Common
WPA	TKIP-based	❌ Deprecated
WPA2	CCMP/AES	✔️ Still widely used
WPA3	SAE + PMF	✔️ Latest
CCMP	AES-based WPA2 cipher	✔️ Standard
GCMP	Faster AES-GCM cipher	✔️ WPA3/Enterprise modern

Cisco AP Modes

Cisco APs can operate in one of the following modes, depending on how they are

configured:

 Local: This default lightweight mode offers one or more functioning BSSs on a specific

channel. During times that it is not transmitting, the AP will scan the other channels

to measure the level of noise, measure interference, discover rogue devices, and match

against wireless intrusion detection system (WIDS) events.

 Monitor: The AP does not transmit at all, but its receiver is enabled to act as a dedicated

sensor. The AP checks for IDS events, detects rogue access points, and determines

the position of stations through location-based services.

 FlexConnect: An AP at a remote site can locally switch traffic between an SSID and a

VLAN if its CAPWAP tunnel to the WLC is down and if it is configured to do so.

 Sniffer: An AP dedicates its radios to receiving 802.11 traffic from other sources,

much like a sniffer or packet capture device. The captured traffic is then forwarded to

a PC running network analyzer software such as WireShark, where it can be analyzed

further.

 Rogue detector: An AP dedicates itself to detecting rogue devices by correlating

MAC addresses heard on the wired network with those heard over the air. Rogue

devices are those that appear on both networks.

 Bridge: An AP becomes a dedicated bridge (point-to-point or point-to-multipoint)

between two networks. Two APs in bridge mode can be used to link two locations

separated by a distance. Multiple APs in bridge mode can form an indoor or outdoor

mesh network.

 Flex+Bridge: FlexConnect operation is enabled on a mesh AP.

 SE-Connect: The AP dedicates its radios to spectrum analysis on all wireless channels.

You can remotely connect a PC running software such as MetaGeek Chanalyzer or

Cisco Spectrum Expert to the AP to collect and analyze the spectrum analysis data to

discover sources of interference.

NOTE Remember that a Cisco AP is normally in local mode when it is providing BSSs and

allowing client devices to associate to wireless LANs. When an AP is configured to operate

in one of the other modes, local mode is disabled.

NOTE Remember that a Cisco AP is normally in local mode when it is providing BSSs and

allowing client devices to associate to wireless LANs. When an AP is configured to operate

in one of the other modes, local mode is disabled.