Junos-eznc

Restrictions

Primary Routing Engine

For devices with multiple Routing Engines, you can only connect to the primary Routing Engine. If you attempt to connect to the backup Routing Engine, the Device.open() method fails with an exception.

Junos OS Software Upgrade

The primary restriction is on software-install functionality provided by the jnpr.junos.utils.sw module. The software-install process is currently designed to support simple deployment scenarios. The expected use case for this software is deploying new equipment. The following scenarios are supported:
- Standalone devices with a single Routing Engine, for example EX4200 switches
- Standalone devices equipped with dual Routing Engines, for example MX960 routers
- EX Series Virtual Chassis in non-mixed-mode configurations (all devices use the same Junos OS software package)
- Deployment configurations that do not have any form of "in-service" features enabled, such as unified ISSU and NSSU.

The following scenarios are known not to be supported:
- SRX Series chassis clusters
- EX Series Virtual Chassis in mixed-mode configurations (devices use different Junos OS software packages)
- Virtual Chassis Fabric (VCF)
- MX Series Virtual Chassis
- Any deployments with "in-service" configurations enabled (such as unified ISSU or NSSU)

Enhancements done

* Introduced bind_addr parameter in Device() API 1279
* Introduced vmhost paramater in dev.facts 1333
* Introduced hostkey_verify paramater in Device() API 1321
* Updated Docker file to use the latest Alpine 1316

Bugs Fixed
* Fixed the missing key to EthernetSwitchingTable 1228
* Fixed error handling on HelloHandler 1339
* Fixed the version check 1338
* Removed Google and Stackflow link from the ReadME 1337
* Fixed SystemStorageTable tables and views to handles multiple routing-engine file system storage information.1244
* Fixed Console' object has no attribute '_use_filter' error when executed Table/View script 1335
* Fixed cli function to get full RPC response 1315
* Fixed sw.install to set no_validate option when validate=False for NSSU and ISSU upgrade 1323
* Fixed UT framework mock to use built-in unittest.mock 1311
* Fixed specific VC member reboot handling 1308 1310
* Supported latest paramiko version which supports aes128-gcm and aes256-gcm cipher

Enhancements done

- Added customer juniper paramiko module as a dependency which supported aes128 and aes257 cipher 1299

Enhancements done
* Support added for Python 3.10 and above version.

Enhancements done
* Introduced optional argument routing instance for fs.cp() API
* Introduced optional argument member_id for installation of pkg on specific member id of EX-VC

Bugs Fixed
* Changed the VlanTable field name to vlan-name and BfdSessionTable field name to client-name 423
* Fixed the port details in StartShell to use the port from Device object instead of default Port 22 573
* Fixed the sw.install to use Windows file path for package copy 1206
* Fixed the sw.install to install the vc_master after the other vc_members gets installed for EX-3400 where unlink is set by default 1247
* Removed Unused Dependency: Netaddr 1257
* Fixed "object": version_info(re_version) emits ValueError: invalid literal for int() with base 10: '17-EVO' for EVO version X50.17-EVO1264

Enhancements done
* Supported option to set look_for_keys with bool True/False 1234

Bugs Fixed
* Fixed build failure against setuptools 1231