Describe or list the activities and services involved in this Function (in the context of this Function). An activity or service can be provided by a computer system, a set of applications, or manual procedures. These activities/services should be described at an appropriate level, with the understanding that sub-activities and services should be described if they are important for operational issues, automation needs, and implementation reasons. Other sub-activities/services could be left for later analysis.
Activity/Service Name xiii
Activities/Services Provided xiv
Object management - Defining resources and attributes
EnergyManagementSystem needs to be aware of resources: routers, hubs, computers, and their attributes.
Defining, modifying and examining relationships
EnergyManagementSystem needs to be aware of the object relationships.
Setting, modifying and examining attribute values
Object attributes need to have values. E.g, number & types of ports per card.
IM is the task of maintaining types and configuration of resources. The inventory information is required for SW and HW maintenance, determination of faults and recovery, and capacity planning.
Dynamically creates a representation of the network topology, and configuration of the devices. The data could be collected manually, which is very tedious and often not accurate for a large network, or though an EnergyManagementSystem. Instances of the managed devices and their internal components are created and connections are made. Components and info on the devices include network cards, ports, interfaces, power supplies, MAC addresses, SW version, OS type, CPU types, IP addresses, etc.
Address management includes allocation IP addresses to devices, determination of subnets, keeping track of used and available IP addresses, and reuse of unused addresses. This task reduces addressing complexities and waste of address space.
Naming establishes a connection between a name and a device, its location, its type, etc. Helps identify devices, IP address mappings, etc. Naming conventions for network devices, starting from device name to individual interface, should be planned and implemented as part of the configuration standard. A well defined naming convention provides the ability to obtain accurate information when troubleshooting. The naming convention for devices can use geographical location, building name, floor, and so forth. For the interface naming convention, it can include the segment to which a port is connected, name of connecting hub, and so forth.
Determine and configure routing tables. This includes configuring parameters for IP routing , Quality of Service, etc.
SW distribution and upgrade
This includes detection of SW releases, distribution of new releases, and testing for interoperability.
Setting & verifying user authorization
Scheduling, user/flow/packet prioritization
This is to allow for a specific treatment of users, flows, or packets based on availability of features on the routers, switches and computers to meet QoS requirements or SLA’s.