Добавил:
Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:

CCNP 642-811 BCMSN Exam Certification Guide - Cisco press

.pdf
Скачиваний:
161
Добавлен:
24.05.2014
Размер:
10.85 Mб
Скачать

576 Appendix A: Answers to Chapter “Do I Know This Already?” Quizzes and Q&A Sections

11.What command can verify the QoS trust relationship between an IP Phone and its attached PC? show mls qos interface

-OR-

show interface switchport

Chapter 19

“Do I Know This Already?”

1.b

2.d

3.b

4.c

5.d

6.b

7.b

The trick is in the “maximum 3” keywords. This sets the maximum number of addresses that can be learned on a port. If only one static address is configured, two more addresses can be learned dynamically.

8.c

9.a

10.b

11.c

12.c

Because of the variety of user host platforms, port-based authentication (802.1x) cannot be used. The problem also states that the goal is to restrict access to physical switch ports, so AAA is of no benefit. Port security can do the job by restricting access according to the end users’ MAC addresses.

Q&A

1.What does the acronym “AAA” stand for? Authentication, authorization, and accounting

Chapter 19 577

2.What external methods of authentication does a Catalyst switch support? RADIUS and TACACS+

3.A RADIUS server is located at IP address 192.168.199.10. What command can be used to configure a Catalyst switch to find the server?

radius-server host 192.168.199.10

4.A Catalyst switch should be configured to authenticate users against RADIUS servers first, followed by TACACS+ servers. What command can define the authentication methods? Make sure users can still authenticate if none of the servers are available.

aaa authentication login default radius tacacs+ local

5.What is the purpose of authorization? What happens if authorization is not used?

It allows an external server to decide if the authenticated user can gain access to specific resources or switch commands. If it is not used, the default behavior is that all users must authenticate as they move to the appropriate privilege level to run switch commands.

6.Is it possible to use different methods to authorize users to run switch commands instead of making configuration changes?

Yes; The aaa authorization command separates these functions so that each can have its own method list.

7.When might the command switchport port-security maximum 2 be used?

The switchport port-security maximum 2 command might be used if it is too much trouble to manually configure MAC addresses into the port security feature. Up to two MAC addresses would then be dynamically learned. The network administrator might also want to control what is connected to that switch port. If another switch or a hub were connected, the total number of active stations could easily rise above two.

8.After port-based authentication is configured and enabled, can any host connect as long as the user can authenticate?

No, only hosts that have 802.1x-capable applications can communicate with the switch port to properly authenticate at all.

9.When the 802.1x force-authorized keyword is used, how does the switch react to users attempting to connect?

The switch always authorizes any connecting user, without any authentication.

578 Appendix A: Answers to Chapter “Do I Know This Already?” Quizzes and Q&A Sections

10.Can more than one host be authenticated on a single switch port with port-based authentication? Yes, if the dot1x multi-hosts command is configured on the switch port interface.

Chapter 20

“Do I Know This Already?”

1.c

2.d

3.d

4.a

5.b

6.a

7.c

8.a

9.c

10.d

11.a

12.b

Q&A

1.When a VACL is implemented on a switch, how is the switching speed affected?

It isn’t; VACLs are implemented in hardware, so packets can be inspected as they are being switched with no performance penalty.

2.What actions can be taken on packets matching a VACL?

Packets can be forwarded, dropped, marked for capture, or redirected to a different Layer 2 switch port.

3.After a VACL is applied using the vlan filter command, how is the traffic direction (inbound or outbound) specified?

It isn’t; VACLs operate on packets as they are being forwarded within a VLAN. Therefore, there is no concept of direction within the VLAN. A direction can’t be specified.

Chapter 20 579

4.A secondary community VLAN is associated with a primary VLAN on a switch. Can hosts assigned to the community VLAN communicate with each other?

Yes, they can. However, they can’t communicate with any other community or isolated VLAN.

5.A secondary isolated VLAN is associated with a primary VLAN on a switch. Can hosts assigned to the isolated VLAN communicate with each other?

No, hosts on an isolated VLAN can’t even communicate among themselves. They can reach only the promiscuous host on the primary VLAN.

6.What command is needed to configure a promiscuous VLAN?

This isn’t possible. The primary VLAN can communicate with all the secondary VLANs that are associated with it. The only promiscuous objects that can be configured are promiscuous hosts, located on the primary VLAN.

7.A router is identifed as the central gatewawy for a private VLAN. What command is needed to configure the switch port where a router is connected?

switchport mode private-vlan promiscuous

8.How many actual VLANs must be configured to implement a common router with two community VLANs?

Three VLANs must be used: one for the primary VLAN where the router is connected and two more for the secondary community VLANs. The primary VLAN will be logically associated with the two community VLANs, but all three must be configured.

9.How is switching performance affected when several SPAN sessions are enabled?

Switching performance is not affected. Packets are simply marked and copied into another switch port’s queue during a SPAN session. The original traffic is still forwarded without being modified or affected.

