// archive·fortigate

FORTIGATE .

────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

#01

2018.02.16

4 min

Fortigate

FORTIGATE NOTLARı

Yazının ilk kısmında okuyacağınız notlar Fortigate ‘te yaşanmış sorunları çözüme kavuşturmak için kullanılmış ve söz uçar yazı kalır kıstasınca vaktiyle bir text dosyasına kaydedilmiş notlardır. İkinci kısmında performans açısından tavsiye edilen uygulamaları (best practices) okuyabilirsiniz. 1.…

:: Fortigate :: Fortinet :: FortiOS [ Read Protocol > ]

#02

2018.01.19

2 min

Fortigate

“FORTIGATE HAS REACHED SYSTEM CONNECTıON LıMıT FOR # SECONDS” HATASı

“Fortigate has reached system connection limit for # seconds” veya “The system has entered conserve mode” hatalarına karşı nasıl iyileştirme yapılabilir? Fortigate yavaşlık Öncelikle Fortigate web arayüzünde Fortiview’dan beklenmedik sayıda session yapan client olup olmadığını kontrol…

:: Conserve mode :: Firewall :: Fortigate :: fortigate yavaş [ Read Protocol > ]

················································································································································································································································································································································································································