Appendix B: Accessing a Paragon II from the KX III130If a connection to the target is in place from the other KX III, theavailability is checked when a connection is attempted. Access is deniedor allowed consistent with the PC-Share policy in place for the KX III.Until that time, the availability is not be updated on the other KX III.If access is denied because the target is busy, a notification is displayed.Working from CC-SGOperations initiated from CC-SG are based on the Status, Availabilityand CIM name reported by the managed KX III. When the target isconnected 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 interfaceassociated with it. Alternatively, a single node can be configured with anoob-kvm interface from each KX III.If the KX IIIs are configured for ‘Private’ mode, when a secondconnection is attempted the user is notified that they cannot connect andaccess 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 correspondingport name of the other KX III will not be updated in CC-SG until aconnection is attempted to the target port via the other KX III’s oob-kvminterface.KX III-to-Paragon II GuidelinesThe P2CIM-APS2DUAL or P2CIM-AUSBDUAL can be connected to aKX III and Paragon II.Concurrent AccessThe KX III and Paragon II must be configured with the same policy forconcurrent access to targets.Paragon IIoperationmodeMode description Supported?Private A server or other deviceon a specific channelport can be accessedexclusively by only oneuser at a time.Supported.Paragon II and the KX IIImust be set to Private. ThePrivate setting is applied onto KX III device, not per usergroup.The Paragon II uses Red toindicate ‘busy’ or Green toindicate ‘available’.PC Share A server or other deviceon a specific channelSupported.However, PC Share Idle
