Certificates for IPv6 Enabled KX II Devices

To prevent certificate errors with IPv6-enabled Raritan devices managed by CC-SG, and added to CC-SG with IP address, ensure that the CN in the certificate has the leading zero suppressed value enclosed in [].

When interacting with a CC-SG managed Raritan device, CC-SG provides a "leading zero suppressed host" in the URL for jar downloads. This means that certs should have leading zero suppressed value enclosed in [] as the CN.

You could also use the hostname for the KX II device as the CN, or use Subject Alternative Names (SAN) in the Certificate Signing Request (CSR), get that CSR signed by an external Certificate Authority, and upload that certificate to the Raritan device.

[fd00:c:d:2400:0:2:3:4]

[fd00:c:d:2400::2:3:4]

[fd00:000c:000d:2400:0000:0002:0003:0004]

See Also

Devices, Device Groups, and Ports

Viewing Devices

Searching for Devices

Discovering and Adding IPv6 Network Devices

Discovering Devices

Adding a Device

Editing a Device

Change the HTTP and HTTPS Ports for a Device

Editing a PowerStrip Device or a Dominion PX Device

Adding Notes to a Device Profile

Adding Location and Contacts to a Device Profile

Deleting a Device

Configuring Ports

Editing a Port

Deleting a Port

Configuring a Blade Chassis Device Connected to KX2 or KX3

Restore Blade Servers Ports to Normal KX2/KX3 Ports

Bulk Copying for Device Associations, Location and Contacts

Configuring Analog KVM Switches Connected to KX2 or KX3

Device Group Manager

Adding Devices with CSV File Import

Upgrading a Device

Backing Up a Device Configuration

Restoring Device Configurations

Copying Device Configuration

Restarting a Device

Pinging a Device

Pausing CC-SG's Management of a Device

Resuming Management of a Device

Pause and Resume Management of Devices Using a Scheduled Task

Device Power Manager

Launching a Device's Administrative Page

Disconnecting Users