Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 1990 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Replacing a host definition on an ASG leaves interface binding in place

rbremer
When creating a new host definition on the ACC 2.200 and deploying it to an ASG, which already has that definition in place (using the replace: data option), the definition will be correctly replaced, however, if it was bound to an interface on the ASG before, this binding will be retained and there is no way to change it (as you can't define interface bindings on the ACC).

Only solution is to delete and redeploy the definition.

Sounds like a bug to me.

Ronny


This thread was automatically locked due to age.
Parents
  • 0
    Ronny, binding a definition to a specific interface is very rarely necessary and can be the cause of mysterious problems when unneeded.  I'd recommend you make the same replacement of any other "bound" definitions you have.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • 0
    Ronny, binding a definition to a specific interface is very rarely necessary and can be the cause of mysterious problems when unneeded.  I'd recommend you make the same replacement of any other "bound" definitions you have.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
  • 0 in reply to BAlfson
    Ronny, binding a definition to a specific interface is very rarely necessary and can be the cause of mysterious problems when unneeded.  I'd recommend you make the same replacement of any other "bound" definitions you have.

    Cheers - Bob


    Bob,

    I agree, it was something the client needed for specific firewall rules when using a VPN connection, but it is no longer required. So thats why we had the bound definitions and the issue replacing them [:)]

    Ronny
Unfiltered HTML