http://community.xangati.com/ Xangati Community en-US Thu, 17 May 2012 13:05:00 +0000 http://bbpress.org/?v=1.0.2 q http://community.xangati.com/search.php http://community.xangati.com/topic.php?id=30#post-176 Sat, 05 May 2012 08:02:14 +0000 yiwai 176@http://community.xangati.com/ <p>good </p> http://community.xangati.com/topic.php?id=47#post-153 Thu, 26 Apr 2012 20:32:09 +0000 XangatiTonja 153@http://community.xangati.com/ <p>View Full Release at <a href="http://searchservervirtualization.techtarget.com/guides/Products-of-the-Year-2011">techtarget.com</a> </p> http://community.xangati.com/topic.php?id=45#post-150 Mon, 23 Apr 2012 17:45:28 +0000 XangatiTonja 150@http://community.xangati.com/ <p>Thanks Mike. Xangati is fully compatible with XenDesktop today. We have a full integration with the XenDesktop agent that allows us to delve deep into the VDI protocol. Today, Xangati supports XenDesktop running on a VMware backend. We anticipate supporting additional hypervisors later in the year. </p> http://community.xangati.com/topic.php?id=45#post-149 Mon, 23 Apr 2012 17:31:16 +0000 mystlawer 149@http://community.xangati.com/ <p>Your product looks great, but is limited to vmware infrastructure. Are there plans to expand the VI which Xangati can monitor and manage?</p> <p>Thanks in advance.</p> <p>-&lt;M&gt;-<br /> Mike </p> http://community.xangati.com/topic.php?id=43#post-77 Fri, 10 Feb 2012 16:49:08 +0000 XangatiTonja 77@http://community.xangati.com/ <p>Rodrohan,</p> <p>Go to Configure&gt;My Network and make sure that the IP address of your iSCSI device falls within the “My Network” address range. If it is outside “My Network”, this could be what is wrong. </p> http://community.xangati.com/topic.php?id=43#post-76 Thu, 09 Feb 2012 22:04:54 +0000 rodrohan 76@http://community.xangati.com/ <p>I just downloaded and installed the trial of Xangati (XSR8U2) and have the XFS_XNR4U2 package installed on one host running ESX 4.1.</p> <p>I can see the datastore statistics (IOPS, etc) for only the local disks on that host. Should I not be able to see the statistics from my SAN (iSCSI) datastores as well? Is there any extra configuration that I'm missing? </p> http://community.xangati.com/topic.php?id=42#post-75 Thu, 26 Jan 2012 09:33:54 +0000 XangatiTonja 75@http://community.xangati.com/ <p><a href="http://www.youtube.com/watch?v=ov8sXIuh54o" rel="nofollow">http://www.youtube.com/watch?v=ov8sXIuh54o</a></p> <p>This in-depth tour of the Xangati dashboard discusses how to generate and analyze the data displayed within the Xangati VI and VDI Dashboards. It reveals virtual infrastructure behavior and shows how to spot anomalies in performance issues through reports and recordings. This video is ideal for someone who has installed the trial version and wants to know basic navigation techniques for their own infrastructure. </p> http://community.xangati.com/topic.php?id=41#post-74 Wed, 11 Jan 2012 18:55:15 +0000 XangatiTonja 74@http://community.xangati.com/ <p>mouimet - in response to your question: if you have 3.2.0.7 or above, sflow is available.</p> <p>Follow these steps to enable SFlow on your Power Connect device:</p> <p> 1.Enter configuration mode.<br /> config</p> <p> 2.Issue the follow commands:<br /> sflow 1 destination owner 1 timeout 4294967295<br /> sflow 1 destination 10.10.10.10 2055<br /> sflow 1 polling ethernet 1/g1-1/g47 30<br /> sflow 1 sampling ethernet 1/g1-1/g32 1024</p> <p> 3.Copy this running configuration to the startup configuration and reboot the device.<br /> copy running-config startup-config</p> <p> 4.Check that the running configuration is correct.<br /> show running</p> <p>Let us know if you have additional questions. </p> http://community.xangati.com/topic.php?id=41#post-73 Wed, 11 Jan 2012 11:55:10 +0000 mouimet 73@http://community.xangati.com/ <p>Hi all. Have anyone successfully enabled sflow from a Dell Powerconnect switch (62xx Series) to Xangati?Interested in the steps you have taken to get this working. </p> http://community.xangati.com/topic.php?id=39#post-55 Mon, 24 Oct 2011 20:45:54 +0000 XangatiTonja 55@http://community.xangati.com/ <p>Hi j.glumac :</p> <p>Here is a link &lt;https://xangati.box.net/shared/z0kvkgla50y78qjop8r9&gt; to the one-pager product specs for the XMD-E product and version you have. This doc is intended for users trialing the software so just disregard the "Length of Evaluation" line.</p> <p>If you have more questions, also feel free to ask <a href="mailto:support@xangati.com">support@xangati.com</a> directly.</p> <p>Thank you! </p> http://community.xangati.com/topic.php?id=39#post-54 Mon, 24 Oct 2011 16:03:40 +0000 j.glumac 54@http://community.xangati.com/ <p>Working on installing Xangati for VDI and were hoping that someone had some hardware guidelines for disk size, disk speed, and RAID level that we should be using.</p> <p>Thanks. </p> http://community.xangati.com/topic.php?id=36#post-51 Thu, 02 Jun 2011 22:57:54 +0000 alee 51@http://community.xangati.com/ <p>What was the solution to this? I could only get the dashboard to show traffic when playing back a recording. Ultimately I would like to view the live console with vm traffic. Thank You </p> http://community.xangati.com/topic.php?id=36#post-50 Thu, 19 May 2011 22:18:31 +0000 XangatiSteve 50@http://community.xangati.com/ <p>Thanks for posting your question. I am just responding that this has been answered by our support team via telephone. </p> http://community.xangati.com/topic.php?id=36#post-49 Thu, 19 May 2011 14:09:46 +0000 einsteinagogo 49@http://community.xangati.com/ <p>Hi, we've just started a trial of Xangati 4.1 Download, Imported the OVF, start VM, configured networking, made sure we've got a prom. port group for Xangati, made sure it's Tagged with 4095.</p> <p>But we observe no traffic.</p> <p>Zero.</p> <p>Any ideas? </p> http://community.xangati.com/topic.php?id=35#post-48 Wed, 18 May 2011 16:31:22 +0000 j.baker 48@http://community.xangati.com/ <p>Here is a working Cisco 2600 config with Netflow setup. Also DHCP and NAT are configured.</p> <pre><code>hostname cisco-2651 ! clock timezone gmt 0 clock summer-time BST recurring last Sun Mar 1:00 last Sun Oct 2:00 ip subnet-zero ip flow-cache entries 1024 ip flow-cache timeout inactive 60 ip flow-cache timeout active 1 ip flow-cache feature-accelerate ip cef ! ! ip domain-name foo.bar.com ip name-server 192.168.253.230 ip name-server 212.23.6.100 ip dhcp excluded-address 192.168.88.1 ! ip dhcp pool 0 network 192.168.88.0 255.255.255.0 domain-name foo.bar.com dns-server 192.168.253.230 212.23.6.100 default-router 192.168.88.1 ! ! interface FastEthernet0/0 bandwidth 100000 ip address 192.168.253.221 255.255.255.0 ip nat outside ip route-cache policy ip route-cache flow duplex auto speed 100 no cdp enable ! interface FastEthernet0/1 bandwidth 100000 ip address 192.168.88.1 255.255.255.0 ip nat inside duplex auto speed 100 ! interface Ethernet1/0 no ip address shutdown half-duplex ! ip default-gateway 192.168.253.254 ip nat inside source list 1 interface FastEthernet0/0 overload ip nat inside source static tcp 192.168.88.10 5900 192.168.253.221 5900 extendable ip flow-export source FastEthernet0/0 ip flow-export version 5 ip flow-export destination 192.168.253.110 2058 ip classless ip http server ip pim bidir-enable ! logging 192.168.253.220 access-list 1 permit 192.168.88.0 0.0.0.255 no cdp run snmp-server community public RO snmp-server community private RW ! ! line con 0 line aux 0 line vty 0 4 password password login ! ntp clock-period 17208075 ntp server 192.168.253.220 prefer ntp server 46.227.200.73 end</code></pre> http://community.xangati.com/topic.php?id=34#post-47 Wed, 18 May 2011 16:17:12 +0000 j.baker 47@http://community.xangati.com/ <p>You need to install NET-SNMP windows binaries</p> <p>You must edit the details to match your setup. The sflowcollector address is a hex value or the ip address of hte Xangati applaince.<br /> <pre><code>@echo off cls echo this script has been tested on a HP Procurve 2610-25 J9086A. echo you will need to have Net-SNMP 5.5.0 binaries installed. echo. echo this is a quick and dirty script to setup sflow to point towards a sflow collector. echo the sflowcollectorhex value is the ip address of the sflow collector in HEX without the dots. C0A8FDDC = 192.168.253.220 echo. echo Badly written by John Baker <a href="mailto:jbaker@ip-performance.co.uk">jbaker@ip-performance.co.uk</a> echo. set snmpwritecommunity=private set sflowport=6343 set switchip=192.168.253.83 set sflowcollectorhex=C0A8FD6E set xangatihostname=Xangati set sflowtimeout=10000000 set sflowsamplerate=60 set sflowsamplerheadersize=128 set pathtonetsmp=c:\usr\bin\ %pathtonetsmp%snmpset -v2c -c %snmpwritecommunity% %switchip% .1.3.6.1.4.1.14706.1.1.4.1.2.1 s %xangatihostname% .1.3.6.1.4.1.14706.1.1.4.1.3.1 i %sflowtimeout% .1.3.6.1.4.1.14706.1.1.4.1.4.1 i 1400 .1.3.6.1.4.1.14706.1.1.4.1.5.1 i 1 .1.3.6.1.4.1.14706.1.1.4.1.6.1 x %sflowcollectorhex% .1.3.6.1.4.1.14706.1.1.4.1.7.1 i %sflowport% .1.3.6.1.4.1.14706.1.1.4.1.8.1 i 5 echo get the number of interfaces on switch. will assume starts at 1 %pathtonetsmp%snmpget -v2c -Oq -OU -Ov -c %snmpwritecommunity% %switchip% .1.3.6.1.2.1.2.1.0 &gt;ethercountfile set /p ethercount= &lt;ethercountfile del ethercountfile /q set /a nicnum=1 set /a nicend=%ethercount%+1 :startloop IF %nicnum%==%nicend% GOTO END call %pathtonetsmp%snmpset -v2c -c %snmpwritecommunity% %switchip% .1.3.6.1.4.1.14706.1.1.5.1.3.11.1.3.6.1.2.1.2.2.1.1.%nicnum%.1 i 1 &gt;NUL call %pathtonetsmp%snmpset -v2c -c %snmpwritecommunity% %switchip% .1.3.6.1.4.1.14706.1.1.5.1.4.11.1.3.6.1.2.1.2.2.1.1.%nicnum%.1 i %sflowsamplerate% &gt;NUL call %pathtonetsmp%snmpset -v2c -c %snmpwritecommunity% %switchip% .1.3.6.1.4.1.14706.1.1.5.1.5.11.1.3.6.1.2.1.2.2.1.1.%nicnum%.1 i %sflowsamplerheadersize% &gt;NUL SET /a nicnum=%nicnum%+1 GOTO startloop :end</code></pre> http://community.xangati.com/topic.php?id=33#post-46 Mon, 18 Apr 2011 22:34:09 +0000 XangatiSteve 46@http://community.xangati.com/ <p>The release notes describe the known issues, notes, security and recommended practices in Xangati Software Release (XSR) 7 U1. Click here to view: <a href="https://xangati.box.net/shared/oqpfkdpnvd" rel="nofollow">https://xangati.box.net/shared/oqpfkdpnvd</a> </p> http://community.xangati.com/topic.php?id=32#post-44 Wed, 13 Apr 2011 20:53:09 +0000 esc 44@http://community.xangati.com/ <p>Free Xangati for ESX now comes with two NICs, I believe. So you can sniff and ping at the same time. </p> http://community.xangati.com/topic.php?id=32#post-43 Tue, 22 Mar 2011 23:15:31 +0000 XangatiSteve 43@http://community.xangati.com/ <p>@colin_hill</p> <p>Please accept my apology. I honestly believed that I had already posted a response to you. This issue was brought to our engineering team and they have already regenerated the code -- in direct response to these posts -- to resolve the issue you were having. I have your email and will send you the direct link for the regenerated code so you don't have to re-register.</p> <p>Best,<br /> Steve </p> http://community.xangati.com/topic.php?id=32#post-42 Tue, 22 Mar 2011 16:07:23 +0000 colin_hill 42@http://community.xangati.com/ <p>Hi - just to let you know we wont be continuing with the evaluation and will be removing the virtual appliance shortly.</p> <p>Since there has been no reponse with regards to the NICs it seems pointless to continue with the trial.</p> <p>I hope other people have better luck with the free evaluation. </p> http://community.xangati.com/topic.php?id=32#post-41 Mon, 14 Mar 2011 14:54:17 +0000 colin_hill 41@http://community.xangati.com/ <p>I have the same problem as foxguy - the appliance can't seem to do both jobs within its current configuration. </p> http://community.xangati.com/topic.php?id=32#post-40 Thu, 10 Mar 2011 22:32:23 +0000 foxguy 40@http://community.xangati.com/ <p>Can someone please clarify on how we are suppose to use this appliance with one virtual nic when we are placing it in the vswitch that is specified with the 4095 vlan id? I dont see a location to tag the vlan id on the management interface. When I have the ip address set and in the 4095 virtual switch I am unable to ping the appliance. When I move the vswitch into a vswitch that has the vlan id of the ip address block I am able to ping the appliance get to the management web but not capture traffic. </p> http://community.xangati.com/topic.php?id=32#post-39 Wed, 09 Mar 2011 04:44:43 +0000 XangatiSteve 39@http://community.xangati.com/ <p>Hi drrue -</p> <p>Thanks for your question. The Xangati XESX Free comes with a single NIC. In normal deployment, this NIC serves both as the management interface as well as the promiscuous mode “packet capture” interface. The Xangati XESX Free does not support additional NICs at this time. Xangati Management Dashboards support multiple vNICs for more complex configurations. Let me know if you are intereseted in a trial of the Management Dashboard. </p> http://community.xangati.com/topic.php?id=32#post-38 Tue, 08 Mar 2011 23:26:38 +0000 drrue 38@http://community.xangati.com/ <p>Recently deployed the free virtual appliance (XESX_XSR6US_ESX4) and found that it only came with one virtual nic configured. How do I configure a second nic so I can attach it to a promiscuous mode port group? </p> http://community.xangati.com/topic.php?id=31#post-37 Tue, 08 Feb 2011 16:31:39 +0000 j.baker 37@http://community.xangati.com/ <p>I would like to see support for authenticated SMTP servers. </p> http://community.xangati.com/topic.php?id=30#post-36 Tue, 08 Feb 2011 16:05:04 +0000 j.baker 36@http://community.xangati.com/ <p>If your main internet connection is connected to the same network switch as your VMware server running Xangati and if your switch support port mirroring, then you can configure Xangati to monitor flows to and from your router for your VM environment and your physical environment.</p> <p>You will need a spare NIC on your VMware server. You will need to setup a mirror port on your switch to mirror the Ethernet interface that the router is connected to. Correct the mirror port to the spare Ethernet port on the VM server.</p> <p>Within VMware make sure that the spare NIC is not associated with any other virtual network. Create a new vSwitch and assign the spare NIC. Edit the properties on this new VSwitch and then edit the VM Network, but not the vSwitch) that was created. Under the security tab enable Promiscuous Mode and set to accept.</p> <p>Now edit the settings on the virtual Xangati appliance with vSphere Client. Locate an unused network adapter. Normally there are four network adapters all assigned to the VM Network vSwitch. Locate a un-configured adapter (2-3 as 1 is the default) and change the network from the default vSwitch to your newly created vSwitch.</p> <p>You now need to run the Xangati appliance (it if was not already running). Then connect to the User Interface from a workstation and select the Setup menu and go to My Network. Make sure that your local subnet is added to the Include addresses. Then move to the Infrastructure Data Feeds.</p> <p>Press Add and enter the IP address of your VM server. Change the monitoring interface to the same on that you edited for the Xangati appliance. </p> <p>Press Finnish. If all went well you should see your traffic flows to/from your router. </p> <p>If not, re-check the port mirror and vSwitch setup.</p> <p>I have this running using the free version of Xangati, although you can only setup and monitor 10 identities (devices/IP). </p> http://community.xangati.com/topic.php?id=29#post-35 Mon, 20 Dec 2010 20:34:20 +0000 niversen 35@http://community.xangati.com/ <p>Integration with vSphere client</p> <p>If you are not using vCenter and still want to have a Xangati icon available to launch the Xangait UI directly from vSphere's management page, you may follow these guidelines:</p> <p>These steps will create a Xangati UI launch icon in vSphere client for easy access to Xangati UI:</p> <p>Save the file at the following address: <a href="https://(Xangati_IP_address)/xer_esxplugin.xml" rel="nofollow">https://(Xangati_IP_address)/xer_esxplugin.xml</a> and put it here:</p> <p>[vmware-vsphere-client]\Virtual Infrastructure Client\Plugins</p> <p>e.g., C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Plugins</p> <p>Of course, you will replace (Xangati_IP_address) and [vmware-vsphere-client] with the appropriate IP addresses for your environment.</p> <p>Recommended file name xer_plugin_ip.xml After saving the file, exit from vSphere client if you are already logged in. Login again to the esx where XER is a VM. The xangati icon will be visible in Home-&gt;admin area of vSphere client main window. </p> http://community.xangati.com/topic.php?id=20#post-26 Wed, 01 Dec 2010 21:55:28 +0000 niversen 26@http://community.xangati.com/ <p>Title: Understanding Xangati Licensing</p> <p>Xangati products are licensed “per socket”. Simply count the number of physical CPU sockets on the motherboard of your monitored hosts to get the number of socket licenses you need. The number of cores on each CPU is not important (i.e. a dual Quad-Core Nehelem server would use(2) socket licenses). For XESX and XESX-PRO, this is the number of sockets on the host you install on. For our larger Dashboards, it is the number of sockets used across the monitored hosts.</p> <p>As you upgrade from XESX to the Pro, and then to our Standard or Enterprise Dashboards, there are meaningful capacity and feature improvements that happen at every step. These capacities are not tied to the number of sockets, but to the license level. For example: an XESX-Pro supports up to 100 mapped identities. It does not matter if there one, two, or four sockets on the host. </p> <p>The easiest way to select the appropriate Xangati license is to use the feature/capacity table here (<a href="http://www.xangati.com/products/management-dashboards-2/" rel="nofollow">http://www.xangati.com/products/management-dashboards-2/</a>) to select the base functionality you need. Then just count up the number of sockets that you will be managing. In most cases, a Xangati “Starter Kit” will include the socket licenses you need.</p> <p>If you have a very large environment with tens or hundreds of thousands of IP addresses, you may also need to purchase "Identity Packs" to scale the number of identities. </p> http://community.xangati.com/topic.php?id=19#post-25 Mon, 15 Nov 2010 20:10:32 +0000 esc 25@http://community.xangati.com/ <p>Does the ESXi server where XFS didnt deploy successfully support DHCP addressing? (You may want to check what vSphere for the ESX says are the VMs and what their addresses are -- if DHCP didnt work, the XFS will not have an IP.) If DHCP-based addressing is not available on that server, XFS has to be deployed manually on that server. </p> http://community.xangati.com/topic.php?id=16#post-24 Mon, 15 Nov 2010 20:03:59 +0000 esc 24@http://community.xangati.com/ <p>The issue is very likely to be whitespace characters in the entry. Recommend clearing the field and reentering the subnet. </p> http://community.xangati.com/topic.php?id=17#post-23 Wed, 03 Nov 2010 21:44:42 +0000 ErikBussink 23@http://community.xangati.com/ <p>No problem Ben, </p> <p>I did indeed redeploy the Xangati for ESX trial to an ESXi 4.1 host, and ran the setup with the setupip/setupip account on the VM. I was then able to connect my browser to the XESX appliance and configure it.</p> <p>My problem was that I had not finished the setupip process and the java installer did not have the proper IP addresse of the appliance.</p> <p>Erik </p> http://community.xangati.com/topic.php?id=19#post-22 Wed, 03 Nov 2010 21:38:09 +0000 ErikBussink 22@http://community.xangati.com/ <p>Hello I've tried deploying multiple XFS probes in a vSphere 4.1 cluster. The XMD-E appliance was able to deploy the XFS on half the servers. On a particulier ESXi 4.1 host, it deployed the XFS probe but it must have stalled during the configuration, so I don't know if it's picking up netflow traffic or not. In the Xangati Management Dashboard I get the following error message in the XFS Deployment Status tab "Error failed checking tomcat state"</p> <p>I've attempted to redeploy the XFS four times to the same host and the result is the same.</p> <p>How can I correct this ?<br /> Thanks </p> http://community.xangati.com/topic.php?id=17#post-20 Fri, 22 Oct 2010 07:46:23 +0000 bvaux 20@http://community.xangati.com/ <p>Hi Erik,</p> <p>We have had a number of discussions on the phone and via email and i believe you now have some progress, can you please, on this forum, update to your current status.</p> <p>Best regards</p> <p>Ben Vaux </p> http://community.xangati.com/topic.php?id=16#post-19 Fri, 22 Oct 2010 00:12:57 +0000 XangatiJaymin 19@http://community.xangati.com/ <p>Hello Blockanz,</p> <p>I apologize for the trouble with the install. I agree that 10.64.8.0/21 is a valid subnet. I have installed the subnet myself without any issues. I understand that you are frustrated due to this very silly and annoying error. I would like to have an opportunity to make sure that we get to the bottom of this asap. My suggestion is that since this is a "potential bug", send an email to <a href="mailto:support@xangati.com">support@xangati.com</a> with some snapshots of your error. Also, provide the Help--&gt;About screen. </p> <p>Once we resolve the issue, we will post the information on the community page. Thx </p> http://community.xangati.com/topic.php?id=17#post-18 Thu, 21 Oct 2010 11:15:15 +0000 ErikBussink 18@http://community.xangati.com/ <p>Hello,<br /> I've sucessfully installed the XESX-P_XSR6U2_ESX4_Appliance on my vSphere ESXi 4.1. After having configured the IP address (maybe you need to add the link to the QuickStart Guide in the emails, rather than just links to Youtube videos) I connect to the XESX appliance. But launching the Xangati Management software the java installer from a Windows x86, Windows x64 with either Java JRE 6.0.18 or Java JRE 6.0.22, I get an error message "Application Error, Unable to launch the Application !"<br /> The details of the error message are "com.sun.deploy.net.FailedDownloadException: Unable to load resource: <a href="https://127.0.0.1:443/install.jnlp" rel="nofollow">https://127.0.0.1:443/install.jnlp</a>"</p> <p>For some reason, the install.jnlp replaces it's IP addresse defined with a simple 127.0.0.1. Even manually editing the .jnlp the application does a bit further before coming back to the same error with the ip addresse 127.0.0.1 </p>