Applies To:

Show Versions Show Versions

sol14331: Adding a self IP address to a VLAN that is a member of a non-default route domain may fail
Known IssueKnown Issue

Original Publication Date: 04/18/2013

Description

Adding a self IP address to a VLAN that is a member of a non-default route domain may fail.

This issue occurs when all of the following conditions are met:

  • A non-default route domain is configured as the Partition Default Route Domain for an administrative partition other than /Common, and subsequently a new VLAN is configured.
  • You attempt to add a self IP address to the VLAN.

    The following example illustrates the sequence of events that result in this issue:

    • The /PartitionExample administrative partition is added.
    • A non-default route domain 1 is added as the Default Route Domain for the /PartitionExample partition.
    • A VLAN named vlanExample is subsequently added to the /PartitionExample.
    • Attempting to add a self IP address to the /PartitionExample/vlanExample VLAN fails.

Impact

You cannot add the self IP address to the affected VLAN.

Symptoms

As a result of this issue, you may encounter the following symptoms:

  • Error messages with the following syntax are logged to the /var/log/ltm file:

    01070712:3: Caught configuration exception (0), Cannot get device index for <VLAN-Name> in <Route-Domain-Name> - ioctl failed: No such device - net/validation/routing.cpp, line 353.

    For example, if you add a new self IP with a VLAN named vlanExample, where the VLAN's route domain is named rdExample, the error message may appear similar to the following example:

    01070712:3: Caught configuration exception (0), Cannot get device index for vlanExample in rdExample - ioctl failed: No such device - net/validation/routing.cpp, line 353.

Status

F5 Product Development has assigned ID 401193 to this issue. F5 has confirmed that this issue exists in the products listed in the Applies To box, located in the top right corner of this article. For information about releases or hotfixes that resolve this issue, refer to the following table:

Type of Fix
Versions Fixed
Related Articles
Release 11.3.0 SOL2200: Most recent versions of F5 software
Hotfix 11.2.1 HF4
SOL9502: BIG-IP hotfix matrix

Workaround

To work around this issue, you can remove the affected configuration that does not allow you to add the new self IP address to the affected VLAN, and recreate the configuration in the recommended order. To do so, perform the following procedures:

  • Remove the affected configuration
  • Re-create the desired configuration
  • Verify the configuration

Remove the affected configuration

Impact of workaround: Removal of the affected configuration may disrupt services that are already in use. F5 recommends that you perform this procedure during a scheduled maintenance window for the affected BIG-IP system.

  1. Log in to the Traffic Management Shell (tmsh) by entering the following command:

    tmsh

    Note: If you are currently logged in to the tmsh shell, you can skip this step.
  2. Modify the related administrative partition to use ID 0 as its default route domain, using the following command syntax:

    modify /auth partition <Partition-Name> default-route-domain 0

    For example, to modify the related administrative partition named ResourceA, type the following command:

    modify /auth partition ResourceA default-route-domain 0

  3. Delete the affected VLAN that failed to create the self IP address, using the following command syntax:

    delete /net vlan /<Partition-Name>/<VLAN-Name>

    For example, to delete the VLAN named vlan-rd1234 that belongs to administrative partition named ResourceA, type the following command:

    delete /net vlan /ResourceA/vlan-rd1234

  4. Delete the affected route domain, using the following command syntax:

    delete /net route-domain /<Partition-Name>/<RD-Name>

    For example, to delete the affected route domain named rd1234 that belongs to administrative partition named ResourceA, type the following command:

    delete /net route-domain /ResourceA/rd1234

  5. Save the configuration using the following command:

    save /sys config

Re-create the desired configuration

F5 recommends that you re-create the affected configuration in the following order:

  • Create the required administrative partition, if it does not yet exist.
  • Under the desired administrative partition, create the required VLAN.
  • Under the desired administrative partition, create the required route domain and add the VLAN from Step 2 as a VLAN member to the route domain.
  • Set the desired route domain as the Partition Default Route Domain.
  • Create the new self IP address, as required.
  • Save the configuration.

To re-create the configuration in the recommended order, perform the following procedure:

Impact of workaround: None.

  1. Log in to the Traffic Management Shell (tmsh) by entering the following command:

    tmsh

    Note: If you are currently logged in to the tmsh shell, you can skip this step.
  2. Create the required administrative partition, using the following command syntax:

    create /auth <Partition-Name>

    For example, to create a new administrative partition named ResourceA, type the following command:

    create /auth partition ResourceA
  3. Change tmsh path to the desired administrative partition, using the following command syntax:

    cd /<Partition-Name>

    For example, to change to the tmsh path to administrative partition named ResourceA, type the following command:

    cd /ResourceA
  4. Under the desired administrative partition created in Step 3, create the required VLAN, using the following command syntax:

    create /net vlan <VLAN-Name> interfaces add { <Network-Interfaces-Number> } tag <VLAN-ID-Value>

    For example, to create the VLAN named vlan-rd1234 with network interface 1.1 and tag it with a VLAN ID 1234, type the following command:

    create /net vlan vlan-rd1234 interfaces add { 1.1 } tag 1234
  5. Create the required route-domain and add the VLAN created in Step 4, using the following command syntax:

    create /net route-domain <RouteDomain-Name> { id <RouteDomain-ID-Value> vlans add { <VLAN-Name> } }

    For example, to create the route-domain named rd1234 with ID value 1234 and add the VLAN vlan-rd1234 as a member to the route-domain, type the following command:

    create /net route-domain rd1234 { id 1234 vlans add { vlan-rd1234 } }
  6. Set the route domain created in Step 5 as the Partition Default Route Domain, using the following command syntax:

    modify /auth partition <Partition-Name> default-route-domain <Route-Domain-ID-Value>

    For example, to set the partition named ResourceA to use route domain ID 1234 as the partition default route domain, type the following command:

    modify /auth partition ResourceA default-route-domain 1234
  7. Create the desired self IP address with the VLAN create in Step 4, using the following command syntax:

    create /net self <IP-Address>/<Netmask> vlan <VLAN-Name>

    For example, to create a self IP address of 10.0.0.100 with netmask 255.255.255.0 with the VLAN vlan-rd1234, type the following command:

    create /net self 10.0.0.100/255.255.255.0 vlan vlan-rd1234
  8. Continue to create any additional required self IP addresses.
  9. Save the configuration, using the following command:

    save /sys config

Verifying the configuration

Impact of workaround: None.

  1. Log in to tmsh by entering the following command:

    tmsh

    Note: If you are currently logged in to the tmsh shell, you can skip this step.

  2. Change to the top-level administrative partition using the following command:

    cd /

  3. List the self IP address that is currently configured in the BIG-IP system, by typing the following command:

    list /net self recursive

Supplemental Information

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)