APC UPS Data Center & Enterprise Solutions Forum
Schneider, APC support forum to share knowledge about installation and configuration for Data Center and Business Power UPSs, Accessories, Software, Services.
Posted: 2021-06-30 06:59 AM . Last Modified: 2024-03-07 11:41 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 06:59 AM . Last Modified: 2024-03-07 11:41 PM
I am having issues configuring the PBE Agent on a few of my Solaris 10 x86 servers. I do know how to access the web GUI using http://localhost:3052, but I am getting looped back to the login page, without mention of error, whenever I attempt to log in. I have tried using loopback and the ip-specific address, but I get the same problem.
Here's the fun part. The web interface works perfectly for many of my other machines (all Solaris 10 x86), and furthermore, I can access the GUI on the troubled servers if I network them and substitute their opposing ip addresses instead of their own (i.e. using machine A to access machine B's PBE Agent, using machine B's ip-address).
This is what I have attempted to do so far (not in any particular order):
1. Stop/Restart the daemon process (S99PBEAgent)
2. Uninstall/Reinstall PBEAgent
3. Reboot (on multiple init levels)
4. Checked and double-checked serial port specifications (and different configurations of such)
I am currently using Java 1.5.0_12-b04, which is well above the required 1.4.2 (not to mention the fact that PBE Agent functions properly on many other machines AND I can access the agent from networked machines).
I am working in a trusted network system, and would prefer being able to only access the machine's own PBE Agent as opposed to any network setup.
In addition, I would also prefer being able to not have to use the web browser to access PBE Agent. Is there any other optional interfaces (or files I can alter) for shutdown configuration?
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 07:00 AM . Last Modified: 2024-03-07 11:41 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 07:00 AM . Last Modified: 2024-03-07 11:41 PM
I am having issues configuring the PBE Agent on a few of my Solaris 10 x86 servers. I do know how to access the web GUI using http://localhost:3052, but I am getting looped back to the login page, without mention of error, whenever I attempt to log in. I have tried using loopback and the ip-specific address, but I get the same problem.
Here's the fun part. The web interface works perfectly for many of my other machines (all Solaris 10 x86), and furthermore, I can access the GUI on the troubled servers if I network them and substitute their opposing ip addresses instead of their own (i.e. using machine A to access machine B's PBE Agent, using machine B's ip-address).
This is what I have attempted to do so far (not in any particular order):
1. Stop/Restart the daemon process (S99PBEAgent)
2. Uninstall/Reinstall PBEAgent
3. Reboot (on multiple init levels)
4. Checked and double-checked serial port specifications (and different configurations of such)
I am currently using Java 1.5.0_12-b04, which is well above the required 1.4.2 (not to mention the fact that PBE Agent functions properly on many other machines AND I can access the agent from networked machines).
I am working in a trusted network system, and would prefer being able to only access the machine's own PBE Agent as opposed to any network setup.
In addition, I would also prefer being able to not have to use the web browser to access PBE Agent. Is there any other optional interfaces (or files I can alter) for shutdown configuration?
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 06:59 AM . Last Modified: 2024-03-07 11:41 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 06:59 AM . Last Modified: 2024-03-07 11:41 PM
I have came to a similar conclusion, and am attempting to load on even more machines accross the board. For all intents and purposes, every machine (considering we are in an evaluation mode) is loaded exactly the same, from OS up. We do have different hardward configurations, which I am testing at the moment.
In addition, as previously stated, even though I can not log in locally on the "trouble" servers, I can access their respective PBE Agents from networked machines. Even the two machines who can not log in locally can access each other's PBE Agent from the web browser.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 06:59 AM . Last Modified: 2024-03-07 11:41 PM
Hello,
It seems like there may be a problem with the Microsoft Loopback Adapter (is there one installed on each machine?) You stated that all of the machines are installed the same, and just for clarification, there are some servers in this setup which work with the http://127.0.0.1:3052 and some that do not. If that is the case, I would try to re-install the loopback adapter. If none of the machines can be accessed through their loopback, that may be the root cause of the problem.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 06:59 AM . Last Modified: 2024-03-07 11:41 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 06:59 AM . Last Modified: 2024-03-07 11:41 PM
What browser are you using?
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 06:59 AM . Last Modified: 2024-03-07 11:41 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 06:59 AM . Last Modified: 2024-03-07 11:41 PM
We do not have any Microsoft components/software installed on the machines. The machines that do work can utilize all variations of access (loopback, localhost, exact ip's). The machines that do not work can not use any variations whatsoever.
The web browser we are using is Mozilla rev. 1.7 for SunJava for use on a SunOS i86pc.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 07:00 AM . Last Modified: 2024-03-07 11:41 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 07:00 AM . Last Modified: 2024-03-07 11:41 PM
It sounds to me like the settings you are using in Mozilla that are preventing the Java from loading properly. Perhaps under Tools>Options>Content you have java disabled? There are other settings under Tools options that may help as well. I would try comparing your settings from a working machine vs. a non-working machine to see if there are any other differences, java or security related.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 07:00 AM . Last Modified: 2024-03-07 11:41 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 07:00 AM . Last Modified: 2024-03-07 11:41 PM
I am fairly certain my java/Mozilla configuration is sufficient.
As stated previously, even though machine A and machine B can not manage themselves locally, machine A can manage machine B remotely, and vice versa.
I have consulted with APC (prior to these posts) and have been informed that all Solaris 10 testing has been done as remote management with a Windows machine.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 07:00 AM . Last Modified: 2024-03-07 11:41 PM
Hello,
If the information you stated is correct, then there is something that is not software related that is causing a conflict of interest. If B can log into A without a problem, and A can log into B without a problem, then there is a loopback conflict that is not allowing A to access A and B to not access B.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 07:00 AM . Last Modified: 2024-03-07 11:41 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 07:00 AM . Last Modified: 2024-03-07 11:41 PM
I tried searching around google and found some documentation about blocking traffic on the loopback address of a Solaris machine. This might be something worth investigating as it doesn't appear to be a port or browser issue. I misunderstood your comment earlier and was under the impression A and B couldn't access their own interfaces or each others.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 07:00 AM . Last Modified: 2024-03-07 11:41 PM
Link copied. Please paste this link to share this article on your social media post.
Posted: 2021-06-30 07:00 AM . Last Modified: 2024-03-07 11:41 PM
I am having issues configuring the PBE Agent on a few of my Solaris 10 x86 servers. I do know how to access the web GUI using http://localhost:3052, but I am getting looped back to the login page, without mention of error, whenever I attempt to log in. I have tried using loopback and the ip-specific address, but I get the same problem.
Here's the fun part. The web interface works perfectly for many of my other machines (all Solaris 10 x86), and furthermore, I can access the GUI on the troubled servers if I network them and substitute their opposing ip addresses instead of their own (i.e. using machine A to access machine B's PBE Agent, using machine B's ip-address).
This is what I have attempted to do so far (not in any particular order):
1. Stop/Restart the daemon process (S99PBEAgent)
2. Uninstall/Reinstall PBEAgent
3. Reboot (on multiple init levels)
4. Checked and double-checked serial port specifications (and different configurations of such)
I am currently using Java 1.5.0_12-b04, which is well above the required 1.4.2 (not to mention the fact that PBE Agent functions properly on many other machines AND I can access the agent from networked machines).
I am working in a trusted network system, and would prefer being able to only access the machine's own PBE Agent as opposed to any network setup.
In addition, I would also prefer being able to not have to use the web browser to access PBE Agent. Is there any other optional interfaces (or files I can alter) for shutdown configuration?
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.