hwDhcpv6SvrGroupTable

This Table is supported only on the NetEngine 8000 F1A.

The configuration table of the DHCPv6 server group.

The index of the table is hwDhcpv6SvrGroupIndex.

OID

Object

Syntax

Max Access

Description

Implemented Specifications

1.3.6.1.4.1.2011.6.8.1.20.1.1

hwDhcpv6SvrGroupIndex

Integer32{(0,4095)}

read-only

The index of DHCPv6 server group.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.6.8.1.20.1.2

hwDhcpv6SvrGroupName

OCTET STRING{(1,32)}

read-create

The name of DHCPv6 server group.

The actually supported access is read-only.

1.3.6.1.4.1.2011.6.8.1.20.1.3

hwIPDhcpv6SvrAddr1

OCTET STRING{(16,16)}

read-create

The primary DNS address.

The actually supported access is read-only.

1.3.6.1.4.1.2011.6.8.1.20.1.4

hwIPDhcpv6SvrAddr2

OCTET STRING{(16,16)}

read-create

The seconday DNS address.

The actually supported access is read-only.

1.3.6.1.4.1.2011.6.8.1.20.1.5

hwIPDhcpv6PriSvrState

INTEGER{down(0),up(1)}

read-only

The status of primary DNS.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.6.8.1.20.1.6

hwIPDhcpv6ScdSvrState

INTEGER{down(0),up(1)}

read-only

The status of secondary DNS.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.6.8.1.20.1.7

hwIPDhcpv6SvrAutoRelease

INTEGER{true(1),false(2)}

read-create

The flag indicating whether server will automaticly send DHCPv6 release packet.

The actually supported access is read-only.

1.3.6.1.4.1.2011.6.8.1.20.1.8

hwIPDhcpv6SvrGroupRefCount

Integer32{(0,4096)}

read-only

The referenced count of DHCPv6 server group.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.6.8.1.20.1.9

hwDhcpv6SvrInterface1

OCTET STRING{(0,255)}

read-create

The outer interface of primary DHCPv6 server.

The actually supported access is read-only.

1.3.6.1.4.1.2011.6.8.1.20.1.10

hwDhcpv6SvrInterface2

OCTET STRING{(0,255)}

read-create

The outer interface of secondary DHCPv6 server.

The actually supported access is read-only.

1.3.6.1.4.1.2011.6.8.1.20.1.11

hwDhcpv6SvrAlgorithm

INTEGER{masterbackup(1),loadingshare(2),polling(3)}

read-create

The algorithm of selecting DHCPv6 server.

The actually supported access is read-only.

1.3.6.1.4.1.2011.6.8.1.20.1.12

hwDhcpv6SvrWeight1

Integer32{(0,100)}

read-create

The weight of primary DHCPv6 server.

The actually supported access is read-only.

1.3.6.1.4.1.2011.6.8.1.20.1.13

hwDhcpv6SvrWeight2

Integer32{(0,100)}

read-create

The weight of secondary DHCPv6 server.

The actually supported access is read-only.

1.3.6.1.4.1.2011.6.8.1.20.1.14

hwIPDhcpv6Svr1VrfName

OCTET STRING{(1,31)}

read-create

The vpn instance name of primary DHCPv6 server.

The actually supported access is read-only.

1.3.6.1.4.1.2011.6.8.1.20.1.15

hwIPDhcpv6Svr2VrfName

OCTET STRING{(1,31)}

read-create

The vpn instance name of secondary DHCPv6 server.

The actually supported access is read-only.

1.3.6.1.4.1.2011.6.8.1.20.1.16

hwDhcpv6SvrGroupRowStatus

INTEGER{active(1),notInService(2),notReady(3),createAndGo(4),createAndWait(5),destroy(6)}

read-create

Row admin status. Support adding, modification and deletion.

The actually supported access is read-only.

1.3.6.1.4.1.2011.6.8.1.20.1.17

hwDhcpv6SvrSourceInterface

OCTET STRING{(1,47)}

read-create

The interface name whose IP address is the source IP address carried in the packets sent to the server.

The actually supported access is read-only.

Creation Restriction

1) The primary and secondary servers cannot be the same.

2) When setting up the server, the primary and secondary servers must be bound to the settings, and the secondary server can be set only when the primary server is set.

3) When hwDhcpv6SvrAlgorithm is load sharing, set the weight of the server hwDhcpv6SvrWeight1, hwDhcpv6SvrWeight2 can work, otherwise the setting is allowed but it does not work.

4) hwIPDhcpv6SvrAddr1 and hwDhcpv6SvrInterface1 cannot be configured at the same time; hwIPDhcpv6SvrAddr2 and hwDhcpv6SvrInterface2 cannot be configured at the same time.

5) The VPN instance can be bound only when the server address is configured. If the VPN instance is bound to the VPN instance, the VPN instance must be delivered along with the server address.

Modification Restriction

The entries in this table cannot be modified.

Deletion Restriction

The entries in this table cannot be deleted.

Access Restriction

Only the active and standby algorithms hwIPDhcpv6PriSvrState and hwIPDhcpv6ScdSvrState can read the valid value.
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >