Details

Support

Additional Information

Device types

 1830PSS-PHN

1830PSIM

Shelf

Yes

Cards

Yes

Ports

Yes

Fans

Yes

Power

No

Pluggable transceivers

Yes

Protocol

TAPI

Data Model

JSON

Notifications

Yes

If there is any exception occurs during notification processing, HCO will go for full polling as a fallback mechanism.

Limitations

If any device is deleted from the controller outside of the HCO, then the same device must be deleted manually from HCO device Manager App.

Details

Support

Additional Information

Link layers

OTS, OMS, OCH, OTU, ODU, ETH, OC, NMC, STM.

·       OCH links extra field is updated to include information on protection-type restoration-policy and reversion-mode (Path restoration bits) data.

·       The TAPI connection response for the OCH layer with connection_path parameter as “Path” will be discovered as NMC link in HCO.

·       NRC-T reports only Optical Transmission Section (OTS) layer and HCO builds Optical Monitoring System (OMS) layer from OTS data but OMS name will be formed in HCO using the format source NE/source port <--> dest NE/dest port.

Cross links

Yes

Cross domain links

No

Protocol

TAPI

Data Model

JSON

Notifications

Yes

The notification from the controller does not carry the modified BW information. So, HCO will poll for that information.

Limitations

·       OTS link name in HCO will contain OMS string as this was reported from NRC-T response itself.

·       For 11DPM12 card, the ODU connection might have the STM end points due the controller issue, due to this HCO will not discover the complete path.

·       For OTS/OMS, Nokia supports unidirectional support. HCO populates both unidirectional pair names in the name field. For some unidirectional packs, Nokia reports only 1 unidirectional port based on where traffic is flowing. In this case, unidirectional pair port name will be having only 1 port name.

·       The OS/OPS links are not supported in HCO. But in some Nokia connections, OPS is used as a physical connection without any OTS/OMS layer involved. To show the full physical path, HCO discovers these OPS links as NMC links in HCO. These NMC links will not have any underlay path as they are the last physical layer in the controller.

·       There will be an LOGICAL NMC link created to visualize filter ports participating in these OPS links, which will have OMS as the underlay path.

Details

Support

Additional Information

Link layers

No

Cross domain links

No

Notifications

No

Protocol

NA

Data Model

NA

Details

Support

Additional Information

Service types

Circuit-E-Line, Wavelength, OTN-Line, SDH-Line.

The TAPI connection response for the OCH layer with connection_path parameter as “Path” will be discovered as Wave Length service/NMC link in HCO.

Service underlay

Yes

Cross domain services

No

Notifications

Yes

Protocol

NA

Data Model

NA

Limitations

·       In HCO, path will discover only one ODU while there can be other ODU layers of same rate available in the controller.

·       For some services, the service ports are reported as down from Nokia TAPI response. Hence, service port status will be shown as DOWN in HCO until the Nokia TAPI response sends the latest status data.

Details

Support

Additional Information

PM types

Yes

PACKET_IN, PACKET_OUT, OCTET_IN, OCTET_OUT

Resource types

Yes

Ethernet Port

Live PMs

No

PM collection method

SFTP PULL

Service type

Creation / Deletion

Modification

Brownfield

IP Link

SR-Policy

No

No

No

No

No

No

Circuit E-Line

Yes

Bandwidth for ODU Flex unprotected services.

Yes

OTN Line

Yes

 No

Yes

SDH Line

Yes

 No

Yes

Wavelength

Yes

 No

Yes

Name

Description

Default

Range/Note

Adapter Properties

Enabled

Enable or disable the adapter.

False

Enable this option once you are ready to run the adapter.

Logging Level

The logging level at which the discovery cycle is reported in the adapter log.

INFO

DEBUG, INFO, WARNING, ERROR, CRITICAL

Topology Data Fetch Interval [sec]

Fetch topology data every X seconds.

3600

Min: 0

Minimal interval between data updates [sec]

The minimum time between data updates. This is the period, for example 30 seconds, during which notifications are stored in the local adapter cache, after which discovery runs on the cache. If this is set to 0 seconds (default), the discovery runs immediately.

0

Min: 0

Full Data Fetch Interval [sec]

Fetch data every X seconds. The default is once a day.

86400

Min: 0

Internal Debug

False

SSH Configuration Parameters

