diff options
| author | Sven Eisenhauer <sven@sven-eisenhauer.net> | 2023-11-10 15:11:48 +0100 |
|---|---|---|
| committer | Sven Eisenhauer <sven@sven-eisenhauer.net> | 2023-11-10 15:11:48 +0100 |
| commit | 33613a85afc4b1481367fbe92a17ee59c240250b (patch) | |
| tree | 670b842326116b376b505ec2263878912fca97e2 /Bachelor/CCNA4/en_CCNA4_v30/ch2/2_3_6/content.html | |
| download | Studium-master.tar.gz Studium-master.tar.bz2 | |
Diffstat (limited to 'Bachelor/CCNA4/en_CCNA4_v30/ch2/2_3_6/content.html')
| -rw-r--r-- | Bachelor/CCNA4/en_CCNA4_v30/ch2/2_3_6/content.html | 73 |
1 files changed, 73 insertions, 0 deletions
diff --git a/Bachelor/CCNA4/en_CCNA4_v30/ch2/2_3_6/content.html b/Bachelor/CCNA4/en_CCNA4_v30/ch2/2_3_6/content.html new file mode 100644 index 0000000..21d1e0c --- /dev/null +++ b/Bachelor/CCNA4/en_CCNA4_v30/ch2/2_3_6/content.html @@ -0,0 +1,73 @@ +<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"> </td>
+ </tr>
+ <tr>
+ <td bgcolor="#669999" height="25" width="18"> </td>
+ <td bgcolor="#669999" height="25"><b><font face="Arial" size="2" color="#FFFFFF">
+ 2.3.6</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 WAN design considerations</font></strong></td>
+ <td bgcolor="#669999" height="25" width="9"> </td>
+ </tr></table>
+
+<table border="0" cellpadding="0" cellspacing="0" width="95%" bordercolor="#111111">
+ <tr>
+ <td width="15"></td>
+ <td><font size="2" face="Arial">
+
+ Many enterprise WANs will have connections to the Internet. This
+ poses security problems but also provides an alternative for
+ inter-branch traffic.<p>Part of the traffic that must be considered during design is going to
+ or coming from the Internet. Since the Internet probably exists
+ everywhere that the enterprise has LANs, there are two principal ways
+ that this traffic can be carried. Each LAN can have a connection to
+ its local ISP, or there can be a single connection from one of the
+ core routers to an ISP. The advantage of the first method is that
+ traffic is carried on the Internet rather than on the enterprise
+ network, possibly leading to smaller WAN links. The disadvantage of
+ permitting multiple links, is that the whole enterprise WAN is open to
+ Internet-based attacks. It is also difficult to monitor and secure the
+ many connection points. A single connection point is more easily
+ monitored and secured, even though the enterprise WAN will be carrying
+ some traffic that would otherwise have been carried on the Internet.<p>If each LAN in the enterprise has a separate Internet connection, a
+ further possibility is opened for the enterprise WAN. Where traffic
+ volumes are relatively small, the Internet can be used as the
+ enterprise WAN with all inter-branch traffic traversing the Internet.
+ <img border="0" src="../../images/1.gif" align="absmiddle" width="12" height="12"> Securing the various LANs will be an issue, but the saving in WAN
+ connections may pay for the security.<p>Servers should be placed closest to the locations that will access
+ them most often. Replication of servers, with arrangement for off-peak
+ inter-server updates, will reduce the required link capacity. Location
+ of Internet-accessible services will depend on the nature of the
+ service, anticipated traffic, and security issues. This is a
+ specialized design topic beyond the scope of this curriculum.
+
+ <p> </td>
+ </tr>
+ </table>
+
+</body>
+
+</html>
\ No newline at end of file |