www.enomalism.com
Hopefully it works as advertised. Looks like it has some features sorely missing from the opensource, management of multiple Xen Servers.
The interesting points:
# Create a cloud of abstracted, highly scalable, and managed compute infrastructure capable of hosting end-customer applications and billed by consumption.
# Simple easy to use web based user interface
# Automagically load balance and and monitor operations using a RESTFul API.
# VM Agnostic, migrate to and from various virtual environments including KVM/Qemu, Amazon EC2 and Xen. (OpenVZ, VirtualBox and VMware coming soon)
# Fully Automated platform with easy setup rules for a completely autonomous and self healing virtual environment
Those alone make it worth while. It depends on mysql for its data storage. I might be trying this out in the lab. When I do, I'll post back.
Since Xen is at least where VMWare Server/ESX is, it is interesting that enomalism might give at least a set of the features available in the ESX/virtual infrastructure product. The main weakness of Xen is managing a pool of Xen servers, and if enomalism does what it advertises, it is a huge step forward.
Sunday, April 20, 2008
Thursday, April 17, 2008
F5 advanced troubleshooting
Say you have a version 9.x F5 Bigip. Nice loadbalancer, does some cool stuff. You add some new config and suddenly you have what looks like a layer 2 problem. So you console the box, and run top and the CPU (and maybe RAM) is pegged. Something called tmm is pegging the box.
TMM is a daemon that does most of the traffic management on F5. It is written by F5 and is opaque... except for:
tmstat
/usr/bin/tmstat from F5 gives you some output about what tmm is doing. So you can kind of figure out where things are going wrong, while you are dialing support.
Output looks vaguely top like:
NAME
CPU: 0% busy 1% idle 99% sleep Thu Apr 17 13:59:00 2008
Memory Allocated New Flow Old Flow Poll
21,081,060 / 1,807,745,024 99,851 25,284 1,228,703 Cycles
[ . : . | . : . ] 1 20 2,035 Total
vnic
Tc4,240b rx Cryplinkps 21,664b txass 27 Timers
[ . : . | . : . ] i8254x:00 (t[ . : . | . : . ]otal) 0 Stats
23,832b rx 1,000 linksa 4,112b txeudo
[ . : . | . : . ]ects 0 fu[ . : . | . : . ]tropy Virtual Class
Wa0b rx 0 linkecord 0b txcure 10,867,070 (total)
[ . : . | . : . ] 0 ci[ . : . | . : . ] 10,485,780 mco db
0 De0b rx 0 linkunseen) 0b tx 168,855 ssl
[ . : . | . : . ] [ . : . | . : . ] 143,727 tcl
0b rx 0 link 0b tx 68,708 (unseen)
[ . : . | . : . ] [ . : . | . : . ]
0b rx 0 link 0b tx Umem Class
[ . : . | . : . ] [ . : . | . : . ] 854 (total)
0b rx 0 link 0b tx 513 xfrag
[ . : . | . : . ] [ . : . | . : . ] 127 connflow
0b rx 0 link 0b tx 117 listener
[ . : . | . : . ] [ . : . | . : . ] 19 poolmbr
0b rx 0 link 0b tx 78 (unseen)
TMM is a daemon that does most of the traffic management on F5. It is written by F5 and is opaque... except for:
tmstat
/usr/bin/tmstat from F5 gives you some output about what tmm is doing. So you can kind of figure out where things are going wrong, while you are dialing support.
Output looks vaguely top like:
NAME
CPU: 0% busy 1% idle 99% sleep Thu Apr 17 13:59:00 2008
Memory Allocated New Flow Old Flow Poll
21,081,060 / 1,807,745,024 99,851 25,284 1,228,703 Cycles
[ . : . | . : . ] 1 20 2,035 Total
vnic
Tc4,240b rx Cryplinkps 21,664b txass 27 Timers
[ . : . | . : . ] i8254x:00 (t[ . : . | . : . ]otal) 0 Stats
23,832b rx 1,000 linksa 4,112b txeudo
[ . : . | . : . ]ects 0 fu[ . : . | . : . ]tropy Virtual Class
Wa0b rx 0 linkecord 0b txcure 10,867,070 (total)
[ . : . | . : . ] 0 ci[ . : . | . : . ] 10,485,780 mco db
0 De0b rx 0 linkunseen) 0b tx 168,855 ssl
[ . : . | . : . ] [ . : . | . : . ] 143,727 tcl
0b rx 0 link 0b tx 68,708 (unseen)
[ . : . | . : . ] [ . : . | . : . ]
0b rx 0 link 0b tx Umem Class
[ . : . | . : . ] [ . : . | . : . ] 854 (total)
0b rx 0 link 0b tx 513 xfrag
[ . : . | . : . ] [ . : . | . : . ] 127 connflow
0b rx 0 link 0b tx 117 listener
[ . : . | . : . ] [ . : . | . : . ] 19 poolmbr
0b rx 0 link 0b tx 78 (unseen)
Subscribe to:
Posts (Atom)
Posts
