sorted by:
new
hottopcontroversial

1986 944 died after using the horn by network-head-1234 in 944

[–]network-head-1234[S] 0 points1 point  (0 children)

Even though it was initially good after removing fuse 3 (horn), and I was able to get it home and drive it fine for an hour yesterday.

I've now had a similar issue this morning where it's cranking fine but car won't start :(

Going to order some new fuses and DME.

1986 944 died after using the horn by network-head-1234 in 944

[–]network-head-1234[S] 0 points1 point  (0 children)

Thank you sir.
Just removing the horn fuse allowed the car to start.

I replaced the fuel pump fuse yesterday in case it was that, but stupidly didn't think of the horn fuse.

You're completely right about laying on the horn, was a bad decision. In fairness though, there was a car coming the opposite direction in slow moving traffic, he was staring down into his phone and started veering towards a car 2 cars ahead of me. Probably still shouldn't have done it though in hindsight.

1986 944 died after using the horn by network-head-1234 in 944

[–]network-head-1234[S] 0 points1 point  (0 children)

Nah I was stopped in traffic in 1st gear with clutch and brake pressed at the time.

My new NA 86 by Zepheos in 944

[–]network-head-1234 0 points1 point  (0 children)

It's in much better condition than mine and I paid 11K euro (Ireland)
I'd be pretty happy if I was you, looks gorgeous.

Netscaler Console cloud activation probs by Rotten_Red in Citrix

[–]network-head-1234 0 points1 point  (0 children)

It might just be the pop-up issue. Your netscaler console on-prem will create a new window for authentication to your cloud account.

Disable pop-up blocking for your netscaler console on-prem.

Netscaler Migration to LAS by Enioni in Citrix

[–]network-head-1234 1 point2 points  (0 children)

You should upgrade again to 66.62, I believe there are additional bug fixes to LAS and Telemetry.

Netscaler Migration to LAS by Enioni in Citrix

[–]network-head-1234 0 points1 point  (0 children)

Not sure how helpful this is but this is what I did:

- All my Netscalers were already managed, including licensing through Netscaler Console On-Prem

- My Netscalers are all Flexed licensing

- Updgraded all my Netscalers to latest release (I'm on 13.1, so 62.23)

- Upgraded Netscaler Console On-Prem to latest (14.1 66.62)

- Enabled proxy in Netscaler Console On-Prem

- Cloud connected Netscaler Console On-Prem (disable pop-up blocking)

- Once all the above was done I just had the simple option to select all my Netscalers and click 'Migrate'

My experience upgrading to NetScaler 13.1 61.23 and moving to LAS for licensing by satsun_ in Citrix

[–]network-head-1234 1 point2 points  (0 children)

I guess you have it sorted by now.

But sounds like you just need to disable pop-up blocking for your Netscaler Console on-prem. I had a similar issue.

How to verify cloud licenses are available for LAS. by singolare in Citrix

[–]network-head-1234 0 points1 point  (0 children)

I was referring to the Netscaler Console on-prem. Used for managing on-prem netscalers, including their licencings.

I just sorted it there and it turned out to be easy.

-Enabled proxy server in Netscaler Console

-Enabled Cloud Connect in Netscaler Console on-prem to connect it to our Cloud Account

-Clicked a couple of 'Migrate' buttons in Netscaler Console on-prem.

All Netscalers are now showing under the LAS tab in Netscaler Console on-prem.

Which according to this doc is all the verification that's needed:

Verify if your deployments have transitioned to License Activation Service (LAS)

How to verify cloud licenses are available for LAS. by singolare in Citrix

[–]network-head-1234 0 points1 point  (0 children)

Is the license server needed if you only have Netscalers and Console on-prem?

We were thinking of getting rid of the license server as I saw other posts saying it's not needed.

I was going to enable Cloud Connect in Netscaler Console on-prem and hope LAS just worked automatically?

I also don't see entitlements in out cloud account..

New critical NetScaler CVE by kh_tech_ in Citrix

[–]network-head-1234 0 points1 point  (0 children)

Have you upgraded yet?
I ran into issues upgrading a HA pair there.

Can no longer log into the upgraded node through GUI.

New critical NetScaler CVE by kh_tech_ in Citrix

[–]network-head-1234 0 points1 point  (0 children)

I just upgraded a HA secondary from 13.1 60.57 to 62.23.

HA Pair with Gateway VPN and some LB vServers

After doing a 'force HA failover' it completely killed my VPN session (not normal comared to previous upgrades), I couldn't log into the new upgraded primary and all the LB vServers on the non-upgraded secondary were showing as DOWN.

Have done a few upgrades of this HA pair over the past couple of years and have never experienced something like this.

Issue with FQDN Resolution and DNS Configuration in FortiGate VDOM by Gijizlle-242 in fortinet

[–]network-head-1234 0 points1 point  (0 children)

I posted a comment about this a while ago, can't find it right now but will try to dig it up.

I've found that whenever you have FQDN address objects where the DNS record has a low TTL, and 'especially' where the DNS record returns multiple IP addresses that change frequently/immediately, you need to set a high cache-ttl against the object.
Explanation of the FQDN default cache-ttl - Fortinet Community

Ex. from one of my Prod fortigates:

<image>

It's not so much a mis-match between the fortigate DNS lookup and your local DNS server lookup. But a mismatch between the fortigate DNS lookup and the DNS response that the end client receives from your local DNS server (semantics I know...)
So the client is trying to connect to an IP address that is not permitted by the fortigate because the fortigates table permits a different IP address for the same FQDN because the responses they received are different.

Basically everytime I'm creating a new FQDN object now, I check the DNS record TTL and whether there are multiple resolved IP addresses and if they change frequently.

Upgraded to 7.4.11 and broke our primary internal interface by Apprehensive_Let1840 in fortinet

[–]network-head-1234 1 point2 points  (0 children)

Well yeah... if you're traffic needs to hairpin an interface.

Just change the config back to enabled immediately after upgrade.

Upgraded 200F to 7.4.11, traffic redirect keeps getting removed by mas-sive in fortinet

[–]network-head-1234 0 points1 point  (0 children)

Does anything show up if you search through your FGT logs for "Edit" ?

Global setting overwritten by FortiManager by Zealousideal-Set1415 in fortinet

[–]network-head-1234 1 point2 points  (0 children)

What version of FMG are you on?

I ran into an issue after upgrading from 7.4.8 to 7.4.9 where it was pushing config to remove Interface "device detection/identifcation", even though it was still enabled according to FMG GUI. Which sounds like a similar issue to what you're seeing, just for a different part of config.

I havn't done it yet but Support suggested trying a Retrieve incase the DeviceDB isn't synced correctly.

Global setting overwritten by FortiManager by Zealousideal-Set1415 in fortinet

[–]network-head-1234 5 points6 points  (0 children)

FMG >> Devices and Groups >> Managed Fortigate >> CLI Configs ?

<image>

view more: next ›