How to configure SSH access on Cisco Catalyst 9400

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

What this guide covers

Enable SSH v2 on the management VTY lines.

Resolve

enable
configure terminal
hostname SW-9400
ip domain-name corp.local
crypto key generate rsa modulus 2048
ip ssh version 2
ip ssh time-out 60
username netadmin privilege 15 secret 0 StrongPasswordExample
line vty 0 15
 transport input ssh
 login local
end
write memory

How to verify

show running-config
show vlan brief
show interface status

Common issues

| Issue | Fix |

|---|---|

| Command rejected | Check you're in the correct mode (# for privileged EXEC, (config)# for global config). |

| Configuration disappears after reload | Confirm write memory (or copy run start) was issued before reload. |

| Counters show drops | Check the related show command for the subsystem and inspect mismatched neighbour settings. |

Frequently asked questions

Will this configuration survive a reload?

Only after write memory (or copy running-config startup-config). On IOS-XE devices in install mode, the install commit is also required.

Is this safe to apply on a production network?

Test in a lab or a maintenance window first. Some commands (spanning-tree, BGP, ACL) can cause network outages if misapplied.

Where can I find the Cisco official documentation?

https://www.cisco.com/c/en/us/support/all-products.html, search the product family + the feature name.

Which IOS / IOS-XE version does this apply to?

The commands above were validated on IOS-XE 17.x family (Catalyst 9000) and IOS-XE 17.x (ISR/ASR/Catalyst 8000). Older trains (15.x for legacy IOS) may need slightly different syntax: check ? in the CLI.

Related guides

• All Cisco fix guides → /cisco/
• Cisco IOS error messages → /cisco/section/ios_error_messages.html
• Cisco troubleshooting by symptom → /cisco/section/troubleshoot_symptoms.html

References

• Cisco System Message Guide for IOS-XE / IOS
• Cisco Bug Search Tool: https://bst.cloudapps.cisco.com/bugsearch/
• Cisco Smart Software Manager: https://software.cisco.com
• Your Cisco SmartNet / Smart Care contract for TAC support

Reference material, not professional advice. Validate against your specific IOS-XE version and test in a non-production environment before applying.

What changed recently?

Fault diagnosis on the affected device goes faster when you map the symptom to a recent change:

• Did firmware update in the last 7 days?
• Did the network (router, ISP, VPN) change?
• Was the device moved physically?
• Did paired devices (phone, hub, app) update?
• Were any accessories swapped in or out?

The answer narrows the root cause to a manageable subset.

Isolate

A few things to confirm so the hardware fix goes cleanly:

• Latest firmware downloaded if you're going to update.
• Warranty + support contract status checked, opening sealed parts may void it.
• Backup of current configuration (where applicable) taken.
• Spare parts on hand if you anticipate replacement.
• Adequate workspace, lighting, and time. rushing causes regressions.

Validate

On the affected device, the test is rarely "reboot and see". Use this list:

• Active reproduction: trigger the original failure path on purpose.
• Indirect reproduction: do an activity that would expose the same subsystem.
• Status indicator review: every LED / display / app status should be green.
• 24-hour soak: leave the device under normal load overnight; check the next morning.
• Telemetry check: review the device or app's diagnostic log for new error entries.

When to call How support instead

Escalate if:

• The same symptom returns within 24 hours of a clean fix.
• You see physical damage (burn marks, swollen battery, cracked PCB).
• The device is in warranty and a hardware replacement is the cheaper outcome.
• Repair requires specialised tools you don't own (alignment jigs, calibration software).
• Following the official path keeps the warranty intact, which matters more than the time spent.

More frequently asked questions

Will this void my warranty?

Applying official firmware updates and following the user manual will not affect warranty. Opening sealed components, jumping safety circuits, or using third-party parts can void warranty in most jurisdictions.

What if my model isn't exactly the same revision?

Cross-check the model code on the rating plate against the manufacturer support page. Major firmware generations sometimes shift the menu path; the option is usually under a similarly-named section.

What if the fix returns after a reboot?

Persistent fault returns mean either: a hardware fault (escalate), a configuration that's being overwritten by a sync source (check cloud profiles), or a regression in a recent firmware update (rollback).

How often should I run preventive checks?

Quarterly for most consumer devices; monthly for production / commercial devices. Set a calendar reminder so the device stays healthy between issues.

Are there safer alternatives for non-technical users?

Yes, the manufacturer's self-service troubleshooter (HP Smart, LG ThinQ, Samsung Members, similar) usually walks through the same steps in a guided UI. Use that first if you're not comfortable with menu paths.

Field notes from real incidents on How to configure SSH access on Cisco Catalyst 9400

