![]() | Note:
|
![]() | Note:
|
This command creates a text description stored in the configuration file for a configuration context.
The description command associates a text string with a configuration context to help identify the content in the configuration file.
The no form of this command removes the string from the configuration.
This command administratively disables the entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics. Many entities must be explicitly enabled using the no shutdown command. The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.
Unlike other commands and parameters where the default state is not indicated in the configuration file, shutdown and no shutdown are always indicated in system-generated configuration files.
The no form of this command places the entity into an administratively enabled state.
This command creates a configuration context for the specified DHCP filter policy if it does not exist and enables the context to configure the specified DHCP filter policy.
This command creates a configuration context for the specified DHCPv6 filter policy if it does not exist and enables the context to configure the specified DHCPv6 filter policy.
The no form of this command reverts to the default.
This command specifies the default action for DHCP filters when no entries match.
The no form of this command reverts to the default.
This command specifies the default action for DHCP6 filters when no entries match.
The no form of this command reverts to the default.
This command configures DHCP filter entries.
The no form of this command removes the entry from the configuration.
This command specifies the action to take on DHCP host creation when the filter entry matches.
The no form of this command reverts to the default wherein the host creation proceeds as normal.
This command specifies the action to take on DHCP6 host creation when the filter entry matches.
The no form of this command reverts to the default wherein the host creation proceeds as normal.
This command configures match criteria for the DHCP filter policy entry.
The no form of this command reverts to the default
This command configures match criteria for the DHCP6 filter policy entry.
The no form of this command reverts to the default.
This command enables the context to configure subscriber management parameters.
This command enables the context to configure a local user database.
The no form of this command reverts to the default.
This command enables the context to configure IPoE host parameters.
This command defines a DHCP or PPP subscriber.
The no form of this command removes the host name from the configuration.
This command specifies the accounting policy used for sending an Accounting Stop message to report RADIUS authentication failures of PPPoE sessions. A duplicate policy can be specified if a copy of the Accounting Stop message must be sent to another destination.
Reporting RADIUS authentication failures with an Accounting Stop message must be enabled in the RADIUS authentication policy (“send-acct-stop-on-fail”).
A duplicate RADIUS accounting policy can be specified if the accounting stop resulting from a RADIUS authentication failure must also be sent to a second RADIUS destination.
The no form of this command reverts to the default.
This command configures how the IP address is defined for this host.
When the user database is used from a local DHCP server, then this command defines how to define the IP address the server will offer to the DHCP-client.
When the user-db is used for PPPoE authentication, the gi-address parameter cannot be used. A fixed IP address will then cause PPPoE to use this IP address. If no IP address is specified, the PPPoE looks for IP address by other means (DHCP). If a pool name is given, this pool will be sent in the DHCP request so that it can be used in by the DHCP server to determine which address to give to the host.
The no form of this command causes no IP address to be assigned to this host. In a user database referred to from a local DHCP server, creating a host without address information will cause the matching client never to get an IP address.
The no form of this command reverts to the default.
This command sets the domain name which can be appended to user-name in RADIUS-authentication-request message for the given host.
The no form of this command removes the domain name from the host configuration.
This command configures the authentication policy of this host and PPPoE hosts. This authentication policy is only used if no authentication policy is defined at the interface level. For DHCP hosts, the host entry should not contain any other information needed for setup of the host (IP address, ESM strings, and so on.). For PPPoE hosts, the authentication policy configured here must have its PPPoE authentication method set to pap-chap, otherwise the request is dropped.
The no form of this command reverts to the default.
This command configures the Diameter application policy.
The no form of this command reverts to the default.
This command is used to configure the Diameter NASREQ application policy to use for authentication.
The no form of this command reverts to the default.
This command allows selection of GI addresses based on the host entry in LUDB.
The gi-address must be a valid address (associated with an interface) within the routing context that received the DHCP message on the access side.
The no form of this command reverts to the default.
This command enables the context to configure host identification parameters.
This command specifies the circuit-id to match.
The no form of this command reverts to the default.
This command configures an ASCII string that uniquely identifies a host and is derived by a Python script from packet content available during a DHCP transaction.
The no form of this command reverts to the default.
This command specifies a range of encapsulation tag as the host identifications. The encapsulation tag is dot1q or qinq on Ethernet port; VPI/VCI on ATM port.
For dot1q, the start/end-tag is single number, range from 0-4094; for QinQ, the start/end-tag format is x.y, x or y could be “*”, which means ignore inner or outer tag;
For ATM the start/end-tag format is vpi/vci, vpi or vci could be “*”, which means ignore VPI or VCI.
![]() | Note: This command is only used when encap-tag-range is configured as one of the match-list parameters. |
The no form of this command reverts to the default.
start-tag | dot1q | qtag1 | |
qinq | (qtag1.qtag2 | qtag1.* | *.qtag2) | ||
atm | (vpi/vci | vpi/* | */vci) | ||
qtag1 | [0 to 4094] | ||
qtag2 | [0 to 4094] | ||
vpi | [0 to 4095] (NNI) | ||
[0 to 255] (UNI) | |||
vci | [1 to 65535] |
end-tag | dot1q | qtag1 | |
qinq | (qtag1.qtag2 | qtag1.* | *.qtag2) | ||
atm | (vpi/vci | vpi/* | */vci) | ||
qtag1 | [0 to 4094] | ||
qtag2 | [0 to 4094] | ||
vpi | [0 to 4095] (NNI) | ||
[0 to 255] (UNI) | |||
vci | [1 to 65535] |
This command specifies the source IPv4/IPv6 address/prefix of the data trigger packet as the host identification.
The no form of this command reverts to the default.
This command specifies the MAC address to match.
The no form of this command reverts to the default.
This command specifies the Vendor-Identifying Vendor Option to match. Option 60 is encoded as Type-Length-Value (TLV). The hex-string portion of Option 60 in the received DHCP request is used for matching. Only the first 32 bytes can be defined here. If Option 60 from the message is longer, those bytes are ignored.
The no form of this command reverts to the default.
This command specifies the remote ID of this host.
The no form of this command returns to the default.
This command specifies the SAP ID from the Nokia vendor-specific sub-option in Option 82 to match.
The no form of this command returns to the default.
This command specifies an existing service ID from the Nokia vendor-specific sub-option in Option 82 to match.
The no form of this command returns to the default.
This command specifies the string from the Nokia vendor-specific sub-option (VSO) in Option 82 to match.
The no form of this command returns to the default.
This command specifies the system ID from the Nokia vendor-specific sub-option in Option 82 to match.
The no form of this command returns to the default.
This command specifies identification strings for the subscriber. This is useful when the server is centralized with Enhanced Subscriber Management (ESM) in a lower level in the network. These strings will be parsed by a downstream Python script or they can be used literally if the strings-from-option option in the config>subscr-mgmt>sub-ident-policy context is set to this option number. In this case, the option number may be set to any allowed number (between 224 and 254 is suggested, as these are not dedicated to specific purposes). If the option number is not given, a default value of 254 is used. For PPPoE only, if the local user database is attached to the PPPoE node under the group interface and not to a local DHCP server, the strings will be used internally so the option number is not used.
The no form of this command returns to the default.
This command specifies the ANCP string which is encoded in the identification strings.
The no form of this command returns to the default.
This command specifies the application profile string which is encoded in the identification strings.
The no form of this command returns to the default.
This command specifies the category map name.
The no form of this command removes the category map name from the configuration.
This command specifies the intermediate destination identifier which is encoded in the identification strings.
The no form of this command returns to the default.
This command specifies the SLA profile string which is encoded in the identification strings.
The no form of this command returns to the default.
This command specifies the subscriber profile string which is encoded in the identification strings.
The no form of this command returns to the default.
This command specifies the ANCP string which is encoded in the identification strings.
The no form of this command returns to the default.
This command specifies the application profile string which is encoded in the identification strings.
The no form of this command returns to the default.
This command specifies the category map name.
The no form of this command removes the category map name from the configuration.
This command specifies the intermediate destination identifier which is encoded in the identification strings.
The no form of this command returns to the default.
This command specifies the SLA profile string which is encoded in the identification strings.
The no form of this command returns to the default.
This command configures the SLA Profile Instance (SPI) sharing group identifier for an IPoE or PPPoE session. It overrides the default SPI sharing method (def-instance-sharing) configured in the SLA profile.
When an spi-sharing-group-id is configured, the IPoE or PPPoE session shares the SLA Profile Instance with other IPoE or PPPoE sessions from the same subscriber that: have the same SLA profile associated, are active on the same SAP, and have the same group identifier.
Configuring an spi-sharing-group-id group-id for an IPoE host, when the IPoE session is disabled on the group interface, results in a setup failure.
The no form of this command returns the SPI sharing group identifier to its default.
This command specifies the subscriber profile string which is encoded in the identification strings.
The no form of this command returns to the default.
This command specifies the subscriber ID which is encoded in the identification strings.
The no form of this command returns to the default.
This command specifies the service name tag in PADI and/or PADR packets to match for PPPoE hosts.
The no form of this command returns to the default.
This command configures the IPoE mask.
The no form of this command removes the parameters from the mask configuration.
This string can only contain printable ASCII characters. The “*” character is a wildcard that matches any substring. If a “\” character is masked, use the escape key so it becomes “\\”.
This command configures the mask.
The no form of this command removes the parameters from the mask configuration.
This string can only contain printable ASCII characters. The “*” character is a wildcard that matches any substring. If a “\” character is masked, use the escape key so it becomes “\\”.
This command configures the IP address of the DHCP server to relay to.
The configured DHCP server IP address must reference one of the addresses configured under the DHCP CLI context of an IES/VPRN subscriber or group interface.
The no form of this command reverts to the default.
This command configures how the username is specified.
The no form of this command returns to the default.
This command enables the group-interface to snoop DHCPv6 relay messages exchange between the subscriber host and the DHCPv6 server. A successful DHCPv6 address assignment will trigger ESM DHCPv6 host creation and a release of the lease will trigger host deletion. This feature is for ESMv6 applications where a Layer 3 aggregation network is upstream from the BNG.
The no form of this command reverts to the default.
This feature is only applicable when DHCPv6-snooping is enabled. The Ethernet header MAC address on DHCPv6 is used as the default key host identification. This command allows addition the keys for identifying the DHCPv6 host. The interface-id can be included in addition to the MAC key to further differentiate each DHCPv6 host.
The no form of this command reverts to the default.
user-ident mac
This command specifies the interface where IPoE sessions are terminated.
The no version of this command disables the parameter.
This command configures static DHCPv6 IA-NA address for the host. This address is delegated to the client as /128 via DHCPv6 proxy function within the router. This IP address must not be part of any DHCP pool within internal DHCP server.
The no form of this command removes the IPv6 address from the host configuration.
ipv6-address: | ipv6-prefix x:x:x:x:x:x:x:x (eight 16-bit pieces) |
x:x:x:x:x:x:d.d.d.d | |
x [0 to FFFF]H | |
d [0 to 255]D |
This command configures static DHCPv6 IA-PD prefix for the host. This prefix can be further delegated by the host itself to its clients. The prefix length is restricted to 48 to 64 bits. This prefix must not be part of any DHCP pool within internal DHCP server.
ipv6-address: | ipv6-prefix x:x:x:x:x:x:x:x (eight 16-bit pieces) |
x:x:x:x:x:x:d.d.d.d | |
x [0 to FFFF]H | |
d [0 to 255]D | |
prefix-length | [48 to 64] |
This command allows configuration of delegated prefix length via local user database.
The no form of this command reverts to the default.
This command configures the pool name that will be used in DHCPv6 server for DHCPv6 IA-PD prefix selection.
The no form of this command removes the pool name from the configuration.
This command enables the context to configure lease times for DHCPv6.
This command specifies the preferred lifetime for the lease times. When the preferred lifetime expires, then any derived addresses are deprecated.
The no form of this command reverts to the default.
days days | 0 to 3650 |
hrs hours | 0 to 23 |
min minutes | 0 to 59 |
sec seconds | 0 to 59 |
This command configures the lease rebind timer (T2) via LUDB.
The T2 time is the time at which the client contacts any available addressing authority to extend the lifetimes of DHCPv6 leases. T2 is a time duration relative to the current time expressed in units of seconds.
The IP addressing authority controls the time at which the client contacts the addressing authority to extend the lifetimes on assigned addresses/prefixes through the T1 and T2 parameters assigned to an IA. At time T1 for an IA, the client initiates a Renew/Reply message exchange to extend the lifetimes on any addresses in the IA. The client includes an IA option with all addresses/prefixes currently assigned to the IA in its Renew message. Recommended values for T1 and T2 are .5 and .8 times the shortest preferred lifetime of the addresses/prefixes in the IA that the addressing authority is willing to extend, respectively.
The configured rebind timer should always be longer than or equal to the renew timer.
The T1 and T2 are carried in the IPv6 address option that is within the IA.
The no form of this command reverts to the default.
rebind-timer min 48
days days | 0 to 14 |
hrs hours | 0 to 23 |
min minutes | 0 to 59 |
sec seconds | 0 to 9 |
This command configures the lease renew time (T1) via LUDB.
The T1 is the time at which the client contacts the addressing authority to extend the lifetimes of the DHCPv6 leases (addresses or prefixes). T1 is a time duration relative to the current time expressed in units of seconds.
The IP addressing authority controls the time at which the client contacts the addressing authority to extend the lifetimes on assigned addresses through the T1 and T2 parameters assigned to an IA. At time T1 for an IA, the client initiates a Renew/Reply message exchange to extend the lifetimes on any addresses in the IA. The client includes an IA option with all addresses currently assigned to the IA in its Renew message. Recommended values for T1 and T2 are .5 and .8 times the shortest preferred lifetime of the addresses in the IA that the addressing authority is willing to extend, respectively.
The configured renew timer should always be smaller than or equal to the rebind timer.
The T1 and T2 are carried in the IPv6 address option that is within the IA.
The no form of this command reverts to the default.
renew-timer min 30
days days | 0 to 7 |
hrs hours | 0 to 23 |
min minutes | 0 to 59 |
sec seconds | 0 to 59 |
This command configured valid-lifetime for DHCPv6 lease (address/prefix).
The valid lifetime is the length of time an address/prefix remains in the valid state (for example., the time until invalidation). The valid lifetime must be greater than or equal to the preferred lifetime. When the valid lifetime expires, the address/prefix becomes invalid and must not be used in communications. RFC 2461, sec 6.2.1 recommends default value of 30 days.
Each address/prefix assigned to the client has associated preferred and valid lifetimes specified by the address assignment authority (DHCP server, RADIUS, ESM). To request an extension of the lifetimes assigned to an address, the client sends a Renew message to the addressing authority. The addressing authority sends a Reply message to the client with the new lifetimes, allowing the client to continue to use the address/prefix without interruption.
The lifetimes are transmitted from the addressing authority to the client in the IA option on the top level (not the address or prefix level).
The no form of this command reverts to the default.
valid-lifetime days 1
days days | 0 to 3650 |
hrs hours | 0 to 23 |
min minutes | 0 to 59 |
sec seconds | 0 to 9 |
This command configures static IPv6 SLAAC prefix (PIO) for the host. The host will assign an IPv6 address to itself based on this prefix. The prefix length is 64 bits.
The no form of this command removes the static IPv6 SLAAC prefix (PIO) for the host from the configuration.
no ipv6-slaac-prefix
<ipv6-prefix/prefi*> : ipv6-prefix x:x:x:x:x:x:x:x (eight 16-bit pieces) | |
x:x:x:x:x:x:d.d.d.d | |
x [0 to FFFF]H | |
d [0 to 255]D | |
prefix-length | 64 |
This command configures the IPv6 SLAAC prefix pool of this host.
The no form of this command reverts to the default.
This command configures the pool name that will be used in DHCPv6 server for DHCPv6 IA-PA address selection.
The no form of this command removes the pool name from the configuration.
This command configures the link address used for prefix selection at the DHCP server.
The link-address is a field in DHCP6 Relay-Forward message that is used in DHCP6 server to select the IPv6 address (IA-NA) or IPv6 prefix (IA-PD) from a pool with configured prefix range covering the link-address. The selection scope is the pool or a prefix range within the pool.
The no form of this command reverts to the default.
<ipv6-address> | ipv6-address - x:x:x:x:x:x:x:x (eight 16-bit pieces) |
x:x:x:x:x:x:d.d.d.d | |
x - [0 to FFFF]H | |
d - [0 to 255]D |
This command configures the IPv6 address of the DHCP6 server to relay to.
The configured DHCP6 server IPv6 address must reference one of the addresses configured under the DHCP6 CLI context of an IES/VPRN subscriber or group interface.
The no form of this command reverts to the default.
This command enables the context to configure RADIUS proxy cache match parameters.
This command specifies the action to take when no match is found in the cache.
The no form of this command reverts to the default.
fail-action drop
This command specifies how a MAC address is represented.
mac-format “aa:”
This command specifies in what DHCPv6 option to retrieve the value to be used as lookup key in the RADIUS proxy cache.
The no form of this command reverts to the default.
match mac
This command specifies the RADIUS proxy server.
The no form of this command reverts to the default.
This command enables the context to configure an MLD import policy.
This command configures an MLD import policy.
The LUDB allows a list of up to 14 MLD import policies per host. The MLD policy also allows the configuration of an additional import policy, providing a total of 15 MLD import policies per host. The import policy inside the MLD policy is always applied last, which determines if the list is a black list or a white list. To configure an MLD white list, the import policies in the LUDB should all be allowed or forward entries and the import policy in the MLD policy should have a default action to deny all. To configure a black list, the import policies inside the LUDB should drop entries and the MLD policy import policy default action should be to forward all. The 15 import policies can be configured to be a mixed white and black list. Since it is difficult to control the order of the import policies within the LUDB, it is recommended to provision the import policy inside the MLD policy first for deterministic behavior.
The no form of this command removes the specified import policy.
This command configures MSAP authentication defaults.
This command configures the group interface.
The no form of this command removes the group interface parameters from the configuration.
This command configures the MSAP policy.
The no form of this command removes the MSAP policy name from the configuration.
This command sets default service for all subscribers created based on trigger packets received on the given capture SAP in case the corresponding VSA is not included in the RADIUS authentication response. This command is applicable to capture SAP only.
The no form of this command reverts to the default.
This command configures the IPv6 address of the DNS server.
The no form of this command removes the IPv6 address from the DNS server configuration.
This command configures the default domain for a DHCP client that the router uses to complete unqualified host names (without a dotted-decimal domain name).
The no form of this command removes the name from the configuration.
This command enables the context to configure IPv6 DNS server information in the local user database
This command configures IPv6 DNS server addresses that can be used for name resolution
The no form of this command removes the IPv6 address from the dns-server configuration.
This command indicates the service ID of the retailer VPRN service to which this session belongs. If the value of this object is non-zero, the session belongs to a retailer VPRN.
The no form of this command removes the service ID from the configuration.
service-id: | 1 to 2147483647 |
service-name: | Service name up to 64 characters. |
This command sets the retail-service ID for a given subscriber host.
The no form of this command reverts to the default.
This command configures the RIP policy name. This policy is applied to a subscriber IPv4 host to enable the BNG to learn RIP routes from the host. RIP routes are never sent to the hosts.
The no form of this command removes the RIP policy name from the configuration
This command applies an RA policy to the host.
The no form of this command removes the policy from the configuration.
This command allows DHCP6 server selection based on the host entry in LUDB.
The configured DHCP6 server IP address must reference one of the v6 addressees configured under the config>service>vprn>sub-if>grp-if>ipv6>dhcpv6>relay or config>service>ies>sub-if>grp-if>ipv6>dhcpv6>relay context.
The no form of this command reverts to the default.
ipv6-address | ipv6-address - x:x:x:x:x:x:x:x (eight 16-bit pieces) x:x:x:x:x:x:d.d.d.d x - [0 to FFFF]H d - [0 to 255]D |
This command enables the context to configure DHCP options to send to the client.
This command configures DHCPv4 options via LUDB that are passed in all DHCP messages to the client. The options are blindly appended to any options already present in the DHCP message. In other words, there is no intelligent merging of the options where overlapping options from different sources are further evaluated to determine whether only one option or multiple options should be returned to the client.
Multiple DHCP options can be configured at the same time although each option requires its own option statement. Those options are equivalent to RADIUS VSAs Alc-ToCLient-Dhcp4-Options.
DHCPv4 options can be provided via DHCPv4 server in the relay case. In addition, DHCPv4 options provided via LUDB or RADIUS can be supplied and consequently appended to the already existing options. If DHCPv4 options are provided simultaneously via LUDB and RADIUS, the RADIUS as a source of DHCPv4 option is blocked and the options supplied via LUDB are passed to the client. This is valid for the relay and proxy case.
Any DHCP option may be encoded in the option statement. An example of the option statement for DHCPv4 default-gateway is given below:
option 3 192.168.1.254
DHCPv4 options may be fixed length or variable length. They are appended at the end of DHCPv4 messages. All options begin with a tag octet, which uniquely identifies the option. Fixed-length options without data consist of only a tag octet. Only options 0 and 255 are fixed length. All other options are variable-length.
The no form of the removes the option from the configuration.
This command enables the context to configure DHCP options to send to the server
This command specifies the DHCPv6 options to send to the server. There are four options:
The no form of this command removes the option parameters from the configuration.
This command enables the context to configure WPP parameters.
This command specifies the initial app-profile for the hosts created on the group-interface. This initial app-profile is replaced after hosts pass web portal authentication.
The no form of this command reverts to the default.
This command specifies the initial sla-profile for the hosts created on the group-interface. This initial sla-profile is replaced after hosts pass web portal authentication.
The no form of this command reverts to the default.
This command specifies the initial sub-profile for the hosts created on the group-interface. This initial sub-profile is replaced after hosts pass web portal authentication.
The no form of this command reverts to the default.
This command configures the portal for the portal group. This command is mutually exclusive with the portal-group command.
router-name: | Base, management |
service-id: | 1 to 2147483647 |
service-name: | Specifies the service name, up to 64 characters |
This command configures the WPP portal group name. This command is mutually exclusive with the portal command.
This command specifies that the initial profiles must be restored after a DHCP host has disconnected. The behavior that system will restore the initial-sla-profile, initial-sub-profile, or initial-app-profile when hosts disconnects instead of removing them.
The no form of this command specifies that the initial profiles will not be restored after a DHCP host has disconnected.
restore-disconnected
This command configures the mask.
The no form of this command removes the mask parameters from the configuration.
This string can only contain printable ASCII characters. The “*” character is a wildcard that matches any substring. If a "\" character is masked, use the escape key so it becomes "\\".
This string can only contain printable ASCII characters. The “*” character is a wildcard that matches any substring. If a "\" character is masked, use the escape key so it becomes "\\".
This command specifies local user database for PPP PAP/CHAP access.
With this configuration, system will access the specified DB again during PPP PAP/CHAP phase.
This configuration only becomes effective when system is accessing parent DB during PPPoE discovery phase.
The no form of this command removes the name from the configuration.
This command specifies the type of matching done to identify a host. There are different match-types for PPPoE or IPoE hosts of which a maximum of four can be specified.
The no form of this command reverts to the default.
![]() | Note: The format of remote-id in IPv6 is different that the format of remote-id in IPv4; IPv6 remote-id contains enterprise-id filed that is also honored in matching. |
dual-stack-remote-id — Specifies the enterprise-id in v6 Remote-id will be stripped off before LUDB matching is performed. Processing of IPv4 Remote-id remains unchanged. This will allow a single host entry in LUDB for dual-stack host where host identification is performed based on the Remote-id field.
sap-id — Specifies the SAP ID on which DHCPv4 packet are received. The sap-id is inserted as ALU VSO (82,9,4) by the DHCPv4 relay in router. This is enabled via configuration under the vendor-specific-option CLI hierarchy of the DHCPv4 relay. Since the dhcp-relay configuration is enabled under the group-interface CLI hierarchy, the group-interface and the service-id must be known before the sap-id can be used for LUDB match.
encap-tag-range — Specifies the VLAN tags.
ip — Specifies the source IPv4/IPv6 address of a data-trigger packet.
service-id — Specifies the service-id of the ingress SAP for DHCPv4 packets. The service-id is inserted as ALU VSO (82,9,3) by the DHCPv4 relay in router. This is enabled via configuration under the vendor-specific-option CLI hierarchy of the DHCPv4 relay.
string — Specifies the custom string configured under the vendor-specific-option CLI hierarchy of the DHCPv4 relay. The string is inserted as ALU VSO (82,9,5) by the DHCPv4 relay in router. Since the dhcp-relay configuration is enabled under the group-interface CLI hierarchy, the group-interface and the service-id must be known before the string can be used for LUDB match.
system-id — Specifies the system-id of the node name configured under the system>name CLI hierarchy. The system-id is inserted as ALU VSO (82,9,1) by the DHCPv4 relay in router. This is enabled via configuration under the vendor-specific-option CLI hierarchy of the DHCPv4 relay. Since the dhcp-relay configuration is enabled under the group-interface CLI hierarchy, the group-interface and the service-id must be known before the system-id can be used for LUDB match.
derived-id — Specifies the value extracted by Python script during processing of DHCP Discover/Solicit/Request/Renew/Rebind Messages (client to server bound messages). The value is stored in the DHCP Transaction Cache (DTC) in a variable named alc.dtc.derivedId. This value has a lifespan of a DHCP transaction (a single pair of messages exchanged between the client and the server, for example DHCP Discover and DHCP Offer).
This command enables the context to configure PPP host parameters.
This command enables the context to configure access loop information.
This command configures the egress encapsulation offset.
The no form of this command reverts to the default.
This command configures the last mile link downstream rate in the access loop.
The no form of this command reverts to the default.
This command enables the context to configure access loop information in the local user database.
This command specifies a circuit-id for PPPoE hosts. A circuit ID received in PPPoE tags has precedence over the LUDB specified circuit ID.
The no form of this command reverts to the default.
This command specifies a remote-id for PPPoE hosts. A remote-id received in PPPoE tags has precedence over the LUDB specified remote ID.
The no form of this command reverts to the default.
This command specifies if the IPv6 control protocol should be negotiated after PPP reaches the Network-Layer Protocol phase.
The no form of this command reverts to the default.
This command enables the context to configure L2TP parameters for the host.
This command configures the L2TP tunnel group. The tunnel-group-name is configured in the config>router>l2tp context. Refer to the 7450 ESS, 7750 SR, 7950 XRS, and VSR Router Configuration Guide.
This command configures the authentication policy for the host. A host name with name “default” will be matched when all other hosts do not match.
This command configures the PADI authentication policy of this host.
This command configures the delay timeout before sending a PPPoE Active Discovery Offer (PADO).
This command specifies a password type or configures password string for pap or chap. The pap and chap passwords are stored in a hashed format in the config files. The hash|hash2 optional keywords are used for config execution.
This command will only be interpreted if the local user database is connected directly to the PPPoE node under the VPRN/IES group interface. It is not used if the local user database is accessed by a local DHCP server.
The no form of this command reverts to the default.
This command configures the RADIUS pre-authentication policy to use to authenticate the PPP host.
The no form of this command reverts to the default.
This command configures the steering profile for the specific host.
The no form of this command removes the steering profile for the host.
When this command is enabled for a subscriber host, the do-not-fragment (DF) bit in the IPv4 header for frames egressing the subscriber interface is ignored, the frames are fragmented according the applicable egress MTU. The DF bit is reset for frames that are fragmented.
This command applies to PPPoE PTA and L2TP LNS frames only. It is not applicable for L2TP LAC frames.
This command configures the interface where PPP sessions are terminated.
The no form of this command reverts to the default.
This command allows the operator to customize the server-id attribute of a DHCPv6 message (such as DHCPv6 advertise and reply). By default, the server-id uses DUID-ll derived from the chassis link layer address. Operators have the option to use a unique identifier by using the duid-en (vendor based on an enterprise number). There is a maximum length associated with the customizable hex-string and ascii-string.
The no form of this command reverts to the default.
server-id duid-ll
This command specifies whether the prefix is assigned to an interface on the specified link.
The no form of this command reverts to the default.
This command configures a managed SAP policy. Managed SAPs allow the use of policies and a SAP template for the creation of a SAP.
The no form of this command removes the MSAP policy from the configuration.
This command enables the context to configure MSAP VPLS properties.
This command enables the context to configure DHCP parameters.
This command instantiates a local DHCP server. A local DHCP server can serve multiple interfaces but is limited to the routing context it was which it was created.
The no form of this command reverts to the default.
This command enables the context to configure failover parameters.
With this flag enabled, the remote IP address or prefix can be taken over immediately upon entering the PARTNER-DOWN state of the intercommunication link, without having to wait for the Maximum Client Lead Time (MCLT) to expire. By setting this flag, the lease times of the existing DHCP clients, while the intercommunication link is in the PARTNER-DOWN state, will still be reduced to the MCLT over time and all new lease times are set to MCLT. This behavior remains the same as originally intended for MCLT.
Some deployments require that the remote IP address/prefix range starts delegating new IP addresses and prefixes upon the failure of the intercommunication link, without waiting for the intercommunication link to transition from the COMM-INT state into the PARTNER-DOWN state and the MCLT to expire while in PARTNER-DOWN state.
This can be achieved by enabling the ignore-mclt-on-takeover flag and by configuring the partner-down-delay to 0.
Enabling this functionality must be exercised with caution. One needs to keep in mind that the partner-down-delay and MCLT timers were originally introduced to prevent IP address duplication in cases where DHCP redundant nodes transition out-of-sync due to the failure of intercommunication link. These timers (partner-down-delay and MCLT) would ensure that during their duration, the new IP addresses and prefixes are delegated only from one node, the one with local IP address-range/prefix. This causes the new IP address delegation to be delayed and the service is impacted.
If it can be assured that the intercommunication link is always available, then the DHCP nodes would stay in sync and the two timers would not be needed. Therefore, it is important that in this mode of operation, the intercommunication link is well protected by providing multiple paths between the two DHCP nodes. The only event that should cause intercommunication link to fail is the entire nodal failure. This failure is acceptable since in this case only one DHCP node is available to provide new IP addresses and prefixes.
The no form of this command reverts to the default.
The maximum-client-lead-time (MCLT) is the maximum time that a DHCP server can extend client’s lease time beyond the lease time currently known by the DHCP partner node. In dual-homed environment, the initial lease time for all DHCP clients is by default restricted to MCLT. Consecutive DHCP renews can extend the lease time beyond the MCLT.
The MCLT is a safeguard against IP address/prefix duplication in cases of a lease synchronization failure when local-remote failover model is deployed
Once the intercommunication link failure between the redundant DHCP servers is detected, the DHCP IP address range configured as remote will not be allowed to start delegating new leases until the MCLT + partner-down-delay intervals expire. This is to ensure that the new lease that was delegated from the local IP address-range/prefix on one node but was never synchronized due to the intercommunication link failure, will expire before the same IP address/prefix is allocated from the remote IP address-range/prefix on the other node.
However, the already existing (and synchronized) lease times can be renewed from the remote IP address range at any time, regardless of the state of the intercommunication link (operational or failed).
Lease synchronization failure can be caused either by a node failure, or a failure of the link over which the DHCP leases are synchronized (intercommunication link). Synchronization failure detection can take up to 3 seconds.
During the failure, the DHCP lease time for the new clients is restricted to MCLT while for the existing clients the lease time will over time (by consecutive DHCP renews) be gradually reduced to the MCLT.
The no form of this command reverts to the default.
maximum-client-lead-time min 10
hrs hours | 1 to 23 |
min minutes | 1 to 59 |
sec seconds | 1 to 59 |
This command configures the partner down delay time. Since the DHCP lease synchronization failure can be caused by the failure of the intercommunication link (and not necessary the entire node), there is a possibility the redundant DHCP servers become isolated in the network. In other words, they can serve DHCP clients but they cannot synchronize the lease. This can lead to duplicate assignment of IP addresses, since the servers have configured overlapping IP address ranges but they are not aware of each other’s leases.
The purpose of the partner down delay is to prevent the IP lease duplication during the intercommunication link failure by not allowing new IP addresses to be assigned from the remote IP address range. This timer is intended to provide the operator with enough time to remedy the failed situation and to avoid duplication of IP addresses or prefixes during the failure.
During the partner-down-delay time, the prefix designated as remote is eligible only for renewals of the existing DHCP leases that have been synchronized by the peering node. Only after the sum of the partner-down-delay and the maximum-client-lead-time will the prefix designated as remote be eligible for delegation of the new DHCP leases. When this occurs, we say that the remote IP address range has been taken over.
It is possible to expedite the takeover of a remote IP address range so that the new IP leases can start being delegated from that range shortly after the intercommunication failure is detected. This can be achieved by configuring the partner-down-delay timer to 0 seconds, along with enabling the ignore-mclt-on-takeover CLI flag. Caution must be taken before enabling this functionality. It is safe to bypass safety timers (partner-down-delay + MCLT) only in cases where the operator is certain that the intercommunication between the nodes has failed due to the entire node failure and not due to the intercommunication (MCS) link failure. Failed intercommunication due to the nodal failure would ensure that only one node is present in the network for IP address delegation (as opposed to two isolated nodes with overlapping IP address ranges where address duplication can occur). For this reason, the operator must ensure that there are redundant paths between the nodes to ensure uninterrupted synchronization of DHCP leases.
In access-driven mode of operation, partner-down-delay has no effect.
The no form of this command reverts to the default.
partner-down-delay hrs 23 min 59 sec 59
hrs hours | 1 to 23 |
min minutes | 1 to 59 |
sec seconds | 0 to 59 |
This command creates a sync tag. DHCP leases can be synchronized per DHCP server or DHCP pool. The pair of synchronizing servers or pools is identified by a tag. The synchronization information is carried over the Multi-Chassis Synchronization (MCS) link between the two peers. MCS link is a logical link (IP, or MPLS).
MCS runs over TCP, port 45067 and it is using either data traffic or keepalives to detect failure on the communication link between the two nodes. In the absence of any MCS data traffic for more than 0.5sec, MCS will send its own keepalive to the peer. If a reply is not received within three sec, MCS will declare its operation state as DOWN and the DB Sync state as out-of-sync. MCS will consequently notify its clients (DHCP Server being one of them) of this. It can take up to three seconds before the DHCP client realizes that the inter-chassis communication link has failed.
The inter-chassis communication link failure does not necessarily assume the same failed fate for the access links. The two redundant nodes can become isolated from each other in the network. This occurs when only the intercommunication (MCS) link fails. It is important that this MCS link be highly redundant.
The no form of this command reverts to the default.
This command enables the startup wait time during which each peer waits after the initialization process before assuming the active role for the prefix designated as local or access-driven. This is to avoid transient issues during the initialization process.
The startup-wait-time should be configured to an interval in which, after boot, both nodes can set up an MCS TCP link and start MCS. The timer is restarted each time the server downloads a lease from the MCS database and stops when the last state record from the peer is synchronized. The next state is (PRE-)NORMAL, unless the timer times out or is forced to stop via the tools command (tools>perform>router>dhcp or dhcp6>local-dhcp-server server-name>pool/failover>abort-startup-wait), in which case the local DHCP server transitions immediately to the COMMUNICATIONS-INTERRUPTED state.
startup-wait-time min 2
This command enables the sending of sending FORCERENEW messages for DHCP.
The no form of this command disables the sending of FORCERENEW messages.
This command configures the time to remember this lease and is applicable for unsolicited release conditions such as lease timeout if the lease-hold-time-for command is set to the default value no solicited-release and is additionally applicable for normal solicited releases from DHCP clients if the lease-hold-time-for command is set to solicited-release.
The no form of this command reverts to the default.
lease-hold-time sec 0
days days | 0 to 7305 |
hrs hours | 0 to 23 |
min minutes | 0 to 59 |
sec seconds | 0 to 59 |
This command enables the context to configure lease-hold-time-for parameters which define additional types of lease or triggers that cause system to hold up leases.
The no form of this command reverts to the default.
This command enables the server to hold up the lease of local IPsec clients.
The no form of this command disables the ability of the server to hold up the lease of local IPsec clients.
This command enables the server to hold up a lease even in case of solicited release; for example, when the server receives a normal DHCP release message.
The no form of this command disables the ability of the server to hold up a lease when a solicited release is received.
This command configures a DHCP address pool on the router.
The no form of this command removes the pool name from the configuration.
This command configures the maximum lease time.
The no form of this command reverts to the default.
max-lease-time days 10
days days | 0 to 3650 |
hrs hours | 0 to 23 |
min minutes | 0 to 59 |
sec seconds | 0 to 59 |
This command configures the minimum lease time.
The no form of this command reverts to the default.
min-lease-time min 10
days days | 0 to 3650 |
hrs hours | 0 to 23 |
min minutes | 0 to 59 |
sec seconds | 0 to 59 |
This command specifies the desired minimum number of free addresses in this pool.
The no form of this command reverts to the default.
minimum-free 1
With this command, if the local DHCPv4 server receives a DHCP request with option 50 (means client try to request a previous allocated message as described in section 3.2 of RFC 2131, Dynamic Host Configuration Protocol) and the address allocation algorithm ends up using a pool and the address in option50 is not in pool, then system will return a DHCP NAK, otherwise system just drop the DHCP packet.
The no form of this command reverts to the default.
no nak-non-matching-subnet
This command configures the time interval during which a DHCP offer is valid.
The no form of this command reverts to the default.
offer-time min 1
min minutes | 0 to 10 |
sec seconds | 0 to 59 |
This command enables the context to configure pool options. The options defined here can be overruled by defining the same option in the local user database.
This command configures specific DHCP options. The options defined here can overrule options in the local user database.
The no form of the removes the custom option parameters from the configuration.
This command configures the IP address of the default router for a DHCP client. Up to four IP addresses can be specified.
The no form of this command removes the address(es) from the configuration.
This command configures the time the client transitions to a rebinding state for a DHCP client.
The no form of this command removes the time from the configuration.
days days | 0 to 3650 |
hrs hours | 0 to 23 |
min minutes | 0 to 59 |
sec seconds | 0 to 59 |
This command configures the time the client transitions to a renew state for a DHCP client.
The no form of this command removes the time from the configuration.
days: | 0 to 3650 |
hours: | 0 to 23 |
minutes: | 0 to 59 |
seconds | 0 to 59 |
This command configures the amount of time that the DHCP server grants to the DHCP client permission to use a specific IP address.
The no form of this command removes the lease time parameters from the configuration.
days days | 0 to 3650 |
hrs hours | 0 to 23 |
min minutes | 0 to 59 |
sec seconds | 0 to 59 |
This command configures up to four Network Basic Input/Output System (NetBIOS) name server IP addresses for a DHCP client.
The no form of this command removes the IP address from the netbios-name-server configuration.
This command configures the Network Basic Input/Output System (NetBIOS) node type.
The no form of this command removes the netbios node type parameters from the configuration.
This command creates a subnet of IP addresses to be served from the pool. The subnet cannot include any addresses that were assigned to subscribers without those addresses specifically excluded. When the subnet is created, no IP addresses are made available until a range is defined.
The no form of the removes the subnet parameters from the configuration.
![]() | Note: A mask of 255.255.255.255 is reserved for system IP addresses. |
This command configures a range of IP addresses to be served from the pool. All IP addresses between the start and end IP addresses will be included (other than specific excluded addresses).
The no form of this command removes the address-range parameters from the configuration.
This command means no new leases can be assigned from this subnet and existing leases are cleaned up upon renew/rebind.
The no form of this command means the subnet is active and new leases can be assigned from it.
This command specifies a range of IP addresses that excluded from the pool of IP addresses in this subnet.
The no form of the removes the parameters from the configuration.
This command configures the maximum number of declined addresses allowed.
The no form of the reverts to the default.
maximum-declined 64
This command configures the minimum number of free addresses in this subnet. If the actual number of free addresses in this subnet falls below this configured minimum, a notification is generated.
The no form of the reverts to the default.
minimum-free 1
This command specifies the subnet-mask option to the client. The mask can either be defined (for supernetting) or taken from the pool address.
The no form of this command removes the address from the configuration.
This command enables the use of gi-address matching. If the gi-address flag is enabled, a pool can be used even if a subnets is not found. If the local-user-db-name is not used, the gi-address flag is used and addresses are handed out by GI only. If a user must be blocked from getting an address the server maps to a local user database and configures the user with no address.
A pool can include multiple subnets. Since the GI is shared by multiple subnets in a subscriber interface the pool may provide IP addresses from any of the subnets included when the GI is matched to any of its subnets. This allows a pool to be created that represents a sub-int.
The no form of the reverts to the default.
This command enables the use of the pool indicated by DHCP client. When enabled, the IP address pool to be used by this server is the pool is indicated by the vendor-specific sub-option 13 of the DHCP option 82. When disabled or if there is no sub-option 13 in the DHCP message, the pool selection falls back to the use-gi-address configuration.
The no form of this command disables the use of the pool indicated by DHCP client.
This command configures a local user database for authentication.
The no form of this command reverts to the default.
This command configures the user identification method for the DHCPv4 server.
The no form of the reverts to the default.
user-ident mac-circuit-id
This command instantiates a DHCP6 server. A local DHCP6 server can serve multiple interfaces but is limited to the routing context it was which it was created.
The no form of this command reverts to the default.
If enabled, the local DHCPv6 server will handle and reply to lease query messages.
The no form of this command disables lease query support.
This command configures server default timer and option values. These can be overridden on a per-pool and per-prefix basis.
This command configures the default preferred lifetime.
The no form of this command reverts to the default value.
preferred-lifetime hrs 1
days days | 0 to 3650 |
hrs hours | 0 to 23 |
min minutes | 0 to 59 |
sec seconds | 0 to 59 |
This command configures the default rebind timer.
The no form of this command reverts to the default.
rebind-timer sec 0
days days | 0 to 14 |
hrs hours | 0 to 23 |
min minutes | 0 to 59 |
sec seconds | 0 to 9 |
This command configures the default renew timer
The no form of this command reverts to the default.
renew-timer min 30
days days | 0 to 7 |
hrs hours | 0 to 23 |
min minutes | 0 to 59 |
sec seconds | 0 to 59 |
This command configures the valid lifetime.
The no form of this command reverts to the default.
valid-lifetime days 1
days days | 0 to 3650 |
hrs hours | 0 to 23 |
min minutes | 0 to 59 |
sec seconds | 0 to 9 |
This command enables the Rapid Commit Option for DHCP6.
The no form of this command disables the Rapid Commit Option.
If enabled, this command enables the behavior where unique /64 prefix is allocated per interface-id, and all clients having the same interface-id get an address allocated out of this /64 prefix for DHCP6. This is relevant for bridged clients behind the same local-loop (and same SAP), where sharing the same prefix allows communication between bridged clients behind the same local-loop to stay local. For SLAAC based assignment, downstream neighbor-discovery is automatically enabled to resolve the assigned address.
The no form of this command reverts to the default.
This command configures the delegated prefix length that is used if the DHCPv6 client does not specify a prefix length hint.
The DHCPv6 client prefix length hint is limited by the range specified by the minimum and maximum parameters. If the hint is smaller than the minimum, the allocated prefix length is equal to the minimum length. If the hint is larger than the maximum, the allocated prefix length is equal to the maximum length.
The no form of this command reverts to the default.
delegated-prefix-length 64 minimum 48 maximum 64
This command defines a prefix that to be excluded from available prefix in the pool for DHCP6. The typical use case is to exclude the interface address.
The no form of this command removes the prefix that is to be excluded from available prefix in the pool.
ipv6-prefix | x:x:x:x:x:x:x:x (eight 16-bit pieces) | |
x:x:x:x:x:x:d.d.d.d | ||
x - [0 to FFFF]H | ||
d - [0 to 255]D | ||
prefix-length | [0 to 128] |
This command configures specific DHCP6 options. The options defined here can overrule options in the local user database.
The no form of the removes the custom option parameters from the configuration.
This command allocates a prefix to a pool from which Prefix Delegation prefixes and or WAN addresses can be assigned for DHCP6.
The no form of this command removes the prefix parameters from the configuration.
prefix failover local
ipv6-address | x:x:x:x:x:x:x:x (eight 16-bit pieces) | |
x:x:x:x:x:x:d.d.d.d | ||
x [0 to FFFF]H | ||
d [0 to 255]D | ||
prefix-length | [1 to 128] |
This command enables the system to send out a warning when the prefix with a configured length is no long available in the provisioned prefix.
For example:
With the above configuration, the system will send out a warning when there is no available /64 that can be allocated out of 2001:0:0:ffe0::/50.
The no form of this command disables the warnings.
This command enables the context to configure pool level thresholds.
thresholds
This command creates a threshold for a given prefix length on the pool level. Up to 128 thresholds could be created. For example, with minimum-free prefix-length 64, then the usage of /64 prefix in the pool is counted.
There are two types of thresholds that could be defined at the pool level:
Configuring this command also enables the system stats collection for configure prefix length, which could be displayed with the show router router-id dhcp6 local-dhcp-server dhcp6-server-name pool-threshold-stats command.
The no form of this command removes the prefix-length from the configuration.
This command enables the system to send out warnings when the prefix with the configured length is no long available in the pool.
The no form of this command disables the warnings.
This command specifies a percentage based threshold which represent the minimal available percentage of the prefix with configured length in the pool. The system will send out a warning if the actual percentage is lower than the configured percentage.
The no form of this command removes the percentage from the configuration.
This command configures a percentage-based or number-based threshold which represents the minimal available percentage or number of the prefix with a configured length in the provisioned prefix. The system will send out a warning if the actual percentage or number is lower than the configured threshold.
For example:
With the above configuration, the system will send a warning when the number of available /64 in prefix 2001:0:0:ffe0::/50 is less than 3.
The no form of this command removes the command parameters from the configuration.
This command configures the local pool selection for IPv6 address or prefix assignment for the configured link-address under relay configuration. The selected pool will contain a prefix covering the link-address. The scope option defines the scope for the match. With scope subnet, the prefix or address selection is limited to the prefix in the pool that covers the link-address. With scope pool, all the prefixes in the selected pool are eligible for assignment.
The no form of the reverts to the default.
scope subnet
This command configures the keys for identification of the DHCPv6 lease being held in the lease-database (for configured period after lease timeout). Subscriber requesting a lease via DHCPv6 that matches an existing lease based on this configured key is handed the matched prefix or address. This allows address and prefix “stickiness” for DHCPv6 assigned prefixes (IA_NA or PD).
The no form of the reverts to the default.
user-ident duid
This command enables the context to configure DHCP parameters.
This command configures the gateway interface address for the DHCP relay. A subscriber interface can include multiple group interfaces with multiple SAPs. The GI address is needed, when the router functions as a DHCP relay, to distinguish between the different subscriber interfaces and potentially between the group interfaces defined.
By default, the GI address used in the relayed DHCP packet is the primary IP address of a normal IES interface. Specifying the GI address allows the user to choose a secondary address. For group interfaces a GI address must be specified under the group interface DHCP context or subscriber-interface DHCP context in order for DHCP to function.
The no form of this command reverts to the default.
This command enables the context to configure DHCP6 parameters.
This command enables DHCP relay and proxy-server for the configured client types.
The no form of this command reverts to the default.
dhcp
This command enables Option 82 circuit ID on relayed DHCP packet matching. For routed CO, the group interface DHCP relay process is stateful. When packets are relayed to the server the virtual router ID, transaction ID, SAP ID, and client hardware MAC address of the relayed packet are tracked.
When a response is received from the server the virtual router ID, transaction ID, and client hardware MAC address must be matched to determine the SAP on which to send the packet out. In some cases, the virtual router ID, transaction ID, and client hardware MAC address are not guaranteed to be unique.
When the match-circuit-id command is enabled this as part of the key is used to guarantee correctness in our lookup. This is only needed when dealing with an IP aware DSLAM that proxies the client hardware MAC address.
The no form of this command disables Option 82 circuit ID on relayed DHCP packet matching.
This command enables and disables dynamic host DHCPv4 lease state management for SAPs.
For VPLS, DHCP snooping must be explicitly enabled (using the snoop command) at all points where DHCP messages requiring snooping enter the VPLS instance (both from the DHCP server and from the subscribers). Lease state information is extracted from snooped DHCP ACK messages to populate lease state table entries for the SAP.
The optional number-of-entries parameter defines the number lease state table entries allowed.
If number-of-entries is omitted, only a single entry is allowed. Once the maximum number of entries has been reached, subsequent lease state entries are not allowed and subsequent DHCP ACK messages are discarded.
The retained lease state information representing dynamic hosts may be used to:
The no form of this command reverts to the default.
This command enables neighbor resolution with DHCPv6 relay.
The no form of this command disables neighbor resolution.
This command enables the context to configure DHCPv6 relay information options.
The no form of this command disables DHCPv6 relay information options.
This command enables the sending of remote ID option in the DHCPv6 relay packet.
The client DHCP Unique Identifier (DUID) is used as the remote ID.
The no form of this command disables remote ID.
This command enables the sending of interface ID options in the DHCPv6 relay packet.
The no form of this command disables the sending of interface ID options in the DHCPv6 relay packet
This command configures a proxy neighbor discovery policy for the interface. This policy determines networks and sources for which proxy ND is attempted, when local proxy neighbor discovery is enabled.
The no form of this command reverts to the default value.
The specified name(s) must already be defined.
This command enables DHCP Option 82 (Relay Agent Information Option) parameters processing and enters the context for configuring Option 82 sub-options.
The no form of this command reverts to the default.
This command configures the Relay Agent Information Option (Option 82) processing.
The no form of this command reverts to the default.
The default is to keep the existing information intact.
When enabled, the router sends an ASCII-encoded tuple in the circuit-id sub-option of the DHCP packet. This ASCII-tuple consists of the access-node-identifier, service-id, and SAP-ID, separated by “|”.
To send a tuple in the circuit ID, the action replace command must be configured in the same context.
If disabled, the circuit-id sub-option of the DHCP packet will be left empty.
The no form of this command reverts to the default.
circuit-id ascii-tuple
This command specifies what information goes into the remote-id sub-option in the DHCP relay packet.
If disabled, the remote-id sub-option of the DHCP packet will be left empty.
The no form of this command reverts to the default.
This command enables the Nokia vendor-specific sub-option of the DHCP relay packet.
The no form of this command reverts to the default.
This command enables the sending of the MAC address in the Nokia vendor-specific sub-option of the DHCP relay packet.
The no form of this command disables the sending of the MAC address in the Nokia vendor-specific sub-option of the DHCP relay packet.
This command enables the sending of the SAP ID in the Nokia vendor-specific sub-option of the DHCP relay packet.
The no form of this command disables the sending of the SAP ID in the Nokia vendor-specific sub-option of the DHCP relay packet.
This command enables the sending of the service ID in the Nokia vendor-specific sub-option of the DHCP relay packet.
The no form of this command disables the sending of the service ID in the Nokia vendor-specific sub-option of the DHCP relay packet.
This command specifies the string in the Nokia vendor-specific sub-option of the DHCP relay packet.
The no form of this command reverts to the default.
This command specifies whether the system-id is encoded in the Nokia vendor-specific sub-option of Option 82.
The no form of this command reverts to the default.
This command enables the context to configure DHCP proxy server parameters.
This command allows access to the DHCP6 proxy server context. Within this context, DHCP6 proxy server parameters of the group interface can be configured.
no proxy-server
This command configures the IP address which will be used as the DHCP server address in the context of the SAP. Typically, the configured address should be in the context of the subnet represented by the service.
The no form of this command reverts to the default setting. The local proxy server will not become operational without the emulated-server address being specified.
The no form of this command reverts to the default.
This command defines the length of lease-time that will be provided to DHCP clients. By default, the local-proxy-server always makes use of the lease time information provide by either a RADIUS or DHCP server.
The no form of this command disables the use of the lease-time command. The local-proxy-server will use the lease-time offered by either a RADIUS or DHCP server.
7 days 0 hours 0 seconds
This command sends the pool name in the Nokia vendor specific sub-option of the DHCP relay packet.
The no form of this command reverts to the default.
This command allows a DHCP IA_NA address to override and replace a host existing SLAAC address. When this feature is enabled, a subscriber SLAAC address is removed once the DHCP IA_NA address assignment is completed. If used with conjunction with the allow-multiple-wan-address command, the DHCP IA_NA address will also override the SLAAC address.
This command enables DHCP IA-PD (delegated prefix) to be modeled as managed (framed) route instead of as a subscriber-host. Antispoof filtering for the subscriber host associated with the IA-PD route must be set to nh-mac. The subscriber specific parameters (such as sla-profile or sub-profile) will be ignored during the authentication phase because IA-PD is not modeled as a subscriber host. Other subscriber host-specific functions (for example, host overrides via CoA or host accounting) are not possible with a PD as the managed route.
By default, or when configured with the next-hop ipv6 parameter, the next-hop for PD managed route is an IPv6 WAN sub-host (DHCP IA-NA or SLAAC) with the same mac address as the one in the DHCP lease state for the managed IA-PD. The DHCP IA-NA next-hop host will always override the SLAAC next-hop host if both are available. If the IPv6 next-hop is not present when the framed IA-PD is instantiated, the IA-PD will be set up but the PD managed route will not be installed in the IPv6 route table and the DHCPv6 lease state for the IA-PD will have the managed route status (DHCP6 MRt Status) set to “noNextHop”.
When configured with the next-hop ipv4 parameter the next-hop for PD managed route is a DHCPv4 sub-host that belongs to the same IPoE session or PPPoE session. For IPoE, ipoe-session must be enabled on the group-interface. If ipoe-session is disabled, an IPv4 next-hop will not be found. If the IPv4 next-hop is not found or not present at the time when the framed IA-PD is instantiated, the IA-PD will be set up but the PD managed route will not be installed in the IPv6 route table. In this case, the DHCPv6 lease state for the IA-PD will have the managed route status (DHCP6 MRt Status) set to noNextHop.
![]() | Note: IPv6 filters, QoS IPv6 criteria, and IPv6 multicast are not supported for DHCPv6 IA-PD as managed route pointing to an IPv4 subscriber host as next-hop. |
The DHCP IA-PD modeled as a route is displayed differently than regular subscriber hosts in show commands related to subscriber host state. The PD managed route is always shown directly below the host it is using as the next hop. The forwarding status of the PD managed route is also shown, where (N) indicate that the PD managed route is not forwarding. In addition, DHCP IA-PD route is displayed as a managed route for the corresponding IPv6 subscriber host (DHCP IA-NA or SLAAC) or DHCPv4 subscriber host.
DHCP IA-PD information for managed IA-PD route is still maintained in the DHCPv6 lease state.
The no form of this command reverts to the default.
This command enables the collection of ingress interface IP stats. This command is only applicable to IP statistics, and not to uRPF statistics.
If enabled, then the following statistics are collected:
Octet statistics for IPv4 and IPv6 bytes at IP interfaces include the Layer 2 frame overhead.
The no form of the reverts to the default.
This command configures the DHCP Unique Identifier (DUID) of the DHCP client.
The no form of this command reverts to the default.
duid 2
This command configures the IPv6 prefix/mask preferred life time. The preferred-lifetime value cannot be bigger than the valid-lifetime value.
The no form of this command reverts to the default value.
preferred-lifetime 604800 (7 days)
This command specifies the remaining time for this prefix to be preferred, thus time until deprecation.
The no form of this command reverts to the default.
preferred-lifetime 3600
This command specifies the remaining time for this prefix to be preferred, thus time until deprecation.
The no form of this command reverts to the default.
preferred-lifetime 3600
days | 0 to 3650 |
hours | 0 to 23 |
minutes | 0 to 59 |
seconds | 0 to 59 |
This command configures the valid lifetime for the IPv6 prefix or address in the option.
The no form of this command reverts to the default.
valid-lifetime days 1
days days | 0 to 49710 |
hrs hours | 0 to 23 |
min minutes | 0 to 59 |
sec seconds | 0 to 5 |
This command specifies the python-policy to be used for DHCPv4 relay.
The no form of this command reverts to the default.
This command specifies the python-policy to be used for DHCPv6 relay.
The no form of this command reverts to the default.
This command enables the context to configure DHCPv6 relay parameters for this interface.
This command enables snooping of DHCP or DHCP6 messages on the SAP or SDP. Enabling DHCP or DHCP6 snooping on interfaces (SAPs and SDP bindings) is required where DHCP or DHCP6 messages important to lease state table population are received, or where Option 82 information is to be inserted. This includes interfaces that are in the path to receive messages from either DHCP or DHCP6 servers or from subscribers.
The no form of this command disables DHCP or DHCP6 snooping on the specified SAP or SDP binding.
This command enabled access to LUDB for DHCPv4 hosts under the capture SAP. The name of this local user database must match the name of local user database configured under the config>service>vprn/ies>sub-if>group-if>dhcp hierarchy.
This command specifies the name of the Python policy. The Python policy is created in the config>python>python-policy name context.
The no form of this command reverts to the default.
This command enables the context to configure DHCP6 parameters. Within this context, DHCP6 parameters can be configured.
This command enters the context to configure DHCPv6 relay information options.
The no form of this command disables DHCPv6 relay information options.
This command enables the sending of interface ID options in the DHCPv6 relay packet.
The no form of this command disables the sending of interface ID options in the DHCPv6 relay packet
This command enables the sending of remote ID option in the DHCPv6 relay packet.
The client DHCP Unique Identifier (DUID) is used as the remote ID.
The no form of this command disables the sending of remote ID option in the DHCPv6 relay packet.
This command enabled access to LUDB for DHCPv6 hosts under the capture SAP. The name of this LUDB must match the name of the LUDB configured under the config>service>vprn/ies>sub-if>grp-if>dhcp hierarchy.
The no form of this command reverts to the default.
This command enabled access to LUDB for PPPoE and PPPoEoA v4and v6 hosts under the capture SAP. The name of this local user database must match the name of local user database configured under the config>service>vprn/ies>sub-if>grp-if>pppoe hierarchy.
The no form of this command reverts to the default.
This command enabled access to LUDB for PPPoE and PPPoEoA v4and v6 hosts under the capture SAP. The name of this LUDB must match the name of the LUDB configured under the config>service>vprn/ies>sub-if>grp-if>pppoe hierarchy.
The no form of this command reverts to the default.
This command assigns a DHCP filter to the group-interface. This feature is used where the SR 7750 is the second DHCP relay or where DHCP messages are snooped for subscriber management. The filter can be used to bypass host creation, drop DHCP message, or perform no action.
The no form of this command reverts to the default.
This command assigns a DHCP6 filter to the group interface. This feature is used where the SR 7750 is the second DHCP6 relay or where DHCP6 messages are snooped for subscriber management. The filter can be used to bypass host creation, drop DHCP6 message, or perform no action.
The no form of this command reverts to the default.
This command enables anti-spoof filtering and optionally changes the anti-spoof matching type for the SAP.
The type of anti-spoof filtering defines what information in the incoming packet is used to generate the criteria to lookup an entry in the anti-spoof filter table. The type parameter (ip, mac, ip-mac) defines the anti-spoof filter type enforced by the SAP when anti-spoof filtering is enabled.
The no form of this command disables anti-spoof filtering on the SAP.
This command enables the relaying of plain BOOTP packets.
The no form of this command disables the relaying of plain BOOTP packets.
This command enables the DHCPv4 relay proxy function on the interface. The command has no effect when no dhcp servers are configured (DHCPv4 relay not configured). By default, unicast DHCPv4 release messages are forwarded transparently.
A relay proxy enhances the relay such that it also relays unicast client DHCPv4 REQUEST messages (lease renewals).
The optional release-update-src-ip parameter updates the source IP address of a DHCP RELEASE message with the address used for relayed DHCPv4 messages.
The optional siaddr-override ip-address parameter enables DHCP server IP address hiding towards the client. This parameter requires that lease-populate is enabled on the interface. The DHCP server ip address is required for the address hiding function and is stored in the lease state record. The client interacts with the relay proxy as if it is the DHCP server. In all DHCP messages to the client, the value of following header fields and DHCP options containing the DHCP server IP address is replaced with the configured <ip-address>:
DHCP OFFER selection during initial binding is done in the relay-proxy. Only the first DHCP OFFER message is forwarded to the client. Subsequent DHCP OFFER messages from different servers are silently dropped.
This command specifies a list of servers where DHCP6 requests will be forwarded. The list of servers can be entered as either IP addresses or fully qualified domain names. There must be at least one server specified for DHCP6 relay to work. If there are multiple servers then the request is forwarded to all servers in the list.
The no form of this command reverts to the default.
ipv6-address: | x:x:x:x:x:x:x:x (eight 16-bit pieces) |
x:x:x:x:x:x:d.d.d.d | |
x: [0 to FFFF]H | |
d: [0 to 255]D |
This command specifies a list of servers where requests will be forwarded. The list of servers can be entered as either IP addresses or fully qualified domain names. There must be at least one server specified for DHCP relay to work. If there are multiple servers then the request is forwarded to all servers in the list.
There can be a maximum of 8 DHCP servers configured.
The no form of this command reverts to the default.
This command enables a virtual-subnet for DHCPv4 hosts under the subscriber-interface. With this command configured, the system will snoop and record the default router address in the DHCP ACK message for the DHCPv4 ESM host. The system could answer ping or traceroute request even if the default router address is not configured on the subscriber-interface.
The no form of this command reverts to the default.
This command enables the context to configure local address assignment parameters.
This command enables local DHCP Server pool management for PPPoXv4 clients. A pool of IP addresses can be shared between IPoE clients that rely on DHCP protocol (lease renewal process) and PPPoX clients where address allocation is not dependent on DHCP messaging but instead an IP address allocation within the pool is tied to the PPPoX session.
This command references a default DHCP address pool for local PPPoX pool management in case that the pool-name is not returned via Radius or LUDB.
This command designates a local DHCPv4 server for local pools management where IPv4 addresses for PPPoXv4 clients will be allocated without the need for the internal DHCP relay-agent. Those addresses will be tied to PPPoX sessions and they will be de-allocated when the PPPoX session is terminated.
This command enables the relaying of plain BOOTP packets.
The no form of this command disables the relaying of plain BOOTP packets.
This command enables the use of ARP to determine the destination hardware address.
The no form of this command disables the use of ARP to determine the destination hardware address.
This command configures the local user database to use for PPP PAP/CHAP authentication
The no form of this command reverts to the default.
This command enables relaying untrusted packets. According to RFC 3046, DHCP Relay Agent Information Option, a DHCP request where the giaddr is 0.0.0.0 and which contains an Option 82 field in the packet, should be discarded, unless it arrives on a “trusted” circuit. If the trusted mode is enabled on an IP interface, the Relay Agent (the router) modifies the request's giaddr to be equal to the ingress interface and forward the request.
![]() | Note: This behavior only applies when the action in the Relay Agent Information Option is keep. In the case where the option 82 field is being replaced by the Relay Agent (action = replace), the original Option 82 information is lost anyway, and thus, there is no reason for enabling the trusted option. |
The no form of this command reverts to the default.
This command enables the context to configure IPv6 parameters for the interface.
This command assigns an IPv6 address to the IES interface.
The no form of this command reverts to the default.
ipv6-address | x:x:x:x:x:x:x:x (eight 16-bit pieces) |
x:x:x:x:x:x:d.d.d.d | |
x [0 to FFFF]H | |
d [0 to 255]D | |
prefix-length | 1 to 128 |
This command enables host to have two WAN addresses, one from DHCP IA_NA and one from SLAAC assignment.
The no form of this command reverts to the default.
This command assists IP-only static hosts to resolve their default gateway and MAC. By default, the BNG anti-spoof filter drops packets from unknown hosts. The auto-reply features first allow hosts to resolve their default gateway and afterwards allow them to forward traffic. Using the data traffic, the BNG can utilize the data-trigger mechanism to learn the host’s MAC and populate the full IP+MAC static host entry.
The no form of this command reverts to the default.
This command enables auto-reply for neighbor solicitation.
The no form of this command disables auto-reply.
neighbor-solicitation
This command enables auto-reply router solicitation.
The no form of this command disables router-solicitation.
router-solicitation
This command enables the context to configure DHCPv6 relay parameters for the interface.
This command configures the processing required when the SR-Series receives a DHCP request that already has a Relay Agent Information Option (Option 82) field in the packet.
The no form of this command returns the system to the default value.
action keep — Per RFC 3046, DHCP Relay Agent Information Option, section 2.1.1, Reforwarded DHCP requests. The default is to keep the existing information intact. The exception to this is if the giaddr of the received packet is the same as the ingress address on the router. In that case the packet is dropped and an error is logged.
The behavior is slightly different in case of Vendor Specific Options (VSOs). When the keep parameter is specified, the router will insert his own VSO into the Option 82 field. This will only be done when the incoming message has already an Option 82 field.
If no Option 82 field is present, the router will not create the Option 82 field. In this in that case, no VSO will be added to the message.
This command enables Option 82 circuit ID on relayed DHCP packet matching. For routed CO, the group interface DHCP relay process is stateful. When packets are relayed to the server the virtual router ID, transaction ID, SAP ID, and client hardware MAC address of the relayed packet are tracked.
When a response is received from the server the virtual router ID, transaction ID, and client hardware MAC address must be matched to determine the SAP on which to send the packet out. In some cases, the virtual router ID, transaction ID, and client hardware MAC address are not guaranteed to be unique.
When the match-circuit-id command is enabled this part of the key is used to guarantee correctness in our lookup. This is only needed when dealing with an IP aware DSLAM that proxies the client hardware MAC address.
The no form of this command reverts to the default.
This command enables DHCP Option 82 (Relay Agent Information Option) parameters processing and enters the context for configuring Option 82 sub-options.
The no form of this command returns the system to the default.
This command configures the Nokia vendor specific sub-option of the DHCP relay packet.
The no form of this command reverts to the default.
This command enables the sending of the MAC address in the Nokia vendor specific sub-option of the DHCP relay packet.
The no form of this command disables the sending of the MAC address in the Nokia vendor specific sub-option of the DHCP relay packet.
The no form of this command reverts to the default.
This command enables the sending of the SAP ID in the Nokia vendor specific sub-option of the DHCP relay packet.
The no form of this command disables the sending of the SAP ID in the Nokia vendor specific sub-option of the DHCP relay packet.
This command enables the sending of the service ID in the Nokia vendor specific sub-option of the DHCP relay packet.
The no form of this command disables the sending of the service ID in the Nokia vendor specific sub-option of the DHCP relay packet.
This command specifies the vendor specific sub-option string of the DHCP relay packet.
The no form of this command returns the default value.
This command specifies whether the system-id is encoded in the Nokia vendor specific sub-option of Option 82.
The no form of this command reverts to the default.
This command enables subscriber host connectivity verification on a given VPLS SAP or within a VPLS service.
This tool will periodically scan all known hosts (from dhcp-state) and perform a UC ARP request. The subscriber host connectivity verification will maintain state (connected vs. not-connected) for all hosts.
The no form of this command reverts to the default.
This command configures the source IPv6 address of the DHCPv6 relay messages.
The no form of this command reverts to the default.
ipv6-address: | x:x:x:x:x:x:x:x (eight 16-bit pieces) |
x:x:x:x:x:x:d.d.d.d | |
x: [0 to FFFF]H | |
d: [0 to 255]D |
This command enables IPv6 IPoE bridged mode.
The no form of this command disables the IPv6 IPoE bridged mode.
This command enables access to the LUDB for DHCPv6 messages under a routed interface. The name of this LUDB must match the name of the LUDB configured by the config>sub-gmt>local-user-db command.
The no form of this command reverts to the default.
This command enables the context to configure DHCPv6 server parameters for the IES interface.
The no form of this command disables the DHCP6 server.
This command configures the maximum number of lease states installed by the DHCP6 server function allowed on this interface.
The no form of this command to the default.
max-nbr-of-leases 8000
This command enables the prefix delegation options for delegating a long-lived prefix from a delegating router to a requesting router, where the delegating router does not require knowledge about the topology of the links in the network to which the prefixes will be assigned.
The no form of this command disables prefix-delegation.
This command specifies the IPv6 prefix that will be delegated by this system.
The no form of this command reverts to the default.
ipv6-address/prefix: | ipv6-address | x:x:x:x:x:x:x:x (eight 16-bit pieces) |
x:x:x:x:x:x:d.d.d.d | ||
x [0 to FFFF]H | ||
d [0 to 255]D | ||
prefix-length | 1 to 128 |
This command instantiates a local DHCP server. A local DHCP server can serve multiple interfaces but is limited to the routing context it was which it was created.
The no form of this command reverts to the default.
This command enables local proxy ARP. When local proxy ARP is enabled on an IP interface, the system responds to all ARP requests for IP addresses belonging to the subnet with its own MAC address, and thus will become the forwarding point for all traffic between hosts in that subnet. When local-proxy-arp is enabled, ICMP redirects on the ports associated with the service are automatically blocked.
The no form of this command reverts to the default.
This command assigns a specific MAC address to a VPRN IP interface.
The no form of this command returns the MAC address of the IP interface to the default value.
The physical MAC address associated with the Ethernet interface on which the SAP is configured.
This command enables a proxy ARP policy for the interface.
The no form of this command disables the proxy ARP capability.
The specified name(s) must already be defined.
This command configures a redundant interface used for dual homing.
The no form of this command reverts to the default.
This command enables remote proxy ARP on the interface.
Remote proxy ARP is like proxy ARP. It allows the router to answer an ARP request on an interface for a subnet that is not provisioned on that interface. This allows the router to forward to the other subnet on behalf of the requester. To distinguish remote proxy ARP from local proxy ARP, local proxy ARP performs a similar function but only when the requested IP is on the receiving interface.
The no form of this command reverts to the default.
This command enables the context to configure system DHCP6 parameters.
This command configures the different DHCPv6 applications to send the NoAddrsAvail Status-Code in DHCPv6 Advertise messages at the global DHCP message level.
By default, all applications send the NoAddrsAvail Status-Code in DHCPv6 Advertise messages at the IA_NA Option level.
Different applications for which NoAddrsAvail Status-Code in DHCPv6 Advertise messages can be configured at the global DHCP message level.
The only valid combination in current SR OS is adv-noaddrs-global esm-relay server.
The no form of this command reverts to the default.
no adv-noaddrs-global. All applications send the NoAddrsAvail Status-Code in DHCPv6 Advertise messages at the IA_NA Option level.
![]() | Note: The command output in the following section are examples only; actual displays may differ depending on supported functionality and user configuration. |
This command enables the context to display DHCP related information.
This command enables the context to display DHCP6 related information.
This command displays local DHCP or DHCP6 server information.
This command displays the interfaces associated with this DHCP or DHCP6 server.
The following output is an example of information associated with this DHCP or DHCP6 server.
Table 40 describes DHCP associations fields.
Label | Description |
Associations | The entity associated with the local DHCP server |
Admin | The administrative state |
This command display information about declined addresses.
The following output is an example of declined address information
Table 41 describes declined address pool output fields.
Field | Description |
Pool | The name of the IP address pool |
Subnet | The subnet address |
IP Address | The declined IP address |
Time | The creation time of this entry |
MAC Address | The declined MAC address |
Type | The type of declined address |
PPPoE User Name | The name of the PPPoE user name |
Option 82 Circuit ID | The declined circuit ID from the Option 82 |
This command displays failover pool statistics.
The following output is an example of failover pool stats information
Table 42 describes failover pool statistics output fields.
Field | Description |
Failover Admin State | Identifiers the failover state of the DHCP server instance inService — The failover admin state is in service outOfService — The failover admin state is out of service |
Failover Oper State | The operational state of a DHCP server instance |
Failover Persist Key | The maximum amount of time that one server can extend a lease for a client's binding beyond the time known by the partner server |
Administrative MCLT | The administrative Maximum Client Lead Time (MCLT) |
Operational MCLT | Indicates the operational MCLT |
Startup Wait Time | The startup wait time. The startup wait time is the time that one IP address pool attempts to contact the partner IP address pool. During this time, the IP address pool is unresponsive to DHCP client requests. |
Partner Down Delay | The minimum safe-time after the beginning of COMMUNICATIONS-INTERRUPTED state. After the expiry of this time, the server enters the PARTNER-DOWN state. |
Ignore McLT | The ignore McLT status. If, after the transition COMMUNICATIONS-INTERRUPTED-to-PARTNER-DOWN state, the DHCP server instance ignores the safety period with a duration of Maximum Client Lead Time; a ‘true’ value has the effect that the DHCP server starts offering IP addresses from the partner's scope immediately after this transition, without waiting for existing leases allocated by the partner and not known by this system to time out. A ‘true’ value increases the risk that duplicate addresses are offered; if the transition to PARTNER-DOWN state is likely to be caused by a failure of the partner system rather than a communications problem, this risk is reduced. |
Failover statistics for pool | The failover statistics for each pool |
Dropped Invalid Packets | The number of BNDUPD packets that were dropped because the packet was malformed |
Failover Shutdown | The number of BNDUPD packets that were dropped because the failover state if the DHCP server instance is shut down |
Lease Already Expired | The number of BNDUPD packets that were dropped because the corresponding lease has expired |
Maximum Lease Count Reached | The number of BNDUPD packets that were dropped because the maximum number of leases were reached |
Subnet Not Found | The number of BNDUPD packets that were dropped because a valid subnet could not be found for the lease |
Range Not Found | The number of BNDUPD packets that were dropped because a valid include range could not be found for the lease |
Host Conflict | The number of BNDUPD packets that were dropped because this DHCP server instance has already leased this address to another host |
Address Conflict | The number of BNDUPD packets that were dropped because this DHCP server instance has already leased another address to this host |
Peer Conflict | The number of BNDUPD packets that were dropped because the failover peer has leased an address within a subnet range of which the failover control is set to local on this local DHCP server instance |
Persist Congestion | The number of BNDUPD packets that were dropped because of persistence congestion on this DHCP server instance |
No Lease Hold Time Configured | The number of BNDUPD packets that were dropped because the lease hold time is zero on this DHCP server instance |
Lease Not Found | The number of Binding Database Update (BNDUPD) remove packets were dropped because the corresponding lease could not be found. |
Number of pools found | The total number of pools found |
This command displays failover server statistics.
The following output is an example of failover server stats information.
Table 43 describes failover server stats fields.
Field | Description |
Failover Admin State | Identifiers the failover state of the DHCP server instance inService — The failover admin state is in service outOfService — The failover admin state is out of service |
Failover Oper State | The operational state of a DHCP server instance |
Failover Persist Key | The maximum amount of time that one server can extend a lease for a client's binding beyond the time known by the partner server |
Administrative MCLT | The administrative Maximum Client Lead Time (MCLT) |
Operational MCLT | Indicates the operational MCLT |
Startup Wait Time | The startup wait time. The startup wait time is the time that one IP address pool attempts to contact the partner IP address pool. During this time, the IP address pool is unresponsive to DHCP client requests. |
Partner Down Delay | The minimum safe-time after the beginning of COMMUNICATIONS-INTERRUPTED state. After the expiry of this time, the server enters the PARTNER-DOWN state. |
Ignore McLT | The ignore McLT status. If, after the transition COMMUNICATIONS-INTERRUPTED-to-PARTNER-DOWN state, the DHCP server instance ignores the safety period with a duration of Maximum Client Lead Time; a ‘true’ value has the effect that the DHCP server starts offering IP addresses from the partner's scope immediately after this transition, without waiting for existing leases allocated by the partner and not known by this system to time out. A ‘true’ value increases the risk that duplicate addresses are offered; if the transition to PARTNER-DOWN state is likely to be caused by a failure of the partner system rather than a communications problem, this risk is reduced. |
Failover statistics for server | The failover statistics for each pool |
Dropped Invalid Packets | The number of BNDUPD packets that were dropped because the packet was malformed |
Failover Shutdown | The number of BNDUPD packets that were dropped because the failover state if the DHCP server instance is shut down |
Lease Already Expired | The number of BNDUPD packets that were dropped because the corresponding lease has expired |
Maximum Lease Count Reached | The number of BNDUPD packets that were dropped because the maximum number of leases were reached |
Subnet Not Found | The number of BNDUPD packets that were dropped because a valid subnet could not be found for the lease |
Range Not Found | The number of BNDUPD packets that were dropped because a valid include range could not be found for the lease. |
Host Conflict | The number of BNDUPD packets that were dropped because this DHCP server instance has already leased this address to another host |
Address Conflict | The number of BNDUPD packets that were dropped because this DHCP server instance has already leased another address to this host |
Peer Conflict | The number of BNDUPD packets that were dropped because the failover peer has leased an address within a subnet range of which the failover control is set to local on this local DHCP server instance |
Persist Congestion | The number of BNDUPD packets that were dropped because of persistence congestion on this DHCP server instance |
No Lease Hold Time Configured | The number of BNDUPD packets that were dropped because the lease hold time is zero on this DHCP server instance |
Lease Not Found | The number of Binding Database Update (BNDUPD) remove packets were dropped because the corresponding lease could not be found. |
This command displays the free addresses in a subnet.
The following output is an example of free address information
Table 44 describes free addresses pool command output fields.
Field | Description |
IP Address | The free IP addresses in the subnet |
No of free addresses | The total number of free addresses in the subnet |
This command displays the DHCP leases.
The command with no parameters shows all leases from the local-user-db.
The following output is an example of lease information
Table 45 describes leases output fields.
Field | Description |
IP Address | The IP address for the specified lease |
Lease State | The lease state of the IP address |
Mac Address | The MAC address of the lease |
Remaining Lifetime | The remaining lifetime of the lease |
Clnt Type | The address type |
PPPoE user name | The PPPoE user name |
Opt82 | The option number that the DHCP server uses to send the identification strings to the PPPoE client |
Circuit ID | The circuit ID from Option 82 |
This command displays extended statistics per DHCPv4 pool in local DHCPv4 server.
The following statistics are included in output:
For each statistic (except for provisioned addresses), there is current value and peak value, peak value is the highest value since pool creation or last reset via the clear router rt-id dhcp local-dhcp-server svr-name pool-ext-stats command.
The following output is an example of pool extended statistics information.
Table 46 describes extended pool statistics output fields.
Field | Description |
Current | The current pool statistics |
Peak | The peak value since the last reset |
Timestamp | The date and time of the last reset |
Pool | The pool name |
Stable Leases | The number of stable leases in the pool |
Provisioned Addresses | The number of provisioned addresses in the pool |
Used Addressed | The number of used addresses in the pool |
Free Addresses | The number of free addresses in the pool |
Used Pct | The percentage of subnets in use in the pool |
Free Pct | The percentage of unused subnets in the pool |
Last Reset Time | The date and time of the last reset in the pool |
Number of entries | The total number of entries |
This command displays DHCP or DHCP6 server statistics.
The following output is an example of server statics information
Table 47 describes server stats show command output fields.
Field | Description |
RX Discover Packets | The number of discover packets received by the DHCP server instance |
Rx Request Packets | The number of request packets received by the DHCP server instance. |
Rx Release Packets | The number of released packets received by the DHCP server instance |
Rx Decline Packets | The number of declined packets received by the DHCP server instance |
Rx Inform Packets | The number of inform packets received by the DHCP server instance |
Tx Offer Packets | The number of offer packets sent by the DHCP server instance |
Tx Ack Packets | The number of DHCP ACK packets sent by the DHCP server instance |
Tx Nak Packets | The number of DHCP NAK packets sent by the DHCP server instance |
Tx Forcerenew Packets | The number of DHCP force renew packets sent by the server instance |
Client Ignored Offers | The number of DHCP offer packets sent by the DHCP server instance that were ignored by clients |
Leases Timed Out | The number of leases timed out |
Dropped Bad Packet | The number of dropped of DHCP packets received that were corrupt |
Dropped Invalid Type | The number of DHCP packets received that had an invalid message type |
Dropped No User Database | The number of DHCP packets dropped because the value of this server instance is not equal to the default value and a local user database with that name could not be found |
Dropped Unknown Host | The number of DHCP packets dropped from hosts which were not found in the user database |
Dropped User Not Allowed | The number of DHCP packets dropped from hosts which are found in the user database, but which have no address or pool specified |
Dropped Lease Not Ready | The number of DHCP packets dropped by the server instance before the lease database was ready |
Dropped Lease Not Found | The number of DHCP packets dropped by the server instance because no (valid) lease was found |
Dropped Not Serving Pool | The number of DHCP packets dropped by the server instance because there were no more free addresses in the pool |
Dropped Invalid User | The number of DHCP packets dropped by the server instance because the MAC address of the sender or the option 82 didn't match the host lease state |
Dropped Overload | The number of DHCP packets dropped by the server instance because they were received more than the server instance can handle |
Dropped Persistence Overload | The number of DHCP packets dropped by the server instance because they were received in more than the DHCP persistence system can handle. If this occurs, only releases and declines are still processed. |
Dropped Generic Error | The number of DHCP packets dropped by the server instance because of a generic error |
Dropped Destined To Other | The number of DHCP requests dropped by the server instance because the (broadcast) request was not destined to this server |
Dropped Address Unavailable | The number of DHCP requests dropped by the server instance because the requested address is not available |
Dropped Max Leases Reached | The number of DHCP packets dropped by the server instance because the maximum number of leases was reached |
Dropped Server Shutdown | The number of DHCP packets dropped by the server instance during server instance shutdown |
Dropped No Subnet for Fixed IP | The number of DHCP packets dropped by the server instance for user-db hosts with a fixed address because the subnet to which the address belongs is not configured |
This command shows either all sticky leases or a single specific sticky lease created under the specified DHCP server.
The following output is an example of sticky lease information
Table 48 describes the sticky leases field descriptions.
Field | Description |
Hostname | The name of the sticky host |
IP address | The IP address of the sticky host |
No. of Matching Entries | The total numbers of entries matching the command criteria |
This command displays extended statistics per DHCPv4 subnet in local DHCPv4 server.
The following statistics are included in output:
For each statistic (except for Provisioned Addresses), there is current value and peak value, peak value is the highest value since subnet creation or last reset via the clear router rt-id dhcp local-dhcp-server svr-name subnet-ext-stats command.
When parameter pool is used, the statistics of each subnet in the pool will be displayed.
The following output is an example of subnet extended statistics information.
Table 49 describes extended subnet statistics output field descriptions.
Field | Descriptions |
Current | The current statistics for the subnet |
Peak | The peak statistics for the subnet |
TimeStamp | The timestamp for the last reset |
Stable Leases | The number of stable leases |
Provision Addresses | The number of provisioned addresses in this subnet |
Used Addresses | The number of used addresses in this subnet |
Free Address | The number of free addresses in this subnet |
Used Pct | The percentage of addresses in this subnet in use |
Free Pct | The percentage of addresses in this subnet currently unused |
Last Reset Time | The time of the last reset |
Number of entries | The total number of entries |
This command displays subnet statistics.
The following output is an example of subnet statistics information.
Table 50 describe the fields for subnet stats pool output.
Field | Description |
Subnet | The subnet address |
Free | The number of addresses in this subnet that are free |
Offered | The number of leases in this subnet that are in state offered |
Stable | The number of leases in this subnet that are in state stable |
FRPending | The number of leases in this subnet that are in state forceRenewPending |
RemPending | The number of leases in this subnet that are in state removePending |
Declined | The number of addresses in this subnet that are declined |
No. of entries | The total number of entries |
This command displays DHCP server summary information.
The following output is an example of DHCP summary information.
This command lists the local DHCP or DHCP6 servers.
The following output is an example of local DHCP or DHCP6 server information.
This command displays statistics for DHCP relay and DHCP snooping.
If no IP address or interface name is specified, then all configured interfaces are displayed.
If an IP address or interface name is specified, then only data regarding the specified interface is displayed.
The following is an example of DHCP statistics information.
Table 51 describes the output fields for DHCP statistics.
Label | Description |
Rx Packets | The number of packets received from the DHCP clients |
Tx Packets | The number of packets transmitted to the DHCP clients |
Rx Malformed Packets | The number of malformed packets received from the DHCP clients |
Rx Untrusted Packets | The number of untrusted packets received from the DHCP clients |
Client Packets Discarded | The number of packets received from the DHCP clients that were discarded |
Client Packets Relayed | The number of packets received from the DHCP clients that were forwarded |
Client Packets Snooped | The number of packets received from the DHCP clients that were snooped |
Server Packets Discarded | The number of packets received from the DHCP server that were discarded |
Server Packets Relayed | The number of packets received from the DHCP server that were forwarded |
Server Packets Snooped | The number of packets received from the DHCP server that were snooped |
This command displays the status of the DHCP6 relay and DHCP snooping functions on each interface.
The following outputs display DHCP and DHCP6 summary information.
Table 52 describes DHCP summary output field descriptions.
Label | Description |
Interface Name | The name of the router interface |
ARP Populate | ARP populate is enabled or disabled |
Used/Provided | The number of used and provided DHCP leases |
Info Option | Option 82 processing is enabled or disabled on the interface |
Admin State | The administrative state |
Table 53 describes DHCP6 summary output fields.
Label | Description |
Interface Name | The name of the router interface |
ARP Populate | ARP populate is enabled or disabled |
Used/Provided | The number of used and provided DHCP leases |
Info Option | Option 82 processing enabled or disabled on the interface |
Admin State | The administrative state |
This command enables the context to display DHCP6 related information.
This command displays information about the DHCPv6 server that uses a unique /64 prefix per interface-ID options combination.
The following output is an example of interface ID mapping information.
Table 54 describes interface ID mapping field descriptions.
Field | Description |
Mapped Prefix | The mapped prefix |
Relay Interface ID | The value of the Interface-ID Option assigned by the DHCPv6 Relay Agent |
LDRA Interface ID | The value of the Interface-ID Option assigned by the Lightweight DHCPv6 Relay Agent |
Active Leases | The number of active leases |
No. of prefixes found | The total number of prefixes found. |
This command displays the DHCP6 leases.
The command with no parameters shows all leases from the local user database.
The following output is an example of lease information.
Table 55 describes DHCP6 lease fields.
Field | Description |
IP Address/Prefix | The IP address and prefix of the lease |
Link-local Address | The link local address of the lease |
Lease State | The lease state of the lease |
Remaining Lifetime | The remaining lifetime of the lease |
Fail Ctrl | The type of failover control |
No. leases found | The total number of leases |
This command displays extended statistics per DHCPv6 pool in local DHCPv6 server.
The following statistics are included in output:
For each statistic (except for Provisioned Addresses), there is current value and peak value, peak value is the highest value since pool creation or last reset via command “clear router <rt-id> dhcp6 local-dhcp-server <svr-name> pool-ext-stats”.
The following output is an example of subnet statistics information.
Table 56 describes DHCP6 extended pool statistics output fields.
Field | Description |
Current | The current pool statistics |
Peak | The peak value since the last reset |
TimeStamp | The date and time of the last reset |
Pool | The pool name |
Stable Leases | The number of stable leases |
Provisioned Blks | The number of provisioned blocks in this pool |
Free Blks | The number of free blocks in this pool |
Used Pct | The percentage of extended statistics in use |
Free Pct | The percentage of /64 blocks currently unused |
Last Reset Time | The date and time of the last reset |
Number of entries | The total number of entries |
This command displays pool statistics.
The following output is an example of pool statistics information.
Table 57 describes pool statistics output field descriptions.
Field | Description |
Failover Admin State | Identifiers the failover state of the DHCP server instance inService — The failover admin state is in service outOfService — The failover admin state is out of service |
Failover Oper State | The operational state of a DHCP server instance |
Failover Persist Key | The maximum amount of time that one server can extend a lease for a client's binding beyond the time known by the partner server |
Administrative MCLT | The administrative Maximum Client Lead Time (MCLT) |
Operational MCLT | Indicates the operational MCLT |
Startup Wait Time | The startup wait time. The startup wait time is the time that one IP address pool attempts to contact the partner IP address pool. During this time, the IP address pool is unresponsive to DHCP client requests. |
Partner Down Delay | The minimum safe-time after the beginning of COMMUNICATIONS-INTERRUPTED state. After the expiry of this time, the server enters the PARTNER-DOWN state. |
Ignore McLT | The ignore McLT status. If, after the transition COMMUNICATIONS-INTERRUPTED-to-PARTNER-DOWN state, the DHCP server instance ignores the safety period with a duration of Maximum Client Lead Time; a ‘true’ value has the effect that the DHCP server starts offering IP addresses from the partner's scope immediately after this transition, without waiting for existing leases allocated by the partner and not known by this system to time out. A ‘true’ value increases the risk that duplicate addresses are offered; if the transition to PARTNER-DOWN state is likely to be caused by a failure of the partner system rather than a communications problem, this risk is reduced. |
Failover statistics for pool | The failover statistics for each pool |
Dropped Invalid Packets | The number of BNDUPD packets that were dropped because the packet was malformed |
Failover Shutdown | The number of BNDUPD packets that were dropped because the failover state if the DHCP server instance is shut down |
Lease Already Expired | The number of BNDUPD packets that were dropped because the corresponding lease has expired |
Maximum Lease Count Reached | The number of BNDUPD packets that were dropped because the maximum number of leases were reached |
Subnet Not Found | The number of BNDUPD packets that were dropped because a valid subnet could not be found for the lease |
Range Not Found | The number of BNDUPD packets that were dropped because a valid include range could not be found for the lease. |
Host Conflict | The number of BNDUPD packets that were dropped because this DHCP server instance has already leased this address to another host |
Address Conflict | The number of BNDUPD packets that were dropped because this DHCP server instance has already leased another address to this host |
Peer Conflict | The number of BNDUPD packets that were dropped because the failover peer has leased an address within a subnet range of which the failover control is set to local on this local DHCP server instance |
Persist Congestion | The number of BNDUPD packets that were dropped because of persistence congestion on this DHCP server instance |
No Lease Hold Time Configured | The number of BNDUPD packets that were dropped because the lease hold time is zero on this DHCP server instance |
Lease Not Found | The number of Binding Database Update (BNDUPD) remove packets were dropped because the corresponding lease could not be found. |
Number of pools found | The total number of pools found |
This commands displays pool level threshold stats of local DHCPv6 server. A minimum-free threshold needs to be configured before system collects threshold stats for the prefix.
The stats for each threshold are calculated based on the configured minimum-free prefix length.
For example, a /59 prefix is provision in the local DHCPv6 server, and the server allocated two PD leases, one /62 and one /63. And there is a /63 minimum threshold configured. The threshold stats are calculated based on /63 as the base unit (block). Then the value of current used block would be 3 because there is one /62 lease and one /63 lease, that equals to a total of three /63.
The following output is an example of pool threshold statistics information.
The command shown above displays an overview of pool level thresholds in the specified pool:
The above command displays detailed statistics of all pool level thresholds in the specified pool:
Table 58 describes pool threshold statistics output fields.
Field | Description |
Operational state | The operational state of the local DHCP server instance unknown — The operational state is unknown inService — The operational state is in service outOfService — The operational state is out of service transition — The operational state is in transition waitPersistence — The DHCP server instance is waiting for a persistence action to complete. |
Pool | The pool ID |
Stable Leases | The number of stable leases |
Advertised leases | The number of advertised leases |
Threshold | The prefix level threshold |
Current Provisioned Blks | The number of provisioned blocks in this pool |
Current Used Blks | The number of used blocks in this pool |
Current Free Blks | The number of free blocks in this pool |
Current Used Percent | The percentage of used prefixes with the minimum free threshold length in the pool compared to the number of provisioned prefixes |
Current Used Peak Blks | A 64-bit word of the peak value of the number of used blocks in the pool with a prefix length |
Current Used Peak Percent | The peak value of the number of used prefixes with the minimum free threshold length in the pool as a percentage of the provisioned prefixes. This depends on the current failover state of the DHCP server or pool |
Current Used Peak Time | The time at which the peak value of the number of used prefixes in the pool was reached |
Current Free Percent | The percentage of free prefixes with the minimum free threshold length in the pool compared to the number of provisioned prefixes. This depends on the current failover state of the DHCP server or pool |
Current Free Too Low | The number of free prefixes with the minimum free threshold length available in the pool that is below the configured number of prefixes with the minimum free threshold length |
Current Free Depleted | The number of prefixes with the minimum free threshold length available in the pool |
Local Provisioned Blks | A 64-bit word of the number of provisioned prefixes with the minimum free threshold length local in the pool |
Local Used Blks | A 64-bit word of the number of used prefixes with the minimum free threshold length local in the pool |
Local Free Blks | A 64-bit word of the number of free prefixes with the minimum free threshold length local in the pool |
Local Used Peak Blks | A 64-bit word of the peak value of the number of used prefixes with the minimum free threshold length local in the pool |
Local Used Peak Percent | The peak value of the number of used prefixes with the minimum free threshold length local in the pool as a percentage of the provisioned prefixes |
Local Used Peak Time | The time at which the peak value of the number of used prefixes local in the pool was reached |
Remote Provisioned Blks | A 64-bit word of the number of provisioned prefixes with the minimum free threshold length remote in the pool |
Remote Used Blks | A 64-bit word of the number of used prefixes with the minimum free threshold length remote in the pool |
Remote Free Blks | A 64-bit word of the number of free prefixes with the minimum free threshold length remote in the pool |
This command displays extended statistics per DHCPv6 prefix in local DHCPv6 server.
The following statistics are included in output:
For each statistic (except for Provisioned Addresses), there is current value and peak value, peak value is the highest value since prefix creation or last reset via command clear>router rt-id>dhcp6>local-dhcp-server svr-name>prefix-ext-stats.
When the pool parameter is used, the statistics of each prefix in the pool will be displayed.
The following output is an example of prefix extended stats information.
Table 59 describes extended prefix statistics output fields.
Field | Description |
Current | The current extended prefix statistics |
Peak | The peak value since the last reset |
TimeStamp | The date and time of the last reset |
Failover Oper State | The operational state of the DHCP specified prefix |
Stable Leases | The number of stable leases |
Provisioned Blks | The number of provisioned blocks |
Used Blks | The number of used blocks |
Free Blks | The number of free blocks |
Used Pct | The percentage of extended prefixes in use |
Free Pct | The percentage of free prefixes in use |
Last Reset Time | The date and time of the last reset |
Number of entries | The total number of entries |
This command displays prefix statistics.
This commands displays prefix level threshold stats of local DHCPv6 server prefix. A minimum-free threshold needs to be configured before system collects threshold stats for the prefix.
The stats for each threshold are calculated based on the configured minimum-free prefix length.
For example, a /59 prefix is provision in the local DHCPv6 server, and the server allocated two PD leases, one /62 and one /63. And there is a /63 minimum threshold configured. The threshold stats are calculated based on /63 as the base unit (block). Then the value of the current used block would be 3 because there is one /62 lease and one /63 lease, that equals to a total three /63.
ipv6-address x:x:x:x:x:x:x:x (eight 16-bit pieces) | |
x:x:x:x:x:x:d.d.d.d | |
x [0 to FFFF]H | |
d [0 to 255]D | |
prefix-length [1 to 128] |
The following output is an example of prefix threshold information.
The command shown above displays an overview of prefix level thresholds in the specified pool:
The command shown above displays detailed statistics of all prefix level thresholds in the specified pool:
The command shown above displays an overview of prefix level thresholds in the specified provision prefix.
The command displayed above displays detailed statistics of prefix level thresholds in the specified provision prefix.
Table 60 describes prefix threshold statistics output fields.
Field | Description |
Operational state | The operational state of the local DHCP server instance unknown — The operational state is unknown inService — The operational state is in service outOfService — The operational state is out of service transition — The operational state is in transition waitPersistence — The DHCP server instance is waiting for a persistence action to complete. |
Pool | The number of pools in the specified prefix |
Stable leases | The number of stable leases associated with the prefix |
Advertised leases | The advertised leases associated with the prefix |
Prefix | The specified prefix |
Draining | The draining state Y — enabled N — disabled |
Threshold | The prefix level threshold |
Current Provisioned Blks | The number of provisioned blocks for this prefix |
Current Used Blks | The number of used blocks for this prefix |
Current Free Blks | The number of free blocks for this prefix |
Current Used Percent | The percentage of used prefixes with the minimum free threshold length for this prefix |
Current Used Peak Blks | A 64-bit word of the peak value of the number of used blocks for this prefix |
Current Used Peak Percentage | The peak value of the number of used prefixes with the minimum free threshold length in the pool as a percentage of the provisioned prefixes. |
Current Used Peak Time | The time at which the peak value of the number of used prefixes in the pool was reached |
Current Free Percent | The percentage of free prefixes with the minimum free threshold length in the pool compared to the number of provisioned prefixes. |
Current Free Too Low | The number of free prefixes with the minimum free threshold length available in the pool that is below the configured number of prefixes with the minimum free threshold length |
Current Free Depleted | The number of prefixes with the minimum free threshold length available |
Local Provisioned Blks | A 64-bit word of the number of provisioned prefixes with the minimum free threshold length local |
Local Used Blks | The higher 64-bits word of the number of used prefixes with the minimum free threshold length |
Local Free Blks | A 64-bit word of the number of free prefixes with the minimum free threshold length |
Local Used Peak Blks | A 64-bit word of the peak value of the number of used prefixes with the minimum free threshold length |
Local Used Peak Percent | The peak value of the number of used prefixes with the minimum free threshold length local in the pool as a percentage of the provisioned prefixes |
Local Used Peak Time | The time at which the peak value of the number of used prefixes local in the pool was reached |
Remote Provisioned Blks | A 64-bit word of the number of provisioned prefixes with the minimum free threshold length |
Remote Used Blks | A 64-bit word of the number of used prefixes with the minimum free threshold length remote in the pool |
Remote Free Blks | A 64-bit word of the number of free prefixes with the minimum free threshold length remote in the pool |
Remote Used Peak Blks | The higher 64-bit word of the number of used prefixes with the minimum free threshold length |
Remote Used Peak Percent | The peak value of the number of used prefixes with the minimum free threshold length remote in the pool as a percentage of the provisioned prefixes |
Remote Used Peak Time | The time at which the peak value of the number of used prefixes remote in the pool was reached. |
Peak Reset Time | The time at which the peak values have been reset |
Valid Dada | The actual status of the threshold statistics data of the pool. Y — the data is up to date and may be used. N — the data is being recalculated in the background and is not stable for further use |
This command displays statistics for DHCP6 relay and snooping.
The following output is an example of DHCP6 statistics information.
Table 61 describes DHCP6 output statistics.
Field | Description |
Rx Packets | The number of packets received |
Tx Packets | The number of packets sent |
Rx Malformed Packets | The number of malformed packets received from the DHCP6 clients |
Rx Untrusted Packets | The number of untrusted packets received from the DHCP clients |
Client Packets Discarded | The number of packets received from the DHCP clients that were discarded |
Client Packets Relayed | The number of packets received from the DHCP clients that were forwarded |
Client Packets Snooped | The number of packets received from the DHCP clients that were snooped |
Client Packets Proxied (RADIUS) | The number of client packets proxied through RADIUS |
Client Packets Proxied (Lease-Split) | The number of client packets proxied through a lease split |
Server Packets Discarded | The number of discarded server packets |
Server Packets Relayed | The number of relayed server packets |
Server Packets Snooped | The number of snooped server packets |
DHCP RELEASEs Spoofed | The number of spoofed DHCP releases |
DHCP FORCERENEWs Spoofed | The number of spoofed FORCERENEW messages |
This command displays DHCP lease state information. The wholesaler service-id parameter is applicable only in the VPRN context.
![]() | Note: The wholesaler service-id parameter is applicable only in the VPRN context (VPRN is supported by the 7750 SR only). |
The following output is an example of lease state information.
Table 62 describes the output fields for DHCP summary.
Label | Description |
Interface Name | The name of the router interface |
ARP Populate | The ARP populate is enabled or disabled |
Used/Provided | The number of used and provided DHCP leases |
Info Option | Option 82 processing is enabled or disabled on the interface |
Admin State | The administrative state |
This command displays DHCP relay statistics.
The following output is an example of DHCP statistics information.
Table 63 describes DHCP statistics output fields.
Field | Description |
Rx Packets | The number of received packets |
Tx Packets | The number of transmitted packets |
Rx Malformed | The number of malformed packets received |
Rx Untrusted Packets | The number of untrusted packets received |
Client Packets Discarded | The number of client packets discarded |
Client Packets Relayed | The number of client packets relayed |
Client Packets Snooped | The number of client packets snooped |
Client Packets Proxied (RADIUS) | The number of client packets proxied through RADIUS |
Client Packets Proxied (Lease-Split) | The number of client packets proxied through a lease split |
Server Packets Discarded | The number of discarded server packets |
Server Packets Relayed | The number of relayed server packets |
Server Packets Snooped | The number of snooped server packets |
DHCP RELEASEs Spoofed | The number of spoofed DHCP releases |
DHCP FORCERENEWs Spoofed | The number of spoofed FORCERENEW messages |
This command displays DHCP or DHCP6 configuration summary information.
The following output is an example of a summary of DHCP information.
The following example is for the 7750 SR:
Table 64 describes the DHCP summary output fields.
Field | Description |
Interface Name | The DHCP interface name |
Arp Populate | The state of ARP populate |
Used/Provided | The number used or provided |
Info Option | The info option |
Admin State | The administrative state of the interface |
Interfaces | The total number of interfaces |
This command displays DHCPv6 lease state information.
![]() | Note: The wholesaler service-id parameter is applicable only in the VPRN context. |
The following output is an example of DHCP6 lease state information.
Table 65 describes DHCP6 lease state router advertisement policy output fields.
Field | Description |
Service ID | The service ID provided by the access node to which this subnet is bound |
IP Address | The IP address of the service |
Client HW Address | The MAC address of the client |
Subscriber-Interface | The subscriber interface for the service |
Group-interface | The group interface for the service |
Sap/Sdp ID | The service SAP and SDP IDs |
Termination Type | The PPP session type |
Up Time | The value of the up time at the time of the last modification of an entry |
Remaining Lease Time | The time left for this lease |
Remaining SessionTime | The time left for this session |
Persistence Key | The persistence key |
Sub-Ident | The subscriber identification policy name |
Sub-Profile-String | The subscriber profile policy name |
App-Profile-String | The application profile policy name |
Lease ANCP-String | The ANCP string |
Category-Map-Name | The category map name |
Dhcp6 ClientID (DUID) | The DHCP client ID |
Dhcp6 IAID | The DHCP6 Identity Association of the client |
Dhcp6 IAID Type | The DHCP6 Identity Association of the client |
Dhcp6 Client Ip | The DHCP6 IP address of the client |
Primary-Dns | The primary DNS, if configured |
Secondary-Dns | The secondary DNS, if configured |
Pool Name | The pool name |
Dhcp6 Server Addr | The DHCP6 server address |
Dhcp6 ServerID (DUID) | The DHCP6 server ID |
Dhcp6 InterfaceId | The DHCP6 interface ID |
Dhcp6 RemoteId | The DHCP6 remote ID |
Radius sub-if prefix | The RADIUS subscriber interface prefix |
Router adv. policy | The router advertisement policy |
Lease Info origin | The lease info origin |
ServerLeaseStart | The date and time the lease was created |
ServerLastRenew | The last renew was done for this lease |
ServerLeaseEnd | The time left for this lease |
Session-Timeout | The session timeout interval |
IPoE|PPP | IPoE or PPP |
Radius User-Name | The RADIUS user name |
Number of lease states | The total number of lease states |
This command displays currently recorded default gateway and subnets for all virtual subnets enabled for DHCPv4 hosts in the specified service.
The following output is an example of virtual subnet information.
Table 66 describes virtual subnet output fields.
Field | Descriptions |
Subscriber | The service identification that identifies the service in the service domain |
Default router | The IP address of the default router received from either the DHCP or the RADIUS server |
Subnet | The IP address of the subnet |
SAP | The SAP associated with the service |
No. of subnets | The total number of subnets for the service |
This command enables the context to display service PPP information for the specified service.
This command displays PPP session information.
This command display PPP statistics information for the specified service ID.
This command display summarized PPP information for the specified service ID.
This command enables the context to clear and reset DHCP entities.
This command clears DHCP server data.
This command clears declined DHCP addresses.
This command clears failover pool statistics.
This command clears DHCP leases.
This command clears extended pool statistics.
This command clears all local DHCP or DHCPv6server statistics.
This command clears sticky leases.
This command clears extended subnet statistics.
This command clears DHCP statistics.
This command enables the context to clear and reset DHCP6 entities.
This command removes the specified leases in the specified local DHCPv6 server.
This commands resets the peak stats in the pool level threshold stats in the specified pool. If the pool name is not specified, then the peak stats in all pools in the server will be reset.
This command reset the begin time of peak values in output of the show router rt-id dhcp6 local-dhcp-server svr-name prefix-ext-stats command/
This commands resets the peak stats in the prefix level threshold stats in the specified provision prefix or pool.
This command clears DHCP6 statistics.
This command clears DHCP statistics.
This command clears DHCP lease state information.
This command clears DHCP6 lease state information.
ipv6 | ipv6-prefix[/pref*: | x:x:x:x:x:x:x:x (eight 16-bit pieces) |
x:x:x:x:x:x:d.d.d.d | ||
x: [0 to FFFF]H | ||
d: [0 to 255]D | ||
prefix-length: | 1 to 128 |
This command clears DHCP statistics for this service.
This command enables DHCP debugging.
The no form of this command disables debugging.
This command debugs the DHCP tracing detail level.
This command debugs the DHCP tracing detail level.
This command enables DHCP debugging
The no form of this command disables debugging.
This command enables, disables or configures debugging for a local DHCP server.
ipv6-address: | x:x:x:x:x:x:x:x [-interface] |
x:x:x:x:x:x:d.d.d.d [-interface] | |
x: [0 to FFFF]H | |
d: [0 to 255]D | |
interface | up to 32 characters, mandatory for link local addresses |
This command enables the context to enable useful tools for debugging purposes.
This command enables the context to enable tools to perform specific tasks.
This command enables tools to control subscriber management.
This command enables tools for controlling the local user database.
This command contains the tools used to control IPoE entries in the local user database.
This command performs a lookup in the local user database. This command looks up the host with the match-list configured in the local user database.
This command contains the tools used to control PPP entries in the local user database.
This command authenticates PPP user name. As local user database PAP/CHAP authentication can only be used when the local user database is connected to the PPP node under the group interface, the user lookup will be performed with match-list username.
This command performs a lookup in the local user database.
This command enables the context to configure tools DHCP parameters.
This command enables the context to configure tools DHCP6 parameters.
This command enables the context to perform local DHCP or DHCP6 server failover tasks.
This command aborts the running start-up-wait time, forcing the DCHP server to transition immediately to the COMMUNICATIONS-INTERRUPTED state.
The start-up-wait time is started after a boot to enable two redundant routers to synchronize the DHCP server lease database before transitioning to the (PRE-)NORMAL state when the last state record from the peer is synchronized. If the last state record is not received before the start-up-wait time expires, it is assumed that the remote DHCP server is not operational and the DHCP server goes in COMMUNICATIONS-INTERRUPTED state.
This command forces a DHCP server to transition from the COMMINICATIONS-INTERRUPTED state to the PARTNER-DOWN state.
It is important to note that this command should only be used if the remote DHCP server is out of service, else duplicate address allocations could occur.
In case of a communication failure between two redundant DHCP servers, the DHCP server transitions to the COMMUNICATIONS-INTERRUPTED state. In this state, the DHCP server allocates IP addresses for new leases from the local and address-driven address-ranges only. This prevents duplicate address allocations.
If during the partner-down-delay time, the communication with the remote DHCP server is not restored, then the DHCP server transitions to the PARTNER-DOWN state. In this state, the DHCP server also allocates IP addresses for new leases from the remote ranges. A DHCP server should only reach this state when the remote DHCP server is out of service, else IP address conflicts can occur.
This command performs local DHCP or DHCP6 server IP address pool tasks.
This command tries to create a lease-state in the specified local-dhcp-server pool with the supplied parameters. The hostname will uniquely identify this lease for subsequent operations. mac/circuit-id and client-id should also have a unique combination of values according to the configured user-ident variables.If the requested-ip-address is provided the server will try to create a lease with this address. If this address is not available in the pool, the command will fail.
This command sends a DHCP FORCERENEW message on behalf of the DHCP server to the DHCP client with specified IP address. A DHCP lease with the specified IP address must exist in the DHCP server.
This command displays the DHCP received packet statistics.
The following output is an example of DHCP RX statistics information.