OMP is the control protocol that is used to exchange routing, policy, and management information between Cisco vSmart Controllers and Cisco IOS XE SD-WAN devices in the overlay network. These devices automatically initiate OMP peering sessions between themselves, and the two IP end points of the OMP session are the system IP addresses of the two devices.

We must reconfigure the IP address after assigning or removing an interface to a VRF. Otherwise that interface does not have an IP address.

Features of the Cisco DNA Assurance solution includes Device 360 and client 360, which provides a detailed view of the performance of any device or client over time and from any application context. Provides very granular troubleshooting in seconds.

Layer2 Flooding

Cisco SD-Access fabric provides many optimizations to improve unicast traffic flow, and to reduce the unnecessary flooding of data such as broadcasts. But, for some traffic and applications, it may be desirable to enable broadcast forwarding within the fabric.

By default, this is disabled in the Cisco SD-Access architecture. If broadcast, Link local multicast and Arp flooding is required, it must be specifically enabled on a per-subnet basis using Layer 2 flooding feature.

Layer 2 flooding can be used to forward broadcasts for certain traffic and

application types which may require leveraging of Layer 2 connectivity, such as silent hosts, card readers, door locks, etc.

https://www.aspiretransforms.com/2018/06/06/ insider-guide-cisco-sd-access/

JWT: JSON Web Tokens are an open and standard (RFC 7519) way for you to represent your user's identity securely during a two-party interaction. That is to say, when two systems exchange data you can use a JSON Web Token to identify your user without having to send private credentials on every request.

The classification is carried in the IP packet header, using 6 bits from the deprecated IP type of service (ToS) field to carry the classification (class) information. Classification can also be carried in the Layer 2 frame.

A control plane node maintains a host tracking database (HTDB), and also uses Locator/ID Separation Protocol (LISP) to provide a map server, populating the HTDB from fabric edge registration messages; and a map resolver to respond to queries from edge devices requesting location information about destination nodes.

Cisco DNA Center creates the backup files and posts them to a remote server. Each backup is uniquely stored using the UUID as the directory name.To support Assurance data backups, the server must be a Linux-based NFS server that meets the following requirements:– Support NFS v4 and NFS v3.– Cisco DNA Center stores backup copies of Assurance data on an external NFS device and automation data on an external remote sync (rsync) target location.– The remote share for backing up an Assurance database (NDP) must be an NFS share.

A picture containing diagram Description automatically generated

Orchestration

 Orchestration means arranging or coordinating multiple systems. It’s also used to mean “running the same tasks on a bunch of servers at once, but not necessarily all of them.”

 Configuration Management

Config Management is part of provisioning. Basically, that’s using a tool like Chef, Puppet or Ansible to configure our server. “Provisioning” often implies it’s the first time we do it. Config management usually happens repeatedly.

Configuration management (CM) is a systems engineering process for establishing and maintaining consistency of a product’s performance, functional, and physical attributes with its requirements, design, and operational information throughout its life Configuration management is all about bringing consistency in the infrastructure.

Configuration Orchestration vs Configuration Management

The first thing that should be clarified is the difference between “configuration orchestration” and “configuration management” tools, both of which are considered IaC tools and are included on this list.

Configuration orchestration tools, which include Terraform and AWS CloudFormation, are designed to automate the deployment of servers and other infrastructure. Configuration management tools like Chef, Puppet, and the others on this list help configure the software and systems on this infrastructure that has already been provisioned.

• Step 1. Create the loopback interface using the interface loopback number global configuration command.
• Step 2. Add a description. Although optional, it is a necessary component for documenting a network.
• Step 3. Configure the IP address.

For example, the following commands configure a loopback interface of the R1 router shown in (shown earlier in the chapter):

R1# configure terminal

R1(config)# interface loopback 0

R1(config-if)# ip address 10.0.0.1 255.255.255.0

R1(config-if)# exit

R1(config)#

This is because the remote span VLAN is used to transport the mirrored traffic from the source switch to the destination switch, where the monitoring server is connected. The remote span VLAN must be defined on both switches and must not be used for any other purpose. The source of this answer is the Cisco ENCOR v1.1 course, module 6, lesson 6.2: Implementing SPAN, RSPAN, and ERSPAN.

Graphical user interface Description automatically generated

From the output exhibit, we notice that the key-string of R1 is ―Cisco123!‖ (letter ―C‖ is in capital) while that of R2 is ―cisco123!‖. This causes a mismatch in the authentication so we have to fix their key-strings.

