Open Transport Configuration & Control
Space shortcuts
Expand all   Collapse all
Child pages
  • 2020-04-15 5G-xHaul Meeting notes
Skip to end of metadata
Go to start of metadata

Date

| 2am PDT | 5am EDT | 9:00 UTC | 11:00 CEST | 12:00 EEST | 14:30 IST | 17:00 CST | 18:00 JST |

https://onf.zoom.us/j/853336915

Attendees

(please feel free to correct, update your names (wink) Thank you very much!!!) 

Info to: 

Goals

  • going forward

Discussion items

TimeItemWhoNotes
00:00chair topic 
no update 

00:00

Admin

Next meetings

2020-04-15: Martin Skorupski

2020-04-22: Martin Skorupski

2020-04-29: Martin Skorupski

2020-05-06: Martin Skorupski

00:05

Thorsten Heinze

Proposal for harmonized error-tags and error-messages

(follow link to see the email)

Decision #1: Use  error-tag "operation-failed" for referenced failures:

  • Attribute/feature is not supported by the hardware
  • Configuration value out of range of hardware capabilities
  • Configuration value contradicts existing configuration
  • Configuration values (entire container) not consistent


Decision #2: Add additonal information about root cause of the configuration failure to be added to the NetConf Error-message  - Please object until 2020-04-22

Decision #3: Due to different implementations and software layers a start and end tag of the additional information. 

Format: #[onf:ERROR_TEXT]#

  • StartTag: "#[onf:"
  • EndTag: "]#"


Decision #4:

ERROR_TEXT - as proposed in the referenced email

  • Failure:
    • Attribute/feature is not supported by the hardware
    • ERROR_TEXT
      • "Attribute/feature not supported by the hardware."
  • Failure: 
    • Configuration value out of range of hardware capabilities
    • ERROR_TEXT
      • "Configuration value out of range of hardware capabilities."
  • Failure:
    • Configuration value contradicts existing configuration
    • ERROR_TEXT
      • "Wished change contradicts existing configuration."
  • Failure:
    • Configuration values (entire container) not consistent
    • ERROR_TEXT
      • "Wished changes are not consistent."






Thorsten Heinze

Proposal to replace maxQueueDepth by availableQueueDepthList

(follow link to see the email)

Goes to the agenda of next week



Thorsten Heinze

Proposal to align modeling of AirEquipment with WireEquipment

(follow link to see the email)

Goes to the agenda of next week



Thorsten Heinze

How to generate an alarm on the EthernetContainer

(follow link to see the email)

Goes to the agenda of next week





0minUUID

core-model allows definition of both Logical Termination Points (interfaces), but also connections

  • Forwarding Domain:
    • either connections inside the same device
    • connections outside devices
  • Link:
    • any type of link, not only microwave
  • Forwarding Construct:
    • concrete forwarding between two or more LTPs / ports
      • unidirectional / bidirectional

core-model is also suitable for representing entire Networks, not only a Device

this means that Universally Unique IDs are required

Devices cannot get the UUIDs from outside, they need to be generated by the device, and cannot be overwritten from outside

Devices are unaware by their surroundings (the network), so it cannot know if a UUID is already used by some other interface in other devices

IETF defines how to create UUIDs, and the core-model references this RFC

  • we need UUIDs for documenting the network
  • we cannot write the UUIDs in the device, the device needs to create it 
  • the device does not have a network wide view
  • this is needed because of the Planning the network

Possible solutions:

  • the device generates whatever, the IDs are retrieved and a mapping table is maintained
  • we prescribe a method/algorithm that is implemented in the device for creating UUIDs (which become predictable):
    • using some prefix which is known during the implementation time of the device - (e.g. MAC address of the Management interface); vendor sends info about Order no. and MAC addr. to the operator and the Planning will be done with these prefixed values → less complex than a field technician configuring the prefix on the device with some dongle
    • fixed UUID with prefix and postfix

Suggestions:

  • use the Device name instead of the MAC addr.
  • clean-up application that handles the changing of MAC addresses

Out of time, we need to follow up: proposal, next week Tuesday 09:00 CET

--

Notes from  

Discussion about UUID and Links/Asszosations/References between object classes

ODL MountPoint is and association to a NetConf server - some NetConf servers representing some times the microwave model.


Action items