中国农业发展银行IT自动化运维操作管理平台.pptVIP

* * What customers need to manage this new paradigm – on top of the Remote Terminal, Server Explorer, and Global Shell tools: Be able to see across both the server and network environment. Today, each group has very limited information about the other groups devices. For instance, a network engineer may only know server names by IP addresses. Automated identification of cross-configuration issues. A great example of this is the duplex mismatch issue we spoke about early. What would allow for automated discovery of this issue is a map of how a server and network device is connected, from a layer 2 and 3 perspective. Presenting this information along with duplex settings discovered on the server and network interfaces would really improve troubleshooting and time to repair. The current tools today are very limited to server and network devices. A new integrated server and network management tool would assist in orchestrating change management for these devices. Of course, it would need to take into account how IT organizations would utilize this type of tool as often, these two teams are still very wary of each other. Finally, compliance today isn’t server or network-centric. Regulatory compliance, such as VISA CISP or Sarbanes-Oxley, spans network and server devices. IT organizations need to set corporate policies that affect both and report on these policies. * Opsware is leveraging its deep operational expertise in each of our current products, Server Automation System and Network Automation System, to build just the tool required for integrated server and network management. First, our management network will allow for access to both server and network devices. Access and visibility permissions will be tight and set by the owners of the devices so other groups will only see what the device owners want them to see. The second part of our strategy is to leverage the layer 2 and VLAN information that’s already discovered in the respective systems and map them togeth