N E T V I R T E X P E R T

     If you are, like me, using Win10 with legacy BOOT option and would like to start playing with newest Windows 11 version - first problem probably will be TPM (Trusted Platform Module) chip... which can be easily added to VM - if it runs UEFI based boot firmware. Change, without proper existing disk preparation, could went wrong in terms of non-bootable machine etc. Summary - it can be done without OS reinstall and here are proposed steps that worked for me: - of course - some kind of backup/snapshot should be there, just in case ;) - run command " Get-Disk"  which should give you output that  Partition style is MBR ; - before actual conversion you can run validation with command " MBR2GPT.exe /validate /allowFullOS " - using variable " allowFullOS " inside running VM; - after successful validation - actual conversion is done by using command " MBR2GPT.exe /convert /allowFullOS "; - shut down VM after conversion is done and change to UEFI boot...

        In case you need TopN talkers usefull output on Cisco IOS-XE you can try customized config like this one: flow record TOP-N match ipv4 source address match ipv4 destination address collect interface input collect interface output collect counter bytes long collect counter packets long   Then create appropriate monitor: flow monitor TOP-N record TOP-N   On WAN side implement new flow record: ip flow monitor TOP-N input   For showing appropriate results you need quite a long show command: show flow monitor TOP-N cache sort highest counter packets...

     As you maybe know SIP doesn't like NAT :)... especially for IOS/IOS-XE Cisco based devices (ASA for example handle that much, much better). For that reason you need straight config to make it work - for control and audio part of communication. These are required steps in UC CME environment with public SIP account for trunk PSTN access: - define 1 ACL for udp SIP traffic (port 5060) and RTP audio port match - very probably high value ports: ip access-list extended UDP_RTP  permit udp any any range 8000 65000  permit udp any any eq 5060 - define 1 route-map (for NAT) that uses previosly created ACL: route-map SIP_NAT permit 10  match ip address UDP_RTP - define  STATIC NAT  translation for your inside SIP voice interface (this example uses 192.168.12.x for that purpose): ip nat inside source static 192.168.12.x [YOUR-PUBLIC-IP] route-map SIP_NAT Adequate ACL for WAN access and SIP secure communication should be in place if you're using public S...

     In case you have problem accessing ASA through ASDM manager which gives you error like " Unable to launch device... " and you already configured everything by the book for ASDM access, then you should check JAVA policies - especially with Java 1.8 - and you can upgrade them so they allow you to use more strict FIPS standard or high ciphers inside your ASA device. You can download required files from  HERE  (for Java 1.8) and upload them, instead of existing one, in your Java install folder --> lib --> security. After that ASDM with enabled strong SSL ciphers should work fine...

    These are recommended installation requirements if you need to play with Vicibox open source scalable contact center solution: -  DB server (for up to 150 agents)  - 8GB RAM, 240GB+ SSD - ALWAYS INSTALL FIRST IN CLUSTER SETUP FOLLOWING WITH ARCHIVE, WEB AND LAST TELEPHONY SERVER! -  Archive server  - 2GB+ RAM, 1TB HDD -  Web server  - 4GB+ RAM, 160GB HDD -  Telephony server  - 4GB+ RAM, 160GB HDD OS installation notes (assumes you already downloaded ISO from  http://download.vicidial.com/iso/vicibox/server/ ): root / vicidial - default login os-install - Suse OS installation yast lan - setup properly network and DNS properties yast firewall - setup properly firewall inside OS zypper up -y - install updates and reboot after that yast timezone - setup properly timezone Vicibox express installation: vicibox-express - complete express setup Vicibox cluster installation: vicibox-install - install required component and reboot af...

    Occasionally Cisco UCS performance manager (based on Zenoss 5) may stop responding with main   serviced  daemon inactive - which leads to unresponsive web access and all features...version on which I founded this was 2.0 (but 2.0.1 and 2.0.2 are also the same) of UCS performance manager. Because of that I created small script to check status of service and do an restart - until something better and official came out: #!/bin/bash service=serviced if (( $(ps aux | grep -v grep| grep -v "$0" | grep serviced| wc -l) > 0 )) then echo "$service is running!!!" else service $service restart fi Give it executable rights -  chmod +x [name of script]  - and schedule it through standard cron job. Until something better this should do it...

If you have problem connecting newest vDP 6.1.2 appliance with vsphere web client in following circumstances: - you are using vDS (Nexus 1kV also) - you migrate everything to standard vswitch and it works like it shoud - THEN please follow procedure from link below: http://www.virtuallypeculiar.com/2016/05/unable-to-connect-vdp-61-to-web-client.html Unable to connect to vCenter appliance with winSCP - please change SFTP environment protocol options in advanced settings to " shell /usr/lib64/ssh/sftp-server"  and enable SSH, Shell access in web Admin settings. It should work like charm...