Question 1mediummultiple choice
Read the full AI and Network Operations explanation →CCNA AI and Network Operations • Complete Question Bank
Complete CCNA AI and Network Operations question bank — all 0 questions with answers and detailed explanations.
Drag a concept onto its matching description — or click a concept then click the description.
Lightweight structured data format often used in API payloads
Architectural style commonly using HTTP methods for software interaction
Defined interface that allows software systems to communicate
Data modeling language used to describe network information
Drag a concept onto its matching description — or click a concept then click the description.
Direction used when applications communicate with the controller
Direction used when the controller communicates with infrastructure devices
Central platform used for policy and management coordination
Software interface used for defined communication between systems
Drag a concept onto its matching description — or click a concept then click the description.
A set of key-value pairs enclosed in braces
An ordered list enclosed in square brackets
The name that identifies a field
The content associated with a key
Drag a concept onto its matching description — or click a concept then click the description.
Central platform used to coordinate policy and management
Defined software interface for interaction between systems
Lightweight structured data format
Data modeling language for network information
Drag a concept onto its matching description — or click a concept then click the description.
Credential-like value used to help control API access
Secure transport commonly used for API communication
Centralized management and policy platform
Application-facing interface used to communicate with the controller
Drag a concept onto its matching description — or click a concept then click the description.
A lightweight structured data format
An ordered list of values or objects
A name used to identify a field in structured data
A data modeling language used to describe network information
Drag a concept onto its matching description — or click a concept then click the description.
Group of key-value pairs
Ordered list of items
Field name
Content associated with a field
Drag a concept onto its matching description — or click a concept then click the description.
Centralized management and policy platform
Defined software interface for communication between systems
Architectural style commonly using HTTP methods
Lightweight structured data format
Drag a concept onto its matching description — or click a concept then click the description.
Credential-like value used to help control API access
Encrypted transport commonly used for secure API communication
Verification of identity
Determination of allowed actions after identity is verified
Drag a concept onto its matching description — or click a concept then click the description.
Named piece of structured data
Content assigned to a field
Group of related key-value pairs
Ordered list of items
Drag a concept onto its matching description — or click a concept then click the description.
HTTP method commonly used to retrieve information
HTTP method commonly used to update or replace a resource
Secure transport for the API exchange
Credential-like value used to help control API access
Drag a concept onto its matching description — or click a concept then click the description.
Retrieve existing information
Submit or create data
Update or replace an existing resource
Remove a resource
Drag a concept onto its matching description — or click a concept then click the description.
Field name
Content associated with a field
Group of key-value pairs
Ordered list of items
Drag a concept onto its matching description — or click a concept then click the description.
Centralized management or policy platform
Application-facing interface to the controller
Structured data format commonly exchanged
Credential-like value used to help control access
Drag a concept onto its matching description — or click a concept then click the description.
Centralized management or policy platform
Defined software interface used for communication
Secure transport commonly used for the interaction
Structured data format carried in API messages
Drag a concept onto its matching description — or click a concept then click the description.
Management or policy platform
Software interface for communication
Structured data format
Secure transport for the communication
Drag a concept onto its matching description — or click a concept then click the description.
Structured payload format
Secure transport for the interaction
Credential-like access value
Specific API target or path
Drag a concept onto its matching description — or click a concept then click the description.
Describes the intended action such as retrieve or delete
Identifies the target resource path
Supports access control for the request
Provides the structured payload format
Drag a concept onto its matching description — or click a concept then click the description.
Lightweight data-interchange format
Data modeling language for structured configuration and state
Architectural style using HTTP methods such as GET and POST
Streaming operational data from devices to collectors
Drag a concept onto its matching description — or click a concept then click the description.
Lightweight key-value data representation
Tag-based markup format
Data modeling language for network configuration and state
Uses HTTP methods such as GET and POST to work with resources
Drag a concept onto its matching description — or click a concept then click the description.
Retrieve information
Create a new resource
Replace or update a resource representation
Remove a resource
Drag a concept onto its matching description — or click a concept then click the description.
Identifies deviations from normal network behavior, such as sudden traffic spikes or unusual login attempts.
Uses historical data and machine learning to forecast future network events, such as capacity needs or potential failures.
Translates high-level business intent into automated network configurations and policies, ensuring continuous alignment.
Trains a model on labeled data to classify or predict outcomes, e.g., identifying known attack signatures.
Discovers hidden patterns or clusters in unlabeled data, e.g., grouping similar traffic flows.
Learns optimal actions through trial-and-error interactions with the network environment, e.g., dynamic routing adjustments.
Drag a concept onto its matching description — or click a concept then click the description.
Autonomous entity that perceives its environment and takes actions to achieve goals
Mechanism that allows an AI agent to invoke external functions or APIs
Workflow that automatically detects, diagnoses, and corrects network issues without human intervention
Technique that combines LLMs with external knowledge retrieval for accurate responses
Approach that translates high-level business intent into network configuration and assurance
Training method where an agent learns optimal actions through rewards and penalties
Drag a concept onto its matching description — or click a concept then click the description.
Alert: immediate action needed
Notification: normal but significant condition
Reference clock (e.g., atomic clock or GPS)
NTP client synchronized to a stratum 1 server
Configures the device as an NTP client
Displays syslog messages in the buffer
Drag a concept onto its matching description — or click a concept then click the description.
Uses community strings for authentication, transmitted in plaintext
Provides authentication and encryption via AuthPriv security model
Cisco-proprietary flow monitoring that caches flows and exports records
IETF standard based on NetFlow v9 for flexible flow export
Push model that continuously streams operational data to a collector
Drag a concept onto its matching description — or click a concept then click the description.
Uses community strings for authentication and supports Get/Set operations
Provides authentication and encryption via User-based Security Model (USM)
Cisco-proprietary flow monitoring that exports packet-level flow records
Standardized version of NetFlow defined in RFC 7011
Push-based model that continuously streams device operational data to a collector
Drag a concept onto its matching description — or click a concept then click the description.
A data modeling language used to define the structure of configuration and state data for network devices
A protocol that uses XML and SSH to transport configuration and state data between a client and a network device
A protocol that uses HTTP methods (GET, PUT, POST, DELETE) to access YANG-defined data on a network device
A file that defines the schema, including data types, groupings, and constraints for network configuration
A node in a YANG data model that groups related leaf nodes and other containers together
A NETCONF operation used to modify the configuration of a network device
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag a concept onto its matching description — or click a concept then click the description.
Manager-agent model; UDP transport; MIB-based data
Flow-based model; UDP transport; template-based data
Subscription-based model; gRPC/TCP transport; structured data (YANG/JSON)
Event-based model; UDP transport; text-based messages
Probe-based model; UDP/TCP transport; latency/jitter metrics
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
R1#show running-config | include ntp|logging logging host 192.0.2.100 logging trap debugging ! R1#show ntp status Clock is unsynchronized, stratum 16, no reference clock nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**10 ntp uptime is 0 minutes, resolution 4000 ms reference time is 0x00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900) clock offset is 0.0000 msec, root delay is 0.00 msec root dispersion is 0.00 msec, peer dispersion is 0.00 msec loopfilter state is 'NC' (No Connection) R1#show ntp associations address ref clock st when poll reach delay offset disp *~0.0.0.0 .INIT. 16 - 64 0 0.000 0.000 16000. * sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured
R1# show running-config | section ntp|logging
ntp server 198.51.100.10
logging host 203.0.113.5
logging trap debugging
!
R1# show ntp status
Clock is unsynchronized, stratum 16, no reference clock
R1# show ntp associations
address ref clock st when poll reach delay offset disp
*~198.51.100.10 .INIT. 16 - 1024 0 0.0 0.0 16000.
~ (synchronized), * (candidate), # (selected), + (peer), - (outlier)
R1# show logging
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited)
Console logging: level debugging, 0 messages logged
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 0 messages logged
Trap logging: level debugging, 0 message lines logged
Logging to 203.0.113.5 (udp port 514, audit disabled)
0 message lines loggedR1# show ntp status
Clock is unsynchronized, stratum 16, no reference clock
nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**10
reference time is 0.0.0.0 (00:00:00.000 UTC Mon Jan 1 2000)
clock offset is 0.0000 msec, root delay is 0.00 msec
root dispersion is 0.00 msec, peer dispersion is 0.00 msec
loopfilter state is 'CTRL' (Normal Controlled Loop)
R1# show run | section ntp
ntp server 203.0.113.10
R1# show run | include logging
logging host 198.51.100.20
no logging console
R1# show logging
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes)
Console logging: disabled
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 0 messages logged
Trap logging: level informational, 0 messages logged
Logging to 198.51.100.20 (udp port 514, audit disabled,
link up)R1#show running-config | section ntp|logging
ntp server 203.0.113.10
logging host 198.51.100.50
logging trap debugging
!
interface Loopback0
ip address 192.0.2.1 255.255.255.255
!
R1#show ntp status
Clock is unsynchronized, stratum 16, no reference clock
nominal freq: 250.0000 Hz, actual freq: 250.0000 Hz, precision: 2**10
reference time: 0.0.0.0 00:00:00.000 UTC Mon Jan 1 2000
clock offset: 0.0000 msec, root delay: 0.00 msec
root dispersion: 0.00 msec, peer dispersion: 0.00 msec
loopfilter state: 'CTRL' (Normal Controlled), drift: 0.00000000 s/s
system poll interval: 64, last update was 0 sec ago.
R1#show ntp associations
address ref clock st when poll reach delay offset disp
*~203.0.113.10 .INIT. 16 - 64 0 0.00 0.00 16000.
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured
R1#show logging | include Logging
Syslog logging: enabled
Console logging: level debugging, 0 messages logged
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 0 messages logged
Trap logging: level debugging, 0 messages logged
Logging to 198.51.100.50 (udp port 514, audit disabled, link up),
2 messages logged, level debuggingR1#show ntp status Clock is unsynchronized, stratum 16, no reference clock nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**10 reference time is 0.0.0.0 (00:00:00.000 UTC Mon Jan 1 2000) clock offset is 0.0000 msec, root delay is 0.00 msec root dispersion is 0.00 msec, peer dispersion is 0.00 msec loopfilter state is 'CTRL' (Normal Controlled Loop) system poll interval is 64, last update was 0 sec ago. R1#show ntp associations address ref clock st when poll reach delay offset disp *~0.0.0.0 0.0.0.0 16 - 64 0 0.00 0.00 16000. * sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured R1#show run | section logging logging host 198.51.100.20 logging trap informational
R1#show running-config | include snmp
Building configuration...
Current configuration : 1234 bytes
!
snmp-server community public RO
!
end
R1#show running-config | include flow
Building configuration...
Current configuration : 1234 bytes
!
!
end
R1#show ip flow export
Flow export v9 is disabled for main cache
Export source and destination details :
No Flow Export destinations configured
This is a main cache
R1#show ip cache flow
IP packet size distribution (0 total packets):
...
(output truncated – no flows captured)Current running-config (relevant sections): ! hostname R1 ! interface GigabitEthernet0/0/0 ip address 192.168.1.1 255.255.255.252 duplex auto speed auto media-type rj45 no shutdown ! interface Loopback0 ip address 10.0.0.1 255.255.255.255 ! ip route 0.0.0.0 0.0.0.0 192.168.1.2 ! snmp-server community CourseivaRO RO ! snmp-server enable traps snmp authentication linkdown linkup ! snmp-server host 192.0.2.100 version 2c CourseivaRO ! ! Note: SNMPv3 user 'monitor' is not yet configured. NetFlow not configured. !
R1#show running-config | section interface GigabitEthernet0/0 interface GigabitEthernet0/0 ip address 192.168.1.1 255.255.255.252 description Link to R2 no shutdown ! R1#show ip interface brief Interface IP-Address OK? Method Status Protocol GigabitEthernet0/0 192.168.1.1 YES NVRAM up up GigabitEthernet0/1 192.168.2.1 YES NVRAM up up R1#show restconf RESTCONF enabled on port 443
R1# show running-config | section interface GigabitEthernet0/0 interface GigabitEthernet0/0 ip address 10.0.0.1 255.255.255.252 duplex auto speed auto media-type rj45 no shutdown ! R1# show ip interface brief Interface IP-Address OK? Method Status Protocol GigabitEthernet0/0 10.0.0.1 YES NVRAM up up GigabitEthernet0/1 unassigned YES NVRAM administratively down down Loopback0 10.0.0.11 YES NVRAM up up
R1#show running-config | section interface GigabitEthernet0/1 interface GigabitEthernet0/1 ip address 192.0.2.1 255.255.255.0 shutdown ! R1#show ip interface brief | include Gig0/1 GigabitEthernet0/1 192.0.2.1 YES manual administratively down down
R1#show running-config | section interface GigabitEthernet0/0 interface GigabitEthernet0/0 ip address 192.168.1.1 255.255.255.0 description To_R2 no shutdown ! R1#show ip interface brief Interface IP-Address OK? Method Status Protocol GigabitEthernet0/0 192.168.1.1 YES NVRAM up up
R1#show running-config | section interface GigabitEthernet0/0/0
interface GigabitEthernet0/0/0
ip address 198.51.100.1 255.255.255.0
description Link-to-R2
no shutdown
!
R1#show ip interface brief | include GigabitEthernet0/0/0
GigabitEthernet0/0/0 198.51.100.1 YES manual up up
RESTCONF base URI: https://198.51.100.1:443/restconf
Curl attempt (GET) — correct:
curl -k -u admin:cisco -H "Accept: application/yang-data+json" https://198.51.100.1/restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0%2F0%2F0
Curl attempt (PATCH) — incorrect (wrong YANG path):
curl -k -u admin:cisco -X PATCH -H "Content-Type: application/yang-data+json" -d '{"Cisco-IOS-XE-native:description":"WAN-Link-to-R2"}' https://198.51.100.1/restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0%2F0%2F0/description
Response to PATCH above: 400 Bad Request - "YANG path does not match data: expected 'Cisco-IOS-XE-native:interface' at root"
Curl attempt (PATCH) — correct:
curl -k -u admin:cisco -X PATCH -H "Content-Type: application/yang-data+json" -d '{"Cisco-IOS-XE-native:description":"WAN-Link-to-R2"}' https://198.51.100.1/restconf/data/Cisco-IOS-XE-native:native/interface/GigabitEthernet=GigabitEthernet0%2F0%2F0/description
Response to correct PATCH: 204 No ContentDrag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag a concept onto its matching description — or click a concept then click the description.
Tool employing a pull mechanism for node configuration using a proprietary DSL
Framework that uses Ruby-coded recipes within a client-server deployment model
Solution providing agentless orchestration via SSH and YAML-written playbooks
High-level programming language utilized for scripting network automation tasks
Web-based interface for programmatic device management using HTTP methods
Given the JSON snippet below, what is the value of hostname?
{
"device": {
"hostname": "R1",
"mgmt_ip": "192.0.2.10"
}
}A REST API query returns this JSON snippet:
{
"interface": {
"name": "GigabitEthernet1",
"admin-status": "up",
"oper-status": "down"
}
}What does this indicate?
A network automation script sends this HTTP request to a controller API:
POST /api/v1/devices
What does the POST method typically indicate in a RESTful API?
A controller API returns this data:
{
"device": {
"hostname": "Dist-1",
"interfaces": [
{"name": "Gig0/0", "status": "up"},
{"name": "Gig0/1", "status": "down"}
]
}
}Which statement is correct?
Goal: Read existing data only
Drag a concept onto its matching description — or click a concept then click the description.
Retrieve existing information
Submit or create data
Update or replace an existing resource
Remove a resource
Drag a concept onto its matching description — or click a concept then click the description.
HTTP method commonly used to retrieve data
HTTP method commonly used to submit or create data
Credential-like value used to help control API access
Structured data format often used in API payloads
Drag a concept onto its matching description — or click a concept then click the description.
Centralized management or policy platform
Defined software interface for communication
Lightweight structured data format
Secure transport commonly used for API access
Drag a concept onto its matching description — or click a concept then click the description.
Encrypted transport commonly used for API communication
Architectural style often using HTTP methods
Structured data format commonly used in API payloads
Credential-like value often used to control API access
Drag a concept onto its matching description — or click a concept then click the description.
Central platform used to coordinate policy and management
Application-facing interface used to communicate with the controller
Lightweight structured data format used in API payloads
Secure transport commonly used for API communication
Drag a concept onto its matching description — or click a concept then click the description.
Defined software interface used for communication
Structured data format
Secure transport for the communication
Credential-like value used to help control access
Drag a concept onto its matching description — or click a concept then click the description.
Centralized management or policy platform
Application-facing interface to the controller
Structured data format commonly used in API payloads
Credential-like value used to help control API access
Drag a concept onto its matching description — or click a concept then click the description.
Software interface used for communication
Structured data format
Secure transport for the communication
Credential-like value used to help control access
Drag a concept onto its matching description — or click a concept then click the description.
Retrieve information
Submit or create data
Update or replace a resource
Remove a resource
Drag a concept onto its matching description — or click a concept then click the description.
Field name
Content associated with a field
Group of key-value pairs
Ordered list of items
Drag each automation or API concept from the left to its corresponding description on the right. Not all descriptions are used.
Concepts: - Northbound API - Southbound API - JSON - HTTPS
Drag a concept onto its matching description — or click a concept then click the description.
Application-facing interface to the controller
Controller-facing interface toward managed infrastructure
Structured data format
Secure transport for API communication
Drag a concept onto its matching description — or click a concept then click the description.
Structured representation of configuration or state
Common machine-readable data format
Specific API target or path
Credential-like access value
Drag a concept onto its matching description — or click a concept then click the description.
Retrieve information
Create or submit data
Update or replace a resource
Remove a resource
Drag a concept onto its matching description — or click a concept then click the description.
Structured data format
Data-modeling language
Access-related value used by a client
Secure transport for API communication
Drag a concept onto its matching description — or click a concept then click the description.
Target resource path
Requested action such as retrieve or delete
Access-related value carried by the client
Structured payload format
Drag a concept onto its matching description — or click a concept then click the description.
Data modeling language for structured network data
Lightweight text format for structured data exchange
Programmatic interface exposed by a system
Credential presented to authenticate or authorize a request
Drag a concept onto its matching description — or click a concept then click the description.
Retrieve a resource
Create a new resource
Update or replace a resource
Remove a resource
GET /api/v1/interfaces Headers: Accept: application/json Response: HTTP/1.1 401 Unauthorized
Request: GET /dna/intent/api/v1/network-device Authorization: Bearer <token>
POST /auth -> token received Subsequent GET /devices uses Authorization header
POST /dna/intent/api/v1/template-programmer/project HTTP/1.1 Host: controller.example.com X-Auth-Token: expired-token HTTP/1.1 401 Unauthorized
Drag a concept onto its matching description — or click a concept then click the description.
Lightweight structured data format often used in API responses
Data modeling language for network configuration and state
Architecture style that commonly uses HTTP methods such as GET and POST
Credential or value used to authorize API requests
Snippet:
{
"hostname": "R1",
"enabled": true,
"vlans": [10,20,30]
}Drag a concept onto its matching description — or click a concept then click the description.
Identifies deviations from normal network behavior, such as unusual traffic spikes or security threats.
Uses historical data and ML models to forecast future network events, like congestion or device failures.
Translates business intents into network policies and continuously verifies that the network meets those intents.
Trains a model using labeled data to classify or predict outcomes, such as identifying specific types of traffic.
Discovers hidden patterns or clusters in unlabeled data, often used for anomaly detection or traffic profiling.
Optimizes network decisions through trial and error, using rewards to learn optimal actions over time.
R1# show ntp status Clock is synchronized, stratum 16, reference is 0.0.0.0 nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**10 ntp uptime is 100 minutes, resolution is 4000 msec reference time is D8C4E1C0.00000000 (12:34:56.000 UTC Mon Mar 15 2021) clock offset is 0.0000 msec, root delay is 0.00 msec root dispersion is 0.00 msec, peer dispersion is 0.00 msec R1# show ntp associations address ref clock st when poll reach delay offset disp *~192.0.2.1 0.0.0.0 16 - 64 0 0.000 0.000 16000. * sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured
Router# show ntp status Clock is synchronized, stratum 16, reference is 0.0.0.0 nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**10 reference time is 0.0.0.0 clock offset is 0.0000 msec, root delay is 0.00 msec root dispersion is 0.00 msec, peer dispersion is 0.00 msec Router# show ntp associations address ref clock st when poll reach delay offset disp *~192.168.1.10 .INIT. 16 - 64 0 0.0 0.00 16000. * sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured Router# show running-config | include ntp ntp server 192.168.1.10
Drag a concept onto its matching description — or click a concept then click the description.
Emergency: system is unusable
Debugging: detailed debug messages
Reference clock (e.g., atomic clock or GPS)
Unsynchronized or maximum usable stratum
Configures an IOS-XE device as an NTP client
Displays NTP synchronization state and stratum
Drag a concept onto its matching description — or click a concept then click the description.
Uses XML-encoded RPCs over SSH for network device configuration
Uses HTTP/HTTPS methods (GET, POST, PUT, DELETE) with JSON or XML
Data modeling language that defines the structure of configuration and state data
High-performance RPC framework using Protocol Buffers and HTTP/2
Vendor-neutral YANG data models for network configuration and monitoring
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag a concept onto its matching description — or click a concept then click the description.
Emergency – system is unusable
Alert – immediate action needed
Critical – critical condition
Error – error condition
Warning – warning condition
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag a concept onto its matching description — or click a concept then click the description.
Data modeling language used to define configuration and state data structures
Protocol using XML over SSH for configuration management and transactional operations
RESTful API using HTTP methods (GET, PUT, POST, DELETE) over HTTPS
Operation to modify configuration with options like merge, replace, create, delete
HTTP method used for partial updates to a resource
R1#show ntp status
Clock is unsynchronized, stratum 16, no reference clock
nominal freq is 250.00000 Hz, actual freq is 250.00000 Hz, precision is 2**10
reference time is 0.0.0.0 (00:00:00.000 UTC Mon Jan 1 2000)
clock offset is 0.0000 msec, root delay is 0.00 msec
root dispersion is 0.00 msec, peer dispersion is 0.00 msec
loopfilter state is 'CTRL' (Normal Controlled Loop)
R1#show ntp associations
address ref clock st when poll reach delay offset disp
*~0.0.0.0 0.0.0.0 16 - 64 0 0.00 0.00 16000.
* sys.peer, # selected, + candidate, - outlyer, x falseticker, ~ configured
R1#show logging
Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
Console logging: level debugging, 0 messages logged
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 0 messages logged
Trap logging: level critical, 0 messages logged
Logging to: 203.0.113.50 (udp port 514, audit disabled, link up)
R1#show running-config | section ntp
ntp server 192.0.2.10
!
R1#show running-config | section logging
logging host 203.0.113.50
!R1#show running-config | include ntp|logging ntp server 203.0.113.5 logging host 192.0.2.20 logging trap debugging ! R1#show ntp status Clock is unsynchronized, stratum 16, no reference clock R1#show ip interface brief | include Loopback0 Loopback0 10.0.0.1 YES manual up up R1#
R1#show ntp status Clock is synchronized, stratum 16, reference is 127.127.7.1 nominal freq is 250.0000 Hz, actual freq is 250.0000 Hz, precision is 2**10 reference time is D3A4B2C1.00000000 (00:00:00.000 UTC Mon Jan 1 2024) clock offset is 0.0000 msec, root delay is 0.00 msec root dispersion is 0.00 msec, peer dispersion is 0.00 msec loopfilter state is 'CTRL' (Normal), drift is 0.000000000 s/s system poll interval is 64, last update was 0 sec ago. R1#show ntp associations address ref clock st when poll reach delay offset disp *~127.127.7.1 .LOCL. 16 25 64 377 0.000 0.000 0.000 * sys_peer, # selected, + candidate, - outlyer, x falseticker, ~ configured R1#show running-config | include ntp|logging ntp server 203.0.113.10 logging host 198.51.100.20 logging trap warnings
R1#show running-config | include ntp|logging ntp server 192.0.2.1 logging host 203.0.113.10 logging trap debugging ! R1#show ntp status Clock is unsynchronized, stratum 16, no reference clock R1#show ntp associations address ref clock st when poll reach delay offset disp *~192.0.2.1 .INIT. 16 - 64 0 0.0 0.0 0.0 ~198.51.100.1 .INIT. 16 - 64 0 0.0 0.0 0.0
R1#show running-config | section snmp|flow Building configuration... Current configuration : 1234 bytes ! snmp-server community public RO snmp-server community private RW ! ! No trap or NetFlow configuration exists ! interface GigabitEthernet0/0 ip address 10.0.0.1 255.255.255.252 duplex auto speed auto media-type rj45 ! interface Loopback0 ip address 10.255.255.1 255.255.255.255 ! end
R1#show running-config | section snmp|ip flow Building configuration... Current configuration : 1234 bytes ! ip flow-export source Loopback0 ip flow-export destination 203.0.113.100 2055 ! end R1#show ip cache flow IP packet size distribution (96 total packets): 1-32 64 96 128 160 192 224 256 288 320 352 384 416 448 480 .0000 .0000 .0000 .0000 .0000 .0000 .0000 .0000 .0000 .0000 .0000 .0000 .0000 .0000 .0000 ... (no flow records shown)
R1# show running-config | section snmp|ip flow ! ip flow-export destination 203.0.113.20 2055 ! snmp-server community public RO ! R1# show snmp Chassis: SNMPv2c Community strings: public (read-only) No SNMPv3 users configured. No trap configuration. R1# show ip cache flow IP packet size distribution: ... No NetFlow export information configured.
R1#show running-config | section snmp snmp-server community publicRW RO snmp-server location Datacenter snmp-server contact admin@example.com ! R1#show running-config | include ip flow i R1#show ip cache flow No flow cache configured.
R1#show running-config | section snmp|ip flow ! ! No SNMP or NetFlow configuration currently exists ! Only the following lines are present: ! snmp-server community public RO !
Current running-config of R1 (relevant sections): ! hostname R1 ! interface GigabitEthernet0/0 ip address 192.0.2.1 255.255.255.252 no shut ! interface GigabitEthernet0/1 ip address 198.51.100.1 255.255.255.0 no shut ! ip route 0.0.0.0 0.0.0.0 192.0.2.2 ! end
R1#show running-config | section snmp snmp-server community public RO snmp-server community private RW ! R1#show running-config | include flow-export no ip flow-export destination no ip flow-export version ! R1#show ip interface brief Interface IP-Address OK? Method Status Protocol GigabitEthernet0/0 10.0.0.1 YES NVRAM up up GigabitEthernet0/1 203.0.113.1 YES NVRAM up up Loopback0 192.0.2.1 YES NVRAM up up !
R1#show running-config | section snmp|flow
Building configuration...
!
ip flow-export source GigabitEthernet0/0
ip flow-export version 9
!
snmp-server community NetOpsRO RO
snmp-server enable traps snmp
snmp-server host 192.0.2.10 version 2c TrapComm
!
end
R1#show ip cache flow
IP packet size distribution (0 total packets):
(No flow data yet)
R1#R1#show running-config | section interface GigabitEthernet0/1 interface GigabitEthernet0/1 ip address 10.0.0.1 255.255.255.252 duplex auto speed auto media-type rj45 ! R1#show ip interface brief Interface IP-Address OK? Method Status Protocol GigabitEthernet0/0 192.0.2.1 YES NVRAM up up GigabitEthernet0/1 10.0.0.1 YES NVRAM up up Loopback0 203.0.113.1 YES NVRAM up up
R1# show running-config | section interface GigabitEthernet0/1 interface GigabitEthernet0/1 description Original description ip address 192.0.2.1 255.255.255.252 no shutdown ! R1# show ip interface brief Interface IP-Address Status Protocol GigabitEthernet0/0 203.0.113.1 up up GigabitEthernet0/1 192.0.2.1 up up Loopback0 10.1.1.1 up up
R1#show running-config | section interface GigabitEthernet0/0
interface GigabitEthernet0/0
ip address 192.0.2.1 255.255.255.0
no shutdown
!
R1#show ip interface brief
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0 192.0.2.1 YES manual up up
RESTCONF base URI: https://192.0.2.1/restconf
Example GET URI (correct):
GET /restconf/data/ietf-interfaces:interfaces/interface=GigabitEthernet0/0
Accept: application/yang-data+json
Example PATCH URI (correct):
PATCH /restconf/data/Cisco-IOS-XE-native:native/interface/GigabitEthernet=0/0
Content-Type: application/yang-data+json
Body: {"Cisco-IOS-XE-native:interface":{"GigabitEthernet":[{"name":"0/0","shutdown":true}]}}R1#show running-config | section interface GigabitEthernet0/0 interface GigabitEthernet0/0 ip address 192.168.1.1 255.255.255.252 duplex auto speed auto ! R1#show ip interface brief Interface IP-Address OK? Method Status Protocol GigabitEthernet0/0 192.168.1.1 YES NVRAM up up
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.