In 5.x developers would work with their own source repository and then push JCR, via the team provider.This team provider was not full featured and not available outside Eclipse.Git enables our repository to work any existing Git tool or team provider.While not yet supported in the UI, this will be added over time, it is possible to connect to the repo and tag and branch and restore things.
Workaround:Copy the "net port-list" and "ltm traffic-matching-criteria" objects from the source to target system, merge them with "tmsh load sys config merge", and then perform a force-full-load-push sync from source to target.If the BIG-IP systems are using device groups with auto-sync enabled, disable auto-sync temporarily while performing this workaround.1. On the source system (the system whose configuration you want to sync to peer), save the configuration and extract the ltm traffic-matching-criteria and port-lists:tmsh save sys config(shopt -s nullglob; echo "#"; echo "# $HOSTNAME"; echo "# generated $(date +"%F %T %z")" cat /config/partitions/*,/bigip_base,.conf awk ' BEGIN p=0 /^(ltm traffic-matching-criterianet port-list) / p=1 /^}/ if (p) p=0; print if (p) print; ' ) > /var/tmp/portlists-and-tmcs.txt2. Copy /var/tmp/portlists-and-tmcs.txt to the target system3. On the target system, load that file: tmsh load sys config replace file /var/tmp/portlists-and-tmcs.txt3a. If loading the config file on the target system fails with the same error message seen during a ConfigSync, follow the procedure inK13030: Forcing the mcpd process to reload the BIG-IP configuration :: tmsh save sys config clsh touch /service/mcpd/forceload clsh reboot4. On the source system, force a full-load sync to the device-group: tmsh run cm config-sync force-full-load-push to-group
TMS Business Core Library v1.15.1.1 with Full Source
2ff7e9595c
Comments