Image: DC design based on VSS

1-      Virtual Switching System (VSS)

• With VSS, the two 6500 will become one.
• This will make both 6500 active in same time, increasing the network bandwidth for all servers and applications.
• This design will eliminate STP.

2-      User Vlans terminated at MSFC

• This will reduce the operational and management task. It will keep the network simple, yet the Data Center will be secured by the FWSM.
• Dynamic routing can be used between the MPLS routing, Core (6500), and future distribution switches that can/should be introduced to follow the standard hierarchy network design.

Image: DC Network Design

From the diagram, we found the following observations.

1- Two MSFC (SUP engine) in each 6500.

• Since all servers are connected two different Chassis (6500), there was no need for redundant (SUP). This is extra redundancy that has no benefit, but only cost of running and purchasing. Redundant SUP are used in scenarios with a single chassis.
• The probability of two SUPs going down is very very low from the manufacturing point of view. It has higher probability in going down in case of fire or loss electricity, then even the Second Chassis with 2 SUPs will go down.

2- Using Static Routing.

• Static routes are not Scalable, not Flexible, not simple, don’t provide high availability. These are major issues that need to be handle when making a new network design. Dynamic routing is a MUST.
• Only when dynamic routing a high available and redundant paths can be utilized.

3- Using Spanning Tree Protocol (STP)

• No new data Center based on STP. All new data center technologies from CISCO, HP, JUNIPER, and BROCADE are going away from STP.
• STP will always have links not utilized. As STP works by “blocking” ports. Hence, all networking components and servers will be running with the half networking capacity.

4- Terminating user Vlans at FWSM (firewall)

• Although this is good for security, it has many issues when it comes to scalability, management, and operation.
• The Server Farm is protected by FWSM, user Vlans are not required to be controlled.
• Referring to point one. The two MSFC (SUP) will not be utilized at all! The 6500 will be used as a giant firewall. If, this is the case. Then there was no requirement to purchase 6500 in first place. Any cheap Cisco 2960 will do the job.

These are the points that i did not like from the design. to tackle this, I would propose my own design that would make better use of the links and hardware in questions.

Once logged into IT360, you can see the dashboard, refer to figure 1. In there The business can be configured (grouped) so all services follow a logical pattern. Practices from ITIL will help to define the group of services, and making them into a logical processes with process owners, who can go and log into IT360 to find the appropriate data that they are monitoring, and operating.

The dashboard will also give the option to see the networks, servers, or applications that are monitored. But i will leave that for some other time. So clicking on the IT360 business (it was the default one). It will take you by default into the Summary tap. as shown in figure 2. The main variables to see are Up-time, recent alarms, application response time, server response time, CPU utilization, link utilization (it is not shown since the network data was not available, misconfiguration?). These readings are very accurate. To this moment of the review, it seems that IT360 provide actual proper data. (our own motoring tool without naming it. wont pull these data, or pull them wrong).

Figure 3 is showing the inventory. This tap will just give a brief idea of health, up-time for all the items that were added. This can be configured to show only the important inventory, or to show everything. when adding routers, it will show the interfaces as well. which is good just to see if everything is up or not. I don’t find the data here interesting, since it is presented in other taps as well.

Business View is how you categorize the Items. As seen from image. It is really good touch, to see which service is down effecting which business. Again, since i haven’t configured this. all shown in one single business.

Last tap, the troubleshoot. will show the status per hour. the period can be changed from hours, to days, to custom. When there is a ticket/alarm clicking on the box will take window to the alarm. This will help to see what was the issue, was it resolved, and who is responsible.

In our next entry, I will go through the network tap. and see all the possible things to monitor, and how to do that. I have not yet done proper review of it. but from the first glance. I really liked it. I think a more deep digging will give me a good insight. but i can tell that it can do everything what our current solution (whatsup) can do. This can be seen in the last article on Manage Enginer IT360.