ccna braindump

ccna braindump

BGP based policy accounting on input is disabled BGP based policy accounting on output is disabled Hardware idb is FastEthernet0/0 Route-map test permit 20 match ip address 2 BGP metric is set to IGP metric test: At this point, the direct connection is re-released on R2 , and it is found that 1.1.1.0 has not been re-released into RIP. BGP4+ , also known as Multiprotocol BGP , extends the BGP-4 specification to support new address clusters such as IPv6 , IPX , VPN, and more. Therefore, BGP4+ can carry routing information for IPv6 and other protocols including IPv4 . RFC2858 and RFC2545 defines the BGP4 + process IPv6 attributes updated. OSPF and IBGP route re-release R3 will initiate a Register to the RP and the multicast data will be sent to R1 . At this time, the multicast data is actually going to R1, that is, to the receiver, but in fact, some more complicated things are still happening underneath. R1 receipt Register Thereafter, there will be formed the source wishes SPT ,ccna braindump, so it asks R2 issued a SPT of the join message, R2 after receiving own Fa0 / 0 is added to the corresponding port multicast table entry outgoing interface list of . However, since the multicast data is always sent from the Fa1/0 port of R2 (because when we tested, the specified outgoing interface is Fa1/0 ), R1 continuously receives the multicast data sent by R3 and encapsulates the multicast data. Register , but did not receive alongSPT passed down the multicast data, therefore, Rl is not to R3 transmits Register-STOP , R3 registration process can be repeated, the multicast data will always be encapsulated in Register transmitted message Rl .