IBM Power Systems 775 Manual page 84

3. Network event reporting
Event management examines each local network hardware event and, if appropriate,
forwards the event to the EMS for analysis and reports to the service focal point. Event
management also sends the following local routing events that indicate changes in the link
status or route tables within the local drawer that other LNMCs need to react to:
– Link usability masks (LUM): One per hub in the drawer, indicates whether each link on
that hub is available for routing
– PRT1 and PRT2 validity vectors: One each per hub in the drawer, more data is used in
making routing decisions
General changes in LNMC or network status are also reported via this interface.
4. Remote network events
After a local routing event (LUM, PRT1, PRT2) is received by CNM, CNM determines
which other LNMCs need the information to make route table updates, and sends the
updates to the LNMCs.
The events are aggregated together by event management and then passed to route
management. Route management generates a set of appropriate route table updates and
potentially some PRT1 and PRT2 events of its own.
Changed routes are downloaded via hardware access. Event management sends out new
PRT1 and PRT2 events, if applicable.
5. Local hardware management
Hardware access provides the following facilities to both LNMC and CNM for managing
the network hardware:
– Reads and writes route tables
– Reads and writes hardware registers
– Disables and enables ports
– Controls optical link connectivity test
– Allows management of multicast
– Allows management of global counter
– Reads and writes performance counters
6. Centralized hardware management
The following functions are managed centrally by CNM with support from LNMC:
– Global counter
– Multicast
– Port Enable/Disable
Central Network Manage
The CNM daemon waits for events and handles each one as separate transactions. There are
software threads within CNM that handle different aspects of the network management tasks.
The service network traffic flows through another daemon called
Computing Hardware Server
Figure 1-55 on page 71 shows the relationships between the CNM software components. The
components are described in the following section.
70
IBM Power Systems 775 for AIX and Linux HPC Solution
.
High Performance