summaryrefslogtreecommitdiffstats
path: root/Bachelor/CCNA4/en_CCNA4_v30/ch2/2_3_5/content.html
diff options
context:
space:
mode:
Diffstat (limited to 'Bachelor/CCNA4/en_CCNA4_v30/ch2/2_3_5/content.html')
-rw-r--r--Bachelor/CCNA4/en_CCNA4_v30/ch2/2_3_5/content.html70
1 files changed, 70 insertions, 0 deletions
diff --git a/Bachelor/CCNA4/en_CCNA4_v30/ch2/2_3_5/content.html b/Bachelor/CCNA4/en_CCNA4_v30/ch2/2_3_5/content.html
new file mode 100644
index 0000000..12e5dd7
--- /dev/null
+++ b/Bachelor/CCNA4/en_CCNA4_v30/ch2/2_3_5/content.html
@@ -0,0 +1,70 @@
+<html>
+
+<head>
+<meta http-equiv="Content-Language" content="en-us">
+<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
+
+
+
+<title>Content</title>
+<base target="_self">
+</head>
+
+<body background="../../images/bg.gif" topmargin="0" leftmargin="0" marginheight="0" marginwidth="0" onLoad="window.focus();" link="#808080" vlink="#808080" alink="#808080">
+
+<table border="0" cellpadding="0" cellspacing="0" width="100%">
+ <tr>
+ <td bgcolor="#336666" width="18" valign="top">
+ <img border="0" src="../../images/content_lines.gif" width="16" height="25">
+ <img border="0" src="../../images/transdot.gif" width="2" height="1"></td>
+ <td bgcolor="#336666"><font face="Arial" size="2" color="#FFFFFF"><b>2.</b></font><b><font face="Arial" size="2" color="#FFFFFF">3</font></b></td>
+ <td bgcolor="#336666"><img border="0" src="../../images/transdot.gif" width="10" height="1"></td>
+ <td bgcolor="#336666" width="100%"><strong>
+ <font face="Arial" size="2" color="#FFFFFF">WAN Design</font></strong></td>
+ <td width="9" bgcolor="#336666">&nbsp;</td>
+ </tr>
+ <tr>
+ <td bgcolor="#669999" height="25" width="18">&nbsp;</td>
+ <td bgcolor="#669999" height="25"><b><font face="Arial" size="2" color="#FFFFFF">
+ 2.3.5</font></b></td>
+ <td bgcolor="#669999"><img border="0" src="../../images/transdot.gif" width="10" height="1"></td>
+ <td bgcolor="#669999" height="25" width="100%"><strong>
+ <font face="Arial" size="2" color="#FFFFFF">Other layered design models</font></strong></td>
+ <td bgcolor="#669999" height="25" width="9">&nbsp; </td>
+ </tr></table>
+
+<table border="0" cellpadding="0" cellspacing="0" width="95%" bordercolor="#111111">
+ <tr>
+ <td width="15"></td>
+ <td><font face="Arial" size="2">
+ Many networks do not require the complexity of a
+ full three-layer hierarchy.
+ <img border="0" src="../../images/1.gif" align="absmiddle" width="12" height="12"> Simpler hierarchies may be used.
+ <img border="0" src="../../images/2.gif" align="absmiddle" width="12" height="12"></font><p><font face="Arial" size="2">
+ An enterprise with several relatively small branches that require
+ minimal inter-branch traffic may choose a one-layer design. Historically
+ this has not been popular because of the length of the leased lines.
+ Frame Relay, where charges are not distance related, is now making this
+ a feasible design solution.</font></p>
+ <p><font face="Arial" size="2">
+ If there is a need for some geographical concentration, a two-level
+ design is appropriate. This produces a “star of stars” pattern. Again,
+ the pattern chosen based on leased line technology will be
+ considerably different from the pattern based on Frame Relay
+ technology.</font></p>
+ <p><font face="Arial" size="2">
+ When planning simpler networks, the three-layer model should still be
+ considered as it may provide for better network scalability. The hub
+ at the center of a two-layer model is also a core, but with no other
+ core routers connected to it. Likewise, in a single-layer solution the
+ area hub serves as the regional hub and the core hub. This allows easy
+ and rapid future growth as the basic design can be replicated to add
+ new service areas.</font></p>
+ <p><font face="Arial" size="2">&nbsp;&nbsp;&nbsp; </font>
+ </td>
+ </tr>
+ </table>
+
+</body>
+
+</html> \ No newline at end of file