Вы находитесь на странице: 1из 2

DEVICES

TECHNOLOGY

SOLUTION

R1

OSPF Authentication

IP ospf authentication message-digest

BGP Neighbor

Change neighbor IP add from 209.56.200.226 -> 209.65.200.226

NAT ACL

Permit 10.2.0.0 in the nat-pool access-list

IP Access-List

Permit 209.65.200.224 0.0.0.3 to ACL 30 / edge-security

R2

IPv6 OSPFv3

On serial interface to R3, enter the command ipv6 ospf 6 area 0

R4

EIGRP AS 10

Change EIGRP AS number from 1 to 10

Route Redistribution

Change route-map name under EIGRP process from EIGRP-to-OSPF to EIGRP->OSPF

IPv4 EIGRP Routing

Remove passive interface default under EIGRP 10 (or remove ints fa0/0-1 )

IP DHCP

Delete ip dhcp-excluded 10.2.1.1-10.2.1.253 & apply ip dhcp-excluded 10.2.1.1-10.2.1.2

DSW1

HSRP

Remove track 1 and replace it with Standby 10 track 10 decrement 60

VLAN Filter

Remove vlan filter test1 vlan-list 10

IP Helper

Make sure the correct ip helper address is; ip helper-address 10.1.4.5

ASW1

Port-security

Delete switchport port-security mac-address 0000.0000.0001 command followed by

 

shutdown and then no shutdown commands under fa1/0/1 ( fa1/0/2 )

 

Access VLAN

Enter Switchport access vlan 10 under interface range fa1/0/1-2

Switch-to-switch

Enter command switchport trunk allowed vlan 10,200 on ints portchannel 13 & 23

Firstly, I started by checking the clients IP addresses using IPCONFIG command on clients.

Secondly, If the ip address 10*** then I will ping R1's ip address (10.1.1.1) to know the type of ticket am working on.

If the ping is successful, I will know its either BGP, NAT ACL, IP Access-list or HSRP ( In HSRP CLT1 can ping all devices including the web server

If the ping is not successful, then its probably OSPF Authentication, EIGRP AS 10, Route Redistribution, Passive Interface, or VLAN Filter

Thirdly, If the clients's ip address is 169***, Its obvious it is either DHCP, IP Helper, Port-security, Switchport Access vlan, or Switch-to-Switch.

Lastly, HSRP and IPv6 OSPFv3 are clearly stated.

CLT1's IP

COMMANDS USED IN TTs

HOW TO DETECT TROUBLE TICKETS

10***

show ip ospf nei / show run

Clt1 can ping 10.1.1.2, but not 10.1.1.1

10***

show ip bgp sum / show run

Clt1 can ping 209.65.200.226

10***

show ip bgp sum / show run

Clt 1&2 are unable to ping webserver

10***

show ip bgp sum / show run

Except R1 no one else can ping webs

ipv6 add

show ipv6 ospf nei / show run

R2 is not an OSPFv3 neighbor on R3

10***

show ip protocol / show run

Clt1 can ping 10.1.4.5 but not 10.1.1.10

10***

show run

Clt1 can ping 10.1.4.5 but not 10.1.1.10

10***

show ip protocol / show run

Clt1 can't ping 10.1.4.5

169***

show run

Use show run to check the dhcp add

10***

show run

Clt1 can ping thru to 209.65.200.241

10***

show run

Clt1 is unable to ping DG or ftpserver

169***

show run

The ip helper-address is changed

169***

show int fa1/0/1 ( fa1/0/2 )

Clt1 is unable to ping Clt2 and DSW1

169***

show run

Clients can ping each other only

169***

show int trunk / show run

Clients can ping each other but unable

)

to ping DSW1 or FTP Server.