ccna ccna

ccna ccna

10.1.12.2 Ip router isis Ip cef 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). ! ! The change has occurred. In the head router, this will record the labels along the way. Fragment number : 0 Interface eth0 0/0 Similar to the concept of DR in OSPF O 3.3.3.3 [110/3] via 10.1.12.2 , 00:00:37, FastEthernet0/0 Show mpls ldp bindings !! Only one interface activates MPLS TE Cisco Router 's ISO addressing R1#sh mpls traffic-eng topology 1.1.1.1 0x2B7C ! Tunnel mpls traffic-eng autoroute announce Set priority Contains the tunnel's prioritization, hold priority, and some flags Mpls ldp router-id loopback0 mpls label range 200 299 interface fast0/0 Router ospf 1 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. R1(config-if)#isis authentication key-chain test level-1 R1(config-if)#isis authentication mode md5 level-1 Fspec: ave rate=20000 kbits, burst=1000 bytes, peak rate=20000 kbits History: Tunnel mpls traffic-eng path-option 10 dynamic C 1.1.1.0 is directly connected, Loopback0 2.0.0.0/24 is subnetted, 1 subnets Link connected to: a Transit Network Time since path change: 10 minutes, 34 seconds Number of LSP IDs (Tun_Instances) used: 521 R2#show mpls traffic-eng link-management advertisements Interface Ethernet0/1 Pop tag LAN Priority: 64 Format: Phase V It is only possible to establish adjacencies with neighboring routers at the same level. [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. 10.1.23.3 [MPLS: Label 300 Exp 0] 0 msec 0 msec 0 msec The TTL is placed in the label header. Turning off TTL propagation prevents the MPLS network from being exposed (by traceroute ). 0 kbits/sec Like all IS-IS packets, the HELLO package consists of a header and a TLV . neighbor is a neighbor of the LDP routerID accept acl to match the prefix ! R1#sh isis neighbors detail 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. *Aug 18 09:06:07.919: 1.1.1.1 (Strict IPv4 Prefix, 8 bytes, /32) Network 10.1.45.4 0.0.0.0 area 0 mpls traffic-eng router-id loopback0 mpls traffic-eng area 0 2.0.0.0/32 is subnetted, 1 subnets Mpls ip 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 Router(config)# mpls ldp session protection for acl-peer duration sencondes Complete basic IP configuration (configuration omitted) Link state ID *Aug 18 09:06:02.699: EXPLICIT_ROUTE type 1 length 52: ESH is ES transmitted to IS of 0/0/0 The TLVs used are: *Aug 18 11:31:44.598: The configuration of R2 is as follows: basic concept *Aug 18 09:06:07.919: SENDER_TEMPLATE type 7 length 12: Interface eth0/1 Route-target import 2345:2 Mpls ldp router-id loopback0 mpls label range 300 399 interface fast0/0 Tunnel mpls traffic-eng path-option protect 10 explicit name R2R3R4 Now let 's take the traffic going to 4.4.4.4 on the R1 to the tunnel , using one of the simplest methods: static routing. Except for HELLO packets based on UDP646 , other packets are based on TCP port number 646. Finally, let's complete the configuration of R1 : ! The configuration of R5 is as follows: ADSPEC Metric: 0 Ip address 55.55.55.55 255.255.255.255 Create a " pseudo-node LSP " in the broadcast subnet and advertise all the routes in the subnet (the LSP is similar to the LSA ) The configuration of R2 is as follows: One is a Point-to-Point IS to IS hello PDU . In fact, this is a metric trick, but when we are thinking about it, remember to take the virtual path of the tunnel into consideration. Exit-address-family Take a look at the routing table for R1 : 75000 A router can have up to 254 th Area ID . Of course, generally one router belongs to one area, and the situation of multiple areas may be used for merging, splitting or changing of areas (see below). Then by default, R1 goes to .5.5.5.5 and 55.55.55.55 is definitely preferred from E0/1 directly to R5 . But what if we want R1 to go to TE tunnel on .5.5.5.5 and 55.55.55.55 traffic ? ! Tspec: ave rate=20000 kbits, burst=1000 bytes, peak rate=20000 kbits RSVP Resv Info: The composition of the router , Backbone must be continuous. Experimental verification *Aug 18 09:06:07.919: Note CISCO IOS in, LDP will not BGP in IPv4 prefix bundled label. R2 (config-keychain)#exit *Aug 18 09:06:07.919: parameter id=127, flags=0, parameter length=5 10.1.34.4 [MPLS: Labels 403/505 Exp 0] 0 ​​msec 4 msec 0 msec Physical Bandwidth: 100000 kbits/sec Res. Global BW: 75000 kbits/sec Res. Sub BW: 0 kbits/sec Downstream:: PSNP (partial serial number PDU ) LSP refresh inverval is the periodic flooding time of an LSP . The default is 15 minutes, which is 900S . Type 1 length 12: FastEthernet0/0 (ldp): xmit/recv Enabled: Interface config 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 R1(config-keychain)#key 1 Local Outgoing Prefix Bytes Label Outgoing Next Hop Label Label or Tunnel Id Switched interface 202 IS ( layer 0 routing ), then the router will look up the destination address and forward the packet along the best path. !! Use the dynamic calculation method to establish the tunnel PATH R1 advertisement Loopback route .1.1.1.1 / 32 Hello interval: 5000 ms; Transport IP addr: 1.1.1.1 LDP Id: 2.2.2.2:0; no host route to transport addr Pop Label The unreservable bandwidth is the bandwidth remaining after being supplied to the TE , that is, the maximum bandwidth of the link minus the bandwidth currently reserved by the TE tunnel. This will cause R2 to calculate the route, from the tunnel0 port to the 5 and 55 route metric becomes 32+1=33 , which is greater than the metric=31 of the route taken from e0/1 . So the routing table of R2 has changed, and the routes of the 5 and 55 network segments have become: Name: R2-PE1_t0 Status: *Aug 18 09:06:07.919: Attached-bit RFC 3358 i ia 10.1.24.0 [115/148] via 10.1.123.2, FastEthernet0/0 i ia 10.1.45.0 [115/158] via 10.1.123.2, FastEthernet0/0 i ia 10.1.34.0 [115/158] via 10.1.123.2 , FastEthernet0/0 C 10.1.123.0 is directly connected, FastEthernet0/0 MAC address, etc. Each priority corresponds to an available bandwidth Control label notification through LDP (conditional notification) 42000 0 kbits/sec i L2 4.4.4.4/32 Look again at R4 's isis database : Neighbor 2.2.2.2 update-source Loopback0 Virtual link !! Note area0 and area1 must activate MPLS TE Router-id 2.2.2.2 Removal Trigger: configuration changed Establish mapping of data link layer address to network layer address ( CLNP address) Router(config)#tunnel mpls traffic-eng path-selection metric igp 5.5.5.5 Tun ID: 0 Ext Tun ID: 1.1.1.1 * 0x0000000C TE with Layer3 Take a look at the routing table for R1 : Was used to replace TLV128 . *Aug 18 11:26:02.546: Experimental needs 3.0.0.0/32 is subnetted,ccna ccna, 1 subnets Interface fast 0/0 Attribute tag and affinity attribute (Link ID) Designated Router address: 10.1.23.2 (Link Data) Router Interface address: 10.1.23.2 Number of TOS metrics: 0 Mpls ip Et0/1 4 10.1.12.1 1060 msec 984 msec 1080 msec Router-id 5.5.5.5 In the default implementation mode, the IIH packet is filled to the outbound interface MTU size (using the method of adding padding , as shown above). The router compares the local interface MTU with the received IIH size to ensure that it can be processed before forming the adjacency. The largest possible packet of neighbors. Labels 0-15 are all reserved labels. Here are some reserved tags that have a specific role: Fa0/0 Look at the example above: A is in the area 49.0001 , B is in 49.0002 , because they are in different areas, so they become Level 2 adjacencies. Maintain adjacencies in the region at the same time. If A is configured: SysID 10.1.12.2 [MPLS: Label 200 Exp 0] 4 msec 0 msec 0 msec The IS-IS network layer protocol ID in the ISO protocol stack is 0x83. Note: a FEC can contain multiple streams, but not a stream of a FEC , such as looking at a host Sina website, which is a stream and looking at Sina's video, which in turn is a stream, the two streams When Sina sends to a remote host, the path should be the same, so one FEC has multiple streams, but each stream does not belong to a separate FEC. ATT/P/OL PSNP (partial serial number PDU ) This will result in the OL bit of the LSP generated by R2 , and the result seen on R1 is this: The metric configuration only affects the tunnel endpoint router itself, and does not advertise to other neighbors. But the forwarding adjacency feature is different. Moreover, the two methods of modifying the metric are not used. The autoroute needs to match the autoroute keyword to modify the metric and only affect the configurator itself. In the forwarding adjacency, the metric is modified directly in the tunnel interface . For example , if ISIS is used , then the isis metric command. If ospf is used , it is ip ospf cost .