Make sure you are not using an incorrect backplane interface ID number. When trying to add a new node to a cluster, you receive rrror "Invalid interface name/number".
When the Content Switch receives HTTP invalid/corrupt header next packets from the same source IP the client may be redirected to an incorrect destination. Once the server was mapped to a Load Balanced Virtual Server the document was editable through the local machine.Ĭontent Switching Virtual Server sends traffic to the wrong Load Balancing Virtual Server, resulting in users receiving 404 HTTP responses.Įnable "Drop Invalid HTTP Headers" on NetScaler.
When editing a document through the local machine you receive error "Cannot open a file, incorrect syntax or file path".Ī WireShark trace shows that the client was sending a request to a server not configured on any of the Content Switching policies. Move the affected NICs in to different VLANs or else aggregate the interfaces in to a link aggregated channel.
When more than one interface is in the same vLAN, you observe MAC moves and MAC conflicts between the NICs. In the Persistency Table, you can only see one backend server connection mapped to the source client however when running command "show ns connection table" you can see connections from the source client to multiple backend servers. Applicable Product Versions Affected (if known)
0 kommentar(er)
