iiQ8 Jobs, News

Server Health Checks - 1 When I’m troubleshooting I like to compartmentalize what I’m looking for.  With that my health checks are set up the same way.  I also believe health checks are quick snapshots of the health of a server.  Sure there are tools that you can use to analyze systems further but in this case we are doing a quick health check.  Not all of these need to be done but some should, you get to decide. CPU   Occasional high CPU spikes are ok as long as you are aware of the process causing this. A server should maintain 80% CPU utilization for an extended period of time.  If it does it may be time to upgrade.  Its a good idea to keep Task Manager open during the duration of your troubleshooting to see trends. Check CPU Usage 1.    Open Task Manager 2.    Check the Processes tab, ensure there are no processes consuming excessive CPU 3.    Check the Performance tab, ensure there are no single CPU’s that have excessive CPU usage Check CPU HW 1.    Open…

Server Health Checks - 3    Check NLBS Configurations 1.    Open up the network properties –> Network Load Balancing, right click & select Properties 2.    On the Cluster Parameters tab, verify that the IP address is configured for the shared NLBS IP and that the subnet mask, domain, and operation mode are configured correctly. 3.    On the Host Parameters tab, make sure each node of the cluster has a unique host identifier. Also verify the IP and subnet mask are configured for the local values. 4.    Also make sure that your switch has a static ARP entry if using multi-cast NLBS. The entry should be that of the virtual MAC of the cluster. To get the virtual MAC of the cluster, you can run the following command : WLBS IP2MAC <virtual IP address> Name Resolution   To healthcheck name resolution, open a command prompt and enter the following ·         nslookup <servername> Verify that the servername is correctly entered in DNS If a reco…