CCT Routing & Switching: From Legacy RSTECH to Field Technician

CCT Routing & Switching is now a legacy Cisco certification name. The former 100-490 RSTECH exam had its last test date on February 9, 2025, and Cisco consolidated the older CCT Data Center and other CCT device-support tracks into the current 800-150 FLDTEC exam for Cisco Certified Field Technician. Candidates preparing in 2026 should use FLDTEC objectives rather than an old RSTECH blueprint.

Within the broader Cisco certification portfolio, the historical certification still describes an important job function: onsite support of routers, switches, cabling, interfaces, software, and basic device configuration. What changed is the credential structure, not the need for technicians who can work safely on production equipment and provide useful evidence to remote engineering teams.

RSTECH was designed around onsite device support

The old CCT Routing & Switching path focused on identifying Cisco routers and switches, understanding interfaces and accessories, using the Cisco IOS command line, handling common cabling, and performing basic maintenance under defined procedures. It was aimed at field engineers rather than network architects.

This distinction matters because support work has a different responsibility boundary from network engineering. A field technician may replace a module, recover connectivity, collect diagnostics, or restore a configuration without being responsible for redesigning the routing domain. Good technicians know where their authority ends and when escalation is the correct technical action.

Legacy study material remains useful for hardware recognition, console access, interface basics, and support workflow, but it should no longer be treated as a complete certification plan.

FLDTEC is the current unified successor

Cisco’s 800-150 FLDTEC exam now covers onsite replacement across routing, switching, data-center, UCS, and collaboration platforms. It includes hardware identification, cabling, configuration backup and restoration, and software upgrade or downgrade procedures. That unified scope better reflects how many field-service organizations operate.

A technician may arrive for what appears to be a switch replacement and discover that the maintenance also touches an uplink optic, a redundant power path, a data-center patch panel, or a connected collaboration system. The common skill is disciplined support across the physical and device-maintenance layers.

Candidates moving from RSTECH to FLDTEC should therefore retain routing-and-switching fundamentals but add the broader platform knowledge required by the current exam.

Physical interfaces and cabling are the first troubleshooting layer

Many network incidents begin with simple physical causes: a disconnected patch lead, incorrect optic, damaged fiber, wrong port, failed power supply, or module that is not seated correctly. Technicians should recognize common copper and fiber media, connector types, transceivers, console interfaces, and indicator states.

The physical check should be precise rather than casual. Verify device identity, interface labels, cable endpoints, link lights, power state, and any alarms before changing configuration. In a densely cabled environment, removing the wrong connection can create a new incident while trying to solve the original one.

Documentation and labeling are therefore operational tools. A technician who records the exact interface, optic, serial number, and cable path gives the remote engineering team evidence that can be correlated with network telemetry and configuration.

Basic switching knowledge helps technicians localize faults

Field technicians should understand what switches do with Ethernet frames, how access ports and trunks differ, why VLANs create logical separation, and how interface state affects local connectivity. Switching fundamentals provide enough context to interpret common symptoms without turning the role into a professional switching course.

If a replacement switch powers on but endpoints remain unreachable, the technician should be able to verify physical links, interface state, expected VLAN configuration, and uplink connectivity before escalating. The goal is not to redesign spanning tree but to determine whether the observed state matches the change plan.

Layer 2 knowledge also prevents dangerous improvisation. An apparently unused cable or port may participate in a redundant topology. Understanding that redundancy exists encourages verification before removal.

Routing fundamentals explain why local success can hide upstream failure

Technicians should recognize IP addressing, subnet masks, default gateways, routing-table basics, and the difference between local and remote reachability. A device can communicate inside its local subnet while still failing every remote connection because a gateway, uplink, route, or upstream interface is unavailable.

Practical subnetting helps technicians decide whether two addresses should communicate directly or through a router. That simple determination is often enough to separate a host configuration issue from an upstream network issue.

The technician does not need to manipulate complex routing policy during field work. The more important skill is reading enough state to describe the fault accurately and avoid making changes outside the assigned procedure.

CLI access should support verification, not uncontrolled configuration

RSTECH historically emphasized Cisco IOS modes and basic CLI use, and that skill remains relevant. Technicians may need to check interface state, capture version information, verify inventory, review logs, or confirm whether a configuration was restored after a replacement.