General parameters regarding router communication, as well as tunnels.

Host

IP of the tunnel.

Port

Port to be used to connect to the tunnel.

8543

NFM-T Port

The NFM-T port.

8443

CAS Port

The CAS port.

443

Timeout

Timeout to connect to the router.

30

Credentials

The credentials to use with the router (SSH credentials).

Notifications Configuration

Used.

Enabled

Should the notifications listener be initialized or not?

False

Log Notifications

Whether to log the notifications?

True

Log Level

The logging level at which the notifications are logged.

INFO

DEBUG, INFO, WARNING, ERROR, CRITICAL

Congestion Control Period [sec]

The congestion control period (CCP) is the maximum gap allowed between two successive notifications before the adapter begins to process the notifications queue. This ensures that all notifications related to a particular network event are handled at the same time. For example, an interface down notification is usually followed by a link down notifications. Once the CCP period has passed with no further notifications, the adapter initiates a collect cycle and consequently processes the notification queue.

This parameter is used in conjunction with the max wait period (MWP).

5

Max Notification Wait Period [sec]

If notifications are received continuously at a frequency that is <= the congestion control period (CCP), then irrespective of the gap between two notifications, if the time elapsed since the first notification is greater than the MWP, the queue is processed immediately.

60

Notification Silent Period [sec]

Notification channel will reset after this period if no notification received.

3600

File bringer Configuration

Used to feed the adapter with local collection files instead of polling the routers directly.

Enabled

Should the File Bringer (FB) be enabled or disabled?

If the FB is enabled, the adapter ignores the server’s configuration and tries to fetch static files using the FB configuration.

These files must be provided by another service.

False

Remote Address with File Pattern

SFTP or a file folder on your machine and the file pattern.

^((ftp|sftp|file):\\/\\/(([^\\/:]+)(:(\\d+))?)?(\\/?[^:]+))|\\s*$

Credentials

The SSH_KEY or SFTP credentials.

PM Configuration

General parameters regarding performance metrics.

Enabled

Whether to collect performance metrics?

False

PM Data Fetch Interval [sec]

Fetch PM data every X seconds.

1800

Add_15mins_stats

Fetch 15 minute PM data.

True

Add_24hrs_stats

Fetch 24 hour PM data.

True

Remote Address with File Pattern

SFTP or a file folder on your machine and the file pattern.

^((ftp|sftp|file):\\/\\/(([^\\/:]+)(:(\\d+))?)?(\\/?[^:]+))|\\s*$

Credentials

The SSH_KEY or SFTP credentials.

Provisioning Configuration

Enable Service Provisioning

Enable Service creation, modification and deletion

False

Timeout [sec]

Timeout in seconds for completion all provisioning operations.

60

Optional Customization

ILA Node Name RE Pattern to Match

ILA node name RE pattern to match.

String

ROADM Node Name RE Pattern to Match

ROADM node name RE pattern to match.

String

OSS OMS Link Name RE Pattern to Match from OTS Link Names

OSS OMS link name RE pattern to match from OTS link names.

^(.*/.*/OMS/\d+)/.*$

String

Service type

Description of Limitation

Limitation Source

Comments

All

Any configuration change done directly in the WS-NOC (e.g ODU Trails mentioned below) must be synced manually with WS-RC to avoid inconsistent state. 

Controller

Use the following API to trigger sync
https://{{server}}:8443/tapi/sync/trigger-tapi-sync/

And the following to check the sync status
https://{{server}}:8443/tapi/sync/get-tapi-sync-status/

Note: One sign of out-of-sync situation is missing end points for ODU trails in the connectivity context response.

Circuit E-Line
OTN Line
SDH Line

Underlying ODU Trail cannot be created in HCO.  The user should create the trail using Controller UI/API

HCO

As the path optimization goals and constraints are applicable to the ODU trail and not the client service as such, these should be applied at the time of the trail creation.  And the use should select the appropriate trail with the required constraints when creating the client services.

Circuit E-Line

Service Capacity (Unsupported ETH Types)
- 10 GB WAN
- 200 GB

Controller

Adapter returns Validation Error:

Unsupported Eth Layer Protocol Qualifier <Eth_Type>

Circuit E-Line

Selection of Optimization Goal 'ADMIN COST' not allowed

Controller

Adapter returns Validation Error::

'Admin Cost' optimization goal is not supported for service creation request.

