Configuring Helpers (NSM Procedure)
You can enable Trivial File Transfer Protocol (TFTP)
or Domain Name System (DNS) request packet forwarding, or configure
the router or interface to act as a Dynamic Host Configuration Protocol
(DHCP) or Bootstrap Protocol (BOOTP) relay agent. You use only one
server address per interface or global configuration. See the following
topics:
Configuring a Router or Interface to Act as a Bootstrap Protocol
Relay Agent
You can configure a router or interface to act as a Dynamic
Host Configuration Protocol (DHCP) or bootstrap protocol (BOOTP) relay
agent using this option.
To configure a BOOTP relay agent in NSM:
- In the NSM navigation tree, select Device Manager > Devices.
- Click the Device Tree tab,
and then double-click the device to select it.
- Click the Configuration tab.
In the configuration tree, expand Forwarding Options
> Helpers > BOOTP.
- Add or modify settings as specified in Table 1.
- Click one:
- OK—Saves the changes.
- Cancel—Cancels the modifications.
Table 1: BOOTP Configuration Details
| Task |
Your Action |
Configures a router or interface to act as
a DHCP or BOOTP relay agent.
|
- In the Comment box, enter the comment.
- Select the Relay Agent check box
to configure router as a BOOTP relay agent.
- From the Maximum Hop Count list,
select the maximum number of hops allowed.
Default: 4 hops
- From the Minimum Wait Time list,
select the minimum time allowed.
Default: 3 seconds
- From the Client Response Ttl list,
select the IIP time-to-live (TTL) value in DHCP response packets sent
to a DHCP client.
|
Configure DHCP option 82.
|
- Click Dhcp Option82 next to Bootp.
- In the Comment box, enter the comment.
- Select the Disable check box to disable
DHCP option 82 on this VLAN.
- Click Circuit Id next to Dhcp Option82.
- In the Comment box, enter the comment.
- From the Prefix list, select the
prefix
- hostname—Set hostname as the
prefix.
- Select the Use Interface Description check box to use interface description instead of name.
- Select the Use Vlan Id check box
to use vlan id.
- Click Remote Id next to Dhcp Option82.
- In the Comment box, enter the comment.
- From the Prefix list, select the
prefix
- none—Set no prefix.
- hostname—Set hostname as the
prefix.
- mac—Set chassis MAC as the
prefix.
- Select the Use Interface Description check box to use interface description instead of name.
- In the Use String check box, enter
the raw string instead of the default remote ID.
- Click Vendor Id next to Dhcp Option82.
- In the Comment box, enter the comment.
- In the Use String check box, enter
the raw string instead of the default remote ID.
|
Specify the interface for a DHCP
and BOOTP relay agent.
|
- Click Interface next to BOOTP.
- Click Add new entry next to Interface.
- Expand Interface.
- In the Name box, enter the interface
for a DHCP and BOOTP relay agent.
- In the Comment box, enter the comment.
- Select the No Listen check box to
disable recognition of DNS requests or stop packets from being forwarded
on a logical interface, a group of logical interfaces, or a router.
- Select the Broadcast check box to
issue the DHCP or BOOTP request as a broadcast message.
- In the Descriptions box, enter the
description of BOOTP, DHCP, Domain Name System (DNS), or Trivial File
Transfer Protocol (TFTP) service, or of an interface that is configured
for the service.
- From the Maximum Hop Count list,
select the maximum number of hops allowed.
Default: 4 hops
- From the Minimum Wait Time list,
select the minimum time allowed.
Default: 3 seconds
- From the Client Response Ttl list,
select the IIP time-to-live (TTL) value in DHCP response packets sent
to a DHCP client.
|
Configure the router to act as a DHCP and
BOOTP relay agent.
|
- Click Server next to Interface.
- Click Add new entry next to Server.
- Expand Server.
- In the Name box, enter the server
identifier.
- In the Comment box, enter the comment.
- Click Logical System next to Server.
- Click Add new entry next to Logical
System.
- Expand logical-system.
- In the Name box, enter the logical
system name.
- In the Comment box, enter the comment.
- Click Routing Instance next to logical-system.
- Click Add new entry next to Routing
Instance.
- In the New routing-instance window,
enter the routing instance name.
- Click Routing Instance next to server.
- Click Add new entry next to Routing
Instance.
- In the New routing-instance window,
enter the routing instance name.
- Click Server next to BOOTP.
- Click Add new entry next to Server.
- Expand Server.
- Click Logical System next to Server.
- Click Add new entry next to Logical
System.
- In the Name box, enter the logical
system name.
- In the Comment box, enter the comment.
- Click Routing Instance next to logical-system.
- Click Add new entry next to Routing
Instance.
- In the New routing-instance window, enter the routing instance name.
- Click Routing Instance next to server.
- Click Add new entry next to Routing
Instance.
- In the New routing-instance window,
enter the routing instance name.
|
Enabling DNS Request Packet Forwarding
You can configure the router to support Domain Name System
(DNS) and Trivial File Transfer Protocol (TFTP) packet forwarding
for IPv4 traffic, which allows clients to send DNS or TFTP requests
to the router. The responding DNS or TFTP server recognizes the client
address and sends a response directly to that address. By default,
the router ignores DNS and TFTP request packets.
To enable DNS request packet forwarding in NSM:
- In the NSM navigation tree, select Device Manager > Devices.
- Click the Device Tree tab,
and then double-click the device to select it.
- Click the Configuration tab.
In the configuration tree, expand Forwarding Options
> Helpers > Domain.
 |
