https://wiki.netyce.com/ 2026-04-25T19:53:25+00:00 https://wiki.netyce.com/ https://wiki.netyce.com/lib/exe/fetch.php?media=wiki:logo.png text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:vendors:supported_devices&rev=1720009873&do=diff Supported devices NetYCE Vendor modules Currently netYCE supports the following Vendors: Vendor Model OS version Protocol OS upgrades File transfer protocols Default protocol Limitations Command parsing Config parsing Cmpl config parsing Alcatel OmniSwitch text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:vendors:supported_transfer_protocols_per_device&rev=1720009873&do=diff Supported transfer protocols per vendor Vendor SFTP SCP FTP TFTP Reverse Fallback plain vrf plain vrf plain vrf plain vrf FTP cli show Alcatel OmniSwitch yes n/a yes n/a yes n/a text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:vendors:vendors&rev=1720009873&do=diff Vendors reference Vendors Main article Supported devices Transfer protocols Main article Supported transfer protocols per vendor Vendor questionnaire When building a NetYCE vendor-module the answers to this list of questions is needed. Main article Vendor Questionnaire State actions A configureable table controls the way each vendor module handles a specific task text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:vendors:vendor_questionaire&rev=1720009873&do=diff Vendor Questionnaire In order to build a new vendor module, we need to get a good overview of the device / vendor. Here are some basic questions and properties whose answers need to be provided: Protocols - telnet, ssh portnumbers - preferences Login text/html 2024-07-03T12:31:13+00:00 Anonymous (anonymous@undisclosed.example.com) https://wiki.netyce.com/doku.php?id=guides:reference:vendors:vendor_state_actions&rev=1720009873&do=diff Vendor State Actions Tasker When executing jobs to interact with the network, the job is first added to the scheduler which then launches the job at the appropriate time. This job is executed using the Tasker. Every job has a mandatory component called the