Appendix C

Memory Tables Answer Key

Chapter 1

Table 1-4 SONET and SDH Differences

Differences SONET SDH

Regional Primarily used in Commonly used in in-

North America; sets ternational contexts; the
the standard for op- dominant standard in
tical Europe and many other
telecommunications parts of the world

Terminology Uses Optical Carrier Uses Synchronous

(OC) levels to specify Transport Module (STM)
data rates (e.g., OC-3, levels (e.g., STM-1, STM-
OC-12) 4) to specify data rates

Frame Uses synchronous Uses synchronous

Structures frames; the basic frames as well; the basic
unit is the unit is the Synchronous
Synchronous Transport Module (STM-
Transport Signal 1 1) frame
(STS-1) frame

Frame Overhead Uses Transport Uses Administrative

Overhead, Section Unit (AU) overhead,
Overhead, Line Multiplex Section
Overhead, and Path Overhead (MSOH), and
Overhead. Path Overhead (POH)

Error Detection Uses Bit Interleaved Has its own version of

Parity 8 (BIP-8) BIP-8

Network Uses a synchronization network called the

Synchronization Synchronous Status Message (SSM)
Table 1-5 SONET and SDH Conversion Chart

SONET SDH

Bit Signal Channels Signal Channels Speed

Rate

Mbps DS1 DS3 E1 E4 Gbps

51.84 STS-1 28 1 STM-0 21 0

155.52 STS-3 84 3 STM-1 63 1

622.08 STS-12 336 12 STM-4 252 4

2488.32 STS-48 1344 48 STM- 1008 16 2.5

16

9953.28 STS- 5376 192 STM- 4032 64 10

192 64

39813.1 STS- 21504 786 STM- 16128 256 40

786 256

Table 1-6 Passive Optical Network Standards

GE- 10G- XGS- NG- 100G-

GPON
PON EPON PON PON2 EPON

Standard IEEE ITU-T IEEE ITU-T ITU-T IEEE

802.3ah G.984 802.3av G.9807.1 G.989 802.3ca
(2004) (2003) (2009) (2016) (2015) (2019
TBD)

Downstream 1.25 2.4 10 10 Gbps 40 100

Rate Gbps Gbps Gbps Gbps Gbps

Upstream 1.25 1.2 10 10 Gbps 10 100

Rate Gbps Gbps Gbps Gbps Gbps

Splitting Up to Up to Up to Up to Up to TBD
Ratio 1:64 1:64 1:128 1:128 1:128
(128) (256) (256)

Coexistence No No GE- GPON GPON GE-

PON PON
Table 1-7 Radio Core Functions

Function Description

EPC (Evolved Packet Core Provides the core architecture for 4G

4G LTE) LTE networks

5GC (Next Generation 5G Provides the core architecture for 5G

Core) NR (New Radio) networks

MME (Mobility Manages signaling for mobility and

Management Entity) session management

eNodeB (Evolved NodeB) Acts as the base station for LTE cellu-
lar networks

SGW (Service Gateway) Manages user plane functionality

(data traffic) between the mobile de-
vice and the eNodeB

PGW (Packet Data Network Connects the LTE network to external

Gateway) packet data networks, such as the
Internet

HSS (Home Subscriber Provides a database to manage sub-

Server) scribers in real time

AMF (Access and Mobility Manages access and mobility for

Management Function) devices

SMF (Session Management Manages session-related functions,

Function) such as establishment, modification,
and termination

UPF (User Plane Function) Manages the user plane and data
forwarding

AUSF (Authentication Is responsible for authentication and

Server Function) key management

Chapter 2

Table 2-2 Package Installation Envelopes

Mandatory (Core Mini Image) PIEs Optional PIEs

OS (kernel, file system, memory management) MPLS

 Mandatory (Core Mini Image) PIEs Optional PIEs

Base (interface manager, SysDB, configuration Multicast

manager, checkpoint services)

Admin (line cards, fabric) BNG