key-string [encryption-type] text-string: Configures the text string for the key. The text-string argument is alphanumeric, case-sensitive, and supports special characters.

The AP will attempt to resolve the DNS name CISCO-CAPWAP-CONTROLLER.localdomain. When the AP is able to resolve this name to one or more IP addresses, the AP sends a unicast CAPWAP Discovery Message to the resolved IP address(es). Each WLC that receives the CAPWAP Discovery Request Message replies with a unicast CAPWAP Discovery Response to the AP.

interface Ethernet0/0.100

encapsulation dot1Q 100

ip address 10.0.111.1 255.255.255.0

standby 15 ip 10.0.111.254

!

cisco(config-subif)#do s stand

Ethernet0/0.100 - Group 15

State is Speak

Virtual IP address is 10.0.111.254

Active virtual MAC address is unknown

Local virtual MAC address is 0000.0c07.ac0f (v1 default)

Hello time 3 sec, hold time 10 sec

Next hello sent in 1.200 secs

Preemption disabled

Active router is unknown

Standby router is unknown

"Cisco Stealthwatch collects and analyzes massive amounts of

data to give even the largest, most dynamic networks

comprehensive internal visibility and protection. It helps

security operations teams gain real-time situational awareness

of all users, devices, and traffic on the extended network so

they can quickly and effectively respond to threats"

Page 1

https://media.zones.com/images/pdf/cisco-stealthwatch-solution-overview.pdf

Cisco Express Forwarding (CEF) switching is a proprietary form of scalable switching intended to tackle the problems associated with demand caching. With CEF switching, the information which is conventionally stored in a route cache is split up over several data structures. The CEF code is able to maintain these data structures in the Gigabit Route Processor (GRP), and also in slave processors such as the line cards in the 12000 routers. The data structures that provide optimized lookup for efficient packet forwarding include:

• The Forwarding Information Base (FIB) table - CEF uses a FIB to make IP destination prefix-based switching decisions. The FIB is conceptually similar to a routing table or information base. It maintains a mirror image of the forwarding information contained in the IP routing table. When routing or topology changes occur in the network, the IP routing table is updated, and these changes are reflected in the FIB. The FIB maintains next-hop address information based on the information in the IP routing table.

Because there is a one-to-one correlation between FIB entries and routing table entries, the FIB contains all known routes and eliminates the need for route cache maintenance that is associated with switching paths such as fast switching and optimum switching.

• Adjacency table - Nodes in the network are said to be adjacent if they can reach each other with a single hop across a link layer. In addition to the FIB, CEF uses adjacency tables to prepend Layer 2 addressing information. The adjacency table maintains Layer 2 next-hop addresses for all FIB entries.

CEF can be enabled in one of two modes:

• Central CEF mode - When CEF mode is enabled, the CEF FIB and adjacency tables reside on the route processor, and the route processor performs the express forwarding. You can use CEF mode when line cards are not available for CEF switching, or when you need to use features not compatible with distributed CEF switching.
• Distributed CEF (dCEF) mode - When dCEF is enabled, line cards maintain identical copies of the FIB and adjacency tables. The line cards can perform the express forwarding by themselves, relieving the main processor - Gigabit Route Processor (GRP) - of involvement in the switching operation. This is the only switching method available on the Cisco 12000 Series Router.

dCEF uses an Inter-Process Communication (IPC) mechanism to ensure synchronization of FIBs and adjacency tables on the route processor and line cards.

For more information about CEF switching, see Cisco Express Forwarding (CEF) White Paper.

A picture containing diagram Description automatically generated

DISTRO-SW1

Sw1

int vlan 100

standby 1 ip 192.168.1.1

standby 1 priority 110

standby 1 preempt

copy run start

DISTRO-SW2

SW2

int vlan 100

standby 1 ip 192.168.1.1

standby 1 preempt

copy run start

OR

MINOR CHANGE IN ABOVE HSRP SCENERIO

Graphical user interface, text, application, email Description automatically generated

Check the IP address 1.254 check the minimum 15 seconds solution get change.

DISTRO-SW1

Sw1

int vlan 100

glbp 1 ip 192.168.1.254

glbp 1 priority 110

glbp 1 timers 5 15

glbp 1 preempt

copy run start

DISTRO-SW2

SW2

int vlan 100

glbp 1 ip 192.168.1.254

