To carry multiple VLANs between switches, trunk links must be configured using IEEE 802.1Q encapsulation. The case study typically requires trunking on the interfaces connecting the two switches and between the switch and the router.
The Bangor router utilizes stateless or stateful configurations to assign regional IPv6 identities. ccna-2v7.0 case study -rev b-
PhoenixSW-1# configure terminal PhoenixSW-1(config)# hostname PHX-SW-1 PHX-SW-1(config)# service password-encryption PHX-SW-1(config)# enable secret class PHX-SW-1(config)# no ip domain-lookup PHX-SW-1(config)# banner motd #UNAUTHORIZED ACCESS IS STRICTLY PROHIBITED# PHX-SW-1(config)# login block-for 60 attempts 3 within 60 PHX-SW-1(config)# ip domain-name cisco.com PHX-SW-1(config)# crypto key generate rsa general-keys modulus 1024 PHX-SW-1(config)# ip ssh version 2 PHX-SW-1(config)# line console 0 PHX-SW-1(config-line)# password cisco PHX-SW-1(config-line)# logging synchronous PHX-SW-1(config-line)# exec-timeout 5 0 PHX-SW-1(config-line)# exit PHX-SW-1(config)# line vty 0 15 PHX-SW-1(config-line)# transport input ssh PHX-SW-1(config-line)# login local PHX-SW-1(config-line)# exit Use code with caution. Switchport Security Implementation To carry multiple VLANs between switches, trunk links
. This wasn't just a lab; it was the final blueprint for the Oakhaven University A typical approach involves:
Using VLSM, you can efficiently allocate IP address space by creating smaller subnets for networks that need only a few hosts (like a WAN link with a /30 mask) and larger subnets for LANs that may host dozens of workstations. A typical approach involves: