lojack - All I will share is this (edited for your privacy):
eth0 Link encap:Ethernet HWaddr 30:85:a9:07:**:**
inet6 addr: fe80::3285:a9ff:****:****/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:419 errors:0 dropped:0 overruns:0 frame:0
TX packets:256 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:77048 (77.0 KB) TX bytes:37129 (37.1 KB)
Also:
Mr ****,
I'd love to have a chat with you sometime about the state of the VUIT merger. I recently moved on from ITS to a position with Yahoo!/Tumblr and really hated to make the move but with the state of the environment there I, like many others, felt I had no choice. The road ahead of you is going to be very rocky as there is a very real animosity between the two departments. I fully agree with you that this has been a long time coming and definitely needs to be done and there will be many issues. There is one that I hold dear and I am bringing it to your attention so that a grievous disaster might be averted.
I was a Network Operations Analyst(noc monkey) for the university side and had the opportunity to help out on the openDCIM project that was started by a former manager of the University data center, Scott M******. OpenDCIM has become one of the leading datacenter information management tools in the industry today and I honestly believe it would be a disaster to lose V********* as a consumer. OpenDCIM started out with the goal of tracking the assets in the University data center and has evolved into a fantastic management tool for power tracking and planning as well as network connection management. We've currently got confirmed installs in more than 30 countries and are actively working on new features regularly. Before I left there were rumblings as to all homegrown software packages were going to have off the shelf solutions found and used as replacements. I hope that when it comes to the datacenters openDCIM will not be lumped into the homegrown solutions pile and be evaluated fairly. openDCIM has been vital to the university to allow for agile transitions in the datacenter layout and much of what we have done the last 5 years would not have been possible without it.
I understand that there is some hesitation on where to get support and how much it will cost to support it. There isn't an easy answer but the most common is it will cost you the time of some of your unix staff to maintain the existing mysql servers as they do now and occasionally apply an update when we release them. The updates are purely optional but we have been trying to add new features with each release. I personally am willing to donate my time to support V******** on any critical issues that it might have, but if you need a line item for support I charge $50/hr consulting time. The data is documented and open to any other custom reporting needs that people could possibly want and there is no charge per datacenter. With our recent additions to allow zoning and containers it is possible to have multiple datacenters in a single install. We are looking to release 3.2 in the coming weeks which will add in realistic device views for the cabinets. This feature as trivial as it seems is one that many people have asked for and sets us apart from the many commercial products that cost tens of thousands of dollars.
I'd love to talk to you about the mass exodus of people you have surely noticed from the IT group but I am afraid there isn't much you can do to fix that situation immediately. I wish I could have had this chat prior to leaving N******** but since I worked overnights I wasn't ever able to attend your round tables or any of the all hands meetings.
Sincerely,