Circuit E-Line

Protection = 1 + Restoration not supported

Controller

Adapter returns Validation Error:

Protection Type 'Protection 1+Restoration' is not supported for CIRCUIT_E_LINE service creation.

Circuit E-Line

Include Node / Exclude Node / Exclude link / Disjoint Link not allowed

Controller / HCO

Controller requires ODU Trail reference in the create payload.  HCO using include link to select underlying ODU trail directly.

Adapter returns Validation Error:

Include nodes, exclude nodes or exclude links are not supported for CIRCUIT_E_LINE service creation.

Circuit E-Line

(Fix & Flex)

Only one primary include link allowed for ODU Fix or ODU Flex unprotected services

Controller / HCO

Controller requires ODU Trail reference in the create payload.  HCO uses include link to select underlying ODU trail directly.

Adapter returns Validation Error if no or more than one Include Link is provided or invalid link is provided:

CIRCUIT_E_LINE Service with 'NO_PROTECTION' should have only one ODU type include-link. Found '0' include-link(s).

   or

'Include' Resource of Layer '<Non-ODU>' is not supported. Only 'ODU link' inclusion is supported.

Circuit E-Line

(Fix & Flex)

Only one primary include link and one protected include link, with matching devices with selected endpoints, are allowed for ODU Fix or ODU Flex protected (1+1 and 1+1+R) services

Controller / HCO

Controller requires ODU Trail reference in the create payload.  HCO using include link to select underlying ODU trail directly.

Adapter returns Validation Error:

CIRCUIT_E_LINE Service with '<Protection Type>' should have 2 ODU type include-links. Found '<n>' include-link(s).

   or

Only 1 valid include link is supported for 'CIRCUIT_E_LINE' service request with Protection Role 'PROTECTION_PRIMARY'.

   or

'Include' Resource Link's ports are from different device(s) than that of selected endpoints' ports.

Circuit E-Line

No restoration links are allowed

Controller

Adapter returns Validation Error:

Service Intent 'Include' Resource with Protection Role 'PROTECTION_RESTORATION' is not supported.

Circuit E-Line (Flex)

BW modification not allowed for ODU Flex Protected services

Controller

     Adapter returns Validation Error:

Service modification is not supported for protected services.

Circuit E-Line (Flex)

BW modification not allowed for ODU Flex Unprotected services that are operationally down

Controller

Adapter returns Validation Error:

Cannot modify Service with UUID {service_uuid} - not in Active state.

Circuit E-Line (Flex)

Non-TAPI parameter 'ASON_ROUTED' must be set to TRUE when provisioning Flex Services for devices which are on Control / Management Plane.  There is no way to automatically determine when this property must be set.

Controller

This parameter can be set via templates, but the user should know when to enable or disable the template as required.

OCH NC (Alien WL)

Selection of Auto Regeneration is not allowed.

Controller

Adapter returns validation error if the check box is 'checked':

"Allow Auto Regeneration" must be unchecked for OCH-NC Link request.

OCH NC (Alien WL)

Selection of Optical Feasibility Threshold is not allowed.

Controller

Adapter returns validation error if any other value is selected:

"Optical Feasibility Threshold" must be None for OCH-NC Link request.

OCH NC (Alien WL)

Selection of Central Frequency is not allowed.

Controller

VF said this parameter is not used in their workflow.

Adapter returns validation error if any value is provided:

Central Frequency (Thz) must be empty for OCH-NC Link request.

OCH NC (Alien WL)

Selection of more than 2 endpoints through ‘Multiple Channel’ is not allowed

Controller

Adapter returns validation error if more than 2 endpoints are added through the selection of ‘Multiple Channel’:

OCH-NC Link request must have exactly 2 endpoints.

OCH NC (Alien WL)

Selection of Optimization Goal 'ADMIN COST' is not allowed

Controller

Adapter returns validation error:

'Admin Cost' optimization goal is not supported for service creation request.

OCH NC (Alien WL)

Exclude Node is not allowed

Controller

Adapter returns validation error:

Exclude nodes are not supported for OCH-NC Link

OCH NC (Alien WL)

Non-TAPI parameters 'WAVE_KEY' and 'WAVE_KEY_TYPE’ must be set when provisioning WL Services

Controller

These parameters can be set via templates.

OTN Line

