cisco3\u968e\u5c64\u6a21\u578b
\u3000core layer(\u6838\u5fc3\u5c64):\u9aa8\u5e79
\u3000distribution layer(\u5206\u9001\u5c64):\u9076\u9001
\u3000access layer(\u5b58\u53d6\u5c64):\u4ea4\u63db
\u7528\u9014:
enables network designers to organize the network into distinct layers of devices.
The resulting network is efficient, intelligent, scalable, and easily managed.
to design a network with a predictable behavior to offer low maintenance and high availability
ps:\u6b64\u4e09\u5c64\u70ba\u908f\u8f2f\u6027,\u4e14\u672a\u5fc5\u662f\u5be6\u9ad4\u5c64\u7684\u88dd\u7f6e,\u6709\u6642\u4e00\u500b\u8a2d\u5099\u57f7\u884c\u591a\u5c64,\u6216\u4e00\u5c64\u591a\u500b\u8a2d\u5099\u5728\u57f7\u884c
ps:
the hierarchy can be collapsed or simplified in certain cases.
ex:
small or medium-size campus networks might not have the size, multilayer switching, or volume requirements that would require the functions of all three layers.
Here, you could combine the distribution and core layers for simplicity and cost savings.
When the distribution and core layers are combined into a single layer of switches, a collapsed core network results <\/p>\n\n\n\n
core layer<\/strong> distribution layer<\/strong> access layer<\/strong> …………………………………….<\/p>\n\n\n\n ………….<\/p>\n\n\n\n Switch Block<\/strong> Sizing a Switch Block<\/strong> Switch Block Redundancy<\/strong> ……………….. <\/p>\n\n\n\n Core Block<\/strong> …<\/p>\n\n\n\n Collapsed Core<\/strong> core\/distribute layer\u900f\u904elayer3 link\u4e92\u9023<\/strong> …<\/p>\n\n\n\n Dual Core<\/strong> ps: \u96d9\u4e3b\u7dda\u540c\u6642\u904b\u4f5c<\/strong> …<\/p>\n\n\n\n Core Size in a Campus Network<\/strong> cisco3\u968e\u5c64\u6a21\u578b\u3000core layer(\u6838\u5fc3\u5c64):\u9aa8\u5e79\u3000 …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"","fifu_image_alt":"","_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[32],"tags":[],"class_list":["post-896","post","type-post","status-publish","format-standard","hentry","category-cisco-network"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/posts\/896","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/comments?post=896"}],"version-history":[{"count":0,"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/posts\/896\/revisions"}],"wp:attachment":[{"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/media?parent=896"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/categories?post=896"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/systw.net\/note\/wp-json\/wp\/v2\/tags?post=896"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\u7db2\u8def\u7684\u6838\u5fc3,\u8ca0\u8cac\u53ef\u9760\u4e14\u8fc5\u901f\u50b3\u9001\u5927\u91cf\u6d41\u91cf,\u76ee\u7684\u662f\u76e1\u5feb\u4ea4\u63db\u6d41\u91cf
\u5bb9\u932f\u80fd\u529b\u662f\u6b64\u5c64\u91cd\u9ede,\u901f\u5ea6\u8207\u5ef6\u9045\u662f\u6b64\u5c64\u4e3b\u8981\u8003\u91cf
\u901a\u5e38\u9023\u63a5\u6240\u6709distribution layer switch
\u8a2d\u8a08\u65b9\u5411:
\u3000\u4e0d\u8981\u505a\u6703\u6e1b\u7de9\u6d41\u91cf\u7684\u4e8b ex:acl(\u4f7f\u7528\u8005\u5b58\u53d6\u6e05\u55ae),vlan\u9593\u9076\u9001,\u5c01\u5305\u904e\u6ffe,…\u7b49
\u3000\u4e0d\u8981\u652f\u63f4\u5de5\u4f5c\u7fa4\u7d44\u7684\u5b58\u53d6
\u3000\u4e0d\u8981\u5728\u6d41\u91cf\u589e\u9ad8\u6642\u64f4\u5145\u6838\u5fc3 ex:\u65b0\u589erouter
\u3000\u4f7f\u7528\u9ad8\u901f\u7db2\u8def ex:FDDI,fast ethernet,ATM,…\u7b49
\u3000\u4f7f\u7528\u8f03\u4f4e\u6536\u6582\u6642\u9593\u7684\u9076\u9001\u5354\u5b9a
\u5fc5\u5099\u80fd\u529b
\u3000Very high throughput at Layer 3
\u3000No costly or unnecessary packet manipulations (access lists, packet filtering)
\u3000Redundancy and resilience for high availability
\u3000Advanced QoS functions<\/p>\n\n\n\n
\u53c8\u7a31workgroup layer(\u5de5\u4f5c\u7fa4\u7d44\u5c64),building distribution switches
\u6b64\u5c64\u63d0\u4f9brouting,filter,wan\u5b58\u53d6,\u5224\u65b7\u5c01\u5305\u5982\u4f55\u5b58\u53d6\u6838\u5fc3
\u9808\u6c7a\u5b9a\u51fa\u8655\u7406\u7db2\u8def\u670d\u52d9\u8acb\u6c42\u7684\u6700\u5feb\u65b9\u5f0f ex:\u5982\u4f55\u5c07\u6a94\u6848\u8acb\u6c42\u8f49\u9001\u7d66\u4f3a\u670d\u5668
\u6b64\u5c64\u5b9a\u7fa9\u5be6\u884cpolicy(\u7db2\u8def\u653f\u7b56)\u7684\u5730\u65b9,\u6b64\u5c64\u5728\u8a2d\u8a08\u4e0a\u4e5f\u6709\u5927\u91cf\u7684\u5f48\u6027
\u8a2d\u8a08\u65b9\u5411:
\u3000\u9076\u9001\u5354\u5b9a\u9593\u7684\u91cd\u65b0\u5206\u9001
\u3000\u5b58\u53d6\u6e05\u55ae,\u5c01\u5305\u904e\u6ffe
\u3000\u7db2\u8def\u5b89\u5168\u653f\u7b56\u5be6\u4f5c ex:nat,firewall
\u3000vlan\u8207\u5176\u4ed6\u5de5\u4f5c\u7fa4\u7d44\u652f\u63f4\u529f\u80fd\u9593\u7684\u9076\u9001
\u3000\u5ee3\u64ad\u8207\u591a\u9ede\u50b3\u64ad\u7db2\u57df\u7684\u5b9a\u7fa9
\u5fc5\u5099\u529f\u80fd
\u3000Aggregation of multiple access-layer devices
\u3000High Layer 3 throughput for packet handling\u3000
\u3000Security and policy-based connectivity functions through access lists or packet filters
\u3000QoS features
\u3000Scalable and resilient high-speed links to the core and access layers
ps:
Notice that the distribution layer usually is a Layer 3 boundary<\/strong>, where routing meets the VLANs of the access layer<\/p>\n\n\n\n
\u53c8\u7a31\u70badesktop layer(\u684c\u9762\u5c64),building access switches
\u6703\u63a7\u5236\u4f7f\u7528\u8005\u8207\u5de5\u4f5c\u7fa4\u7d44\u5c0d\u4e92\u9023\u7db2\u8def\u8cc7\u6e90\u7684\u5b58\u53d6
\u5e38\u4f7f\u7528\u7684\u6280\u8853\u6709\u4e59\u592a\u7db2\u8def\u4ea4\u63db,\u975c\u614b\u9076\u9001
\u8a2d\u8a08\u65b9\u5411:
\u3000\u5ef6\u7e8c\u81eadistribution layer\u7684\u5b58\u53d6\u63a7\u5236\u8207policy
\u3000\u5efa\u7acb\u7368\u7acb\u7684\u78b0\u649e\u7db2\u57df
\u3000\u5de5\u4f5c\u7fa4\u7d44\u5c0ddistribution layer\u7684\u9023\u7d50
\u5fc5\u5099\u80fd\u529b
\u3000Low cost per switch port
\u3000High port density
\u3000Scalable uplinks to higher layers
\u3000User access functions such as VLAN membership, traffic and protocol filtering, and QoS
\u3000Resiliency through multiple uplinks<\/p>\n\n\n\n
Modular Network Design<\/strong>
1. each layer of the hierarchical network model can be broken into basic functional units
2. These units, or modules,can then be sized appropriately and connected, while allowing for future scalability and expansion
3. to divide enterprise campus networks into the following basic elements
Switch block:<\/strong>A group of access-layer switches, together with their distribution switches
Core block:<\/strong>The campus network’s backbone<\/p>\n\n\n\n
1. switch block contains switching devices from the access and distribution layers.
2. All switch blocks then connect into the core block, providing end-to-end connectivity across the campus.
3. each access-layer switch connects to devices in the distribution layer.
Layer 2 functionality<\/strong>:transports data among all connected access switches at a central connection point.
Layer 3 functionality<\/strong>:also can be provided in the form of routing and other networking services (security, QoS, and so on)<\/p>\n\n\n\n
1. Consider the following factors
\u3000Traffic types and patterns
\u3000Amount of Layer 3 switching capacity at the distribution layer
\u3000Number of users connected to the access-layer switches
\u3000Geographic boundaries of subnets or VLANs
\u3000Size of spanning-tree domains
2. switch block size should be based primarily on the following:
\u3000Traffic types and behavior
\u3000Size and number of common workgroups
3. a switch block is too large if the following conditions are observed:
\u3000The routers (multilayer switches) at the distribution layer become traffic bottlenecks
\u3000Broadcast or multicast traffic slows the switches in the switch block
\u3000Network congestion occurs<\/p>\n\n\n\n
A switch block consists of two distribution switches that aggregate one or more access layer switches
1. Each access layer switch should have a pair of uplinks-one connecting to each distribution switch
2. The physical cabling is easy to draw, but the logical connectivity is not always obvious
recommand <\/strong>
all Layer 2 connectivity should be contained within the access layer.
The distribution layer should have only Layer 3 links.<\/p>\n\n\n\n
1. A core block is required to connect two or more switch blocks in a campus network
2. the core must be as efficient and resilient as possible.
3. The core is the campus network’s basic foundation and carries much more traffic than any other block
\u4e3b\u8981\u6709\u4ee5\u4e0b\u5169\u985e\u578b
\u3000Collapsed Core
\u3000dual core<\/p>\n\n\n\n
1. the hierarchy’s core layer is collapsed into the distribution layer
both distribution and core functions are provided within the same switch devices.
ps:keeping these functions distinct and properly designed is important
2. the collapsed core is not an independent building block but is integrated into the distribution layer of the individual standalone switch blocks
\u5e38\u898b\u74b0\u5883
in smaller campus networks, where a separate core layer (and additional cost or performance) is not warranted.<\/p>\n\n\n\n
1. Connectivity between the distribution and core switches is accomplished using Layer 3 links (Layer 3 switch interfaces, with no inherent VLANs)
2. The VLANs terminate there because the distribution layer uses Layer 3 switching
it limits the broadcast domains, removes the possibility of Layer 2 bridging loops,and provides fast failover if one uplink fails
3. At Layer 3, redundancy is provided through a redundant gateway protocol for IP<\/p>\n\n\n\n
1. A dual core connects two or more switch blocks in a redundant fashion
2. this core appears as an independent module and is not merged into any other block or laye
ps:
Although the collapsed core can connect two switch blocks with some redundancy,
the core is not scalable when more switch blocks are added<\/p>\n\n\n\n
In the past
the dual core usually was built with Layer 2 switches to provide the simplest and most efficient throughput
Layer 3 switching was provided in the distribution layer
In a Layer 2 core, the switches cannot be linked to avoid any bridging loops
Now
Multilayer switches now have become cost-effective and offer high switching performance.
Building a dual core with multilayer switches is both possible and recommended
A Layer 3 core uses routing rather than bridging, so bridging loops are not an issue<\/p>\n\n\n\n
each distribution switch has two equal-cost paths to the core, allowing the available bandwidth of both paths to be used simultaneously
Both paths remain active because the distribution and core layers use Layer 3 devices that can manage equal-cost paths in routing tables
\u96d9\u4e3b\u7dda\u6a5f\u5236<\/strong>
manage equal-cost paths in routing tables
If one switch fails, the routing protocol reroutes traffic using an alternative path through the remaining redundant switch.<\/p>\n\n\n\n
the actual number of directly connected peers is quite small, regardless of the campus network size<\/strong>
ps:
When multilayer switches are used in the distribution and core layers,
the routing protocols running in both layers regard each pair of redundant links between layers as equal-cost paths.
Traffic is routed across both links in a load-sharing fashion, utilizing the bandwidth of both<\/p>\n","protected":false},"excerpt":{"rendered":"