CIG-CLIENTS-MIB: View SNMP OID List / Download MIB

This module defines the cig Clients. The first client in the DHCP client used for getting dynamic IP address and configuration parameters from DHCP server.The DHCP client will be a function of interfaces. The second client is DNS resolver client. Copyright notice: This AVAYA SNMP Management Information Base Specification (Specification) embodies AVAYA confidential and Proprietary intellectual property. AVAYA retains all Title and ownership in the Specification, including any revisionsIt is AVAYA's intent to encourage the widespread use of this Specification in connection with the management of AVAYA products. AVAYA grants vendors, end-users, and other interested parties a non-exclusive license to use this Specification in connection with the management of AVAYA products.This Specification is supplied 'as is', and AVAYA makes no warranty, either express or implied, as to the use, operation, condition, or performance of the Specification.

DHCP IP address conflict detection. This trap is based on: The Client Decline Packets after the client sent gratuitous Arp and get response which implies that another station use this IP address.

cigDhcpClientsTable parameters. Used for DHCP clients which gathered dynamic IP addresses and configuration from DHCP servers.

cigDhcpClients Entry Parameters.

A unique value for each interface. This value is same as ifIndex from ifTable. The DHCP client can be enabled on Vlan and on WAN Fast Ethernet interfaces.

This is a row status mib item For adding and deleting DHCP clients interfaces. For configuring only DHCP client parameters use create and wait for specific interface. When activating the DHCP client, activate the row. Activating the row will create a new row in the ipDynamic Table in CROUTE-MIB that presents dynamic ipInterface. Deactivating the DHCP client will cause to erasing the row in the ipDynamic Mib table and deactivating the DHCP client row in order to keep the specific DHCP parameters which already were configured.

This object is an 'alias' name for the lower-layer interface on top of which this IP interface is defined. It is the same as the ifAlias from the standard interface table.

The IP address received from remote peer during the DHCP session. This is the same MIB item as ipInterface table in CROUTE-MIB.

The subnet mask associated with the IP address of this entry. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0. In case of DHCP client this is DHCP option 1 == Subnet Mask. This is the same MIB item as ipInterface table in CROUTE-MIB.

Client identifier used for manual leased. The structure of the client identifier is as follows: combination of TYPE and Data. Where Type = 01 if for Ethernet MACs and Data for this case if Ethernet MAC address. The user can use also other client identifiers as strings. Default: '' - 01:Interface MAC address.

Host name is sent by the DHCP client as Dhcp option 12. It is specifically used by part of DHCP servers (MS2000) to identify the client in the binding file (more user intuitive). This option is used as well by part of the DHCP server with the support of DHCP client (sending option 81) to update the DNS server with the new IP for specific host. The format of the string can be: 'usernameA'. The hostname shall comply to RFC 1035 naming convention with the following exceptions: a. allow digits at the start of the name. b. Do not check length constraints of 63 bytes. The default of the host name used by the DHCP client is the device host name.

The Requested leased time in seconds. Infinite is defined as 0xffffffff. 0 - used to present that no lease time requested from the DHCP server. I.e. option 51 will not be sent by the client. Default 0 seconds.

The received leased time from the DHCP server in seconds. Infinite is defined as 0xffffffff. Default 0 seconds.

The remains leased time in seconds . Infinite is defined as 0xffffffff. Default 0 seconds.

The time defined for renewing phase in seconds . Infinite is defined as 0xffffffff. It is defined as 0.5 of the receive lease. Default 0 seconds.

The time defined for rebinding phase in seconds . Infinite is defined as 0xffffffff. It is defined as 0.875 of the receive lease. Default 0 seconds.

Default Gateway is Dhcp option 3. Default = '' = Null String. The format of the string can be up to 8 IP addresses in the list, for example: '121.23.1.12 135.64.13.190 192.123.242.230'

DNS Server is Dhcp option 6. Default = '' = Null String. The format of the string can be up to 8 IP addresses in the list, for exapmle: '121.23.1.12 135.64.13.190 192.123.242.230'

