Incercare Flashcards
Front
Back
<div>What does the following OSPF configuration command do?</div>
<div>(config-router)# area <i>area-id</i> range <i>ip-address</i> <i>netmask</i> [cost <i>n</i>]<br></br></div>
On ABR (not ASBR), this summarises the routes <b>from</b> the specified area<br></br>
Which command is used to summarise OSPF routes on an ASBR?
(config-router)# summary-address <i>prefix</i> <i>netmask</i>
How can routes be filtered on OSPF ABRs?
Two ways:<div>(config-router)# area <i>area-id</i> range <i>ip-address</i> <i>netmask</i> not-advertise - this will stop advertisements of the specified route (and all more specific routes) from the specified area<br></br></div><div><br></br></div><div>Or:</div><div><div>(config-router)# area <i>area-id</i> filter-list prefix <i>PREFIX-FILTER</i> in - filter routes received from the specified area</div>(config-router)# area <i>area-id</i> filter-list prefix <i>PREFIX-FILTER</i> out - filter routes advertised into the specified area<br></br></div>
What is the difference between E1 and E2 external route in OSPF
<div>E1 - Includes the cost of reaching the ASBR</div>
<div>E2 - Does not include the cost of reaching the ASBR</div>
How to select the type of external OSPF routes advertised by a router?
This is configured with a <b>metric-type</b> parameter for redistribute command<br></br><div>(config-router)# redistribute <i>source</i> subnets metric-type { 1 | 2 }</div>
What is a stubby area?
Stubby areas are guaranteed not to have an ASBR. Since they themselves don’t redistribute any external routes into OSPF, routers in a stubby area can safely assume that any traffic to external prefixes needs to go via ABR into area 0. Therefore, a stubby area does not receive LSA type 4 and 5.
What is a totally stubby area?
A totally stubby area is a type of a stubby aread in which ABRs simply act as a default gateway and don’t generate specific summary (type 3) LSAs. Instead, they just send a type 3 LSA with the default route. Therefore, LSAs 3 (exception: default route LSA), 4 and 5 are not used in totally stubby areas.
What is a <b>not-so-stubby area</b> (NSSA)
Not-so-stubby areas (NSSA) disallow type 4 and type 5 LSAs, but can actually have an ASBR. Since type 5 LSA are disallowed, a new type, type 7, is used to propagate external routes. Unlike type 5, type 7 LSAs can be summarised. They are translated into type 5 on ABRs.
What is a <b>totally not-so-stubby</b> area
A totally not-so-stubby area doesn’t allow type 3, 4 or 5 LSAs. They allow ASBR and use type 7 LSAs to propagate external routes. Since type 3 is disallowed, all routers received a default route to an ABR to get to the backbone.
What are the OSPF packet types?
<div>1. Hello – Establish neighborship and monitor</div>
<div>2. DBD – Database Description</div>
<div>3. LSR – Link-state requests</div>
<div>4. LSU – Link-state update</div>
<div>5. LSACK – Acknowledgement</div>
Commands to configure non-standard OSPF areas
<div>Stubby – (config-router)# area <i>n</i> stub</div>
<div>Totally stubby – (config-router)# area <i>n</i> stub no-summary</div>
<div>NSSA – (config-router)# area <i>n</i> nssa</div>
Totally NSSA – (config-router)# area <i>n</i> nssa no-summary
What is a type 1 LSA?
Router LSA – Describes router ID, interfaces (including status), IP addresses and masks
What is a type 2 LSA?
Network LSA – Describes DR and BDR IP addresses, subnet ID and mask
What is a type 3 LSA?
Summary LSA – Describes subnet ID and mask as well as RID of ABR that advertises this LSA. They retain the metric of from the originating area, adding the metric from the backbone area if necessary, giving an accurate measure of the cost to get to the destination network. Only one summary LSA for each prefix is created by an ABR even if there are multiple paths.
What is a type 4 LSA?
ASBR Summary - Describes a pair of ASBR and ABR routers, contains their IDs only. This lets other routers know how to get to an ASBR from another area.
What is a type 5 LSA?
External LSA – Describes information on routes redistributed into OSPF by an ASBR. This is flooded to all areas, except stub and NSSA areas, unchanged. Type 5 LSA cannot be summarised.
What is a type 7 LSA?
NSSA LSA – Replaces Type 5 in NSSAs and totally NSSAs. They are translated into type 5 LSAs on ABRs when sent to area 0. Type 7 LSAs can be summarised, unlike type 5.
What is an OSPF virtual link and how to configure it?
A virtual link allows attaching a non-backbone area to another non-backbone area. ABR will create a de facto tunnel with a router in area 0 and act as if it had an interface in area 0 itself. To configure this:<div><br></br></div><div>(config-router)# area <i>n</i> virtual-link <i>corresponding-router-ID</i> - this needs to be done on both routers. Use the transit area ID.</div>
How can OSPF AD be configured?
(config-router)# distance intra-area <i>AD</i> inter-area <i>AD</i> external <i>AD</i>
How to check the FIB?
show ip cef [<i>ip-address</i>/<i>prefix</i>]
How to check CEF adjacency table?
show adjacency
What are the STP Root port selection tiebreakers?
<div>1. Lower cost </div>
<div>2. Lowest priority of the advertising switch (if multiple switches are advertising)</div>
<div>3. Lower system MAC on the advertising switch (if multiple switches are advertising)</div>
<div>4. Lowest port priority on the advertising switch (if selecting among links to the same switch)</div>
<div>5. Lowest port number on the advertising switch (if selecting among links to the same switch)</div>
When two non-root switches are connected, ports on one must be blocked to avoid a loop. What tiebreakers are used to decide which switch should block the port?
<div>1. The switch with the lowest root path cost forwards, the other one blocks</div>
<div>2. The switch with the lowest priority forwards</div>
<div>3. The switch with the lowest system MAC forwards</div>
2. e - EGP
3.? - incomplete
This protocol and the origin code are no longer used.
- (config)# key chain chain-name
- (config-keychain)# key n
- (config-keychain-key)# key-string string
- (config-if)# ip authentication mode eigrp as-number md5
- (config-if)# ip authentication key-chain eigrp as-number chain-name
- Matching BGP versions
- Source IP for Open message matches the configured peer IP
- AS in the Open message matches the configure peer AS
- BGP Router ID (RID) must be present and unique.
- Security parameters (password, TTL) must be correct
- (config-router)# address-family afi safi - for IP traffic AFI is either ipv4 or ipv6, SAFI is either unicast or multicast. IPv4+unicast by default.
- (config-router-af)# neighbor ip-address activate
- Distribution lists
- Prefix lists
- AS path ACL
- Route maps
- There is no route to the tunnel destination address
- The source interface is down
- Router has detected recursive routing
- Keepalive is configured and has expired
- Tunnel interface is administratively disabled
- Tunnel is configured with IPSec and the associated IPSec SA is down.
- maim mode - 6 messages
- aggressive mode - 3 messages at the cost of reduced encryption security and leaking the identities of both IKE peers.
- Best effort - No QoS.
- Integrated Services (IntServ) - Applications reserver bandwidth using RSVP and CAC.
- Differentiated Services (DiffServ) - Packets are classified for shaping and policing purposes.
- IP Precedence (IPP) - deprecated
- Differentiated Service Code Point (DSCP)
- voice (AC_VO)
- video (AC_VI)
- best effort (AC_BE)
- background (AC_BK)
- Single-rate, two-colour
- Single-rate, three-colour (srTCM)
- Two-rate, three-colour (trTCM)
- Define class-maps to categorise traffic into classes
- Define policies for classes using policy-maps
- Apply policy maps to interfaces
1. To the secondary or tertiary configured WLC
2. To other discovered WLCs
- Devices use VRF to create multiple routing tables
- Control plane uses LISP Instance IDs to separate the VRFs.
- Data plane uses VXLAN VNID field to carry VN information.
- vManage NMS
- vSmart Controller
- vBond Orchestrator
- SD-WAN routers
- vAnalytics
- vEdge - Dedicated router running Viptela software.
- cEdge - Cisco router running a specialised IOS XE with SD-WAN functionality. Offers additional security features compared to vEdge.
- Source IP
- Destination IP
- Source port
- Destination port
- Layer 4 protocol type (TCP, UDP etc.), i.e. the IP protocol field
- ToS byte
- Input logical interface
- Allows customisation of key fields used to identify a flow
- Allows traffic sampling to reduce the CPU and memory load
- Allows configuration of different receivers for different flows
- Flow exporters - destinations where NetFlow data should be sent
- Flow records - defines key fields used to identify flows and non-key fields which should be collected
- Flow monitors - combines records with exporters, i.e. “this data should be sent to this receiver”. Monitors are then applied to interfaces to effect the configuration and start collecting data. Monitor caches data structured per the record attached and sends it to the exporters at moments determined by cache configuration (see configuration below)
- Flow samplers - Enable sampling. Flow samplers are applied to flow records.
- (config)# monitor session session-id filter vlan vlan-id
- (config-vlan)# remote-span
- (config)# monitor session session-id source {interface {ifname|ifrange} | vlan vlan-id} [rx|tx|both] - add a source interface/vlan. An interface range can be specified, and multiple sources can be configured for the same session if the command is repeated. By default, both ingress and egress traffic is captured, this can be overridden with tx (egress only) or rx (ingress only) keywords.
- (config)# monitor session session-id destination interface ifname - mirror traffic from source(s) to the specified interface.
- (config)# monitor session session-id source {interface {ifname|ifrange} | vlan vlan-id} [rx|tx|both] - add a source interface/vlan. An interface range can be specified, and multiple sources can be configured for the same session if the command is repeated.
- (config)# monitor session session-id destination remote vlan vlan-id
- (config)# monitor session session-id source remote vlan vlan-id
- (config)# monitor session session-id destination interface ifname
- (config)# monitor session session-id erspan-source - Enter ERSPAN configuration mode
- (config-mon-erspan-src)# source interface if-name
- (config-mon-erspan-src)# filter vlan-id (optional)
- (config-mon-erspan-src)# destination - enter destination configuration mode
- (config-mon-erspan-src-dst)# ip address ipaddress - configure destination IP
- (config-mon-erspan-src-dst)# erspan-id id - (optional) configure ERSPAN ID, used to differentiate different sessions from same source at the destination
- (config-mon-erspan-src-dst)# origin ip address ipaddress - (optional) configure source IP for this traffic
- Branch - Remote, more difficult to secure
- Campus - Numerous users
- Data centre - Highly critical
- Edge
- Cloud
- WAN
- Management - management of devices and systems
- Security intelligence - detection of emerging security threats
- Compliance - compliance with security and privacy regulations.
- Segmentation
- Threat defense
- Secure services
- Local Web Authentication (LWA) - the switch hosts the web server and redirects HTTP/HTTPS traffic to it. Credentials input via WebAuth are sent to the Radius server, which then either grants or denies access. Little customisation is possible. No VLAN assignment possible. dACL is possible.
- Central Web Authentication (CWA) - Uses Cisco ISE. Switch initiates MAB, Cisco ISE responds with an URL hosted on itself. HTTP/HTTPS traffic is redirected to this URL where the end user can authenticate via a web browser. VLAN assignment and dACL are possible.
- Cisco ISE
- Common Classification Policy Language (C3PL)
- Enhanced FlexAuth
- Dynamically - Cisco ISE assigns a tag depending on the outcome of the authentication process.
- Statically - SGT mapped statically to IPs, subnets, VLANs, interfaces etc.
- Security Group ACL (SGACL) - Distributed by Cisco ISE and installed on routers and switches
- Security Groupd Firewall (SGFW) - FW rules referencing SGTs and defined locally on the FW.
- Authentication using Galois Method Authentication Code (GMAC)
- Encryption+authentication using Galois/Counter Mode AES (GCM-AES)
- Security Association Protocol (SAP) - Cisco proprietary, used only between switches (uplink MACsec)
- MACsec Key Agreement (MKA) - Open standard, used both between switches (uplink MACsec) and between the edge switch and end device (downlink MACsec)
- (config)# mac access-list {standard | extended} acl-name
- (config-ext-macl)# {deny | permit} source destination
- (config-if)# mac access-group acl-name {in | out}
- Define an ACL to match IP or Ethernet traffic
- Create a VLAN access map to match ACL with an action (forward or drop)
- Apply the VLAN access map to a VLAN
- (config)# vlan access-map name seq
- (config-access-map)# match {ip address {acl-number | acl-name} | mac address acl-name}
- (config-access-map)# action {forward | drop} [log]
- (config)# vlan filter access-map-name vlan-list list - the list can be a single number, a range, or several comma-separated numbers and ranges
- Inbound PACL
- Inbound VACL
- Outbound VACL
- Inbound PACL
- Inbound VACL
- Inbound RACL
- Outbound RACL
- Outbound VACL
- Passwords configured directly on lines - not recommended
- Local usernames and passwords - recommended as fallback
- AAA - recommended as the primary method
- (config-line)# login - enable password checking for the specified line
- (config-line)# password {[0] password | 7 encrypted-string} - specify password. It will be stored in cleartext unless (badly) encrypted if service password-encryption is enabled.
- Self-zone - contains the device’s own IPs. Any host-inbound or host-outbound traffic will cross this zone’s boundary.
- Default zone - all interfaces that are not explicitly assigned to another zone. Default zone needs to be explicitly enabled, otherwise all traffic to and from interfaces not assigned to a zone is dropped.
- Create zones
- Assign interfaces to zones
- Create inspection class-maps to classify traffic
- Create inspection policy-maps to define actions for each traffic class
- drop [log]
- pass [log]
- inspect
- Docker
- LXD
- rkt
- Linux-VServer
- Windows Containers
- Open vSwitch Data Plane Development Kit (OVS-DPDK)
- PCI passthrough
- Single-root I/O virtualisation (SR-IOV)
- Hardware layer - x86-based physical hardware that runs other components. Cisco offers tailor-made hardware packages:
- Network Functions Virtualization Infrastructure Software (NFVIS) - Linux-based OS that provides virtualisation and works with orchestration, management and monitoring software.
- VNF - Both Cisco (vISR, ASAv, NGFWv, vEdge, cEdge, vWAAS, vWLC) and third party
- Management and Orchestration (MANO) - provided by Cisco DNA Center
- Enterprise Network Compute System (ENCS)
- Cisco 4000 Series ISR + UCS E-Series
- UCS C-Series
- Cisco Cloud Services Platforms
- request running configuration and device’s state - request all or part of configuration from a datastore - Edit configuration on a datastore - Copy configuration to another data store - Deletes configuration from a datastore
(config)# event manager session cli username username
- Ansible
- Salt SSH
- Puppet Bolt
- Puppet
- Salt
- Chef
- (config)# spanning-tree mode mst - enable MSTP
- (config)# spanning-tree mst configuration - enter MSTP configuration mode
- (config-mst)# name region-name - configuration name for the MST region
- (config-mst)# revision no - Configuration revision for the MST region
- (config-mst)# instance msti vlan vlan-list - associate VLANs with MSTI
- (config)# spanning-tree bpduguard default
- (config)# spanning-tree bpduguard {enable | disable}
- (config-if)# ip nat inside – declare the interface to be on the internal network
- (config-if)# ip nat outside – declare the interface to be on the outside
- (config)# ip nat inside source static inside_local inside_global – create a static mapping. This command needs to be issued separately for each mapping.
- (config-if)# ip nat inside – declare the interface to be on the internal network>
- (config-if)# ip nat outside – declare the interface to be on the outside
- (config)# ip access-list {acl_number | acl_name} rule – create/populate an ACL to specify which inside local addresses can use NAT
- (config)# ip nat pool pool-name first-address last-address netmask subnet-mask – define a range of inside global addresses to use. Netmask is used only for verification: if the address range does not fit the subnet as determined by netmask, the command is rejected.
- (config)# ip nat inside source list {acl_number | acl_name} pool pool-name – enable dynamic NAT and allow mappings between inside local addresses permitted by the specified ACL and inside global addresses in the pool
- (config-if)# ip nat inside – declare the interface to be on the internal network
- (config-if)# ip nat outside – declare the interface to be on the outside
- (config)# ip access-list {acl_number | acl_name} rule – create/populate an ACL to specify which inside local addresses can use NAT
- (config)# ip nat inside source list {acl_number | acl_name} interface ifname overload – allow dynamic mappings between inside local addresses, permitted by the specified ACL, and ports and the inside global interface ifname and its ports.