User Tools
Writing /app/www/public/data/meta/development/applications/polaris/pushconfiguration.meta failed
development:applications:polaris:pushconfiguration
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| development:applications:polaris:pushconfiguration [2018/05/04 14:55] – ashevyakov | development:applications:polaris:pushconfiguration [2021/06/25 10:09] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ===== PUSH SnmpManager Configuration ===== | ||
| + | Note: PUSH and PUT terms are used interchangeably and mean the exact same thing. | ||
| + | |||
| + | ==== General ==== | ||
| + | Polaris equipment room data flatfile is generated **EVERY_TEN_MINUTES** using the **GeneratedFile** domain for the generation process and **RemoteFile** domain for actually putting the files to the remote server (ATC FTP, refer to the **PwSafe** for details). | ||
| + | \\ | ||
| + | \\ | ||
| + | Only the equipment room data ("Main Equipment Room") is transferred. The flatfile is of the same format as the [[https:// | ||
| + | \\ | ||
| + | \\ | ||
| + | The generated equipment room data flatfile is transferred to the specified location (ATC FTP server, root directory) daily at 01:00 EST. | ||
| + | \\ | ||
| + | \\ | ||
| + | Generated file format: **Errigal_Equipment__< | ||
| + | \\ | ||
| + | \\ | ||
| + | All the PUSH attempts are recorded via the **GeneralDiscoverySyncHistory** domain with the **jobType** being **REMOTE_FILE_REQUEST** (the **targetAddress** field will also say that the remote file interaction was **PUT**). | ||
| + | |||
| + | ==== Current Configuration (ATC Production) ==== | ||
| + | === Generated File === | ||
| + | {{: | ||
| + | === Remote File === | ||
| + | {{: | ||
| + | |||
| + | ==== Data Model ==== | ||
| + | |||
| + | === RemoteFile === | ||
| + | {{: | ||
| + | |||
| + | === RemoteFileTransferType (Enum) === | ||
| + | {{: | ||
| + | |||
| + | ==== Troubleshooting ==== | ||
| + | * Verify that the remote file is assigned to the correct **RemoteFileHost** entry and that its details are correct | ||
| + | * Verify that the remote file transfer type is PUT | ||
| + | * Verify that the remote file is active | ||
| + | * Verify that the generated file is active | ||
| + | * Verify that the remote file transfer destination directory is correct and pointing to an existing location on the remote server | ||
| + | |||
Page Tools
