pktcEUEUsrIMPIEntry

Each entry in this data table contains an instance
of a user IMPI and associated credentials.
Each IMPU provisioned in the eUE SHOULD be associated
with an entry in this table. The exception is in networks
where certain users are unauthenticated for application
access.
 At boot time the eUE MUST populate conceptual rows in this
 order:
 - First, instances provisioned via device configuration (e.g.,
 config file, dynamically created via SNMP). These instances
 MUST NOT persist across reboots.
 - Second, entries provisioned via Certificate Bootstrapping
 File. These entries may appear again after device
 re-initialization, depending on Certificate Bootstrapping
 file persistence requirements defined elsewhere.
 As a side effect, if an instance loaded from a Certificate
 Bootstrapping file is updated via SNMP later on, those changes
 are not required to be reflected in the CB file persistence
 storage (if CB file persistence is supported). Instead, the
 trigger of a new CB file download is preferred to update CB
 information.

MIB

CL-PKTC-EUE-USER-MIB

OID

.1.3.6.1.4.1.4491.2.2.10.4.1.1.3.1

Type

row

Status

current

Parent

pktcEUEUsrIMPITable

Table

pktcEUEUsrIMPITable

Children

6