socket swt sing a style s/s

Single Switch Socket Outlet, 250V, 15A, A Style Deep Curved Plate

Catalogue Number: A15/15A
socket swt sing a style s/s
Colour: White Electric
Colour: Per UOM Std.
  • Black 1 PCE
  • White Electric 1 PCE

Specifications

hide show
Product brand
Clipsal
Range of product
Metal Plate
Control type
ON/OFF button
Number of gangs
1 gang
Pin number
3
Number of power socket outlets
1
Actuator
  • switch
  • rocker
    • Mounting position
      horizontal
      Fixing mode
      by screws
      Local signalling
      without light indicator
      Material
      stainless steel
      [Ue] rated operational voltage
      250 V AC
      [In] rated current
      15 A
      Depth
      30 mm
      Length
      115 mm
      Width
      70 mm
      Fixing center
      84 mm
      Standards
    • AS/NZS 3100
    • AS/NZS 3112
    • AS/NZS 3133:approval number S/1
      • Sustainable offer status
        Green Premium product
        EU RoHS Directive
        Compliant
        Mercury free
        Yes
        RoHS exemption information
        Yes
        China RoHS Regulation
        Product out of China RoHS scope. Substance declaration for your information
        Environmental Disclosure
        ENVPEP120506EN
        Circularity Profile
        N/A

        Frequently Asked Questions

        hide show

        What is the part number for the 10A version of A15/15M-WE?

        The part number for the 10A version of  A15/15M is A15M.

        For further information please visit https://the part number for the 10A version of A15/15M-WE


         

        What is the threaded plug to suit clipsal SS15/15

        PDL56P315

        What are the part numbers for a suspension socket with a switch

        Part numbers are SS15 or SS15/15

        In the 600 Series, is the 691/15 available in RED

        Not available, but Clipsal 2015/15 is available in red but it's horizontal.

        What is another option for a 15A version of the PDL 927P ?

        Could use the Clipsal SS15/15 with PDL 56P315

        what tunnel sizes does the L10/35a have ?

         
         
        3 x 9mm diameter to suit 35mm2 and 7 tunnels at 6mm to suit 16mm2
         
         

        Does Clipsal have a Link Bar with at 13 tunnels and 1 x 50mm and 3 x 16mm tunnels?

        Yes the L13/150 will suit those requirements.

        What are the part number for a 15 amp outlet with RCD protection?

        Not available as 1 unit. Would have to use 2015/15 with 2031VRCD30
        For further information , visit links below:-
        https://www.clipsal.com/Trade/search-results?q=2015/15
        https://www.clipsal.com/Trade/search-results?q=2031VRCD30
        User-added image
        User-added image

        AP5610, AP5615, and AP5616 KVM Switch LDAP Implementation Example


        Issue

        I need help setting up LDAP with my AP5610, AP5615, and AP5616 KVM Switch.


        Product Line


        • KVM Switches
          • AP5610
          • AP5615
          • AP5616
        Environment

        • All firmware versions
        • LDAP or LDAPS configured in your environment

        Cause

        This article is provided as an example LDAP set up.


        Resolution

        Refer to the PDF attachment in this knowledge base.

        Shipping weights of the NetBotz 310 Wall & Rack appliances

        Issue:

        Product Shipment Weights for the NetBotz 310 Units

        Product Line:

        NetBotz

        Environment:

        NetBotz 310

        Cause:

        Product information

        Resolution:

        The NetBotz 310 (Wall & Rack have the following shipping weights:

        310 Wall: 6 lbs
        310 Rack: 6 lbs 

        Product Shipment Weights for the NetBotz 320 Units

        Issue:

        Product Shipment Weights for the NetBotz 320 Units

        Product Line:

        NetBotz

        Environment:

        NetBotz 320

        Cause:

        Product information

        Resolution:


        The NetBotz 320 has the following shipping weights:

        320 Wall: 7 lbs
        320 Rack: 7 lbs

        SNMP Version Supported by Netbotz Version 1 Appliances

        Issue:

        SNMP version supported by Version 1 Appliances

        Product Line:

        NetBotz

        Environment:

        Monitoring NetBotz version 1 via SNMP

        Cause:

        Supported configurations

        Resolution:

        300, 303, 310, 400 series appliances support SNMP version 1 only.

        What is the part number for a replacement for 15/15/EL30?

        There is no direct replacement for this unit. Customer would be able to use 3 items to make this up - 2015/15 , 2031RC30 & 2000H2

        For further information , visit links below:-
        https://www.clipsal.com/Trade/search-results?q=2015/15
        https://www.clipsal.com/Trade/search-results?q=2031RC30
        https://www.clipsal.com/Trade/search-results?q=2000H2
        User-added image

        User-added image
        User-added image

        Does APC support Wake On LAN technology?


        Issue

        Does APC support Wake On LAN technology?


        Product Line

        • All

        Environment
        • All


        Cause



        Background about Wake On LAN technology - t
        he computer/machine to be "woken" is shutdown with power reserved for the network card, but not disconnected from its power source. The network card listens for a specific packet containing its MAC address called the "Magic Packet", broadcast on the broadcast address for that particular subnet.


        Resolution

        Currently, Wake On LAN is not implemented/supported by any APC product.

        Using the Male to Male BNC Adapter Included in a Day/Night CCTV Camera (NBAC0224)

        Issue:

        Using the Male to Male BNC Adapter Included in a Day/Night CCTV Camera (NBAC0224)

        Product Line:

        NetBotz

        Environment:

        NetBotz NBAC0224

        Cause:

        Physical configuration options.

        Resolution:

        The NetBotz Day/Night CCTV Camera has a BNC female output.

        The NetBotz CCTV Pod has BNC connection that looks like a male connector but it actually has a hole in the male connection so it will accept the male-male adaptor included with a Day/Night CCTV Camera.


        List of Device Definition Files (DDF) for Version 2 Netbotz Advanced Device Crawlers

        Issue:

        List of Device Definition Files (DDF) for Version 2 Netbotz Advanced Device Crawlers

        Product Line:

        NetBotz

        Environment:

        NetBotz version 2

        Cause:

        Supported configurations

        Resolution:

        The following is the list of available device definition files (DDF) as of March 2009. Available DDF files:

        APC
        Alcatel
        Avaya
        Best Power
        Cisco Systems
        Compaq
        DMTF
        Dell
        Extreme Networks
        Foundry Networks
        IBM
        Juniper Networks
        Kohler
        Liebert
        MGE
        MIB2-UPS
        Mitsubishi
        NetBotz
        Powerware
        Server Technology
        Sun Microsystems


        SNMP version supported by Version 2 Appliances

        Issue:

        SNMP version supported by Version 2 Appliances

        Product Line:

        NetBotz

        Environment:

        Monitoring NetBotz version 2 via SNMP

        Cause:

        Supported configurations

        Resolution:

        The NetBotz model 320, 420, & 500 appliances only support SNMP version 1 when using Botzware version 2.4 or lower. Starting with version 2.5.0 of Botzware, version 2c and version 3 of SNMP are supported.

        SNMP Device Crawlers Targets Show Offline or Unavailable

        Issue:

        SNMP Device Crawlers Targets Show Offline or Unavailable

        Product Line:

        NetBotz

        Environment:

        NetBotz version 2 SNMP Device Crawlers

        Cause:

        Device Crawlers or Advanced Device Crawlers generally show an unavailable status on a device for one of the following reasons

        Resolution:


        - No connectivity between the bot and the device
        - No SNMP agent installed
        - Wrong community name

        Will the NetBotz Fluid Detector (FD100 or NBES0301) detect 100% pure water?

        Issue:

        Will the NetBotz Fluid Detector (FD100 or NBES0301) detect 100% pure water

        Product Line:

        NetBotz

        Environment:

        NetBotz fluid detectors NBES0301 and NBFD0100

        Cause:

        Fluid detectors work using conductivity. Pure water is not conductive enough to sense.

        Resolution:

        The NetBotz Fluid Detector will detect distilled water but not 100% pure water.

        However, the NetBotz Fluid Detector will probably work in most environments as the minute pure water makes contact with any impure surface (metal pans, floors, etc..) it will pickup ions and should immediately become conductive.

        What are the operational limitations I might encounter when using my APC IP KVM (AP5610, AP5615, AP5616, KVMXXXX) with APC Rack PDU (AP79XX, AP89XX, AP86XX) and AP5641 cable?


        Issue

        Limitations with AP561X or KVMXXX series KVM Switches and APC Rack PDU models using Rack PDU Power Integration features.

        Product Line

        KVM Switches
        • AP5610
        • AP5615
        • AP5616
        • KVM0216A
        • KVM2116P
        • KVM2132P
        Switched Rack PDU
        • AP79XX
        • AP89XX
        • AP86XX

        Environment
        • Installations utilizing the AP5641 power management cable connecting their Switched Rack PDU to their supported KVM Switch model.
        Cause

        There are certain operational limitations that may be encountered when using an APC Digital IP KVM (AP5610, AP5615, AP5616, KVMXXXX) in conjunction with an APC Rack PDU (AP79XX, AP89XX, AP86XX), connected by an AP5641 cable. See below.


        Resolution
        • The AP5641 cable is required for use with the AP5610, AP5615, AP5616, and KVMXXXX series KVMs. The AP9317 cable will not work with these KVM models.
        • With the AP56XX KVM series only, the Rack PDU cannot be accessed over the network when it is connected to an AP56XX IP KVM. This is expected behavior. The Rack PDU allows only one user connection at a time; the KVM uses this connection which prevents any other connection from being made. Users wishing to manage the Rack PDU must do so through the AP56XX IP KVM local or remote interface.
          • The KVMXXXX series KVMs allow the user to set a scan interval to update data between the PDU and KVM.
             
        • When a Rack PDU outlet is turned off through the AP56XX KVM user interface, the outlet turns off immediately instead of using the delay. It also turns on immediately.
           
        • The AP56XX KVM user interface shows that any banked Rack PDU is three-phase, even if it is single-phase.
           
        • The AP56XX KVM user interface shows an incorrect upper limit for the Max Amps alarm threshold.
           
        • For any AP56XX KVM switch installation, the Rack PDU must use the default username/password combination of apc/apc.

        How can I identify what Server Modules are connected to my KVM (AP5602, AP5610, AP5615, AP5616) through the KVM interface?

        Issue

        How can I identify what Server Modules are connected to my KVM (AP5602, AP5610, AP5615, AP5616) through the KVM interface?


        Product Line
         

        • Rack Accessories - KVM Switches
          • AP5602
          • AP5610
          • AP5615
          • AP5616



        Environment

        • All serial numbers
        • All firmware versions



        Cause

        This information is provided for general reference.


        Resolution


        Note: This ONLY applies to the AP5602, AP5610, AP5615 and AP5616

        In the KVM’s web interface home screen (connection page) you should see all of your connected servers. Under the EID column on that page you should see a 12 digit number divided in half by a hyphen (ex. 520705-0000A2). The first 6 digits of that number refer to the physical ID of the Server module that is being used. Reference the EID chart below for easy translation:

         

        Model

        EID Description
         AP5630 520705 APC KVM PS/2 Server Module  
         AP5631 520706 APC KVM USB Server Module 
         AP5632 520707 APC KVM SUN Server Module 
         AP5634 520709  APC KVM USB VM Server Module 
         AP5635 520710 APC KVM PS/2 VM Server Module
         AP5636 520713 APC KVM VT100 Serial Server Module  
         AP5602 520698 APC 16-Port Cat5 KVM (0x2x16)
         AP5610 520701 APC 16-Port IP KVM (2x1x16)
         AP5615 520703 APC 32-Port IP KVM (2x1x32)
         AP5616 520704 APC 32-Port IP KVM (8x1x32)


         

        How do I reset the password on my KVM (AP5602, AP5610, AP5615, AP5616)?


        Issue

        Forgotten or lost password on my APC KVM Switch - models AP5602, AP5610, AP5615, or AP5616


        Product Line
        • Rack Accessories - KVM Switches
          • AP5602
          • AP5610
          • AP5616


        Enviromment
        • All serial numbers
        • All firmware versions


        Cause

        Lost or forgotten password


        Resolution


        By default, there isn't a password on the AP56XX series KVM Switches. If you need to reset the current password please follow these steps:
        1. Local access from the local OSD (on screen display) is required.
        2. Attempt to log in to the KVM. If AP5610, AP5615, or AP5616 an option for "forgot password" will be below the text field. Click this and go to the next step. If  you are using an AP5602, type "Admin" as the username (if necessary) and "help" as the password (both are case sensitive). Press enter and the KVM will display the screen in the next step.
        3. There will be a 16 digit key and EID number displayed. Alternatively, the EID number can be found on the sticker on the bottom of the KVM. Gather this information.  Do not navigate away from this screen.  The 16 digit key is a one time, unique key.
        4. Contact APC technical support (https://www.apc.com/support/contact/)
        5. The representative will be able to generate a backdoor password which will remove the password from the KVM when entered.

        This password reset procedure only resets the local console password. If you have forgotten a username and password for WEB access, you will need to gain local console access and connect to the KVM with a serial connection in order to Restore the KVM to Factory Defaults via the console menu. After doing so, you will lose all of your settings but be able to login with the default WEB username and password of apc/apc.
         

        Network Management Card - Single Phase Symmetra SNMP Trap #77 details


        Issue

        Network Management Card - Single Phase Symmetra SNMP Trap #77 details

        Product Line

        • UPS Network Management Card 1 - AP9617, AP9618, AP9619

        • UPS Network Management Card 2 - AP9630/AP9630CH, AP9631/AP9631CH
           


        Environment

        • All serial numbers
        • All firmware versions
        • SNMPv1 or v3 traps


        Cause

        SNMP trap # 77 (abnormalCondition) is reserved for specific UPS failures. When trap #77 is sent, it also has a binded subtrap which gives further detail into the nature of the fault. The subtraps are specific to the UPS family type. 


        Resolution

        Attached is a breakdown for the Symmetra single phase line of UPS (Symmetra RM, Symmetra LX, Symmetra Power Array), which uses the Network Management Card APP called 'sy'.

         

        Which firewall ports are required to be open in order to establish a KVM over IP connection with the AP561X series of KVM switches?


         
        Issue

        Which firewall ports are required to be open in order to establish a KVM over IP connection with the AP561X series of KVM switches?


        Product Line
        • Rack Accessories - KVM Switches
          • AP5610
          • AP5615
          • AP5616
             

        Environment

        • All firmware versions
        • All serial numbers


        Cause

        Firewall ports must be open in order for the KVM viewer to function properly.


        Resolution


        The Video Session Viewer on the AP56XX line of APC's KVM switches communicates with the KVM over TCP ports 8192 and 2068. Digitized video data is sent over port 8192. Encrypted keyboard and mouse data is sent over port 2068. The Management Panel (MP) communicates with the KVM switch over TCP/UDP port 3211. All data on ports 2068 and 3211 is encrypted using the Secure Socket Layer (SSL) protocol. The KVM switch retains the database of user accounts and permissions. The Viewer performs user authentication over encrypted port 2068. The MP performs user authentication over encrypted port 3211.



         





         

        What UPS units are officially supported by the AP9610 (Relay I/O SmartSlot Card)?


        Issue

        What UPS units are officially supported by the AP9610 (Relay I/O SmartSlot Card)?


        Product Line

        • SmartSlot Accessories
        • Various APC UPS Models - single and three phase

        Environment

        • AP9610
        • Supported UPS models listed below
           
        Cause

        The user is unsure if the AP9610 is supported in their device or AP9610 is not working properly and compatibility is not confirmed.


        Resolution

        The following UPS lines have been officially tested with the AP9610 Relay I/O Card by APC:

        1.  Smart-UPS Model Types with the following prefix:  
          1. SU
          2. SUA 
          3. SURT (except SURTD)
          4. SURTA
          5. SUVT/Galaxy 3500 (Must use Configuration #2 - same as Symmetra)
          6. SUM

        1.  Matrix-UPS series Model Types*

        1.  All single phase Symmetra Model Types including:
          1. Symmetra
          2. Symmetra RM
          3. Symmetra LX
        1. Certain three phase Symmetra PX Model Types including:
          1. 20kW Symmetra PX All-In-One
          2. 40kW Symmetra PX
          3. 80kW Symmetra PX
          4. 48kW Symmetra PX All-In-One
          5. 160kW Symmetra PX
        1. All Silcon DP300E series Model Types.


        *
        Matrix UPSs must be running Matrix firmware revision Z for compatibility with AP9610.

        Please note: The AP9610 is a UPS-Link based product and is not compatible with Microlink UPSs, such as Smart UPS models with the following prefixes: SMT, SMX, SURTD. Please see this APC knowledgebase for more information on the APC Micro-link UPS communication language.

        All other Smart Slot enabled UPS models may work in conjunction with the AP9610.  However, these models have not been officially tested by APC. 

         

        Why does the network card report "UPS: Runtime calibration cancelled" on Symmetra products, even when the calibration finishes?


        Issue

        My UPS Network Management Card reports "UPS: Runtime calibration cancelled" on my Symmetra UPS but the calibration finished.

        The user can issue a runtime calibration either through the NMC or from the front display (PowerView). When the user initiates a runtime calibration, the UPS runs on battery until the UPS reaches roughly 25-35% battery capacity. Upon completion of the calibration the results can differ depending on the device:

        The NMC reports "UPS: Runtime calibration cancelled."
        ISX Manager reports "UPS: A runtime calibration ended."
        The Powerview reports "Run Time Calibration Stopped."


        Product Line

        • UPS Network Management Card 1 (NMC1) - AP9617, AP9618, AP9619 


        Environment

        • NMC is installed in a single phase or three phase Symmetra UPS
        • A runtime calibration command has been issued via the NMC or PowerView front display


        Cause

        APC has identified an issue that pertains to the Symmetra single and three phase product families and the Network Management Cards with SY or SY3P firmware applications. The Network Management Card will report "UPS: Runtime calibration cancelled" in the event log when a runtime calibration is attempted ,regardless of whether the UPS completed the runtime calibration or not. 


        Resolution

        This issue does not exist in UPS Network Management Card 2 products (AP963/AP9630CH/AP9631/AP9631CH/AP9635/AP9635CH). Due to the discontinuation of UPS Network Management Card 1 products listed above, this will not be fixed with a firmware upgrade in those models.

        Customers experiencing this issue should know that:

        • This is purely cosmetic - meaning only the Network Management Card is at fault.  The UPS will complete its runtime calibration if it is not cancelled manually or other factors play into the UPS automatically aborting the process.
        • Because a runtime calibration involves a deep battery discharge, consult with APC support if a runtime calibration is necessary.  Typically, it is unnecessary to perform a runtime calibration more than once a year.

        Network Management Card Compatibility with the Symmetra PX 250/500kVA UPS

        Issue:

        Network Management Card Compatibility with the Symmetra PX 250/500kVA UPS
         

        Product Line:
        • Facility & Data Center 3 Phase UPS
          • Symmetra PX 250/500
         
        • UPS Network Management Card 2
          • AP9635/35CH

        Environment:
        • All installation scenarios

        Cause:

        The AP9635/AP9635CH Network Management Card 2 (NMC2) is restricted for use with the Symmetra PX 250/500 UPS and other select UPS models. Additionally, before upgrading the firmware for the Management Card when installed in a, you must make sure that the firmware upgrade is compatible with the firmware level that is running on the UPS system (its MIM, PM, etc) . For example, as described in the chart below, a Management Card running v5.0.0 firmware cannot support a UPS with system firmware 4.1.x.x unless the Management Card is upgraded to the SYPX APP v5.0.1 firmware. To obtain the firmware upgrade files for the Management Card, you must contact Technical Support.


        Alternatively, the UPS System firmware can be updated to support a Management Card with newer firmware.

        Note: The UPS system firmware upgrade can only be performed by a Field Service Engineer.


        Resolution:

        Review the chart below to make sure the Management Card is running firmware that is compatible with the UPS. To view the UPS System firmware and NMC APP firmware versions from the UPS touchscreen display, press the Firmware Overview button in the System Information menu. The APP firmware version of the Management Card is also displayed in its Web interface, under the Administration->General->About menu.

         

        Compatible Symmetra PX 250/500 UPS and Network Management Card firmware releases
         

        UPS Release

        Network Management Card Firmware APP/Version

         3.x.2

        SYPX/5.0.0

        4.0.4

        SYPX/5.0.1 

        4.11.5 

        SYPX/5.0.2 or 5.1.0 

        4.21.6

        SYPX/5.1.2 or 5.1.3

        4.24.8

        SYPX/5.1.5

        4.25.9 SYPX/5.1.6
        4.27.10 SYPX/5.1.6 or 6.0.8
        4.29.11 SYPX/5.1.6 or 6.0.8
        4.36.12 SYPX/6.4.6
        4.37.12 SYPX/6.5.0

         

        Why is my AP561X KVM Switch Not Recognizing My Rack PDU for Power Management Integration?


        Issue

        My AP5610, AP5615, or AP5616 KVM Switch is not recognizing the attached Rack PDU for Power Management.

        AP561X Digital IP KVM Switches support Rack PDU power integration for the ability to control outlets via the KVM interface. This allows the user to power on/off/reboot a device connected to the KVM if it becomes 'frozen' or warrants a control action. This functionality also allows the user to set and configure outlet delays and monitor current from a supported PDU.



        Product Line

        AP561XX Digital IP KVM Switch models including:
        • AP5610
        • AP5615
        • AP5616
         

        Switched Rack PDU models including:
        • AP79XX
        • AP89XX
        • AP86XX
         


        Environment

        • All serial numbers
        • All firmware versions


        Cause

        One or more of the requirements has not been met to utilize the Rack PDU Power Integration


        Resolution


        In order to use the functionality, please ensure you have met the requirements listed below:
        • You are using either a AP5610, AP5615, or AP5616 Digital IP KVM Switch
        • You are using an APC Switched Rack PDU beginning with AP79XX, AP89XX, or AP86XX connected between your supported KVM Switch's port labeled 'PDU,' 'PDU1,' or 'PDU2' and the RJ-12 serial connection on a supported Switched Rack PDU is the required AP5641 power management cable
        • Your PDU has rpdu application 2.7.0 or higher
        • The username and password on your PDU is set to apc/apc
        Once you have met all the requirements above, PDU functionality should work properly. Some screen captures are below for reference.







        Are APC by Schneider Electric network enabled products IPv6 compliant?


        All APC by Schneider Electric Network Management Card 2 devices with AOS (APC Operating System) > version 5.1.1 or higher are Certified IPv6 Ready (Phase-2/Gold Logo) by the IPv6 forum (https://www.ipv6ready.org). The Logo ID# is 02-C-000439 and was approved on Feb 15, 2010. The Phase 2 Gold Logo verifies optimum compliance with the IPv6 protocol.

        UPS Network Management Card 2 SKUs include but are not limited to: AP9630, AP9631, AP9635, AP9630CH, AP9630J, AP9631CH, AP9631J, AP9635, and AP9635CH.

        Devices that have a mini embedded Network Management Card 2 or UPSs with a preinstalled Network Management Card 2 are Certified IPv6 Ready (Phase-2/Gold Logo) by the IPv6 forum (https://www.ipv6ready.org), as above. 

        Devices with mini embedded Network Management Card 2 include but are not limited to: second generation APC by Schneider Electric Rack Power Distribution Units and select Audio/Video products.

        You can check the model and AOS version from the interface of your Network Management Card 2 from the command line interface via telnet, SSH, and local access by issuing the about command. Via the web interface, navigate to the Administration tab->General->About to view the model and AOS version.

        Additionally, certain APC by Schneider Electric KVM switches include IPv6 functionality, including AP5610, AP5615, AP5616, KVM2132P, KVM2116P, and KVM1116P.

        APC KVM Switch Compatibility (AP5610, AP5615, AP5616 or KVM1116P, KVM2116P, KVM2132P and KVM Access) with Java 7, Update 51 and higher


        Issue

        APC's Rack IP/Digital KVM Switch models rely on a Java viewer for browser access.

        Upon upgrading Java 7, Update 51, the Java client/viewer (accessible via the web browser) for KVM1116P, KVM2116P, and KVM2132P KVM switches will not launch successfully. "Unable to launch the application" may appear or a similar security warning.
         

        Prior to upgrading to Java 7, Update 51, the following message may have been received on KVM1116P, KVM2116P, or KVM2132P:
         
        This application will be blocked in a future Java security update because the JAR file manifest does not contain the Permissions attribute. Please contact the Publisher for more Information.




        On AP5610, AP5615, or AP5616, the following message may also be received:
         



        Lastly, KVM Access Software v1.0.085 for Windows or Linux is not Java 7 compatible. Java 32 bit works best in general. The user may receive an error message similar to below:
         



        Product Line
         
        • Rack Accessories - KVM Switches
          • KVM1116P
          • KVM2116P
          • KVM2132P
          • KVM Access Software
          • AP5610 (discontinued)
          • AP5615 (discontinued)
          • AP5616 (discontinued)



        Environment
        • Java 7, Update 51 and higher on client computer using to access the KVM Switch via a web browser
          • Note: Excludes Java 8
        • KVM1116P, KVM2116P, KVM2132P - firmware v1.0.081 or older
        • KVM Access Software v1.0.085
        • AP5610, AP5615, AP5616 - all firmware versions


        Cause

        Starting with Java 7 Update 51, Java has enhanced security model to make user system less vulnerable to the external exploits. The new version of Java does not allow users to run the applications that are not signed (Unsigned), Self signed (not signed by trusted authority), and the applications that are missing permission attributes.



        Resolution

        Update: The web browser Java client within KVM1116P, KVM2116P, and KVM2132P has been updated within a firmware upgrade to work properly. v1.0.086 is available for KVM2132P/KVM2116P Enterprise IP KVMs and v1.0.088 is available for KVM1116P SMB IP KVM. Please find them attached to this knowledge base below. For KVM Access Software, v1.1.102-02 setup and upgrade files are available and also attached to this knowledge base. 

        Note: KVM Access Software v1.1.102 does not work properly with Java 8. As an interim solution if the user is using Java 8 on their operating system, you can downgrade it to Java 7, then install the KVM Access Software. After successfully installing the KVM Access Software, the user can upgrade to Java 8 again and the software will run with Java 8.

        KVM1116P, KVM2116P, KVM2132P only: The downloadable Java Client AP does not experience this problem. This is an alternative which will allow a user to access the KVM Switch remotely outside of a web browser. Within the web interface of the KVM, select the Download -> Java Client AP and save it to your local machine.

        All KVM models: As a workaround prior to or in place of a KVM firmware upgrade, the user can use Exception Site list feature within Java to run the applications blocked by security settings. By adding the URL of the blocked application to the Exception Site list, it allows the application to run with some warnings.

        For more information on this workaround, please visit this link: https://www.java.com/en/download/help/java_blocked.xml

        AP5610, AP5615, and AP5616 have been discontinued since late 2008 and will not have any future firmware upgrades available.


         

        Can I change the input plug or reduce the cord length on my Rack Power Distribution Unit (Rack PDU) or Rack Automatic Transfer Switch (ATS)?


        Issue

        What is the policy on changing a Rack PDU/ATS input power plug? Can I reduce the cord length? Can I hardwire the input?


        Product Line
         
        • Rack Power Distribution Unit (PDU) Models
          • AP95XX
          • AP75XX
          • AP78XX
          • AP79XX
          • AP84XX
          • AP86XX
          • AP88XX
          • AP89XX
         
        • Rack Automatic Transfer Switch (ATS) Models
          • AP77XX
          • AP44XX


        Environment
         
        • Installation scenarios requiring input plug modifications or cord length reductions


        Cause

        APC policy is provided for reference or documentation reasons.



        Resolution

        APC will continue to honor the product warranty on a Rack PDU or Rack ATS if a licensed electrician is used to change the input plug or provided the replacement plug has the equivalent ratings of the original APC supplied plug. This also applies to users who wish to reduce the cord length. APC will invalidate any warranty claim if a failure is determined to be caused by replacement plug quality, cord modification, and/or installation error. If a warranty replacement is ordered, it is important to understand that the replacement unit will be provided with the original APC specified plug and/or cord length.

        It is the customer's responsibility to ensure the modifications adhere to code standards. In terms of agency approval, it is the responsibility of the Authority Having Jurisdiction (AHJ) to determine the acceptability of the modification or if the modifications are significant enough to require one of UL's Field Engineering Services staff members to evaluate the modified product.

        For more information on UL markings, please see the attached document.


        Note: Opening the actual chassis of the PDU or ATS is strictly prohibited, poses a safety risk, and will immediately void the warranty. APC Rack ATS and Rack PDU products have not been evaluated by safety agencies for hardwiring in the field and as such, customer modification of these products for hard wiring cannot be supported. Hardwiring these products would require removing the cover to gain access to the internal power connections. As mentioned, opening the chassis will immediately void the warranty. Additionally, removing the cover and modifying the input power wiring can create dangerous shock hazards that may result in death or serious injury.
         

        Why doesn't StruxureWare or ISX Manager's mass configuration feature update or show password credentials on APC Network Management Card devices?


        Issue

        Mass configurations of APC UPS Network Management Cards or Network Management Card enabled devices done via ISX Manager or StruxureWare may not work as expected, depending on the firmware version of the devices.


        Product Line

        • Web/SNMP Card - AP9606
        Devices with an embedded Web/SNMP Card include (but are not limited to): Environmental Monitoring Unit 1 (AP9312TH)
         
        • Network Management Card 1 (NMC1) - AP9617, AP9618, AP9619
        Devices with an embedded Network Management Card 1 include (but are not limited to): Metered/Switched Rack PDUs (AP78XX, AP79XX), Rack Automatic Transfer Switches (AP77XX, Environmental Monitoring Units (AP9320, AP9340, NetBotz 200)
         
        • Network Management Card 2 (NMC2) - AP9630/AP9630CH, AP9631/AP9631CH, AP9635/AP9635CH

        Devices with an embedded Network Management Card 2 include (but are not limited to): 2G Metered/Switched Rack PDUs (AP86XX, AP88XX, AP89XX), Certain Audio/Video Network Management Enabled products.

        • InfrastruXure Manager - AP92200



        Environment
         

        • All serial numbers
        • NMC1 AOS v3.6.1 and higher
        • NMC2, versions as noted



        Cause


        In AOS 3.6.1 and above for NMC1 (AP9617, AP9618, AP9619, or any devices with an integrated card), passwords (users, SNMP, etc) were removed from the config.ini stored on the card.  This was done for security reasons.  In NMC2 (AP9630, AP9631, AP9635, or any devices with an integrated card) v5.X.X, the passwords are also not stored in this configuration file.  With v6.X.X firmware, usernames and user passwords specifically are managed completely outside of the config.ini, as outlined in knowledge base FA176542.

        This affects ISX Manager's ability to make mass configuration change of the various password field. Because the ISX Manager takes one device's configuration file and sends it to many, this procedure is now ineffective for retrieving passwords and pushing them to other devices.


        Resolution

        In general, with firmware versions v3.X.X and v5.X.X, the config.ini can still be edited with a keyword to push new passwords to devices, just not to view a current password or retrieve and push one from another device.

        See below for the blurb from a config.ini:
         

        [SystemUserManager]
        ; To change the Administrator, Device, or Read-Only users
        ; passwords, use the AdminPassword, DevicePassword, or
        ; ReadOnlyPassword keywords respectively. i.e., AdminPassword=apc
         

        The config.ini file could be manually configured outside of ISX Manager to include the password using the information from the [SystemUserManager] section above.  APC has a utility that sends one config file to many devices.  It is available for free, with instructions in knowledge base FA156117.
         

        If you have ISX Central or StruxureWare Data Center Expert,  this should not be an issue. These tools will allow the user to retrieve the config.ini, write in a value for the specific password(s) and allow you to push them to your devices. Please see knowledge base FA158360 for further detail.
         

        For further assistance, please contact APC support.
         

         

        Can I plug my APC Rack-Mount Power Distribution Unit (Rack PDU) into a feed receptacle located in the under floor plenum? (Also applicable to Configurable & Modular Power Distribution)


        Yes, provided the installation conforms to NFPA 70 the National Electric Code requirements as stated in Article 645 Information technology equipment.

        With the 2008 Edition (and subsequently the 2011 Edition), Article 645.5 clearly states that cord-and-plug connections and certain cable types are allowed under raised floors, provided certain conditions are met. Following are excerpts from the 2008 Edition of the Code. Refer to the complete section of the applicable edition of the NEC for your locality.
         

        645.5 Supply Circuits and Interconnecting Cables

        (B) Cord-and-Plug Connections. The data processing system shall be permitted to be connected to a branch circuit by any of the following listed means:
         

        (1) Flexible cord and attachment plug cap not to exceed 4.5 m (15 ft).

        (2) Cord set assembly, where run on the surface of the floor, shall be protected against physical damage.
         

        (D) Under Raised Floors. Power cables, communications cables, connecting cables, interconnecting cables, cord-and-plug connections, and receptacles associated with the information technology equipment shall be permitted under a raised floor, provided the following conditions are met:
         

        (1) The raised floor is of suitable construction, and the area under the floor is accessible.

        (2) The branch-circuit supply conductors to receptacles or field-wired equipment are in rigid metal conduit, rigid nonmetallic conduit, intermediate metal conduit, electrical metallic tubing, electrical nonmetallic tubing, metal wireway, nonmetallic wireway, surface metal raceway with metal cover, nonmetallic surface raceway, flexible metal conduit, liquidtight flexible metal conduit, or liquidtight flexible nonmetallic conduit, Type MI cable, Type MC cable, or Type AC cable. These supply conductors shall be installed in accordance with the requirements of 300.11.

        (3) Supply cords of listed information technology equipment in accordance with 645.5(B).

        (6) "Cables," shall be listed as Type DP. Type DP cable having adequate fire resistant characteristics suitable for use under raised floors of an information technology equipment room.


        Rack Power Distribution

        All of APC's Rack PDUs are UL Listed and as such meet all requirements for NEC 645 ITE data center installations. Prior to the 2008 Edition of the NEC, cord-and-plug connections under the raised floor were not explicitly identified in the 2005 Edition of the Code. However, based on the following code sections, these cord-and-plug connections of APC Rack PDUs are acceptable. 1) per 645.4(3) the equipment is UL Listed 2) per 645.5(B)(1) the flexible cord and attachment plug cap do not exceed 15 ft. 3) per 645.5(D)(2) branch-circuit supply conductors to receptacles are properly installed in accordance with 300.11 4) 645.5(D)(5) specifically relates to "cables" used under the raised floor, and not "flexible cord" as is the IT equipment power cord.


        Making Power Connections to Rack PDUs Using Flexible Conduit

        Some installations use wiring in flexible conduit (i.e. Sealtite) that is directly attached to a mating connector body for making the power connection to Rack PDUs. Any US installation must use methods that conform to NFPA 70 Article 300.

        For 50A Rack PDUs that have CS8365 Hubbell style connector, Hubbell has a mating Pro-series connector body that can be attached directly to flexible conduit fittings. We recommend using a Hubbell Pro connector (CS8364L) with a 1/2" (H050) or 3/4" (H075) seal tight connector.


        Configurable and Modular Power Distribution

        Power cables from APC Configurable and Modular Power Distribution units are Type DP-1 TC-ER tray cable and per 645.5(D)(6) and Table 645-5 are allowed under raised floors.
         

         



         

        Netbotz Version 1 Appliances - Ethernet Compliance and Feature Set

        Issue:

        Netbotz Version 1 Appliances - Ethernet Compliance and Feature Set

        Product Line:

        NetBotz

        Environment:

        NetBotz version 1

        Cause:

        The following is the data sheet info on the ethernet chip set used on the version 1 appliances

        Resolution:



        LU3X31FT Single-Port 3 V 10/100 Ethernet Transceiver TX/FX

        Overview
        The LU3X31FT is an integrated 10/100 Mbits/s physical layer device with an integrated transceiver. This part was designed for 10/100 Mbits/s applications where board space, cost, and power are at a premium and stringent functional interoperability is a necessity. Operating at 3.3 V, the LU3X31FT is a powerful device for the forward migration of legacy 10 Mbits/s products and noncompliant (does not have auto negotiation) 100 Mbits/s devices. The LU3X31FT was designed from the beginning to conform fully with all pertinent specifications, from the ISO*/IEC 11801 and EIA/TIA 568 cabling guidelines to ANSI X3.263 TP-PMD to IEEE § 802.3 Ethernet specifications.

        100 Mbits/s PLL, combined with the digital adaptive equalizer, robustly handles variations in rise-fall time, excessive attenuation due to channel loss, duty-cycle distortion, crosstalk, and baseline wander. Transmit rise-fall time manipulated to provide lower emissions, amplitude fully compatible for proper interoperability. Programmable scrambler seed for better FCC compliancy. Selectable CIM, Class II support, and powerful MII drivers for repeater applications.

        IEEE 802.3u Clause 28 compliant auto-negotiation for full 10M and 100M control. Fully configurable via pins and management accesses. Extended management support with interrupt capabilities. PHY rise fall support. Symbol mode option. Full LED support. Low power consumption 150 mA max. 80-pin MQFP and 80-pin LQFP packages.

        Features

        Single-chip integrated physical layer and transceiver for auto-negotiation-T and/or 100Base-T functions.
        IEEE 802.3 compatible auto-negotiation-T and 100Base-T physical layer interface and ANSI X3.263 TP-PMD compatible transceiver.
        PECL interface for external FX transceiver. Built-in analog 10 Mbits/s receive filter, removing the need for external filters. Built-in 10 Mbits/s transmit filter. 10 Mbits/s PLL exceeding tolerances for both preamble and data jitter.
        ISO is a registered trademark of The International Organization for Standardization. EIA is a registered trademark of The Electronic Industries Association. ANSI is a registered trademark of The American National Standards Institute, Inc. § IEEE is a registered trademark of The Institute of Electrical and Electronics Engineers, Inc.

        Troubleshooting Netbotz Version 1 Appliance LED Messages

        Issue:

        Troubleshooting Netbotz Version 1 Appliance LED Messages

        Product Line:

        NetBotz

        Environment:

        NetBotz version 1 appliances.

        Cause:

        After you power up the NetBotz appliance, the appliance performs several self-checks. If the appliance is functioning normally, the LEDs are then used to indicate alert conditions for specific sensors. For example, if the appliance is functioning correctly and the Temp LED is illuminated it indicates that the appliance is currently reporting a Temperature alert state. However, if during the power on test cycle the appliance detects an error with any components, it indicates the problem by lighting up one or more LEDs on the appliance. The following LEDs are present on the front of the NetBotz appliance:Green LEDs: * On * Lk * Tx * Rx * 10/100 Yellow LEDs: * Temp * Humidity * Airflow * Contact * Sound * Crawlers * External (WallBotz 310, WallBotz 400, and RackBotz 400 only) Note which LEDs are illuminated on your appliance and then refer to the following table to determine potential causes and solutions.

        Resolution:

        Illuminated LEDs Problem Solution
        ON & LK If the On and LK LEDs are lit, your appliance is functioning normally. These light should remain lit up while the appliance is plugged in. Not Applicable
        Temp only The appliance boot loader has failed. Specifically the checksum for the boot ROM is faulty. Return the appliance to NetBotz; contact NetBotz support for instructions.
        Humidity Only The firmware failed its checksum. Return the appliance to NetBotz; contact NetBotz support for instructions.
        Airflow only The onboard RAM is faulty Return the appliance to NetBotz; contact NetBotz support for instructions.
        Contact only The real-time clock failed. Return the appliance to NetBotz; contact NetBotz support for instructions.
        Temp, Humidity, & Contact The appliance detected a problem while testing the sensors. Specifically, the analog-to-digital converter is out of calibration. Cycle the appliance power, which may cause the appliance to reset itself. If this does not work, contact NetBotz support for instructions on return or possible recalibration.
        Temp, Humidity, Airflow, & Contact The camera failed to initialize. Cycle the appliance power, which may cause the appliance to reset itself. If this does not work, contact NetBotz support for instructions.
        Contact & Temp The Ethernet MAC hardware failed its loopback test. Cycle the appliance power, which may cause the appliance to reset itself. If this does not work, contact NetBotz support for instructions.
        Contact & Humidity The Ethernet PHY hardared failed its loopback test. Cycle the appliance power, which may cause the appliance to reset itself. If this does not work, contact NetBotz support for instructions.

        How do I recover the firmware on an AP5610, AP5615, AP5616 Digital IP KVM models?


        Issue

        Need KVM Firmware Recovery Procedure to remedy a corrupted firmware image.


        Product Line
         
        • Rack Accessories - KVM Switches:
          • AP5610
          • AP5615
          • AP5616
             

        Environment
         
        • All serial numbers
        • All firmware versions
        • Corrupted firmware image
        • KVM Power LED flashing constantly after applying power

        Cause
         
        If power to the KVM switch is lost during a firmware upgrade, it can corrupt the firmware image stored on the KVM switch. If you have a KVM switch that will not boot to the On Screen Display, it may be required to recover the firmware in the following method outlined below.


        Resolution

        Follow the steps below.


        Required Items:
         
        • PC with network card
        • TFTP software (there is freeware available on the web such as 3CDaemon, TFTPD32, or PumpKIN). It MUST be TFTP.
        • Network cable (Cat5 or Cat6, does not have to be crossover if the NIC supports gigabit)
        • Local access to the KVM switch
        • Latest firmware file available via apc.com
        • CMN number on the upper left hand corner of the white sticker on the bottom of the KVM switch. Refer to the chart below if you are sure about your KVM switch model.

         

        KVM Switch Model

         CMN Number

         AP5610

         1016

         AP5615/AP5616

         1025


        Procedure:
         
        • Create a direct connection between the network card of the PC and the network port on the KVM switch using the network cable
        • Reconfigure the PC to have a static/manual IP address of 10.0.0.3 and subnet mask of 255.0.0.0, no default gateway is required.
        • Rename the firmware file to the following syntax: CMN-XXXX.fl
          • Replace X’s with the CMN number gathered off the bottom of the unit or from the chart noted above. This filename is case sensitive.
        • Place the firmware file in the TFTP server's root directory and ensure the TFTP server is started/enabled.
        • When the KVM first turns on, it has an IP address of 10.0.0.2. It will look for a TFTP server at 10.0.0.3 and boot from the network if it finds a TFTP server with the proper firmware file being hosted.
          • When the transfer begins, you will see a TFTP request/transfer on your TFTP server's log.
        • Upon completion of the firmware recovery, the KVM switch will flash all of it's LEDs and now boot to its On Screen Display menu. Alternatively, you can establish a local console session to gain access to the KVM configuration menu.


        Note: The TFTP server MUST be set to provide all files when asked, meaning; there isn’t any prompting by the TFTP server. Please check the TFTP server's options to ensure this is set correctly.
         

         
        If you have problems following this procedure, please contact APC by Schneider Electric technical support for assistance.



         

        APC KVM Switches and Corresponding Cables/Server Modules

         

        APC KVM Part Numbers and Corresponding Cables/Server Modules


        KVMXXXX Series KVM Switches/Cabling

        The KVMXXXX series of KVM Switches include KVM0108A, KVM0116A, KVM1116P, KVM0216A, KVM2116P, and KVM2132P. There is no backwards or forwards compatibility between this series and any other KVM models or families listed below except for the AP5641 power management cables and AP5262/AP5262 daisy chain cables as listed below.

        KVM0108A/KVM0116A - SMB Analog KVMs are compatible with:
         
        • KVM-USB - APC KVM 2G, Server Module, USB
        • KVM-PS2 - APC KVM 2G, Server Module, PS/2
        • AP5262 - APC KVM Daisy-Chain Cable - 2 ft (0.6 m)
        • AP5263 - APC KVM Daisy-Chain Cable - 6 ft (1.8 m)
          • Please note: It is possible to connect AP5262/AP5263 together for a maximum length of 18 ft.

        KVM1116P, KVM2116P, KVM2132P - SMB/Digital IP KVMs are compatible with:
         
        • KVM-USB - APC KVM 2G, Server Module, USB
        • KVM-PS2 - APC KVM 2G, Server Module, PS/2
        • KVM-USBVM - APC KVM 2G, Server Module, USB with Virtual Media
        • KVM-PS2VM - APC KVM 2G, Server Module, PS/2 with Virtual Media
        • KVM-USBVMCAC - APC KVM 2G, Server Module, USB with Virtual Media and CAC
        • KVM-SERIAL - APC KVM 2G, Server Module, Serial
        • AP5641 - APC KVM Power Management Cable

         


         

        The analog KVM (AP5602) and Digital IP KVMs (AP5610, AP5615, AP5616) use their own set of server modules and cabling. There is no backward or forward compatibility between the AP56XX KVMs and APC's first generation IP/Cat5 KVM offering (AP54XX). There is also no compatibility between the aforementioned models and the KVMXXXX KVM series, except for the AP5641 power management cable. All require CAT5 or 6 UTP cabling.
         

        AP5602 - CAT5 analog KVM is compatible with:
         
        • AP5630 APC KVM PS/2 Server Module
        • AP5631 APC KVM USB Server Module
        • AP5632 APC KVM SUN Server Module
        AP5610, AP5615, AP5616 - IP KVM's are compatible with
        • AP5630 - APC KVM PS/2 Server Module
        • AP5631 - APC KVM USB Server Module
        • AP5632 - APC KVM SUN Server Module
        • AP5634 - APC KVM USB VM Server Module
        • AP5635 - APC KVM PS/2 VM Server Module
        • AP5636 - APC KVM VT100 Serial Server Module
          • AP5640 - Power supply for Serial Server Module *
        • AP5641 - APC KVM Power Management Cable**

        * Power supply for Serial Server Module can support up to (4) APC KVM Serial Server Modules.

        ** AP5641 is the only supported cable for Power management. AP9317 has similar connections but should NOT be used as it is for a different purpose.


        The first generation of APC CAT5 Analog KVM (AP5401) and IP KVM (AP5405) require both a server module and CAT5 or 6 UTP cabling.

        AP5401 - 16 port Analog CAT5 KVM (PC PS/2, PC & SUN USB, SUN Mini-DIN)
        AP5405 - 16 port IP KVM (PC PS/2, PC & SUN USB, SUN Mini-DIN)

        • AP5460 - CAT5/IP KVM PS/2 Server Module (SM)
        • AP5461 - CAT5/IP KVM USB Server Module (SM)
        • AP5462 - CAT5/IP KVM SUN Server Module (SM)
           

        The APC Multi-Platform Analog KVM Switches with pre-set lengths of cables listed below:

        AP5201 - 8 port Multi-Platform Analog KVM (PC PS/2, USB, SUN 13W3 or VGA)
        AP5202 - 16 port Multi-Platform Analog KVM (PC PS/2, USB, SUN 13W3 or VGA)
        AP5808 - 17" Rack LCD Console with Integrated 8 Port Analog KVM Switch
        AP5816 - 17" Rack LCD Console with Integrated 16 Port Analog KVM Switch

        • AP5264 – 3' PS/2 Cable
        • AP5250 – 6' PS/2 Cable
        • AP5251 - 6' SUN (13W3) Cable
        • AP5252 - 6' SUN (VGA) Cable
        • AP5253 – 6' USB Cable
        • AP5254 – 12' PS/2 Cable
        • AP5255 - 12' SUN (13W3) Cable
        • AP5256 - 12’ SUN (VGA) Cable
        • AP5257 – 12’ USB Cable
        • AP5258 - 25' PS/2 Cable
        • AP5259 - 25' SUN (13W3) Cable
        • AP5260 - 25' SUN (VGA) Cable
        • AP5261 - 25' USB Cable
        • AP5262 - 2' AP52XX/AP58XX Daisy Chain Cable
        • AP5263 - 6' AP52XX/AP58XX Daisy Chain Cable
        • AP5821 - 6' USB Extension Cable (AP5808/AP5816 only)
        • AP5822 - 12' USB Extension Cable (AP5808/AP5816 only)
        • AP5823 - 25' USB Extension Cable (AP5808/AP5816 only)

         




        ***Note: These KVM switches and related cables are no longer manufactured or sold by APC.

        AP9254 4 port KVM (PC only)

        • AP9850 - 10’ PS/2 Cable
        • AP9851 - 25’ PS/2 Cable for AP9254/ AP9258

        AP9258 8 port KVM (PC only)
        • AP9850 - 10’ PS/2 Cable for AP9254/ AP9258
        • AP9851 - 25’ PS/2 Cable for AP9254/ AP9258

        AP9278 8 port KVM (PC/Sun PS/2, USB)
        • AP9850 - 10’ PS/2 Cable for AP9254/ AP9258
        • AP9851 - 25’ PS/2 Cable for AP9254/ AP9258
        • AP9853 - 15’ Cable for Sun for AP9278 
        • AP9854 - 15’ 13W3 Cable for Sun for AP9278
        • AP9855 - 12’ USB Cable for AP9278


        Pairing Cable for AP9258 and AP9254 ONLY: AP9852


        *NOTE: In order to pair the above KVMs, the units must have a serial number greater than: RA0235
         


        MasterView KVM Part #s and Corresponding Cables


        58066 – 4 port KVM (PC only) Cascade up to 64 PCs

        • 58PS2V-Length – Available in 6, 10, 15 and 25 foot lengths, for PS/2 Kbd/Mouse, Video
        • 58ATV-Length – Available in 6, 10, 15 and 25 foot lengths for, PC Kbd, Serial Mouse, Video

        58065 – 8 port KVM (PC only) Cascade up to 302 PCs
        • 42011-10 – 10’ Cable for PS/2 Keyboard & Mouse, Video
        • 42010-10 – 10’ Cable for PC Keyboard, Serial Mouse, Video
        • 42014-10 – 10’ Extension cable for 42011 & 42010
        • 58012-3/10 – 3’ or 10’ Cascading cable for 58065 KVM Switch


        58068 - 16 port KVM (PC only) Cascade up to 302 PCs, w/ audio

        • 42011-10 – 10’ Cable for PS/2 Keyboard & Mouse, Video
        • 42010-10 – 10’ Cable for PC Keyboard, Serial Mouse, Video
        • 42014-10 – 10’ Extension cable for 42011 & 42010
        • Or 42087-6/10/15 for Audio support as well as PS/2 Kbd/Mouse, Video
        • 42088-2 cascade cable for 58068 KVM Switch


        58098 – 4 port KVM (PC only)

        • 58PS2V-Length – 6,10,15 and 25 foot length


        58100 – 4 port USB KVM (PC only)

        • 58USB-6 -Length – 6 foot
        • 58USB-10 -Length – 10 foot
         

        Why does my local mouse (the mouse on the server I am connecting from) not synchronize with my remote mouse (the mouse on the server I'm connecting to) when connected through the APC IP KVM product?



        Issue

        When using an IP KVM Switch, the local mouse does not sync up with the remote mouse on the target device. The mouse is 'laggy.'


        Product Line

        • Rack Accessories - IP KVM Switches
          • KVM1116P
          • KVM2116P
          • KVM2132P
          • AP5610
          • AP5615
          • AP5616
          • AP5405


        Environment

        • IP KVM Switch
        • Mouse lag/sync problems
        • All firmware versions
        • All serial numbers

        Cause

        When connecting to a server via a Digital IP KVM, you may notice that the local mouse (your desktop) is not synchronizing with the remote mouse (the workstation/server that you are attaching to). There are a couple of steps that you can take to resolve this, depending on the KVM you are using.



        Resolution


        Recommended options and tweaks for KVM1116P, KVM2116P, and KVM2132P
        • Try enabling mouse sync mode which is an icon option available from the Remote Viewer Toolbar.
        • From the same toolbar, it is recommended to try and set the Network Type to 512K ADSL under Video Settings
        • Consider changing the mouse mode between single, dot, dual, crosshair options along with enabling/disabling mouse sync between each of the mouse modes. (This is also accessible from the Remote Viewer Toolbar.)
        • Make sure "Cable Length" is set accurately for your configuration. The available options are short, medium, and long. (This is also accessible from the Remote Viewer Toolbar.)
        Recommended options and tweaks for AP5610, AP5615, AP5616

        • Connect to a server via the Digital IP KVM. Once connected to the target server via the IP KVM's Java viewer, select Tools, then Single Cursor mode to sync your mouse with the target server's.
        Recommended options and tweaks for AP5405

        • If using an AP5405, connect to a server via the IP KVM. Once connected, scroll to the top of the server window. You should see the following menu options: Shortcuts, Options, Connection, Host OS, About.... Choose Options, then Auto Sync Mouse.

        You can also try adjusting mouse settings direct from the attached servers (i.e. mouse acceleration) if the mouse is not working correctly (meaning the servers attached to the KVM, not the server you're connecting from).


        Windows NT Platforms :

        Connect to the server via the IP KVM. Perform the following steps:
        1. Start/Settings/Control Panel to open the Control Panel window.
        2. Double-click the Mouse icon to open the Mouse Properties dialog box.
        3. Click the Motion tab.
        4. Move the pointer speed slider to slow, which is the tick mark furthest to the left).
        5. Make sure the Snap to default checkbox is unchecked.
        6. Click OK to close the Mouse Properties dialog box and to save your settings.

        Windows 2000 Platforms:

        Connect to the server via the IP KVM. Perform the following steps:
        1. Start/Settings/Control Panel to open the Control Panel window.
        2. From the Control Panel, double-click the Mouse icon to open the Mouse Properties dialog box.
        3. Click the Motion tab.
        4. Move the speed slider to the default of 50% (the middle of the slider or the sixth tick from the left).
        5. Set the Acceleration option to None.
        6. Make sure the Snap to default checkbox is unchecked.
        7. Click OK to close the Mouse Properties dialog box and to save your settings.

        Windows XP, 2003, Vista, 7, or 2008:


        Connect to the server via the IP KVM. Perform the following steps:
        1. Start/Control Panel to open the Control Panel window. (Accessing the Control Panel can differ depending on the version of Windows is being used)
        2. From the Control Panel, double-click the Mouse icon to open the Mouse Properties dialog box.
        3. Click the Pointer Options tab.
        4. Set the Select a pointer speed slider to the default of midpoint (the middle of the slider or the sixth tick mark from the left).
        5. Uncheck the Enhance pointer precision checkbox.
        6. Make sure the Snap To and the Visibility checkboxes are unchecked.
        7. Click OK to close the Mouse Properties dialog box and to save your settings.


        Systems with Intellipoint Drivers:


        Connect to the server via the IP KVM. Perform the following steps:
        1. Start/Control Panel to open the Control Panel window.
        2. From the Control Panel, double-click the Mouse icon to open the Mouse Properties dialog box.
        3. Click the Pointer Options tab.
        4. Set the Select a pointer speed slider to the default of midpoint (the sixth tick mark from the left).
        5. Uncheck the Enhance pointer precision checkbox.
        6. Make sure the Snap To and the Visibility checkboxes are unchecked.
        7. Click the Wheel tab.
        8. Uncheck the Enable accelerated scrolling ... checkbox.
        9. Click OK to close the Mouse Properties dialog box and to save your settings.

        Linux (pre 8.0)


        Connect to the server via the IP KVM. Perform the following steps:
        1. From the Workspace Menu, click the Desktop Manager icon and select Application Manager -Desktop_Controls to open the Control Center dialog box.
        2. From the tree view, select Peripherals - Mouse to list the mouse settings.
        3. Set the Acceleration slider to the center position.
        4. Optional) Select the desired Mouse buttons option and set the Threshold slider to the desired position.
        5. Click OK to close the Control Center dialog box and to save your settings.

        Linux (post 8.0)


        Connect to the server via the IP KVM. Perform the following steps:
        1. Click the Red Hat icon.
        2. Select Preferences - Mouse to open the Mouse Preferences dialog box.
        3. Click the Motion tab.
        4. Set the Acceleration slider slightly left of the center position.
        5. (Optional) Set the Sensitivity and Threshold sliders to the desired positions.
        6. Click Close to close the Mouse Preferences dialog box and to save your settings.

        Red Had Enterprise Edition


        Connect to the server via the IP KVM. Perform the following steps:
        1. Click the Main Menu icon.
        2. Select Programs - Settings - Peripherals - Mouse to open the Mouse dialog box.
        3. Click the Start Here icon to open the Start Here dialog box.
        4. Click the Preferences icon to open the Control Center dialog box.
        5. Click the Peripherals icon to open the Peripherals dialog box.
        6. Set the Acceleration slider to the middle position.
        7. (Optional) Select the desired Mouse buttons option and set the Threshold slider to the desired position.
        8. Click OK to close the Mouse dialog box and to save your settings.

        SUSE Linux


        Connect to the server via the IP KVM. Perform the following steps:
        1. Click the SUSE icon and select Control Center. (By default, SUSE uses a modified version of the KDE graphical user interface.)
        2. Click anywhere in the screen area to open the Behavior (first time use default) - Control Center window where you clicked.
        3. If the Index side navigation bar is shown in tree view, click the plus symbol (+) next to Peripherals to display the submenu items.
        4. Select the Mouse option to display the Mouse - Control Center dialog box.
        5. Click the Advanced tab.
        6. Set the Pointer acceleration slider to the leftmost position (1.0x).
        7. (Optional) Set the Pointer threshold, Double click interval, Drag start time, Drag start distance and Mouse wheel scrolls by sliders to the desired positions.
        8. If necessary, click Defaults to restore the default settings.
        9. Click Apply to save your settings.
        10. Click the X button in the upper-right corner to close the Mouse - Control Center dialog box.

        Solaris 9


        Connect to the server via the IP KVM. Perform the following steps:
        1. From the Workspace Menu, select Desktop Manager and go to step 3 - or -
        2. Click on the tab above the Text Note control and select Applications to open the Application Manager window.
        3. Click the Desktop_Controls icon to open the Application Manager - Desktop_Controls window.
        4. Double-click the Mouse Style Manager icon to open the Style Manager toolbar and Style Manager - Mouse dialog box.
        5. In the Style Manager - Mouse dialog box, set the Acceleration slider to 1.0.
        6. (Optional) Select the desired Handedness and Button 2 options and set the Double-Click and the Threshold sliders to the desired positions. Test the double-click speed by double-clicking on the mouse icon.
        7. Click OK to close the dialog box and to save your settings.

        Solaris 10


        Connect to the server via the IP KVM. Perform the following steps:
        1. In the Front Panel dashboard, click the Style Manager icon to open the Style Manager toolbar.
        2. Double-click the Mouse icon to open the Style Manager - Mouse dialog box.
        3. In the Style Manager - Mouse dialog box, set the Acceleration slider to 1.0.
        4. (Optional) Select the desired Handedness and Button 2 options and set the Double-Click and the Threshold sliders to the desired positions. Test the double-click speed by double-clicking on the mouse icon.
        5. Click OK to close the dialog box and to save your settings.

        Certain Sun/Linux Varieties adjustment via Terminal Session

        Open a terminal session and issue the following command:

        Sun: xset m 1
        Linux: xset m 0 or xset m 1 (if one doesn't help, try the other.)
        Linux using the Redhat AS3.0 mouse mode: xset m 1


        Mac OS


        Connect to the server via the IP KVM. Perform the following steps:
        1. Click the Apple icon.
        2. Select System Prefs to open the System Prefs window.
        3. Select View - Mouse to open the Mouse dialog box.
        4. Set the Tracking Speed slider to the default of the fifth tick mark from the left.
        5. (Optional) Set the Double-Click Speed slider to the desired position. Test the double-click speed by double-clicking a word in the text field below the slider.
        6. Close the Mouse dialog box to save your settings.

        If your mouse is still not synchronizing, please contact APC technical support. Please be sure to provide the following to your technical support representative to expedite resolution.
        • How far apart is the local and remote mouse pointer?
        • Does this problem occur on all remote servers?
        • What type of browser is local and remote?
        • What operating system platform is on the local and remote server/workstation?
        • What is the firmware revision of your IP KVM?
        • Server module part number (Server modules are the components that connect the from the RJ-45 port on the KVM to your remote server).
        • Length and type of Ethernet cable being used between the KVM and the server.