H3C Technologies H3C Intelligent Management Center - Manual (Page 42)

28
Networks can also grow in their demand for higher performance from IMC as the demand for network
services and network management services grows. Given IMC distributed processing at the CSU or
middleware layer and a communication bus that all IMC instances and service modules publish and
subscribe to, operators can meet this demand by deploying separate instances of one or more CSUs.
For example, organizations that have high demand for fault management may consider deploying the
Fault CSU on a dedicated system. Or, large organizations that use IMC to manage device configurations
and change may consider deploying the Configuration CSU on a dedicated system for higher
performance.
IMC can also grow in diversity of device types that can be managed. IMC abstracts information about
device vendors, device types, command sets, and execution methods and stores this at the Data
Abstraction Layer that is shared by all CSU modules. This means that IMC can easily and seamlessly add
new devices as they emerge and continue to add abstractions for existing devices with each new release
of IMC.
Given IMC SOA framework, H3C continues to develop new CSU modules at the middleware layer that
are aligned with IT functional needs as those needs change and grow. Extending IMC to meet new
functional needs is as simple as developing a new CSU that participates in the publish/subscribe
communication bus and shared Data Access Layer and IMC database resources.
In short, IMC framework offers administrators and operators room to grow as their networks grow and
their demand for integrated network management grows.