New pages
From Notes_Wiki
(newest | oldest) View (newer 50 | older 50) (20 | 50 | 100 | 250 | 500)
- 06:53, 7 January 2026 Step-by-Step Firmware Upgrade Procedure for Managed Network Switches (Including TP-Link Switches as example) (hist | edit) [6,292 bytes] Jamshad (talk | contribs) (Created page with "'''Purpose''' This document outlines a standardized procedure for performing firmware upgrades on managed network switches. The procedure is designed to minimize impact on network operations and includes detailed steps for pre-upgrade assessment, configuration backup, firmware upgrade execution, and post-upgrade validation. Additionally, this document provides a vendor-specific example illustrating the upgrade process for TP-Link managed switches. ==Scope== This procedu...")
- 09:59, 3 January 2026 Operational Guide for Per-Policy Bandwidth and Traffic Consumption Analysis on Palo Alto Firewalls (hist | edit) [4,494 bytes] Kalyan (talk | contribs) (Created page with "= Operational Guide for Per-Policy Bandwidth and Traffic Consumption Analysis on Palo Alto Firewalls = == Purpose == This Knowledge Base explains how to generate and analyze bandwidth usage and per–security policy data consumption on Palo Alto Firewalls. It is useful for tracking traffic related to specific internal servers, applications, or dedicated traffic flows by leveraging ACC → Network Activity and Traffic Logs. == Scope == This KB covers: * Generating bandw...")
- 08:26, 3 January 2026 Configuring SSL VPN User with Full Internal Network Access on FortiGate Firewall (hist | edit) [3,469 bytes] Jamshad (talk | contribs) (Created page with "'''Purpose''' This article explains how to configure an SSL VPN user with full access to internal networks on a FortiGate firewall. It covers SSL VPN user creation, tunnel configuration, firewall policy setup, validation, and best practices. '''Scope''' * SSL VPN user creation * SSL VPN tunnel configuration * Internal network access using split-tunnel or full-tunnel * Firewall policy configuration * Validation and best practices Home > Enterprise secu...")
- 07:36, 31 December 2025 Configuring Alerts for a Particular Host Group (hist | edit) [2,730 bytes] Kamal (talk | contribs) (Created page with " Home > Zabbix > Configuring Alerts for a Particular Host Group")
- 07:35, 31 December 2025 Zabbix (hist | edit) [86 bytes] Kamal (talk | contribs) (Created page with " Home > Zabbix *Configuring Alerts for a Particular Host Group")
- 07:28, 29 December 2025 PBS pbs sched Startup Fix After Reboot (hist | edit) [3,036 bytes] Akshay (talk | contribs) (Created page with "Home > CentOS > CentOS 7.x > CentOS 7.x Rocks cluster 7.0 > CentOS 7.x Rocks Cluster OpenPBS pbs_sched Startup Fix After Reboot == CentOS 7.x Rocks Cluster OpenPBS pbs_sched Startup Fix After Reboot == '''Background:''' As per the Rocks cluster architecture, the master node has two hostnames: * A '''public hostname''' * A '''private hostname''' In OpenPBS, all scheduler and node communication happens strictly through hostnames. OpenPBS...") originally created as "CentOS 7.x Rocks Cluster OpenPBS pbs sched Startup Fix After Reboot"
- 06:05, 29 December 2025 CentOS 8.x Control Web panel Increase CSF Process Tracking User Memory Limit (hist | edit) [1,113 bytes] Akshay (talk | contribs) (Created page with "Home > CentOS > CentOS 8.x > Email servers > Control Web panel > CentOS 8.x Control Web panel Increase CSF Process Tracking User Memory Limit == Increase CSF Process Tracking User Memory Limit == '''Purpose:''' To prevent CSF from triggering alerts or killing user processes due to low memory limits, the Process Tracking user memory limit needs to be increased. '''Steps:''' 1. Edit...")
- 10:29, 26 December 2025 Steps to Quarantine an Infected Host (hist | edit) [1,975 bytes] Rohith (talk | contribs) (Created page with " = CrowdStrike – Steps to Quarantine an Infected Host = == Purpose == To quarantine (network contain) an infected host using the CrowdStrike Admin Console and to lift the containment after remediation. == Prerequisites == * Access to CrowdStrike Admin Console * Hostname of the infected system == Steps to Quarantine an Infected Host == === Step 1: Login === * Login to the CrowdStrike Admin Console. === Step 2: Identify the Host === * Navigate to: → Host Setup...")
- 10:14, 26 December 2025 CrowdStrike (hist | edit) [82 bytes] Rohith (talk | contribs) (Created page with "= CrowdStrike – Steps to Quarantine an Infected Host = == Purpose == To quarantine (network contain) an infected host using the CrowdStrike Admin Console and to lift the containment after remediation. == Prerequisites == * Access to CrowdStrike Admin Console * Hostname of the infected system == Steps to Quarantine an Infected Host == === Step 1: Login === * Login to the CrowdStrike Admin Console. === Step 2: Identify the Host === * Navigate to: → Host Setup...")
