-
Title
Setting MTU on Replica Produces an error in TPAM 2.5.919 -
Description
When connected to the /config interface and attempting to set the MTU on a replica, an error will be displayed:
"at Quest.Core.Network.NetworkConfiguration.ParseIpv4Address(String addr) in c:\hudson\workspace\paa-console-919-installers-mor\console\src\Core\Network\NetworkConfiguration.cs:line 368 at Quest.Core.Network.NetworkConfiguration.SetInterfaceConfig(InterfaceDetail interfaceDetail) in c:\hudson\workspace\paa-console-919-installers-mor\console\src\Core\Network\NetworkConfiguration.cs:line 118 at Quest.Core.Network.NetworkConfiguration.SetInterfaceConfig(InterfaceDetail interfaceDetail, Boolean force) in c:\hudson\workspace\paa-console-919-installers-mor\console\src\Core\Network\NetworkConfiguration.cs:line 171 at Quest.WebServices.ServiceHosts.SysAdminService.SetInterface(InterfaceDetail detail) in c:\hudson\workspace\paa-console-919-installers-mor\console\src\WebServices\ServiceHosts\SysAdminService.cs...). Set ip to 192.168.1.1, Subnet to 255.255.255.0 40, Gateway to 192.168.1.11280, MTU Size to 1500 (result 65280) Network Settings Change Failed Parameter name: addr Parameter name: addr (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: Quest.WebServices.Contracts.ArgumentFaultException: Invalid IPv4 Address (format). System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Invalid IPv4 Address (format)."
-
Cause
The page appears to be append the expected MTU (1280 in this example) to the IP Address (192.168.1.1) -
Resolution
WORKAROUND: On 2.5.919, if the Replica is force failed over, it is then possible to configure the MTU.
RESOLUTION: This was addressed in TPAM 2.5.920; via BFER #10055. From the 2.5.920 Release Notes under the "Resolved Issue" section:
"Receive an error when trying to edit the MTU size on a replica."
-
Change Request
10055