Free Cisco 642-832 Exam Dumps Questions & Answers

The implementations group has been using the test bed to do a `proof-of-concept'. After several changes to the network addressing, routing schemes, a trouble ticket has been opened indicating that the loopback address on R1 (2026::111:1) is not able to ping the loopback address on DSW2(2026::102:1).
Use the supported commands to isolated the cause of this fault and answer the following questions.
On which device is the fault condition located?

• A.  R2
• B.  DSW1
• C.  ASW1
• D.  R4
• E.  R3
• F.  DSW2
• G.  R1
• H.  ASW2

What is the result of configuring the logging console warning command?

• A.  Messages with a severity level of 4 and higher will be logged to all available TTY lines.
• B.  Warning, critical, alert, and emergency messages will be logged on the console.
• C.  The logging console warning command needs to be followed in the configuration with logging buffered byte size to specify the message buffer size for the console.
• D.  Only warning messages will be logged on the console.
• E.  Warning, error, critical, and informational messages will be logged on the console.

DRAG DROP Match the items on the left to their purpose on the right

Correct Answer:

Explanation:
EEM -> CLI based Management and Monitoring
SDM -> Provides a GUI for Administration
FTP -> Used for Backup and Restore
Cisco IOS Embedded Event Manager (EEM) is a powerful and flexible CLI based subsystem that provides
real-time network event detection and onboard automation. It gives you the ability to adapt the behavior of
your network devices to align with your business needs.
Cisco SDM is an intuitive, Web-based device-management tool for Cisco IOS@ Software-based routers.
The Cisco SDM simplifies router and security configuration through smart wizards, which help customers
and Cisco partners quickly and easily deploy, configure, and monitor a Cisco router without requiring
knowledge of the command-line interface (CLI). The Cisco SDM is supported on a wide range of Cisco
routers and Cisco IOS Software releases.
Cisco devices can use FTP to backup and restore configuration files and IOS software. Some examples of
this are shown below:
Example 1: Backing up manually
R1# copy startup-config ftp://kevin:[email protected] Address or name of remote host [ 192.168.22.33]?
Destination file name [r1-confg]?
Writing R1-confg !!!
3458 bytes copied in 3.443 secs (1243 bytes/sec)
Example 2: Backing up automatically
The configuration below will make a backup:
write-memory Trigger backup when running-config is copied to nvram time-period 1440 Trigger backup
every 1440 minuttes. 60*24=1440 !
ip ftp username kevin
ip ftp password dj7jS
!
archive
path ftp://192.168.2.33/R1-config
write-memory
time-period 1440Viewing
R1#show archive
The next archive file will be named ftp://192.168.2.33/R1-confg-4 Archive # Name
1 ftp://192.168.2.33/R1-confg-1
2 ftp://192.168.2.33/R1-confg-2
3 ftp://192.168.2.33/R1-confg-3 <- Most Recent

The implementations group has been using the test bed to do a `proof-of-concept' that requires both Client 1 and Client 2 to access the WEB Server at 209.65.200.241. After several changes to the network addressing, routing scheme, DHCP services, NTP services, layer 2 connectivity, FHRP services, and device security, a trouble ticket has been opened indicating that Client 1 cannot ping the 209.65.200.241 address.
Use the supported commands to isolated the cause of this fault and answer the following questions.
The fault condition is related to switch technology?

• A.  Switch Virtual Interface
• B.  VLAN ACL Port ACL
• C.  Loop Prevention
• D.  Access Vlans
• E.  Switch-to-Switch Connectivity
• F.  NTP
• G.  Port Security

Topic 10, Ticket 8 : Redistribution of EIGRP to OSPF
Topology Overview (Actual Troubleshooting lab design is for below network design)
Client Should have IP 10.2.1.3
EIGRP 100 is running between switch DSW1 & DSW2
OSPF (Process ID 1) is running between R1, R2, R3, R4
Network of OSPF is redistributed in EIGRP
BGP 65001 is configured on R1 with Webserver cloud AS 65002
HSRP is running between DSW1 & DSW2 Switches
The company has created the test bed shown in the layer 2 and layer 3 topology exhibits.
This network consists of four routers, two layer 3 switches and two layer 2 switches.
In the IPv4 layer 3 topology, R1, R2, R3, and R4 are running OSPF with an OSPF process number 1.
DSW1, DSW2 and R4 are running EIGRP with an AS of 10. Redistribution is enabled where necessary.
R1 is running a BGP AS with a number of 65001. This AS has an eBGP connection to AS 65002 in the
ISP's network. Because the company's address space is in the private range.
R1 is also providing NAT translations between the inside (10.1.0.0/16 & 10.2.0.0/16) networks and outside
(209.65.0.0/24) network.
ASW1 and ASW2 are layer 2 switches.
NTP is enabled on all devices with 209.65.200.226 serving as the master clock source.
The client workstations receive their IP address and default gateway via R4's DHCP server.
The default gateway address of 10.2.1.254 is the IP address of HSRP group 10 which is running on DSW1
and DSW2.
In the IPv6 layer 3 topology R1, R2, and R3 are running OSPFv3 with an OSPF process number 6.
DSW1, DSW2 and R4 are running RIPng process name RIP_ZONE.
The two IPv6 routing domains, OSPF 6 and RIPng are connected via GRE tunnel running over the
underlying IPv4 OSPF domain. Redistrution is enabled where necessary. Recently the implementation group has been using the test bed to do a `proof-of-concept' on several implementations. This involved changing the configuration on one or more of the devices. You will be
presented with a series of trouble tickets related to issues introduced during these configurations.
Note: Although trouble tickets have many similar fault indications, each ticket has its own issue and
solution.
Each ticket has 3 sub questions that need to be answered & topology remains same.
Question-1 Fault is found on which device,
Question-2 Fault condition is related to,
Question-3 What exact problem is seen & what needs to be done for solution


Client is unable to ping IP 209.65.200.241

Correct Answer:

Solution Steps need to follow as below:
When we check on client 1 & Client 2 desktop we are not receiving DHCP address from R4 ipconfig ----Client will be receiving IP address 10.2.1.3
IP 10.2.1.3 will be able to ping from R4 , but cannot ping from R3, R2, R1
This clearly shows problem at R4 since EIGRP is between DSW1, DSW2 & R4 and OSPF protocol is running between R4, R3, R2, R1 so routes from R4 are not propagated to R3, R2, R1
Since R4 is able to ping 10.2.1.3 it means that routes are received in EIGRP & same needs to be advertised in OSPF to ping from R3, R2, R1.
Need to check the routes are being advertised properly or not in OSPF & EIGRP vice-versa.
From above snap shot it clearly indicates that redistribution done in EIGRP is having problem & by default all routes are denied from ospf to EIGRP... so need to change route-map name.
Change required: On R4, in redistribution of EIGRP routing protocol, we need to change name of route-map to resolve the issue...


So in ticket Answer to the fault condition will be as below for