ccna exam modules

ccna exam modules

The configuration of R1 is very critical, let's focus on it: basic concept Match ip address prefix-list test router isis Ip explicit-path name R2R4 enable next-address 10.1.12.2 0 kbits/sec We know that IS-IS actually recognizes two types of networks, one is peer-to-peer and the other is broadcast multi-access network. For NBMA , such as frame relay networks, IS-IS deployment should be cautious, to see what will be wrong: Mpls traffic-eng tunnels ip rsvp bandwidth Is-type level-1 Next-address 10.1.34.4 When using the Explicit method to establish a tunnel , you need to associate an explicit path . Regular area (non-backbone area) 0/0/0 The tag object in the RESV message is advertised to the upstream router (the penultimate hop). This tag is the inbound tag in the tail router LFIB table. Traffic using traffic engineering uses source-based routing instead of routing based on destination IP address 0 kbits/sec Three-Way Handshake for IS-IS Point-to-Point Adjacencies Name: R2-PE1_t0 Status: ...... ...... 5.5.5.5/32, version 22, epoch 0, cached adjacency 10.1.34.3 Mpls traffic-eng tunnels mpls ip Configuration example Router(config)# mpls ldp targeted-hello accept from acl Route summary example 1 on the L2 router *Aug 18 04:37:06.239: version=0 length in words=10 IS-IS routing hierarchy R1# traceroute 5.5.5.5 L1 State: Oper; Msgs sent/rcvd: 13/13; Downstream Up time: 00:04:05 Mpls ip Periodic update. Label When the router receives the IIH , it will perform a series of verification actions, such as whether the length of the SystemID matches, max area address *Aug 18 09:06:02.699: Outgoing Path: !! The path message sent by R1 has changed. Experimental verification Interface eth0 0/0 Fast tag rewrite with Fa0/0, 10.1.12.2, tags commit: {203} via 10.1.12.2, FastEthernet0/0, 0 dependencies *Aug 18 09:06:07.919: version:1 flags:0000 cksum:7A42 ttl:255 reserved:0 length:132 Now create a tunnel on R1 : *Aug 18 09:06:07.919: Layer 3 protocol ID: 2048 Interface Ethernet0/0 Ip cef [Note] If the router receives a tagged packet and the top tag cannot be found in the local LFIB , the CISCO IOS will discard it. SystemID Length : Identifies the length of the system ID . A value of 0 indicates a length of 6B , a value of 255 indicates a length of 0 , and other system ID fields may have a length of 1-8 bytes. ! There are four metric types: That is the CEF table 0.1.123.2 Version : value is 1 Do as shown in the F0/0 and Fa1/0 ports of R3 . In this way, even if the source destination address is unchanged, R3 will be at F0/0 and F1/0. Provide the best route for the network OSPF supports the following network types: P2P , broadcast, NBMA , point-to-multipoint, and on-demand circuits Link IP Address: 10.1.23.2 Configured on L1/L2 rouer, which is R2 , a default route is generated and flooded to R3 , but not to R1 . Next Hop Ip router isis interface Serial0/0 The configuration of R2 is as follows (all configurations are omitted from the configuration of interface IP ): Interface eth 0/1 The refresh interval is 900s , and the timer value is adjustable. ! TE with Layer 2 overlay PHP penultimate jump pop-up mechanism Network 10.1.12.1 0.0.0.0 area 0 The LFIB table does not contain inbound interface information. FastEthernet0/0.12 (ldp): xmit/recv Select the path with the least number of hops Network 10.1.23.3 0.0.0.0 area 0 Note: a L1 / L2 router if the other area router adjacency relationship, it will to this area of the L1 router advertisement himself outlet, the specific method is the raw cost region L1 LSP when packets ATT bit Set 1 Reservable Bandwidth[0]: Level1 area default route [4]: Local Circuit ID Local circuit ID is a link identifier. The identity of this circuit is assigned by the router that sent the Hello PDU and is unique on the interface of the router. At the other end of the point-to-point link , the local circuit ID in the Hello message may or may not be the same value. Mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 Network 10.1.23.2 0.0.0.0 area 0 Bandwidth: 0 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF Metric Type: TE (default) *Aug 18 04:37:06.243: FILTER_SPEC type 7 length 12: Network 2.2.2.2 0.0.0.0 area 0 Physical_bw: 100000 (kbps), max_reservable_bw_global: 75000 (kbps) There are four metric types: Only when a neighbor solicitation label mapping message to the local strip prefix , local will announce the label mapping messages to neighbors Sub Pool See if you receive HELLO from the other party Mpls traffic-eng tunnels ip rsvp bandwidth This time we did the test, environmental test just a different, TE the Tunnel tail end now is to R4 of 4.4.4.4 . Extended OSPF and IS-IS to TE required information flooding in the network, then Tunnel head-end router can build your own TE Record Route: NONE Interface Serial0/1 Router ospf 1 The port in TCP/IP . Filter_Spec Object name DIS send HELLO interval ordinary packet router of 1/3 (default 3.3s ), which ensures DIS when a failure occurs can be more quickly found. Mpls traffic-eng tunnels ip rsvp bandwidth 42000 TLV The configuration of R2 is as follows (the tunnel is not configured temporarily ): 1230 Router(config)#tunnel mpls traffic-eng path-selection metric ? igp use IGP metric If the payload of the MPLS is an IPv6 packet, the load balancing is performed according to the source and destination addresses in the IPv6 header. IPv6 , then it must publish routing information with this NLPID value. Next-address 10.1.24.4 Signalling: connected 1230 Prefix OutLabel : FastEthernet1/0, implicit-null RSVP Signalling Info: 4.4.4.4/32 Current LSP: Interface fast 0/0 If the link or node fails, the traffic will be rerouted due to the failure. If the rerouting takes a few seconds, the high performance of the link will cause a large amount of traffic pointing to the fault point to be discarded. For some businesses, business interruption may result. There seems to be no problem in this environment, but the route summary has problems in the point-to-point LSP environment, such as MPLS VPN , TE. Mpls traffic-eng tunnels ip rsvp bandwidth Eventually this tagged package with 403 and 505 is sent to the TE Tunnel , so: !!! Peer LDP Ident: 3.3.3.3:0; Local LDP Ident 1.1.1.1:0 If the LSP database is too large, send multiple csnp Name: R1_t0 Status: Total Allocated BW (kbps) 1.1.1.1:0 Bandwidth: 2000 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF Metric Type: TE (default) IGP metric: 1 i ia 5.5.5.0 [115/158] via 10.1.123.2, FastEthernet0/0 10.0.0.0/24 is subnetted, 4 subnets The configuration of R1 is very critical, let's focus on it: Path: valid IGP Area[1] ID:: ospf area 0 System Information:: Of course, both IS-IS and OSPF have been successfully tested during the test and have been eligible for the ISP network intranet IP routing protocol. Both protocols have achieved some new extensions over the past few years. For example , support for MPLS TE ,ccna exam modules, support for IPv6 , and so on. On the other hand, one of the more intuitive phenomena we can observe is that OSPF has much more technical documentation than IS-IS .