Exact Cisco 300-135 Rapidshare

None

Cisco routers, switches, PIX and ASA firewalls prioritize log messages into 8 levels (0-7), as shown below: LevelLevel NameDescription
0 Emergencies System is unusable 1 Alerts Immediate action needed 2 Critical Critical conditions
3 Errors Error conditions
4 Warnings Warning conditions
5 Notifications Informational messages
6 Informational Normal but significant conditions 7 Debugging Debugging messages
When you enable logging for a specific level, all logs of that severity and greater (numerically less) will be logged. In this case we can see that logging level of 3 (as seen by the 3 in “LINK-3-UPDOWN”) and level 5 (as seen by the 5 in “LINEPROTO-5-UPDOWN”) are shown, which means that logging level 5 must have been configured. As shown by the table, logging level 5 is Notifications.

None

On DSW1, related to HSRP, under VLAN 10 change the given track 1 command to instead use the track 10 command.

Port security is causing the connectivity issues. On ASW1, we need to remove port-security under interface fa1/0/1 & fa1/0/2.

None

The problem here is that VLAN 10 is not configured on the proper interfaces on switch ASW1.

Based on the network diagram, we know that a virtual link will need to be configured to logically connect area 2 to the back area 0. However, this is not the problem as we can see that R3 has been correctly configured to do this. It is, however, missing the network statement for the link to R4.
Here, we see that the link to R4 is using the 192.168.34.0 network, but that this network has not been added to OSPF


Based on the network diagram, this link should be added to Area 1, not Area 2.

First three octets are 01-00-05e for every single multicast address.Las three octets are the hexadecimal version of the las three octets of the IP address, in this case 193.5.10 is translated to c1-05-0a.
Reference:

Start to troubleshoot this by pinging the loopback IPv6 address of DSW2 (2026::102:1). This can be pinged from DSW1, R4, and R3, which leads us to believe that the issue is with R2. Going further, we can see that R2 only has an IPV6 OSPF neighbor of R1, not R3:
Screen Shot 2015-03-11 at 10

We can then see that OSPFv3 has not been enabled on the interface to R3: Screen Shot 2015-03-11 at 10

So the problem is with R2, related to IPV6 Routing, and the fix is to enable the “ipv6 ospf 6 area 0”command under the serial 0/0/0.23 interface.

None

On DSW1, VALN ACL, Need to delete the VLAN access-map test1 whose action is to drop access-list 10; specifically 10.2.1.3

None

None

None

The EIGRP AS number configured on R4 is wrong.

As explained earlier, the problem is with route redistribution on R4 of not redistributing RIP routes into OSPF for IPV6.

None

None

None