Forwarding (FIB, ACL, QoS, ARP, others) Satellite

Line Card drivers Carrier Grade

NAT

Routing (RIB, OSPF, IS-IS, BGP, RPL) Security

Lawful Intercept

Virtual Services
Module

Chapter 4

Table 4-2 RPL Primary Actions

Action Description

Pass The route is granted a ticket to pass the default drop, and
processing continues to the next RPL statement.

Set The route is granted a ticket to pass the default drop, an at-
tribute is modified, and processing continues to the next
RPL statement.

Done The route is granted a ticket to pass the default drop, but
processing stops for the specified route.

Drop A route is discarded, and processing stops.

Chapter 5

Table 5-2 Configuring Basic IS-IS in IOS XE and IOS XR

Step
IOS XE IOS XR
#

1 Create IS-IS routing process

 Step
IOS XE IOS XR
#

2 Choose the IS-IS NET

3 Activate IS-IS on the Select the IS-IS interfaces

interfaces

4 Activate the address

family

Table 5-3 More Relevant IS-IS Troubleshooting Commands

Command Clues It Provides

show isis neighbor Shows level type, interfaces, state,

holdtime

show isis neighbor Displays SPNA, IPv4/IPv6 addresses, area

detail address

show isis protocol Displays interfaces, protocols and metrics,

System ID

show isis database Displays a detailed view of SPF tree and

detail LSP database

show isis topology Displays IS-IS paths to Intermediate

Systems

show isis lsp-log Displays LSP transitions

show ip route isis Displays incoming IS-IS routes

show clns interface Displays interface status and configura-

tion, MTU

clear isis * Clears all IS-IS data structures

clear isis lspfull Clears LSP state

debug isis adj- Debugs IS-IS adjacency information

packets

debug isis Debugs IS-IS authentication events

authentication
Chapter 6

Figure 6-1 OSPF LSA Types

Table 6-2 OSPF Area Type and Corresponding LSAs

Area Command ASBR

LSAs Present
Type (example) Support

Normal area 100 1, 2, 3, 4, 5 Yes

Stub area 100 stub 1, 2, 3 No

Totally area 100 stub 1, 2, 3 as only a default No

stubby no-summary route supplied by ABR

Not so area 100 nssa 1, 2, 3, 7 Yes

stubby

Totally area 100 nssa 1, 2, 3 as only a default Yes

not so no-summary route supplied by ABR
stubby and can be changed to
7, 7

Table 6-3 OSPF Packet Types

Type Name Purpose

1 Hello Sent out periodically to discover

and maintain OSPF router
adjacencies

2 Database Description Describes LSDB contents, ex-

(DBD) changed upon adjacency

3 Link-State Request Requests a portion of a neighbor’s

(LSR) LSDB when the local LSDB appears
 Type Name Purpose

stale

4 Link-State Update Responds to a Type 3 request for a

(LSU) particular prefix

5 Link-State Responds to flooded LSAs, ensures

Acknowledgment the reliability of the flooding
mechanism

Table 6-4 OSPF Adjacency States and Stages

Stage What Happens

Down No OSPF Hello packets have been received.

Attempt On nonbroadcast networks, the router attempts to com-

municate with a neighbor but does not see new
information.

Init A Hello packet has been received from another router,

but there is no two-way communication.

2-Way There is two-way communication and DR/BDR election

if necessary.

ExStart The router agrees on the master/slave relationship for

LSDB synchronization.

Exchange Links states and Type 2 DBD packets are exchanged.

Loading LSRs are sent to update what was missed during the
Exchange stage.

Full Routers are fully adjacent.

Table 6-5 OSPF Network Types

Type Notes Timers DR

Broadcast Default for Ethernet Hello = Yes

10
Dead =
40
 Type Notes Timers DR

Nonbroadcast Default on Frame-Relay main Hello = Yes

interfaces or Frame-Relay mul- 30
tipoint subinterfaces Dead =
120

