58 Cisco Systems Intelligent Gigabit Ethernet Switch Module
As noted, an important aspect of these two network-based management paths is that the
selection of which to use is an
either/or proposition. It is necessary to configure specifically to
manage the IGESM via the Management Modules uplink (as shown in scenarios 1, 2, and
possibly 7) or its own uplinks (as demonstrated in scenarios 3 and 4). Attempting to configure
IGESM management for both paths at the same time usually creates intermittent connectivity
issues when attempting to connect to the IGESM. Scenarios 5 and 6 show examples of
configurations that incorrectly enable and configure for both paths simultaneously.
With that said, the first and perhaps simplest approach for managing the IGESM is to use the
Management Module’s uplink port to manage the IGESM (paths 1 and 2 in Figure 5-40 on
page 57). This connectivity is demonstrated in scenarios 1, 2, and 7 in this section and is also
discussed in more detail below. Because it is simpler to deploy,
using the Management
Module’s uplink to manage the IGESM is preferred
over managing the IGESM via its own
uplinks, with both scenarios 1 and 2 being recommended equally based on the customer’s
requirements.
As already noted, the second approach is to manage the IGESM via its own external uplink
connections, ports G0/17 - 20 (paths 3 and 4 in Figure 5-40 on page 57). This connectivity is
demonstrated in scenarios 3 through 6, and discussed in more detail below.
It is important to note that although scenarios 3 through 6 all show attempts to manage the
IGESM via its own uplink ports, only scenarios 3 and 4 are recommended when using this
path. Scenario 3 is the recommended choice when using IGESM uplink management, but
scenario 4 is still considered a viable option.
Scenarios 5 and 6 are provided in this section only to show possible problems that could arise
with certain designs when using the IGESM uplinks to manage the IGESM, and thus are not
recommended solutions.
In summary, the selection process involves choosing the desired management path and
configuring it appropriately to ensure correct operation. As already noted, using the
Management Module uplink to manage the IGESM (scenarios 1 and 2) is preferred over
using the IGESM uplinks to manage the IGESM (scenarios 3 and 4). However, scenarios 3
and 4 are certainly viable options for those users requiring true in-band management.
The rules for configuring for management over the Management Module’s uplink are listed in
5.3.4, “Considerations: Using the Management Module uplink to manage the IGESM” on
page 59.
The rules for configuring for management over the IGESM’s uplinks are found in 5.3.5,
“Considerations: Using the IGESM uplinks to manage the IGESM” on page 61 below.
VLAN Best Practice
Closely related to the various other recommendations in this section are certain best
practices for VLAN usage and isolation.
There are many possible approaches to VLAN utilization that may work (such as everything
on a single VLAN network), but are they good designs? Do they account for robust security,
predictable traffic flows, and high availability? With that in mind, several items should always
be remembered when designing secure and robust networks—all designs, not just those
involving the IGESM:
Normally, avoid the use of VLAN 1 for carrying either management or data traffic.
Note: Descriptions of these scenarios begin on page 64.
Comments to this Manuals