Nortel-Magellan-Passport-HuntGroupMIB: View SNMP OID List / Download MIB

This entry controls the addition and deletion of hg components.

A single entry in the table represents a single hg component.

This variable is used as the basis for SNMP naming of hg components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the hg tables.

This variable represents the index for the hg tables.

This entry controls the addition and deletion of hgHgM components.

A single entry in the table represents a single hgHgM component.

This variable is used as the basis for SNMP naming of hgHgM components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the hgHgM tables.

This variable represents the index for the hgHgM tables.

The Provisioned group contains the provisioned attributes of the hunt group member.

An entry in the hgHgMProvTable.

The address attribute specifies the numbering plan and digits which form a unique DNA identifier of the hunt group member. The format of the address attribute is . where numbering plan is x for X.121 and e for E.164. An example X.121 address is x.12345678.

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the hgHgMStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

The Operational group defines operational attributes associated with the HuntGroupMember component.

An entry in the hgHgMOperationalTable.

This attribute indicates the current availability of the member. The higher the value, the more available the member is perceived to be. A value of 0 indicates the member is unavailable. A member must be considered 'available' by the hunt group in order to receive a call, regardless of the selection policy in use. The hunt group members report whether or not they are available to receive calls to the hunt group. Some services base their availability on unused logical channels, others on bandwidth or memory capacity. During initialization, the hunt group assumes all of its members are equally available and sets their availability value to the maximum of 4095. Similarly, a new hunt group member added to an existing hunt group has its availability value initialized to 4095. This ensures that members which have not reported their availability to the hunt group are tried in order to trigger the member to report its true availability. The availability of a member can change in the following ways: - Hunt group members can report their availability to the hunt group using a DPRS availability packet. - A network operator can temporarily change the value by the Set command. This change remains in effect until changed again by any of these ways. - The hunt group resets a member's availability to the maximum of 4095 if it has been 0 for at least 2.5 hours. This ensures that 'lost' availability information does not prevent a member from returning to service.

This attribute counts the number of availability update packets received by the hunt group member. This counter wraps to 0 when it exceeds its maximum value.

This attribute counts the number of call packets which were returned to the hunt group by the member because it could not connect the call. If this counter increments frequently, it could indicate a problem with the member's reporting of its availability to the hunt group or an incompatibility in the call options. This counter wraps to 0 when it exceeds its maximum value.

This group contains the attribute for a component's Customer Identifier (CID). Refer to the attribute description for a detailed explanation of CIDs.

An entry in the hgCidDataTable.

This attribute holds the Customer Identifier (CID). Every component has a CID. If a component has a cid attribute, the component's CID is the provisioned value of that attribute; otherwise the component inherits the CID of its parent. The top- level component has a CID of 0. Every operator session also has a CID, which is the CID provisioned for the operator's user ID. An operator will see only the stream data for components having a matching CID. Also, the operator will be allowed to issue commands for only those components which have a matching CID. An operator CID of 0 is used to identify the Network Manager (referred to as 'NetMan' in DPN). This CID matches the CID of any component. Values 1 to 8191 inclusive (equivalent to 'basic CIDs' in DPN) may be assigned to specific customers.

This group contains attributes common to all NSAP format addresses.

An entry in the hgNsapAddressTable.

The address attribute specifies the numbering plan and digits which form a unique DNA identifier of the hunt group. The format of the address attribute is . where numbering plan is x for X.121 and e for E.164. An example X.121 address is x.12345678.

The Provisioned group contains the provisioned attributes of the hunt group.

An entry in the hgProvTable.

This attribute specifies the logical processor on which the hunt group process will execute. The Lp/n Eng Hgs component contains statistics for all hunt groups on the LP.

The selectionPolicy attribute specifies the algorithm used to select a hunt group member. A value of startFromZero means that on a new call, the first available member starting from the member with the lowest instance value is selected. Subsequent hunts for the same call select the first available member starting from the previously chosen member. This algorithm is used when it is desirable to have the first member receive the majority of the calls and subsequent members only receive calls in overflow situations. A value of rotary means that on a new call, the first available member is selected starting from the member which received the last new call. Subsequent hunts for the same call select the first available member starting from the previously chosen member. This algorithm is used when it is desirable to loadspread the calls equally across the members. A value of mostAvailable means that on a new call, the most available member is selected based on the availability information received from the member. Subsequent hunts for the same call select the most available member starting from the previously chosen member. This algorithm is used when it is desirable to send each call to the member which has the highest probability of connecting it. Enumeration: 'mostAvailable': 2, 'rotary': 1, 'startFromZero': 0.

The maxHuntAttempts attribute specifies the maximum attempts allowed to hunt the call. Hunting ceases if either this maximum is exceeded or the member list is exhausted.

The appendSuffixDigits attribute specifies how suffix called address digits are handled. Suffix called address digits are any trailing digits, signalled in a call, beyond the provisioned hunt group address. If this attribute is set to yes, suffix digits are appended to the member address before the call is forwarded to the member. If it is set to no, suffix digits are not appended to the member address. Enumeration: 'yes': 1, 'no': 0.

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the hgStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

The Operational group contains the operational attributes of the hunt group.

An entry in the hgOperationalTable.

This attribute counts the total number of hunt attempts made by the hunt group. The count includes both initial and subsequent hunt attempts. This count is contained within the huntAttempts attribute of the Lp/n Eng Hgs component. This counter wraps to 0 when it exceeds its maximum value.

This attribute counts the number of calls which could not be connected by any of the hunt group members. This could occur if the hunt group is locked or has exhausted its member list. If a call cannot be connected by the hunt group it is sent to call redirection. This counter wraps to 0 when it exceeds its maximum value.

This attribute counts the number of new (non-hunted) calls received by the hunt group which are forwarded to a member. This counter wraps to 0 when it exceeds its maximum value.

This attribute counts the number of availability update packets received by the hunt group from its members. This counter wraps to 0 when it exceeds its maximum value.

This attribute counts the number of times a member could not be selected to receive a call with suffix address digits because its DNA length would exceed the maximum of 14 digits with the suffix digits appended. This counter wraps to 0 when it exceeds its maximum value.

This attribute counts the number of unrecognizable packets received by the hunt group and discarded. This counter wraps to 0 when it exceeds its maximum value.