circuit-id (DHCP Relay Agent)
Syntax
circuit-id {
include-irb-and-l2;
keep-incoming-circuit-id ;
no-vlan-interface-name;
prefix prefix;
use-interface-description (logical | device);
use-vlan-id;
}
Hierarchy Level
[edit forwarding-options dhcp-relay relay-option-82], [edit forwarding-options dhcp-relay group group-name relay-option-82], [edit logical-systems logical-system-name forwarding-options dhcp-relay relay-option-82], [edit logical-systems logical-system-name forwarding-options dhcp-relay group group-name relay-option-82], [edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-options dhcp-relay relay-option-82], [edit logical-systems logical-system-name routing-instances routing-instance-name forwarding-options dhcp-relay group group-name relay-option-82], [edit routing-instances routing-instance-name forwarding-options dhcp-relay relay-option-82], [edit routing-instances routing-instance-name forwarding-options dhcp-relay group group-name relay-option-82]
Description
Specify the Agent Circuit ID suboption (suboption 1) of the DHCP relay agent information option (option 82) to include in DHCP packets destined for a DHCP server. Optionally specify that the suboption includes a prefix, textual description, or VLAN tag.
For Layer 3 interfaces, when you configure relay-option-82 only, the Agent Circuit ID is the default. If no VLAN tags are configured, then the default is the logical interface device (IFL) name. For integrated routing and bridging (IRB) interfaces, the default is the Layer 2 IFL name and bridge domain name.
The interface to bridge domain relationship may be implicit (the interface is mapped to the bridge domain by the system based on VLAN tag) or explicit (the interface is mapped to the bridge domain by configuring it in the bridge domain definition). For the explicit case, tagging might not be relevant for the mapping.
The format of the Agent Circuit ID information for Fast Ethernet or Gigabit Ethernet interfaces that do not use virtual LANs (VLANs), stacked VLANs (S-VLANs), or bridge domains is as follows:
(fe | ge)-fpc/pic/port.subunit
For remote systems, the subunit is required and is used to differentiate an interface for remote systems.
The format of the Agent Circuit ID information for Fast Ethernet or Gigabit Ethernet interfaces that use VLANs is as follows:
(fe | ge)-fpc/pic/port:vlan-id
The format of the Agent Circuit ID information for Fast Ethernet or Gigabit Ethernet interfaces that use S-VLANs is as follows:
(fe | ge)-fpc/pic/port:svlan-id-vlan-id
In the case of an IRB interface, the format displays the Layer 2 interface instead of the IRB interface along with the bridge domain name. For IRB interfaces (or other pseudo devices) the default format is as follows:
IRB interfaces that use bridge domains but do not use VLANs or S-VLANs:
(fe | ge)-fpc/pic/port.subunit:bridge-domain-name
IRB interfaces that use VLANs:
(fe | ge)-fpc/pic/port.subunit:vlan-name
To include the IRB interface name with the Layer 2 interface
name, configure the include-irb-and-l2 statement. The format
is as follows:
IRB interfaces that use bridge domains but do not use VLANs or S-VLANs:
(fe | ge)-fpc/pic/port:bridge-domain-name+irb.subunit
IRB interfaces that use VLANs:
(fe | ge)-fpc/pic/port:vlan-name+irb.subunit
To include only the IRB interface name without the Layer 2 interface
and bridge domain or VLAN, configure the no-vlan-interface-name statement. The format is as follows:
irb.subunit
The remaining statements are explained separately. Search for a statement in CLI Explorer or click a linked statement in the Syntax section for details.
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 8.3.
include-irb-and-l2 , no-vlan-interface-name, and use-vlan-id options added in Junos OS Release 14.1.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.
circuit-id CLI statement in a stateless DHCP relay
configuration. You can configure stateless DHCP relay using the
forward-only CLI statement at the [edit
forwarding-options dhcp-relay] hierarchy level.