Solved

Analytic Telemetry With Different VR

  • 2 April 2019
  • 2 replies
  • 349 views

Userlevel 5
Hi,

Currently have a network where the switches have been configured with IP's that are in different VRF's other than VR-Default, or VR-Mgmt.

In terms of doing backups and upgrades I have adjusted the script that allows the change in VR.

The issue I have is running the Telemetry Script in Analytics. It doesn't seem to include any VR in its script or an option that I can see that allows you to change it:



code:
Die command issued: Script failed : * Slot-1 SthHse-Core2.16 # tftp get 10.1.0.83 telemetry.pol telemetry.pol force-overwrite
Error: Could not connect with tftp server at 10.1.0.83


The script therefor fails because it can not TFTP the telemetry.pol file. Although I could manually transfer this there are some additional configuration that is added with reference to a VRF:

https://gtacknowledge.extremenetworks.com/articles/How_To/Application-Telemetry-Debug

The answer might be the configuration and transfer has to be done manually, but if something can be adjusted in XMC it would be good to know.

Thanks in advance.
icon

Best answer by Martin Flammia 22 May 2019, 12:37

Did this manually in the end.

I still run thought the process in XMC, Analytics to push the configuration to the switches that failed but this action might have created the policy files you will need in the XMC /TFTP folder.

Those 2 files will be:

  • telemetry.pol
  • telemetryegress.pol
Download these files to the switch using tftp get, and then run the following configuration:

code:
configure access-list telemetry any ingress
configure access-list telemetryegress any egress
create mirror "EAN"
configure mirror EAN to remote-ip 10.1.0.81 vr VR-admin from 10.255.255.2
enable mirror "EAN"
configure sflow collector 10.1.0.81 port 6343 vr "VR-Admin"
configure sflow sample-rate 1024
configure sflow poll-interval 60
configure sflow ports 1:1-72,2:1-72 sample-rate 1024
enable sflow ports 1:1-72,2:1-72 ingress
enable sflow


So far that seems to have worked well, and hopefully useful to someone else.

Thanks,
View original

2 replies

Userlevel 5
Did this manually in the end.

I still run thought the process in XMC, Analytics to push the configuration to the switches that failed but this action might have created the policy files you will need in the XMC /TFTP folder.

Those 2 files will be:

  • telemetry.pol
  • telemetryegress.pol
Download these files to the switch using tftp get, and then run the following configuration:

code:
configure access-list telemetry any ingress
configure access-list telemetryegress any egress
create mirror "EAN"
configure mirror EAN to remote-ip 10.1.0.81 vr VR-admin from 10.255.255.2
enable mirror "EAN"
configure sflow collector 10.1.0.81 port 6343 vr "VR-Admin"
configure sflow sample-rate 1024
configure sflow poll-interval 60
configure sflow ports 1:1-72,2:1-72 sample-rate 1024
enable sflow ports 1:1-72,2:1-72 ingress
enable sflow


So far that seems to have worked well, and hopefully useful to someone else.

Thanks,
Should be fixed in XMC/Analytics Version 8.2.4.55:

"Adding an ExtremeXOS device to ExtremeAnalytics as an Application Telemetry Source was not supported when the host IP was applied to an engine other than the VR-Default."

Reply