Bugs Baer was right.
The newspaper writer and cartoonist once defined a good neighbor as “a fellow who smiles at you over the back fence but doesn’t climb over it.”
If your Data Centers are like most, they have many neighbors – er, tenants – in them. Some want open access, so they can quickly update applications and hardware. Others want a highly-restricted environment, where changes are few and far between. Still others want operational policies somewhere in between.
How, then, to construct a Data Center so everyone remains good neighbors? That is, meeting everyone’s particular operational needs while ensuring that no tenant activities – or restrictions – ever impact those around them?
Below, I suggest some design considerations when building a multi-tenant Data Center.
What else do you think someone should consider when hosting very different clients in their Data Center?
Tags: cage walls, coc-data-center, data center, datacenterdeconstructed, mult-tenant data center
If you had a team of Data Center experts at your beck and call, what would you ask them?
How to lower your Data Center costs? How to get more performance out of a legacy server environment? Who thought an emergency-power-off button was a good idea for a facility filled with business-critical hardware?
I’m launching this blog series to be a forum to share useful information about Data Centers. Rather than me telling you what I think is important, though, you’re in charge. Submit a question and I’ll locate a Data Center expert to provide the answer you’re looking for. I’ll post the resulting question-and-answer here, for everyone to watch and learn from.
Click below for a brief introduction and instructions on how to submit a question.
A new video will be added each week, so come back regularly for the latest questions and answers.
To see all Data Center Deconstructed posts, go to http://blogs.cisco.com/tag/datacenterdeconstructed/.
Tags: coc-data-center, data center, datacenterdeconstructed
In November 2010, Cisco introduced its own software-based enterprise collaboration platform: Cisco Quad. Underlying this platform at Cisco is the development of a transformed way of working that Cisco calls the Integrated Workforce Experience, or IWE. IWE powered by Cisco Quad extends the power of collaboration to employees by combining a foundation of video and unified communications with personalization and relevancy features, applications, and services on the network and integrating them with business and content management systems.
Integral to the IWE environment are collaborative communities created around job and organizational functions, roles, and topics of interest. Members of a community collaborate to achieve their goals, organize and access informational assets and transactional tools, and promote their interests.
Early adopters of IWE span multiple organizations across Cisco including Cisco’s Central Development Organization, Customer Value Chain Organization, and Finance teams to name a few. All these organizations who span multiple geographies and time zones, are already benefiting from an IWE environment that enhances their virtual collaboration and improves productivity; provide quick, convenient access to technical experts and knowledge sharing companywide; and inspires new ways of conducting the product development process.
The following case studies describe the business benefits that internal Cisco functions are reaping from their early implementations of IWE.
Tags: Cisco Quad, coc-collaboration, collaboration, quad
Like many IT organizations, Cisco IT provides help-desk support only for Microsoft Windows-based PCs. Yet many Cisco employees choose to use a Mac, even if it means they are on their own for resolving problems, obtaining repairs, installing software upgrades, and similar support tasks. By the end of fiscal year 2009, Cisco had over 8,000 Mac users, and by fiscal 2010, over 12,000.
Read More »
Tags: Apple, coc-collaboration, communities, macs, support, wikis
In my last blog I described how Cisco employees have adopted teleworking, using either a software VPN client, or a hardware VPN solution called Cisco Virtual Office (CVO). Cisco employees who telework on a regular basis prefer CVO over software VPN because the connection tends to be more stable and Cisco Virtual Office saves them the trouble of constantly logging back in. In addition, CVO provides QoS (quality of service) for voice and video which is critical to a high quality audio and video experience.
The preference for CVO is reflected in the fact that our employees who use the software VPN client work a little over 1 day per week from home while the 21,000 employees who use CVO report that they telework an average 2.5 days per week.
Read More »
Tags: cisco on cisco, Cisco Virtual Office, coc-borderless-networks, CVO, ISR, QoS