DNS Server is Dhcp option 15. Default = Null String The format of the string can be: 'avaya' There is no ability to configure this option in the general option table.

The DHCP server IP address that the client gets from it the IP address allocation and keep requesting for lease extension from it. In case no IP address is gathered from DHCP server then value is 0.0.0.0. Default 0.0.0.0.

Used for instruct the DHCP client to perfrom release or renew operations. Enumeration: 'release': 2, 'idle': 1, 'renew': 3.

The status of the DHCP client. Select - Sending DISCOVER packets Request - Requesting IP address after selecting from all the offer packets. Bound - Receiving ACK packet and there is no conflict detection by sending ARP packets. Rebind - After 0.875 out of the lease time the renewal phase enter to rebind. Renew - After 0.5 out of the lease time the device try to renew the lease until 0.875 of the lease time. Release - The client release the lease. Decline - The client detect IP conflict by sending ARP packet. Idle - The client did not get IP address and keep trying after an Idle time (~40 seconds) to reach new IP address. Enumeration: 'decline': 7, 'request': 2, 'bound': 3, 'reboot': 8, 'rebind': 4, 'renew': 5, 'release': 6, 'notSupported': 255, 'idle': 9, 'select': 1.

Each bit of this value set to '1' indicates a specific requested DHCP option (Bitmap of 255 options represented by 32Bytes). When the bit is set to '1' then specific DHCP option is requested by the client. Subnet mask bit 1 - is always requested. Bits are numbered from the most-significant leftmost bit in the octet (bit 0) to the least-significant rightmost bit (bit 7). Numbering continues across octets, so that octet 1 bit 0 is called bit 8. Default: '0x5201' which equals to: bit 1 - Subnet mask (Always requested!) Bit 3 - Default routers Bit 6 - DNS servers Bit 15 - Domain Name

Bind the status of the DHCP default router to an object-tracker by specifying the ID of the object-tracker (avstrTrackerId in AVAYA-SAA-TRACK-MIB). A value of 0 means that the default router is not bound to any object-tracker. A value of 0xffffffff is notSupported feature for the relevant default router.

Enable the DNS resolver in the device. Default = True (Enable).

The number of retries for each query for specific DNS server when there is timeout. The range is 0-100.

The timeout in seconds for each query for specific DNS server. The range is 1-3600 seconds.

Used for specific operations for DNS server. clearDynamicServers(2) will clear all the dynamic servers (learnt from PPP interfaces and DHCP clients) from DNS server list. clearDNSCache(3) - Clear the DNS Resolver cache. Enumeration: 'clearDynamicServers': 2, 'idle': 1, 'clearDNSCache': 3.

Lists of DNS servers. The default list(1) includes all the static DNS server and the dynamic DNS servers from the DHCP clients/PPP interfaces as PPPoE and Dial out modem.

The DNS servers list. Lists of DNS servers.

The index of the list of DNS servers. Default list index is 1. The user will not be able to create lists other then default list at the first release.

This is the list description. Default for DNS list #1: 'DNS list #1'

This is a row status mib item For adding and deleting DNS server lists. The user will not be able to create lists other then list 1 at the first release.

DNS servers. The user can configure up to 6 static servers located in places 1-6. The other indexes are of dynamic servers which can not be created (learnt automatically by the device) but can be erased. The indexes 1-99 are for static servers (only the first 6 are configurable). The indexes 100-199 are for dynamic servers.

The DNS server entry. The user can configure up to 6 static servers located in places 1-6. The other indexes are of dynamic servers which can not be created (learnt automatically by the device) but can be erased. The indexes 1-99 are for static servers (only the first 6 are configurable). The indexes 100-199 are for dynamic servers.

The index of the list of DNS servers. Default list index is 1. The user will not be able to create lists other then default list at the first release.

The index of DNS server in the list of DNS servers. The index presents the preference of the server. The lower the index the higher priority to use it.

The DNS server IP address.