glbp 1 timers 5 15

glbp 1 preempt

copy run start

This is because the response “204 No Content” means that the REST API request was successful, but there is no content to return. The request was a DELETE method, which is used to remove a resource from the server. The resource in this case was the interface loopback 100, which was deleted from the configuration of the device. The source of this answer is the Cisco ENCOR v1.1 course, module 8, lesson 8.4: Implementing REST API.

This is because a dictionary attack is a type of password cracking attack that uses a list of common or previously leaked passwords to guess the credentials of a user. A dictionary attack becomes more effective because of global leakages of users’ passwords, as the attacker can use the leaked passwords as a source for the dictionary. The source of this answer is the Cisco ENCOR v1.1 course, module 2, lesson 2.3: Implementing Wireless Security.

This is because the GCMP256 cipher is the only one that supports both WPA2 and WPA3 with the Personal security type. The GCMP256 cipher provides stronger encryption and authentication than the CCMP ciphers, which are only compatible with WPA2. The source of this answer is the Cisco ENCOR v1.1 course, module 7, lesson 7.2: Implementing WPA2 and WPA3.

https://www.ciscolive.com/c/dam/r/ciscolive/emea/docs/2020/pdf/BRKCRS-2832.pdf

 This is because the Cisco DNA Center Template Editor feature is a tool that allows the network administrator to create and deploy configuration templates to multiple network devices. The configuration templates use parameterized elements or variables, which are placeholders for values that can be customized for each device. For example, a variable can represent the hostname, IP address, or interface number of a device. The parameterized elements or variables can be defined manually or automatically using the Cisco DNA Center inventory. The source of this answer is the Cisco ENCOR v1.1 course, module 8, lesson 8.5: Implementing Network Configuration Management.

The collection that contains the resources to obtain a list of fabric nodes through the vManage API is the device inventory collection. This collection can be accessed through the Cisco Encor Documents and provides resources such as the Fabric Visualization, Device List, and Fabric Node Inventory APIs. These APIs can be used to obtain information about the fabric nodes, such as the device inventory, status, and version.

The following different OSPF types are compatible with each other:

+ Broadcast and Non-Broadcast (adjust hello/dead timers)

+ Point-to-Point and Point-to-Multipoint (adjust hello/dead timers)

Broadcast and Non-Broadcast networks elect DR/BDR so they are compatible. Point-topoint/

multipoint do not elect DR/BDR so they are compatible.

Weighted: Defines weights to each device in the GLBP group to define the ratio ofload balancing between the devices. This allows for a larger weight to be assigned to bigger routers that can handle more traffic.  protocol is used by an extended

This is because Fast Transition (FT) is a feature that allows 802.11r-capable clients to roam faster between access points by reducing the authentication and key exchange time. FT can be configured in two modes: adaptive and over-the-DS. Adaptive mode is recommended for mixed environments where both 802.11r-capable and non-capable clients are present, as it allows the access point to negotiate the FT mode with the client. Over-the-DS mode is only suitable for environments where all clients are 802.11r-capable, as it requires the access point to communicate with the previous access point over the distribution system. FT + PSK is a security option that enables FT with pre-shared key (PSK) authentication, which is a simple and common method of securing wireless networks. WPA2-AES is an encryption standard that provides strong security and privacy for wireless networks. The source of this answer is the Cisco ENCOR v1.1 course, module 7, lesson 7.2: Implementing WPA2 and WPA3.

 This is because the EEM applet needs to specify the full path of the Tcl script that is stored in the flash memory of the device. The script name is write_backup.tcl and it is used to backup the running configuration to a remote server. The source of this answer is the Cisco ENCOR v1.1 course, module 8, lesson 8.3: Implementing Embedded Event Manager.

Option B is the correct command set to update the existing configuration to achieve the desired results. The configuration steps are as follows12:

• Define a standard access list that permits only the administrators from the 192.168.1.0/24 subnet to access the vty lines. In this case, the access list is named ADMIN and it allows any host with an IP address in the range of 192.168.1.1 to 192.168.1.254 to access the vty lines: ip access-list standard ADMIN and permit 192.168.1.0 0.0.0.255.
• Apply the access list to the vty lines using the access-class command. This command restricts incoming and outgoing connections between a particular vty and the addresses in the access list. In this case, the access list ADMIN is applied to the vty lines 0 to 15 in the inbound direction, which means that only the hosts that match the access list can initiate a connection to the vty lines: line vty 0 15 and access-class ADMIN in.
• Disable the clear-text protocols such as Telnet for the vty lines using the transport input command. This command specifies which protocols are allowed for incoming connections. In this case, only SSH is allowed for the vty lines, which is a secure protocol that encrypts the data between the client and the server: transport input ssh.

Option A is incorrect because it does not apply the access list to the vty lines, which is required to restrict the access to the administrators from the 192.168.1.0/24 subnet. Without the access-class command, any host can attempt to connect to the vty lines12.

Option C is incorrect because it does not disable the clear-text protocols for the vty lines, which is required to prohibit the access to the vty lines using unsecure protocols. Without the transport input ssh command, both Telnet and SSH are allowed for the vty lines by default12.

Option D is incorrect because it uses an extended access list instead of a standard access list, which is not recommended for controlling access to the vty lines. An extended access list requires more configuration and processing than a standard access list, and it cannot be applied directly to the vty lines. It has to be applied to each interface that can be used to access the vty lines, which increases the complexity and the possibility of errors12. References: 1: Controlling Access to a Virtual Terminal Line, 2: Configuring Secure Shell

Option A is the properly formatted JSON script. JSON (JavaScript Object Notation) is a standard text-based format for representing structured data based on JavaScript object syntax. It is commonly used for transmitting data in web applications (e.g., sending some data from the server to the client, so it can be displayed on a web page, or vice versa). The JSON syntax rules are as follows12:

• Data is in name/value pairs, separated by commas. A name/value pair consists of a field name (in double quotes), followed by a colon, followed by a value: "name": "value".
• Curly braces hold objects. An object can contain multiple name/value pairs: {"name": "value", "name": "value", ...}.
• Square brackets hold arrays. An array can contain multiple values, separated by commas: ["value", "value", ...].
• Values can be strings (in double quotes), numbers, booleans (true or false), null, objects, or arrays.

Option A follows these rules and is a valid JSON script. It defines an object with four name/value pairs: "name", "age", "hobbies", and "address". The value of "name" is a string, the value of "age" is a number, the value of "hobbies" is an array of strings, and the value of "address" is another object with two name/value pairs: "city" and "country". The object is enclosed in curly braces and the name/value pairs are separated by commas.

Option B is not a valid JSON script because it uses single quotes instead of double quotes for the field names and string values. JSON requires double quotes for strings12.

Option C is not a valid JSON script because it does not use commas to separate the name/value pairs. JSON requires commas to separate the data elements within an object or an array12.

Option D is not a valid JSON script because it uses a semicolon instead of a colon to separate the field name and the value. JSON requires a colon to separate the name and the value in a name/value pair12. References: 1: JSON Introduction, 2: JSON Syntax

https://developer.cisco.com/docs/dna-center/#!api-quick-start/cisco-dna-center-platform-api-overview

CLOUD1 and 3ON-PREMISES2 and 4

obj = json.JSONEncoder().encode(data)

Option C is the correct set of commands to apply flexible NetFlow on a group of switches with the given requirement. The configuration steps are as follows12:

• Define a flow record that specifies the fields to be collected and exported for the flows. In this case, the flow record is named FNF-RECORD and it collects the source and destination IP addresses, the input and output interfaces, the transport protocol, and the source and destination port numbers: flow record FNF-RECORD and match ipv4 source address, match ipv4 destination address, match interface input, match interface output, match transport protocol, match transport source-port, match transport destination-port.
• Define a flow exporter that specifies the destination and transport protocol for sending the flow data. In this case, the flow exporter is named FNF-EXPORTER and it uses UDP port 9996 to send the flow data to the IP address 10.10.10.10: flow exporter FNF-EXPORTER and destination 10.10.10.10, transport udp 9996.
• Define a flow monitor that applies the flow record and the flow exporter to the monitored traffic. In this case, the flow monitor is named FNF-MONITOR and it uses the flow record FNF-RECORD and the flow exporter FNF-EXPORTER. It also sets the cache timeout for inactive flows to 20 seconds, which means that the flow sample will be exported if the flow is idle for 20 seconds: flow monitor FNF-MONITOR and record FNF-RECORD, exporter FNF-EXPORTER, cache timeout inactive 20.
• Apply the flow monitor to the interfaces that need to be monitored. In this case, the flow monitor FNF-MONITOR is applied to the input and output direction of the interface GigabitEthernet0/1: interface GigabitEthernet0/1 and ip flow monitor FNF-MONITOR input, ip flow monitor FNF-MONITOR output.

