This relates to the setup article for the OKM. IR4 and OKM Setup – InVue Help Center
DHCP:
- Get a DHCP address.
- Must be able to acquire an IP via DHCP.
- Access InVue DNS server
- Will look up CNAME for NNNNN.tenant.invue-am.com where NNNNN is the Installer Code
- Can access LIVE Access URL given to the customer.
- Uses port 443/8443
- Firmware updates
- must be able to access https://storage.googleapis.com
- Uses port 443/8443
Static IP:
- Static IP address
- Must have a designated static IP assigned by the IT team.
- Access InVue DNS server
- Will look up CNAME for NNNNN.tenant.invue-am.com where NNNNN is the Installer Code
- Can access LIVE Access URL given to the customer.
- Uses port 443/8443
- Firmware updates
- must be able to access https://storage.googleapis.com
- Uses port 443/8443
Finding Deployment URL from Installer Code
Let's do a DNS lookup of the deployment URL in a Windows command shell using the installer code!
This will also help us check if we can reach the URL from your connection, specifically through the ethernet port.
Steps:
- Get ready to connect your PC to the Ethernet cable that was plugged into OKM.
- It's time to open up the CMD window on your laptop/PC.
- Let's execute the CMD: nslookup -type=CNAME <installer_code>.ir4.lb.invue-am.com
- Don't forget to replace it with the specific installer code for the environment you are testing.
Example:
C:\>nslookup -type=CNAME 21233.ir4.lb.invue-am.com
Server: INVUE211.Omega.local
Address: 192.168.21.121
Non-authoritative answer:
21233.ir4.lb.invue-am.com canonical name = testtest.invue-am.com
Trace Route Test
This tells us the route that the OKM is taking to get to the server.
Windows: tracert 21233.ir4.lb.invue-am.com
MAC: traceroute 21233.ir4.lb.invue-am.com
Ping Test
This tells us if the OKM can get out and what IP it is pulling from the DNS to get out of the network.
Windows & MAC: ping 21233.ir4.lb.invue-am.com
Comments
0 comments
Please sign in to leave a comment.