A reliable network is checked methodically, not at random. Adopting a verification routine after every configuration prevents nasty surprises and speeds up troubleshooting.

An effective routine

• Document the addressing plan before you configure anything.
• Check the state of the interfaces with show ip interface brief.
• Review the known routes and the IPv6 addressing.
• Test local connectivity first, then remote, using ping.
• Save the configuration once it is validated.

R1# show ip interface brief
R1# show ipv6 interface brief
R1# show ip route
R1# copy running-config startup-config

By checking from the nearest point (the interface, the gateway) out to the farthest (the remote network), you isolate any anomaly quickly. The final save guarantees that the validated configuration survives a reboot. This kind of discipline is what makes a network technician dependable.

Key point: document, check interface by interface, test from local to remote, then save. See Lab 15 – Full verification of a network.