HIP distribution into Remote Networks

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

HIP distribution into Remote Networks

L1 Bithead

We have:

 

* Mobile Users

* Remote Networks

* Internal Gateways

 

We get Mobile Users userid and hip data by redistributing into the on-prem environment from all three Service Connections.

 

However, we setup distribution into Remote Networks from the Internal Gateway and TAC said it's not a supported configuration to distribute into Remote Networks, since it introduces a loop.

 

Is that correct?

Is there a way to prevent Remote Networks from redistributing back to the Service Connections? 

For others who use Mobile Users, Remote Networks, and Internal Gateways, how do you redistribute userid/hip appropriately?

 

 

0 REPLIES 0
  • 21 Views
  • 0 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!