Page Comparison

mains logs to look for

tech-support-info.log >>> Events

statusMonitor.log

Code Block

title	stateMonitor.log
collapse	true

Total alarms for node: 4
Apr 24 10:27:50.653 [DATA| -- ] INFO  (stateMonit-ZKTT) Alarm new action: clear {{
  "node-name" : "node1",
  "resource" : "/t128:config/authority-config:authority/router[name='LAB-PAX5-128T-SPOKE-1']/peer[name='LAB-MAX2-128T-RTR-1']",
  "state-key-name" : "peerPathStatus",
  "category" : "peer",
  "interface-name" : "",
  "source" : "LAB-MAX2-128T-RTR-1+185.216.98.109+node1+wan0+0",
  "shelved-reason" : "",
  "creation-time" : "2023-04-24 10:27:44Z",
  "severity" : "major",
  "shelved-status" : "not-shelved",
  "message" : "Peer LAB-MAX2-128T-RTR-1 path is down (PeerName: LAB-MAX2-128T-RTR-1 | Destination: 185.216.98.109 | NodeName: node1 | DeviceName: wan0 | Vlan: 0)",
  "value" : "down"
}}

serviceArea.log packet drop in the service

highway.log

coredumpctl ???

automatedProvisioner.log can give you more granular details for onboarding

configDirector.log on both conductor and local to the router which can give more information for anything config related

all the logs

ls /var/log/128technology/

Code Block

title	logs

[t128@conductor ~]$ ls /var/log/128technology/ | egrep -v '[0-9].log' | egrep -v 'log.[1-9]'
accessManager.log
analyticsReporter.log
audit
auditdReceiver.log
automatedProvisioner.log
conflux.log
databaseQueryCoordinator.log
dnsManager.log
dynamicPeerUpdateManager.log
highwayPlatform.log
influx_clean.log
influx_configure.log
influxdb_http.log
influxdb.log
minionWatchdog.log
nodeMonitor.log
persistentDataManager.log
processes.log
processManager.log
saltEventPublisher.log
saltMaster.log
saltMasterProcess.log
secureCommunicationManager.log
securityKeyManager.log
snmpTrapAgent.log
stateMonitor.log
step
stepRepository.log
systemServicesCoordinator.log
tank_clean.log
tunnelProcesses.log
yin-and-friends.log
zookeeperServer.log

...

Versions Compared

Old Version 4

New Version Current

Key