Point-to-point Default on Frame-Relay point- Hello = No

to-point subinterfaces 10
Dead =
40

Point-to- Used in hub-and-spoke topolo- Hello = No

multipoint gies (DMVPN, L2VPN MPLS, 30
etc.), generates a /32 host route Dead =
120

Loopback Default on loopback interfaces, N/A No

generates a /32 host route, re-
gardless of subnet mask as-
signed to this interface

Table 6-6 OSPFv3 LSA Types

LSA
Description
Type

0x2001 Router-LSA: Originated by the router to describe the state

and cost of the router’s interfaces to the area.

0x2002 Network-LSA: Originated by the link’s designated router

to describe all routers attached to the link, including the
designated router itself.

0x2003 Inter-area-prefix-LSAs: The IPv6 equivalents of OSPFv2

for IPv4’s type 3 summary-LSAs are originated by area
border routers to describe routes to IPv6 address prefixes
that belong to other areas.

0x2004 Inter-area-router-LSAs: The IPv6 equivalents of OSPFv2

for IPv4’s type 4 summary-LSAs are originated by area
border routers to describe routes to AS boundary routers
in other areas.

0x2005 AS-external-LSAs: Originated by AS boundary routers to

describe destinations external to the AS.
 LSA
Description
Type

0x2006 Not used.

0x2007 NSSA-LSAs: Originated by AS boundary routers within an

NSSA to describe destinations external to the AS that may
or may not be propagated outside the NSSA.

0x2008 Link-LSAs: Originated by a router for a link-local flooding

scope; they are never flooded beyond the associated link.

0x2009 Intra-area-prefix-LSAs: Advertise one or more IPv6 ad-

dress prefixes that are associated with a local router ad-
dress, an attached stub network segment, or an attached
transit network segment.

Table 6-7 OSPFv3 Options Field Bits

Option Description

V6-bit If this bit is clear, the router/link should be excluded from

IPv6 routing calculations. Not in our case. We are routing
IPv6.

E-bit This bit describes the way AS-external-LSAs are flooded.

Not in our case. This bit will be cleared in stub areas, and
mismatch E-bit values will prevent neighboring
adjacencies.

R-bit If you clear this bit (not in our case), then routes that tran-
sit this node cannot be computed. Used for router staging
or disabling routing for non-locally addressed packets.

DC-bit This bit describes the router’s handling of demand circuits

for Hello suppression. This is beyond the scope of the
exam.

N-bit This bit indicates whether or not the router is attached to

an NSSA area.

Table 6-8 OSPFv3 Router LSA Bits

Value Name Description

0x01 B-bit Indicates the router is an ABR

 Value Name Description

0x02 E-bit Indicates the router is an ASBR

0x04 V-bit Indicates the router is a virtual link endpoint

0x08 Not
used

0x10 Nt-bit Indicates the router is an NSSA border router

that translates LSA Type 7 into Type 5

Chapter 7

Table 7-2 BGP Address Families

Network Layer Information AFI SAFI

IPv4 Unicast 1 1

IPv4 Multicast 1 2

IPv4 Unicast with MPLS Label 1 4

MPLS L3VPN IPv4 1 128

IPv6 2 1

IPv6 Unicast with MPLS Label 2 4

MPLS L3VPN IPv6 2 128

Virtual Private LAN Service (VPLS), Virtual Private 25 65

Wire Service (VPWS)

Ethernet VPN (EVPN) 25 70

BGP-LS 16388 71

BGP-LS 16388 72
Table 7-3 BGP aggregate-address Additional Keywords

Configuration Tools
Associated with aggregate-ad- Description
dress Command

summary-only Stops specific routes from being

advertised

as-set Preserves originating autono-

mous systems

advertise-map (route-map) Determines which routes will

have attributes within the
aggregate

suppress-map (route-map) Determines which routes will be

suppressed when the aggregate is
advertised

attribute-map (route-map) Sets attributes to the aggregate

route

