piyush_mehta
March 20 2009, 03:18 PM
Hi,
I installed Zyrion to learn more about the product. Here are my general notes on the installation and preliminary exploration. Please note that I am coming to this product from the dark so to speak - so some of the comments may be more of the nature of 'operator ignoramus'.
Thx.,
Piyush
Installation
-----------
Initial installation stalled (maybe because I had a lot of other activity going on on the computer?) and did not complete. There was no immediate sense of where to look for help.
I needed to kill the installation from Windows Task Manager. Traverse did seem to have installed though - and I tried to start all components. Two however would not start (including he Web Application component). Neither would the web console page launch. Realizing that this is not going to cut it, I decided to reinstall the product. Re-installation failed -
in a couple of places. When I asked it not to reuse existing data - I figured it would be able to start anew - but it complained
about not being able to set things up since they already preexist. I was forced to abandon that install. The next
attempt to install I picked the option to use the data - but subsequently it failed again - with an error message that was
not clear to me. Finally decided to uninstall the software - which went pretty well.
Rebooted the system and started a new installation - this time with minimum other activity on the system. Installation went well.
I was popped a question about ports - something I had not seen the earlier install. In the page with three settings, where the last setting is
'mail', I chose to leave that blank this time around. Also, in the option to start the services automatically, I chose not to have
them started automatically. This time the installation completed successfully.
All components, except the Web Application component started successfully. The webapp.stdout log file indicated that the binding on port 8005 did not work. Upon using the
netstat command (netstat -ano) and the Windows Task Manager, determined that there is another tomcat instance that is already
in bind on 8005. Googling indicated that this is a server port (likely used for shutdown). Note that during installation, when prompted for the HTTP port andSSL port, I had elected non-standard values for the ports as I was aware I had another instance of Tomcat running. However, that form did not present this port to be changed. Changed the tomcat server file
for traverse to use 8006 (<Server port="8006" shutdown="SHUTDOWN" debug="0">). This time around the Web Application component started just fine.
Basic Exploration
----------------
For the first time, I could launch the Traverse Web Application (http://127.0.0.1:84). Logged in as zyrion/zyrion. Was surprised though to see 30 failed tests of 32 - a big red for the 'Traverse Server' device. Not sure why this is the case - and I did not find information in the User Guide about the 'Availability and performance of Zyrion Traverse running on the local server' set of tests. I am running this software on a very bare-bones Windows XP home edition laptop - so I am not very surprised that these issues exist - I would have just liked to read up some more about these conditions.
I did not find a way to auto discover devices on the network. Please bear in mind that I have not really reviewed the documentation. But I was hoping the user interface would lead me into it naturally. Also, as a first time user, I had trouble with the 'Status' and 'Administration' tabs. My immediate reaction was to try to do things (including admin related things) right from all the items under the Status page. I need to give it more thought as to how the two can be seamless. This is in contrast to OpenNMS - it did an auto-discovery (discovered the laptop it was installed in and another device - the printer connected over the network. It did not detect the router/wireless access point). It also seems to have a more navigation-friendly layout. However, I had the same difficulty here - I was not able to readily understand how to add services to existing devices.
I finally did stumble upon the fact that the Administration Tab will allow me to add devices. I added my laptop (the same machine where I have installed the Traverse server). Without having gone through all the documentation, I was not quite sure how to set up the tests. I opted to create new tests from the provided Application Profiles - but did not find anything for applications already installed on my computer - for instance tests formySQL on my machine. I picked up WIndows Generic Server and was merrily along my way with a bunch of ready tests. It was pretty nice to see all the stats, interface and service details pop up.
I clicked PANORAMA to learn more about that tab. I was presented with a FireFox window asking how I would like the panorama.jnlp file to be opened up. I picked the default response - Java Web Start Launcher. I was next presented with a warning box stating that the application's digital signature could not be verified. I left the box 'Always trust content from this publisher' unchecked and clicked on the Run button. I was next presented a credentials window to connect - and upon providing the information (account/password/port), I was able to connect. However, the port defaults to 80 (whereas, if possible, itshould've been correctly picked up from the tomcat server.xml file - I had set it up to be 84 during the Traverse installation). I exited the Panorama application. However, every time I want to access Panorama from within the Traverse web console, I have to go through these steps all over again.
OpenNMS
---------
There seemed to be a conflict between OpenNMS and Traverse. With all traverse components running, OpenNMS threw an exception and would not launch. Upon shutting all Traverse components, OpenNMS did launch successfully. I decided to troubleshoot it a bit to understand the issues. With Traverse components turned off and OpenNMS running, I turned on Traverse components one by one, starting with the Aggregated Database at the top. They all started up - and I can now access both interfaces. Need to understand this better.
I left all the Traverse components running, and stopped and started OpenNMS. This time OpenNMS started off correctly. Not sure at all what the issue/s are.
I installed Zyrion to learn more about the product. Here are my general notes on the installation and preliminary exploration. Please note that I am coming to this product from the dark so to speak - so some of the comments may be more of the nature of 'operator ignoramus'.
Thx.,
Piyush
Installation
-----------
Initial installation stalled (maybe because I had a lot of other activity going on on the computer?) and did not complete. There was no immediate sense of where to look for help.
I needed to kill the installation from Windows Task Manager. Traverse did seem to have installed though - and I tried to start all components. Two however would not start (including he Web Application component). Neither would the web console page launch. Realizing that this is not going to cut it, I decided to reinstall the product. Re-installation failed -
in a couple of places. When I asked it not to reuse existing data - I figured it would be able to start anew - but it complained
about not being able to set things up since they already preexist. I was forced to abandon that install. The next
attempt to install I picked the option to use the data - but subsequently it failed again - with an error message that was
not clear to me. Finally decided to uninstall the software - which went pretty well.
Rebooted the system and started a new installation - this time with minimum other activity on the system. Installation went well.
I was popped a question about ports - something I had not seen the earlier install. In the page with three settings, where the last setting is
'mail', I chose to leave that blank this time around. Also, in the option to start the services automatically, I chose not to have
them started automatically. This time the installation completed successfully.
All components, except the Web Application component started successfully. The webapp.stdout log file indicated that the binding on port 8005 did not work. Upon using the
netstat command (netstat -ano) and the Windows Task Manager, determined that there is another tomcat instance that is already
in bind on 8005. Googling indicated that this is a server port (likely used for shutdown). Note that during installation, when prompted for the HTTP port andSSL port, I had elected non-standard values for the ports as I was aware I had another instance of Tomcat running. However, that form did not present this port to be changed. Changed the tomcat server file
for traverse to use 8006 (<Server port="8006" shutdown="SHUTDOWN" debug="0">). This time around the Web Application component started just fine.
Basic Exploration
----------------
For the first time, I could launch the Traverse Web Application (http://127.0.0.1:84). Logged in as zyrion/zyrion. Was surprised though to see 30 failed tests of 32 - a big red for the 'Traverse Server' device. Not sure why this is the case - and I did not find information in the User Guide about the 'Availability and performance of Zyrion Traverse running on the local server' set of tests. I am running this software on a very bare-bones Windows XP home edition laptop - so I am not very surprised that these issues exist - I would have just liked to read up some more about these conditions.
I did not find a way to auto discover devices on the network. Please bear in mind that I have not really reviewed the documentation. But I was hoping the user interface would lead me into it naturally. Also, as a first time user, I had trouble with the 'Status' and 'Administration' tabs. My immediate reaction was to try to do things (including admin related things) right from all the items under the Status page. I need to give it more thought as to how the two can be seamless. This is in contrast to OpenNMS - it did an auto-discovery (discovered the laptop it was installed in and another device - the printer connected over the network. It did not detect the router/wireless access point). It also seems to have a more navigation-friendly layout. However, I had the same difficulty here - I was not able to readily understand how to add services to existing devices.
I finally did stumble upon the fact that the Administration Tab will allow me to add devices. I added my laptop (the same machine where I have installed the Traverse server). Without having gone through all the documentation, I was not quite sure how to set up the tests. I opted to create new tests from the provided Application Profiles - but did not find anything for applications already installed on my computer - for instance tests formySQL on my machine. I picked up WIndows Generic Server and was merrily along my way with a bunch of ready tests. It was pretty nice to see all the stats, interface and service details pop up.
I clicked PANORAMA to learn more about that tab. I was presented with a FireFox window asking how I would like the panorama.jnlp file to be opened up. I picked the default response - Java Web Start Launcher. I was next presented with a warning box stating that the application's digital signature could not be verified. I left the box 'Always trust content from this publisher' unchecked and clicked on the Run button. I was next presented a credentials window to connect - and upon providing the information (account/password/port), I was able to connect. However, the port defaults to 80 (whereas, if possible, itshould've been correctly picked up from the tomcat server.xml file - I had set it up to be 84 during the Traverse installation). I exited the Panorama application. However, every time I want to access Panorama from within the Traverse web console, I have to go through these steps all over again.
OpenNMS
---------
There seemed to be a conflict between OpenNMS and Traverse. With all traverse components running, OpenNMS threw an exception and would not launch. Upon shutting all Traverse components, OpenNMS did launch successfully. I decided to troubleshoot it a bit to understand the issues. With Traverse components turned off and OpenNMS running, I turned on Traverse components one by one, starting with the Aggregated Database at the top. They all started up - and I can now access both interfaces. Need to understand this better.
I left all the Traverse components running, and stopped and started OpenNMS. This time OpenNMS started off correctly. Not sure at all what the issue/s are.