I was not able to get a seat for my 2nd attempt in all over ASIA (Sydney, Tokyo, Hong Kong) due to no more space available up to October 18, 2009 (Version 3.0). So I decided to go over the version 4.0 CCIE R&S by December 3, 2009 in Hong Kong.
I purchased the INE’s Volume 4.0 workbook. Below are my log on each lab tickets. Sharing to you my thoughts.
Internetwork Expert’s R&S Lab Workbook Volume IV Logs – Lab 1
Ticket 1: VOIP Quality issue
-Think of a QOS policy configuration on the LLQ!
-Check for asymetric routing issue. Do traceroute.
-Do show frame-relay pvc xxx, check for CIR, BC, Fragment size.
-Verify applied service policy and map-class frame-relay if any.
-Check for the queueing strategy on the interface. LLQ is “Conversation 40″, minimum bandwidth reservation is “Conversation 41″ on the show policy-map interface command.
-Ping test with higher MTU size to check for fragmentation if working.
Ticket 2: OSPF load balancing.
-It is critical that the adjancency database to be sync, check individual database of the advertising router (show ip ospf data router adv <rid>)
-OSPF does not install routes on the routing table with different DB entries and interface types.
-Watch OSPF adjacencies can still be form even on a different network types, as long as timers are match. Here p2p and broadcast types can form adjacendy.
-Check basic connectivity.
-show ip route
-Check OSPF topology table on the LSA type.
-show ip ospf database router self-originate/advertising-router xxxx.
-debug ip bgp
Ticket 3: BGP Peering.
-BGP TTL Security HOPs. Nice TTL security feature for BGP. Sets outgoing TTL to 255 and the Incoming TTL equals to 255-x, where x is the TTL hops on the command “neighbor <iP> ttl-security hops x”.
-Without TTL security hops feature, OUT TTL is 1 by default and Incoming is 0. So it means ebgp sessions can be established from anywhere on the network.
-Check basic connectivity.
-Check for any filtering issue on tcp port 179.
-Debug ip packet detail ACL, ACL matches TCP source and destinations ports.
Ticket 4: Connectivity Issue
-Watch out for inconsistent RB for a vlan. Check spann tree guard root command. Check L2 diagram for the any spanning tree diagram (root down, down to up).
-Do basic ping test.
-Check for VACL’s applied on the switch.
-Verify CDP neighbors.
-Check interface ACL’s applied.
-show spanning tree vlan and verify proper tree distribution or path from the ROOT down.
Ticket 5. Old Backup
-check for frame relay mapping issue
-Check for EIGRP router-id should be unique throughout the entire EIGRP domain.
-RIP – Check out send and receive versions.
-Check for IN and OUT filters within the protocol by issuing the command show ip protocols.
-Can use temporary* static route to test connectivity issue.
-Basic ping test, -Verify CDP neighbors.
-Prefix not installed on the routing table – 1. check AD, 2. Distribute-list Filtering. 3. Same Router ID Filtering External Routes.
Ticket 6. BGP prefix
-check out for cluster id issue. If your router-id is taken by other IBGP neighbor, you can establish neighborship but does not exchange bgp routes. (this case the RR has same RID with the client. So the client does not receive any bgp routes from the RR due to CLUSTER-LIST loop.
-To fix this, issue a unique bgp cluster-id on the router bgp process.
-clear bgp neighborship using soft-in
-debug ip bgp xxxx updates
Ticket 7. DHCP
-Use debugging technique for DHCP to gather information.
-Use logging buffer.
-debug ip dhcp server packets
-debug ip dhcp server events
-show ip dhcp.
-check doc cd
-use all options ? command technique.
Ticket 8. Port Security Violation
-By default port security violation allows only 1 MAC address.
-If you use FHRP with port security be sure to allow at least 2 MAC address on the switch port.
-Else use standby use-bia on the Router port for it not to use any other MAC address.
-Be sure to shut/no shut switch port to re-enable interface with error-disable state.
-Show port-security interface f0/1
-logging console debugging.
Ticket 9. IPV6
-RIPng uses the link local address as next hop interface.
-Make sure to map the link local address on the frame map statement.
-Check IPV6 routing table
-Ping test.
Ticket 10. Multicast
-ping testing usually is automatically source on the loopback interface (sparse-dense), so make sure the loopback interface has ip pim mode on it.
-mtrace back from last hop router to the source.
-check for RP configs
-use process switch for troubleshooting and debug ip mpacket
-check for any RFP issue, use static mroute if needed only.
-mtrace from destination back to source.
-check rpf failure for the RP and source separately!
-check mroute table.
-show ip igmp groups
-show ip igmp rp mappings




