Cisco Operators: Catalyst Center, ISE and SD-WAN

Cisco Operators work campus, network access and branch tickets through Catalyst Center, Cisco ISE and Catalyst SD-WAN, and leave risky changes to a person.

REQUEST DEMO

READ THE DOCS

2501's three Cisco Operators work through Cisco's own platforms: Catalyst Center for the campus, Cisco ISE for network access and Catalyst SD-WAN for branch links. Each investigates first, changes only what the ticket needs and leaves risky changes to a person.

A user cannot get on the Wi-Fi, a branch keeps dropping off, a switch has drifted from its standard configuration. The cause often sits elsewhere: a failed Wi-Fi login shows up in the access system but usually comes from the directory, the user's device or the network equipment.

What 2501 does

Cisco Catalyst Center Operator: keeps the device inventory in step, checks device and Wi-Fi health, fixes configuration drift through your templates and upgrades software in approved maintenance windows.
Cisco ISE Operator: diagnoses failed logins from the reason ISE recorded, registers network devices, manages endpoints and unlocks internal users locked out after failed attempts.
Cisco SD-WAN Operator: investigates branch reachability, unstable tunnels and applications missing their performance targets, and corrects configuration drift on branch devices.

When the cause lies in another system, the ticket goes to whoever owns it, with the findings.

Scope map of 2501's Cisco Operators: through Catalyst Center it checks device and Wi-Fi health, keeps the inventory in step, fixes configuration drift and upgrades software in approved windows, through Cisco ISE it diagnoses failed logins, registers devices, manages endpoints and unlocks users, and through Catalyst SD-WAN it investigates branch links and corrects drift; access rules, SD-WAN policies, sites, campus layout, device removal, large batches and unclear causes go to a person, and the platforms' own access and cluster settings and passwords are never touched.

You stay in control

You choose the level, per specialty: investigate only, act after a person confirms, or act on its own within your rules.
Risky changes wait for a person: editing access rules, activating an SD-WAN policy, changing sites or the campus layout, removing devices, changing more than ten devices at once, and any fix whose cause is unclear.
The platforms stay yours: their own access and cluster settings are never touched, and blacklisted commands stay out of reach.
On-prem, cloud or hybrid: 2501 runs wherever you do. On-prem, no data leaves your network.

Frequently asked

Will it reset a password to fix a login? No. Passwords belong to your identity team. After an unlock, it waits for the user's next real login to confirm the fix.

Will it push configuration straight to a switch? Not for anything a template manages. Changes go through Catalyst Center or the SD-WAN manager, so the next sync keeps them.

Problems it handles

Each page is one kind of ticket, and how this specialty handles it within the limits you set.

A failed network login recorded in Cisco ISE is diagnosed by 2501 from the reason ISE recorded, which fixes what belongs in ISE with the smallest change and hands the rest to the team that owns it

Problem

Cisco ISE authentication failure

A failed login shows up in Cisco ISE, but the cause often sits elsewhere. How 2501 reads the reason ISE recorded, fixes what belongs in ISE and routes the rest.

See how it is handled

Cisco Operators: Catalyst Center, ISE and SD-WAN

What 2501 does

You stay in control

Frequently asked

Related

Problems it handles

SEE IT ON YOUR OWN INFRASTRUCTURE