Figure 44 Ethernet Bridged Network Example
This network is used to demonstrate the documentation template for an Ethernet [transparent] bridged network. Table 4-4. Ethernet Documentation Template for Bridged Segments [Example]
|
Organization: |
Network Operations | ||
|
LAN Segment Name: |
NOC_EastCoast | ||
|
LAN Segment Description: |
East Coast NOC in Philadelphia, PA | ||
|
LAN Backbone Speed [10/100 Mbps]: |
100 Mbps | ||
|
Hub Device [Vendor and Model]: |
Cisco 2611 |
Mgmt Address: |
10.142.16.1 |
|
Number of Users: |
~50 |
Primary Network Apps: |
E-Mail and SNMP Traffic |
|
ID |
Port |
Host Name |
MAC Address |
Network Address |
Description |
|
A |
1 |
NOC_WS1 |
00-31-0d-c1-f1-16 |
10.142.16.10/24 | |
|
B |
2 |
NOC_WS2 |
00-37-00-e3-00-21 |
10.142.16.11/24 | |
|
C |
3 |
NOC_WS3 |
00-41-00-ab-d1-f1 |
10.142.16.14/24 | |
|
D |
6 |
NOC_SUPE1 |
00-31-0c-d1-f0-1c |
10.142.16.17/24 | |
|
E |
8 |
NOC_SUPE2 |
09-00-2b-01-00-01 |
10.142.16.22/24 |
NOC_SUPE1 Backup |
|
F |
9 |
NOC_WS4 |
03-00-0c-00-00-01 |
10.142.16.23/24 | |
|
G |
4 |
NOC_MAILSVR |
00-40-0b-b2-f4-00 |
10.142.16.15/24 |
E-mail Server |
|
H |
5 |
NOC_AGENTSVR |
00-40-0b-d4-f1-0c |
10.142.16.16/24 |
SNMP Agent Server |
|
I |
7 |
NOC_Printer |
00-00-0c-05-10-00 |
10.142.16.43/24 |
Network Printer |
|
J |
10 |
NOC_WAN_Router |
00-42-a1-31-ff-01 |
10.142.16.8/24 |
Interface E1 |
|
K | |||||
|
L | |||||
|
M |
|
AD | |||||
|
AE | |||||
|
AF | |||||
|
Notes: Any miscellaneous information pertaining to the network environment, such as users, pending changes, and so on would be entered here. Such as noted previously, the bridging functions in this network are implemented within the Cisco router. | |||||
• Organization— The organization(s) that this LAN segment supports.
• LAN Segment Name— A unique identifying name for this LAN segment.
• LAN Segment Description— The purpose of this LAN segment.
• LAN Backbone Speed [10/100]— 10 Mbps or 100 Mbps.
• Bridge Device [Vendor and Model]— Not necessary, but useful if vendors' technical support organization assistance is needed.
• Management Address— Used if the bridge is capable of being remotely managed.
• Number of Users— The total number of users on the segment; identified as active, inactive, or both.
• Primary Network Apps— The applications that this segment primarily supports.
• ID— An alpha-character ID used to easily identify a network device. This ID can also serve as a reference point for network review and analysis.
• Port— The bridge port ID. Although not necessary, this information can be useful for network troubleshooting.
• Host Name— It is recommended that this be a unique name, although it is not necessary. The advantage of a unique host name are the features and advantages of DNS implementation that can be realized.
• MAC Address— The OSI Layer 2 physical address of the device. This address is useful for network troubleshooting, but is not necessary if the Network Address is known.
• Network Address— This is the OSI Layer 3 logical (network) address of the device. This address is useful for network troubleshooting, but is not necessary if the MAC Address is known.
• Description— This is a miscellaneous field used for descriptive or other comments regarding the device. This field could be optional but is worth using because any information makes for more efficient network management and planning.
Was this article helpful?
Post a comment