Index
A
ABB (Architecture Building Blocks), 47
access (authorized), example of IBN, 225–226
access layer, 4
access port configuration, 135, 196, 207
access requests, architecture frameworks, 233–235
access switches
configuration, 125–126, 160–161
accounting, RADIUS, 293
action lists, 144
analysis, 144
decision lists, 144
management summaries, 143
Activation process (IBN), 81
ad hoc operations (organizational maturity), 138
ADM (Architecture Development Method), 43
requirements management, 45
Agile software engineering methodology, 33–34
analysis (action plans), 144
analytics, 312
application behavior analytics, 112–113
architecture frameworks, 232
network analytics, 111, 120–121
application behavior analytics, 112–113
network function analytics, 111–112
network services availability, 112
trend analysis, 112
validation of Intent, 111
network function analytics, 111–112
anchor controller deployments, 15
Ansible
component overview of, 105–106, 108
control engine, 106
playbooks, 107
AR and, 216
API (Application Program Interface)
calls, matching to tools, 219
concept API definitions, 218
definitions, 218
network intents
API calls, matching to tools, 219
concept API definitions, 218
identifying, 217
Prime Infrastructure, 116
APIC-EM (Application Policy Infrastructure Controller-Enterprise Module), 100–101
App-Credits use case, 225
applications
business-supported apps/portals (communication plans), 223
enterprise building example (application organization), 130–132
AR (Augmented Reality), 215–216
architecture frameworks, 231–232
application architectures, 230
building blocks, 231
business architectures, 230
change, possibility of, 231
Cisco DNA, 51
Cisco DNA-ready infrastructures, 68–69
cloud service management, 57–58
infrastructure, 59
overview of Cisco solutions, 73–74
RESTful API, 71
data architectures, 230
DIY architectures, 49
drawbacks of, 39
enterprise architectures
drawbacks of, 39
guidelines/principles, 46
flexibility, 231
IBN, impact of, 232
analytics, 232
automation, 232
Cloud Service Management, 232
implementation of, 231
reusability, 231
serviceability, 231
technology architectures, 230–231
application architectures, 42
data architectures, 42
technology architectures, 42–43
Assurance process, 81–82, 162–166
asymmetric SSH key authentication and Ansible, 106–107
authentication
asymmetric SSH key authentication and Ansible, 106–107
IEEE 802.1X network access control standard, 291–293
RADIUS, 293
Authentication Server (IEEE 802.1X), 291
Authenticator (switch), IEEE 802.1X, 291
authorization
IBN, authorized access, 225–226
Autoconf, 207
automation, 174
architecture frameworks, 232
build pipelines, 33
configuration changes, 173
day-1 operations, 174
day-2 operations, 173
IBN, transitioning to, 166–167
network automation, 111, 119–120
custom-built automation tools, 109–111
SWIM, 167
switch upgrades, 169
B
border nodes
dynamic VLAN, 190
SDA, 86
BPDU (Bridge Protocol Data Unit) packets, 16–17
breakouts
central controller with
central breakout deployments, 12–13
FlexConnect deployments, 13–14
local controller with local breakout deployments, 13
budget (prioritizing challenges in IBN transitions), 142
build pipelines (automated), 33
building blocks (architecture frameworks), 46–47, 231
business
communication plans 222
processes and digitalization, 238
supported apps/portals (communication plans), 223
C
calls (API), matching to tools, 219
campus networks
Agile software engineering methodology, 33–34
Cloud Edge infrastructures, 30–32
collapsed core/two-tier topologies, 8–9
connected devices (IoT/non-user operated devices), 26–27
digitalization, 35
functional layers, 4
access layer, 4
hardware, inventories, 133–134, 152
IBN, transitioning to, 129
access port configuration, 135
challenges to day-to-day operations, 129–132, 145
change procedures, 149
configuration standardization, 160–162
day-1 operations, 174
day-2 operations, 173
design/configuration documentation, 149
disaster recovery, 149
enterprise building example (application organization), 130–132
generic IT visions/strategies, 149
incident management, 149
inventories, 132–134, 145, 152
lab environments, 179–181, 187
level of standardization, 134–138, 141–142, 145, 155
lifecycle management, 149, 152–155
matching requirements, 148
network infrastructure requirements, 151–155
organizational maturity, 138–140, 145
organizational requirements, 148–155
port-centic to policy-centric design migration, 155–159
prioritizing challenges, 142–143
resource availability, 150–151
shared switch configuration, 135
standardization across locations, 137–138
uplink standardization, 135–136
vendor/product selection, 149
VLAN configuration standardization, 136–137
wired campus design, 134
wireless campus design, 134–135
security, 29
shared switch configuration, 135
single switch topologies, 9–10
software, inventories, 133, 152
wired design, 134
CAPWAP (Control and Provisioning of Wireless Access Points) tunnels, 10–11
catalogs, network intents service, 219–220
business-supported apps/portals, 223
pilots/proof of concepts, 222
sharing successes/failures, 221–222
understanding a business, 222
CDB (Configuration Database) and NSO, 101–102
central controller with
central breakout deployments, 12–13
FlexConnect deployments, 13–14
challenges
day-to-day operations, 129–132, 145
prioritizing in IBN transitions, 142–143
chance of success (prioritizing challenges in IBN transitions), 142
change
change management, 271–272, 281
communication, 276
failures, 277
fear of change, 274
focus, maintaining, 276
forward thinking, 277–278, 281
learning stages of a new skill, 272–273
lifecycle management, 280
ownership, 281
positivity, 281
speed of change, 281
training, 281
training/demonstration, 279
enterprise architectures, 231
procedures, 149
CICD (Continuous Integration/Continuous Delivery), 33–34
Cisco Design Thinking Framework, 243–245
Cisco DNA (Digital Network Architecture), 51, 77. See also IBN
architecture frameworks, 232
analytics, 232
automation, 232
Cloud Service Management, 232
cloud service management, 57–58
overview of Cisco solutions, 73–74
RESTful API, 71
Cisco DNAC (DNA Center), 97–100
API, 215
CiscoLive Europe intent API use case, 215–216
classic VLAN (Virtual Local Area Networks), 184
automation, 185
Layer 2 intents, 185
overlay networks, 186
Scalable Group Tags, 185
templates, 186
testing, 186
VRF-Lite distribution switches, 184
Cloud Edge infrastructures, 30–32
cloud
Cloud Service Management
architecture frameworks, 232
COBIT (Control Objectives for Information and related Technologies), 138
ad hoc operations, 138
defined/documented processes/responsibilities, 139
internal control, 139
intuitive operations, 138
optimization, 139
quality checks, 139
repetitive operations, 138
risk management, 139
version control, 139
collapsed core/two-tier topologies, 8–9, 89–90
commitment (prioritizing challenges in IBN transitions), 142
communication
change management, 276
business-supported apps/portals, 223
pilots/proof of concepts, 222
successes/failures, sharing, 221–222
understanding a business, 222
complexity of campus networks, 28–29
concept API definitions, 218
configuration
access port configuration, 135, 196
access switches, 125–126, 160–161
automation and configuration changes, 173
design/configuration documentation, 149
distribution switches, 124, 126, 161
generic (global) configuration, shared switch configuration, 135
global (generic) configuration, standardization, 160–162
Layer 3 configuration, shared switch configuration, 135
links, 191
NTP, 161
ports, shared switch configuration, 135
shared switch configuration, 135
Syslog, 161
underlay routing, 192
uplink port configuration, 196
connected devices (IoT/non-user operated devices)
connections per capita, 27
control (internal), organizational maturity, 139
control nodes, SDA, 86
controllers
anchor controller deployments, 15
central controller with central breakout deployments, 12–13
local controller with local breakout deployments, 13
wireless controllers, Cisco DNAC Assurance, 166
CSI (Continual Service Improvement), 255–256
custom-built automation tools, 109–111
CVD (Cisco Validated Designs), 3
D
day-1 operations, 174
day-2 operations, 173
day-to-day operations, challenges to, 129–132, 145
defined/documented processes/responsibilities (organizational maturity), 139
demonstration/training, change management, 279
deployments, wireless networks, 15
anchor controller deployments, 15
central controller with
central breakout deployments, 12–13
FlexConnect deployments, 13–14
local controller with local breakout deployments, 13
design
DHCP (Dynamic Host Configuration Protocol)
enterprise building example (application organization), 131
LAN automation, 190
PnP
day-0 operations, 170
business processes, 238
enterprise architectures, 246–247
organizational impact, 246
enterprise architectures, 246–247
business and IT alignment, 239
IT as business enabler, 240
IT change business processes, 241
IT proactive support of business, 240–241
disaster recovery, 149
distance-vector routing protocol, 299
distribution layer, 4
distribution switches
VRF-Lite distribution switches, 184
DIY enterprise architectures, 49
DNA (Digital Network Architecture), 51, 77. See also IBN
architecture frameworks, 232
analytics, 232
automation, 232
Cloud Service Management, 232
cloud service management, 57–58
overview of Cisco solutions, 73–74
RESTful API, 71
API, 215
PnP, 286
DNS (Domain Name System), enterprise building example (application organization), 131
documentation
design/configuration documentation, 149, 221
organizational maturity, 139
dynamic VLAN (Virtual Local Area Networks), border nodes, 190
E
enterprise architectures, 231–232
application architectures, 230
building blocks, 231
business architectures, 230
change, possibility of, 231
data architectures, 230
DIY architectures, 49
drawbacks of, 39
flexibility, 231
guidelines/principles, 46
implementation of, 231
reusability, 231
serviceability, 231
technology architectures, 230–231
application architectures, 42
data architectures, 42
technology architectures, 42–43
enterprise building example (application organization), 130–132
estimated timelines (action plans), 144–145
Ethernet and STP, 308–310, 320
examples of IBN (Intent-Based Networking), 223
incident response security, 223–224
extended IBN (Intent-Based Networking)
security, 204
IEEE 802.1X network access control standard, 205–208
risks, 209
scalability, 210
F
failures
change management, 277
communication plans, sharing, 223
fear of change, 274
FinTech Ltd. use case, 25
automation, 64
communication and focus in change management, 276
DIY architectures, 49
IBN technologies, choosing, 186
first hop security, 196
FlexConnect, central controller with FlexConnect deployments, 13–14
flexibility, enterprise architectures, 231
focus, maintaining in change management, 276
forward thinking, change management, 277–278, 281
frameworks (architecture), 231–232
application architectures, 230
building blocks, 231
business architectures, 230
change, possibility of, 231
Cisco Design Thinking Framework, 243–245
Cisco DNA, 51
Cisco DNA-ready infrastructures, 68–69
cloud service management, 57–58
infrastructure, 59
overview of Cisco solutions, 73–74
RESTful API, 71
data architectures, 230
DIY architectures, 49
drawbacks of, 39
enterprise architectures
drawbacks of, 39
guidelines/principles, 46
flexibility, 231
IBN, impact of, 232
analytics, 232
automation, 232
Cloud Service Management, 232
implementation of, 231
IT operations frameworks, 263
CSI in ITIL framework, 255–256
ITIL framework, 252
reusability, 231
serviceability, 231
technology architectures, 230–231
application architectures, 42
data architectures, 42
technology architectures, 42–43
frequency band (unlicensed spectrum), 26
functional layers, 4
access layer, 4
G
generic (global) configuration
shared switch configuration, 135
generic IT visions/strategies, 149
H
hardware, inventories, 133–134, 152
communication, 276
failures, 277
fear of change, 274
focus, maintaining, 276
forward thinking, 277–278, 281
learning stages of a new skill, 272–273
ownership, 281
positivity, 281
speed of change, 281
I
IBN (Intent-Based Networking), 77, 213–215). See also Cisco DNA
Activation process, 81
calls, matching to tools, 219
concept API definitions, 218
definitions, 218
generalizing network intents, 217–218
identifying network intents, 217
network Intent service catalogs, 219–223
architecture frameworks, IBN impact on, 232
analytics, 232
automation, 232
Cloud Service Management, 232
Assurance process, 81–82, 162–166
collapsed core/two-tier topologies, 89–90
enterprise building example (application organization), 130–132
examples of, 223
incident response security, 223–224
extended IBN
feedback
intent-based feedback, 82
network-driven feedback, 81–84, 93
intent
example of, 78
intent-based feedback, 82
requesting, 81
metrics, 82
network analytics, 111, 120–121
application behavior analytics, 112–113
network function analytics, 111–112
network services availability, 112
trend analysis, 112
validation of Intent, 111
network automation, 111, 119–120
custom-built automation tools, 109–111
policy-centric networks, 83, 93
border nodes, 86
classic VLAN over SDA topologies, 90–91
control nodes, 86
virtual networks, 85
security, IEEE 802.1X network access control standard, 205–208
systematic approach to networks, 80
transitioning to, 129
access port configuration, 135
challenges to day-to-day operations, 129–132, 145
change procedures, 149
configuration standardization, 160–162
day-1 operations, 174
day-2 operations, 173
design/configuration documentation, 149
disaster recovery, 149
generic IT visions/strategies, 149
incident management, 149
inventories, 132–134, 145, 152
lab environments, 179–181, 187
level of standardization, 134–138, 141–142, 145, 155
lifecycle management, 149, 152–155
matching requirements, 148
network infrastructure requirements, 151–155
organizational maturity, 138–140, 145
organizational requirements, 148–155
port-centic to policy-centric design migration, 155–159
prioritizing challenges, 142–143
resource availability, 150–151
risk management, 149
shared switch configuration, 135
standardization across locations, 137–138
tips for success. See change management
uplink standardization, 135–136
vendor/product selection, 149
VLAN configuration standardization, 136–137
wired campus design, 134
wireless campus design, 134–135
Translation process, 82
validation, 82
IEEE 802.1b, 23
IEEE 802.1X network access control standard, 156–157, 290–291, 319
access port configuration, 207
authentication process, 291–293
Authentication Server, 291
Authenticator (switch), 291
supplicants, 291
implementation of enterprise architectures, 231
incentives, change management, 274–275
incidents
management, 149
response security, example of IBN, 223–224
infrastructure
architecture frameworks, 232–235
Cisco DNA, 59
Prime Infrastructure, 97–100, 115–117, 170
requirements (networks), 151–155
installations (next-next-finish), 157
intent API (Application Program Interface), 215–217
Intent-Based Networking. See IBN
intents
IBN, transitioning to
Layer 2 intents, classic VLAN, 185
network intents
API calls, matching to tools, 219
concept API definitions, 218
identifying, 217
internal control (organizational maturity), 139
intuitive operations (organizational maturity), 138
inventories, transitioning to IBN, 132–134, 145, 152
IoC (Indication of Compromise), 223–224
IoT (Internet of Things), growth of, 27
IP address pools, LAN automation, 189–190
IPv6, first hop security, 196
ISE (Identity Services Engine), 157
port-centic to policy-centric design migration, 159
SDA, 183
IS-IS, underlay routing configuration, 192
IT operations
conflicts/recommendations
changing design patterns, 264, 268
management by exception, 265–266, 268–269
organizational change, 266–267, 270
working across domains, 266, 269–270
digitalization
business and IT alignment, 239
IT as business enabler, 240
IT change business porcesses, 241
IT proactive support of business, 240–241
frameworks, 263
CSI in ITIL framework, 255–256
ITIL framework, 252
visions/strategies (generic), 149
L
lab environments, 179–181, 187
LAN (Local Area Networks)
Layer 2 intents, classic VLAN, 185
Layer 2 networks, redundancy, handling, 16–17
Layer 3 configuration, shared switch configuration, 135
Layer 3 networks, redundancy, handling, 17
learning stages of a new skill, 272–273
LEI (Lean Enterprise Institute), 259
lifecycle management, 149, 152–155, 280
links, configuration, 191
link-state routing protocol, 299–300
LISP (Locator/Identifier Separation Protocol), 302–305, 319
lists
action lists, 144
decision lists, 144
local controller with local breakout deployments, 13
locations, extended IBN, 202–203
LogiServ Inc. use case
automation, 169
port-centic to policy-centric design migration, 158
standardization and design, 221–222
switch upgrades, 169
M
manageability of campus networks, 29–30
management
classic VLAN over SDA topologies, 90
summaries (action plans), 143
VRF, 90
matching API calls to tools, 219
maturity level of an organization, 138, 145
ad hoc operations, 138
defined/documented processes/responsibilities, 139
internal control, 139
intuitive operations, 138
optimization, 139
organizational requirements, 148–150
quality checks, 139
questions and related maturity levels, 140
repetitive operations, 138
risk management, 139
version control, 139
MDT (Model-Driven Telemetry), 316–318, 320
microsegmentation, IBN, 83, 93
MSTP (Multiple Spanning Tree Protocol), 310
N
NAD (Network Access Devices), RADIUS servers, 293
NED (Network Elements Drivers) and NSO, 101
networks
application behavior analytics, 112–113
network function analytics, 111–112
network services availability, 112
trend analysis, 112
validation of Intent, 111
building automation tools, 109–111
campus networks
access port configuration, 135
action plans and IBN transitions, 143–146
Agile software engineering methodology, 33–34
Cloud Edge infrastructures, 30–32
configuration standardization, 160–162
connected devices (IoT/non-user operated devices), 26–27
day-1 operations, 174
day-2 operations, 173
digitalization, 35
hardware inventories, 133–134, 152
level of standardization, 134–138, 145, 155
organizational maturity, 138–140
port-centic to policy-centric design migration, 155–159
prioritizing challenges in IBN transitions, 142–143
security, 29
shared switch configuration, 135
stakeholders and IBN transitions, 141–142, 145
standardization across locations, 137–138
transitioning to IBN. See IBN, transitioning to
uplink standardization, 135–136
VLAN configuration standardization, 136–137
wired design, 134
digitalization, 35
infrastructure requirements, 151–155
API calls, matching to tools, 219
concept API definitions, 218
identifying, 217
NAD and RADIUS servers, 293
overlay networks and classic VLAN, 186
policy-centric networks, port-centic to policy-centric design migration, 155–159
services, network analytics, 112
VLAN, 305–308, 311–312, 319–320
wireless networks
configuration standardization, 161–162
connected devices (IoT/non-user operated devices), 26–27
frequency band (unlicensed spectrum), 26
security, 29
next-next-finish installations, 157
non-user operated devices
connections per capita, 27
NSO (Network Services Orchestrator), 101
NED and, 101
NTP (Network Translation Protocol), configuration, 102–103, 161
O
open standards, Cisco DNA, 69–70
optimization (organizational maturity), 139
option 43 (DHCP), and PnP, 285–286
order pickers, 24
organizational change, 271–272, 281
communication, 276
failures, 277
fear of change, 274
focus, maintaining, 276
forward thinking, 277–278, 281
learning stages of a new skill, 272–273
lifecycle management, 280
ownership, 281
positivity, 281
speed of change, 281
training, 281
training/demonstration, 279
organizational maturity, 138, 148–150
ad hoc operations, 138
defined/documented processes/responsibilities, 139
internal control, 139
intuitive operations, 138
optimization, 139
quality checks, 139
questions and related maturity levels, 140
repetitive operations, 138
risk management, 139
version control, 139
organizing
applications, enterprise building example (application organization), 130–132
meetings, example of IBN, 224–225
overlay networks, classic VLAN, 186
P
PacketFence, 158
pilots/proof of concepts (communication plans), 222
playbooks and Ansible, 107
DNAC and, 286
Pokemon Go, 215
policies
policy-centric networks, port-centic to policy-centric design migration, 155–159
portals, business-supported apps/portals (communication plans), 223
ports
access port configuration, 135, 196, 207
port-centic to policy-centric design migration, 155–159
routed ports
shared switch configuration, 135
switchports
uplink port configuration, 196
positivity, change management, 281
Prime Infrastructure, 97–100, 115–117, 170
prioritizing challenges in IBN transitions, 142–143
processes/responsibilities (organizational maturity), 139
product/vendor selection, 149
proof of concepts/pilots (communication plans), 222
protocols
distance-vector routing protocol, 299
link-state routing protocol, 299–300
MSTP, 310
routing protocols, 298–300, 319
RSTP, 310
Python and ZTP, 288
Q
QoS (Quality of Service), use case, 28–29
quality checks (organizational maturity), 139
R
RACI matrix, 141
RADIUS,
RADIUS (Remote Access DialUp Services), 293–295, 319
RADIUS servers, 158
authorization rules, 157
IEEE 802.1X network access control standard, 196, 205
repetitive operations (organizational maturity), 138
repositories (architecture), 47–48
requirements
IBN, transitioning to
matching requirements, 148
organizational requirements, 148–155
organizational requirements, maturity level of an organization, 148–150
resource availability, 150–151
responsibilities/processes (organizational maturity), 139
RESTful API, Cisco DNA, 71
reusability, enterprise architectures, 231
routed ports
routing protocols, 298–299, 319
distance-vector routing protocol, 299
link-state routing protocol, 299–300
routing (underlay), configuration, 192
RSTP (Rapid Spanning Tree Protocol), 310
S
SBB (Solution Building Blocks), 47
scalability, extended IBN security, 210
Scalable Group Tags. See SGT
SDA (Software-Defined Access), 84, 181–184, 284
border nodes, 86
classic VLAN and, 90–91, 183–187
control nodes, 86
STP, 185
virtual networks, 85
security
enterprise building example (application organization), 131
first hop security, 196
IBN, 204
IEEE 802.1X network access control standard, 205–208
risks, 209
scalability, 210
incident response example, 223–224
networks, 29
servers (RADIUS), 293
service catalogs (network intents), 219–220
business-supported apps/portals, 223
pilots/proof of concepts, 222
sharing successes/failures, 221–222
understanding a business, 222
serviceability, enterprise architectures, 231
SGT (Scalable Group Tags), 295–298, 319
classic VLAN, 185
shared switch configuration, 135
SharedService Group use case, 28–29
datacenter automation, 110–111
digitalization, IT proactive support of business, 240
IT operation frameworks, overusing, 252–253
lab environments, 187
lifecycle management, 153
port-centic to policy-centric design migration, 158
virtualizing network functions, 61
VLAN configuration standardization, 136
single switch topologies, 9–10
skills, learning stages of new, 272–273
slow change, change management, 281
small switches, topology of, 308–309
SNMP (Simple Network Management Protocol), 312–314, 320
software
Agile software engineering methodology, 33–34
Spanning Tree Protocol. See STP
speed of change, change management, 281
SSH (Secure Shell), asymmetric SSH key authentication and Ansible, 106–107
SSID (Service Set Identifiers), VLAN configuration standardization, 136
stakeholders
IBN, transitioning to, 141–142, 145
RACI matrix, 141
standardization
access switch configuration, 160–161
benefits of, 221
design and, 221
distribution switch configuration, 161
global (generic) configuration, 160–162
wireless network configuration, 161–162
storage, repositories (architecture), 47–48
STP (Spanning Tree Protocol), 308–310, 320
classic VLAN over SDA topologies, 90
SDA and, 185
successes
chance of success, prioritizing challenges in IBN transitions, 142
communication plans, sharing, 223
supplicants (IEEE 802.1X), 291
SWIM (SoftWare Image Management), 167
switches
access switches
configuration standardization, 160–161
automating upgrades, 169
distribution switches
configuration standardization, 161
VRF-Lite distribution switches, 184
shared switch configuration, 135
small switches, topology of, 308–309
upgrading, 169
VRF-Lite distribution switches, 184
switchports
T
technology architectures, 42–43, 230–231
templates
classic VLAN, 186
time (prioritizing challenges in IBN transitions), 142
timelines (action plans), estimated, 144–145
TOGAF® (The Open Group Architecture Framework), 39–41, 48
ADM, 43
requirements management, 45
application architectures, 42
data architectures, 42
technology architectures, 42–43
topologies
collapsed core/two-tier topologies, 8–9
single switch topologies, 9–10
training
Translation process (IBN), 82
trend analysis, network analytics, 112
U
UDLD (Unidirectional Link Detection), 18
underlay routing, configuration, 192
understanding a business (communication plans), 222
unlicensed spectrum (frequency band), 26
upgrading switches, 169
uplinks
port configuration, 196
standardization, level of, 135–136
use cases
App-Credits use case, 225
automation, 173
CiscoLive Europe use case, Intent-based API, 215–216
configuration and automation, 173
examples of IBN, 223
incident response security, 223–224
FinTech Ltd. use case, 25
automation, 64
choosing IBN technologies, 186
communication and focus in change management, 276
DIY architectures, 49
incident response security, 223–224
LogiServ Inc. use case
automation, 169
port-centic to policy-centric design migration, 158
standardization and design, 221–222
switch upgrades, 169
quid pro quo, change management, 275
SharedService Group use case, 28–29
datacenter automation, 110–111
IT proactive support of business, 240
lab environments, 187
lifecycle management, 153
overusing IT operation frameworks, 252–253
port-centic to policy-centric design migration, 158
virtualizing network functions, 61
VLAN configuration standardization, 136
V
validated designs, 3
vendor/product selection, 149
version control (organizational maturity), 139
virtual networks, SDA, 85
visibility, transitioning to IBN, 162–166
VLAN (Virtual Local Area Networks), 305–308, 319
automation, 185
Layer 2 intents, 185
overlay networks, 186
Scalable Group Tags, 185
templates, 186
testing, 186
VRF-Lite distribution switches, 184
configuration standardization, 136–137, 161–162
dynamic VLAN, border nodes, 190
management VLAN, classic VLAN over SDA topologies, 90
VNF (Virtualize Network Functions), 60–61
vPC (Virtual PortChannel), 17–19
VRF (Virtual Routing and Forwarding), classic VLAN over SDA topologies, 90
VRF-Lite (Virtual Routing and Forwarding-Lite), 184, 289–290, 319
VSS (Virtual Switching Solutions)
VTP (VLAN Trunking Protocol), 311–312, 320
VXLAN (Virtual eXtensible Local Area Networks), 301–302, 319
W
WAN (Wide-Area Networks), enterprise building example (application organization), 131
wired design, campus networks, 134
wireless controllers, Cisco DNAC Assurance, 166
wireless design, campus networks, 134–135
anchor controller deployments, 15
central controller with
central breakout deployments, 12–13
FlexConnect deployments, 13–14
configuration standardization, 161–162
connected devices (IoT/non-user operated devices)
connections per capita, 27
frequency band (unlicensed spectrum), 26
local controller with local breakout deployments, 13
security, 29
WLC, 10
WLC (Wireless LAN Controllers), 10
Y
YAML (YAML Ain’t Markup Language), playbooks and Ansible, 107
Z
ZTP (Zero Touch Provisioning), 288
Python and, 288