| Table of Contents |
|---|
| Note |
|---|
To avoid investing a lot of effort into this only to realize that there’s a requirement that can’t be satisfied, make sure that all the below requirements are satisfied Important Notice: Be sure to review and meet all the requirements listed below early in the process . In particular we’ve had problems with customers not realizing that their setup and policies fails the to prevent any unexpected issues. We've seen some customers face challenges, particularly with the "no-NAT" requirement, described below. If you need assistance, don't hesitate to reach out to your Customer Support Manager for help. |
Use cases:
Positioning with DNA Spaces
FMF with DNA Spaces
...
That means there should be no NAT or proxy between the clients and the Proxy-LIPI server.
| Note |
|---|
...
Ensure this requirement is |
...
reviewed by your IT department, specifically someone with expertise in network configuration, early in the process to avoid potential issues. |
Installation, running and basic usage
...
| Code Block |
|---|
sudo docker ps -a sudo docker logs -f <container_id> |
Upgrading, Restarting, and
...
Maintenance
There can be many reasons why you want to restart the container. When it starts, it downloads a certificate and a configuration associated with your LIPI API key, and if any of those have changed, you need to restart in order to see the effects of those changes. Changes to these things require a restart to take effect:
...
LIPI-Cisco (DNA) Spaces diagram
FAQ
| Info |
|---|
Q: Do we need a static NAT so that MAZEMAP can communicate with it ? Specifically this would be required if we require inbound access rules on the Firewall not just outbound. A: We do not need inbound access. |
...