0 valutazioniIl 0% ha trovato utile questo documento (0 voti)
37 visualizzazioni10 pagine
This document provides configuration examples for hierarchically designing a network with Cisco devices. It shows configurations for an access layer switch, distribution layer switch, and core router. The access switch is configured with VLANs and trunking to the distribution switch. The distribution switch acts as the DHCP server for each VLAN and has trunking configured to the access switches. The core router acts as the DNS server and default gateway for traffic exiting the network.
Descrizione originale:
Creating a hierarchical network for optimal traffic flow in a LAN
This document provides configuration examples for hierarchically designing a network with Cisco devices. It shows configurations for an access layer switch, distribution layer switch, and core router. The access switch is configured with VLANs and trunking to the distribution switch. The distribution switch acts as the DHCP server for each VLAN and has trunking configured to the access switches. The core router acts as the DNS server and default gateway for traffic exiting the network.
This document provides configuration examples for hierarchically designing a network with Cisco devices. It shows configurations for an access layer switch, distribution layer switch, and core router. The access switch is configured with VLANs and trunking to the distribution switch. The distribution switch acts as the DHCP server for each VLAN and has trunking configured to the access switches. The core router acts as the DNS server and default gateway for traffic exiting the network.
ueslgnlng ?our neLwork lor LffecLlve 8ouLlng and SwlLchlng
1hls documenL shows how you can hlerarchlcally deslgn your neLwork keeplng local Lrafflc local and uslng Clsco devlces as boLh uPC and unS servers ln your neLwork
1o down|oad a copy of th|s document v|s|t http]]www|deapoo|on||newordpresscom]
epartment A Conf|gurat|on (1hls ls Lhe access layer swlLch any lowend Clsco swlLch can be used)
eptA#show run 8ulldlng conflguraLlon ! hosLname uepLA ! lp subneLzero ! ! lnLerface ClgablLLLherneL0/1 swlLchporL access vlan 10 swlLchporL mode access ! lnLerface ClgablLLLherneL0/2 swlLchporL access vlan 10 swlLchporL mode access ! lnLerface ClgablLLLherneL0/24 1took lotetfoce coooecteJ to clsco J560 l0/J ttook pott swlLchporL mode Lrunk ! lnLerface ClgablLLLherneL0/23 ! lnLerface ClgablLLLherneL0/26 ! lnLerface vlan1 no lp address ! lnLerface vlan43 1bls ls tbe moooqemeot vloo fot tbe swltcbloq oetwotk tbe moooqemeot lp oJJtesses fot oll tbe swltcbes most be lo some oetwotk descrlpLlon MAnACLMLn1 vLAn lp address 1010098 233233233224 ! lp defaulLgaLeway 1010097 1be Jefoolt qotewoy ll oJJtess ls tbe fltst ll oJJtess lo tbe moooqemeot vloo ll block no lp hLLp server lp hLLp secureserver accessllsL 23 permlL 1010096 00031 an access llsL ls creaLed Lo permlL only Lhe l ln Lhe managemenL vlan for ssh access Lo Lhe swlLch ! ! llne con 0 password 7 logln llne vLy 0 4 accessclass 23 ln logln local LransporL lnpuL ssh llne vLy 3 13 accessclass 23 ln logln local LransporL lnpuL ssh ! Lnd
1. Trunk links are typically used to connect switches to other switches, routers, or a server that uses an IEEE 802.1q-enabled network card to participate in multiple VLANs. . The trunk link also does not belong to a specific VLAN. 3. By default, frames from VLAN 1 belong to the native VLAN, and are carried across the trunk untagged. 4. t is recommended that the native VLAN should never be used as a user VLAN or the management VLAN. . Earlier it was stated that control traffic, CDP, VTP, PAgP, and DTP, is transmitted over VLAN 1, the default native VLAN. f the native VLAN is changed to something other than VLAN 1, then the control traffic would then be transmitted on VLAN 1 as tagged traffic. This will have no ill effects on the control traffic. 6. t is fine to leave VLAN 1 as the default native VLAN, as long as VLAN 1 is not used as a user VLAN or as the management VLAN. Control traffic should be the only information carried across VLAN 1. However, it is also common practice to change the native VLAN to some dummy VLAN (other than VLAN 1) that is not used for any data or management traffic. 7. t is also important to ensure that both ends of a switch-to-switch link have consistent native VLANs configured. f the native VLANs on both ends of a link are not the same, there will effectively be a bridge between the two VLANs and they will no longer be independent broadcast domains. Fortunately, recent versions of the OS alert the user when mismatches in the native VLAN occur.