Cisco Ethernet switch Operations Instructions download pdf (Page 59)

Chapter 5. Cisco Systems IGESM management and user orientation 45

advanced way, by attaching it to a terminal server that is connected to an IP network (for the

purposes of remote management through the

service port on the Cisco Systems IGESM).

See “Possible issues with Hyperterm when using the console port” on page 237 to ensure

successfully utilizing this connection.

Consequences of configuring for a particular management path

Configuring for the use of a specific path as previously noted requires conscious choices that

can affect the availability of the other paths.

For example, configuring for in-band access (path 3 or 4 as previously described) precludes

the use of paths 1A and 2. Conversely, configuring specifically for the use of path 1A or path 2

precludes the use of path 3 or 4.

Path 1B and path 5 are fairly isolated from all of these choices and are not affected by the

configuration choices that are necessary for selecting an out-of-band path (paths 1 and 2) or

in-band path (paths 3 and 4).

Section 5.3, “In-depth management path discussions” on page 55 goes into great detail about

selecting and administering a desired management path for the IGESM.

One final comment: It might appear that if you configure the Management Module and the

Cisco Systems IGESM for in-band management and set the internal Ethernet interface of the

Management Module to the IP subnet being used by the Cisco Systems IGESM, that you

could actually manage the Management Module though the Cisco Systems IGESMs. This is

not the case. The Cisco Systems IGESM has certain hard-coded filters that prevent any traffic

that enters any of the upstream ports (g0/17 -20) from exiting out the Management Module

facing ports (g0/15 - 16), and vice-versa. (This also prevents any unexpected spanning-tree

loops.) The only way to manage the Management Module is through the external Ethernet

interface of the Management Module.

5.2.4 Cisco Cluster Management Suite

The Cisco Cluster Management Suite (CMS), which is available on 12.1(14) versions of IOS

for the IGESM, is Web-based network management software embedded in the BladeCenter

switch designed for small to mid-size enterprises and branch office networks. The software

can reduce the time it takes to deploy and configure multiple switches by simplifying repetitive

and time-consuming network management tasks and providing monitoring and

troubleshooting tools.

Cisco CMS Software is embedded in the BladeCenter Cisco Switch (running a 12.1(14)

version of IOS) and can manage a mix of Cisco switches in a single GUI screen. Through

Cisco Switch Clustering technology, users access Cisco CMS with any standard Web browser

to manage up to 16 of these switches at once, regardless of their physical proximity.

More information can be found at:

http://www.cisco.com/en/US/products/hw/switches/ps628/products_data_sheet09186a00800913ce.h

tml

What Cisco CMS software is not

The word Cluster in Cluster Management Suite is sometimes misconstrued to mean

something other than what it is. In this case, the term represents clustering switches together

on a single GUI screen solely for their management.

It is not involved with clustering servers

or clustering switches for high availability of data paths; it is simply a tool to manage

switches.

1 ... 58 59 60 ... 266

Comments to this Manuals

No comments

Cisco Ethernet switch Operations Instructions Page 59

Comments to this Manuals

Related products and manuals for Networking Cisco Ethernet switch