Filter
Top Products
Appendix A: Specifications
297
KX II-to-KX II Paragon CIM Guidelines
The following system configuration guidelines should be followed when
you are using Paragon CIMs in a KX II-to-KX II configuration:
Concurrent Access
Both KX II KVM switches should be configured with the same policy for
concurrent access to targets - both PC-Share or both Private.
If Private access to targets is required, both KVM switches must be
configured accordingly:
From Security > Security Settings > Encryption & Share, set PC
Share Mode to ‘Private’
This guarantees that concurrent access to targets is prohibited, for all
targets by all user groups.
The KX II allows for more granular control of concurrent access to
targets on a per user group basis. This is done by setting the user
group’s PC Share permissions. However, this is only enforced within
the boundary of a KX II. User Group PC Share permissions must not
be relied on if Privacy must be guaranteed when using the
P2CIM-APS2DUAL or P2CIM-AUSBDUAL with the KX II.
CIM Name Updates
The P2CIM-APS2 and P2CIM-AUSB names are stored within the CIM’s
memory. There are two memory locations provided to accommodate
the Paragon naming convention (12 characters) and the KX II naming
convention (32 characters).
When first connected to a KX II, the Paragon name will be retrieved from
memory and written into the CIM memory location used by KX II.
Subsequent queries for the CIM name or updates to the CIM name from
the KX II will be made to the memory location used by the KX II.
Updates will not be made by the KX II to the memory location used by
Paragon II.
When the CIM name is updated by one KX II, the other KX II will detect
and retrieve the updated name on the next attempt to connect to that
target. Until that time, the name will not be updated on the other KX II.
Port Status and Availability
The port status, displayed on the KX II Port Access page as either Up or
Down, is updated to show whether the CIM is powered up and
connected to the KX II port.
The port availability, as displayed on the KX II Port Access page as Idle,
Busy or Connected, is only updated to reflect activity on a target that has
been initiated from that same KX II.