404 errors seen in the gateway.log file on Virtual Network Assurance (VNA) for the Viptela Plugin:

Products

• CA Virtual Network Assurance

Issue/Introduction

404 errors seen in the gateway.log file on Virtual Network Assurance (VNA) for the Viptela Plugin:

Examples:

<DATE_TIME> ERROR Viptela_ftp=Inventory Poll [OC_SCRIPTING] ViptelaHttpBase 236  Failed to receive response for https://<IPADDRESS>:<PORT>/dataservice/client/token , status code = 404 , reason phrase = Not Found , body = ...

<DATE_TIME> ERROR Viptela_<UUID>=Notification Poll [OC_SCRIPTING] ViptelaHttpBase 236  Failed to receive response for https://<IPADDRESS>:<PORT>/dataservice/client/token , status code = 404 , reason phrase = Not Found , body = ...

<DATE_TIME> ERROR Viptela_<UUID>=Performance Poll [OC_SCRIPTING] ViptelaHttpBase 236  Failed to receive response for https://<IPADDRESS>:<PORT>/dataservice/client/token , status code = 404 , reason phrase = Not Found , body = ...

<DATE_TIME> ERROR Viptela_<UUID>=SLA Class Poll [OC_SCRIPTING] ViptelaHttpBase 236  Failed to receive response for https://<IPADDRESS>:<PORT>/dataservice/client/token , status code = 404 , reason phrase = Not Found , body = ...

<DATE_TIME> ERROR task-2)  [VIPTELA_PLUGIN] ViptelaHttpBase 236  Failed to receive response for https://<IPADDRESS>:<PORT>/dataservice/client/token , status code = 404 , reason phrase = Not Found , body = ...

Environment

Release : 3.7

Component : Virtual Network Assurance For CA Performance Management

Cause

This is the plugin checking to see if the version of Viptela needs the XSRF token.

 A 404 is expected if it’s not supported. 

 But the plugin should then continue and process the calls.

Resolution

This error is benign if you are on a revision of Viptela that does not support the XSRF token.