ccna syllabus 2016 pdf

ccna syllabus 2016 pdf

1.0.0.0/24 is subnetted, 1 subnets Needless to say this? Activate CEF ! Outgoing tag or VC Bgp router-id 5.5.5.5 10.1.23.3 Circuit type : 01 means L1 router, 10 means L2 router, 11 means L1/2 router value The configuration of R1 is as follows: A label switched path (LSP) Traditional TE solutions have the following examples: MPLS TE path optimization Mpls traffic-eng tunnels ip rsvp bandwidth Eventually this tagged package with 403 and 505 is sent to the TE Tunnel , so: FastEthernet0/0 (ldp): xmit/recv Enabled: Interface config Next, add a PVC between R2 and R3 : ! IS-IS routers belong to only one specific area MPLS application 668 MPLS TE status State: Oper; Msgs sent/rcvd: 13/13; Downstream Up time: 00:04:05 0 kbits/sec In this environment, since the tail end of the tunnel is at R4 , the label that R4 assigns to this tunnel through RSVP is POP . RFC1195 As I said earlier, the NSAP address has an area adddress part that is longer, so when we get an address, how do I know which part of the address corresponds to what? Cisco IOS software from the right explanation NSAP address (here use NSAP of OSI format). First, counting from the right, the first B is NSEL , the left 6B is SystemID , and the rest is AreaID . The TEDB already has link state information in all areas, so there is no need to use the IGP routing protocol. ! Frame-relay map ip 10.1.123.3 103 broadcast frame-relay map clns 102 broadcast Verify view Virtual link Or Tunnel Id SRM ( Send Routing Message ): Send routing information message For IP applications , 1 byte defines AFI in the NSAP address , at least 2 bytes defines the actual area information, 6 bytes defines the system ID and Record Route ( RRO ) Tunnel mpls traffic-eng bandwidth 2000 Safety and certification Nexthop 10.1.12.2 FastEthernet0/0 label 204 Since the IP packet is generated on the initial router, the CEF table is searched . With the " show ip cef detail " command, you can see from the output whether the route is pushed into the label. The distribution label is based on The prefix in the CEF table is assigned. Configuration command Retention mode : Label Retention *Aug 18 04:37:06.243: version:1 flags:0000 cksum:FFAA ttl:255 reserved:0 length:92 Record Route ( RRO ) And OSPF difference is that a router must belong to a whole region, the border area can not on the router, it said, the interface can not belong to a certain area, the other interface belonging to other regions If a router plurality of distribution on the net, these NET system ID must be the same. Network 1.1.1.1 0.0.0.0 area 0 ! ESH is ES transmitted to IS of Complete basic IP configuration (configuration omitted) Can quickly converge when the network fails Removal Trigger: re-route path verification failed Both support two levels of hierarchical routing MPLS supports multiple Layer 3 protocols LSP various types of TLV R1# Tunnel mpls traffic-eng autoroute metric absolute y In fact, it is for CLNS , and it has been expanded to become an integrated IS-IS , which can support IP routing. IS 3.3.3.0 [115/20] via 10.1.34.3, Serial0/0 Use the clns host command in global configuration mode to establish a mapping of hostnames to NSAP addresses. In this way, in the link state database, LSP *Aug 18 11:31:44.598: 0x00000011 This TLV , in this way, provides a simple and reliable mechanism for advertising hostname information. As shown in the figure below, this is an LSP message: Ciphertext interface authentication 1 Mpls ldp router-id Loopback0 10.1.23.2 4.4.4.4/32 Auto Route : 0x80000001 0x0090AA 0 *Aug 18 09:06:07.919: General Parameters break bit=0 service length=8 OutLabel : Ethernet0/1, 305 Therefore, R2 receives the packet destined for 6.6.6.6 and first pushes the inner VPN label of 505 . Periodic reoptimize Circuit type : 01 means L1 router, 10 means L2 router, 11 means L1/2 router From the above figure, we can see that R1 and R4 act as L1 routers and only maintain the link state database of Level1 , and R2 and R3 are L1/L2. The loopback0 address space of all devices is xxxx/32 , and x is the device number. Bgp router-id 5.5.5.5 ! Router(config)#mpls traffic-eng tunnels The IS-IS packets have the same common 8B above , and the additional header fields are different, and then the TLV field. At the time of packet capture , the ternary in the TLV : type, length, variable length content, type and length in the packet, the packet capture software may not be presented,ccna syllabus 2016 pdf, but the type and length can be found from the binary code of the packet capture result. content. Primary lsp path: 10.1.12.1 10.1.12.2 The configuration of R1 is very critical, let's focus on it: We see that due to the updated LSA in R2 , the metric is set to 65535 for the directly connected network segment 10.1.12.0/24 . Therefore, in the routing table of R3 , we see 1.1.1.1/32 and 10.1. The 12.0/24 routing metrics are both bizarre. Look again at the Type 1 LSA produced by R2 : Provide a loop-free network ! The downstream label was not transmitted, because LDP Neighbor was not established. OutLabel : FastEthernet1/0, 301 In IPv4 , the empty tag is 0 , and the ipv6 is 2 . 0 kbits/sec Local Ip route 5.5.5.5 255.255.255.255 Tunnel0 You can see the main two contents contained in it: one is the directly connected network segment of R1 , here is 10.1.123.0 and 1.1.1.0 , and the other is the direct connection of R1 . Affinity: 0x00000000 OSPF Router with ID (2.2.2.2) (Process ID 1) Router Link States (Area 0) Of course, if you are running in a single zone, you can use a full L1 router or a full L2 router solution. The initial environment is as shown above, and the traffic from R1 to R8 has been carried on the green path shown in the figure. 1096 Its ingress and exgress LSRs Default route injection Ip unnumbered Loopback0 Interface eth 0/1 Switched Network 55.55.55.55 area 0 Tunnel priority Fa0/0 Although the implicit null tag also uses a tag with a tag value of 3 , tag 3 will never appear in the tag stack of the MPLS message, which is why it is called an implicit null tag. 10.1.12.2 IS-IS packets are encapsulated in data link layer frames. 4.4.4.4/32 IS-IS Router ospf 1 InLabel : - 6bits The configuration of R1 is as follows (the tunnel is not configured temporarily ): After the LSP is sent, the SRM is set. Routing entry for 5.5.5.0/24 *Aug 18 09:06:07.919: Path Latency (microseconds):0 LDP discovery sources: Tu0 R2(config)#key chain test R2 (config-keychain)#key 1 The TTL is placed in the label header. Turning off TTL propagation prevents the MPLS network from being exposed (by traceroute ). 10.1.23.2 10.1.23.3 Next-address 10.1.45.5 The loop detection mechanism of LDP depends on the IGP protocol. L1 router Router-id 4.4.4.4 IS-IS packets are encapsulated in data link layer frames. Experimental procedure Network 4.4.4.4 0.0.0.0 area 0 Wait for the message to view the adjacency. Next, the DIS election process begins . The OSPF adjacency relationship will not be established until the LDP session is successfully established or the "synchronization hold time" expires . The synchronization here indicates that the local label bundle has been sent to the LDP peer through the LDP session . However, if A is activated on the router and MPLS LDP-IGP is synchronized, and there is only one link between A and B , and no other available path to B , the OSPF adjacency will never be established. Because OSPF waits for the LDP session is established, but the LDP session can not be set up because A can not learn in its routing table B of LDP routerID route, so enter an infinite loop, OSPF and LDP adjacencies will never Unable to create. In this case, LDP-IGP synchronization will activate the OSPF adjacency unconditionally , so that the link will advertise the largest.The metric value until the synchronization is complete.