Nokia NRC-T Adapter
Controller name: NRC-T Adapter
Vendor: Nokia
Controller version: R22.6
HCO version: 10.0
Adapter version:
Adapter release date:
· Inventory discovery - Yes
· Topology discovery - Yes
· Service underlay discovery (LSP, tunnels) - No
· Service discovery - Yes
· Assurance - Yes
· Service provisioning – No
· RON - No
|
Details |
Support |
Additional Information |
|
Device types |
1830PSS-PHN 1830PSIM |
|
|
Shelf |
Yes |
|
|
Cards |
Yes |
|
|
Ports |
Yes |
|
|
Fans |
Yes |
|
|
Power |
No |
|
|
Pluggable transceivers |
Yes |
|
|
Notifications |
Yes |
|
|
Protocol |
TAPI |
|
|
Data Model |
JSON |
|
|
Limitations |
|
|
|
Notifications |
|
If there is any exception happened during notification processing, HCO will go for full polling as a fallback mechanism. |
|
Details |
Support |
Additional Information |
|
Link layers |
OTS, OMS, OCH, OTU, ODU, ETH, OC |
OCH Links extra field was updated to include info on protection-type restoration-policy and reversion-mode(Path restoration bits)data. |
|
Cross links |
Yes |
|
|
Cross domain links |
No |
|
|
Notifications |
Yes |
|
|
Protocol |
TAPI |
|
|
Data Model |
JSON |
|
|
Details |
Support |
Additional Information |
|
Link layers |
No |
|
|
Cross domain links |
No |
|
|
Notifications |
No |
|
|
Protocol |
NA |
|
|
Data Model |
NA |
|
|
Details |
Support |
Additional Information |
|
Service types |
No |
|
|
Service underlay |
No |
|
|
Cross domain services |
No |
|
|
Notifications |
No |
|
|
Protocol |
NA |
|
|
Data Model |
NA |
|
|
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 |
|
Protocol |
NA |
|
|
|
Data Model |
NA |
|
|
|
Limitations |
|||
|
<service type> |
Monitoring operations are not supported. |
||
The
following list comprises APIs utilized by the Nokia NRC-T adapter.
|
Discovery Type |
Item |
HTTP Requests |
HTTP Method |
|
Authentication |
Token |
/rest-gateway/rest/api/v1/auth/token/ |
POST |
|
Inventory |
ONE, Shelf, Card, Port, Fan,
Transceivers, Links (OTS, OMS), Connections
(OCH, OTU, ODU, ETH) |
/tapi/data/tapi-common:context/ |
GET |
|
LLDP/All Physical Ports |
/oms1350/data/otn/networkinventory/allphysicalports |
GET |
|
|
LLDP/GET All Physical Ports
JSON |
/data_report/data_extraction/npt/inventory/allphysicalports/physicalports.json |
GET |
|
|
Notification |
Get subscription uuid |
/tapi/data/tapi-common:context/tapi-notification:notification-context/notif-subscription/ |
POST |
|
Establish subscription channel |
/tapi/data/context/notification-context/notif-subscription/sse/{uuid} |
GET |
|
|
Delete subscription uuid |
/tapi/data/tapi-common:context/tapi-notification:notification-context/notif-subscription={uuid}/ |
DELETE |
|
|
Notification Endpoints |
DEVICE_ACCESS_PORT |
/tapi/data/tapi-common:context/tapi-equipment:physical-context/device={device-uuid]/access-port={uuid} |
GET |
|
DEVICE_EQUIPMENT |
/tapi/data/tapi-common:context/tapi-equipment:physical-context/device={device-uuid}/equipment={uuid}/ |
GET |
|
|
DEVICE |
/tapi/data/tapi-common:context/tapi-equipment:physical-context/device={uuid}/ |
GET |
|
|
CONNECTIVITY_CONNECTION |
/tapi/data/tapi-common:context/tapi-connectivity:connectivity-context/connection={uuid}/ |
GET |
|
|
CONNECTIVITY_SERVICE |
/tapi/data/tapi-common:context/tapi-connectivity:connectivity-context/connectivity-service={uuid}/ |
GET |
|
|
|
NODE_NEP |
/tapi/data/tapi-common:context/tapi-topology:topology-context/topology={uuid}/node={uuid}//owned-node-edge-point={uuid}/ |
GET |
|
|
TOPOLOGY_LINK |
/tapi/data/tapi-common:context/tapi-topology:topology-context/topology={uuid}/link={uuid}/ |
GET |
|
|
TOPOLOGY_NODE |
/tapi/data/tapi-common:context/tapi-topology:topology-context/topology={uuid}/node={uuid}/ |
GET |
|
Stats |
Get PMs |
sftp://<SFTP server
IP> /*.csv |
SFTP PULL |
Configuration Parameters for the Nokia NCR-T Adapter.
|
Name |
Description |
Default |
Range/Note |
|
Adapter Properties |
|
|
|
|
Enabled |
Enable/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 resets 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 not. 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. |
|
|
|
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 |