About components

Overview

WildcoreDMS functionality is made of components — modules that can be enabled and disabled as needed. A component adds pages and buttons to the web interface, role permissions, background tasks, console commands and API methods. If a component is disabled, its pages, tabs and buttons are not shown.

Which component provides which functionality

Working with hardware

Component	Key	What it provides
OLTs	olts	OLT page: ONU tree, physical and PON ports, ONU page, DHCP Snooping, ONU blacklist, background OLT polling
OLTs control	olts_control	ONU actions (reboot, disable, delete, reset, description), UNI and physical port control
Switches	switches	Switch page: ports, VLANs, errors, FDB, cable and SFP diagnostics, port page
Switches control	switches_control	Reboot, save configuration, clear counters, port state/speed/description
Routers	routers	L3 hardware: ARP, FDB, direct routes
Mikrotik RouterOS	router_os	Mikrotik routers via API: interfaces, DHCP, ARP, queues, BGP
Sensors	sensor_devices	Monitoring devices (sensors) and their mode control
Pinger	pinger	ICMP availability monitoring, ICMP devices, availability percentage, outage log
Charts	prometheus_wrapper	Traffic, error, signal, CPU/RAM charts from history
Live traffic	live_traffic	Real-time port/ONU traffic chart
FDB history	fdb_history	MAC address history on ports and ONUs
Web console	console	Browser terminal to hardware with auto-login and session log
Macros	macros	Custom console command scenarios with parameters
ONT registration	onts_registration	Unregistered ONUs and template-based registration
Config backups	oxidized	Hardware configuration backups with change history
SNMP traps	trapservice	Receiving SNMP traps — instant reaction to port/ONU state changes

Network and topology

Component	Key	What it provides
Links	links	Links between devices, topology (tree, graph), routes on the map
Autotopology	auto_topology	Automatic link building via LLDP/FDB
Autodiscovery	autodiscovery	Finding new devices in the network and adding them automatically

Events, analytics, notifications

Component	Key	What it provides
Events	events	Rule-based events (device/port down, errors, signal)
Notifications	notifications	Sending events and actions to Telegram and Email
Analytics	analytics	Network reports: statuses, signals, duplicate MACs/ONUs, growing errors — see Features

Integrations and API

Component	Key	What it provides
MikBill	mikbill_integration	Subscriber sync, billing data on the port/ONU page
NoDeny Plus	nodeny_plus	NoDeny Plus billing integration
Userside	userside_integration	Device and coordinate sync with Userside
Diagnostic	diagnostic	Subscriber diagnostics API for billing (JSON/HTML card), ARP ping
Search devices	search_device	API to find a subscriber by MAC/IP (FDB, ARP)

Tools

Component	Key	What it provides
Attachments	attachments	Photos and documents for devices, ports, ONUs
QR code Generator	qr-generator	QR labels linking to the object page

Dependencies

Control components (olts_control, switches_control) work only together with the base ones (olts, switches). Dependency list — wca component:dependencies.

Managing components

In the web interface

Configuration > System configuration → "Components" tab: the component list with state, install, enable and disable buttons. Component settings are there too (see System configuration).

In the console

sudo wca component:list                               # components and their state
sudo wca component:control <key> install              # install
sudo wca component:control <key> enable               # enable
sudo wca component:control <key> disable              # disable
sudo wca component:dependencies                       # dependencies

Note

Third-party integration components are disabled by default — enable the ones you need after configuring connection parameters.

What a component can do

• add pages, tabs, cards and buttons to the web interface;
• add role permissions;
• add API methods;
• add console commands (prefixed with the component key, e.g. olts:);
• add scheduler tasks and system event handlers;
• have its own parameters in System configuration.