Bug ID 569814: iRule "nexthop IP_ADDR" rejected by validator

Last Modified: Oct 01, 2018

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 13.0.0

Fixed In:
13.1.0, 13.0.0 HF1, 12.1.3.4

Opened: Jan 25, 2016
Severity: 4-Minor
Related AskF5 Article:
K30240351

Symptoms

The nexthop command allows an administrator the ability to specify a forwarding address in an iRule. The form which takes an IP address may be rejected by the validator with an error message of the form: 01070151:3: Rule [/Common/irule_example] error: Unable to find vlan, vlangroup or tunnel (10.0.0.1) referenced at line 2: [nexthop 10.0.0.1]

Impact

The iRule containing the 'nexthop IP_ADDR' command cannot be associated with a virtual server.

Conditions

This occurs when the nexthop command contains only the IP address, for example: when HTTP_REQUEST { nexthop 10.0.0.1 }

Workaround

The 'nexthop VLAN IP_ADDR' form of the command does pass the validator. Choose the named vlan on which IP_ADDR can be reached. For example: when HTTP_REQUEST { nexthop internal 10.0.0.1 }

Fix Information

Validator now allows 'nexthop IP_ADDR' in iRules.

Behavior Change