Raritan Computer Home Security System - Manual (Page 367)

Appendix I: FAQs
349
Grouping FAQs
Question Answer
Grouping
Is it possible to put a given
server in more than one
group? Yes. Just as one user can belong to multiple groups,
one device can belong to multiple groups.
For example, a Sun in NYC could be part of Group
Sun: "Ostype = Solaris" and Group New York:
"location = NYC."
What impact to other usage
would be blocked through
the active usage of the
console port, for example,
some UNIX variants not
allowing admin over network
interfaces? A console is generally considered a secure and
reliable access path of last resort. Some UNIX
systems allow root login only on the console. For
security reasons, other systems might prevent multiple
logins, so that if the administrator is logged in on the
console, other access is denied. Finally, from the
console, the administrator can also disable the
network interfaces when/if necessary to block all other
access.
Normal command activity on the console has no
greater impact than the equivalent command run from
any other interface. However, since it is not dependent
upon the network, a system that is too overloaded to
be able to respond to a network login may still support
console login. So, another benefit of console access is
the ability to troubleshoot and diagnose system and
network problems.
How do you recommend
handling the issue of CIMs
being moved/swapped at the
physical level with changes
to the logical database? For
example, what happens if I
physically move a CIM with
target server from one port
to another (either on the
same device or a different
device)? What happens to
the port names? What
happens to the node? What
happens to the interfaces? Each CIM includes a serial number and target system
name. Our systems assume that a CIM remains
connected to its named target when its connection is
moved between switches. This movement is
automatically reflected in the ports and interfaces in
CC-SG; the port name and interface name are
updated to reflect the change. The interface appears
beneath the node that is associated with the port.
However, the node name does not change. You must
rename the node manually by editing the node. This
scenario assumes all ports involved were already
configured. If you physically move the target server
and CIM to a different and unconfigured port, you can
then configure the port in CC-SG, and the node will be
created automatically.