Skip to main content

Posts

Netscaler AGEE plugin and Windows 8.1

I recently tried to access VPN site (Netscaler SSLVPN ) from Windows 8.1 laptop However i could not connect to the resources . After checking the logs , i found that the AGEE client version on the laptop was not correct as it did not match the server version we had (10.125.8) I downloaded the AGEE version specific to our Netscaler Environment (10.125.9) in our case. After installing this version of AGEE and restarting the laptop , i was then able to connect to the VPN resources. Hope this helps.

Find all active domain Users in a particular OU

Sometime s you need to find AD users in a particular OU who have logged on to any system  in past 90 days . I found this powershell query online that helped me to create a html report for all users with the logon times. $oldDate = (Get-Date).AddDays(-90).ToFileTime().toString() Get-ADUser -SearchBase 'OU=Users,dc=domain,dc=com' -Properties lastlogontimestamp -LDAPFilter "(lastlogontimestamp>=$oldDate)" |     select @{n='User';e={$_.name}}, @{n='LastLogOn';e={[datetime]::FromFileTime($_.lastlogontimestamp)}} |     ConvertTo-Html -Title 'Recent Users' | Out-File 'RecentUsers.html' Invoke-Item 'RecentUsers.html' Hope this helps.

NFS storage and ESXi 5.5 TCP delayed ack

By default the behavior of ESXi 5.5 is to have TCP  delayed_ack  set to 1  It caused some performance issues related to latency between the ESXi host and our NFS storage. We need to change the behavior by setting the value to 0 , so that latency issues are solved. vsish -e set /net/tcpip/instances/defaultTcpipStack/sysctl/_net_inet_tcp_delayed_ack 0 In order too ensure that delayed _ack is disabled across reboots we need to edit /etc/rc.local.d/local.sh and add the following line in there. vsish -e set /net/tcpip/instances/defaultTcpipStack/sysctl/_net_inet_tcp_delayed_ack 0 Hope this helps.

Unable to contact the management VM to configure Netscaler SDX

It may happen that when you start configuring Netscaler SDX (11500 in our case)  that you are unable to connect to the management VM  (svm) at all throughthe default IP 192.168.100.1 Ping , http , ssh to 192.168.100.1  doesnt work in our case the console connection did work  and we could ssh into 192.168.100.2 However ssh to 192.168.100.1 or 168.254.0.10 doesn't work even from within the console session. FOr us when we launched xsconsole  , it doesnt show any Mangement VM as well In our case factory reset was done for the Netscaler and that did resolve the issue. Make sure you check the  svm.conf located in cd /flash/mpsconfig It may happen that IP/Subnet configuration is not default Some additional info:  http://support.citrix.com/article/CTX130496 Hope this helps

XenServer 6.2 does not show nvidia kernel module after installing nVIDIA vGPU Drivers Dell R720

While Trying to setup Dell R720 with NVIDIA Grid K2  for XenServer 6.2 SP1 It may happen that after you install the nvidia driver and reboot the server , the module for nvidia is not recognized . To verify the install after reboot you may run the following command  lsmod | grep nvidia If it does not find any module then we may have to disable one setting in System BIOS for Dell R720 server. This is the setting you need to disable. (Memory Mapped I/O above 4GB) You can find it Under > System BIOS > Integrated Devices > After the server come back online , you can run the following command to verify the module was loaded fine lsmod | grep nvidia The output should be something like nvidia               9626462  26 i2c_core               20294  1 nvidia Verify that the NVIDIA kernel driver can successfully communicate with the GRID physical GPUs in your system by runni...

XenServer 6.2 upgrade SP1 not applicable issue

It may happen that you are unable to update to  SP1 for XenServer 6.2 either using CLI or XenCenter. It appears as if the update is not applicable , even though you know it is. XenServer build number: 70446c XenServer Version: 6.2 From the image you can see that after choosing the update my server shows grayed out as if the update is not applicable. In our case the issue was ,we had not assigned any license server to the XenServer. Once we assigned the license it worked and we were able to upgrade successfully. Hope this Helps.