The Pulse Services Director makes it easy to manage a fleet of virtual ADC services, with each application supported by dedicated vADC instances, such as Pulse Virtual Traffic Manager (Pulse vTM). In fact, Services Director can even support mixed versions of Pulse vTM, which means that some applications can be managed with an older version of Pulse vTM, while others with the very latest version of Pulse vTM.
|
Services Director
|
|
|
|
|
|
2.4
(EoS)
|
17.2
(LTS)
|
18.1
(EoS)
|
18.2
|
18.3
|
19.1
|
20.1
(LTS)
|
|
|
Traffic Manager
|
|
|
|
|
|
|
|
|
|
9.9 (EoS)
|
1
|
1
|
1
|
1
|
1
|
1
|
1
|
|
|
10.4 (EoS)
|
Y
|
1
|
1
|
1
|
1
|
1
|
1
|
|
|
17.2 (LTS)
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
|
|
18.2 (LTS)
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
|
|
18.3
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
|
|
19.1
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
|
|
19.2 (LTS)
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
|
|
19.3
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
|
|
20.1 (LTS)
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
|
|
20.2
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
Y
|
|
Limitations of feature support:
Although the table above indicates that most combinations are supported to some extent, some key capabilities are of course dependent on the respective versions of SD and of vTM. The capability must be available by both your installation of Services Director and the instance of vTM, in order to be fully functional.
For example, the capability for instances of vTM to “Self-Register” with Services Director is only supported in Services Director 2.4 and higher, and in vTM versions 10.4 and higher:
|
Example SD Capability
|
Available from which version
|
|
|
Services Director
|
vTM
|
|
vTM Cluster Awareness
|
2.3
|
10.3
|
|
vTM Instance Health
|
2.4
|
10.2
|
|
vTM Self Registration
|
2.4
|
10.4
|
|
vTM Backup/Restore
|
2.5 (note 2)
|
11.0
|
|
vTM Enterprise Management
|
18.1 (note 2)
|
18.1
|
|
vTM Traffic Analytics
|
18.1 (note 3)
|
17.2
|
|
SD/vTM Communications through NAT (note 4)
|
19.1
|
19.1
|
|
LDAPS/STARTTLS Admin Authentication (note 5)
|
20.1
|
20.1
|
Key to the Table
|
Y
|
This combination is fully compatible, supporting all capabilities which are supported in both of the corresponding versions of SD and vTM.
This should be interpreted that a given feature is compatible, if both the SD and vTM support that feature in the same way. It does not imply (for example) that an older version of SD will support all features in a newer version of vTM.
|
|
1
|
This combination is compatible, but some features are NOT fully supported, depending on the respective versions of SD and vTM.
|
|
2
|
From SD 18.3, Centralized Backup/Restore is enabled for each vTM instance managed by SD.
|
|
3
|
From SD 18.3, Traffic Analytics, Data Export and the Analytics Application requires an optional Analytics Feature Pack to be installed in SD.
|
|
4
|
From SD & vTM 19.1, An alternate communications channel is created between SD and all managed vTMs which provides improved monitoring in Kubernetes and NAT deployments.
|
|
5
|
From SD & vTM 20.1, LDAPS/STARTLS are recommended for admin authentication profiles.
|
|
EoS
|
This software version is no longer supported.
|
EOL/EOS Information
For complete information about EoL and EoS dates, see the support pages:
This data is correct at the time of last update - July 2020. , please contact your Pulse technical sales representative.
