| 4-7 |
In the segment being monitored by SwiMon, there is a terminal whose IP address is displayed as "********" and is marked with a yellow diamond-shaped "?" symbol. |
4. Troubleshooting
|
| 4-8 |
When replacing a switch managed by SwiMon, if I use the same model and configure it with exactly the same settings, will it be ready to use immediately? |
4. Troubleshooting
|
| 4-11 |
What steps should I follow to completely delete the collected information (such as Manager logs and database data)? |
4. Troubleshooting
|
| 4-13 |
I configured the NetSkateKoban Sensor (appliance product) to use an NTP server, but time synchronization is not working. |
4. Troubleshooting
|
| 4-14 |
Even though I haven't interfered with communications, an entry appears in the Windows PC's ARP table with a "Physical Address" of "00-00-00-00-00-00" and a "Type" of "Invalid". |
4. Troubleshooting
|
| 4-15 |
I uninstalled NetSkateKoban Manager, but the "NetSkateKoban Manager" setting remains in Windows Services. |
4. Troubleshooting
|
| 4-16 |
Even if I enable the Sensor function for the NetSkateKoban Sensor (appliance product), the Sensor operation status in the "Monitoring Interface List" of the Koban Browser will still show as "Process Stopped". |
4. Troubleshooting
|
| 4-19 |
I installed the system using PostgreSQL, but when I try to launch the Manager, I get the error "Cannot pool a connection to the database" and it won't start. |
4. Troubleshooting
|
| 4-20 |
After installing an additional Ethernet interface card on the machine where the NetSkateKoban Manager is installed, I could no longer connect via the console. |
4. Troubleshooting
|
| 4-21 |
I installed the database server and NetSkateKoban Manager on the same Windows Server machine, but the NetSkateKoban Manager does not start even after configuring the services to start automatically. |
4. Troubleshooting
|
| 4-22 |
I manually stopped the communication interference targeting a specific terminal, but I am unable to communicate with other terminals. |
4. Troubleshooting
|
| 4-24 |
In segments monitored by NetSkateKoban Sensor, there are terminals that rarely appear on the map even though they are connected to the network. |
4. Troubleshooting
|
| 4-27 |
In environments using L3 switches, an unexpectedly large amount of terminal connection history data is recorded compared to the number of terminals being monitored. |
4. Troubleshooting
|
| 4-28 |
When attempting to display a graph from a web browser in "CpMonitor, NetSkateKoban for CATV", a message stating "Application blocked by security settings" appears, and the graph does not display. |
4. Troubleshooting
|
| 4-30 |
On network segments monitored by the NetSkateKoban Sensor, Windows machines configured with a static IP address may be unable to communicate upon startup. |
4. Troubleshooting
|
| 4-31 |
Why are intermediate locations displayed in red in the tree view of the Koban browser or the network map screen? |
4. Troubleshooting
|
| 4-32 |
Some Sensors show a "Host Unreachable" status, but I can ping them successfully and access their configuration screens via a web browser. What is causing this? |
4. Troubleshooting
|
| 4-33 |
The Koban Console seems to be running slowly, such as when launching or displaying information. Please tell me about situations where the Koban Console slows down. |
4. Troubleshooting
|