A unique value for each interface. This value is same as ifIndex from ifTable. This field is used when the DNS server is learnt from interface running DHCP client or PPP negotiated (PPPoE/Dial Out modem). This field has no valid value when the type of the DNS server is static.

This is the server type. The user can create new row only when the server type is static. dynamic-dhcp represents DNS server learnt from DHCP client. dynamic-ppp represents DNS server learnt from ppp interface (PPPoE/Dial out modem). Enumeration: 'static': 1, 'dynamic-dhcp': 2, 'dynamic-ppp': 3.

This is a row status mib item For adding and deleting DNS servers. The user can add only static servers in locations 1-6. For static servers the operation suppported is CreateAndWait and dynamic servers are automatically created by the device.

The address type of cigDnsResolverDnsServerInetAddress.

The Inet Address of the dns server. 1. The address type of this object is specified in cigDnsResolverDnsServerInetAddressType. 2. Management applications can use cigDnsResolverDnsServerIpAddress or cigDnsResolverDnsServerInetAddressType/cigDnsResolverDnsServerInetAddress to set IPv4 server address and only cigDnsResolverDnsServerInetAddressType/cigDnsResolverDnsServerInetAddress to set IPv6 server address. 3. The cigDnsResolverDnsServerInetAddressType must always been set before the cigDnsResolverDnsServerInetAddress is set (the avGenOpServerInetAddress must conform to the cigDnsResolverDnsServerInetAddressType). 4. Setting cigDnsResolverDnsServerIpAddress address mib item will change cigDnsResolverDnsServerInetAddressType to IPv4(1) and cigDnsResolverDnsServerInetAddress to IPv4 address configured. 5. Setting cigDnsResolverDnsServerInetAddress as IPv4 address will also set cigDnsResolverDnsServerIpAddress. 6. Setting cigDnsResolverDnsServerInetAddress as IPv6 address will also set cigDnsResolverDnsServerIpAddress to 0.0.0.0. 7. Default of cigDnsResolverDnsServerInetAddressType is unknown(0) and cigDnsResolverDnsServerInetAddress is zero length. 8. Setting cigDnsResolverDnsServerInetAddressType to IPv4 will return cigDnsResolverDnsServerIpAddress and cigDnsResolverDnsServerInetAddressType to default value of 0.0.0.0. Setting genOpServerInetAddressType to value other than IPv4 return cigDnsResolverDnsServerIpAddress to default value of 0.0.0.0 and cigDnsResolverDnsServerInetAddressType to default value of null string. Row status can not be active if cigDnsResolverDnsServerIpAddress or cigDnsResolverDnsServerInetAddressType/cigDnsResolverDnsServerInetAddress are not configured.

The domains used by the DNS resolver to add to non full qualified names. I.e. when the host name is not a full host name then these domains are added in order to resolve the non full qulified name. an example for domain is : avaya.com. an example for non qualified name is lantis. Therefore when trying to resolve lantis the suffix avaya.com will be added to create the name lantis.avaya.com

The Domain entry. The domains used by the DNS resolver to add to non full qualified names. I.e. when the host name is not a full host name then these domains are added in order to resolve the non full qulified name. an example for domain is : avaya.com. an example for non qualified name is lantis. Therefore when trying to resolve lantis the suffix avaya.com will be added to create the name lantis.avaya.com

The index of the domain. The index presents the precedence of the domain. I.e. the lower the index the higher priority this domain is used.

The Domain shall follow RFC 1035 Host name convention. The following syntax will result in fewer problems with many applications that use domain names (e.g., mail, TELNET). Note that while upper and lower case letters are allowed in domain names, no significance is attached to the case. That is, two names with the same spelling but different case are to be treated as if identical. The labels must follow the rules for ARPANET host names. They must start with a letter, end with a letter or digit, and have as interior characters only letters, digits, and hyphen. There are also some restrictions on the length. Labels must be 63 characters or less. For example, the following strings identify hosts in the Internet: A.ISI.EDU XX.LCS.MIT.EDU SRI-NIC.ARPA

This is a row status mib item For adding and deleting domains. The row is created by CreateAndWait.