How to add a new MAC Vendor to macvendor table
To insert mac value in macvendor table:
insert into system.macvendor(prefix, vendor,hi, lo) values ('90:6C:AC','ARUBA NETWORKS', -1, -1);
Once done, import a macvendor pattern with expression set to ‘ARUBA NETWORKS’ (vendor name that you inserted with above sql) along with other profiling attributes.
<patterns xmlns="urn:lumeta:pattern:6.0" user-provided="true" version="184.108.40.20623">
Steps to take when discovery is not happening
Steps to take when one cannot login to the Spectre CC box
Steps to take when VM runs out of disk space
If your Spectre CC VM is running out of disk space, there are certain tables in the database that can be cleaned up to make more space. Please login to your CC as admin and run “support db” or login to your CC as root from console and run “db” (in both cases, you will be entering database mode). Then execute:
How to force deleting of a zone (when deleting a zone from GUI/CLI fails)
If for some reason, you cannot delete the zone via GUI or CLI (because it is timing out or resulting in an error), you will need to login to db and delete it
NOTE: In the above example, even though the zone id is 35, in hex it becomes 0023.
How to manually disable NTPD on Spectre boxes
Here are the manual steps to disable NTP for Spectre:
How to verify open ports for a device (similar to how Spectre verifies)
Command to check if port on a device is open. From command center
How to change Spectre’s hostname
If for some reason, the hostname under database and application filesystem is not in sync, then you will need to reboot the system.
In more depth, here's a bit more about the two names, how to see them, and how you might change them (these assume you're at a root shell prompt)
All these changes should occur automatically via the "system hostname" CLI command, but that's where you can look if that doesn't work out.
How to disable PKI from bash prompt
As root, run the command: /usr/local/lumeta/bin/observer_pki enable false
Steps to disable FIPS mode on Spectre 3.2.7 (and later) CC/Scout when it is configured with BGP with MD5
Steps to perform if Scout runs out of memory during upgrade
While Upgrading a Scout, if you see the error message "Out of memory!", please perform the following steps:
DO NOT REBOOT.
Via CLI continue with the upgrade.
You can monitor the upgrade if you have a second ssh session window. Cd/var/log..there will be an esi-update file; Tail -f /var/log/esi-update.log
If successful the Spectre system will reboot, and when it comes back online verify via CLI (system version spectre) or login in through the UI that the installation was successful