CeRedunScope

• Base type Enumeration

Defines the following group redundancy scopes: other(1) The scope is not described by any of the other categories listed below. local(2) All redundancy group members reside on a single managed system and are reachable through a single management IP address. remoteChassis(3) This redundancy group has peer members on physically separate local and remote managed systems with separate management IP addresses. But the local and remote systems can communicate with each other and are contained in the same instance of a supercontainer 'stack' entPhysicalClass, even if they don't physically reside in close proximity. Therefore the members in the separate systems can be represented by a common entPhysicalIndex numbering scheme. An example might be a multi-shelf system where redundant member linecards are located on separate shelves. Each shelf may have a separate management port to allow SNMP control, but the linecards are designated by a common shelf/slot numbering instead of just a slot number. Therefore both members can be configured by communicating with one of the SNMP managed systems even though only one member is physically located on that managed shelf. remoteSystem(4) This redundancy group has peer members on physically separate local and remote managed systems with separate management IP addresses. The local and remote systems have independent entPhysicalIndex numbering. The local and remote members may be tied together by some other means, such as by configuration of an InetAddress for the remote peer member and the requirement to use matching ceRedunGroupTypeIndex and ceRedunGroupIndex values on the local and remote systems. Because of the independent PhysicalIndex numbering, the primary member configuration would need to be done on one managed system and the peer secondary member configuration would need to be done on the remote managed system.