Manual Chapter : Managing FEC Tunnel Profiles

Applies To:

BIG-IQ Centralized Management

  • 8.4.0
  • 8.3.0
  • 8.2.0
  • 8.1.0
  • 8.0.0
  • 7.1.0
back-action BIG-IQ Centralized Management: Local Traffic and Network Implementations

Managing FEC Tunnel Profiles

You can create or modify custom tunnel profiles in BIG-IQ Centralized Management, and then attach the resulting tunnel to a virtual server to deploy them to your managed devices.

When you create a profile, you specify a parent profile from which the custom profile inherits its properties. You then specify which of these properties you want to override. You can name any existing profile as a parent profile. When you modify a profile that has child profiles (that is, profiles that name your profile as a parent profile), all of the child profiles inherit any changes you made in the parent profile (except those you choose to override).

You must discover a device and import that device’s service configurations before you can add a profile to that device from BIG-IQ Centralized Management.

When you create a new profile, you specify the parameters that define the characteristics you want your virtual servers to use. Each virtual server that references this profile uses the parameters that you specify for this profile. Additionally, the parameters you define for this profile are given to the profiles that name this profile as their parent profile.

  1. At the top of the screen, click Configuration, then, on the left, click NETWORK > Tunnel Profiles.

    The screen displays the list of tunnel profiles defined on this device.

    Note: If you select the check box for a tunnel profile, you can delete it. You can also view details about other configuration objects to which this tunnel profile relates.

  2. Click Create.

    The New tunnel profile screen opens.

  3. Type a Name for the tunnel profile you are creating.

  4. If the device for which you are creating this FEC tunnel profile is in a silo as part of a conflict resolution work flow, select that Silo here; otherwise, leave the default setting.

    Note: For detailed work flows explaining how you can use a silo to resolve configuration object conflicts, refer to BIG-IQ: Resolving Device Object Conflicts on support.f5.com.

  5. For Partition, type the name of the BIG-IP device partition on which you want to create the profile.

  6. Select the Parent Profile from which you want your profile to inherit settings.

    Note: The parent profile you select determines the value of the profile parameters for this profile. You can override these values, but if you do not, changes made to parameters in the parent profile propagate to all child profiles.

    Values for the selected parent profile display. There are two controls for each field. The first one (a check box) controls whether you want to override the inherited value for that field. The second control (the type varies by field) sets the value you want for the parameter.

  7. For any settingsyou want to override, select the Override check box and then specify the value you want for the field you selected.

    Note: You can select Override All if you want to override all of the parent profile parameter values.

    Important: If you override a parent profile parameter, regardless of whether or not you change the parameter’s value, then future changes to the parent’s parameter value will not be inherited by this profile.

    Note: For detailed information on the impact of using a particular profile parameter value, refer to BIG-IP Local Traffic Management: Profiles Reference on support.F5.com.

  8. Click Save & Close.

    The system creates the new profile you specified and adds it to the list of profiles. You can now use the profile you created. You can select it when you configure a virtual server. You can also use it as a parent profile to base new BIG-IP tunnel profiles on.

Changes that you make are made only to the pending version. The pending version serves as a repository for changes you stage before deploying them to the managed device. Object settings for the pending version are not the same as the object settings on the actual BIG-IP device until they are deployed or discarded.

To pin this profile to specific devices, click Configuration > LOCAL TRAFFIC > Pinning Policies.

Note: For details about how pinning works, refer to Managing Object Pinning on support.f5.com.

When you finish specifying the settings for this profile, you need to evaluate and then deploy the changes to the target device. Until you deploy the changes stored in the pending version, objects on the managed device are not changed.

When you edit a profile, you can revise the parameters that define the characteristics that you want your virtual servers to use. Each virtual server that references this profile uses the parameters you specify for this profile. Additionally, the parameters you define for this profile are given to the profiles that name this profile as their parent profile.

  1. At the top of the screen, click Configuration, then, on the left, click NETWORK > Tunnel Profiles.

    The screen displays the list of tunnel profiles defined on this device.

    Note: If you select the check box for a tunnel profile, you can delete it. You can also view details about other configuration objects to which this tunnel profile relates.

  2. Click the name of the profile you want to edit.

    The screen displays the current settings for the selected profile.

  3. Under Referenced by, note the virtual servers and profiles that refer to this profile.

    Changes you make to this profile impact all of the virtual servers listed here.

    Any changes you make to this profile are also inherited by all profiles listed here that name this profile as their parent profile.

  4. Under the Override All check box, select the check box corresponding to any setting you want to override, and then specify the value you want for the setting you selected.

    Note: You can select Override All if you want to override all of the parent profile parameter values.

    Note: If you are editing a root profile, the override check boxes are disabled. Because a root profile does not have a parent profile, it does not inherit any settings, so there are no values to override.

    Note: For detailed information on the impact of using a particular profile parameter value, refer to BIG-IP Local Traffic Management: Profiles Reference on support.F5.com.

  5. When your edits are complete, click Save & Close.

    The system updates the profile with the settings you specified and adds it to the list of profiles.

Changes that you make are made only to the pending version. The pending version serves as a repository for changes you stage before deploying them to the managed device. Object settings for the pending version are not the same as the object settings on the actual BIG-IP device until they are deployed or discarded.

If you want to pin this profile to specific devices, click Configuration > LOCAL TRAFFIC > Pinning Policies.

Note: For details about how pinning works, refer to Managing Object Pinning on support.f5.com.

When you finish revising the settings for this profile, you next need to evaluate and then deploy the changes to the target device. Until you deploy the changes stored in the pending version, objects on the managed device are not changed.