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

Unified Call manager digit matching: X - any single digit in range 0-9 (ex. 8000-8999) ! - single or more digits in range 0-9 (ex. 82! - 82999999999999) ? - 0 or more occurrences of the preceding digit + - 1 or more occurrences of the preceding digit [] - enclose a range of values . - used as a delimiter, separates CM access code from the DN Call manager express digit matching: . - means a single digit. [0-9] - specifies a range .* - any digit followed by zero or more occurence, virtually any digit including null .+ - ny digit followed by one or more occurence, virtually any digit excluding null ^$ - no digits CME examples: /^123$/ /456/ - replaces only the number 123 as the source number with 456 /^123+/ /456/ - replaces any number that starts with 12 and has 1 or more occurence of 3 with 456 /.*/ /123/ - replaces any number with the number 123, including null CME advanced examples: /^\(5..\)/ /1234\1/ - match numbers in 500-599 range and transform it in 1234500-1234599...

Summary steps for configuring Cisco Unified Communication manager (ex Call manager) feature: multiple login not allowed but can be enabled in EM service parameter section create service for phones (CM6.1 Device/Device Settings/Phone services...) LOGIN and LOGOUT service uses same URL http:// CMipaddress /emapp/EMAppServlet?device=#DEVICENAME # check that exist default device profile for each type of IP phone create new user device profile with adequate DN number subscribe created profile to phone service already defined define user and associate with created profile enable Extension mobility for IP phones and define default logout profile

OK...I really need this. I can't memorize all of the router cli tasks, altough they are logical and follow the basic concept of Cisco IPSec site2site technology. Anyway, just in case... define transform-set define isakmp policy crypto ACL crypto MAP  assign MAP to INTF define INTF ACL some kind of routing must exist...static or dynamic If everything went OK, then check established IPSec tunnel parameters with show crypto isakmp sa  and show crypto ipsec sa.

First of all...never test thing on production environment...never. I have 3 ESXi 4 servers, two of them on vDS switches and one on old fashion virtual standard switch. When I moved third one to vDS and after assigning vmnic's to appropriate dvPort groups I had problems with connectivity...so because if was urgent (Production), I decided to bring all back to vSS just for this one ESXi 4. If you make mistake and remove physical NIC from vDS you may lose management connectivity to server at all...which is bad. But here are some useful comands which you need to enter directly on ESXi console to restore basic connectivity and after that everything else in your environment: alt+F1 , to access cmd line interface on ESXi type unsupported with your admin password From cli now you can see your curent configuration: esxcfg-vswitch -l , list your curent DVSwitch, DVPort and vmnic names (if output after this cmd is to big and you can't see what you need use | grep or | less or | more opti...

After new release of ESXi 4 update 1 I have had one of servers with famous "Unsupported boot partition..." problem. Of course, there was Windows 7 and vSphere client problem also...there was alternate solution to make client works under 7, I tested it but it wasn't so great. It works, but not as it should be working...with this update that problem is solved...you can now use vSphere client normally under 7 but not all of features. At least I can't...remote console view from client doesn't work. For upgrade I used Host update utility which comes with client installation...it went OK except that update utility crashes under 7 at 80% of upgrade process which made me go insane :)...but, everything was OK because upgrade process was already copied all files to server and server himself just finished upgrade. So, be aware of vSphere components and Win 7...certainly, for some time there could be "little" problems...