Equipment/Interface and Alarm-Severity-Assignment
If the user provisions resource (equipment/interface) and alarm-severity-assignment at single commit, the
operaon fails. The user needs to provision resource and commit the resource rst, and the user needs to
provision alarm-severity-assignment.
Port-Connecon Direcon
If the user saves the conguraon le in the current release, user deletes the port-connecon <direcon></
direcon> from the conguraon le before execung the load replace command. The direcon eld is
moved to operaon side in the next release.
Example:
<port-connection xmlns="urn:fujitsu:params:xml:ns:yang:eqpt:fcon">
<connection-id>PORT-ADD</connection-id>
<src-shelf>2</src-shelf>
<src-slot>1</src-slot>
<src-subslot>0</src-subslot>
<src-port>E1</src-port>
<dst-shelf>1</dst-shelf>
<dst-slot>0</dst-slot>
<dst-subslot>0</dst-subslot>
<dst-port>C1</dst-port>
<mode>normal</mode>
<direction>UNI</direction> #direction need to be deleted
</port-connection>
Fabric Connecon
When the user does a load replace on an exisng fabric with changes in aributes like xcon-id, src-id, dst-if, and
dst-och, the validaon fails if the xcon-id is not alphabecally bigger than the xcon-id being replaced.
For example, consider a fabric connecon with values (xcon-id=ABC, src-if=A, dst-if=B) is already provisioned in
the database.
The following commands fail validaon at commit because the dst-if is changed to C.
Commands:
% delete fabric och-connection ABC
% set fabric och-connection ABC src-if A dst-if C
% commit
The following commands are another failure example of which the user only changes the xcon-id.
Commands:
% delete fabric och-connection ABCDEF
% set fabric och-connection ABC src-if A dst-if B
% commit
Load
Conguration Operation
Limitations on Load Conguration
456
Release 19.1.1 · Issue 1.1, May 2021
Fujitsu and Fujitsu Customer Use Only
To Next Page
Loading...
Need help?
General