...
If log collection option as described in previous chapters is not available/ can not be accessed, log collection may be performed manually by ssh access to Yarnman
Please send screenshot of error encountered and detailed steps to reproduce and time stamp from ssh via date command
run command via ssh to collect logs
tar -czvf yarnman-logs.tar.gz --exclude='*.tar.gz' /var/log/yarnman
Then sftp file and send to support as required
Yarnman database log collection
If requested by support this log collection may be required
...
Then sftp file and send to support as required
Yarnman increase disk space for database
To increase the storage space for any of the log or database filesytems in Yarnman.
2.5.X process
Log in to Yarnman using ssh
Type df which will show you the size of the filesystems. Note the space in var/lib/couchdb. If this is more than 50% used it is recommended to increase space so that less than 50% of the filesystem is used
...
Log in to vCentre and select the VM in question.
If there are any snapshots, these must be removed before increasing the storage for VM (a new snapshot can be performed after increasing disk space)
Increase the disk space - generally, the default diskspace allocated for Yarnman is 100G, increase the required diskspace to ensure that the /var/lib/couchdb partitionwill be less than 50% used
Once the storage space on the VM has been increase - log back into Yarnman using ssh
To increase the storage space for the couchdb partition, using all of the increased VM storage, type sudo ./scripts/resize-disk.sh var-lib-couchdb
Verify that filesystem storage is now OK
To further reduce storage space, it is recommended to compact couchdb as per below process
Yarnman database compaction
From time to time - particularly before/ after migrating very large CUCM clusters using Wrangler, it is prudent to compact the couchdb database
In 2.5.x
Log in to Yarnman using ssh
Type cd /opt/yarnlab/yarnman
type sudo node ./scripts/compactdb.js
Upgrade Yarnman - Apply a patch
...
External Firewall Ports
User Access to Yarnman
From (Sender) | To (Listener) | Destination Port | Purpose |
|---|---|---|---|
user segment | Yarnman node | TCP/443 | HTTPS |
user segment | Yarnman node | TCP/80 | HTTP redirect to HTTPS |
user segment | Yarnman node | TCP/22 | SSH - Support |
Yarnman to Other Systems
From (Sender) | To (Listener) | Destination Port | Purpose |
|---|---|---|---|
Yarnman node | CUCM/UCXN/EXPW |
| HTTP Webservices (AXL,RIS,Perfmon) |
Yarnman node | CUCM | TCP/2748 | CTI/QBE JTAPI (test_mate & orca_mate) |
UC Services (CUCM/MTP/Phone) | Yarnman node | UDP/6700-6799 (configurable in Yarnman) | Receive RTP ports (test_mate) |
Yarnman node | UC Services (CUCM/MTP/Phone) | UDP/16384 - 32767 (configurable in CUCM) | Transmit RTP ports (test_mate) |
Yarnman node | CUCM/UCXN/EXPW | TCP/22 | SSH proxy (yarn_gate) |
Yarnman node | CUCDM8 | TCP/8181 | Webservice |
Yarnman node | CUCDM10/11/VOSS4UC | TCP/443 | Webservice |
Yarnman node | Kurmi | TCP/443 | Webservice |
Arm deployment
From (Sender) | To (Listener) | Destination Port | Purpose |
|---|---|---|---|
Yarnman Arm node | Yarnman Core node |
| Database |
Yarnman Arm node | Yarnman Core node |
| Message Bus |
Yarnman Arm node | Yarnman Core node | TCP/22 | SSH - Support |
Yarnman Core node | Yarnman Arm node | TCP/22 | SSH - Patch Transfer |
High Avalilbity deployment
From (Sender) | To (Listener) | Destination Port | Purpose |
|---|---|---|---|
Yarnman Core node | Yarnman Core node | TCP/9100-9200 | Database Clustering |
Yarnman Core node | Yarnman Core node |
| Database Clustering |
Yarnman Core node | Yarnman Core node |
| Message Bus Clustering |
Yarnman Core node | Yarnman Core node | TCP/1000 | Message Bus Clustering |
Certificates
From Yarnman Menu - Select "Certificates"
...