blob: ff90b006cf6a7f374e0d515be4a06ea0b47ac531 [file] [log] [blame]
Matteo Scandoloa6a3aee2019-11-26 13:30:14 -07001/*
2 * Copyright (c) 2018 - present. Boling Consulting Solutions (bcsw.net)
3 *
4 * Licensed under the Apache License, Version 2.0 (the "License");
5 * you may not use this file except in compliance with the License.
6 * You may obtain a copy of the License at
7 * http://www.apache.org/licenses/LICENSE-2.0
8 * Unless required by applicable law or agreed to in writing, software
9 * distributed under the License is distributed on an "AS IS" BASIS,
10 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
11 * See the License for the specific language governing permissions and
12 * limitations under the License.
13 */
14/*
15 * NOTE: This file was generated, manual edits will be overwritten!
16 *
17 * Generated by 'goCodeGenerator.py':
18 * https://github.com/cboling/OMCI-parser/README.md
19 */
20package generated
21
22import "github.com/deckarep/golang-set"
23
24const SoftwareImageClassId ClassID = ClassID(7)
25
26var softwareimageBME *ManagedEntityDefinition
27
28// SoftwareImage (class ID #7)
29// This ME models an executable software image stored in the ONU (documented here as its
30// fundamental usage). It may also be used to represent an opaque vendor-specific file
31// (vendorspecific usage).
32//
33// Fundamental usage
34//
35// The ONU automatically creates two instances of this ME upon the creation of each ME that
36// contains independently manageable software, either the ONU itself or an individual circuit pack.
37// It populates ME attributes according to data within the ONU or the circuit pack.
38//
39// Some pluggable equipment may not contain software. Others may contain software that is
40// intrinsically bound to the ONU's own software image. No software image ME need exist for such
41// equipment, though it may be convenient for the ONU to create them to support software version
42// audit from the OLT. In this case, the dependent MEs would support only the get action.
43//
44// A slot may contain various equipment over its lifetime, and if software image MEs exist, the ONU
45// must automatically create and delete them as the equipped configuration changes. The identity of
46// the software image is tied to the cardholder.
47//
48// When an ONU controller packs are duplicated, each can be expected to contain two software image
49// MEs, managed through reference to the individual controller packs themselves. When this occurs,
50// the ONU should not have a global pair of software images MEs (instance 0), since an action
51// (download, activate, commit) directed to instance 0 would be ambiguous.
52//
53// Relationships
54// Two instances of the software image ME are associated with each instance of the ONU or
55// cardholder whose software is independently managed.
56//
57// Attributes
58// Managed Entity Id
59// Managed entity ID: This attribute uniquely identifies each instance of this ME. The first byte
60// indicates the physical location of the equipment hosting the software image, either the ONU (0)
61// or a cardholder (1..254). The second byte distinguishes between the two software image ME
62// instances (0..1). (R) (mandatory) (2 bytes)
63//
64// Version
65// Version: This string attribute identifies the version of the software. (R) (mandatory)
66// (14 bytes)
67//
68// Is Committed
69// Is committed: This attribute indicates whether the associated software image is committed (1) or
70// uncommitted (0). By definition, the committed software image is loaded and executed upon reboot
71// of the ONU or circuit pack. During normal operation, one software image is always committed,
72// while the other is uncommitted. Under no circumstances are both software images allowed to be
73// committed at the same time. On the other hand, both software images could be uncommitted at the
74// same time if both were invalid. Upon ME instantiation, instance 0 is initialized to committed,
75// while instance 1 is initialized to uncommitted (i.e., the ONU ships from the factory with image
76// 0 committed). (R) (mandatory) (1 byte)
77//
78// Is Active
79// Is active: This attribute indicates whether the associated software image is active (1) or
80// inactive (0). By definition, the active software image is one that is currently loaded and
81// executing in the ONU or circuit pack. Under normal operation, one software image is always
82// active while the other is inactive. Under no circumstances are both software images allowed to
83// be active at the same time. On the other hand, both software images could be inactive at the
84// same time if both were invalid. (R) (mandatory) (1 byte)
85//
86// Is Valid
87// Is valid: This attribute indicates whether the associated software image is valid (1) or invalid
88// (0). By definition, a software image is valid if it has been verified to be an executable code
89// image. The verification mechanism is not subject to standardization; however, it should include
90// at least a data integrity check [e.g., a cyclic redundancy check (CRC)] of the entire code
91// image. Upon ME instantiation or software download completion, the ONU validates the associated
92// code image and sets this attribute according to the result. (R) (mandatory) (1 byte)
93//
94// Product Code
95// Product code: This attribute provides a way for a vendor to indicate product code information on
96// a file. It is a character string, padded with trailing nulls if it is shorter than 25 bytes. (R)
97// (optional) (25 bytes)
98//
99// Image Hash
100// Image hash: This attribute is an MD5 hash of the software image. It is computed at completion of
101// the end download action. (R) (optional) (16 bytes)
102//
103type SoftwareImage struct {
104 ManagedEntityDefinition
105 Attributes AttributeValueMap
106}
107
108func init() {
109 softwareimageBME = &ManagedEntityDefinition{
110 Name: "SoftwareImage",
111 ClassID: 7,
112 MessageTypes: mapset.NewSetWith(
113 ActivateSoftware,
114 CommitSoftware,
115 DownloadSection,
116 EndSoftwareDownload,
117 Get,
118 StartSoftwareDownload,
119 ),
120 AllowedAttributeMask: 0XFC00,
121 AttributeDefinitions: AttributeDefinitionMap{
122 0: Uint16Field("ManagedEntityId", 0, mapset.NewSetWith(Read), false, false, false, false, 0),
123 1: MultiByteField("Version", 14, nil, mapset.NewSetWith(Read), true, false, false, false, 1),
124 2: ByteField("IsCommitted", 0, mapset.NewSetWith(Read), true, false, false, false, 2),
125 3: ByteField("IsActive", 0, mapset.NewSetWith(Read), true, false, false, false, 3),
126 4: ByteField("IsValid", 0, mapset.NewSetWith(Read), true, false, false, false, 4),
127 5: MultiByteField("ProductCode", 25, nil, mapset.NewSetWith(Read), true, false, true, false, 5),
128 6: MultiByteField("ImageHash", 16, nil, mapset.NewSetWith(Read), true, false, true, false, 6),
129 },
130 }
131}
132
133// NewSoftwareImage (class ID 7 creates the basic
134// Managed Entity definition that is used to validate an ME of this type that
135// is received from the wire, about to be sent on the wire.
136func NewSoftwareImage(params ...ParamData) (*ManagedEntity, OmciErrors) {
137 return NewManagedEntity(softwareimageBME, params...)
138}