White | Mounting Spacer Block 12mm 600 Series

The part for Optiline trunking 185 x 55, ISM1550.

Use PDL 100MPIR + PDL 600RM relay

Issue:
Netbotz and FTP Return Codes

Product Line:
NetBotz

Environment:

NetBotz FTP codes

Cause:
When configuring the FTP Alert Action on a Netbotz device, the FTP server may return error codes which may viewed in the Appliance Log. The return codes may be used to further troubleshoot the problem.

Resolution:

The return codes for FTP servers are:

110 Restart marker reply. In this case, the text is exact and not left to the particular implementation; it must read: MARK yyyy = mmmm where yyyy is User-process data stream marker, and mmmm server's equivalent marker (note the spaces between markers and "=").

120 Service ready in nnn minutes.

125 Data connection already open; transfer starting.

150 File status okay; about to open data connection.

200 Command okay.

202 Command not implemented, superfluous at this site.

211 System status, or system help reply.

212 Directory status.

213 File status.

214 Help message.On how to use the server or the meaning of a particular non-standard command. This reply is useful only to the human user.

215 NAME system type. WhereNAME is an official system name from the list in the Assigned Numbers document.

220 Service ready for new user.

221 Service closing control connection.

225 Data connection open; no transfer in progress.

226 Closing data connection. Requested file action successful (for example, file transfer or file abort).

227 Entering Passive Mode (h1,h2,h3,h4,p1,p2).

230 User logged in, proceed. Logged out if appropriate.

250 Requested file action okay, completed.

257 ""PATHNAME"" created.

331 User name okay, need password. 332 Need account for login.

350 Requested file action pending further information

421 Service not available, closing control connection. This may be a reply to any command if the service knows it must shut down.

425 Can't open data connection.

426 Connection closed; transfer aborted.

450 Requested file action not taken.

451 Requested action aborted. Local error in processing.

452 Requested action not taken. Insufficient storage space in system.File unavailable (e.g., file busy)

500 Syntax error, command unrecognized. This may include errors such as command line too long.
501 Syntax error in parameters or arguments.

502 Command not implemented.

503 Bad sequence of commands.

504 Command not implemented for that parameter.

530 Not logged in.

532 Need account for storing files.

550 Requested action not taken. File unavailable (e.g., file not found, no access). (550 a:: no such directory means no diskette in a: drive.)

551 Requested action aborted. Page type unknown.

552 Requested file action aborted. Exceeded storage allocation (for current directory or dataset). 553 Requested action not taken. File name not allowed.
 

Issue:
Captured clips shows duration and frame rate as per previous video capture settings on NetBotz 750 / 755

Product Line:
NetBotz 700 series

Environment:
Nebotz 5.2.3 firmware and prior
NBRK0750
NBWL0755
StruxureWare Data Center Expert

Cause:

This issue may be seen in StruxureWare Data Center Expert's surveillance data for the 700 series appliance with the issue.

Steps to recreate the issue:

1. Set both pre capture and post capture time to 30 seconds
2. Set frame rate/second to 30 seconds (Under camera settings)
3. Trigger an alarm with clip capture attached
4. Captured clip contains around 330 frames and duration 45 seconds
5. Resolve the alarm (Do not delete the alarm configuration)
6. Change both pre capture and post capture time to 2 seconds
7. Set frame rate/second to 2 seconds(Under camera settings)
8. Trigger an alarm with clip capture attached
9. Captured clip contains around 557 frames and duration 1 minute


Resolution:

1. Delete the alarm configurations in which clip capture option selected
2. Create a new alarm configuration with clip capture option selected
3. In the triggered alarm, Captured clip should now contain around 8 frames and duration 3 seconds.


This issue is slated to be fixed in BotzWare 5.3

Use the PDL 100MPIR + 600RM if required to switch higher loads