free download ccna exam paper pdf

free download ccna exam paper pdf

Router isis L1/L2 router re-releases external routes into IS-IS ( to level1 ) Reservable Bandwidth[6]: *Aug 18 09:06:07.919: Error Code: 24 (Routing Problem) !! The outbound label is 301 75000 TE Metric 75000 Note: a IS-IS routing domain ( routing Domain ) does not necessarily need to have two levels, if only a region of deployment, it may be all L1 or all L2 of , recommended L2 of , to obtain a good scalability. 562 OSPF , this is not the same as other IGP protocols. Therefore, if you want to make the routing full, you need to add a re-release directly to R3 . The principle is similar to the plaintext interface authentication, but can be given HMAC-MD5 certification. But if the router performing load balancing is a P router, what does it receive is a label package with multiple labels? We know that no matter how many tags you have, the tag stack is followed by the IP header, and the first field of the IP packet is version , if *Aug 18 11:26:02.546: Contains information such as the tunnel sender address, LSP ID, etc. Fa1/0 Router ospf 1 Addresses bound to peer LDP Ident: 5.5.5.5 Tun ID: 0 Ext Tun ID: 1.1.1.1 Ip address 10.1.56.5 255.255.255.0 *Aug 18 09:06:02.699: 10.1.24.4 (Strict IPv4 Prefix, 8 bytes, /32) Configure targeted-hello accept acl We have to change the topology: 75000 kbits/sec, Interface eth 0/0 Tag rewrite with Fa0/0, 10.1.12.2, tags imposed: {203} Is an extended form of type 2 TLV Only support IP RFC3209 RSVP-TE Extensions to RSVP for LSP tunnels describes the extension of MPLS TE function by RSVP protocol . And R2 routing table at the moment is such that: Token bucket fragment (service_id=1, length=6 words parameter id=127, flags=0, parameter length=5 Generated Mpls traffic-eng tunnels ip rsvp bandwidth R2# show ip route Mpls traffic-eng reoptimize events link-up *Aug 18 04:37:06.239: Error Node: 10.1.12.2 Activate the MPLS TE extension for each router's OSPF and manually set the RouterID for MPLS TE . Route summary ! MPLS TE considers configuring (static) bandwidth on the link Mpls traffic-eng tunnels mpls label range 500 599 Such as 39.0f01.0002. 0000.0c00.1111 . 00 TE router ID of the device *Aug 18 09:06:07.919: Minimum Path Bandwidth (bytes/sec): 2147483647 2.0.0.0/24 is subnetted, 1 subnets An NSAP address with a NSEL value of 0 is used to identify the device, which is the network address of the device, NET . Therefore NET is determined by the area Id and the system ID . In general, the biggest difference between NSAP addressing style and IP addressing style is that NSAP uses only one address to identify a router , while IP is assigned an Ip address for each port . 10.1.12.2 Interface Tunnel0 / / Whether the local will retain all the label mapping messages received from the neighbor in the database 10.1.45.4 Experimental procedure *Aug 18 11:31:44.598: Controlled Load Service break bit=0 service length=0 Fa0/0 3.3.3.3/32 ! Commonalities: IS-IS and ES-IS do not place routing information in IP or CLNP packets, but directly in the data link layer Frame (so that packaging is more efficient). 1bit 0/0/0 697 *Aug 18 09:06:07.919: After receiving the label from the tail router, the penultimate hop router uses the label as the outbound label of the TE tunnel , and assigns a label to the tunnel and places the label in the label object in the RESV message. Send it to its own upstream router. Mpls traffic-eng tunnels ip rsvp bandwidth IS-IS basic module [115/10] via 10.1.123.2, FastEthernet0/0 (Tunnel0) Destination: 5.5.5.5 In R2 configuration backup link, R2 increase in the following configuration: The TLV section contains fields for system characteristics, as shown below: Record Route: NONE description State: explicit path option 10 is active 10.1.12.2 10.1.12.1 Interface tunnel0 Phenomenon observation ! *Aug 18 11:31:44.598: Neighbor 5.5.5.5 send-community extended exit-address-family 75000 Network 10.1.34.4 0.0.0.0 area 0 i*L1 0.0.0.0/0 [115/10] via 10.1.123.3, FastEthernet0/0 When the router receives an ISH packet on a point-to-point link , the router checks the local neighboring database to see the source of the packet. Ip explicit-path name R3R4 enable next-address 10.1.23.3 Prefix *Aug 18 09:06:07.919: Label Router-id 5.5.5.5 LSP , using LSP to carry all routing information Mpls traffic-eng tunnels mpls label range 100 199 103 Local tag The TEDB already has link state information in all areas, so there is no need to use the IGP routing protocol. IGP Area[1] ID:: ospf area 0 System Information:: Router(config)#mpls traffic-eng reoptimize timers frequency ? 1.0.0.0 Router(config)#mpls traffic-eng reoptimize timers frequency ? Mpls traffic-eng tunnels mpls label range 400 499 FastEthernet0/0 via high priority queue 103 Link state information IGP itself supports 10.1.12.2 1010 (The router address and link information in the result of capturing the packet are respectively). Priority 2 : 9375000 Label End system adjacency routing Interface eth0/1 5 10.1.12.2 Therefore, the MPLS VPN environment, if we MPLS VPN Backbone inherent R1 to R5 establish a TE the Tunnel , is not 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 . Tunnel mpls traffic-eng autoroute metric relative z Ip address 1.1.1.1 255.255.255.0 ip router isis To form an adjacency relationship. Extended OSPF and IS-IS to TE required information flooding in the network, then Tunnel head-end router can build your own TE 0/0/0 Outgoing The configuration of R2 is as follows: Although the L1 / L2 router having both L1 and L2 function, but sometimes simply Establishing a specific interface on a layer adjacent relationship,free download ccna exam paper pdf, are arranged on the other interfaces in the first 2 layers adjacent relationship. The labels constituting the LFIB may not be distributed by LDP , and the RSVP allocation label is used in the MPLS traffic engineering . In the MPLS VPN , Ip address 55.55.55.55 255.255.255.255 Priority 5 : 9375000 *Aug 18 11:31:44.598: 1 Finally choose the red path above because the TE metric of this path is smaller Interface Loopback0 i L1 Router ospf 1 vrf VPN-A redistribute bgp 2345 subnets network 10.1.56.5 0.0.0.0 area 0 R1 # show mpls forwarding-table R1 of LFIB table For certification Do not advertise routes re-published from other routing protocols Show mpls ldp discovery detail Show mpls ldp parameters Show mpls ldp neighbor *Aug 18 11:26:02.546: The virtual link implements a level 1 repair path through the backbone . The zone designated router sets the partition repair of its level1 LSP . Label Network 10.1.34.3 0.0.0.0 area 0 The configuration of R2 is as follows (all configurations are omitted from the configuration of interface IP ): A list of directly connected IP address prefixes is listed, which is only used in non-pseudo-node LSPs . LDP is in Frame Mode . The LSR assigns a label to each route. The local direct route is assigned a POP. 13223 TCP connection: 2.2.2.2.61914 - 1.1.1.1.646 0x26DC Priority 3 : 9375000 *Aug 18 11:31:44.598: Path MTU: 1500 ! Interface fas0/0 10.1.12.2 4 msec 4 msec 0 msec Ip cef The configuration of R2 is as follows: R1#show mpls forwarding-table i ia 5.5.5.0 [115/158] via 10.1.123.2, FastEthernet0/0 10.0.0.0/24 is subnetted, 4 subnets Then on R1 to see the tunnel , his TE metric becomes 102 . Show mpls traffic-eng topology ? Like all IS-IS packets, the HELLO package consists of a header and a TLV . 404 After the configuration is complete, we find that the adjacency relationship between R1 and R2 is UP , that is, the area authentication does not carry the authentication information in the IIH packet. Not only that, but the PSNP sent by R1 also has no authentication information, but the issued LSP has clear text authentication information. The experimental phenomenon is quite interesting. For R1 , all IS-IS messages received by R2 are not authenticated. R1 mainly focuses on LSP . It is found that the LSP sent by R2 has no TLV for authentication , so R1 ignores The LSP sent by R2 causes the routing table of R1 to be empty. However, although the LSPs sent by R1 are all with authentication information, R2 is not enabled.Area authentication, so R2 receives this packet, can also read, and can also use these LSPs , so R2 can learn the route of R1 .