ccna exam content

ccna exam content

Ip unnumbered Loopback0 tunnel mode mpls traffic-eng tunnel destination 5.5.5.5 Interfaces: 300 R2-PE1#show mpls forwarding-table detail Will affect the VPN traffic. IS reachability ISIS for NBMA support network is still flawed, as in the previous experiment demonstrates, if it is run on a Frame Relay main interfaces ISIS , or P2MP run on sub-interfaces ISIS , then you must ask PVC full-mesh, otherwise, the route study Not normal,ccna exam content, but even if the PVC is fully interconnected, there are hidden dangers. If a PVC fails, routing will still have problems. 42000 Virtual link Next , take a look at the Tunnel on R1 : *Aug 18 11:31:44.598: Types of Type 7 length 16: ! Interface loopback0 Duration refers to the time required to obtain continuous protection (based on the target LDP session ) after the LDP link adjacency is DOWN . The default is permanent. Router ospf 1 Set as a P2P sub-interface or broadcast link (if it is fully interconnected) Parameters: Extended OSPF and IS-IS to TE required information flooding in the network, then Tunnel head-end router can build your own TE Fa0/0 IS , since this is a LAN environment, DIS is elected , and each non- DIS router advertises its own adjacency with the DIS without notifying the adjacency with other physical ISs . The LSP of R3\R3 is similar, and will not be described here. Take a look at the LSP of this pseudonode : Tunnel mpls traffic-eng path-option 10 dynamic There are four metric types: Physical_bw: 100000 (kbps), max_reservable_bw_global: 75000 (kbps) 668 Switched MPLS TE using type 10 of LSA to a region within MPLS TE work. Route metric is 168, traffic share count is 1 ! Name: R2-PE1_t0 Status: ! Experimental phenomena [1]: 75000 kbits/sec 668 5.5.5.5/32 DIS advertises all neighbors in the LAN in the "pseudo-node LSP " (similar to the LSA in OSPF ) LSRs maintain only one LDPsession for each label space *Aug 18 11:31:44.598: Path Latency (microseconds):0 !! Re-release the local direct loopback 2.2.2.0/24 to level1 To add: In the above environment, the loopback interface cost=1 , and the cost of all other physical interfaces =10 . Then if we configure: We see the above output, R1 , R2 , R3 all generate LSP , and the asterisk entry is issued by R1 itself. In addition, there is a special IPv6 , then it must publish routing information with this NLPID value. !! 2.2.2.2 The metric of the link is unchanged *Aug 18 11:31:44.598: 75000 For example, this CEF shows that the data going to 4.4.4.4 is stamped with 203 and then sent to 10.1.12.2 . Nolabel/505 Router ospf 1 First R2 routing table: 3.3.3.3/32 Provide a loop-free network Router isis If a router does not refresh its generated LSP after the LSP refresh interval , and the LSP remaining timer field has been reduced to 0 , all routers that have the LSP copy will copy the LSP from its own chain after the 60S grace period. Clear in the road state database. This 60S time is ZeroAgeLifetime , zero lifetime, and not configurable. 2.2.2.2/32 Assuming the bandwidth of the local physical outgoing interface is 100M , the default reservable bandwidth of rsvp is 75% . Here is 75M. L1 router For example, to perform interface ciphertext verification between R1 and R2 : Domain-password In IPv4 , the empty tag is 0 , and the ipv6 is 2 . By default, Cisco IOS starts both L1 and L2 operations on the IS-IS router . If you want to specify the router as only the area router or trunk router , use the router configuration mode: Router ospf 1 vrf VPN-A redistribute bgp 2345 subnets network 10.1.12.2 0.0.0.0 area 0 Type 1 length 12: 10.1.23.0/24 LSP The Address Interface IPv6 : type value 232 ( 0xE8 ), which corresponds to the IPv4 in " the IP Interface the Address" TLV , but the original 32 -bit IPv4 address to the 128 -bit IPv6 address. lab environment Router isis Link state messages are used to propagate link and node information in the area (describe the topology of the local network) Interface Tunnel0 Tspec: ave rate=20000 kbits, burst=1000 bytes, peak rate=20000 kbits RSVP Resv Info: 1112 In this way, my network resources will be more rationally utilized. When R1 goes to 1.0/24 and 2.0/24 , traffic will be sent to different tunnels on R1 . At this moment R1 is the head end of my tunnel , and R5 is the end. The tunnel can set bandwidth requirements so that my tunnel can make more scientific and reasonable routing in the network, not just using OSPF metric for routing. The calculation of the tunnel path is done on the R1, which is the tunnel first-end router. In order to enable the head-end router to calculate the tunnel path more reasonably (not only using metric , but also participating in the path with elements such as available bandwidth and link attributes. Computation), we need to extend the link state routing protocol running in the network, in order to flood the information required for more path calculations, extended OSPF and IS-IS can accomplish this task.