Integrating with other Systems
Do you have plans for integrating your OSS with other systems but don’t know where to start? I start by developing an Interface Requirement Specification (IRS). This course provides you with the process and templates for identifying your NBI and mapping data across these interfaces into your OSS. The templates include sample device types for many different styles of network elements and systems
The course walks you through the creation of an Interface Requirement Specification (IRS) with sections that include
- Introduction to the interface
- Interface description (eg manufacturer, domain, agent type, version, physical interface, management interface)
- Interface types (eg alarms, performance, inventory / config, provisioning, admin, etc). [Note that a single device type may have completely independent interfaces for each of the interface types]
- Interface protocol (eg SNMP, CORBA, etc)
- Connectivity specifications (eg MIBs, IDLs, etc)
- Code libraries and associated documentation
- Message style – some interfaces use file / log transfers rather than messages, others allow sessions to be established
- Format of the messages (eg header, object identifiers, index/counters, message content, framing, timestamps, timeouts, status, etc).
- List of message types, definitions, variables and usage / description
- Managed objects (eg devices, cards, ports, etc)
- Special interpretations, enrichments, parsing rules, mapping, derivations, thresholds or actions to take with each type of message. [Note that you may even need a description of the network under management, such as topologies, services, naming conventions, etc to explain the interpretation of messages]
- Classification of OSS objects (eg fields in a database) for the source data to be mapped to
- Mapping of messages into OSS objects
- List of violations or exceptions and corresponding descriptions of how to handle them
Fill in your details below if you’d like to find out more about this course:
