ccna syllabus 2015 pdf

ccna syllabus 2015 pdf

*Aug 18 11:26:02.546: 4 is IPv4 . If it is 6 or IPv6 , the LSR uses this value to determine whether the message is V4 or V6 , and then selects a complex equalization algorithm according to different IP versions. PHP penultimate jump pop-up mechanism Reservable Bandwidth[1]: Options: (No TOS-capability, DC) LS Type: Router Links The status of IP traffic engineering Router ospf 1 Can be modified as the basis for calculating the shortest path of the TE tunnel 33M *Aug 18 09:06:02.699: EXPLICIT_ROUTE type 1 length 52: Network 10.1.23.2 0.0.0.0 area 0 mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 *Aug 18 04:37:06.243: SESSION type 7 length 16: Create a TE tunnel on R1 , the source is its own loopback0 , and the destination is 4.4.4.4 of R4 . Config Parameters: Ip router isis Network 1.1.1.1 0.0.0.0 area 0 10.1.12.2 Interzones can only be interconnected via L2 or L1/L2 routers The routing table for R1 is as follows (direct route is ignored): NLPID: 3 N/P Untagged 202 DN *Aug 18 04:37:06.243: peak rate = 250000 bytes/sec Reservable Bandwidth[6]: All routers in the area (except the border router) can only establish neighbor relationships with routers in the area. There are two types of tunnel priorities: CLNP is similar to the IP protocol except that it serves the ISO transport layer. IS-IS , ES-IS , and CLNP are network layer protocols that are encapsulated directly in the data link layer frame. Compared with the OSPF packet in TCP/IP , it is hidden behind the IP header. The encapsulation efficiency of the former protocol packet is higher. AutoRoute Next Hop 0x00000010 Outgoing The last byte of the NSAP is used to identify the program on the same device, similar *Aug 18 09:06:07.919: parameter id=127, flags=0, parameter length=5 For the device number, this IP is also the LDP routerID . L2 router *Aug 18 09:06:07.919: Token bucket fragment (service_id=1, length=6 words POP is the TTL of the top-level tag minus 1 and then pops up. The new TTL value is written to the top-level tag of the outbound data. Nexthop 10.1.12.2 FastEthernet0/0 label 204 *Aug 18 09:06:07.919: Error Code: 24 (Routing Problem) This global command is used to modify it. After the expiration of the timer, the IGP will establish an adjacency on the link. Once the IGP adjacency is established and the LDP session has not been synchronized, the IGP will advertise the metric of the link to the maximum. Area address 1bit i L1 10.1.34.0 [115/20] via 10.1.123.3, FastEthernet0/0 C 10.1.123.0 is directly connected, FastEthernet0/0 i* L1 0.0.0.0/0 [115/10] via 10.1.123.3, FastEthernet0/0 It should be noted that usually the terminal systems in our live network environment, such as PCs , do not use ES-IS because these PCs are running 0 kbits/sec Experimental needs Look at the LDP neighbor on R2 : The R2 re-released 2.2.2.0 external route is still there; the inter-area route is gone, except for a R2 local direct connection of 24.0 ; in addition, R1 still does not use R2 as the next hop of the default route. It became untagged , before it was POP , why is it untagged now? Analysis, we modified the R2 's loopback mouth, into 2.2.2.2/24 , then for R2 own, this is the direct route 2.2.2.0/24 , right? R2 may for this 2.2.2.0/24 assign a label, since it is directly connected, so R2 to this prefix divided empty tag 3 . Then send the label mapping message to other LDP neighbors including R1 and R3 : IGP Neighbor: ID 10.1.23.2 4 is IPv4 . If it is 6 or IPv6 , the LSR uses this value to determine whether the message is V4 or V6 , and then selects a complex equalization algorithm according to different IP versions. *Aug 18 09:06:02.699: Outgoing Path: !! The path message sent by R1 has changed. No synchronization State: Oper; Msgs sent/rcvd: 16/16; Downstream Up time: 00:05:38 By default, the IS the IS- retention time ( Holding-Time ) for the 30s , Source-based routing can be used here. This LSP is called an MPLS TE tunnel. It is one-way. And the configuration of the tunnel only needs to be performed on the headend LSR . L2 router Fa0/0 Ip address 10.1.45.4 255.255.255.0 Or Tunnel Id MPLS TE traffic forwarding 0x0000000E !! Path error message sent by R2 to R1 !! Activate mpls on the interface , actually activate ldp 0 packets, 0 bytes tag information set AutoRoute: enabled LockDown: disabled Loadshare: 2000 bw-based auto-bw: disabled Router-id 4.4.4.4 Election DIS . In this network, the DIS will generate and flood the new pseudo-node LSP on each of the routing layers it participates in (whether L1 or L2 ) and on each LAN it is connected to . Each router on the LAN establishes adjacency with all other routers and DISs , and does not elect to back up the DIS router. The elected DIS does not guarantee that it will always be DIS . 0x4F65 75000 1178 Environmental description i ia 5.5.5.0 [115/158] via 10.1.123.2, FastEthernet0/0 10.0.0.0/24 is subnetted, 4 subnets R1(config)#interface fa0/0 RFC 2205 Resource Reservation Protocol (RSVP) Interface eth0/1 ! Router isis RSVP The acl-peer is an association ACL used to match the LDP peer to be protected . Note that the matching ACL must be the neighbor's LDP router ID. Load balancing of tagged messages Interface eth 0/2 Interface loopback0 10.1.45.4 10.1.45.5 75000 SNPA is equivalent to the Layer 2 address of NSAP or NET . 1 class 2 class LSA may carry a plurality of IP prefixes; 3 class 4 class 5 class LSA only carry a single IP prefix, if necessary send multiple IP prefix information, a plurality of LSA TLV R2 will immediately trigger a new LSP and clear the ATT , which causes R1 not to use R2 as the next hop for the default route. ISO10589 75000 In order to ensure the simplicity of the experimental environment first, I will ignore the existence of the R4 and R4 direct links. When you don't exist, you will be there. Checksum: 0x6FEB Length: 132 MPLS TE using type 10 of LSA to a region within MPLS TE work. ( NLPID 0x81 ) and IP ( 0xCC ) Bandwidth: 20000 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF Metric Type: TE (default) Route-map test permit 10 router isis LFIB label forwarding information base Mpls traffic-eng tunnels ip rsvp bandwidth Mpls traffic-eng tunnels mpls label range 400 499 LDP ID election is the same as OSPF routerID Route summarization on the L1/L2 router ( to level2 ) Interface eth0 1/0 Router-id 4.4.4.4 Version:1 flags:0000 cksum:7931 ttl:255 reserved:0 length:132 Router ospf 1 103 The local device will actively advertise the generated label mapping message to all LDP neighbors. 0x8973 Ip cef Router(config-if)#tunnel mpls traffic-eng priority 6 6 RSVP 697 0 kbits/sec Peak rate *Aug 18 09:06:07.919: Path Latency (microseconds):0 The distribution of the label is like this: 303 TE metric: 1 Link connected to: a Transit Network Name: R1_t0 Neighbor discovery is performed by means of the Hello packet of UDP . The source and destination port of this Hello packet are both UDP646 . Regional merger Used to confirm and request link status information Network 10.1.12.2 0.0.0.0 area 0 Flooding Status: ready Affinity Bit : 0x0 IGP Metric : 1 R1.00-00 Access-list 100 deny udp any any eq 646 access-list 100 permit ip any any 1.0.0.0 *Aug 18 04:37:06.239: version=0,ccna syllabus 2015 pdf, length in words=7 Net 49.0001.0000.0000.0002.00 Tunnel mpls traffic-eng autoroute announce tunnel mpls traffic-eng priority 7 7 If you change the Path-selection metric to igp , the shortest path to the tunnel will ignore the configuration in the physical interface. Alternatively, you can configure the following command on the tail router: Options: (No TOS-capability, DC) LS Type: Router Links Next Hop Comparison of terms between IS-IS and OSPF : *Aug 18 09:06:02.699: Path MTU: 1500 Net 49.0002.0000.0000.0004.00 ! In R2 on System Id Type Interface IP Address State Holdtime Circuit Id Version:1 flags:0000 cksum:7931 ttl:255 reserved:0 length:132 Network 10.1.34.3 0.0.0.0 area 0 You can use router(config)# ip rsvp signalling rate-limit to limit the rate at which signaling messages are sent or use router(config-if)# hold-queue x in to limit the rate of reception. 10.1.23.3 [MPLS: Label 300 Exp 0] 0 msec 0 msec 0 msec Mpls traffic-eng router-id loopback0 The configuration of R1 is as follows: Interface eth0 0/0 The main function of the ES-IS protocol is to provide mapping of NSAP addresses to SNPA addresses for network devices . Version : value is 1 R1(config)#key chain test R1(config-keychain)#key 1 Interface fa0/0 mpls ip metric [1]: 75000 kbits/sec O C . There is a small detail, noted that the distribution of the label no concept of split horizon, that although B may be from C to learn the route to X , but B still will be prefixed with X passed to the bundled label C . C will also put the label passed from B in the LIB , but don't worry about loops, because LDP can prevent loops by means of IGP routing protocol. RouterID , or the IP address of the interface . 5.5.5.5 Ip cef Show mpls ldp bindings Src 2.2.2.2, Dst 5.5.5.5, Tun_Id 0, Tun_Instance 5 RSVP Path Info: Network 10.1.23.2 0.0.0.0 area 0 Tunnel mpls traffic-eng bandwidth 2000 Prefix Solution: R1 and R4 use the loopback interface to establish IBGP neighbor relationships. Ordered control mode : Odered Control Static route *Aug 18 09:06:02.699: version=0, length in words=7 Removal Trigger: re-route path verification failed Mpls traffic-eng tunnels ip rsvp bandwidth ! DC Attached-bit Ip cef See below for more details on how labels are handled. Mpls traffic-eng tunnels ip rsvp bandwidth ! Mpls traffic-eng tunnels ip rsvp bandwidth After completing the above configuration, we find that the is-is neighbor relationships of R2 , R3, and R3 and R4 are UP . This is because the IIH package does not carry TLV information for verification . In addition, the routing table of R3 is empty. Min unit=0 bytes, max pkt size=2147483647 bytes Above we can see the reservable bandwidth of all tunnel priorities. Now let's modify the reservable bandwidth of the tunnel with priority 6 . ! Error notification 5.5.5.5/32, version 22, epoch 0, cached adjacency 10.1.34.3 Link state information IGP itself supports Interface loopback0 For certification *Aug 18 09:06:07.919: SENDER_TSPEC type 2 length 36: Mpls traffic-eng tunnels ip rsvp bandwidth Note that we are studying the label allocation of frame-mode . All interconnected IPs are shown O 2.2.2.2 [110/2] via 10.1.12.2, 00:00:37, FastEthernet0/0 Interface Loopback0 Router ospf 1 Mpls traffic-eng tunnels ip rsvp bandwidth Mpls traffic-eng tunnels ip rsvp bandwidth Fa0/0 Network 10.1.45.4 0.0.0.0 area 0 Router ospf 1 So far, the basic configuration has been completed. Now let 's create a TE Tunnel on R2 : Various bandwidth information !! The unit is Bytes , multiplied by 8 is 100Mbps The IS-IS related interface is Up or Down . 908 Interface Ethernet0/0 R1#sh mpls ldp bindings We can still see the label bundles passed by R3 before in the LIB table of R1 : 10.1.23.3 The Chinese translation of the verbatim word is "completely literal." The purpose of this is to preserve the EXP field in order to preserve QoS. The configuration of R4 is modified as follows: Set as a P2P sub-interface or broadcast link (if it is fully interconnected) The penultimate hop pop-up mechanism has two types of labels, one is POP or implicit null , the label value is 3 in LDP , the other is explicit null , and the label value is 0 in LDP . If the tag value sent by the neighbor about a route is 3 , then when I send the data to the neighbor, I will pop the tag and transfer the inner data to the neighbor. If the neighbor has a tag value of 0 for a route , the local device will send a label ( zero ) to the neighbor and send it to the neighbor.