Command-line confidence should be paired with change discipline. Before entering configuration mode, confirm that the procedure authorizes the change. Capture existing state when required, record commands that alter behavior, and validate the expected result afterward.

In production environments, “I know the command” is not sufficient justification for using it. The field technician’s value comes from reliable execution under an approved plan.

Troubleshooting should be layered and evidence-driven

A structured network troubleshooting methodology is particularly valuable for field technicians because they are often the remote team’s eyes and hands. Begin with scope and physical state, then move into interface status, addressing, local reachability, upstream reachability, and required services.

Compare expected and observed state. If a replacement device does not come online, determine whether it has power, whether uplinks are physically active, whether configuration was restored, whether the management address is correct, and whether the remote team can see the device.

Photographs, timestamps, console output, serial numbers, LED states, and exact error messages can be more useful than a vague statement that “the network is still down.” High-quality evidence shortens escalation time.

The legacy path can still lead into modern networking roles

Technicians who enjoy routing and switching can progress into CCNA and later CCNP Enterprise. Those certifications move away from component replacement and into deeper configuration, troubleshooting, architecture, security, assurance, and automation.

An older routing and switching certification history can provide useful context, but candidates should not mistake historical naming for the current program. Cisco’s certification architecture has changed substantially, and current exam objectives must govern preparation.

The practical lesson is straightforward: CCT Routing & Switching remains a recognizable description of legacy field-support skills, but the active 2026 certification is Cisco Certified Field Technician through FLDTEC. Study the old material for context only where it supports the current unified role.

Software and configuration recovery deserve the same care as physical replacement. Before swapping a device, technicians should know whether configuration will be restored automatically, loaded from a backup, or applied by a remote engineer. They should verify the backup date and target identity so an old or incorrect configuration is not introduced during recovery.

Console access is often the difference between a recoverable device and a blind escalation. Practice connecting through approved console methods, recognizing boot output, identifying whether a device has completed startup, and capturing error messages without making unauthorized changes. Boot loops, missing images, storage errors, and configuration-register problems can look like ordinary network failure from a remote monitoring system.

Field technicians should also understand redundancy at a basic level. A device may have dual power supplies, redundant uplinks, stacked members, or paired supervisors. Removing one component can be safe only if the redundant path is healthy. Verification must happen before the component is touched, not after an unexpected outage.

Environmental checks can matter as well. Heat, blocked airflow, power events, contamination, or repeated physical stress can cause intermittent faults that disappear during a short test. Record environmental alarms and recurring patterns instead of assuming every hardware replacement permanently solved the problem.

Finally, closeout validation should be broader than a green link light. Confirm expected interface state, management reachability, upstream visibility, restored configuration, normal alarms, and any service checks defined in the change plan. A technician should be able to tell the remote team exactly what passed and what still requires engineering attention.

Pre-change capture is especially useful on routing and switching devices. Record interface status, neighbor relationships, software version, inventory, relevant configuration, and active alarms before replacement when the failure state allows it. Those records help prove which conditions existed before the technician touched the system.

After replacement, compare the same evidence. A device that boots and answers on the management address may still be missing an uplink, routing neighbor, VLAN, port-channel member, or expected software image. Side-by-side validation is more reliable than relying on a single “device up” status.

Technicians should also recognize the difference between hardware symptoms and control-plane symptoms. Repeated link flaps can originate in cabling, optics, port hardware, negotiation, or the remote endpoint. Missing reachability can originate in routing or policy even when every light is green. The role is not to solve every advanced control-plane problem, but to avoid replacing hardware without evidence that hardware is actually implicated.

Remote engineers may ask for packet captures, show-command output, loopback tests, or a cable move to isolate the fault. The field technician should understand what each requested test changes and should report the result exactly. If an instruction conflicts with the approved change window or site procedure, the discrepancy should be escalated rather than silently worked around.

A useful lab exercise is to document a small switch or router replacement as if another technician had to execute it. Include cable labels, console access, configuration backup, software state, validation commands, rollback, and escalation criteria. Writing the procedure exposes assumptions that are easy to miss when simply following one.