Special Coverage Series

Network Computing

Special Coverage Series

Commentary


Introducing the InteropNet NOC Team

InteropNet provides the IT infrastructure for Interop conference attendees and exhibitors. Here are some of the people who make it happen.

InteropNet provides the IT infrastructure and network connectivity to attendees and exhibitors of the Interop conferences. While InteropNet is about technology, the most important component of any network is the people who design, operate and maintain it. Without good people, the best technologies are just an incoherent set of building blocks. The folks that come together to build the InteropNet are, to me, the difference between success and failure.

The organizational structure of the InteropNet team is what I call a democratic dictatorship; input is welcome, but there are times when one person must make final decisions and take responsibility.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

The structure is relatively flat by design. We have a Leader, Team Leads and then the working teams that include the Sponsor Vendors and Volunteer Team Members (ITMs). The goal of the team is to build something together while being willing to teach and learn. It is a place where competitors in the open market set aside their egos and work toward a common goal.

The Team Leads ensure that InteropNet stays on track. There are eight Team Lead positions across a variety of IT disciplines. These roles are filled by volunteers who offer up their time and expertise in return for the opportunity to learn from different vendors and develop knowledge of new concepts to take back to their daily roles. The Team Leads play major role in fine tuning the design and also in the implementation and operation of InteropNet.

Most of the Team Leads started InteropNet life as a team member, terminating cables, troubleshooting booth connections, helping exhibitors and supporting their teammates. They now operate in high places within their own organizations and the networking industry in general--not because they are involved in the InteropNet (although I suspect that has something to do with it), but because they contribute, learn and teach.

I want to recognize the Team Leads who are building InteropNet for Las Vegas 2013.

Brandon Ross: Logical Network Utility Force

The Logical Team Lead is responsible for managing and working with the switching and routing vendors to ensure a stable, reliable network at the logical level. Duties include internal and external routing, Openflow and Fabric-based networking, VLAN assignments and some IP Addressing.

Mark Sullivan: Infrastructure Ascent Technical Group

The Infrastructure Team Lead is responsible for the overall planning, installation, troubleshooting, and operation of the network cable plant. The key areas of focus include deployment and connectivity of the fiber backbone, interconnect links and copper drops; deployment and connectivity of the fiber backbone, interconnect links and copper drops;

The Infrastructure Teal Lead also provides connectivity for meeting rooms, conference sessions, hallway booths, attendee connecting points, and any external facilities. Other duties include the design, documentation and installation of cabling, and the distribution/return of networking equipment.

Nicola Foggi: Systems and Management/Monitoring DePaul University

This Lead is responsible for the integration and operation of application services within the InteropNet. Services include DNS, RADIUS authentication and VoIP services. Requirements for the role include an understanding of the core network and the design of integrated systems, as well as the ability to manage multiple tasks. This Lead also provisions traffic monitoring and management systems.

Andrew Hoyos: Wireless Hoyos Consulting

The Wireless Lead is responsible for the integration and operation of all wireless related systems and services within the InteropNet. This includes attendee secured and unsecured access, secured NOC access, secured show management access, an opt-in BYOD demonstration and the creation of wireless policies.

Gilly Canty-Ross: Troubleshooting Subspace Communications

The Troubleshooting Lead is responsible for coordinating all troubleshooting efforts of the internal network, but is not responsible for equipment configuration, or external troubleshooting and connectivity.

This Lead works with the network team to ensure that all routing, filters, redundancies and management functions are in place within the network. The lead establishes coordinates, and leads the individual troubleshooting efforts of the volunteer team. The lead also works with staff and other leads to ensure that adequate education and leadership is provided for the volunteer team. Finally, this position works closely with Infrastructure, Wireless and Monitoring Leads to help designate resources to the appropriate areas.

Bill (WEJ) Jensen: Generalist Department of IT, University of Wisconsin, Madison

This lead bridges multiple vendors to pro-actively prevent interoperation issues. Requirements for the role include an understanding of the core network and the design of integrated systems, as well as the ability to manage multiple tasks. The key areas of focus of this lead are to be knowledgeable and capable enough to lead or assist in any of the areas of the network. This Lead will also help guide teams that are having difficulties or are not yet completely integrated with the overall project.

Brian Chee: Education University of Hawaii, ANCL

The Education Lead is a new role for 2013. Education is an important focus within the InteropNet, both through our attendee-facing program and our volunteer program. This role has been created to develop our internal team education program. A key value add to volunteers (Team Leads and ITMs) by using Team Leads and Sponsor engineers to coach and mentor the ITMs in a semi-formal setting.

Fr. Robert Ballecer, SJ: Messaging TWiT

