...
Note: The PNF is the master of its IP address and would over-write the IP address in the PNF A&AI entry with the one provided in the VES event.
PNP-4605 [DUBLIN][PRH] - The PRH shall enter the following information into the A&AI entry for the PNF extracting the corresponding information from the incoming pnfRegistration VES message.
| A&AI PNF ENTRY | BASED ON pnfREGISTRATION VES FIELD |
|---|---|
| serial-number | serialNumber |
| equip-vendor | vendorName |
| equip-model | modelNumber |
| equip-type | unitType |
| pnf-name | sourceName |
| pnf-id | |
| ipaddress-v4-oam | oamV4IpAddress |
| ipaddress-v6-oam | oamV6IpAddress |
| software_versions | software_versions [1] { softwareVersion (from pnfRegistration) activeSw = "True" } |
PNP-4610 [PRH] – If the PRH encounters a situation that there is a PNF entry in A&AI (without IP address), but the VES event itself does not have an PNF IP address it shall log the error. Note: if the PNF does not send its IP address in the VES event this could be from a variety of reasons from a software error to a communication failure.
...
PNP-5145 Role Assignments [FUTUREDUBLIN][DCAE] - This is no longer needed because the PNF Registration (YML) will serve as a mechanism to "authorize" the PNF. i.e. DCAE knows that it is expecting a VES event from this those PNF types.
...