Background: During NCS' short life, a number of customers had problems (NCS failing to start, backups failing, etc.) where exhausting disk space was at the root, but they had overlooked the gentle warnings that a critical alarm gave. Prime Infrastructure 1.2 has disk space messages that are highly intrusive, and were meant to be intrusive so customers wouldn't run out of space and not know it.
The threshold for these alarms is a hard set 50% utilization. At the most basic level, in order to copy out temp files to create a backup copy of the database, the /opt partition shouldn't be more than 50% utilized. Say, for example, one's /opt partition is 100GB, and their database is 75 GB, where is Prime Infrastructure supposed to be able to put 75 GB of temp files in order to create a backup? The 50% threshold is very important, particularly if NFS mounts are not being used to hold these temp files or the final backup.tar.gpg files the backup process creates.
In all installations, if the utilization level of the /opt partition (or /dev/mapper/smosvg-optvol in the Prime Infrastructure GUI under Administration > Appliance) is less than 60%, it's possible that the temporary archive log files from the Oracle database have accumulated and can be cleaned with the following commands at the Prime Infrastructure command line interface.
Prime Infrastructure release 184.108.40.206 resolved a number of backup/restore, migration and database issues. The subsequent 1.3.1 patch (filename PI_220.127.116.11_Update_1-12.tar.gz ) has fixed even more issues with backup/restore and reduced the filesize of the resulting backup.tar.gpg file that the backup process creates. Be sure to keep up to date with the latest bug fixes by upgrading to 18.104.22.168 and any subsequent patches, as soon as practicably possible.
NOTE: It's critical that Prime Infrastructure be stopped BEFORE starting an ncs cleanup. In some installations that are on the border of alarming, the "ncs cleanup" command may clear enough space to stop the alarms.
In installations with a virtual appliance, adding additional disk space is straightforward: Stop Prime Infrastructure with the "halt" command, add a second virtual hard disk to the VM, then power the VM back on. On boot up, the file system table will be updated with the new disk, and Prime Infrastructure will detect it and add it to both the /opt and /localdisk partitions in an 85%/15% mix. On logging into the GUI after adding the additional virtual hard disk, the disk space alarms will be gone. Unfortunately, increasing the size of the existing virtual hard disk in the virtual machine is not an option, as Prime Infrastructure's disk grow utility will not see that; it is looking for an additional virtual hard disk to be added to the VM.
In installations where High Availability (HA) is configured, remove HA
Administration > High Availability > HA Configuration > Remove button
before adding additional disk space. The primary and secondary can receive the additional disk space separately and brought back online, then HA restored.
Hello, Two dynamic interfaces are created at the WLC and Switch. DHCP server is located at the switch for vlan10(Guest) and vlan20(for internal client). My question is if the port f0/9 has to be trunk? Configuring it as access mode cannot work for the cli...
Hi all, I have an Cisco Catalyst 9120 AXI running with integrated EWC.Obviously, the 9120 has slower wifi speed than an AP2802i Mobility Express.2802i wifi speed 660Mbps9120 wifi speed 500 MbpsBoth devices are connected to cisco poe inj 6Is there any...
Hello,I have a question. vWLC 8.0 is installed at vmware workstation and then the ap3702 can join the vWLC, but if the same vWLC installed in ESXi6.7, the same ap cannot join the same vWLC at ESXi. I got the below message, some of them show “Bad certifica...
Hello, Anyone can help to resolve the issue? AP3702 cannot join vWLC 8.5, Below is some info, with below message, why it has ip address 10.0.100.175, i did not assign the ipPlease let me know it if any info needed. Thank you AP: ...