Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.


Share this Page URL
Help

Chapter 4: Nokia Network Voyager > Frequently Asked Questions - Pg. 160

160 Chapter4·NokiaNetworkVoyager Frequently Asked Questions Q: When I log in to Nokia Network Voyager, will I be able to manage everything on the appliance? A: Nokia Network Voyager is role-based. Depending on the account you log in with, you might be able to manage all or only specific items for the appliance. Q: How can I determine what I have access to? A: If you do not have access to a system item, then the item does not appear in the navigation tree. Read-only access gives you access to the page, but with the buttons disabled. Q: How can I prevent another user from making system changes while I am logged in to Nokia Network Voyager? A: If you log in with an exclusive configuration lock, no other user can change the system configuration. Q: I went back one Web page and my changes are gone. What happened? A: You should not use the Back and Forward buttons of your Web browser while in Nokia Network Voyager. Because the browser caches the HTML page information, the latest page information might be lost when moving from page to page. To update the page information, you can use the Web browser reload or refresh button. Q: I am about to use my IPSO system for the first time. Is there anything I should know? A: When you set up your IPSO system for the first time, configure the basic Nokia Network Voyager options and change your SSL/TLS certificate from the default certificate. Q: What does IPSO use to secure client connections? A: To secure Nokia Network Voyager client connections to the IPSO system over the internet, IPSO uses the Secure Sockets Layer/Transport Layer Security (SSL/TLS) protocol. Q: I cannot access the Nokia Network Voyager interface. What could the problem be? A: Verify you are using the correct URL, that you are using the correct PEM-encoded certificate and private key, and that the certificate and private key are installed properly with the dashed begin and end lines. Finally, verify the HTTP daemon error message log.