Difference between revisions of "CCNA Explorer 4 Frame relay"
m (→Verifying Frame Relay Operation) |
m (→Frame Relay Bursting) |
||
(2 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{TOCright}} | {{TOCright}} | ||
*Se [[Frame Relay]] notater. | *Se [[Frame Relay]] notater. | ||
− | |||
− | |||
{| | {| | ||
|- | |- | ||
Line 133: | Line 131: | ||
| | | | ||
== Frame Relay Bursting == | == Frame Relay Bursting == | ||
− | | | + | {| |
|[[Image:Exp4fr33.png|800px|left|thumb|Committed Interface Rate]] | |[[Image:Exp4fr33.png|800px|left|thumb|Committed Interface Rate]] | ||
|- | |- | ||
Line 141: | Line 139: | ||
|- | |- | ||
|[[Image:Exp4fr36.png|800px|left|thumb|Bursting eksempel]] | |[[Image:Exp4fr36.png|800px|left|thumb|Bursting eksempel]] | ||
− | | | + | |} |
− | + | *Committed Information Rate | |
− | + | *Committed Burst Information Rate | |
+ | *Excess Burst | ||
+ | |||
== Frame Relay Flow Control == | == Frame Relay Flow Control == | ||
*FECN: Forward Explicit Congestion Notification | *FECN: Forward Explicit Congestion Notification | ||
Line 154: | Line 154: | ||
|- | |- | ||
| | | | ||
+ | |||
== configuring Subinterfaces == | == configuring Subinterfaces == | ||
|- | |- | ||
Line 176: | Line 177: | ||
|[[Image:Exp4fr45.png|800px|left|thumb|]] | |[[Image:Exp4fr45.png|800px|left|thumb|]] | ||
|- | |- | ||
− | + | | | |
+ | == Debugging Frame relay operation == | ||
+ | |- | ||
+ | |[[Image:Exp4fr46.png|800px|left|thumb|]] | ||
+ | |- | ||
+ | | | ||
+ | == Overview == | ||
+ | |- | ||
+ | |[[Image:Exp4fr47.png|800px|left|thumb|]] | ||
+ | |- | ||
|} | |} | ||
[[Category:CCNA]] | [[Category:CCNA]] |
Latest revision as of 09:16, 25 January 2012
- Se Frame Relay notater.
Virtual Circuits | ||||
There are two ways to establish VCs:
| ||||
(IP) adresse til DLCI mapping | ||||
Statisk Adresse til DLCI mapping | ||||
Dynamisk Adresse til DLCI mappingInterfacet udsender Inverse ARP request på alle kendte DLCI'er og modtager addresse retur. (IP)
LMI - Local Management InterfaceCa. hvert 10. sekund sender DTE'en en LMI en request (Dumb eller FULL) til Frame Relay Switchen (ISP) som returner status. Switchen returnerer svar. (Hvis FULL også en liste med aktive DLCI'er) LMI ExtensionsIn addition to the Frame Relay protocol functions for transferring data, the Frame Relay specification includes optional LMI extensions that are extremely useful in an internetworking environment. Some of the extensions include:
| ||||
The 10-bit DLCI field supports 1,024 VC identifiers: 0 through 1023. The LMI extensions reserve some of these identifiers, thereby reducing the number of permitted VCs. LMI messages are exchanged between the DTE and DCE using these reserved DLCIs. There are several LMI types, each of which is incompatible with the others. The LMI type configured on the router must match the type used by the service provider. Three types of LMIs are supported by Cisco routers:
| ||||
Configuring Frame Relay | ||||
Eksempel 1 | ||||
Eksempel 2 | ||||
Split HorizonBemærk: Der er en fejl i de to tegninger nedenunder. Der står at R2 er en Spoke og R1 er en Hub. Der er vist et Full Mesh. Der skal ikke være en PVC mellem R2 og R3. | ||||
Frame Relay Subinterfaces |
||||
Frame Relay Bursting
Frame Relay Flow Control
| ||||
configuring Subinterfaces | ||||
Verifying Frame Relay Operation | ||||
Debugging Frame relay operation | ||||
Overview | ||||