Table Of Contents
CiscoView Device Manager for the Cisco Catalyst 6500 Series Switch Version 1.0
The Next Generation of Device-Embedded Solutions
End-to-End Setup Using a Single Tool
Data Sheet
CiscoView Device Manager for the Cisco Catalyst 6500 Series Switch Version 1.0
CiscoView Device Manager for the Cisco® Catalyst® 6500 Series Switch resides in the switch and manages several Layer 2 and Layer 3 features for a single chassis. A task-based tool, CiscoView Device Manager eases the initial setup and deployment of end-to-end services across modules by offering configuration templates based on recommended practices. It further enhances the user-friendliness of the Cisco Catalyst 6500 Series through graphical representation of the VLAN, and by providing a single launch point for multiple module managers. CiscoView Device Manager is a free application with a small footprint that easily can be downloaded and installed on the supervisor engine Flash memory.
The Next Generation of Device-Embedded Solutions
Managing the Cisco Catalyst 6500 Series Switch requires a high level of command-line interface (CLI) awareness for users to completely control the versatility of all the features and services available. Some typical challenges faced by users include:
•
Support of initial deployment of several services, such as firewalls, content load balancing, and intrusion detection
•
Complete "service deployment" instead of only "module configuration"
•
Visualization of VLAN interconnectivity between services
CiscoView Device Manager for the Cisco Catalyst 6500 Series manages several Layer 2 and Layer 3 features on the Catalyst 6500 Series and helps users accomplish these tasks with ease. CiscoView Device Manager offers the following features:
•
Easy-to-use graphical interface for VLAN visualization, monitoring, and port setup
•
Configuration based on templates and recommended practices to simplify the initial setup of services
•
Comprehensive end-to-end services setup using a single tool
Graphical VLAN Visualization
CiscoView Device Manager makes it easier than was previously possible through the CLI to visualize the Cisco Catalyst 6500 "network-in-a-box."
Figure 1
The Home Page Gives Users a Graphical Snapshot of the Chassis Status
CiscoView Device Manager provides network and security operations personnel with a clear picture of the VLAN connectivity in a chassis. Representing individual modules within a chassis as nodes on a network topology map is useful to highlight security loopholes, such as VLANs being inadvertently configured to bypass firewalls. This view allows users a quick and easy way to troubleshoot such potential security issues with a more appropriate configuration. Port configuration, setup, and VLAN assignments are easy using this graphical interface. Configuration can be accomplished through a series of mouse clicks, significantly reducing the time required to complete the initial setup on the switch.
Initial Setup
CiscoView Device Manager enables users to access Cisco Systems® expertise by facilitating configurations using wizards and dialog boxes.
Figure 2
Configuration Based on Templates and Recommended Practices
Users create configurations by responding to a series of questions in user-friendly wizards and dialog boxes, and CiscoView Device Manager designs the recommended-practice CLI configuration based on those responses. At the end of the process, users view the CLI command syntax created and decide whether to deploy the configurations to the chassis immediately or to save them for future editing.
CiscoView Device Manager includes the following templates for initial configuration:
Firewall Inside—This scenario typically is used in the Internet data center. Placing the Multilayer Switch Feature Card (MSFC) outside the Cisco Catalyst 6500 Series Firewall Services Module (FWSM) makes it possible for the MSFC to perform routing toward the core network. The FWSM provides routing to the border routers and the demilitarized zone (DMZ).
Firewall Inside with Cisco Content Switching Module (CSM)—This scenario typically is used in intranet data centers. Placing the MSFC outside the Cisco Catalyst 6500 Series FWSM in the intranet data center means that the MSFC faces the core. In this design, the default gateway for the servers is either the FWSM or the Cisco CSM.
Firewall Outside—This scenario typically is used in Internet data centers. Placing the Cisco Catalyst 6500 Series FWSM outside the MSFC in the Internet data center allows the MSFC to face the core. In this design, the default gateway for the servers is the FWSM.
Figure 3
Firewall Outside with Cisco CSM Template
Firewall Outside with Cisco CSM—This scenario is usually used in Internet data centers. Placing the Cisco Catalyst 6500 Series FWSM outside the MSFC means that the MSFC performs routing toward the core. The FWSM performs routing toward the border routers and the DMZ.
Figure 4
VPN and Firewall Template
VPN and Firewall—This scenario usually is used to terminate secure connections to remote offices and telecommuters while providing the firewall function to the general public accessing an Internet server farm. The Cisco Catalyst 6500 Series FWSM is used to apply firewall policies to untrusted clients while the Cisco 7600/Catalyst 6500 IPSec VPN Services Module (VPN SM) provides secure access to the internal network.
VPN Outside—This scenario is used when the Cisco 7600/Catalyst 6500 IPSec VPN SM serves as the headend VPN termination platform for either remote access or enterprise customers. The VPN SM and Cisco Catalyst 6500 Series FWSM protect the internal and DMZ networks.
MSFC and Cisco CSM—This scenario configures connectivity between the MSFC and Cisco CSM modules. The Cisco CSM provides load-balancing services for the server farm.
Figure 5
Custom VLAN Creation by" Drag-and-Drop" of Lines Between Modules
A custom setup mode is available that allows additional services to be specified, where VLANs can be created by drag-and-drop of lines between any modules on the topology map. CiscoView Device Manager intelligently detects VLANs being created between modules that should not be directly connected and cautions users against connecting them.
End-to-End Setup Using a Single Tool
Users not familiar with the CLI can create complex end-to-end service configurations using CiscoView Device Manager.
Figure 6
End-to-End Configuration Using GUI Tools
CiscoView Device Manager configures global parameters, such as spanning tree, banners, and other chassis-level features such as setting up connectivity to individual modules. After the configurations are complete, users can launch the embedded managers for each of the modules (such as CiscoView Device Manager for the Secure Sockets Layer [SSL] module, Firewall Device Manager on the firewall module, etc.) for deeper module-specific configuration.
Providing a single launch point for the device managers for each module in a Cisco Catalyst 6500 Series chassis, CiscoView Device Manager makes configuring end-to-end services smooth, reducing error-prone tasks associated with using a CLI.
Table 2 Cisco IOS Software Release Support1
Module Cisco IOS Release Software Release for Services Module Supervisor IA12.1(13)E, 12.1(19)E, 12.1(20)E
-
Supervisor II12.2S(14)Y, 12.1(13)E, 12.1(19)E, 12.1(20)E
Supervisor 72012.2(14)SX1, 12.2(17A)SX1, 12.1(17B)SXA
-
VPN12.2S(14)Y, 12.1(17B)SXA
-
CSM12.1(13)E, 12.1(19)E, 12.1(20)E, 12.2(14)SX1, 12.2(17A)SX1, 12.1(17B)SXA
3.1(4) and higher
Intrusion Detection System Module (IDSM) II12.2S(14)Y, 12.1(19)E, 12.2(14)SX1, 12.2(17A)SX1, 12.1(17B)SXA, 12.1(20)E
4.0, 4.1
FWSM12.2S(14)Y, 12.1(13)E, 12.1(19)E, 12.2(14)SX1, 12.2(17A)SX1, 12.1(17B)SXA, 12.1(20)E
1.1(2), 1.1(3), 1.1(4), 2.2
Network Analysis Module (NAM) (I and II)12.2S(14)Y, 12.1(13)E, 12.1(19)E, 12.2(14)SX1, 12.2(17A)SX1, 12.1(17B)SXA, 12.1(20)E
2.2, 3.1
SSL Service Module (SSLSM)12.1(13)E, 12.1(19)E, 12.2(14)SX1, 12.2(17A)SX1, 12.1(17B)SXA, 12.1(20)E
1.1(1), 1.2(1) and higher
Ethernet and Gigabit Ethernet Cards12.2S(14)Y, 12.1(13)E, 12.1(19)E, 12.2(14)SX1, 12.2(17A)SX1, 12.1(17B)SXA, 12.1(20)E
-
1 CiscoView Device Manager for the Cisco Catalyst 6500 Switch v1.0 Supports Native Mode Deployments Only