Option A is incorrect because it does not set the cache timeout for inactive flows to 20 seconds, which is required by the question. The default cache timeout for inactive flows is 15 seconds1.

Option B is incorrect because it does not apply the flow monitor to the output direction of the interface, which is required to capture both incoming and outgoing traffic on the interface1.

Option D is incorrect because it does not use a flow record to specify the fields to be collected and exported for the flows, which is required to customize the flow data according to the user’s needs1. References: 1: Configuring Flexible NetFlow, 2: Flexible NetFlow Configuration Guide

This is because a virtual switch is a software-based switch that operates at the data link layer of the OSI model and provides connectivity between virtual machines that are running on the same physical host or different hosts. A virtual switch can also connect virtual machines to external networks, such as the Internet or a local area network, by using physical network adapters on the host. A virtual switch can perform the same functions as a physical switch, such as learning MAC addresses, forwarding frames, and applying VLANs. The source of this answer is the Cisco ENCOR v1.1 course, module 9, lesson 9.1: Implementing Network Virtualization.

Graphical user interface, application Description automatically generated

The Python code in the exhibit defines a function called average that takes two parameters a and b and returns the arithmetic mean of them. The function is then called with the arguments 5 and 10, which are assigned to a and b respectively. The function returns (5 + 10) / 2, which is 7.5. Therefore, the result of the Python code is 7.5. References: Python Functions, Python Arithmetic Operators

This is because the LC connector is a small form factor connector that is commonly used on network interface cards (NICs) and transceivers. The LC connector has a push-pull locking mechanism that makes it easy to insert and remove. The LC connector can support both single-mode and multimode fibers. The LC connector is also compatible with the SFP and SFP+ transceiver modules that are widely used on NICs. The source of this answer is the Cisco ENCOR v1.1 course, module 1, lesson 1.3: Comparing Copper and Fiber Cabling.

Perform this task to create a password security policy and to apply the policy to a specific user profile.

Device> enable

Device# configure terminal

Device(config)# aaa new-model

Device(config)# aaa common-criteria policy policy1

Device(config-cc-policy)# char-changes 4

Device(config-cc-policy)# max-length 20

Device(config-cc-policy)# min-length 6

Device(config-cc-policy)# numeric-count 2

Device(config-cc-policy)# special-case 2

Device(config-cc-policy)# exit

Device(config)# username user1 common-criteria-policy policy1 password password1

Device(config)# end

Coverage defines the ability of wireless clients to connect to a wireless AP with a signal strength and quality high enough to overcome the effects of RF interference. The edge of the coverage for an AP is based on the signal strength and SNR measured as the client device moves away from the AP.

The signal strength required for good coverage varies dependent on the specific type of client devices and applications on the network.

To accommodate the requirement to support wireless Voice over IP (VoIP), refer to the RF guidelines specified in the Cisco 7925G Wireless IP Phone Deployment Guide. The minimum recommended wireless signal strength for voice applications is -67 dBm and the minimum SNR is 25 dB.

The first step in the analysis of a post site survey is to verify the ‘Signal Coverage’. The signal coverage is measured in dBm. You can adjust the color-coded signal gauge to your minimum-allowed signal level to view areas where there are sufficient and insufficient coverage. The example in Figure 8 shows blue, green, and yellow areas in the map have signal coverage at -67 dBm or better. The areas in grey on the coverage maps have deficient coverage. Source from Cisco

https://www.cis co.com/c/en/us/td/docs/wireless/technology/vowlan/troubleshooting/vowlan_troubleshoot/8_Site_Survey_RF_Design_Valid.html

A picture containing diagram Description automatically generated

The BFD (Bidirectional Forwarding Detection) is a protocol that detects link failures as part of the Cisco SD-WAN (Viptela) high availability solution, is enabled by default on all vEdge routers, and you cannot disable it.

https://community.cisco.com/t5/networking-documents/cam-content-addressable-memory-vs-tcam-ternary-content/ta-p/3107938

When using Ternary Content Addressable Memory (TCAM) inside routers it’s used for faster address lookup that enables fast routing.

In switches Content Addressable Memory (CAM) is used for building and lookup of mac address table that enables L2 forwarding decisions.

Besides Longest-Prefix Matching, TCAM in today’s routers and multilayer Switch devices are used to store ACL, QoS and other things from upper-layer processing.

