ccna router simulator

ccna router simulator

Next Hop Each tag mapping message contains two elements : FEC TLV and Label TLV 0x0000000D 10.1.34.4 [MPLS: Label 403 Exp 0] 0 msec 0 msec 4 msec Tunnel mpls traffic-eng priority 5 5 R1#sh mpls ldp bindings We can still see the label bundles passed by R3 before in the LIB table of R1 : Insert ( impose or push ) IGP metric: 1 *Aug 18 09:06:07.919: 10.1.45.4 (Strict IPv4 Prefix, 8 bytes, /32) Remarks Verify that you receive the LDP Hello from the other party. ! 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,ccna router simulator, the tag stack is followed by the IP header, and the first field of the IP packet is version , if Path option 10, type dynamic (Basis for Setup, path weight 20) In this way , when the IP packet is tagged on the border device, the TTL value in the original IP header is not copied , but a 255 value is used instead. Two processes: neighbor discovery process, session establishment process At this point for R2 , he has two paths to 5.5.5.5 and 55.55.55.55 . For the device number, this IP is also the LDP routerID . 1921.6800.1024. *Aug 18 11:31:44.598: R1#show isis neighbors Path setting option path-option The term link is a path between two ISs (routers). When two adjacent SNPAs can communicate, the link is in the UP state. (Link Data) Router Interface address: 0.0.0.13 Number of MTID metrics: 0 --------------- Record Route: NONE Brief introduction to the work process Metric Type: TE (default) InLabel : - R1#show mpls forwarding-table Frame-relay map ip 10.1.123.2 301 broadcast Virtual link NET 0/0/0 For certification Record Route: NONE The IETF 's draft-ietf-isis-ipv6-05.txt specifies what IS-IS adds to support IPv6 . It is mainly a newly added two TLVs ( Type-Length-Values ) supporting IPv6 routing information and a new NLPID ( Network Layer Protocol Identifier ). IS-IS is not like RIP and OSPF . These two protocols have separate versions of RIPng and OSPFv3 support IPv6 . 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 . To form an adjacency relationship. Rational use of network resources Outgoing tag or VC 55.55.55.55 [110/31] via 10.1.23.3, 00:03:44, Ethernet0/1 O 75000 The Level1 area is a collection of L1 routers and L1/L2routers , and Level2area is a collection of L2 routers and L1/L2 routers . 0 kbits/sec 2.2.2.2/32 Unlike OSPF , DIS is preemptible and there is no backup DIS . When a DIS hangs, it is directly elected. After the basic configuration is completed, since R2 and R3 are L1\L2 routers , for both of them, they will advertise themselves to the local level1 area as a way to go out , by setting ATT in the LSP generated by themselves . we R1 point of view isis database has been able to see out. R1#show isis database Therefore, R1 will only use R4 's label mapping for 3.3.3.3 , that is, use label 404 to send the label packet to 3.3.3.3 . *Aug 18 04:37:06.243: version = 0 length in words = 7 Type block This is 1B , which contains a number of important bits: The LFIB table does not contain inbound interface information. Configuration example 2 : UP No output feature configured *Aug 18 09:06:07.919: 5 Interface level command, modify the MPLS mtu of the interface , it should be noted that mpls mtu can not be larger than the interface mtu 2.2.2.2/32 This inbound label packet, with a label value of 203 , indicates in the LFIB table of R2 that 203 needs to be exchanged to 300 and then dropped to the next hop. Fa0/0 *Aug 18 09:06:07.919: SENDER_TSPEC type 2 length 36: 1921.6800.1024. Ip cef ! When forwarding, if the destination address is present in the area within, the direct use of L1 LSDB routes generated forward packets, if the destination address is not in the region, the use of this area nearest L1 / L2router as an outlet outside the area network, whereby May cause sub-optimal routing Network 10.1.12.2 0.0.0.0 area 0 The router address TLV carries the router TE router ID for the TE . Router(config-if)#tunnel destination ip-addr ! Average rate=250000 bytes/sec, burst depth=1000 bytes Traditional TE solutions have the following examples: Peer-to-peer network *Aug 18 09:06:07.919: Tun Dest: 5.5.5.5 Tun ID: 0 Ext Tun ID: 1.1.1.1 MPLS TE information distribution Bytes Label Switched Mpls ip interface fast1/0 Local binding: tag: 102 Router ospf 1 IS-IS supports two levels of routing: Level1 and Level2 . Level1 supports routing within the region, Level2 support routing between areas. The Level 2 LSP encapsulates the Level 2 network topology information obtained from the routers connected to the backbone network . The complete Level 2 network topology can be obtained by using the SPF algorithm in the Level 2 link state database . Interface tunnel0 The composition of the router , Backbone must be continuous. 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. Set-overload-bit on-startup wait-for-bgp IGP Area[1] ID:: ospf area 0 System Information:: Mpls traffic-eng tunnels Tunnel mpls traffic-eng path-option 10 dynamic Static Routing Static Route 10.1.12.2 Interface Ethernet0/0 Interface Tunnel0 The boundary of the area is on the link If there is no PSN pseudo node, the situation is like the above picture. The LSPDB of all routers on the LAN is as shown in the figure. The red dotted line in the figure is the adjacency. We see that there are many adjacencies and the LSPDB is huge. So, is there a PSN pseudo node? Look at the picture below: OSPF adjacency does not DOWN , then R1 routing table, about 3.3.3.3/32 still choose R2 as the next hop, this is a problem. In the LFIB on R1 , the entry for 3.3.3.3/32 might look like this: Password: not required, none, in use 0x2F89 Router(config-if)#mpls traffic-eng flooding thresholds up/down ? 75000 Local tag The area address groups configured on the router are listed. It only appears in non-pseudo nodes 75000 ...... ...... After the above configuration is completed, there is one more unidirectional direct link to R5 on R2 . This link will directly participate in the routing calculation of R2 itself. The overall result is that there are now three straight connectors on R2 : eth0/0 , eth0/1 , tunnel0 . 3.3.3.3 Protction the Node (Node Protection) 105 Priority 7 : 9375000 Interface Serial0/0 When there is a problem with the path of R1-R2-R5 , for example , the link between R2-R5 is DOWN , then the TE tunnel will switch to the path-option of the next priority , that is, the dynamic setting mode. Therefore, it will switch to R1-R3-R4-R5 . Access-list 100 deny udp any any eq 646 access-list 100 permit ip any any Set-attached-bit route-map test ! The configuration of R1 is as follows ( R2 does not open area password temporarily ): In-label Out intf/label Keeping priority indicates how much weight a tunnel has, so that it can be preserved in the link; Metric Type: TE (default) The flooding of LSPs means that when a router reports its own LSPs to neighboring routers , the neighboring routers transmit the same LSPs to its neighboring routers, and then LSPs are transmitted to the entire hierarchy. One way inside. Through this "flooding", each router in the entire hierarchy can have the same LSP information and keep the LSDB synchronized. Each LSP has its own 4- byte serial number. The sequence number of the first LSP sent by the router is 1. When the new LSP needs to be generated , the sequence number of the new LSP is incremented by 1 on the previous LSP sequence number . A higher serial number means an updated LSP .