10.What command can specify the source of a SPAN session as VLAN 100? monitor session 1 source vlan 100

580Appendix A: Answers to Chapter “Do I Know This Already?” Quizzes and Q&A Sections

11.When a SPAN session is enabled, what direction of traffic flow (relative to the source port) is mirrored for analysis?

By default, traffic in both directions is mirrored.

12.What two things can identify more granular traffic to be mirrored to a SPAN destination?

A VLAN ACL (VACL) can match and mark packets for capture. A SPAN VLAN filter can also identify specific VLANs to mirror, if the source is a trunk port.

13.Three switches are connected in series with trunk links. The RSPAN source is on the first switch and the destination is on the third. How does the intermediate (second) switch learn about the RSPAN’s source and destination locations?

It doesn’t. The intermediate switch has no knowledge that RSPAN is being used. The only configuration needed is to define the RSPAN VLAN and to allow that VLAN on the trunk links. Beyond that, the intermediate switch can flood only the RSPAN packets to all ports carrying the RSPAN VLAN.

14.What must be configured on all switches connecting an RSPAN source and destination? What commands can be used?

The special-purpose RSPAN VLAN must be configured. Define the VLAN number and then use the remote-span command.

15.One of the advantages of RSPAN is that mirrored traffic can be isolated in the RSPAN VLAN on a trunk. If a GigabitEthernet port is to be monitored on one switch, which is better to use as a transport for the RSPAN VLAN: a GigabitEthernet trunk already carrying user traffic in other VLANs, or an isolated GigabitEthernet trunk link set aside for RSPAN?

The existing trunk will work fine because the RSPAN traffic will be isolated in its own VLAN. However, you must be careful not to place an excessive load on that trunk link. RSPAN traffic can easily add to the bandwidth burden on a link, considering that the source here is also a GigabitEthernet port. In this case, it might be better to transport the RSPAN mirrored traffic over its own trunk link, if one is available and cost-effective.

Index

Symbols

(*,G) multicast flows, 363 (S,G) multicast traffic, 362

Numerics

10 Mbps Ethernet, 112–113 10GbE, 118–119

80/20 rule, 18 802.1Q

tunneling, 153–155 configuring, 155

802.1x

configuring, 461–463

A

AAA accounting

enabling on Catalyst switches, 459 authentication

enabling on Catalyst switches, 455–

457 authorization

enabling on Catalyst switches, 457– 458

access layer, 20 switches, 23

access layer switches, 22–23 accounting

enabling on Catalyst switches, 459 aCEF (Accelerated CEF), 315

ACLs, 65

See also VACLs addressing

multicast, 358

OUI values, 358 reserved addresses, 358

adjacency tables, 315–316 advertisements

VTP, 172–173

subset advertisements, 174 summary advertisements, 173

aggregate policers, 390 aggressive mode (UDLD), 272

application-specific integrated circuits (ASICs), 10

applying

trusts to QoS, 406

VACLs to VLAN interfaces, 474

ARP throttling, 316

ASICs (application-specific), 10 assigning

IP address to management VLAN, 90–91 authentication

enabling on Catalyst switches, 455–457 port-based

configuring, 461–463 authorization

enabling on Catalyst switches, 457–458 auto-RP process, 365

AVF (active virtual forwarder), 339 AVG (active virtual gateway), 338

B

baby giant frames, 149 BackboneFast, 254–255 best effort QoS, 382 Blocking state (STP), 225 blocks

core, 42, 44

BßU

skew detection, 270

BPDU Guard, 268–269 BPDUs

BPDU Guard, 268–269 Configuration BPDUs, 217–218 convergence, 285–286

protecting agains sudden loss, 269 Root Guard, 267–268

RSTP, 285

TCN BPDUs, 228

Bridge IDs, 219 bridging

transparent redundancy, 215

versus Ethernet switches, 213–214 bridging loops, 216

preventing with STP, 217 broadcast traffic, 357 building access switches, 20 building block model

enterprise edge block, 47 network managment block, 46–47 server farm blocks, 46

server provider edge block, 47 building blocks (QoS)

ingress queueing, 388

bundled ports (EtherChannel), 194 bundleds

distributed EtherChannel traffic, 194–195 bundles (EtherChannel)

troubleshooting, 200–203

C

CAM (Content Addressable Memory), 65 CAM tables, 70

troubleshooting, 76

campus networks, 25, 28 building blocks

enterprise edge block, 47

network management block, 46–47 server farm blocks, 46

server provider edge block, 47

LAN segmentation model, 14–15, 17 models, 12

modular design

core blocks, 41–45 switch blocks, 38–41

modular designs, 37

network traffic models, 17–18 predictable network model, 19 shared network model, 13–14

campus-wide VLANs deploying, 145

Catalyst switches, 24–26

CDP, 91

file management, 92 configuration files, 93–94 image files, 92–93 moving files, 94–95

