Jump to content
Updated Privacy Statement

Jeff Riechers -GM

Members
  • Posts

    14
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Jeff Riechers -GM's Achievements

  1. Ok. Updating to the latest version of ADM and adding flex now properly shifts the view. However, if you are using application grouping you will want to license and assign all existing applications before applying the new licenses. At a customer site that heavily used groups we were unable to add existing items that now were licensed to groups. But new items could be. We since shifted to Regex presentation of applications to groups to make it work for now.
  2. That's not the issue. ADM is working fine for vpxes. The problem is there is no provided license to download with the new license models coming out on March 3rd. And all old ADM vserver licenses were scrubbed from the customer license portal. Will there be a new version of ADM that removes the vserver license need?
  3. I had a customer convert over to the new licensing model that is being released on March 3rd. We need to allocate the new licenses to the ADM as their Virtual Servers allocated licensing is expiring soon, but there is no legacy style license available. We applied the flex licensing but it did not increase the virtual server license count. Does this mean on-prem ADM is dead for analytics?
  4. Well, I think I found the issue. I had enabled Login Encryption on the image to harden the environment. Once I changed that back it worked correctly.
  5. So I have a special nfactor setup in my lab built with my terraform that provides a dropdown list of authentication methods for LDAP, Azure SAML, Google, Okta, etc. I was testing out setting up FAS and updated my netscaler to the latest 14.1 build when out of nowhere the nfactor dies after selecting your policy. So I rolled back to my snapshot beforehand, re-applied the same terraform code, and it is still broken. I created a manual nfactor flow with my schemas and policies and they also don't work. I am trying to get details on where the failure is taking place, but I can't find anything in the logs, or in the web code that gives me any direction. I have included a copy of the scrubbed config if that helps.
  6. So ran into this at a customer that we have been upgrading since 13.0. They are now up to the latest 14.1 firmware for all the new features it has. When going to the application dashboard we only see a select few applications that they have permissions too. It says like 1 of 4 applications, or 8 of 31. If you drill down you can see they have all the necessary permissions to them. But just can't get them on that heat map dashboard. Is there some setting we are missing? Or is this due to us upgrading from older firmware? I can get some scrubbed screenshots if it helps.
  7. I ran into an issue with a customer that was upgrading their 13.1 NetScalers from 49.15 to 50.23. When they did the upgrade any GSLB service that was created as ANY with a public port of 0 were deleted from the configuration. And attempting to recreate the service threw this error. ERROR: Integer value below minimum [publicPort, 1] Most of their GSLB services are tied to a single port, only the VIPs with TCP Any had the public port set to 0. Is this something new in the firmware, or possibly something that was incremented in the new release.
  8. We work with customers that have both and are looking to consolidate down to 1 solution since they both do the same thing. But since Citrix Gateway is only supported on NetScalers, we tend to recommend that solution. Also when it comes to configuration I tend to find the NetScalers much more intuitive, and the configuration language is easier for me to read, more similar to Cisco style configs. But yes support for Citrix is still hurting. Hopefully that gets turned around soon.
  9. Well, disregard. I hadn't put .63 in. Once I did that it was fine. Must have been something with .61.
  10. Well, disregard. I hadn't put .63 in. Once I did that it was fine. Must have been something with .61. So I setup Prometheus and Grafana for testing out metric collections. After updating firmware I no longer have data in Grafana. Going and checking the logs I see the output log file is empty, and in metricscollector.log file I see the following error start ERROR: Invalid schema file : /var/metrics_conf/schema.json: cannot open file Fri May 12 15:21:27 2023 start ERROR: Dynamic schema init failed for profile ns_analytics_time_series_profile Check if schema file and file_path is valid!! Fri May 12 15:21:27 2023 The schema file has not changed and looks fine.
  11. Is the F5 to NetScaler conversion tool still available? Is this a tool we as engineers could get access to for migrating F5s to NetScaler?
×
×
  • Create New...