ISOBAR TEE-OFF BOOTS PACK 50 PT005-22B

Isobar Tee-Off Boots Pack 50 Pt005-22B

Catalogue Number: ISOBOOTS
ISOBAR TEE-OFF BOOTS PACK 50 PT005-22B
Colour:
Colour: Per UOM Std.
  • 1 PCE

Specifications

hide show
Range
Acti 9
Product or component type
Isobar boots
Accessory / separate part category
connection accessory
Quantity per set
set of 50
Range compatibility
Acti 9 Isobar B distribution board
EU RoHS Directive
Compliant
WEEE
The product must be disposed on European Union markets following specific waste collection and never end up in rubbish bins

Documents & downloads

hide show
Filter items
  • All

  • Technical Data Catalogues

  • Specifications

Frequently Asked Questions

hide show

Does Combox have a scheduled timeout requiring login?

The Combox does not timeout except when it reboots at 3:05AM. If Combox screen reverts to login during the day, it means the Combox 
has lost connection. Check network.

NetBotz TFTP upgrade procedure.

Issue:
NetBotz TFTP upgrade procedure.

Product Line:
NetBotz version 3

Environment:
NetBotz model: 355, 455, 450, 550,  570.

Cause:
Optional NetBotz firmware upgrade/recovery instructions. This option may also be a suggested procedure for restoring a NetBotz appliance to default due to unknown configuration issues or other unknown behavior on a NetBotz appliance.

Resolution:
 
NOTE:  These steps must be run from a PC on the same network segment as the NetBotz Appliance.
NOTE:  The only cables/sensors that can remain plugged into the NetBotz Appliance during this procedure are the USB console cable and the network cable.
 
1) Download the firmware for the NetBotz Appliance.

2) Extract the zip file on your computer.

3) Due to antivirus programs setting the TFTPd32.exe file as a virus, it is no longer provided within the firmware download.  You may use any tftp program, or if you would like to use the TFTPd32.exe program, see FA274811.

4) Set the base directory of your TFTP server to be the extracted firmware files tftp directory (/releases_netbotzv3/4.X.X/tftp/)
NOTE: Ensure that there are no firewalls or other network security that would block TFTP traffic between the NetBotz Appliance and the computer running the TFTP server.

5) Connect a USB cable from your computer to the console port on the Appliance.

6) To find the correct communication (COM) port to use within the next step, you will need to open the Device Manager within the control panel.  Within the Ports section will be a USB Serial port with a COM# listed at the end in parenthesis.  If the USB Serial Adapter is not showing, refer to knowledge base FA158350.

7) Open a terminal emulator such as Windows HyperTerminal or PuTTy.  Select serial communication and use the following settings:
- Bits/second: 38,400
- Data Bits: 8
- Parity: None
- Flow Control: None
- Stop Bits: 1

Example PuTTy Configuration:

1) Under Session, change the connection type to serial.

2) Edit the serial connection parameters under: Connection > Serial


Example HyperTerminal Configuration:
 
1) Type a name for the connection and on the next screen select the appropriate COM port that was discovered earlier

8) When opening the connection, you should be at a login prompt.

NOTE: Please read ALL of step 9 before continuing.
9) Unplug the power from the NetBotz Appliance while keeping the serial connection open.  Wait 5 seconds and plug it back in.  When it is turned bac on, you will need to have the serial session active.  It will be counting down to stop the auto-boot, press <enter> to stop the auto-boot sequence.  If you do not see the countdown, repeat this step.

10) You should now be at a NetBotz> prompt.  Enter the following commands to direct the appliance where to retrieve the new code from: 
a) setenv serverip aaa.bbb.ccc.ddd <enter>  (aaa.bbb.ccc.ddd is the IP address of the PC that has the TFTP server installed and running)
b) saveenv <enter> (saving the server settings)
c) printenv <enter> (print the settings to the screen for verification)
NOTE: Please read step 11 before performing Step 10d.
d) reset <enter>

11) Stop the auto-boot again before the countdown expires.

12) If the appliance is using DHCP, please proceed to step 12f.  If the appliance is not using DHCP, set the IP address using the following steps:
a) setenv ipaddr aaa.bbb.ccc.ddd <enter> (IP address for the NetBotz Appliance)
b) setenv gatewayip aaa.bbb.ccc.ddd <enter> (Gateway IP address for the NetBotz Appliance)
c) setenv netmask aaa.bbb.ccc.ddd <enter> (Subnet mask for the NetBotz Appliance)
d) saveenv <enter> (saving the network settings)
e) printenv <enter> (print the network settings to the screen for verification)
NOTE: Read step 13 before performing step 12f.
f) reset <enter> (reboots the NetBotz Appliance)

