Kenon Ewing

Since the testing and implementation of the CSM load balancer module, we have preparing to migrate the webmail servers behind the load balancer. This entailed getting IP addresses on the CSM server vlan for the webmail servers, and one IP address on the CSM client vlan. Configuring the serverfarm for the webmail servers on the CSM, and changing the webmail DNS name to the client vlan IP.

I also generated a report on the servers that I am the primary caretaker for and their current monitoring status. This is the first step in a process to ensure all of our services  are being monitored

In the Virtual Infrastructure, arrangements had been made to migrate 5 law virtual machines and 23 owen virtual machines to be hosted in our virtual infrastructure. This took careful preparation from network configurations to allocated storage. We successfully migrated all virtual machines in question in less a month.

I also began assiting with the web server migration project. I was responsible for copying sites from the old environment to the new environment, testing and working with users to get full functionality of their websites.

The NDE server that serves core network topology information to both the Network Desidn team as well as the general community, had a head crash on a hard drive. In order to bring the system up to current ITS standards, we decided that the Applications Hosting group would take over the maintenance of the physical hardware and the operating system for the Network Design team. We rebuilt this server on a virtual machine in our virtual infrastructure

CSM

The CSM load balancing project picked up pace this month, since testing was completed last month. I had to get all the network configurations for the Virtual Infrastructure, and have the network team configure all the ports needed on the correct VLANS. This entailed moving 24 cat6 copper connections from the high density switch in the redundant data center, to the new 6513 where the CSM resides, and having the network team pre-configure the ports on the 6513. Then, I had to reconfigure the virtual switch inside of the ESX server’s configuration to virtually add the trunks that were physically added in the re-configuration from the network team. I then documented the process / procedure to add a service to the CSM load balanced and used it to configure a serverfarm to house the webmail environment. I also noticed that there was no firewall protection around the CSM private VLACN or CSM server VLAN, which would have been a security implication. I had the firewall expert change the behavior of the firewall to block any inbound request to the private VLAN.

Changes

I assisted the amcom rollout, by generating pub/priv keys for jprod1.its and jprod2.its and reconfiguring the start up script for the apps2 instance to load the key on start up. This allows a secure transmission of files from MIS to jprod servers to process data, then pass it along to amcom.

Organizational Consolidation

Started the consolidation of the Owen and law schools to our virtual infrastructure. In order, to get this to occur, I had to get then Owen / Law’s VLAN put on the physical trunks for the virtual infrastructure, and reconfigure our ESX hosts to add the VLAN to the virtual switch. Once this was in place, we could hose some of the owen virtual machines on our hardware, so they put their ticketing system virtual machine configurations on a USB drive and i added that to out ESX hosts.
Streaming Services

After the disk failure on the streaming server, I was approached about providing a third media server to stream content in preparation for graduation. I successfully deployed the streaming media server into a Virtual machine and it is fully functional and on stand by for graduation.
Virtual Infrastrucutre

Getting prepared to move the management console for our virtual infrastrucutre and the service console of out esx servers to a non-routable private network. I got the admin switch in place and configured for the admin network. Successfully moved two of the esx hosts to the private network when i realized a small routing issue that has postponed the move. We should get this accomplished next week.