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/ch4/4_3_6/content.html | |
| download | Studium-master.tar.gz Studium-master.tar.bz2 | |
Diffstat (limited to 'Bachelor/CCNA4/en_CCNA4_v30/ch4/4_3_6/content.html')
| -rw-r--r-- | Bachelor/CCNA4/en_CCNA4_v30/ch4/4_3_6/content.html | 151 |
1 files changed, 151 insertions, 0 deletions
diff --git a/Bachelor/CCNA4/en_CCNA4_v30/ch4/4_3_6/content.html b/Bachelor/CCNA4/en_CCNA4_v30/ch4/4_3_6/content.html new file mode 100644 index 0000000..7f52400 --- /dev/null +++ b/Bachelor/CCNA4/en_CCNA4_v30/ch4/4_3_6/content.html @@ -0,0 +1,151 @@ +<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>4.</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%"><b>
+ <font face="Arial" size="2" color="#FFFFFF">DDR Configuration</font></b></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">4.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">Dialer profiles</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 face="Arial" size="2">Legacy DDR is limited because the
+ configuration is applied directly to a physical interface. Since the IP
+ address is applied directly to the interface, then only DDR interfaces
+ configured in that specific subnet can establish a DDR connection with
+ that interface. This means that there is a one-to-one correspondence
+ between the two DDR interfaces at each end of the link.</font><p>
+ <font face="Arial" size="2">Dialer profiles remove the configuration
+ from the interface receiving or making calls and only bind the
+ configuration to the interface on a per-call basis. Dialer profiles
+ allow physical interfaces to dynamically take on different
+ characteristics based on incoming or outgoing call requirements. Dialer
+ profiles can do all of the following:</font></p>
+ <ul>
+ <li><font face="Arial" size="2">Define encapsulation and access
+ control lists </font></li>
+ <li><font face="Arial" size="2">Determine minimum or maximum calls</font></li>
+ <li><font face="Arial" size="2">Turn features on or off</font></li>
+ </ul>
+ <p><font face="Arial" size="2">Dialer profiles aid in the design and
+ deployment of more complex and scalable circuit-switched internetworks
+ by implementing a more scalable DDR model in Cisco routers and access
+ servers. Dialer profiles separate the logical portion of DDR, such as
+ the network layer, encapsulation, and dialer parameters, from the
+ physical interface that places or receives calls.
+ <img border="0" src="../../images/1.gif" align="middle" width="12" height="12"></font></p>
+ <p><font face="Arial" size="2">Using dialer profiles, the following
+ tasks may be performed:</font></p>
+ <ul>
+ <li><font face="Arial" size="2">Configure B channels of an ISDN
+ interface with different IP subnets.</font></li>
+ <li><font face="Arial" size="2">Use different encapsulations on the B
+ channels of an ISDN interface.</font></li>
+ <li><font face="Arial" size="2">Set different DDR parameters for the B
+ channels of an ISDN interface.</font></li>
+ <li><font face="Arial" size="2">Eliminate the waste of ISDN B channels
+ by letting ISDN BRIs belong to
+ multiple dialer pools.</font></li>
+ </ul>
+ <p><font face="Arial" size="2">A dialer profile consists of the
+ following elements:
+ <img border="0" src="../../images/2.gif" align="absmiddle" width="12" height="12"></font></p>
+ <ul>
+ <li><font face="Arial" size="2"><b>Dialer interface</b> – A logical
+ entity that uses a per-destination dialer profile.</font></li>
+ <li><font face="Arial" size="2"><b>Dialer pool</b> – Each dialer
+ interface references a dialer pool, which is a group of one or more
+ physical interfaces associated with a dialer profile.</font></li>
+ <li><font face="Arial" size="2"><b>Physical interfaces</b> –
+ Interfaces in a dialer pool are configured for encapsulation
+ parameters and to identify the dialer pools to which the interface
+ belongs. PPP authentication, encapsulation type, and multilink PPP are
+ all configured on the physical interface.
+ <img border="0" src="../../images/3.gif" align="absmiddle" width="12" height="12"></font></li>
+ </ul>
+ <p><font face="Arial" size="2">Like legacy DDR, dialer profiles activate
+ when interesting traffic is queued to be sent out a DDR interface.
+ First, an interesting packet is routed to a remote DDR IP address. The router
+ then checks the configured dialer interfaces for one that shares the
+ same subnet as the remote DDR IP address. If one exists, the router
+ looks for an unused physical DDR interface in the dialer pool. The
+ configuration from the dialer profile is then applied to the interface
+ and the router attempts to create the DDR connection. When the
+ connection is terminated, the interface is returned to the dialer pool
+ for the next call.</font></p>
+ <p>
+ <TABLE bgcolor="#B0AFAF" width="95%" border="0" cellspacing="0" cellpadding="0">
+ <TR>
+ <TD valign="top">
+ <TABLE bgcolor="#669999" width="100%" cellspacing="0" cellpadding="0" border="0">
+ <TR>
+ <TD width="5">
+ <img border="0" src="../../images/lab_toplft.gif" width="116" height="23"></TD>
+ <TD><IMG alt="" height="1" width="3" src="../../images/s.gif"></TD><TD align="right" valign="top">
+ <IMG alt="" src="../../images/corner_ur_7.gif" width="7" height="7"></TD>
+ </TR>
+ </TABLE>
+
+ <TABLE bgcolor="#B0AFAF" width="100%" cellspacing="0" cellpadding="0" border="0">
+ <TR>
+ <TD>
+ <TABLE width="100%" cellpadding="2" cellspacing="0" border="0" bordercolor="#111111">
+ <TR>
+ <TD bgcolor="#ffffff" width="15"> </TD>
+ <TD bgcolor="#ffffff"><font FACE="Arial" SIZE="2" COLOR="#000000">
+ <p><font color="#808080">
+ <img border="0" src="../../images/links_icon.gif" width="25" height="25">
+ <b>Web Links</b></font></p>
+ </font><font FACE="Arial" SIZE="2" COLOR="#808080">
+
+ <p>Dialer Profiles<p>
+ <a target="_blank" href="http://www.cisco.com/en/US/tech/tk801/tk133/tk159/tech_protocol_home.html">
+ http://www.cisco.com/en/US/tech/
+ tk801/tk133/tk159/ tech_protocol_home.html</a></font></p>
+
+ <p>
+ <IMG alt="" height="2" width="1" src="../../images/s.gif"></p>
+ </TD>
+ </TR>
+ </TABLE>
+ </TD>
+ </TR>
+ </TABLE>
+ </TD>
+ </TR>
+ </TABLE><p>
+
+ <font face="Arial" size="2"> </font></td>
+ </tr>
+ </table>
+
+</body>
+
+</html>
\ No newline at end of file |