13) Stop the auto-boot again before the countdown expires.

14) Issue the following command:  postupg <enter>  (This starts the firmware upgrade process)
a) If you see this, it means the network is not setup correctly and the steps need to be performed again (starting with step 9)
b) If it is successful, it will look like the following:

NOTE: Read through step 16, before performing step 15.
15) After the upgrade completes, issue the following command: reset <enter> (reboots the NetBotz Appliance)

16) Stop the auto-boot again before the countdown expires.

17) Issue the following command:  rootupg <enter> This process will take approximately 7-8 minutes to complete.  After completing, the system will automatically reboot.
NOTE: There is an additional option of rootupgkeep instead of rootupg, which will keep the settings on the appliance.

18) If you are not using DHCP, after reboot, log into the appliance using a username/password of root/apc to set the network settings on the appliance.

You should now be able to manage the NetBotz Appliance using the Advanced View application.

What can I do if the PLC TM221 reboots continuously after have updated it with the firmware 1.3.2.1 SP1?

This issue can be solved downloading any application in the PLC TM221 via USB in power less mode ( no power supply connected )
After that the issue will not appear anymore

CM4000 rebooting intermittently

Issue
CM4000 meter reboots itself intermittently.

Product Line
CM4000, CM4000T

Cause
Sending an IRIG-B time synch signal (instead of a DCF-77 format signal) into a digital input configured for time synch on the CM4000 causes it to reboot randomly.

Resolution
Ensure that the proper I/O format signal is connected to the CM4000.
The CM4000's can only accept DCF-77 time synch signals.

Kindly refer to page 72 of the CM4000 Reference Manual for more details on time synch signals.

PM850/870 Device Reboots For No Apparent Reason in ION Enterprise \SPM \ PME

Issue
An ION Enterprise 5.6 SP1 or 6.0, StruxureWare Power Monitoring (SPM), Power Monitoring Expert (PME) system which includes a PM850 or PM870 device,
the device reboots periodically for no apparent reason.

Product Line
PM850
PM870

Environment
ION Enterprise 5.6 SP1, StruxureWare Power Monitoring (SPM), Power Monitoring Expert (PME)
PM850
PM870

Cause
There is a problem with firmware versions for PM8 devices prior to v10.8 which can cause the device to reboot if it is polled frequently.

Resolution
Upgrade the meter firmware to version 10.8 or greater. Upgrading the meter firmware will also allow the device to provide information required for a CBEMA plot.

Access to firmware upgrade instructions, including a how-to video and a link to the latest firmware can be found at:  Firmware Upgrade - Instructions and Downloads
If only the firmware is required, it can be downloaded directly from: https://www.schneider-electric.com/en/download/document/PM8xx_V12.5/

Or Alternatively,

1) Using a internet browser navigate to www.schneider-electric.com
2) select Support, then Download Center from the Green menu bar
3) type "PM800 Series V12.500 Firmware" into the search bar and click on the Search button
4) click on the "PM800 Series V12.500 Firmware" link presented in the search results
5) click on the Download button to start the download and save the file

Note: Also by entering only PM800 and/or keyword search criteria into the search bar, you be find wide variety of PM800 related documents.

ION8650 firmware v4.30 or v4.31 continuous reset when using IRIG-B time syncing

Issue
A ION8650 meter running firmware v4.30 or v4.31 using IRIG-B for time sync goes into continual reboots or power cycling.

Product Line
ION8650

Environment
ION8650s at firmware 4.30 or 4.31 using IRIG-B for time sync.

Cause
When the meter is set to IRIG-B in the clock source setting, and a valid timestamp is sent to the meter via IRIG-B hardware, the meter performs a reset.  In some cases, this reset only happens once, and the meter will return to normal operation. However, there are reported cases where the meter will continuously reset when a valid IRIG-B signal is present.

Resolution
The condition has been identified and addressed in firmware update v4.31.1 as stated in the What's new in PowerLogic ION8650 firmware V4.31.1 document.  

The suggested resolution is to update to the current version of the firmware v4.31.2.

Does pressing the Reset button on a Metered or Switched Rack PDU or Rack ATS cause the outlets to reboot?


Issue

Does pressing the pinhole reset button on a Metered or Switched Rack PDU or Rack ATS cause the outlets to reboot or disrupt power in any way?



Product Line
 
  • Rack Power Distribution - Power Distribution Units and Automatic Transfer Switch
    • AP77XX - Rack ATS
    • AP44XX - Rack ATS
    • AP78XX - Metered Rack PDU
    • AP79XX - Switched Rack PDU
    • AP84XX - Metered By Outlet PDU
    • AP86XX - Switched Rack PDU with Metering By Outlet
    • AP88XX - Metered Rack PDU 2G
    • AP89XX - Switched Rack PDU 2G