SW1 has been configured with the following commands:

SW1(config)#monitor session 1 source remote vlan 50 SW1(config)#monitor session 2 source interface fa0/14 SW1(config)#monitor session 2 destination interface fa0/15

The session 1 on SW1 was configured for Remote SPAN (RSPAN) while session 2 was configured for local SPAN. For RSPAN we need to configure the destination port to complete the configuration.

Note: In fact we cannot create such a session like session 1 because if we only configure ―Source RSPAN VLAN 50‖ (with the command ―monitor session 1 source remote vlan 50‖) then we will receive a ―Type: Remote Source Session‖ (not ―Remote Destination Session‖).

Diagram, line chart Description automatically generated

Table Description automatically generated

+ accepts LISP encapsulated map requests: LISP map resolver

+ learns of EID prefix mapping entries from an ETR: LISP map server

+ receives traffic from LISP sites and sends it to non-LISP sites: LISP

proxy ETR

+ receives packets from site-facing interfaces: LISP ITR

Explanation

ITR is the function that maps the destination EID to a destination RLOC and then

encapsulates the original packet with an additional header that has the source IP address of

the ITR RLOC and the destination IP address of the RLOC of an Egress Tunnel Router (ETR).

After the encapsulation, the original packet become a LISP packet.

ETR is the function that receives LISP encapsulated packets, decapsulates them and

forwards to its local EIDs. This function also requires EID-to-RLOC mappings so we need to

point out an “map-server” IP address and the key (password) for authentication.

A LISP proxy ETR (PETR) implements ETR functions on behalf of non-LISP sites. A PETR is

typically used when a LISP site needs to send traffic to non-LISP sites but the LISP site is

connected through a service provider that does not accept no routable EIDs as packet

sources. PETRs act just like ETRs but for EIDs that send traffic to destinations at non-LISP

sites.

Map Server (MS) processes the registration of authentication keys and EID-to-RLOC

mappings. ETRs sends periodic Map-Register messages to all its configured Map Servers.

Map Resolver (MR): a LISP component which accepts LISP Encapsulated Map Requests,

typically from an ITR, quickly determines whether or not the destination IP address is part

of the EID namespace

These message logs inform that the radio channel has

been reset (and the AP must be down briefly). With

dynamic channel assignment (DCA), the radios can

frequently switch from one channel to another but it also

makes disruption. The default DCA interval is 10 minutes,

which is matched with the time of the message logs. By

increasing the DCA interval, we can reduce the number of

times our users are disconnected for changing radio

channels.

HTTP Status 204 (No Content) indicates that the server has successfully fulfilled the request and that there is no content to send in the response payload body.

The Option 43 hexadecimal string is assembled as a sequence of the TLV values for the Option 43 suboption: Type + Length + Value. Type is always the suboption code 0xf1. Length is the number of controller management IP addresses times 4 in hex. Value is the IP address of the controller listed sequentially in hex.

On this question, there is 1 controller with management interface IP addresses 172.16.50.5/24. The type is 0xf1. The length is 1 * 4 = 8 = 0x04. The mgmt IP addresses 172.16.50.5 translate to ac.10.32.05 (0xac103205). When the string is assembled, it yields f108c0a80a05c0a80a14. The Cisco IOS command that is added to the DHCP scope is:

option 43 hex f104ac103205

Diagrama Descripción generada automáticamenteMED Attribute:+ Optional nontransitive attribute (nontransitive means that we can only advertise MED to routers that are one AS away)+ Sent through ASes to external BGP neighbors+ Lower value is preferred (it can be considered the external metric of a route)+ Default value is 0

The TCP port 6514 has been allocated as the default port for syslog over Transport Layer Security

(TLS).

The ―ip sla 10‖ will ping the IP 192.168.10.20 every 3 seconds to make sure the connection is still up. We can configure an EEM applet if there is any problem with this IP SLA via the command ―event track 10 state down‖.

Diagram Description automatically generated

+ Fabric edge node: This fabric device (for example, access or distribution layer

device) connects

We cannot filter traffic that is originated from the local router (R3 in this case) so

we can only configure the ACL on R1 or R2. “Weekend hours” means from Saturday

morning through Sunday night so we have to configure: “periodic weekend 00:00

to 23:59”.

Note: The time is specified in 24-hour time (hh:mm), where the hours range from 0

to 23 and the minutes range from 0 to 59.

Chart, line chart Description automatically generated

