NETWORK OPERATIONS

Network Maintenance, Monitoring and Support Service

We track the status of switches, routers and access points, port errors and capacity. We define configuration backups, the update schedule and the people who receive notifications in the maintenance plan.

Monitoring, backups and planned maintenance

We set up early warnings for links approaching capacity and rising port errors.

SERVICE SCOPE / 01

Operating the network after installation

Network maintenance isn’t just firmware updates. Configuration backups, monitoring thresholds, secure management access, inventory and change records are managed together.

01

Visibility

SNMP, syslog and event logs

02

Health

Device, port and uplink status

03

Change

Versioned configuration backups

04

Planning

Capacity, EoL/EoS and maintenance calendar

MONITORING / 02

What do we monitor?

The monitoring server polls devices regularly with SNMP. Depending on configuration, devices can send SNMP notifications and syslog messages. We use SNMPv3 where the device supports it; in SNMPv2c the community string is carried in clear text on the network. In SNMPv3 the security level, user, MIB view and monitored counters are defined separately; changing the version doesn’t by itself provide more data. If user and security events are to be correlated alongside port and device monitoring, consider the scope of SIEM setup and security logs.

Reachability

Devices and links are monitored with their dependencies; when the core switch goes down, a separate alert isn’t raised for every device behind it.

Capacity

Threshold breaches on uplinks and internet lines raise warnings; long-term graphs feed into capacity planning.

Health

CPU, memory, temperature, fans, power supplies and the PoE budget are tracked.

Errors

Increases in interface error and discard counters can point to a cable, module or queue problem.

ENGINEERING APPROACH / 03

Give operations a measurable routine

Monitoring, backups, updates and reporting run under one scope. Work that carries an outage risk is done in an announced maintenance window: a backup is taken first, rollback steps are prepared, then the change is applied.

01

Monitoring baseline

Device reachability, interface errors, bandwidth use and alert thresholds are defined.

02

Planned maintenance

Firmware compliance, backups, certificate/license expiry dates and maintenance windows are tracked.

03

Reporting

Recurring incidents, capacity trends and recommended improvements are shared periodically.

SCHEDULED MAINTENANCE / 04

Scheduled checks

The table below is an example maintenance plan. We set the schedule together based on the size of the network and how critical it is to your business.

FrequencyCheckPurpose
ContinuousReachability, utilization, error counters, event logsDetecting loss of access according to the monitoring interval and alert rules
DailyConfiguration backup and change comparisonCatching unauthorized or faulty changes
MonthlySecurity bulletins, software versions, capacity trendsPlanned updates and improvements
QuarterlyBackup link and line failover tests, user and permission reviewVerifying that redundancy really works
YearlySupport end dates (EoL/EoS), warranties, topology and documentation updatesBudget and renewal plan
CONCRETE DELIVERABLES / 05

What will you have with maintenance and monitoring?

A device inventory, configuration backups, monitoring thresholds and periodic maintenance reports.

A documented, verifiable result

01

Current network inventory and monitoring scope

02

Configuration backup routine

03

Periodic health and risk report

04

Incident and change records

FREQUENTLY ASKED QUESTIONS / 06

Let’s clarify a detail

If your question is specific to your network, write to us; we’ll look at the current setup and give you a clear answer.

01

Once a monitoring system is set up, is maintenance unnecessary?

No. Monitoring makes problems visible; maintenance is the process that fixes them, reduces risk and keeps configuration discipline.

02

Do we need a separate device installed on our network for monitoring?

Usually a monitoring server or virtual machine running on the internal network is enough. The monitoring server polls devices with SNMP. Depending on configuration, devices can send SNMP notifications and syslog messages. The extra traffic depends on the number of monitored devices and the polling frequency.

03

Who receives alerts, and how?

They are sent by email or message to designated people according to severity. After-hours notification, first response and intervention scope are set by the contract terms.

04

Can you use our existing monitoring system?

Yes. If the existing system is adequate, we continue by adjusting thresholds, dependencies and reports; moving to a new system isn’t mandatory.

ERETEK NETWORK

Let’s monitor your network continuously and maintain it regularly

Share your device count and sites; let’s work out the monitoring scope and maintenance calendar together.