Environment
 
  • All installations


Cause

Many users ask if rebooting their network management card affects outlet status or power output of their device. See below for additional information.


Resolution

Resetting the network interface using the small reset button near the network jack has no effect on the electrical output of the Rack PDU or Rack ATS. This procedure simply reboots the embedded Network Management Card, which will render the network port inaccessible for a short period of time while it reboots.



However,  on AP7XXX series, if you press and hold the display button (the gray button near the LCD) while the network interface is rebooting (you will see 88 on the display) and the outlets WILL turn off. APC recommends that you never press the display button during reboot of the network interface and there is no functional reason that requires a user to ever do this.

 

Why does my Rack ATS (AP77XX) lose SNMPv1 communication with my StruXureWare device or ISX Manager?



Issue

My Rack ATS (AP77XX) is losing SNMPv1 communication with my StruXureWare device, ISX Manager, or other SNMP NMS periodically.


Product Line
 
  • Only the following Rack Automatic Transfer Switch (ATS) models:
    • AP7752
    • AP7753
    • AP7721
    • AP7723
    • AP7724
    • AP7730
    • AP7732

Environment
 
  • All serial numbers
  • Rack ATS app g2ats v3.5.7 and below
  • Rack ATS monitored by the SNMPv1 protocol


Cause

An issue has been previously indentified with the aforementioned Next Generation Rack ATS product firmware that causes the device to lose SNMPv1 communication with StruXureWare, ISX Manager, or other SNMP monitoring programs. This issue occurs after an undefined amount of uptime but limiting access control to specific devices seems to help increase the uptime to about 30-45 days for the integrated Network Management Card.


Resolution


This has been addressed in Rack ATS Firmware g2ats v3.7.0 and higher. If you are unable to update to v3.7.0 or higher from https://www.apc.com/tools/download/index.cfm, a warmstart of the Network Management Card Interface is required to re-establish communication. This can be accomplished by pushing the "Reset" button on the front of the ATS or issuing the Reboot Management Interface from the Network Management Card UI (web, telnet/SSH, or local console). This action does not disrupt power output of the ATS and only reboots the Management Interface.


 

Information Controller v 1.x Upgrade Procedure

"APC Information Controller Firmware Upgrade Procedure

1. Download the psx1_3_5.tar file from APC web site to a folder on the local client.

2. Log on to the Information Controller using the administrative Username and Password values, and click Connect.

3. Select Network in the navigation bar.

4. Select the FTP tab to make sure that FTP Access is enabled.

5. Use FTP to import the psx1_3_5.tar file to the Information Controller from the client.

a. At a command prompt, use the cd command to navigate to the directory that contains the psx1_3_5.tar file.
b. Type ftp and the IP address used to log on to the Information Controller in step 2, and press ENTER.
c. At the User prompt, type the Information Controller’s FTP username (the default is lowercase apc)and press ENTER
d. At the Password prompt, type the Information Controller’s FTP password (the default is lowercase apc) and press ENTER.
e. At the ftp> prompt, type bin (or binary) and press ENTER.
f. At the next ftp> prompt, type send psx1_3_5.tar and press ENTER.
g. At the next ftp> prompt, type bye and press ENTER to exit FTP.

6. Select ""System"" in the navigation bar of the Information Controller.

7. Select the ""Tools"" tab and click ""Update Software"". Highlight the 1.3.5 upgrade file and click the ""update"" button to install the psx1_3_5.tar update at the Information Controller.

8. After the Information Controller reboots at the end of the update, log back on to the Information Controller to confirm the update was successful by clicking on ""Help"" and then the ""About"" tab."

Communication loss in the System Manager Software (error 513) for device(s) downstream of a CM4 with an ECC21 card

Goals and Symptoms

Issue
Communications will drop out for devices on the serial port of an ECC card housed in a CM3/4 and come back on the next health check, data upload, or with a communication test (i.e. there is no loss of data). The error with the communication loss is 513 which is defined as"negative acknowledgement"

Causes and Fixes

Cause

This is is generally a wiring issue where someone will have to "ring out" or check the wiring on the daisy chain for continuity; however the problem may be solved by cycling power to the ECC21. An easy way to cycle power to the ECC21 is to do a soft reset to the meter.

Resolution

Perform a soft rest on the meter by enabling an unused data log on the CM3/4. Whenever a change is made to a data log the CM4 reset itself which, in turn, reboots the ECC card. After the initial soft reset, the unused data log can be un-enabled to return the data log to its original state (this will cause another soft reset).

Alternately, a soft reset can be initiated by writing 1110 to register 8000.

