This table defines the objects that support provisioning of 'container' class physical entities. Provisioning sets up a 'container' to hold a specified physical entity. This allows a management client to configure the specified physical entity, including all of its subordinates physical entities, before installation. Provisioning allows the network manager to 'create' the physical entities that represent the new modules. In essence, the device simulates the installation of the new modules into the system. This has the effect of creating all conceptual rows in all the necessary tables that support the physical entity and all its subordinate physical entities (e.g., entPhysicalTable, and ifTable). The table extends some entries in the entPhysicalTable (see ENTITY-MIB for further details). A entry appears in this table for a physical entity matching the following criteria: 1) Its entPhysicalClass object has a value of 'container'; 2) It can contain one (but not multiple) physical entity; and, 3) It supports provisioning. The following states cause an alarm to be raised at the level of the containing module: IF provAssignmentState = assigned(1) AND provEquipmentState = unequipped(2) THEN 'eqMissing' alarm IF provEquipmentState = invalid(3) THEN 'eqNotAccepted' alarm