After CONNECT to a NETCONF device registered specific devicemanager factories are starting one specific devicemanager.
The startup decision is taken by provided NETCONF capabilities. First matching factory is accepted.
Abstraction by data-provider YANG spec "urn:opendaylight:params:xml:ns:yang:data-provider", 2019-08-01
Legend
- Featurecode:
- A: Interfacing with ONAP AAI
- D: Devicesupervision (NetConf Connection supervision)
- F: Fault management (via NETCONF)
- I: Inventory management
- N: NETCONF notification (including create-subscription)
- P: Performance management
- V: Forward NETCONF notification to VES
Devicetype: NetworkElementDeviceType in data-provider yang spec (Issue data-provider Herbert creats)
- NTS Simulated device name: the name of the simulated device to be used within the NTS Framework when simulating such a device type
- Color coding:
- white: Frankfurt, available
- yellow: ONAP Guilin
- blue: O-RAN-SC Cherry
- purple: Guilin (open)
- green: Not published because of open yang license issue
| if condition true selects devicemanager | data-provider-type | Featurecode | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Devicemanager- | Subtype | Condition "capability list contains .." | Devicetype | NTS Simulated device name | A | D | F | I | N | P | V |
| no match | Unknown | N/A | |||||||||
| onf | Base | "urn:onf:params:xml:ns:yang:core-model", "2017-03-20" | Optical | N/A | x | x | x | ||||
| Microwave | "urn:onf:params:xml:ns:yang:core-model", "2017-03-20" and one of
| Wireless | hightec/ntsim_onf_core_model_1_2 | x | x | x | x | x | x | ||
| gran | "urn:3gpp:tsg:sa5:nrm:Top", all revisions | RAN3GPP | hightec/ntsim_3gpp | ||||||||
oran | ORanNe | "urn:o-ran:hardware:1.0", all revisions | O-RAN-FH | hightec/ntsim_oran | x | ||||||
| NtsNe | "urn:onf:params:xml:ns:yang:network-topology-simulator", all revisions | NtsManager | hightec/ntsim_manager | ||||||||
| onf | Base | "urn:onf:params:xml:ns:yang:core-model", "2017-03-20" | Optical | N/A | x | x | x | ||||
| Microwave | "urn:onf:params:xml:ns:yang:core-model", "2017-03-20" and one of
| Wireless | hightec/ntsim_onf_core_model_1_2 | x | x | x | x | x | x | ||
| openroadm | Optical | OrgOpenroadmDevice.QNAME, all revisions | O-ROADM | hightec/ntsim_openroadm_device | x | x | x | x | |||
| onf14 | IP/Microwave/Optical | "urn:onf:yang:core-model-1-4", all revisions | Wireless | hightec/ntsim_onf_core_model_1_4 | x | x | x | x | x | x | |
| adapter-manager | NtsManager | "urn:onf:params:xml:ns:yang:network-topology-simulator", all revisions | NtsManager | hightec/ntsim_manager | |||||||
o-ran/ru-fh | ORanNe | "urn:o-ran:hardware:1.0", all revisions | O-RAN-FH | hightec/ntsim_oran | x | ||||||
| x-ran/ru-fh | XRanNe | ?? | xRAN | ||||||||
| gran | "urn:3gpp:tsg:sa5:nrm:Top", all revisions | RAN3GPP | x | ||||||||
| tr069 | "urn:org:onap:ccsdk:features:sdnr:northbound:onecell-notification"; all revisions | O1-TR069 | x | x | |||||||
| oran-o1 | Base | "urn:3gpp:tsg:sa5:nrm:Top", all revisions | O-RAN | N/A | |||||||
| NearRtRic | x | x | |||||||||
| ORanOCuUp | x | x | |||||||||
| ORanOCuUp | x | x | |||||||||
| ORanODu | x | x | x | ||||||||
| ORanORu | x | x | x | ||||||||
| adapter-manager | NtsManager | "urn:onf:params:xml:ns:yang:network-topology-simulator", all revisions | NtsManager | hightec/ntsim_manager | |||||||
| ManagerCore12 | (ONF mediators) | ONFCore12Manager | |||||||||
| ManagerDraftO1 | |||||||||||
| DraftO1 | |||||||||||
| default | "urn:ietf:params:xml:ns:netconf:notification:1.0", all revision | N/A | x | ||||||||
| "urn:ietf:params:xml:ns:yang:ietf-alarms", all revision | x | ||||||||||
| "urn:ietf:params:xml:ns:yang:ietf-hardware", all revision | x | ||||||||||
3 Comments
Vishal Varvate
will the FM(below feature code) provides fault correlation support as well.
Ravi Pendurty
Fault correlation is not supported. Only current alarms (alarms already existing in the network) and alarm notifications are supported. Correlation has to be implemented separately.
Vishal Varvate
Thank you Ravi Pendurty for your reply.
Also can you please let us know that what will be the future plan for implementing alarm correlation , is it the SDNR itself or Holmes will be used for it?