NOTE: Since making any changes to a data log clears the data in all of the logs for that meter; do an "execute now" on any tasks that get data from the data logs in the meter before making the changes to the unused data log.


Legacy KB System (APS) Data: RESL210238 V1.0, Originally authored by MaTh on 01/07/2013, Last Edited by MaTh on 01/07/2013
Related ranges: ECC21

UPS Sync Control option in the UPS Network Management Card


Issue

Understanding the Sync Control in the UPS Network Management Card


Product Line
 
  • UPS Network Management Card 1 (NMC1) - AP9617, AP9618, AP9619
 
  • UPS Network Management Card 2 (NMC2) - AP9630/AP9630CH, AP9631/AP9631CH



Environment
 
  • Redundant UPS Scenarios
  • Sync Control Users
  • PowerChute Network Shutdown Users


Cause

This article outlines the functionality and caveats of UPS sync control.


Resolution

The UPS Sync Control option allows you to have two or more UPS units with their output synced up with one another. In this scenario, you can remotely turn off or reboot one UPS and it will turn off/reboot other UPS units in the same sync group. This option is primarily used in cases where you have either a server or switch that has redundant power supplies. You will need one UPS per power supply. If one UPS were to become unavailable, then the other UPS will support the other power supply. Lastly, bypass is NOT a supported control option.


However, if the you need to reboot the server/switch, you need to ensure that all power supplies are being rebooted. In this case, the sync group allows the user to reboot one UPS, which in turn, reboots all that are part of the sync group. A problem that could occur is that if you had two UPS units that are part of the same sync group and are the two UPS' being monitored through PowerChute Network Shutdown. If you were to turn off/reboot one of the UPS units, the other would turn off/reboot as well. When this happens, the server would turn off/reboot as well.


This is why we don't advise enabling sync control when using PowerChute Network Shutdown without making sure you configure it for a multiple UPS scenario/configuration.

Security Notification - Petya Ransomware Attack

Overview

Starting June 27th, a new variant of the Petya ransomware, also known as Petrwrap, Not Petya and exPetr, spread internationally to several businesses. Ukraine, Russia and Western Europe were among those that needed to go offline. More than 2,000 attacks took place with the help of the Windows SMBv1 vulnerability that the WannaCry ransomware attacks utilized. Unlike WannaCry, Petya does not encrypt files one by oone on a targeted machine or system. Instead, Petya reboots the victim's machine and encrypts the hard drive's master file table (MFT). The master boot record (MBR) is rendered inoperable therefore, restricting access to the full system by seizing information on file names, sizes, and location on the physical disk. Petya replaces the computer's MBR with its own malicious code that displays the ransom note and leaves computers unable to boot. Researchers at Symantec say they have confirmed the ransomware is using the Eternal Blue exploit. The malwares capabilities include the following: network surveying, password extraction, and file decryption.

Products Affected

Schneider is currently assessing impact.

Recommended Mitigations

Schneider Electric recommends customers with supported systems check with their designated supoort portals first before executing the following to prevent this attack:
  • Immediately apply the Microsoft patch for the MS17-010 SMB vulnerability:
    https://technet.microsoft.com/en-us/library/security/ms17-010.aspx?utm_campaign=Customer%20Advisory%3A%20Ransomware%20%26%20NSA&utm_source=hs_email&utm_medium=email&utm_content=51891072&_hsenc=p2ANqtz-_NvE2mLBDpHPM291B5t32lBa1Ymb4vsbyTDxRevQ2DoPbqW-1KlECy9-gEjL1kIZ4yifVn8I1IVX64iWT7x4vND3pgP614Sp6I1naq4esvOsuOZio&_hsmi=51891072
  • Based upon guidance from your product support team, you may want to consider disabling SMB v1 file-sharing protocol.
  • Ensure you have up-to-date backups. This alone is the most effective way to recover from a ransomware attack.
  • Enable strong spam filters to prevent phishing e-mails from reaching the end users and authenticate in-bound e-mail.
  • Configure access controls including file, directory, and network share permissions with least privilege in mind.
  • Inform and educate your employees to identify scams, malicious links, and social engineering attempts.
For More Information

Ensure all other cyber-defenses are up-to-date. If you are unclear then seek engagement with the Industrial Cybersecurity Services team: https://www.schneider-electric.com/b2b/en/services/field-services/industrial-automation/industrial-cybersecurity/industrial-cybersecurity.jsp

To obtain full details on the issues and assistance on how to protect your installation, please contact your local Schneider Electric representative. These organizations will be fully awate of the situation and can support you through the process. 

For further information on vulnerabilities in Schneider Electric's products, please visit Schneider Electric's cybersecurity web page at https://www.schneider-electric.com/b2b/en/support/cybersecurity/overview.jsp
Show More