ccna 2 chapter 7 pdf

ccna 2 chapter 7 pdf.interfaceserial 0/1/1.3 point-to-point ipaddress 140.1.3.4255.255.255.0 frame-relay interface-dlci 51interfacegigabitethernet 0/0 ipaddress 140.1.14.4 255.255.255.255.0Also, a large number of default settings are used in this example configuration, but some of the defaults are different from what is configured on the physical interface. Also like the configuration of the full mesh interconnection example, the LMI type is auto-aware and uses Cisco encapsulation. In the point-to-point subinterface, reverse ARP is not really needed, but it is enabled by default in case the router on the other end of the VC needs to use reverse ARP, as will be explained later.Two of the new commands are used to create the configuration required for the point-to-point subinterface. First, the interfaces serialO/1/1.1point-to-point command creates a logical subinterface number 1 under the physical interface SerialO/1/l. This command defines a point-to-point subinterface instead of a point-to-multipoint. The configuration must then combine a PVC with this subinterface. The frame-relay interface-dlci subinterface subcommand tells the router which individual local DLCI to combine with this subinterface.Give an example to help understand how the frame-relayinterface-dlci command works. Observe the router Atlanta shown in Figure 14-5. the LMI information received by Atlanta on the SerialO/1/l interface declares three PVCs (i.e., local DLCIs of 52, 53, and 54, respectively) enabled. So which PVC matches which subinterface? The CiscoIOS software needs to associate the correct PVC with the correct subinterface, and this can be done using the frame-relay interface-dlci command. Complete the subinterface configuration and frame-relay interface-dlci configuaration shown in Example 14-8 through Example 14-11. Compare them to the DLCI and subnets in Figure 14-5. Remember that the local DLCI configured with the frame-relay interface-dlci command in each case corresponds to that subnet (based on the ip address command).Before exiting the point-to-point window, note that the subinterface number does not necessarily have to match the router on the other end of the PVC. In this example, the subinterface number is given only for ease of memory. In practice, it can be useful to program information about the network numbering scheme into the subinterface numbers.For example, a company could program a portion of the carrier circuit ID into the subinterface number so that operators can find the correct information and inform the telephone company when fixing a link failure. Many sites use the DLCI as the subinterface number, and of course, information such as the DLCI, the name of the router on the other end of the VC, and other information that is useful for troubleshooting can be configured with text descriptions using the description command. In any case, it is not necessary to match the subinterface number. This example simply matches the subinterface number to the 3rd octet of the IP address.300 Chapter 14 Implementing Frame Relay Verifying Point-to-Point Frame Relay Example 14-12 shows some of the most commonly used Cisco IOS software Frame Relay EXEC commands whose output can be used to monitor Frame Relay, in this case running these commands on the Atlanta router.Example 14-12 EXEC Command Output on an Atlanta RouterAtlanta# show frame-relay pvc PVC Statistics for interface SerialO/1/1 (Frame Relay DTE) Active Inactive Deleted Static Local 2 0 0 0 0 0 Switched 0 0 0 0 0 Unused 1 0 0 0 0 DLCI = 52, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = SerialO/1/1 input pkts 80 output pkts 76 in bytes 5940