Dominion Kx Ii To Paragon Ii Guidelines - Raritan Dominion KX II User Manual

If a connection to the target is in place from the other Dominion KX II, the
availability is checked when a connection is attempted. Access is denied
or allowed consistent with the PC-Share policy in place for the Dominion
KX II. Until that time, the availability is not be updated on the other
Dominion KX II.
If access is denied because the target is busy, a notification is displayed.
Working from CC-SG
Operations initiated from CC-SG are based on the Status, Availability
and CIM name reported by the managed Dominion KX II. When the
target is connected to two managed Dominion KX IIs and the devices are
added to CC-SG, two nodes will be created. Each node will have its own
oob-kvm interface associated with it. Alternatively, a single node can be
configured with an oob-kvm interface from each Dominion KX II.
If the Dominion KX IIs are configured for „Private‟ mode, when a second
connection is attempted the user is notified that they cannot connect and
access is denied.
When a port name change is initiated via the CC-SG Port Profile pane,
the changed name is pushed to the managed Dominion KX II. The
corresponding port name of the other Dominion KX II will not be updated
in CC-SG until a connection is attempted to the target port via the other
Dominion KX II‟s oob-kvm interface.

Dominion KX II to Paragon II Guidelines

The P2CIM-APS2DUAL or P2CIM-AUSBDUAL can be connected to a
Dominion KX II and Paragon II.
Concurrent Access
Both the Dominion KX II and Paragon II must be configured with the
same policy for concurrent access to targets.
Paragon II Mode description
operation
mode
Private A server or other device
on a specific channel
port can be accessed
exclusively by only one
user at a time.
Appendix A: Specifications
Supported?
Supported.
Both Paragon II and the
Dominion KX II must be set
to Private. The Private
setting is applied on to
Dominion KX II device, not
per user group.
The Paragon II uses Red to
indicate „busy‟ or Green to
269