Filter
Top Products
Appendix A: Specifications
278
If a connection to the target is in place from the other KSX 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 KSX II.
Until that time, the availability is not be updated on the other KSX 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 KSX II. When the target is
connected to two managed KSX 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 KSX II.
If the KSX 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 KSX II. The corresponding
port name of the other KSX II will not be updated in CC-SG until a
connection is attempted to the target port via the other KSX II‟s oob-kvm
interface.
KSX II to Paragon II Guidelines
The P2CIM-APS2DUAL or P2CIM-AUSBDUAL can be connected to a
KSX II and Paragon II.
Concurrent Access
Both the KSX II and Paragon II must be configured with the same policy
for concurrent access to targets.
Paragon II
operation
mode
Mode description
Supported?
Private
A server or other device
on a specific channel
port can be accessed
exclusively by only one
user at a time.
Supported.
Both Paragon II and the KSX
II must be set to Private. The
Private setting is applied on
to KSX II device, not per
user group.
The Paragon II uses Red to
indicate „busy‟ or Green to