With Mobile use becoming the most dominant means of accessing social media a new way of monetizing FB is needed
Read the Article at HuffingtonPost
Monthly Archives: May 2012
Server Load Balancing is an advanced feature supported by Cisco Switches in the 45XX and 65XX Line of Multi-Layer Switches.
The Feature allows a Virtual IP address to be configured on the switch. This Virtual Ip Address or VIP will be used to represent a cluster of servers on a given network.Most persons will never require a 65XX or even a 45XX series switch in their Lans but we all would like have highly available systems. While they are Hardware and Software Load Balancing solutions it would be great to leverage your existing investment in your cisco switches so here is an idea may be able to support Server Load Balancing on a Cisco 35XX series switch.
Let say We need to load balance two MS Exchange 2010 front end servers. First Configure a loopback adaptor on each Server. The IP address of the loopback adaptors will be our chosen Virtual IP address. so lets say our VIP is 172.16.1.1 both loop back adaptors will be assigned this address.
On Your 3560 create two Static Routes pointing to our VIP via the Physical Addresses of the Servers.
# Locate VIP
ip route 172.16.1.1 255.255.0.0 172.16.1.2 with 172.16.1.2 being the address of one of the exchange servers
ip route 172.16.1.1 255.255.0.0 172.16.1.3 with 172.16.1.3 being the address of the second exchange front End
Configure CEF Destination Load Sharing by issuing the command IP load-sharing per-destinantion. This command shares traffic based on source/destination address pairs. We can use IP SLA to track the
reachability of the physical hosts and assign a tracking object to the static route above.
Note I have yet to use the technique above but it should work in theory.
The I/O and CPU requirements of most malware solutions are a serious impediment to the optimal performance of virtual machines and older physical hosts. In a virtual environment consisting of many virtual machines each executing their own copy of a single malware protection package, the underlying hypervisor utilizes many I/O and CPU cycles that are sourced from each of its guests which are constantly scanning various files and memory pages. The memory, I/O and CPU cycles utilized to process calls generated by the Virtual Machine‘s malware software can be greatly reduced by eliminating the practice of installing malware software within a guest operating system.
A hypervisor Resident program (HRP) can be used to scan VM memory pages some of which are shared via transparent memory sharing (TPS) which essentially is a technique used to allow many virtual machines to share identical memory pages thus reducing the memory requirements of the host machine.
All writes and modification of guest memory pages should be examined by the HRP which should be developed to use signatures stored on shared solid state storage. The signatures required by the HRP will be transferred from central storage to memory as required, if possible all signatures should be memory resident. The HRP should also support Heuristic detection of malware as a means of reducing the amount of signatures needed and thus reducing the storage required for these said signatures.
The caching of memory pages that have already been scanned can be achieved by storing a checksum of each scanned memory page to a protected portion of memory, cached pages should only be re-scanned if the page has been modified. I/O requirements are reduced by eliminating on-access scanning of files being written and read from disk,it is assumed that all malware needs to be executed while stored in main memory