HP-ICF-FTRCO
This MIB module manages Application Coordination Restriction Policies
Main OID:
hpicfFtrCo.1.3.6.1.4.1.25506.11.1.46
26
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
26 total| Object Name |
|---|
hpicfFtrCoThis MIB module manages Application
Coordination Restriction Policies MODULE-IDENTITY .1.3.6.1.4.1.25506.11.1.46 |
IMPORTSThis MIB module manages Application
Coordination Restriction Policies Unknown .1.3.6.1.4.1.25506.11.1.46 |
hpicfFtrcoObjects OBJECT IDENTIFIER .1.3.6.1.4.1.25506.11.1.46.1 |
hpFtrCoEntityTableTable of all Entities setting restrictions, as set by some external
entity. Any restriction for an Entity can be deleted by deleting the
Entity name, by deleting a specific restriction, or by any expiration
value. Once an Entity name has been added to the table, it exist until
the name has specifically been removed. Entity rows also maintain the
'next-index' value for any restriction table entry. SEQUENCE OF HpFtrcoEntityEntry .1.3.6.1.4.1.25506.11.1.46.1.1 |
hpFtrCoEntityEntryA row entry in the table for a specific entity user of the Feature
Coordinator facility. Entries in this table are created and removed
dynamically. An entity can add and remove a restriction regarding
some pre-defined facility in the switch and it will only be for a
specific Entity name. If the Entity name is removed, so are all of
its restrictions. HpFtrcoEntityEntry .1.3.6.1.4.1.25506.11.1.46.1.1.1 |
hpFtrCoEntityNameAn administratively assigned string, which may be used to identify
the unique owner of a set of restrictions. IndexName .1.3.6.1.4.1.25506.11.1.46.1.1.1.1 |
hpFtrCoRestrictNextIndexIs the next indexing parameter that allows multiple, like
restrictions. It is has a default value of 1 and is incremented
each time its index value is used. This is an independent value
and must be specified as the next added index (regardless of the
restriction type). In the event there is a collision due to a race
with reading the current value, the 'losing' restriction is denied
and the value should be re-read for a next attempt. The value is
always 1 whenever a new Entity record is created.rw Integer32 .1.3.6.1.4.1.25506.11.1.46.1.1.1.2 |
hpFtrCoEntityDateThis represents the switch's understanding of the current UTC time.
It should be used when setting an restriction expiration
DateAndTime value. Please note that this value is uniquely
determined each time the object is read (dynamic) and is
subject to changing when a change is made to the switch's
configuration (e.g. setting the local time-zone).ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.25506.11.1.46.1.1.1.3 |
hpFtrCoEntityStatusAdministrative status of this Entity entry.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.25506.11.1.46.1.1.1.4 |
hpFtrCoRestrictionTableTable of all restrictions, set by an external entity. The restrictions
can be deleted by deleting the entity name or by the restriction
expiration value. Expiration policies are logically ORed so that any policy
expiration that is met causes the restriction to be removed. SEQUENCE OF HpFtrCoRestrictEntry .1.3.6.1.4.1.25506.11.1.46.1.2 |
hpFtrCoRestrictEntryAn entry in the table for a specific Entity user of the Feature
Coordinator facility. Entries in this table are created and removed
dynamically. An entity can add and remove a restriction to some
facility in the switch. These entries can also expire, based on
entity specified criteria. A restriction is never modified (all
restrictions are only created or deleted). If a value needs to be
modified, a new restriction could be added and then the old one
deleted (e.g. adding or removing an interface). HpFtrCoRestrictEntry .1.3.6.1.4.1.25506.11.1.46.1.2.1 |
hpFtrCoRestrictIdThe Restriction enumeration (Id). Expect this list to grow as are
more restrictions are developed (and needed). Enumeration .1.3.6.1.4.1.25506.11.1.46.1.2.1.1 |
hpFtrCoRestrictIndexAn indexing parameter to allow multiple, like restrictions. It is
created by the Entity portion of MIB and used for addressing an
individual restriction rule. Any new restriction added to a
restriction table must be equal to the current 'next-restriction'
value. Integer32 .1.3.6.1.4.1.25506.11.1.46.1.2.1.2 |
hpFtrCoRestrictIdParmAn optional parameter for the restriction enumeration.rw Integer32 .1.3.6.1.4.1.25506.11.1.46.1.2.1.3 |
hpFtrCoRestrictStatusAdministrative status of this entry.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.25506.11.1.46.1.2.1.4 |
hpFtrCoRestrictMessageAn error message containing information about the restriction that
can be used by the caller, indicating the reason for this restriction
being in place. It is occasionally referred to as a friendly error
message. SIZE reflects that a message must exist and that it has
a maximum 'String' length of 255 character.rw SnmpAdminString .1.3.6.1.4.1.25506.11.1.46.1.2.1.5 |
hpFtrCoRestrictPortsA list of ports, if applicable to the restriction.rw PortList (Q-BRIDGE-MIB) .1.3.6.1.4.1.25506.11.1.46.1.2.1.6 |
hpFtrCoRestrictVlansA VidList of vlan IDs, if applicable to the restriction.rw VidList .1.3.6.1.4.1.25506.11.1.46.1.2.1.7 |
hpFtrCoExpireSlotSetting this value will cause this restriction to expire when
corresponding switch slot is signaled to be down. Note, if the slot
never comes up, there will be no slot-down signal.rw Integer32 .1.3.6.1.4.1.25506.11.1.46.1.2.1.8 |
hpFtrCoExpireApplicationThis setting will cause the restriction to expire whenever a signal
is received that this application-name has gone down.rw IndexName .1.3.6.1.4.1.25506.11.1.46.1.2.1.9 |
hpFtrCoExpireVidDeleteA signal indicating this VlanIndex has been deleted will cause this
restriction to expire. The specified VID record must exist in the
switch configuration for this policy to be set. NOTE: ExpireVidDelete
is unused in this release; it is available, you can set it; but it is
totally ignored with current processing.rw Integer32 .1.3.6.1.4.1.25506.11.1.46.1.2.1.10 |
hpFtrCoExpireDateThis expiration event occurs whenever it is determined that the
switch-time exceeds this setting. The switches sw_time() represents
the UTC time value (relative to Jan 1, 1990) used with this comparison
(compare with sw_localtime). NOTE: ExpireDate is unused in this release;
it is available, you can set it; but it is totally ignored with current
processing.rw DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.25506.11.1.46.1.2.1.11 |
hpFtrCoExpireBootWhen specified as 'true', this expiration event occurs whenever the
switch reboots. It is a necessary expiration policy since all
restrictions are persistent and it is possible that we can have an
obsolete policy (slot-down) following a power-fail condition.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.25506.11.1.46.1.2.1.12 |
hpicfFtrCoConformance OBJECT IDENTIFIER .1.3.6.1.4.1.25506.11.1.46.2 |
hpicfFtrCoCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.25506.11.1.46.2.1 |
hpicfFtrCoGroups OBJECT IDENTIFIER .1.3.6.1.4.1.25506.11.1.46.2.2 |