5751 - Need to restrict the managment of the appliance to a single IP address.
4313 - Virtual Traffic Manager does not allow Traffic IP Groups to be set up due to network interface name is longer than 15 characters
5384 - vADC Virtual Appliance has different Ethernet Ports: eth0 is e1000 and eth1 is VMXnet3
KB43614 - Cannot connect to Wifi networks when Pulse is installed on a system that uses Hyper-V virtual switch/adapters
KB22294 - [PCS] Unable to access Virtual desktops configured through the Virtual Desktop Resource Profile
KB43967 - Unavailability of Virtual Appliance images for Pulse Connect Secure-9.0R3.0 Software (Build 64003) and Pulse Policy Secure-9.0R3.0 Software (Build 51661)
5833 - When does the virtual Traffic Manager appliance (VA) rotate log files?
8800 - What is the recommended steps to upgrade a Stingray Traffic Manager Amazon EC2/AWS instance?
7654 - Is the virtual Traffic Manager FIPS 140-2 compliant?
6967 - How to disable certain cipher suites for virtual Traffic Manager?
What would you like to know?
< Back to search results
5758 - The MTU setting is disabled on the virtual Traffic Manager virtual appliance on Hyper-V under the System > Networking page.
Last Modified Date
11/27/2017 4:51 PM
This article describes an issue where the MTU setting is disabled for vTM on Hyper-V.
Problem or Goal
Currently, vTM only supports an MTU of 1500.
Was this article helpful?
Please tell us how we can make this article more useful.