unsuppress-map (route-map) Determines which routes will be

unsuppressed when the aggregate
is advertised

Table 7-6 Regular Expression Characters

Character Meaning

? Repeats the previous character one or zero times.

* Repeats the previous character zero or many times.

+ Repeats the previous character one or more times.

^ Matches the beginning of a string.

$ Matches the end of a string.

[] Is a range.

_ Matches the space between AS numbers or the end of

the AS-PATH list.
 Character Meaning

\ Is an escape character. You’ll need this for BGP

confederations.

Chapter 9

Table 9-2 Important Multicast Ranges

Addresses Block Name Relevant to Exam Usage

224.0.0/24 Local Network Never forwarded off the local net-

Control work; TTL set to 1 (do you recall
AllSPFRouters?)

224.0.1.0/24 Internetwork Control traffic forwarded through

Control the Internet; Cisco RP-Announce
(224.0.1.39) and Cisco RP-Discovery
(224.0.1.40), which you will see
soon enough

232.0.0.0/8 Source-Specific Traffic for multicast sources ex-

Multicast plicitly requested by the receivers
(SSM)

239.0.0.0/8 Organization- Private range (think of these as

Local Scope “RFC 1918 for Multicast”), which
does not conflict with the same
range being used by other
organizations

233.0.0.0/8 GLOP A block where the middle two

octets are formed from assigned
ASNs, giving any operator assigned
256 globally unique multicast
group addresses

Table 9-3 Important Reserved Multicast Addresses

Multicast Addresses Reserved for

224.0.0.1 All-hosts on a subnet

224.0.0.2 All-routers on a subnet

224.0.0.13 All PIM routers

 Multicast Addresses Reserved for

224.0.0.22 IGMPv3-capable multicast routers

224.0.1.39 Cisco Auto-RP Announce

224.0.1.40 Cisco Auto-RP Discovery

Table 9-4 MLDv1 Messages

Name Type Description

Listener deci- Sent by router, there are two subtypes:

Query mal General Query is used to learn which multi-
130 cast addresses have listeners on an attached
link; the Multicast Address field will be set to
zero and will be sent to the all-nodes multicast
address FF02::1.
Multicast-Address-Specific Query is used if a
particular multicast address has listeners on
an attached link; the multicast address will be
set to a specific IPv6 multicast address.

Listener deci- A receiver/host/listener indicates interest in a

Report mal specific IPv6 multicast address, and the report
131 is sent to the multicast address group.

Listener deci- A receiver/host/listener stops listening to a spe-

Done mal cific IPv6 multicast address and MAY send a
132 single Done message to the link-scope all-
routers multicast address FF02::2 unless sup-
pressed by hearing another Report message
(see above).

Chapter 11

Table 11-4 Ethertype and Ports Combinations

VLAN Ethertype
Tag Port Port Type Note
Type Value

None Per Untagged Access IP = 0x800,

Protocol Frame port ARP =
0x0806, etc.
 VLAN Ethertype
Tag Port Port Type Note
Type Value

Customer 0x8100 Tagged 802.1Q 802.1Q

Frame trunk port VLAN
tagging

Service 0x88a8 QinQ 802.1ad 802.1ad

tagged (QinQ) provider
Frame VLAN tunnel
trunk port

Chapter 14

Figure 14-17a Brainstorm: MPLS TE FRR Roles, Solution

Chapter 15

Table 15-2 LSD (Label Switching Database) Label Ranges

Label Range Reserved for Examples

0–15 Base special-purpose MPLS 0—IPv4 Explicit

labels NULL
3—Implicit NULL

16–15,999 Static MPLS labels LDP assigned

16,000–23,999 SRGB Global Segments

(SR)

24,000– Dynamic allocation Adjacency

1,048,575 Segments
Table 15-3 IS-IS TLVs

TLV Name Description Reference

2 IIS Neighbors Shows all running inter- ISO 10589

