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

32
The format and method for the delivery of data varies considerably for stakeholders.
Operations teams needing data as quickly as possible rely on methods such as Email or SMS
text messaging, console presentation or integration with other management systems for the
quick delivery of data. Oftentimes, operations teams and NOCs use one or more of these
methods and formats for data.
• If the data is needed for historical reporting, what kinds of reports are needed? Tabular, graphical?
Historical reporting requirements typically focus more on how the data is presented.
Understanding how your stakeholders want the data presented (bar charts, pie charts, scatter
graphs, and tables) helps you meet their needs.
• Is export to raw data files required?
Many times stakeholders want raw data as they have their own systems for analyzing and
presenting the data in ways most useful for them. Additionally, stakeholders may have data
retention or polling requirements that extend beyond the scope or ability of IMC.
Understanding the data requirements of your stakeholders enables you to know whether or not
exporting data from IMC is the best option available for your stakeholders.
Stakeholder access and configuration requirements
In addition to the data that provides stakeholders with visibility into network resources and services,
stakeholders also need access to IMC. Access may be needed for viewing purposes only, for configuring
and managing devices, users, and services in IMC, or for the configuration and management of IMC
itself. Understanding what levels of access are needed to IMC and the devices, users, and resources it
manages helps you configure IMC to support stakeholder needs.
Knowing your network infrastructure
To deploy IMC successfully, you need to have a clear understanding of the network infrastructure that
IMC monitors and manages.
Knowing your network topology
While IMC does auto discoveries, it relies on the accurate identification of seed IP addresses to begin the
discovery process. Identifying those IP addresses that best serve as seed IP addresses to discover the
whole of your network ensures a successful IMC deployment. Also, IMC can auto discover logical
relationships in the network infrastructure and this influences how IMC identifies root and symptom
alarms in its event deduplication and root cause analysis algorithms. If needed, you can make
adjustments to the devices IMC defines as the core and access devices that determine how root and
symptom alarms are identified. The network documentation that you need includes topology maps, IP
addressing schemes, and information identifying areas of your network that require special attention.
The topology maps you need should ideally include both physical and logical diagrams of the network.
A logical map helps you understand the relationships between devices and verify the accuracy of the
topology maps generated by IMC. Physical diagrams, including data center maps and details of
individual wiring racks, support you in creating accurate data center topology maps in IMC.
Next you need current and accurate documentation on the IP address schemes used. IP address
documentation should also include any areas in your infrastructure that have overlapping address spaces.
In addition, this documentation should include any locations or devices on the network that use
non-routable IP addresses.
The network documentation should also identify areas or zones in your network that have special access
requirements.