Note:
For configuring TFTP, expand Forwarding
Options > Helpers > TFTP.
|
- Add or modify settings as specified in Table 2.
- Click one:
- OK—Saves the changes.
- Cancel—Cancels the modifications.
Table 2: DNS and TFTP Configuration Details
| Task |
Your Action |
Specify the interface for monitoring and forwarding
DNS or TFTP requests.
|
- In the Comment box, enter the comment.
- In the Description box, enter the
description of BOOTP, DHCP, Domain Name System (DNS), or Trivial File
Transfer Protocol (TFTP) service, or of an interface that is configured
for the service.
- Click Interface next to Domain.
- Click Add new entry next to Interface.
- Expand Interface.
- In the Name box, enter the interface
for a DHCP and BOOTP relay agent.
- In the Comment box, enter the comment.
- Select the No Listen check box to
disable recognition of DNS requests or stop packets from being forwarded
on a logical interface, a group of logical interfaces, or a router.
- Select the Broadcast check box to
issue the DHCP or BOOTP request as a broadcast message.
- In the Descriptions box, enter the
description of BOOTP, DHCP, Domain Name System (DNS), or Trivial File
Transfer Protocol (TFTP) service, or of an interface that is configured
for the service.
- Click Server next to Interface.
- In the Comment box, enter the comment.
- In the Address box, enter the address
of the server.
- Expand Server.
- Click Logical System next to Server.
- Select logical-system or routing-instance.
- Click Server next to Domain.
- In the Comment box, enter the comment.
- In the Address box, enter the address
of the server.
- Expand Server.
- Click Logical System next to Server.
- Select logical-system or routing-instance.
|
Configuring a Port for a DHCP or BOOTP Relay Agent
You can a configure port for a DHCP or BOOTP relay agent
using this option.
To configure port for a DHCP or BOOTP relay agent
in NSM:
- In the NSM navigation tree, select Device Manager > Devices.
- Click the Device Tree tab,
and then double-click the device to select it.
- Click the Configuration tab.
In the configuration tree, expand Forwarding Options
> Helpers.
- Select Port.
- Add or modify settings as specified in Table 3.
- Click one:
- OK—Saves the changes.
- Cancel—Cancels the modifications.
Table 3: Port Configuration Details
| Task |
Your Action |
Configuring a Port.
|
- From the Name list, select the port
number.
- In the Comment box, enter the comment.
- In the Description box, enter the
description of BOOTP, DHCP, Domain Name System (DNS), or Trivial File
Transfer Protocol (TFTP) service, or of an interface that is configured
for the service.
- Expand Port.
- Click Interface next to Domain.
- Click Add new entry next to Interface.
- Expand Interface.
- In the Name box, enter the interface
for a DHCP and BOOTP relay agent.
- In the Comment box, enter the comment.
- Select the No Listen check box to
disable recognition of DNS requests or stop packets from being forwarded
on a logical interface, a group of logical interfaces, or a router.
- Select the Broadcast check box to
issue the DHCP or BOOTP request as a broadcast message.
- In the Descriptions box, enter the
description of BOOTP, DHCP, Domain Name System (DNS), or Trivial File
Transfer Protocol (TFTP) service, or of an interface that is configured
for the service.
- Click Server next to Interface.
- Expand Server.
- In the Comment box, enter the comment.
- In the Address box, enter the address
of the server.
- Click Logical System next to Server.
- Select the corresponding logical system.
- Click Server next to Port.
- In the Comment box, enter the comment.
- In the Address box, enter the address
of the server.
- Click Logical System next to Server.
- Select the corresponding logical system.
|
Configuring Tracing Operations for BOOTP, DNS, and TFTP Packet
Forwarding
You can configure tracing operations for BOOTP, DNS,
and TFTP packet forwarding using this option. BOOTP, DNS, and TFTP
forwarding tracing operations track all BOOTP, DNS, and TFTP operations
and record them in a log file. The logged error descriptions provide
detailed information to help you solve problems faster.
To configure tracing operations in NSM:
- In the NSM navigation tree, select Device Manager > Devices.
- Click the Device Tree tab,
and then double-click the device to select it.
- Click the Configuration tab.
In the configuration tree, expand Forwarding Options
> Helpers > TFTP.
- Select Traceoptions.
- Add or modify settings as specified in Table 4.
- Click one:
- OK—Saves the changes.
- Cancel—Cancels the modifications.
Table 4: Traceoptions Configuration
Details
| Task |
Your Action |
Define tracing operations for event policy.
|
- In the Comment box, enter the comment
for the traceoptions.
- Select the No Remote Trace check
box to disable remote tracing globally or for a specific tracing operation.
- From the Level list, select the level.
|
Specify the name of the file to
receive the output of the tracing operation and the maximum number
of trace files.
|
- In the Comment box, enter the comment
for the file.
- In the Filename box, enter the name
of the file to receive the output of the tracing operation.
- In the Size box, enter the maximum
size of each trace file, in kilobytes (KB), megabytes (MB), or gigabytes
(GB).
- From the Files list, select the maximum
number of trace files.
Range: 2 through 1000.
Default: 3
- Select one of the following:
- world-readable—To enable unrestricted
file access
- no-world-readable—To
restrict file access to owner. This is the default setting.
- In the Matchbox, enter the regular
expression.
|
Specify the tracing operation to
perform
|
- Click Add new entry next to Flag.
- From the Name list, select the flag.
- In the Comment box, enter the comment
for the flag.
|
Published: 2009-08-23