Managing interactions with other switch features

Managing SSH or Telnet sessions

Switches in a non-stacking configuration support up to six sessions running SSH or Telnet concurrently. However, if stacking is configured, each stacking connection reduces the number of sessions available. For example, five connections into the stack leaves only one session available for SSH or Telnet.

Managing switch-level configuration interactions

In a stack, the Commander functions as a single switch and the Standby and Members function as additional network ports for that switch. Switch configuration is performed in the same manner as for any other switch, as described in these manuals:

HP Switch Software Basic Operation Guide
HP Switch Software Management and Configuration Guide
HP Switch Software Advanced Traffic Management Guide
HP Switch Software Multicast and Routing Guide
HP Switch Software Access Security Guide
HP Switch Software IPv6 Configuration Guide

Managing port-level configuration interactions

For features that are configured on specific switch ports in a stack, the configuration procedures are the same as for stand-alone switches, but the port designations for the ports in the stack are modified. Each port is identified by the stack member ID of its switch, followed by a slash and then the port number as it is shown on the switch. For example, for a switch with stack member ID 3, port 10 on that switch would be identified as port 3/10.

Viewing show interfaces brief output for port 3/10

HP Switch(config)#: show interfaces brief 3/10

 Status and Counters - Port Status

                         | Intrusion                           MDI  Flow Bcast
  Port         Type      | Alert     Enabled Status Mode       Mode Ctrl Limit
  ------------ --------- + --------- ------- ------ ---------- ---- ---- -----
  3/10         100/1000T | No        Yes     Down   1000FDx         off  0

Similarly, CLI commands requiring specific port (interface) numbers on an HP 3800 switch configured for stacking require the modified port designations. For example, to enter the port context for port 10 on stack member 2, type:

HP Switch(config)#: interface 2/10   
HP Switch(eth-2/10)#:_

In the output containing designated port numbers for an HP 3800 switch configured for stacking, the port numbers are likewise listed in the modified format.

Viewing show interfaces config output

HP Switch(config)#: show interfaces config

 Port Settings

  Port   Type      | Enabled Mode         Flow Ctrl MDI
  ------ --------- + ------- ------------ --------- ----
  1/1    100/1000T | Yes     Auto         Disable   Auto
  1/2    100/1000T | Yes     Auto         Disable   Auto
  1/3    100/1000T | Yes     Auto         Disable   Auto
   .
   .
   .
  2/1    100/1000T | Yes     Auto         Disable   Auto
  2/2    100/1000T | Yes     Auto         Disable   Auto
  2/3    100/1000T | Yes     Auto         Disable   Auto
  2/4    100/1000T | Yes     Auto         Disable   Auto
.
.
.

Attempting to enter a CLI command for a port on a stack member without using the modified port number format generates a “Module not present...” message such as the following:

HP Switch(config)#: interface 10Module not present for port or invalid port: 10 HP Switch(config)#:

LACP support

LACP trunking can support up to 144 trunks in a stacking configuration, each with up to eight links (ports) per trunk.

Managing OOBM ports

Each OOBM port of a member is assigned one MAC address from that member's manufacturing allocated range. The OOBM port also can be assigned an IP address (IPv4 /v6/DHCP/Manual/Auto-Config/LinkLocal). The commander's OOBM IP address (called the Global IP address) is used for managing the commander through the OOBM port.

After switchover/failover of control from the Commander to the Standby, the OOBM port IP address of the new Commander is the Global IP address. This change in address causes some undesirable behavior (after failover):

When using DHCP or DHCPv6, the new Commander requests a new lease and typically receives a new network address (IPv4 or IPv6). With OOBM high availability (HA), it will seem as if a new link has come up requesting a network address.
IPV6 link-local or auto-config addresses will change.

Using a static IP address avoids these issues. During failover, it will be as if the IP address is reconfigured. All ARP entries are updated automatically.

For more information on OOBM operation, see the Management and Configuration Guide for your switch.

prev	up	next
Troubleshooting stacking	home	Understanding stacking election