Cisco: How to configure password encryption type 8 / type 9

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

What this guide covers

How to configure password encryption type 8 / type 9.

Repair sequence

1. Type 9 (Scrypt) is the strongest IOS-XE password hash.
2. Use username X algorithm-type scrypt secret Y to store passwords with Scrypt.
3. Or use enable secret with algorithm-type.

CLI commands

configure terminal
username netadmin privilege 15 algorithm-type scrypt secret 0 StrongPass
enable algorithm-type scrypt secret 0 EnableStrongPass
service password-encryption

Verify

• Test from a non-admin workstation.
• Confirm fallback works in case AAA / external service is down.
• Document the change in your CMDB / change-control.

Frequently asked questions

Will this work on my exact IOS-XE / ASA version?

The procedure reflects current IOS-XE 17.x and ASA 9.20 behaviour. Older trains (15.x, 9.16 ASA) may need minor syntax adjustments. use ? in the CLI.

Should I open a TAC case immediately?

Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your SmartNet is active first.

Where can I find the Cisco official documentation?

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

Is this procedure safe in production?

Test in a lab or maintenance window first. Capture pre-change state so you can roll back.

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
• Cisco TAC: https://mycase.cloudapps.cisco.com/case

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

Signal review

When this symptom shows up on a Cisco: device, three patterns repeat:

1. Recent firmware update changed behavior: the symptom started within a week of an OTA push. Rollback or wait for the hotfix. 2. Environmental trigger, temperature, humidity, line voltage, network changes. Look at what changed in the environment. 3. Cumulative wear. components like batteries, gaskets, fans degrade over time. Replace the consumable rather than chasing a software fix.

Knowing which pattern applies saves time on the wrong fix.

Safety + preconditions

Before any work on a Cisco: device:

• Unplug from mains for any internal-access procedure.
• Discharge stored energy (capacitors in PSUs, residual battery charge) per manufacturer guidance.
• Use ESD-safe handling for boards and modules, no carpet, no wool sleeves.
• Avoid moisture; never apply liquids near vents or connectors.
• If you smell smoke, see scorch marks, or feel uneven heat, stop and escalate.

Post-repair audit

Before you walk away from a Cisco: device fix, run through:

1. Reproduce the original trigger: does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + firmware version.

When to call Cisco: 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 the procedure work on the international variant?

Some features and firmware paths are region-locked. Check the model spec sheet to confirm your variant supports the menu option referenced. If you're outside the US/EU, look for the regional support portal.

Can I roll this back if something breaks?

Yes for software-level changes (firmware rollback, config rollback). Hardware changes are usually one-way. Always back up settings before starting.

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.

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.

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.

Field notes from real incidents on Safe Protocols & Hardening

When I work on Cisco: How to configure password encryption type 8 / type 9 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. Cisco TAC will ask for show tech-support and a topology diagram on call one. I have both ready before I open the case.

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.

Tools I actually reach for

For Cisco: How to configure password encryption type 8 / type 9 on Safe Protocols & Hardening 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 show platform hardware capacity, packet capture on the ingress interface (TAC will ask for it), and finally to show tech-support (capture for TAC) only when the cheaper tools cannot reach the layer the failure lives in. That ordering matches the failure surfaces I have actually seen on Safe Protocols & Hardening 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 Cisco: How to configure password encryption type 8 / type 9 resolved on a Safe Protocols & Hardening 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 ip route <prefix>  # confirm best path post-change

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 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 logging | include %LINK|%LINEPROTO|%BGP|%OSPF

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 bgp summary  # confirm session state after route changes

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 Safe Protocols & Hardening detail, the disambiguation order I lean on is stable across products and across years. cisco.com/c/en/us/td/docs/ios-xml for IOS XR is where I start for the ground-truth view. Cisco TAC case knowledge base is where I start for the ground-truth view. developer.cisco.com for NSO / model-driven APIs 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 Cisco: How to configure password encryption type 8 / type 9 is rarely worth the time it saved.

Pitfalls I have walked into on this exact path

The shortcuts that look smart on Cisco: How to configure password encryption type 8 / type 9 have a habit of biting back. The pitfalls below are the ones I have personally walked into on a Safe Protocols & Hardening unit, not things I read about. 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. 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 Cisco: How to configure password encryption type 8 / type 9 off to the next person on rotation, the three lines I leave in the runbook are these. First, the symptom signature on Safe Protocols & Hardening - 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 Cisco: How to configure password encryption type 8 / type 9 on a Safe Protocols & Hardening 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:

• AnyConnect Secure Client OSPF area type mismatch stub vs nssa: Fix
• AnyConnect Secure Client OSPF network type mismatch broadcast vs point-to-point:
• AnyConnect Secure Client OSPF NSSA Type 7 LSA not converted to Type 5: Fix
• How to configure AnyConnect SSL VPN basic on AnyConnect Secure Client
• How to configure BGP route reflector iBGP scaling on AnyConnect Secure Client
• How to configure Catalyst Center fabric site on AnyConnect Secure Client