As most business people know, engineers are great at getting the job done, but lousy at letting people know how things are being done or that the job is complete. Therefore, this Team Lead has a very simple brief: Get the message out about the InteropNet and its people in any way possible.

If you'd like to see the InteropNet for yourself, tours of the NOC are available Wednesday, May 8, and Thursday, May 9, on the expo floor at 11:00, 1:00 and 3:00 p.m. at the Las Vegas show. Team leads and volunteers host the tours.

Glenn Evans, founder and CEO of Acrux Consulting, is the lead network engineer for the InteropNet project. He brings more than 25 years of systems and networking experience in both management and technical operations, including 15 years in the event space.



Related Reading



Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | Please read our commenting policy.
 

Editor's Choice

Research: 2014 State of Server Technology

Research: 2014 State of Server Technology

Buying power and influence are rapidly shifting to service providers. Where does that leave enterprise IT? Not at the cutting edge, thatís for sure: Only 19% are increasing both the number and capability of servers, budgets are level or down for 60% and just 12% are using new micro technology.
Get full survey results now! »

Vendor Turf Wars

Vendor Turf Wars

The enterprise tech market used to be an orderly place, where vendors had clearly defined markets. No more. Driven both by increasing complexity and Wall Street demands for growth, big vendors are duking it out for primacy -- and refusing to work together for IT's benefit. Must we now pick a side, or is neutrality an option?
Get the Digital Issue »

WEBCAST: Software Defined Networking (SDN) First Steps

WEBCAST: Software Defined Networking (SDN) First Steps


Software defined networking encompasses several emerging technologies that bring programmable interfaces to data center networks and promise to make networks more observable and automated, as well as better suited to the specific needs of large virtualized data centers. Attend this webcast to learn the overall concept of SDN and its benefits, describe the different conceptual approaches to SDN, and examine the various technologies, both proprietary and open source, that are emerging.
Register Today »

Related Content

From Our Sponsor

How Data Center Infrastructure Management Software Improves Planning and Cuts Operational Cost

How Data Center Infrastructure Management Software Improves Planning and Cuts Operational Cost

Business executives are challenging their IT staffs to convert data centers from cost centers into producers of business value. Data centers can make a significant impact to the bottom line by enabling the business to respond more quickly to market demands. This paper demonstrates, through a series of examples, how data center infrastructure management software tools can simplify operational processes, cut costs, and speed up information delivery.

Impact of Hot and Cold Aisle Containment on Data Center Temperature and Efficiency

Impact of Hot and Cold Aisle Containment on Data Center Temperature and Efficiency

Both hot-air and cold-air containment can improve the predictability and efficiency of traditional data center cooling systems. While both approaches minimize the mixing of hot and cold air, there are practical differences in implementation and operation that have significant consequences on work environment conditions, PUE, and economizer mode hours. The choice of hot-aisle containment over cold-aisle containment can save 43% in annual cooling system energy cost, corresponding to a 15% reduction in annualized PUE. This paper examines both methodologies and highlights the reasons why hot-aisle containment emerges as the preferred best practice for new data centers.

Monitoring Physical Threats in the Data Center

Monitoring Physical Threats in the Data Center

Traditional methodologies for monitoring the data center environment are no longer sufficient. With technologies such as blade servers driving up cooling demands and regulations such as Sarbanes-Oxley driving up data security requirements, the physical environment in the data center must be watched more closely. While well understood protocols exist for monitoring physical devices such as UPS systems, computer room air conditioners, and fire suppression systems, there is a class of distributed monitoring points that is often ignored. This paper describes this class of threats, suggests approaches to deploying monitoring devices, and provides best practices in leveraging the collected data to reduce downtime.

Cooling Strategies for Ultra-High Density Racks and Blade Servers

Cooling Strategies for Ultra-High Density Racks and Blade Servers

Rack power of 10 kW per rack or more can result from the deployment of high density information technology equipment such as blade servers. This creates difficult cooling challenges in a data center environment where the industry average rack power consumption is under 2 kW. Five strategies for deploying ultra-high power racks are described, covering practical solutions for both new and existing data centers.

Power and Cooling Capacity Management for Data Centers

Power and Cooling Capacity Management for Data Centers

High density IT equipment stresses the power density capability of modern data centers. Installation and unmanaged proliferation of this equipment can lead to unexpected problems with power and cooling infrastructure including overheating, overloads, and loss of redundancy. The ability to measure and predict power and cooling capability at the rack enclosure level is required to ensure predictable performance and optimize use of the physical infrastructure resource. This paper describes the principles for achieving power and cooling capacity management.