Troubleshoot Workbook: April and May - 2014
Troubleshoot Workbook: April and May - 2014
Troubleshoot Workbook: April and May - 2014
Workbook
April and May -2014
Note: just only for Training and same as TS5 New Reported. And don’t for
dumper.
TS5 New
Troubleshooting Guidelines
This section is comprised of a set of troubleshooting scenarios.
The final score of this section is combined with the Configuration sections to comprise your final Pass or Fail status
on the given lab exam.
You will be presented with preconfigured routers and Frame-Relay switches in the topology. DO NOT change the
following configuration on the devices.
Hostname
Enable password "cisco"
Console line configuration
For all of the authentication configuration in the lab, password is "cisco" unless changed to introduce a
break. Do NOT change AAA configuration unless explicitly stated in a question.
Points are awarded for finding AND fixing inserted faults in the presented fully configured topology.
An inserted fault is an introduced break for a scenario that was previously working. Depending on the
scenario, fixing the inserted faults could require multiple command lines on the same or multiple devices.
The resolution of one incident may depend on the resolution of previous incident(s) . The
dependency will not be visible if the tickets are resolved in sequence.
There are NO physical faults introduced in the presented topology.
Do NOT change any routing protocol boundaries. Refer to the provided diagram.
DO NOT REMOVE ANY FEATURE CONFIGURED IN ORDER TO RESOLVE AN INCIDENT, YOU MUST
RESOLVE MISCONFIGURATION RATHER THAN REMOVING IT ALL (examples: Access-lists, PBR,
CoPP, MQC, etc.)
Static and default routes are NOT permitted unless preconfigured. These restrictions include floating
static and those generated by routing protocols. Routes to Null0 that are generated of a dynamic routing
protocol solution are permitted.
Tunneling and policy-routing are NOT permitted unless preconfigured.
Dynamic Frame Relay mappings are NOT permitted.
Points will be deducted for every incident in which candidate uses a prohibited solution.
Candidates have control of all required devices in the topology.
If required to verify the reachability from a host machine during the lab exam, use the ping command with
source option on the router that is shown connected to the subjected host in the diagram.
Q1 SNMP
- From R14, when you use command : GetR17Hostname, you must have exactly output
same.
R14#GetR17Hostname
Topology :
Q2 PPP Multilink
- Telnet from R27 should reach 100.25.25.25 located on R25
Refer to the While you are resolving this issue, you are not allowed to create any new interfaces.
And remove access-list. You can only modify it.
- Client in ACME Branch Office (R34) must be succes ping Server (R31) in Headquater.
- Test solution by ping and tracert route from R33 and R34
Q8: BGP:
- From R17 must ping and tracer success to 5.2.2.2
- The output tracer from R17 to 5.2.2.2 shoul be 4 hops and same as ouput:
Topology:
Q9: MST:
- SW5 success ping server R31 with source is VLAN 5
- Tracer from SW5 to R31 with source VLAN5 must be same as output :
That’s all ! I’m big thank to Uncle Cao and Brother wit. Who help me and other have a good
question about TS5 NEW.
Good Luck
-----HN03-DLP------
--------------------------------------------The End--------------------------------------------