ccna test king

ccna test king

TLV 22 : Extended intermediate-System Reachability Link IP Address: 10.1.23.2 0xCC Level1 area Interface eth 0/2 *Aug 18 04:37:06.239: ADSPEC type 2 length 48: R2#show ip route Certification Information The static route forwarding mode of the MPLS TE tunnel supports route recursion. 10.1.12.2 Link Link LSP refresh inverval is the periodic flooding time of an LSP . The default is 15 minutes, which is 900S . Tu0:403 Now we will complete the following configuration on R2 : !! Change the TE tunnel 's setup priority and hold priority to 5 Fa0/0 *Aug 18 09:06:07.919: version=0, length in words=7 Mpls ip We can avoid this problem by using overload-bit . The command is explained as follows (configured under the router isis process): In R2 configuration backup link, R2 increase in the following configuration: R3.00-00 Basic Experiment 2 ( IS-IS ) The configuration of R2 is similar, so that in the TLV used for authentication in the IIH , the ciphertext after the hash is loaded, and the password is not exposed. ! LDP IP before 4B is when there is a loopback when interfaces, loopback maximum interface IP , if there is no lp interface, is the largest active physical interface IP , use the following command to change: System ID 6 -byte system ID , ES or IS identifier, similar to OSPF 's Router ID , each device has a system ID , and the IP network, each interface has an IP , which is the difference between one of . Note: The SystemID must be unique across the entire Area and trunk ( Level2 ). Contains information such as the tunnel destination address, tunnel ID , and extended tunnel ID (that is, the tunnel start point) Regular area (non-backbone area) Interface Loopback0 10.1.12.2 Outgoing interface Config Parameters: 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. The configuration of R2 is as follows: Record Route: NONE R3#show ip cef exact-route 10.1.35.55 1.1.1.1 End LSP ID : End LSP ID . Indicates the last LSP ID of the LSP range described in the TLV field . Activate RSVP on the interface and configure reserved bandwidth (optional) The interface of each router activates RSVP and MPLS TE tunnel support. Based (internet per-Platform ) compared to the label space-based interface ( per-interface ) security label space to lower Regional separation Still this figure, but the configuration of R2 becomes: Interface Redistribute ospf 1 vrf VPN-A match internal external 1 external 2 exit-address-family Configure on R2 as follows: Label subobject: Flags 0x1, C-Type 1, Label 200 4.4.4.4/32, Flags: 0x20 (No Local Protection, Node-id) Label subobject: Flags 0x1, C-Type 1, Label 403 5.5.5.5/32, Flags: 0x20 (No Local Protection, Node-id) Network 10.1.23.2 0.0.0.0 area 0 mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 LSPID Interface loopback0 *Aug 18 11:31:44.598: Nodes level and area level Interface Ethernet0/0 We see that there are two layers of labels here. Therefore, R2 pushes the original IP packet into a layer of VPN label 505 and pushes in two layers of labels 305 403 . It is noted here that the label 403 is the LDP label assigned by R4 with the prefix 5.5.5.5/32 , which is passed to R2 through the targeted LDP connection . And 305 is the label that R3 assigns to the TE tunnel through RSVP . Remote binding: tsr: 2.2.2.2:0, tag: imp-null tib entry: 10.1.13.0/24, rev 8(no route) In area 49.0001, we can see that all routers flood their own LSPs . LSPs are represented by LSPIDs , such as R1.00-00 . This R1 is the hostname of the device . Here we have the default hostname mapping mechanism. See above. . In addition , 00 after R1 is a pseudo node identifier, and 00 means that the originating router of the LSP is not a DIS , and then the last 00 is a fragmentation flag. 0x00000037 Tunnel mpls traffic-eng path-option 10 explicit name R3R4 Flooded Links: 2 33M If the payload of the MPLS is an IPv4 packet,ccna test king, load balancing is implemented by hashing the source and destination IP addresses of the IPv4 packet header . Traffic engineering ( Traffic Engineering ) we can be loosely understood as "the ability to control traffic across the network," we can by TE allows the deployment of traffic in an optimal way transmission from one node to another node in the network. Flag position The composition of the router , Backbone must be continuous. AutoRoute: disabled LockDown: disabled Loadshare: 20000 bw-based 10.1.23.2 R2-PE1#show mpls traffic-eng tunnels The configuration of R2-PE1 is as follows: After everyone's LFIB is built, we can see that when A receives an IP packet and wants to access X , then A checks its own CEF table. Each transport layer entity is assigned an NSAP address. The NSAP address is the network layer address of the CLNS packet . It is used to identify the device. It consists of an initial domain part ( IDP ) and a domain-defined part ( DSP ). These two parts are detailed below, let us understand this. 10.1.12.2 300 *Aug 18 09:06:02.699: SESSION type 7 length 16: 10.1.23.3 In the standard SPF algorithm, there can be multiple equivalent paths to the same destination. We call it ECMP ( Equal-cost Multipath ). Or Tunnel Id *Aug 18 11:26:02.546: *Aug 18 09:06:07.919: SENDER_TSPEC type 2 length 36: Interface Tunnel0 10.1.12.2 Integrated IS-IS Broadcast multi-access link *Aug 18 04:37:06.239: General Parameters break bit=0 service length=8 10.1.123.0 is directly connected, FastEthernet0/0 0.0.0.0/0 [115/10] via 10.1.123.3, FastEthernet0/0 IS-IS can be used purely for IP routing, or it can be used purely for ISO routing, or both. Frame-relay map ip 10.1.123.1 201 broadcast TE metric: 1, IGP metric: 1, attribute_flags: 0x0 Ip router isis Mpls traffic-eng signalling advertise implicit-null [acl x] The loopback0 address space of all devices is xxxx/32 , and x is the device number. 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. * 0x0000000B Frame-relay map ip 10.1.123.3 301 broadcast frame-relay map clns 301 broadcast OutLabel : Ethernet0/0, 200 RSVP Signalling Info: New object for RSVP-TE extension Prefix How long in msecs to wait upon flooding a down forwarding adjacentcy Outgoing *Aug 18 11:26:02.546: Interface Tunnel0 MPLS TE can change the bandwidth and attribute parameters of the link through adaptation. Set-overload-bit on-startup <5-86400 sencondes> The label assigned to the prefix is available on any local MPLS interface and will be distributed to all LSR neighbors. This can be area at any level within the router adjacency relationship; may be other area adjacent L2 or L1 / L2 router forming L2 For the first layer LSP database, you use the first 1 layer CSNP and PSNPs , for the first 2 used in the first layer 2 layer CSNP *Mar 1 00:00:32.755: ISIS-Upd: Building L1 LSP 2 The route prefix is ​​learned locally by the IGP , but the next hop router of the route prefix must advertise the label mapping message corresponding to the prefix to the local, and the local will assign a label to the prefix. i L2 Exit OSI PDU IS-IS only supports reliable diffusion on point-to-point links, and the spread on the broadcast link is unreliable. However, periodic broadcasts through DIS Mpls traffic-eng tunnels ip rsvp bandwidth There are two types of tunnel priorities: Its ingress and exgress LSRs Each IP prefix is ​​assigned a bunch of metrics . Tunnel destination 5.5.5.5 Network 10.1.34.3 0.0.0.0 area 0 1bit The TLV section contains fields for system characteristics, as shown below: Mpls traffic-eng tunnels ip rsvp bandwidth Router ospf 1 vrf VPN-A redistribute bgp 2345 subnets network 10.1.56.5 0.0.0.0 area 0 There are actually some hidden dangers here. For example, using traceroute may expose the internal structure of the network ( after TTL=0 , the router will return an error message, which may expose network information). 6 SRM and SSM are used to coordinate diffusion and database synchronization Flooding Status: ready 2 10.1.23.3 [MPLS: Labels 305/403/505 Exp 0] 8 msec 4 msec 4 msec R4 the loopback port) of the OSPF Metric =. 3 , so the default TE metric = 3 Configuring multiple NETs for a single IS-IS process Bw[4]: Control metric through dynamic routing protocol to affect routing routing Ip cef R1(config-keychain)#exit 9 Outgoing Tunnel mpls traffic-eng autoroute announce Interface Ethernet0/0 Router(config)#tunnel mpls traffic-eng path-selection metric igp Outgoing R3#sh mpls forwarding-table Set-overload-bit Interface fa0/0 Tunnel mpls traffic-eng path-option 10 dynamic Recommendations for Interoperable IP Networks using IS-IS Reservable Bandwidth[4]: *Aug 18 04:37:06.243: Shared-Explicit (SE) Ip cef 5.5.5.5 [110/2] via 0.0.0.0, 00:00:01, Tunnel0 Test 1 : set-overload-bit The RSVP transmits the signaling in the path for the TE tunnel, but it also carries the obligation of MPLS label distribution, so that the packet can be label-switched along the path of the TE tunnel. 0x0000000C ! LockDown: disabled Loadshare: 2000 Oper: up Configuration change 2 *Aug 18 04:37:06.239: Tun Sender: 1.1.1.1 LSP ID: 20 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 : 4 --------------- 0 ! *Aug 18 09:06:07.919: version=0 length in words=10 Test the transmission process of the data stream, observe the phenomenon Router-id 1.1.1.1 OAM alarm tag Interface Loopback0 *Aug 18 11:31:44.598: Pop tag (Link ID) Network/subnet number: 2.2.2.2 (Link Data) Network Mask: 255.255.255.255 Number of TOS metrics: 0 The boundary of the area is on the link Mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 You can see Path weight=3 . How did this 3 come from? Because R1 establishes a tunnel to R4 , then R1 reaches R4 (note that it is not Name: R1_t0 Network 10.1.12.2 0.0.0.0 area 0 Provide network stability Network 10.1.34.4 0.0.0.0 area 0 There is a unique NET ! Attached-bit *Aug 18 09:06:07.919: Path MTU: 4294967295 !!! I/E The static route forwarding mode of the MPLS TE tunnel supports route recursion. Reservable Bandwidth[2]: Outgoing interface lab environment The RSVP transmits the signaling in the path for the TE tunnel, but it also carries the obligation of MPLS label distribution, so that the packet can be label-switched along the path of the TE tunnel. Do not advertise routes re-published from other routing protocols MPLS does not assign labels to BGP routes, but assigns labels to the next hop of BGP routes. IS reachability For example, in the above example, tunnel0 is established in R3 to R7 . For R1 and R2 , they do not know the existence of the tunnel . When they go to 7.7.7.7/32 , only the IGP 's own routing is performed. Calculation, then R2 is likely to take the path of R4-R6-R7 , but we may prefer that these traffic can be transmitted through the tunnel , then for this requirement, autoroute can not be achieved, need to use Forwarding ajacency .