No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

NE40E-M2 V800R010C10SPC500 Feature Description - LAN Access and MAN Access 01

This is NE40E-M2 V800R010C10SPC500 Feature Description - LAN Access and MAN Access
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
DHCP Relay on a Termination Sub-interface

DHCP Relay on a Termination Sub-interface

On the network shown in Figure 7-16 and Figure 7-16, the Dynamic Host Configuration Protocol (DHCP) relay function is configured on termination sub-interfaces. This function allows the sub-interfaces to add user tag information into Option 82, so that a DHCP server can assign IP addresses based on the tag information.

The DHCP relay function can be configured on a sub-interface for Dot1q VLAN tag termination or sub-interface for QinQ VLAN tag termination, based on whether the user packets received by a PE contain one or two VLAN tags.

  • If the user packets contain one tag, the sub-interface that has the DHCP relay function configured is a sub-interface for Dot1q VLAN tag termination.

  • If the user packets contain double tags, the sub-interface that has the DHCP relay function configured is a sub-interface for QinQ VLAN tag termination.

DHCP Relay on a Sub-interface for Dot1q VLAN Tag Termination

On the network shown in Figure 7-15, the packet received by the DHCP relay carries a single tag. If a sub-interface for Dot1q VLAN tag termination does not support the DHCP relay, the DHCP relay regards the received packet as an invalid packet and discards it. As a result, the DHCP client cannot obtain an IP address from the DHCP server.

On the sub-interface for Dot1q VLAN tag termination, the DHCP relay function is implemented as follows:
  1. When receiving a DHCP request message, the DHCP relay adds user tag information into the Option 82 field in the message.

  2. When receiving a DHCP reply message (ACK message) from the DHCP server, the DHCP relay analyzes the DHCP reply and generates a binding table.

  3. The DHCP relay checks user packets based on the user tag information.

Figure 7-15 DHCP relay on a sub-interface for Dot1q VLAN tag termination

DHCP Relay on a Sub-interface for QinQ VLAN Tag Termination

On the network shown in Figure 7-15, the packet received by the DHCP relay carries double tags. If a sub-interface for QinQ VLAN tag termination does not support the DHCP relay, the DHCP relay regards the received packet as an invalid packet and discards it. As a result, the DHCP client cannot obtain an IP address from the DHCP server.

On the sub-interface for QinQ VLAN tag termination, the DHCP relay function is implemented as follows:
  1. When receiving a DHCP request message, the DHCP relay adds user tag information into the Option 82 field in the message.

  2. When receiving a DHCP reply message (ACK message) from the DHCP server, the DHCP relay analyzes the DHCP reply and generates a binding table.

  3. The DHCP relay checks user packets based on the user tag information.

Figure 7-16 DHCP relay on a sub-interface for QinQ VLAN tag termination

Download
Updated: 2019-01-02

Document ID: EDOC1100058405

Views: 17787

Downloads: 23

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next