ccna routing and switching latest dumps
-
- 5607 Reviews
The above network is a typical Hub&Spoke network. Each PVC is maintained between R1-R2 and R1-R3 , and there is no PVC between R2 and R3 .
LDP discovery sources:
301
Outgoing interface
L2 rouer redistributes external routes into IS-IS
The configuration of R4 is modified as follows:
*Aug 18 11:31:44.598:
Partition repair
Interface Serial1/0
*Aug 18 09:06:07.919:
Route summarization on the L1/L2 router ( to level1 )
10.1.12.2
Token bucket fragment (service_id=1, length=6 words parameter id=127, flags=0, parameter length=5
Ip cef
RESV response PATH message, to establish and maintain LSP passage
1 10.1.12.2 12 msec 4 msec 4 msec
Routing information diffusion in point-to-point links
Discovery Sources:
Network 2.2.2.2 0.0.0.0 area 0
Allocated i/f max flow max sub max
Interface eth 0/2
Interface Tunnel0
Isis password
Selecting designated routers in the broadcast network to control the spread and reduce the system resource requirements of many-to-many neighbors in such media
10.1.12.2
Multicast packets belonging to a specific multicast group
DN
MPLS TE tunnel
Interface loopback0
After the configuration is complete, the level 2 LSP sent by R2 will carry the cipher text authentication TLV information (the level 1 LSP is not carried). If this configuration is maintained, we will find that R2 can only learn the R1 release. Routing, this is because level1 LSPs are not authenticated. After completing this experiment, R3 and R4 complete the configuration.
10.1.12.2 8 msec 4 msec 0 msec
Next Hop
MOSPF extension provides support for IP multicast routing
The LSR does not need to re-establish an LDP session, and the efficiency of convergence is improved.
Interface Loopback0
102
Pop tag
Router ospf 1
Network 10.1.34.3 0.0.0.0 area 0
Name: R2-PE1_t0 Status:
302
Tunnel mpls traffic-eng priority 6 6
Setting the priority and maintaining the priority all indicate whether a TE tunnel can preempt another TE tunnel by using the corresponding value . The lower the priority, the higher the importance.
It can be seen that we allocated 33M bandwidth for the tunnel with priority 6. The total reserved bandwidth of the original interface is 75M , and it is divided into 33M , so there is 42M . We can also see because we have modified the priority. The reservable bandwidth of the tunnel of level 6 is therefore lower, and the reserved bandwidth is also changed.
The status here is active . When the primary link does not expire, status is displayed as ready
*Aug 18 11:31:44.598: Controlled Load Service break bit=0 service length=0
The password is inserted in Level2 LSP , CSNP ,ccna routing and switching latest dumps, and PSNP . The command is as follows (in the routing process):
Look at the routing table for R1 :
10.1.12.2
Static hostname mapping
!
OAM is basically used for error detection, location, and monitoring implementation. This tag distinguishes between ordinary messages and OAM messages. CISCO IOS does not use tag 14 , which performs MPLS OAM but is not implemented by tag 14 .
Interface eth0/0
Address-family vpnv4 neighbor 5.5.5.5 activate
Note ESH and ISH PDU are ES-IS of the PDU instead of IS-IS of the PDU
Or Tunnel Id
1/0/0
10.1.34. 4 4.4.4.4
i L2 2.2.2.0 [115/20] via 10.1.24.2, Serial0/0
For certification
Route summary
Use the above command to view the TE metric.
!
The configuration of R5 is as follows:
Interface Tunnel0
MPLS TE using type 10 of LSA to a region within MPLS TE work.
RFC 2966
Route-map test permit 10 router isis
Bw[7]:
Router-id 2.2.2.2
3.3.3.3
Remarks
In the explicit setup mode, we must specify the router that the TE tunnel needs to traverse. You can specify the TE of the router in the link.
Interface Tunnel0
LSP Seq Num
Certification Information
Network 10.1.45.5 0.0.0.0 area 0
Generate a default route to this device as the egress route by ATT bit with its nearest L1/L2 router
!! The type of IS is level1
Interface
Router ospf 1
TE tunnel reoptimize
10.1.23.2
Next-address 10.1.24.4
Peer LDP Ident: 4.4.4.4:0; Local LDP Ident 2.2.2.2:0 TCP connection: 4.4.4.4.24940 - 2.2.2.2.646
*Aug 18 09:06:02.699: 10.1.12.2 (Strict IPv4 Prefix, 8 bytes, /32)
R3.01-00
10.1.45.0/24 [110/30] via 10.1.23.3, 00:00:01, Ethernet0/1
Router ospf 1 vrf VPN-A redistribute bgp 2345 subnets network 10.1.12.2 0.0.0.0 area 0
10.1.45.5*
Link connected to: a Transit Network
Interface fas0/0
BW (kbps)
The configuration of R4 is as follows:
It can be seen that we allocated 33M bandwidth for the tunnel with priority 6. The total reserved bandwidth of the original interface is 75M , and it is divided into 33M , so there is 42M . We can also see because we have modified the priority. The reservable bandwidth of the tunnel of level 6 is therefore lower, and the reserved bandwidth is also changed.
!! activation Tunnel of forwarding-adjacency
2 10.1.34.3 [MPLS: Label 303 Exp 0] 856 msec 1012 msec 1072 msec
* 0x0000002B
Summary of tag processing actions
Show isis database on R1
Pop Label
Pop tag
The configuration of R3 is as follows:
NSAP
Activate the MPLS TE extension for each router's OSPF and manually set the RouterID for MPLS TE .
Configure MPLS TE tunnel on R1 .
!! OSPF cost of the interface
R3.00-00
Mpls ldp router-id loopback0
10.1.34.0/24
State: Oper; Msgs sent/rcvd: 9/9; Downstream
0x2F89
Current LSP:
PDU
All routers in the area (except the border router) can only establish neighbor relationships with routers in the area.
OSPF is encapsulated in an IP packet with the protocol number of 89.
!
Router(config-if)# mpls traffic-eng path-option x {dynamic | explicit name y } [ lockdown ]
*Aug 18 09:06:07.919: version=0, length in words=7
In order for the protection feature to work properly, you need to enable this feature on both LSRs . If one end does not support this feature, you can configure the feature in one segment and the mpls ldp discovery targeted-hello accept command on the other end to receive target-hello .
Next-address 10.1.23.3
i L1
AutoRoute: disabled LockDown: disabled Loadshare: 0 bw-based auto-bw: disabled
Interface eth0/0
Next Hop
*Aug 18 11:26:02.546:
101
The local device will actively advertise the generated label mapping message to all LDP neighbors.
The sub-TLV of 0-244B is mainly used for MPLS TE.
*Aug 18 09:06:07.919: ADSPEC type 2 length 48:
Set-overload-bit on-startup <5-86400 sencondes>
Type escape sequence to abort. Tracing the route to 4.4.4.4
It is only possible to establish adjacencies with neighboring routers at the same level.
Tunnel mpls traffic-eng autoroute metric relative parsing if the configuration of R2 changes as follows:
The configuration of R4 is as follows:
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.
Interface eth0/0
LDP and IGP synchronization
Total Allocated
To meet the above requirements, IS-IS is designed as a link state routing protocol and uses the SPF shortest path first algorithm to achieve fast convergence and loop-free networks.
42000
Maximum bandwidth : 12500000
Interface Ethernet0/1
System Id Type Interface IP Address State Holdtime Circuit Id
Reserved bandwidth changes (significant changes)
!
LSP link state data unit
SystemID Length : Identifies the length of the system ID . A value of 0 indicates a length of 6B , a value of 255 indicates a length of 0 , and other system ID fields may have a length of 1-8 bytes.
Type-10 Opaque Link Area Link States (Area 0)
The TCP/IP protocol stack, similar to ES-IS , is done by ARP , ICMP , and DHCP protocols in the TCP/IP stack .
*Aug 18 04:37:06.239: SESSION type 7 length 16:
The above commands can also be configured in the tunnel port.
!
Interface loopback0
OutLabel : Ethernet0/1, 304
Et0/1
The IS-IS related interface is Up or Down .
Activate RSVP on the interface and configure reserved bandwidth (optional)
ISO10589
R1#
Different LANs on the DIS .
Then we wait for the BGP neighbor relationship on R2 to be established. You can debug it:
2.2.2.2/32, Flags: 0x21 (Local Prot Avail/to NHOP, Node-id)
201
R1#show mpls traffic-eng tunnels
!
Mpls traffic-eng area 1
Aggregation: The label stack is removed and an IP lookup is performed on the IP packet.
Set-overload-bit suppress interlevel redistribute connected level-1
!
Use the lockdown keyword (note that the above configuration is configured in the TE tunnel port).
Then, R4 goes to 5.5.5.5 and the next hop is 10.1.12.1 . When 6.6.6.6 accesses 5.5.5.5 , the IP packet arrives at R4 . R4 checks the CEF and labels the IP packet. The key is On this label, R4 will use the label of 10.1.12.0 for this route ( 12.0 is the next hop to 5.5.5.5 ), and this label is assigned by R3 (the label I give to the export data is always the LDP neighbor. s Mark).