Service Capacity (Unsupported ODU Types)
- ODU3E2
- ODUC2
- ODUC4
- ODUC5
- ODUC6
- ODUC7
- ODUC8

Controller

Adapter returns validation error for unsupported Service Capacity (odu_type):

'<odu_type>' is not supported for OTN_LINE service creation

OTN Line

ODU Flex is not supported

Controller

Adapter returns validation error for unsupported Service Capacity (ODU Flex):

'ODU_FLEX' is not supported for OTN_LINE service creation

OTN Line

Protection “1 + Restoration” is not supported

Controller

Adapter returns Validation Error:

Protection Type 'Protection 1+Restoration' is not supported for OTN_LINE service creation.

OTN Line

Selection of Optimization Goal 'ADMIN COST' is not allowed

Controller

Adapter returns Validation Error:

'Admin Cost' optimization goal is not supported for service creation request.

OTN Line

Include Node / Exclude link / Disjoint link is not allowed

Controller / HCO

Controller requires ODU Trail reference in the create payload.  HCO uses include link to select underlying ODU trail directly.

Adapter returns validation error for other data:

Include nodes, exclude nodes or exclude links are not supported for OTN_LINE service creation.

OTN Line

Exclude Node not allowed

Controller

Same as above

OTN Line

Only one Include Link allowed for unprotected services

Controller / HCO

Controller requires ODU Trail reference in the create payload.  HCO uses include link to select underlying ODU trail directly.

Adapter returns Validation Error if no or more than one Include Link is provided or invalid link is provided:

OTN_LINE Service with 'NO_PROTECTION' should have only one ODU type include-link. Found '0' include-link(s).

   or

'Include' Resource of Layer '<Non-ODU>' is not supported. Only 'ODU link' inclusion is supported.

OTN Line

Only one primary Include Link and one protected include link, with matching devices with selected endpoints, are allowed for protected (1+1 and 1+1+R) services

Controller / HCO

Controller requires ODU Trail reference in the create payload.  HCO using include link to select underlying ODU trail directly.

Adapter returns Validation Error:

OTN_LINE Service with '<Protection Type>' should have 2 ODU type include-links. Found '<n>' include-link(s).

   or

Only 1 valid include link is supported for ‘OTN_LINE' service request with Protection Role 'PROTECTION_PRIMARY'.

   or

'Include' Resource Link's ports are from different device(s) than that of selected endpoints' ports.

OTN Line

No restoration links are allowed

Controller

Adapter returns Validation Error:

Service Intent 'Include' Resource with Protection Role 'PROTECTION_RESTORATION' is not supported.

SDH Line

Service Capacity (Unsupported STM Types)
- STM0
- STM3
- STM6
- STM8
- STM12
- STS<n>

Controller

Adapter returns validation error for unsupported Service Capacity (stm_type):

Unsupported SDH Layer Protocol Qualifier <stm_type>

SDH Line

Selection of Optimization Goal 'ADMIN COST' not allowed

Controller

Adapter returns Validation Error:

'Admin Cost' optimization goal is not supported for service creation request

SDH Line

Include Node / Exclude Node / Exclude link / Disjoint link not allowed

Controller / HCO

Controller requires ODU Trail reference in the create payload.  HCO using include link to select underlying ODU trail directly.

Adapter returns validation error for other data:

Include nodes, exclude nodes or exclude links are not supported for SDH_LINE service creation.

SDH Line

Only one Include Link allowed for unprotected services

Controller / HCO

Controller requires ODU Trail reference in the create payload.  HCO uses include link to select underlying ODU trail directly.

Adapter returns Validation Error if no or more than one Include Link is provided or invalid link is provided:

SDH_LINE Service with 'NO_PROTECTION' should have only one ODU type include-link. Found '0' include-link(s).

   or

'Include' Resource of Layer '<Non-ODU>' is not supported. Only 'ODU link' inclusion is supported.

SDH Line

Only two primary include links, with matching devices with selected endpoints, are allowed for protected services

Controller / HCO

Controller requires ODU Trail reference in the create payload.  HCO using include link to select underlying ODU trail directly.

Adapter returns Validation Error:

SDH_LINE Service with '<Protection Type>' should have 2 ODU type include-links. Found '<n>' include-link(s).

   or

'Include' Resource Link's ports are from different device(s) than that of selected endpoints' ports.