The Bellcore state dictionary visuals
Describes the three primary states and various secondary states of the Bellcore state dictionary.
Illustrates the graphical representation of the three Bellcore primary states.
Provides the graphical representations of Bellcore secondary states.
Graphical representation of the Bellcore primary states
These graphical representations are based on the base element states introduced in Introducing business objects and data sources. The same graphical representations are used for links, groups, and cards. Note that the primary state of empty slots is not represented graphically.
These states are represented graphically by a change in the appearance of the object base (hatched around the perimeter, flat base, or base in relief).
|
Bellcore State Value |
Visual |
|
Disabled/Idle |
|
|
Enabled/Idle |
|
|
Enabled/Active |
|
Graphical representation of the Bellcore secondary states
Secondary states are almost always represented graphically by adding an icon to the top left corner of the object base element.
The only exceptions concern the “Unassigned,” “Unequipped,” and “Pre-Post Service” secondary states for which the OOS representations are denoted by a main change in the base element visual (as shown in table Other representations of Bellcore secondary states).
How to read the When Applicable column
The meaningful representation of the secondary states depends on the current Bellcore primary state set to the telecom object. The Bellcore primary states are the following:
-
OOS—Disabled/Idle
-
NT—Enabled/Idle
-
CT—Enabled/Active
The “When Applicable” column in table Icon-based representations of Bellcore secondary states lists the graphic representation of the Bellcore secondary states for a given primary state. A blank entry indicates that the secondary state has no meaning in that particular primary state.
Secondary state names
In Icon-based representations of Bellcore secondary states , the symbolic name “ Secondary State Definition ” that appears after each “Secondary State Name” corresponds to the static secondary state definition. For example, the “Inhibit In Progress” secondary state is defined by InhibitInProgress, which corresponds to the static definition InhibitInProgress.
Secondary state icons
It is possible to change the icon associated with a secondary state by using global settings, see Using global settings. The icon property name to be used with IltSettings.SetValue() must include the secondary state definition and the primary state. For example:
-
Bellcore.SecState.IdleTransmit.NT.Icon
where:
IdleTransmit is the secondary state definition of the “Idle Transmit” secondary state
NT is the corresponding Bellcore primary state (Enabled/Idle)
For more information on how to use global settings to modify the Bellcore secondary state icons, see Customizing the Bellcore state system.
|
Secondary State Name Secondary State Definition |
When Applicable: OOS, NT, CT |
Comment |
||
|
Blocked Blocked |
|
No outgoing traffic is allowed on the entity. The restriction is imposed by the far-end network element. |
||
|
Busy Busy |
|
The entity is currently in use and has no spare operating capacity for further usage demand. |
||
|
Cold Standby ColdStandby |
|
The entity is about to back up another entity and is synchronized with the backed-up entity. It requires initialization before it can take over. |
||
|
Combined Combined |
|
This load-sharing entity has assumed the load of its mate entity in addition to its own. |
||
|
Diagnostic Diagnostic |
|
|
|
Diagnostic activity that affects the service is currently being performed on the entity. |
|
Disconnected Disconnected |
|
|
|
Subscribed service has been disconnected, but still exists in the database with a specific intercept treatment. |
|
Exercise Exercise |
|
|
|
Service-affecting exercise is currently being performed on the entity. |
|
Facility Failure FacilityFailure |
|
|
|
The associated transport facility is OOS. |
|
Far End Processor Outage FarEndProcessorOutage |
|
|
|
The processor at an associated far-end network element is OOS. |
|
Fault Fault |
|
The entity is OOS because it is faulty. |
||
|
Forced Forced |
|
|
The entity has been manually forced into the In Service state from an Out Of Service state that occurred under the normal procedure. |
|
|
Hot Standby HotStandby |
|
The entity is to back up another entity and is synchronized with the backed-up entity. It does not require initialization before it can take over. |
||
|
Idle Idle |
|
The entity is available to provide service, but is not currently used. |
||
|
Idle Receive IdleReceive |
|
Applicable to bidirectional termination points only. The receiving direction is not cross-connected. |
||
|
Idle Transmit IdleTransmit |
|
Applicable to bidirectional termination points only. The transmission direction is not cross-connected. |
||
|
Inhibit In Progress InhibitInProgress |
|
|
|
The entity is waiting for users to terminate before transitioning to OOS. |
|
Locked Out LockedOut |
|
|
|
No outgoing traffic is allowed on the entity. This restriction may be imposed for maintenance reasons. |
|
Loopback Test LoopbackTest |
|
|
|
A loopback activity is being performed on the entity. |
|
Maintenance Maintenance |
|
|
|
The entity has been manually removed from service for maintenance activity. |
|
Maintenance Limited MaintenanceLimited |
|
|
|
Normal trouble detection function is not provided for the entity because of defects developed in the entity or in an associated entity. |
|
Mismatch Of Equipment MismatchOfEquipment |
|
|
|
The entity is installed with improper equipment or circuit pack, or the correct equipment has improper attributes. |
|
Monitor Monitor |
|
|
The entity has reached a monitored performance level considered as abnormal. |
|
|
Overflow Overflow |
|
|
The entity has no more storage capacity for capturing additional information. In this state, the entity is read-only. |
|
|
Performance Monitor Inhibited PerformanceMonitorInhibited |
|
|
|
The performance monitoring function of the entity has been temporarily suspended. |
|
Power Power |
|
The entity is abnormal or OOS because there is a defect in the power supply. |
||
|
Pre-Post Service PrePostService |
|
|
The entity has been manually removed from service for the pre/post-service administration activity. |
|
|
Protection Release Inhibited ProtectionReleaseInhibited |
|
|
The entity is inhibited from protection release. |
|
|
Protection Switch Exercise ProtectionSwitchExercise |
|
|
A protection switching exercise is currently running on the entity. |
|
|
Protection Switch Inhibited ProtectionSwitchInhibited |
|
|
The regular protected entity is inhibited from switching to protection. |
|
|
Protocol Protocol |
|
The entity is OOS due to a Layer-2 or higher protocol violation. |
||
|
Providing Service ProvidingService |
|
The redundant (backup, protecting) entity is currently providing service. This value is mutually exclusive of cold-standby, warm-standby, and hot-standby. It is equivalent to the Working secondary state. |
||
|
Rearrangement Rearrangement |
|
The entity has been removed from service because of physical and/or logical rearrangement activity. |
||
|
Red Lined RedLined |
|
|
|
The entity is a special (red-lined) circuit. |
|
Software Downloading SoftwareDownloading |
|
|
|
Software download activity is currently being performed on the entity. |
|
Software Transfer Inhibited SoftwareTransferInhibited |
|
|
|
Software transfer is inhibited on the entity. |
|
Software Transfer Only SoftwareTransferOnly |
|
|
|
Only software transfer is allowed on the entity. |
|
Software Uploading SoftwareUploading |
|
|
|
Software upload activity is currently being performed on the entity. |
|
Standby Inhibited StandbyInhibited |
|
The standby entity is inhibited from taking over the role of the backed-up entity. |
||
|
Standby Switched StandbySwitched |
|
|
Indicates the state of a protection system, for example, switched on to provide service. |
|
|
Supported Entity Absent SupportedEntityAbsent |
|
|
|
The associated support entities are absent. |
|
Supported Entity Exists SupportedEntityExists |
|
|
|
The entity is currently supporting other entities. |
|
Supporting Entity Absent SupportingEntityAbsent |
|
|
|
The associated supporting entities are absent. |
|
Supporting Entity Outage SupportingEntityOutage |
|
There is an outage on the supporting entity. |
||
|
Supporting Entity Swapped SupportingEntitySwapped |
|
|
|
The associated supporting entity has swapped to a spare (backup) entity. |
|
Suspend Both SuspendBoth |
|
|
|
Any attempt to establish connection to or from the entity is administratively inhibited for non-maintenance reasons. |
|
Suspend Origination SuspendOrigination |
|
Any attempt to establish a connection with the entity is administratively prohibited for non-maintenance reasons. The consequences are the same as disabled, which is used for maintenance. |
||
|
Suspend Termination SuspendTermination |
|
Any attempt to establish a connection with the entity is administratively prohibited for non-maintenance reasons. The consequences are the same as disabled, which is used for maintenance. |
||
|
Switched System Activity SwitchedSystemActivity |
|
The entity is removed from service due to switching system activities. |
||
|
Terminated-Both Terminated-Both |
|
|
When applied to a termination point, the receiving signal is terminated and an insertion word is transmitted instead of the normal signal. |
|
|
Terminated-From Terminated-From |
|
|
|
When applied to a termination point, the receiving signal is terminated. |
|
Terminated-To Terminated-To |
|
|
|
When applied to a termination point, an insertion word is transmitted instead of the normal signal. |
|
Test Test |
|
|
|
Test activity, other than loopback, diagnostics, and exercise, is currently being performed on the entity. |
|
Test Failure TestFailure |
|
The object is OOS due to a test failure. |
||
|
Transferred Transferred |
|
|
|
The load sharing entity has transferred its normal load responsibility to its mate entity. |
|
Warm Standby WarmStandby |
|
The entity is to back up another entity and gets synchronized with the backed up entity at regular intervals. It does not require initialization before it can take over. |
||
|
Working Working |
|
The redundant (backup, protecting) entity is currently providing service. This value is mutually exclusive of cold-standby, warm-standby, and hot-standby. |
||
|
Secondary State Name Secondary State Definition |
Visual (OOS only) |
Comment |
|
Pre-Post Service PrePostService |
|
The entity has been manually removed from service for the pre/post-service administration activity. |
|
Unassigned Unassigned |
|
The entity has not been assigned the required provisioning data. No service or maintenance is permitted in this state since the necessary data has not been assigned. |
|
Unequipped Unequipped |
|
The equipment entity has not been equipped with the necessary hardware or the software entity has not been loaded with the necessary data or code. |






