A set of object types is used to represent a wide range of active equipment such as switches, routers, muxes, and CPEs (Customer Premises Equipment). To manage different kinds of structures, the object model is organized into six levels.

 

Object Model

Active equipment

This is the top level and the only object type placed in nodes or racks. All other levels in the hierarchy exist only within active equipment. The active equipment can represent anything from a small CPE to a multi-shelf high-end switch. It is media-independent, meaning it does not belong to the fiber, copper, or radio domain.

 

Shelf/Module

This optional level represents a shelf, typically a horizontal shelf as part of a larger switch. It can only be placed in active equipment. The shelf is media-independent. At the same level, the module represents a more generic concept. For the remainder of this section, the term "shelf" is used.

 

Card

This optional level represents a card, either vertical or horizontal, and may be placed in a shelf or in active equipment. The card is media-independent.

 

Group

This optional level represents a collection of ports that are typically not removable, like a card, but still have properties in common. The group can be placed in a card, a shelf, or in active equipment. The group is media-independent.

 

Port/Interface

This level is not optional and is media-dependent, meaning it has separate object types for fiber, copper, and radio. A port/interface can be placed in a group, a card, a shelf, or in active equipment. For the remainder of this section, the term "port" is used.

 

Contact

The contact is a child of the port/interface and connects to fibers, patches, copper wires, and so on.

 

Product specification

For each level in the object model, except for the contact level, there is a corresponding product specification object type. The primary purpose of the product specification is to define the structure below its level. This is often done by using references to other product specifications, forming a hierarchy that mirrors the hierarchy of the actual equipment objects.

See section Create product specification for further description of product specifications.

 

Product specification - Active equipment unit

A product specification for the top-level object, the active equipment, has five parts:

•Attributes - A set of attributes that belong to the active equipment level. Some of these attributes, such as the ID, belong only to the product specification, while other attributes will be copied to the actual active equipment when the product specification is applied.

•Shelf components - Zero or more components representing shelves that are directly placed in the active equipment. These components have a set of attributes that will be copied into actual shelves when the product specification is applied. The component may also contain a reference to a shelf product specification.

•Card components - Zero or more components representing cards that are directly placed in the active equipment and not via a shelf. These components have a set of attributes that will be copied into actual cards when the product specification is applied. The component may also contain a reference to a card product specification.

•Group components - Zero or more components representing groups that are directly placed in the active equipment and not via a shelf or card. These components have a set of attributes that will be copied into actual groups when the product specification is applied. The component may also contain a reference to a group product specification.

•Port components - Zero or more components representing ports that are directly placed in the active equipment and not via a shelf, card, or group. These components have a set of attributes that will be copied into actual ports when the product specification is applied. The component may also contain a reference to a port product specification.

 

Product specification - Active equipment shelf/module

The shelf product specification has four parts, similar to the five parts of the product specification for active equipment, except that the first part refers to the shelf rather than the active equipment, and the part with shelf children is missing.

 

Product specification - Active card

The card product specification has three parts, similar to the four parts of the product specification for shelves, except that the first part refers to the card rather than the shelf, and the part with card children is missing.

 

Product specification - Active equipment group

The group product specification has two parts, similar to the three parts of the product specification for cards, except that the first part refers to the group rather than the card, and the part with group children is missing.

 

Product specification - Port

The product specification for ports is the last in the hierarchy and only specifies the contacts and their attributes.

 

Create objects in active equipment

Except for the top-level object, which is always created when placed in either a rack or a node, there are two main ways to create objects in active equipment:

•Using attribute forms - In the attribute forms of active equipment, shelves, cards, groups, and ports, there are tables that list the direct child objects. For example, in active equipment, there is a separate table for each shelf, card, group, and port. These tables include buttons for adding and deleting the respective objects.

•Applying product specifications - When a product specification is applied at any level, the structure defined in the product specification will create the specified objects. This process cascades throughout the hierarchy, so when product specifications reference other product specifications, all referenced specifications will be applied.

 

Active equipment management for larger devices

Although the active equipment model supports a product specification for a full hierarchy, this is not always the optimal solution.

In many cases, it may be better for the product specification of the top-level object, meaning, the active equipment, to include only the ports mounted in the chassis and perhaps a card that is always present. The other cards can be created and placed manually within the equipment. This approach should also be used when adding additional cards to an existing device.

 

SFP handling

dpCom does not explicitly model the SFP (Small Form-factor Pluggable) slot. Instead, the SFP module is treated as a variant of a port and is placed similarly to a fixed ethernet or fiber port. An SFP slot that does not contain an SFP can either be ignored or documented using the Empty SFP object.

When replacing an SFP, there are two options for updating this in dpCom:

•No configuration change - If the configuration of the contacts remains the same, simply update the relevant attributes of the existing port to reflect the new SFP. This approach maintains any existing patches to the contacts.

•Configuration change - If the SFP type changes significantly, such as from single fiber to dual fiber, the process is more complex as it involves modifying the underlying contact structure. In such cases, it might be more efficient to delete the existing port and create a new one. For changes from an Ethernet SFP to a fiber SFP, you must delete the Ethernet SFP and create a new fiber SFP.