Search This Blog

mynetworkjourney

ccnp exams

Get link
Facebook
X
Pinterest
Email
Other Apps

- January 24, 2011

Hi friends these are the valid Dumps for ccnp route exams

Route-642-902
http://www.examcollection.com/cisco/Cisco.PassGuide.642-902.v2010-10-7.by.DoDo.255q.vce.file.html

http://www.examcollection.com/cisco/Cisco.PassGuide.642-902.v2010-11-27.by.gogy.272q.vce.file.html

Switch-642-813

http://www.examcollection.com/cisco/Cisco.CertifyMe.642-813.v2011-01-13.by.Petter.500q.vce.file.html

http://www.examcollection.com/cisco/Cisco.TestKing.642-813.v2010-09-20.by.fliper.496q.vce.file.html

Get link
Facebook
X
Pinterest
Email
Other Apps

Comments

Adding ACLS for allowing access from Client-A LAN to Client-B Lan

- July 22, 2020

Disabling Unneeded Services

- February 20, 2012

Step 1: Configure the Physical Interface Because this lab uses only one router, you will simulate an active FastEthernet connection by activating the interface and applying the no keepalive command to initiate an “always up” state, regardless of the existence of a device at the remote end. Normally, you would not use the no keepalive command on a routed interface, except in special circumstances. In this lab, you will use it only for simulation purposes. Configure the R1 physical interface using the IP address shown in the topology diagram. Use the no keepalive command in interface configuration mode, and then use the no shutdown command to activate the interface. Because you have disabled keepalives, the interface status displays as link state (Layer 1) and line protocols state (Layer 2) “up,” even if it is not connected to an external device. R1(config)# interface fastethernet0/0 R1(config-if)# ip address 192.168.10.1 255.255.255.0 R1(config-if)# no keepalive R1(config-if)# no s...

EBGP Multihop

- February 15, 2011

Configuring iBGP doesn't require the neighbor address to be directly connected. The best practice for iBGP is to use the loopback address as the ip address configured on the BGP neighbor statement. Loopback interfaces never go down so provided that there is an alternate route to the loopback ip address through an IGP, BGP session will not be torn down. Using loopback addresses for eBGP is also a good practice if there are multiple links between two routers on different autonomous system as shown on the example diagram below. This will also achieve load balancing. The initial configuration for this lab is shown below. R1# ! interface Serial1/0 ip address 10.10.10.1 255.255.255.0 serial restart-delay 0 end ! interface Serial1/1 ip address 10.10.20.1 255.255.255.0 serial restart-delay 0 end ! interface Loopback0 ip address 1.1.1.1 255.255.255.255 ! router bgp 1 no synchronization bgp log-neighbor-changes neighbor 2.2.2.2 remote-as 2 no auto-summary ! ip route 2.2.2.2 255.255.2...