Model Interfaces Reference¶
The NOC's inventory enables the storage of additional data in the Model Interfaces. Each Model Interface comprises attributes that convey specific physical or logical meanings. We define each Model Interface to serve a particular task, such as dimensions, weight measurements, power consumption, and more. NOC provides a wide range of built-in model interfaces, and users can create their own interfaces for their unique tasks.
This section details the Model Interfaces available in NOC, their attributes, and how they find application in various scenarios.
Built-in Model Interfaces¶
| Model Interface | Description |
|---|---|
| address | External GIS system bindings |
| agent | NOC Agent's bindings |
| airflow | Airflow direction for cooling |
| asset | Inventory reference, asset, and serial numbers |
| caps | Object's capabilities |
| contacts | Administrative, billing and technical contacts for container (PoP, Room, Rack) |
| container | Denotes object containers |
| cpe | CPE bindings |
| cpu | CPU capabilities |
| dimensions | Physical dimensions, like length, width, and height |
| dwdm | DWDM transponders capabilities |
| geopoint | Geographical coordinates |
| hwlimits | Hardware limits of the devices |
| length | Cable length |
| management | Managed Object binding |
| modbus | Modbus endpoint configuration |
| optical | Optical transceiver capabilities |
| plan | Plan or scheme position |
| pop | Point of Presence capabilities |
| power | Power consumption parameters |
| rack | Rack enclosures |
| rackmount | Rackmount equipment parameters and position |
| sector | Antenna sector position |
| splitter | Split optical/electrical input power to outputs with given gain |
| stack | Indication of stack/virtual chassis/cluster |
| twinax | Twinax transceiver (two transceivers connected by cable in the assembly) |
| weight | Weight properties |