highlights and lowlights of the daily business of network engineers

Download als PDF File

Purpose

This note compares iMaster NCE-Campus and Cisco Catalyst Center in detail from the perspective of technical operations staff.

Scope:

• This document focuses on Catalyst Center.
• ISE is referenced only where the functional boundary of Catalyst Center is reached.
• NAC / AAA / policy details will follow in a separate note dedicated to ISE.

1. Technical Positioning

Technical takeaway:

• NCE-Campus is the central platform layer on the Huawei side.
• Catalyst Center is the central campus layer for management and automation on the Cisco side.
• The Cisco overall architecture is more modular and split than the Huawei architecture.

2. Platform Architecture

iMaster NCE-Campus

Architecture characteristics:

• deployment as single node, minimum cluster, distributed cluster, multi-cluster
• role separation is possible:
  • service / controller
  • middleware
  • big-data analytics
• documented geo-redundancy with primary, secondary, arbitration
• operating models for on-prem, MSP-owned cloud, and Huawei public cloud

Cisco Catalyst Center

Architecture characteristics:

• central controller for Cisco campus design and operations
• appliance- / cluster-oriented model
• strong coupling to Cisco campus architecture, especially SDA
• assurance, automation, and provisioning services inside the platform
• no direct equivalent to Huawei multi-cluster

Direct Comparison

3. Site and Hierarchy Model

iMaster NCE-Campus

• Site-based structure is a basic platform element.
• Site objects are directly linked to configuration, monitoring, device association, and in some cases policies.
• Visible in the demo UI:
  • Network Plan
  • Site Configuration
  • Batch Site Configuration
  • Clone from an existing site

Catalyst Center

• hierarchical site modeling is also a core platform element
• sites are used for design, device assignment, policy scope, and provisioning
• typical hierarchy:
  • area
  • building
  • floor
• strongly coupled to provisioning, PnP, and SDA workflows

Direct Comparison

4. Device Onboarding and Day-0

iMaster NCE-Campus

Technical characteristics:

• device association through ESN, model, site, and device type
• ESN-free preplanning supported
• southbound IP service as part of site creation
• device types explicitly selectable in the site context:
  • Cloud AP
  • AR
  • FW
  • LSW
  • WAC

Operational meaning:

• preplanning before actual hardware claiming is possible
• rollouts can be prepared in a model-based way
• hardware can be assigned later to the predefined site

Catalyst Center

Technical characteristics:

• PnP is the central onboarding model
• claiming through serial number, device record, site assignment, and provisioning workflow
• clearer separation between design and provision than in many Huawei workflows
• strong coupling to Cisco device inventory and Cisco-specific discovery / claiming mechanisms

Operational meaning:

• standardized Cisco rollout process for new devices
• strong linkage with site assignment and template / day-1 provisioning

Direct Comparison

5. Configuration Model

iMaster NCE-Campus

Visible and documented building blocks:

• Template Management
• Configuration Mode
• Default Settings
• Clone from an existing site
• Configuration File
• Batch Device Configuration
• Batch Site Configuration
• Configuration Results
• Configuration Saving
• Configuration Consistency
• Configuration Review
• Configuration Source Tracing

Technical characteristics:

• configuration is organized in a platform-centric way
• site, template, and batch models are tightly integrated
• config governance is explicitly visible
• source tracing and consistency checks are strong operational features

Catalyst Center

Typical building blocks:

• design
• provision
• template-based configuration
• compliance / provisioning state
• device- / site-based rollout logic
• intent- / fabric-related policies

Technical characteristics:

• configuration is more strongly tied to Cisco design models and fabric / intent logic
• template workflows are strong, but the operational context is more tightly coupled to Cisco architecture
• provisioning and policy are more tightly linked to SDA and Cisco design objects

Direct Comparison

6. Fabric / Overlay / Segmentation

iMaster NCE-Campus

• VXLAN is explicitly visible in the configuration model.
• Virtual Network / campus-fabric-related logic is part of the Huawei campus stack.
• Overlay and segmentation are not reduced to one single operating model.

Catalyst Center

• SDA is the dominant fabric model.
• fabric provisioning, fabric sites, policy, and segmentation are tightly coupled in the Cisco campus model.
• VXLAN is the technical underlay / overlay mechanism, but operationally strongly abstracted by SDA.

Direct Comparison

7. Monitoring and Operational Data

iMaster NCE-Campus

Visible in the UI and notes:

• Device 360
• Clients
• WLAN Monitoring
• Site Monitoring
• Inter-Site Monitoring
• Statistics Analysis
• Agile Reports
• Periodic Tasks
• Data Collection Settings

Technical characteristics:

• operational data, monitoring, and configuration data are closely linked
• site, device, and client perspectives are directly connected
• data collection can use HTTP/2, UDP, and Telemetry

Catalyst Center

Technical characteristics:

• device, client, and site health are core elements of assurance
• telemetry- and event-driven analytics
• strong use of health scores, client context, and fabric / path context
• reports and assurance are part of the standard operating model

Direct Comparison

8. Assurance, Telemetry, and Analytics

iMaster NCE-Campus

• CampusInsight extends NCE-Campus with deeper analytics.
• Focus:
  • Network Health View
  • User Experience
  • Application Experience
• technical data path:
  • SNMP for device management
  • Telemetry for metrics
  • Syslog for logs
  • big-data stack with Kafka, Spark, HDFS, Druid
  • AI engine

Catalyst Center

• assurance is a native platform component
• focus:
  • network health
  • client health
  • device / path context
  • event correlation
  • root cause
• for deeper cross-domain experience or specialized analytics, additional Cisco components may become relevant

Direct Comparison

Technical takeaway:

• Huawei documents the analytics architecture more explicitly.
• Cisco integrates assurance deeply into the campus controller operational model.
• In Cisco environments, functional coverage is often distributed more strongly across multiple platform components.

9. Operations and Day-2

iMaster NCE-Campus

Visible in the demo menu:

• Device Upgrade
• Device Logs
• Device Syslog Settings
• Diagnosis Tools
• SLA Management
• Device Health Check
• File Management
• Device License Activation

Catalyst Center

Typical focus:

• software image management
• device provision / reprovision
• compliance / config drift / inventory
• assurance-driven fault analysis
• fabric / policy-related day-2 changes

Direct Comparison

10. Functional Boundary to ISE

This is where the clean Catalyst Center comparison ends.

Topics that do not primarily belong to Catalyst Center on the Cisco side:

• AAA
• RADIUS / TACACS control plane
• guest lifecycle
• profiling
• posture
• central access-policy decision
• identity-store-adjacent logic

These topics must be compared against ISE, not Catalyst Center.

11. Technical Conclusion

In short:

• iMaster NCE-Campus is more integrated as a total platform.
• Catalyst Center is technically strong, but more tightly aligned to the Cisco campus stack.
• As soon as access policy, NAC, and AAA are compared in depth, the analysis must be expanded to ISE.

Next Step

• Next, iMaster NCE Admission / Policy / Guest should be compared in detail against Cisco ISE.

Samuel Heinrich

Senior Network Engineer at Selution AG (Switzerland)

Arbeitet in Raum Basel (Switzerland) als Senior Network Engineer mit über 15 Jahren Erfahrung im Bereich Netzwerk