Appendix B: Accessing a Paragon II from the KX III
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 KX III. When the target is connected to two
managed KX IIIs 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 KX III.
If the KX IIIs 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 KX III. The corresponding port name
of the other KX III will not be updated in CC-SG until a connection is attempted
to the target port via the other KX III’s oob-kvm interface.
KX III-to-Paragon II Guidelines
The P2CIM-APS2DUAL or P2CIM-AUSBDUAL can be connected to a KX III and
Paragon II.
Concurrent Access
The KX III and Paragon II must be configured with the same policy for
concurrent access to targets.
Paragon II
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.
Paragon II and the KX III must
be set to Private. The Private
setting is applied on to KX III
device, not per user group.
The Paragon II uses Red to
indicate ‘busy’ or Green to
indicate ‘available’.
PC Share A server or other device on
a specific channel port can
be selected and controlled
by more than one user,
but only one user has
keyboard and mouse
control at any one time.
Supported.
However, PC Share Idle
Timeout, which is configured
on the Paragon II, is not
supported. Both users will
have concurrent keyboard and
mouse control.
The Paragon II uses Green to
indicate ‘available’. This will
also be true if another user is
already accessing the target.