The administrative state of blades/blade systems. Reflects what the administrator has done. The operational state of blades/blade systems. Reflects if the entity is on/off. The availability state of blades/blade systems. Reflects if the entity is useable or not. The bus type used by a blade. Parent of all blade systems. This class describes a Blade System. It serves as a mountpoint for the blade system specific model. A user friendly Blade System name, must be set at creation and can be changed when BS is locked. An identifier for the BS. A new integer has to be used every time a new BS is created. The identity of the Software Group (SWG) that the BS implements. The revision of the Software Group (SWG) that the BS implements. The identity of the correction package (CXR) applied to the SWG. The revision of the correction package (CXR) applied to the SWG The administrative state of the Blade System. The operational state of the Blade System. The availability status of the Blade System. The identity of the Blade System domain the Blade system belongs to. IP address of the Blade System OaM Master. Locks the blade system. If the system already is locked the action does nothing. Unlocks the blade system. If the system already is unlocked the action does nothing. This operation orders the blade system to be unlocked. However the blade system may not be unlocked even if this order works. See the operational state to figure out if the unlock succeded. Shuts down the blade system. If the system already is locked the action does nothing. Action to create a backup file from the current Blade System. It is stored locally on disk. An instance of the MO class Software/Jobs/Backup/Create is created as a log of this action. A user specified backup creation job name Action to restore a backup into the current Blade System. It is fetched from the local disk. An instance of the MO class Software/Jobs/Backup/Restore is created as a log of this action. The IS site local backup identity A user specified backup restore job name Action to upgrade the current Blade System. Files are fetched from the local disk storage. An instance of the MO class Software/Jobs/Upgrade is created as a log of this action. A user specified ugrade job name The Ericsson product number of blade system software group The Ericsson revision of blade system software group The Ericsson product number of software correction package The Ericsson revision of software correction package The Ericsson product number of blade software group The Ericsson revision of blade software group The maximum time allowed to finish the entire software change procedure (minutes). Default value depends on blade system software. This class describes a Blade. A Blade is identified by the subrack and slot number. A reference to the associated subrack (i.e. the value of 'subrackId' for the associated subrack) 031 The slot number for this Blade within the subrack. 025 The slot label of the blade. Will only be set at creation. This should be used in alarms related to the slot to inform the operator of what position in the subrack the blade is located in. E.g. for GEM subracks it will be a string like X02 for slot 0 up to X80 for slot 25. An identifier for the BS to which the blade belongs. A value of 0 means that the blade is inserted in the subrack but it has not been configured to any BS yet. The type of the Blade defined by a string BladeTypeId. The expectedregistered SW group id of the Blade. The registered SW group revision state of the Blade. The installed SW group id of the Blade. The installed SW group revision state of the Blade. Indicates if this blade is a BSOM candidate. Set to protected if blade sholud no be knocked out before the switch blade. A user friendly Blade name, always possible to set. Default value indicates HwmBladeType and used slot. The administrative state of the Blade. The operational state of the Blade. The availability status of the Blade. The type of maintenance bus on the found Blade The Product Number of the found Blade The Product Revision of the found Blade. The Serial Number of the found Blade. The Product Name of the found Blade. The Vendor name of the found Blade. The manufacturing date of the found Blade. The aggregated MAC address of the found Blade. The left link MAC address of the found Blade. Only used by some blades The right link MAC address of the found Blade. Only used by some blades The date when the blade was last changed. IP address on the ISBS subnet. IP address on the ISOB subnet. IP address on the ISLCT subnet. Locks the blade. If the blade already is locked the action does nothing. This operation orders the blade to be locked. It may however take long time before it happens. Unlocks the blade. If the blade already is unlocked the action does nothing. This operation orders the blade to be unlocked. However the blade may not be unlocked even if this order works. See the operational state to figure out if the unlock succeded. Shuts down the blade. If the blade already is locked the action does nothing. Action to upgrade the current blade. Files are fetched from the local disk storage. An instance of the MO class Software/Jobs/Upgrade is created as a log of this action. A Blade may have one or more resilient interfaces to the backplane. Such an interface is called a Link Service Access Point (LSAP), which is the point where you access layer 2. LSAPs are automatically created and deleted along with the hosting blade. The id of a LinkSap is a number from 0 to X within the slot. The MO branch where the Blade System specific Network resources are mapped to blade system network requirements to common Integrated Site resources. This activity must be performed before a new blade or blade system successfully can be unlocked via the Hardware service. Some blade system designers have partly pre-registered their network requirements, while others demand that you read the corresponding information from separate Operation Procedure Instructions and manually register the blade system network requirements. The pre-registered network requirements automates parts of the blade system-specific configuration activity. In an Integrated Site, the blade systems obtain their actual network configuration dynamically in runtime. When you change the network configuration it will affect blade systems. In order to minimize the disturbance of active blade systems, the changes are normally applied in a separate storage which not is visible to the blade systems. In order to make use of the new unpublished configuration, it must explicitly be published by altering the updateMode. If the new settings introduces severe problems the configuration can be reverted to the old settings by altering the updateMode. The common Network configuration including updateMode and its publish mechanism is specified in a separate MIM called CPD MIM. A BS VLAN is mapped to one IS VLAN. A BS VLAN is the requirement a Blade System have of an IS VLAN. Different instances of a Blade System type may call their BS VLANs the same thing but in the end the IS Site Designer can choose to map them to the same or different IS VLAN. BS VLANs can either be created manually by the operator or they can be automatically created from pre-registered network requirements bundled with the Blade System software. Regardless of how they are created, each one needs to be mapped to an IS VLAN before the blades can be unlocked. The mapping is done with the 'isVlanRef' attribute. Different instances of a Blade System type may call their BS VLANs the same thing but in the end the IS Site Designer can choose to map them to the same or different IS VLAN. Name of the BS VLAN. It is unique within the Blade System. Short description of the BS VLAN. Setting the private attribute to true, means that the corresponding IS VLAN not can be used by other Blade Systems. The IS VLAN is private for this particular Blade System. The mapping to a corresponding IS VLAN. This mapping must be done before the blades of the Blade System can be unlocked. A BS Logical Network (BSLN) is associated to one IS Logical Network. A BS Logical Network is the requirement a Blade Systems have of an IS Logical Network. BS Logical Networks can either be created manually by the operator or they can be automatically created from pre-registered network requirements bundled with the Blade System software. Regardless of how they are created, each one needs to be mapped to an IS Logical Network before the blades can be unlocked. The mapping is done with the 'isLogicalNetworkRef' attribute. Different instances of a Blade System type may call their BS Logical Networks the same thing but in the end the IS Site Designer can choose to map them to the same or different IS Logical Network. Name of the BS logical network. It is unique within the Blade System. Short description of the BS Logical Network. Flag that shows whether the BS Logical Network is private for this Blade System or if it may be shared among several Blade Systems. Reference to the corresponding IS Logical Network. A BS Subnet (BSSN) is associated to one IS Subnet. A BS Subnet Network is the requirement a Blade Systems have of an IS Subnet. BS Subnets can either be created manually by the operator or they can be automatically created from pre-registered network requirements bundled with the Blade System software. Regardless of how they are created, each one needs to be mapped to both a BS VLan and an IS Subnet before blades can be unlocked via the Hardware service. Each BS Subnet contains one or more BS Subnet Segments. The mappings are done with the 'bsVlanRef' and 'isSubnetRef' attributes. Different instances of a Blade System type may call their BS Subnets the same thing but in the end the IS Site Designer can choose to map them to the same or different IS Subnet. Name of the BS Subnet. It is unique within the BS Logical Network. Short description of the BS Subnet. default The mapping to a corresponding BS Vlan. This mapping must be done before the blades of the Blade System can be unlocked. The mapping to a corresponding IS Subnet. This mapping must be done before the blades of the Blade System can be unlocked. A BS Subnet Segment (BSSNS) is associated to one IS Subnet Segment. A BS Subnet Segment is the requirement a Blade Systems have of an IS Subnet Segment. BS Subnet Segments can either be created manually by you or they can be automatically created from pre-registered network requirements bundled with the Blade System software. Regardless of how they are created, each one needs to be mapped to an IS Subnet Segment before the blades can be unlocked via the Hardware service. The mapping is done with the 'isSubnetSegmentRef' attribute. Different instances of a Blade System type may call their BS Subnet Segments the same thing but in the end the IS Site Designer can choose to map them to the same or different IS Subnet Segment. Name of the BS Subnet Segment. It is unique within the BS Subnet. Short description of the BS Subnet Segment. Number of required IP addresses in the IS Subnet Segment. Flag that controls whether the corresponding IS Subnet Segment is required to have DHCP enabled or not. Flag that controls whether the corresponding IS Subnet Segment is required to have a router configured or not. The mapping to a corresponding IS Subnet Segment. The mapping here must be done before the blades of the blade system can be unlocked. There is a BS VLAN Service Access Point (BSVSAP) for each Link Service Access Point that an IS VLAN straddles. It is per BS VLAN Service Access Point that certain VLAN properties, such as if it is mandatory to enable isolation protection. BS VLAN Service Access Points can either be created manually by the operator or they can be automatically created from pre-registered network requirements bundled with the Blade System software. Regardless of how they are created, each one needs to be mapped to an Link SAP before the blades can be unlocked. The mapping is done with the 'linkSapRef' attribute. Name of the BS VLAN SAP. It is unique within the BS VLAN. Short description of the BS VLAN SAP. Flag which controls whether this BS VLAN SAP makes static or dynamic use of the corresponding IS VLAN. Flag which controls whether this BS VLAN SAP should be isolation protected or not. A mapping to the corresponding Link Service Access Point. A BS IP Traffic Class (BSIPTC) is the requirement a Blade System have of an IS IP Traffic Class. BS IP Traffic Classes can either be created manually by you or they can be automatically created from pre-registered network requirements bundled with the Blade System software. Regardless of how they are created, each one needs to be mapped to an IS IP Traffic Class before the blades can be unlocked via the Hardware service. The mapping is done with the 'isIpTrafficClassRef' attribute. Different instances of a Blade System type may call their BS IP Traffic Classes the same thing but in the end the IS Site Designer may choose to map them to the same or different IS IP Traffic Classes. The name of the BS IP Traffic Class. It is unique within the Blade System. A short description of The BS IP Traffic Class. The mapping to a corresponding IS IP Traffic Class. This mapping must be done before the blades of the Blade System can be unlocked. A BS LAN Traffic Class (BSLANTC) is the requirement a Blade System have of an IS LAN Traffic Class. Different instances of a Blade System type may call their BS Traffic Classes the same thing but in the end the IS Site Designer may choose to map them to the same or different IS LAN Traffic Classes. BS LAN Traffic Classes can either be created manually by you or they can be automatically created from pre-registered network requirements bundled with the Blade System software. Regardless of how they are created, each one needs to be mapped to an IS LAN Traffic Class before the blades can be unlocked via the Hardware service. The mapping is done with the 'isLanTrafficClassRef' attribute. Different instances of a Blade System type may call their BS LAN Traffic Classes the same thing but in the end the IS Site Designer may choose to map them to the same or different IS LAN Traffic Classes. Name of the BS IP Traffic Class. It is unique within the Blade System. Short description of the BS IP Traffic Class. The mapping to a corresponding IS LAN Traffic Class. This mapping must be done before the blades of the Blade System can be unlocked. 1 1 1