IES Interface Commands
Page 968 7750 SR OS Services Guide
keep — The existing information is kept in the packet and the router does not add any additional
information. In the downstream direction the Option 82 field is not stripped and is forwarded
towards the client.
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.
circuit-id
Syntax circuit-id [ascii-tuple | ifindex | sap-id | vlan-ascii-tuple]
no circuit-id
Context config>service>ies>if>dhcp>option
config>service>ies>sub-if>grp-if>dhcp>option
Description When enabled, the router sends either an ASCII tuple, or the interface index (If Index), on the
specified SAP ID in the circuit-id suboption of the DHCP packet.
If disabled, the circuit-id suboption of the DHCP packet will be left empty.
The no form of this command returns the system to the default.
Default circuit-id ascii-tuple
Parameters ascii-tuple — Specifies that the ASCII-encoded concatenated tuple will be used which consists of
the access-node-identifier, service-id, and interface-name, separated by “|”.
ifindex — Specifies that the interface index will be used. The If Index of a router interface can be
displayed using the command show>router>interface>detail.
sap-id — Specifies that the SAP ID will be used.
vlan-ascii-tuple — Specifies that the format will include VLAN ID, dot1p bits in addition to what is
included in ascii-tuple already. The format is supported on dot1q and qinq ports only. Thus,
when the Option 82 bits are stripped, dot1p bits will be copied to the Ethernet header of an
outgoing packet.
match-circuit-id
Syntax [no] match-circuit-id
Context config>service>ies>sub-if>grp-if>dhcp
Description 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 HW 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
To Next Page
Loading...