faces to which IS-IS is
connected, has a maxi-
mum metric of 6 with
only 6 out of 8 bits used.

10 Authentication The information is used ISO 10589

to authenticate IS-IS
PDUs.

22 Extended IS Increases the maximum RFC 5305

Reachability metric to 3 bytes (24 bits),
addressing TLV 2 metric
limitation.

134 TE Router ID MPLS Traffic Engineering RFC 5305

router ID.

135 Extended IP Provides a 32-bit metric RFC 5305

Reachability with a “up/down” bit for
the route-leaking of L2 Đ
L1.

149 Segment Advertises prefixes to RFC 8867

Identifier/Label SID/Label mappings. This
Binding functionality is called the
Segment Routing
Mapping Server (SRMS).

222 MT-ISN Allows for multiple-topol- RFC 5120

ogy adjacencies.

236 IPv6 Reachability Describes network reach- RFC 5308

ability through the speci-
fication of a routing
prefix.

242 IS-IS Router Allows a router to an- RFC 7981

CAPABILITY TLV nounce its capabilities
within an IS-IS level or
the entire routing
domain.
Chapter 16

Table 16-4 BGP Flowspec NLRI Types

BGP Flowspec Value Input

QoS Match Fields
NLRI type Method

Type 1 IPv4 or IPv6 destination Prefix length

address

Type 2 IPv4 or IPv6 source address Prefix length

Type 3 IPv4 last next header or IPv6 Multivalue

protocol range

Type 4 IPv4 or IPv6 source or desti- Multivalue

nation port range

Type 5 IPv4 or IPv6 destination port Multivalue

range

Type 6 IPv4 or IPv6 source port Multivalue

range

Type 7 IPv4 or IPv6 ICMP type Single value

Type 8 IPv4 or IPv6 ICMP code Single value

Type 9 IPv4 or IPv6 TCP flags (2 Bit mask

bytes include reserved bits)

Type 10 IPv4 or IPv6 packet length Multivalue

range

Type 11 IPv4 or IPv6 DSCP Multivalue

range

Type 12 IPv4 fragmentation bits Bit mask

Table 16-5 BGP Flowspec Traffic Filtering Actions

BGP
Action Description
Community

0x8006 traffic-rate Rate-limits traffic in bytes per sec-

ond before dropping
 BGP
Action Description
Community

0x8007 traffic- Samples traffic to gather attack

action information

0x8008 redirect Directs traffic into a VRF

0x8009 traffic- Changes DSCP codes

marking

Chapter 22

Table 22-2 HTTP Status Codes

Status Code
Description
Category

1xx: Communicates transfer protocol-level

Informational information.

2xx: Success Indicates that the client’s request was accepted

successfully.

3xx: Redirection Indicates that the client must take some addi-
tional action to complete their request.

4xx: Client error This category of error status codes points the
finger at clients.

5xx: Server error The server takes responsibility for these error
status codes.

Table 22-4 XML Elements

Operation Description

<get> Retrieve running configuration and device state

information

<get-config> Retrieve all or part of the specified configuration

data store

<edit-config> Load all or part of a configuration to the specified

configuration data store
 Operation Description

<copy-config> Replace an entire configuration data store with

another

<delete- Delete a configuration data store

config>

<commit> Copy the candidate data store to the running data

store

<lock> / Lock or unlock the entire configuration data store

<unlock> computer

<close- Close the NETCONF session gracefully

session>

<kill-session> Force the NETCONF session to end

Table 22-5 gRPC Authentication Methods

Authentication Authorization
Type Configuration Client Requiremen
Method Method

Metadata Username/password Username grpc Username/passwor

with TLs

Metadata Username/password Username grpc no-tls Username/passwor

without
TLS

Metadata Username/password Username grpc tls- Username/passwor

with mu- mutual key
tual TLS

Certificate Client’s certificate Username grpc tls- Username/passwor

based (common name from client’s mutual key
field) certificate grpc certifi-
(common cate
name field) authentica-
tion