port security, 460–461 product summary, 25–26, 29 remote access, 90–91 SPAN, 480

local SPAN, 481, 483–484 RSPAN, 484–486

VSPAN, 481, 483–484

CatOS, 87 host name

changing, 88 passwords, 89

recovering, 90 troubleshooting, 96–98

584 cd flash command

cd flash command, 95 CDP

viewing neighboring device information, 98

CDP (Cisco Discovery Protocol) inter-switch communication, 91

CEF, 312

adjacency table, 315–316 configuring, 316 fallback bridging, 317 FIB, 314–315

packet rewrites, 316 process switching, 69 verifying, 319, 321

CEF (Cisco Express Forwarding), 67 CGMP (Cisco Group Membership Protocol),

368–369

Cisco IOS Software, 87 running configuration, 89

Cisco IP Phones

inline power, 435–436 configuring, 437 verifying, 443

trunking modes, 438 class maps

defining as QoS policy, 411 classification (packets), 388 client mode (VTP), 172

configuring, 176 collapsed core blocks, 42–43 collision domain, 13 collisions

preventing, 15 commands

cd flash, 95 copy flash, 95

debug commands

troubleshooting CatOS, 97–98 delete flash, 95

dir, 95

erase flash, 95 format flash, 95 show commands

troubleshooting CatOS, 96–97 show etherchannel port-channel, 196 show vtp status, 178

community VLANs, 475 comparing

Ethernet switches and transparent bridges, 213–214

configuration

dual core blocks, 44

hierarchical network design, 25, 28 modular network designs, 37

Configuration BPDUs, 217–218 configuration files

manipulating, 95 moving, 94–95 switches, 93–94

configuring

802.1Q tunneling, 155

accounting on Catalyst switches, 459 authentication on Catalyst switches, 455–

457

authorization on Catalyst switches, 457–458 CEF, 316

EtherChannel, 198

LACP, 199–200

load balancing, 195–197

PAgP, 199

inline power on Cisco IP Phones, 437 interVLAN routing, 310

Layer 2 mode, 310

Layer 3 mode, 311 SVI ports, 312

Layer 2 protocol tunnels, 156 local SPAN, 481–482, 484 MST, 295–296

PIM-DM, 362

PIM-SM, 364

port security on Catalyst switches, 460–461 PVLANs, 477, 479

associating secondary VLANs to primary VLANs, 479

mapping promiscuous mode ports, 478

QoS

trust, 441

RSPAN, 484–486 RSTP, 290

SLB, 344–345 static VLANs, 143 STP

Root Bridges, 246–248 timers, 250–251 UDLD, 273

switch ports, 123–124 port mode, 125 speed, 124

VACLs, 473–474

VLAN trunks, 150–152 voice VLANs, 438, 440 VSPAN, 482–484

VTP

client mode, 176 management domains, 175 pruning, 182

server mode, 176 transparent mode, 176 version, 177–178

WRED

thresholds, 416–417 congestion

relieving, 13 congestion avoidance, 391

mapping internal DSCP values to CoS values, 414–415

mapping packets to egress queues, 415–416 tail drop, 391, 416

WRED, 392–393, 416

thresholds, configuring, 416–417 connecting switch block devices, 121

Gigabit Ethernet port cables, 121–122 connectivity, 21

core blocks, 42, 44 switch ports

troubleshooting, 126–127 console ports

connecting switch block devices, 120 convergence

controlling on STP, 252

with BackboneFast, 254–255 with PortFast, 252

with UplinkFast, 253–254

STP timers, 227 convergences

RSTP, 285–286 TCN BPDUs, 228

copy flash command, 95 copying

Catalyst switch files, 94–95 core blocks, 41–42, 44

collapsed core, 42–43 dual core, 43–45

core layer, 21

core layer switches, 24 CoS (class of service), 384

mapping to internal DSCP values, 407

designing campus networks

585

criteria for process switching, 69 CST (Common Spanning Tree), 229 customizing

STP

Port ID, 250

Root Path Cost, 248–249 timers, 250–251

D

DC inline power for Cisco IP Phones, 435–436 configuring, 437

verifying, 443

dCEF (Distributed CEF), 315 debug commands

troubleshooting CatOS, 97–98 decision processes of packets in multilayer

switches, 67, 69 defining

QoS policies, 409 class maps, 411 marking, 412 policing, 412–413

traffic classification, 409–410 trusted information, 412

VACL matching conditions, 473–474

Delay, 381

delete flash command, 95 deleting SPAN sessions, 483 demand-based switching, 66 Dense Mode (PIM), 362 deploying

VLANs, 144 end-to-end, 145 local, 145

design, 42 Designated Ports

election procedure, 223–224 designing

hierarchical networks access layer, 20 core layer, 21 distribution layer, 21

designing campus networks building block model

enterprise edge block, 47

network management block, 46–47

Соседние файлы в предмете Сети и Телекоммуникации