The final step is to configure RPs. To manually identify an RP, use the following global configuration command: Router(config)# ip pim rp-address ip-address [access-list] [override] Alternatively, RPs can be dynamically determined using Auto-RP. With Auto-RP, some routers need to volunteer to be RPs, while others need to advertise the RPs. Auto-RP identifies a centrally located and well-connected router to function as the mapping agent. The mapping agent learns ..
Matching AS_SET and AS_CONFED_SEQ
Example 13-5 shows how to use a BGP filter list to match the AS_SET and AS_CONFED_SEQ segment types. Figure 13-5 depicts the specifics of the example. In this case, R4 summarizes 16.0.0.0/4, creating an AS_SET entry for the summary, and advertising it to R1 and R3. R1 and R3 in turn advertise the route to R2; R1’s route includes an AS_CONFED_SEQ, because R1 and R2 are confederation eBGP peers. Figure 13-5 Generating AS_SET and AS_CONFED_SEQ Example 13-5 shows two ..
TCP Connections and Port Numbers
Two host applications using TCP must establish a TCP connection before data can flow. Each connection exists between a pair of TCP sockets, with a socket being defined as an IP address of the host, the port number used, and the transport layer protocol (TCP in this case). The connection establishment process essentially initializes the sockets, including the source and destination ports, as well as the Sequence and Acknowledgement fields. Figure 6-2 depicts a typical three-wa..
AppleTalk Routing Configuration
The assignment of AppleTalk network numbers and zone names to IOS devices and interfaces is necessary but not sufficient for AppleTalk devices to communicate with each other. To pass data back and forth, the workstations and servers on the AppleTalk network also must know which paths to take to reach one another. AppleTalk routers build and refer to tables of network numbers, which are known as routing tables. The AppleTalk routing tables operate much like IP routing tables, ..
PPP Layer 2 Payload Compression
Cisco IOS software supplies three different payload compression options for PPP, namely Lempel-Ziv Stacker (LZS), Microsoft Point-to-Point Compression (MPPC), and Predictor. Stacker and MPPC both use the same underlying Lempel-Ziv (LZ) compression algorithm, with Predictor using an algorithm called Predictor. LZ uses more CPU and less memory in comparison to Predictor, and it typically results in a better compression ratio. Table 17-7 summarizes some of the key points regar..