When I work on configure SSH access on Cisco Catalyst 9400 the rhythm I lean on is the one I have built over years of these tickets, not a stack of generic advice. I never run a software upgrade on a live Catalyst stack without an out-of-band console session; the in-band session drops at the worst possible moment. The newer Cisco IOS-XE traceability tools (show platform hardware fed) are massively underused; they answer questions the old CLI cannot.

Most catalyst stack issues I have triaged were power-budget related, not software: the show power detail output answers it in 5 seconds. Cisco bug search tool is the cheapest sanity check before a config change, search the symptom, sort by affected releases, decide. Cisco TAC will ask for show tech-support and a topology diagram on call one. I have both ready before I open the case.

Tools I actually reach for

For configure SSH access on Cisco Catalyst 9400 on How to configure SSH access on Cisco Catalyst 9400 the cheapest signal I can land usually comes from a known order of operations, not a kitchen-sink approach. I start with show running-config | include <feature> because it is the lowest-friction way to confirm the failure is real and reproducible. If that returns ambiguous data, I escalate to packet capture on the ingress interface (TAC will ask for it), show platform hardware capacity, ping vrf <vrf> <target>, and finally to show interfaces counters errors only when the cheaper tools cannot reach the layer the failure lives in. That ordering matches the failure surfaces I have actually seen on How to configure SSH access on Cisco Catalyst 9400 units over the last few years, not an abstract taxonomy. The cheap signals gate the expensive ones so the investigation does not balloon into a multi-hour exercise.

Verification I run before I close the ticket

Before I mark configure SSH access on Cisco Catalyst 9400 resolved on a How to configure SSH access on Cisco Catalyst 9400 unit, the verification loop below is what I actually run. Each step proves a different layer is green, and the order matters - the cheap checks gate the more expensive ones so I never burn an hour on a deep test that a shallow one would have failed in seconds.

show spanning-tree summary  # confirm topology stability

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

show bgp summary  # confirm session state after route changes

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

show interfaces <int> | include errors|drops|CRC

If that one comes back clean, move to the next check. If it does not, stop and dig in there before layering more verification on top of a red signal.

show logging | include %LINK|%LINEPROTO|%BGP|%OSPF

Only when every line above runs clean do I close the ticket and update the runbook with the timestamps. A green verification that nobody can reproduce is not a fix, it is luck waiting to regress.

Where I check first when the docs disagree

When two sources contradict each other on a How to configure SSH access on Cisco Catalyst 9400 detail, the disambiguation order I lean on is stable across products and across years. Cisco TAC case knowledge base is where I start for the ground-truth view. cisco.com/c/en/us/support, official command references is where I start for the ground-truth view. cisco.com/c/en/us/td/docs/ios-xml for IOS XR is where I start for the ground-truth view. Random blog posts and reseller wikis are signal, not ground truth, and I treat them as such until the references above either confirm or contradict the claim. The cost of trusting an unauthoritative source on configure SSH access on Cisco Catalyst 9400 is rarely worth the time it saved.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on configure SSH access on Cisco Catalyst 9400 have a habit of biting back. The pitfalls below are the ones I have personally walked into on a How to configure SSH access on Cisco Catalyst 9400 unit, not things I read about. The newer Cisco IOS-XE traceability tools (show platform hardware fed) are massively underused; they answer questions the old CLI cannot. Cisco bug search tool is the cheapest sanity check before a config change: search the symptom, sort by affected releases, decide. When in doubt I revert to the slower path that the manual prescribes - the time I save by skipping it is always smaller than the time I spend cleaning up afterwards.

What I tell the next on-call

When I hand configure SSH access on Cisco Catalyst 9400 off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature on How to configure SSH access on Cisco Catalyst 9400 - not a paraphrase, the exact string that surfaces in logs or on the screen. Second, the diagnostic that gave the highest signal in the least time. Third, the exact verification command whose green output justified closing the ticket. That trio is what turns a one-off fix into a runbook entry the next engineer can use without paging me at three in the morning.

I also add a one-line note on the cost of getting this wrong. For configure SSH access on Cisco Catalyst 9400 on a How to configure SSH access on Cisco Catalyst 9400 unit, the cost is rarely the replacement part or the patch itself. It is the downtime, the second site visit, and the trust deficit you spend with whoever owns the asset when the fix does not hold. That framing keeps the next on-call from choosing the cheap-looking shortcut that ends up costing the most in elapsed hours and goodwill.

Related fixes

Related guides worth a look while you sort this one out:

• How to configure SSH access on Cisco Catalyst 2960X
• How to configure SSH access on Cisco Catalyst 3850
• How to configure SSH access on Cisco Catalyst 9200
• How to configure SSH access on Cisco Catalyst 9300
• How to configure access port on Cisco Catalyst 9400
• How to configure SSH access on Cisco Catalyst 9500