The ―autocommand‖ causes the specified command to be issued automatically after the user logs in. When the command is complete, the session is terminated. Because the command can be any length and can contain embedded spaces, commands using the autocommand keyword must be the last option on the line. In this specific question, we have to enter this line ―username CCNP autocommand show running-config‖.

A fabric edge node provides onboarding and mobility services for wired users and devices (including fabric-enabled WLCs and APs) connected to the fabric. It is a LISP tunnel router (xTR) that also provides the anycast gateway, endpoint authentication, and assignment to overlay host pools (static or DHCP), as well as group-based policy enforcement (for traffic to fabric endpoints).

From Cisco's guide, under SDA roaming - When a client on a fabric enabled WLAN, roams from an access point to another access point on a different access-switch, it is called Inter-xTR, like a highway. Intra is within intra is between. Like interstate highways. That's how I remember. https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/config-guide/b_wl_16_10_cg/mobility.html

 Clustering lets you group multiple Firepower Threat Defense (FTD) units together as a single logical device. Clustering is only supported for the FTD device on the Firepower 9300 and the Firepower 4100 series. A cluster provides all the convenience of a single device (management, integration into a network) while achieving the increased throughput and redundancy of multiple devices.}

 Scrypt is safer than MD5, so answer A is wrong and answer D is correct

R1(config)#username user secret ?0 Specifies an UNENCRYPTED secret will follow5 Specifies a MD5 HASHED secret will follow8 Specifies a PBKDF2 HASHED secret will follow9 Specifies a SCRYPT HASHED secret will follow<0-9> Encryption types not explicitly specifiedLINE The UNENCRYPTED (cleartext) user secretLINE The UNENCRYPTED (cleartext) user secret

C:\Users\SANJAY~1\AppData\Local\Temp\SNAGHTML492d5ca9.PNG

During operation, an Egress Tunnel Router (ETR) sends periodic Map-Register messages to all its configured map servers.

Graphical user interface, text Description automatically generated

Lines (CON, AUX, VTY) default to level 1 privileges.

A picture containing table Description automatically generated

A picture containing graphical user interface Description automatically generated

SD-Access Wireless Architecture Control Plane Node –A Closer Look

Fabric Control-Plane Node is based on a LISP Map Server / Resolver

Runs the LISP Endpoint ID Database to provide overlay reachability information

+ A simple Host Database, that tracks Endpoint ID to Edge Node bindings (RLOCs)+ Host Database supports multiple types of Endpoint ID (EID), such as IPv4 /32, IPv6 /128* or MAC/48+ Receives prefix registrations from Edge Nodes for wired clients, and from Fabric mode WLCs for wireless clients+ Resolves lookup requests from FE to locate Endpoints+ Updates Fabric Edge nodes, Border nodes with wireless client mobility and RLOC information

https://www.rapidtables.com/convert/number/hex-to-decimal.html

(19)₁₆ = (1 × 16¹) + (9 × 16⁰) = (25)₁₀

Example: Configuring an ERSPAN Source Session on a WAN Interface

The following example shows how to configure more than one WAN interface in a single ERSPAN source monitor session. Multiple interfaces have been separated by a commas.

monitor session 100 type erspan-source

source interface Serial 0/1/0:0, Serial 0/1/0:6

Example: Configuring an ERSPAN Destination Session

The following example shows how to configure an ERSPAN destination session:

monitor session 2 type erspan-destination

destination interface GigabitEthernet1/3/2

destination interface GigabitEthernet2/2/0

source

erspan-id 100

ip address 10.10.0.1

Fabric Enabled WLC:

Fabric enabled WLC is integrated with LISP control plane. This WLC is responsible for AP image /Config, Radio Resource Management, Client Session management and roaming and all other wireless control plane functions.

For WLC Fabric Integration:

• Wireless Client MAC address is used as EID
• It inform about Wireless MAC address with its other information like SGT and Virtual Network Information
• VN information is mapped to VLAN on FEs
• WLC is responsible for updating Host Database tracking DB with roaming information

https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/cisco-sda-design-guide.html#FabricWLC

Both fabric WLCs and non-fabric WLCs provide AP image and configuration management, client session management, and mobility services. Fabric WLCs provide additional services for fabric integration such as registering MAC addresses of wireless clients into the host tracking database of the fabric control plane nodes during wireless client join events and supplying fabric edge node RLOC-association updates to the HTDB during client roam events.