Configuring the Local Status Page

Last updated
Save as PDF

The following dashboard configuration options are needed to access the local status page:

Changing Log-In Credentials

Default credentials for the local status page should be modified to use an administrator-defined password. To do so: Navigate to Network-wide > Configure > General > Device configuration and provide a strong password.

The password you set will apply to all devices in your network.

Passwords will need to meet following requirements:

At least one number
At least one uppercase letter
At least one lowercase letter
At least one symbol
Allowed symbols: !"#$%&'()*+,-./:;<=>?@[]\^_`{}|~
14 character length minimum

Changing to an empty password

Customers have the ability to clear their password and reduce their security posture if so desired.

To clear the password using the API, the network admin would set the password to null or an empty string ””.
To clear the password using the UI, the network admin would update with an empty field.

Do I need to change my password if it does not currently meet this criteria?

No, these password requirements are only enforced when an update to the Local Status Page password is made. The current state of passwords are not impacted.

Viewing the Local Status Page Password

Users are unable to view the existing password in Dashboard. If you have forgotten/misplaced your LSP password, you may update it as per above.

Resetting the Local Status Page Password

You can reset your local status page password back to default: delete the current password and then save the change; password will be back to default after your device gets new configuration from your Dashboard.

Note: Support is not able to view or update your password.

Default credentials when logging in for the first time

username = admin, password = serial number (Cloud ID) of the device (upper case letters and dashes)
- MR devices running MR 32+ firmware
- MX devices running MX 19+ firmware
- MS devices running MS 17+ firmware
- MS390/Catalyst devices (CS 17+ or IOS-XE 17.15+)
- MG devices running MG 4.1.1 firmware

username = serial number (Cloud ID) of the device (upper case letters and dashes), password = 'no password'
- All devices running other firmware versions

Networks created after August 1, 2025

To ensure the highest level of security and meet evolving regulatory requirements, we are implementing mandatory passwords for all Local Status Page access on devices created after August 1, 2025. Any networks created prior to this time will not be impacted.

Why is this Change Necessary

This enhancement is being implemented to comply with EU RED (European Union Radio Equipment Directive) security regulations and strengthen overall device security. Previously, some devices could, and can continue to use their serial number as a default access credential, which poses potential security vulnerabilities.

All new networks created after August 1, 2025 will require stronger authentication mechanisms to protect network infrastructure.

What's Changing

Networks created before August 1, 2025:

Networks could be created without passwords and devices could use the serial number as a password or none (firmware dependent, see “Default credentials when logging in for the first time” section).

Networks created after August 1, 2025:

All new networks after August 1, 2025 will require a password to be explicitly set for Local Status Page access.

Scenarios:

Setting a password when the network is created:
The network admin is required to set a password after the network is created on the network settings page. Passwords will need to meet the criteria for "strong password" defined in the "Changing Log-In Credentials" section.
Setting a null or empty password (“”):
A network admin may choose to not use a password if desired, which can be done via API, by providing a null or empty string (“”) value for the password, or in the UI by updating with an empty field.
Auto-generated password with admin intervention before first LSP use:
If a password is not explicitly set by an admin, an auto-generated password will be sent to the device on its first configuration fetch, causing the Local Status Page to be inaccessible until a password (or lack thereof) is set by the admin.

Neither Meraki nor the network admin will have visibility to this password. If the device has not connected to the internet, it may use its default credentials to access the Local Status Page.

How does this impact template or cloned networks:

Networks created via template or cloning after the August 1, 2025 00:00:00 UTC date will be subject to the mandatory password criteria. If a password already exists in the template or origin network, that password will be transferred to the new network and will not have an auto-generated password applied.

If a newly created network is bound to a template that has never had a password set, the network admin must set one on the template. They have two options:

Set the template password to the recommended credentials, which will apply to all networks bound to the template.
Set the template password to empty, which preserves the null password behavior for existing networks and allows new networks to function without a password.

How does this impact Automated Network Deployments:

If you currently use automation tools or scripts for network provisioning and device setup, please update your automation workflows to include setting a Local Status Page password via the Network Settings API (https://developer.cisco.com/meraki/api-v1/update-network-settings)