DevNetSandboxUCManager11.0andPresence

LabUserGuide

JosephKearns

CiscoDevNetSandbox

2

Contents

1 Introduction...................................................................................................................................3

2 Reservingthelab............................................................................................................................3

3 ConnectingtoyourSandboxServers.............................................................................................4

4 MainTopologyPage.......................................................................................................................5

5 AccessingLabResources................................................................................................................8

CUCMpublisher.............................................................................................................................9

CUCMSubscriber............................................................................................................................9

PresenceServer............................................................................................................................10

Windows2008ADandDNSserver..............................................................................................10

6 CUCMandCUPConfiguration......................................................................................................11

3

1 Introduction

Welcome to DevNet Sandbox Collaboration 11.0 lab environment. This sandbox supports voice,video, IM and presence as well as the Collaboration APIs incorporated into Call Manager andPresence.Theenvironmentconsistsofthefollowingservers.

• UnifiedCommunicationsManagerPublisher11.0• UnifiedCommunicationsManagerSubscriber11.0• UnifiedPresence11.0• Windows20012R2ActiveDirectoryandDNSServer

ThisisafreeofchargelabwhichisavailabletoanyCiscoDevNetmember

2 Reservingthelab

TheDevNetSandbox isaccessiblethroughCiscoDevNetathttp://developer.cisco.com.Usersneedto register and login to theDevNet site. This is completely free of charge.Once registered, scrolldown to the Sandbox Icononand click. Thiswill bring you into the Sandboxhomepage.Clickon“Get Started with Sandbox” link. This will open the sandbox portal and immediately display allavailablesandboxestoyou.

SelectCollaborationontherighthandcategorymenu.Look for the“CiscoUCManager11.0.” tile.Hitreserve.

Figure2.1Collaboration11.0tile

4

Figure2.2Reservationwindow

Chooseduration. You can reserveup to amaximumof 5days. The reservationname canalsobechanged.Hitthereservebuttontokickstartyourlabsetup.

Themain topologypagewill thenopenand the labwillgo intosetupmode.During this time, theserversareclonedandafreeVLANisassignedtotheuser.Thistakesapproximately15minutes.Anemailwillbesenttotheuserwhenthesetupiscompleteandthelabisready.

3 ConnectingtoyourSandboxServers

TherearetwowaystoconnecttoyourprivateCollabroation11.0Sandbox.TheprimaryandmostpopularmethodisCiscoAnyconnectVPNClient.Thisclientcanbedownloadedhere(Windows,Macand Linux). Mobile Versions of Anyconnect are also available for Android and iOS. These areavailablefreefromtheappstore.

Whenyoursandboxisbuilt,youwillreceiveanemailwithsubject“YourDevNetSandboxisready”.This containsall the informationyouneed to connect to the lab.OnceAnyconnect is installedonyourdeviceyouarereadytoconnecttoyourprivatesandbox.

The mail contains and VPN headend and credentials specific to your lab. Enter these into theAnyconnect client to connect. Please note that these credentials are revoked at the end of yourreservation.

For more information on Anyconnect installation and configuration, see the “VPN” tab on yoursandboxportalinstructions.

ThesecondmethodisusingahardwareVPNroutertobuildatunneltothelabdirectly.WesupportIPsecconnectionsfrom881or891routers.Formoreinformationonthis,pleaseopenacaseonyoursupport page here. Setup of HW VPN takes time and but can be useful when requiring physicalphonesorserversconnectedtothesandbox

5

4 MainTopologyPage

Oncesetupiscomplete,thelabwillgointoActivemode(seeupperrighthandcorner).Thismeansthattheserversareclonedandarereadyforuse.

Figure4.1Collaboration11.0topology

The main topology page is shown in figure 4.1 above.. From this page, the user can accessinstructions,documentationandeachoftheavailableservers.Theusercanalsoendorextendtheirreservation.

Themainfunctionsareasfollows:

Clicking on this opens a tabbed window on the left hand side of the screen. This provides anoverviewofthelab,documentation,VPNaccessinstructionsandlinkstootherresources.Clickingonthebuttonagainwillclosethewindow.

Clicking on the commandswindow opens up awindow on the right had side of the screen. Thisshowsanyexecutedcommandsrunbytheautomationorinsometopologiesbytheuser.

Thiswilldisplaytheautomationcommandsrunduringsetup.Thisisnotapplicabletotheuserinthisparticulartopology.

6

Displays the scriptingoutputduring setupand teardownod the sandbox.Thiswindowcanbe leftopentodisplaythecurrentstatusofsetup.UserassignedVPNURLandcredentialsarealsoprovidedinthiswindow.

Figure4.2OutputWindowdisplay

Clickingon thiswillopena small topologymapat thebottom lefthandsideof thescreen.This isusefulwhennegotiatinglargertopologiesthatcannotfitonthescreenatonce.

Thiswillreduce/increasethesizeoftheresources.

Thisindicatoronthetoprighthandsideofthepageshowhowlongisleftinthereservation.Notethattheclonedserverswillbedeletedattheendofthereservation.

7

The user may end the reservation immediately by clicking on this icon. Confirmation will berequested.

Thisallowstheusertoextendthereservation

Thisisthestatusindicatorofthelab.Thiscaneitherbein

“Setup”Labissettingupandserversarecloning.Userdoesnothaveaccessduringthistime

“Active”:Labiscompleteandreadyforuse.UserreceivesemailwithVPNaccessdetails

“Teardown”:LabserversaredeletedandVPNaccessisrevoked.

8

5 AccessingLabResources

Theresourcesinthelabaredisplayedonthetopologywindow,asshownbelow.

Figure5.1ResourcesintheCollaboration11.0Environment

Eachresourceisrepresentedbyarectangularicon.“VLANXXX”representstheprivateVLANthattheserversareattachedto.Thisisnotrelevanttothesandboxuser.I

The lab resourcesof interest to theuserareprependedby theSandboxusername i.e. jokearns inthis case. These are the Call Manager Publisher, Call Manager Subscriber, Presence Server andWindows2012R2DNSserver.

In order to get more information about any of these resources, hover over the icon and selectAttributes.Thisactioncanbeperformedforanyoftheavailableresources.

Figure5.2AccessingResourceAttributes

Ontherighthandcommandwindow,informationforthatparticularresourcewillbedisplayed.

9

Figure5.3ResourceAttributesMenu

TheIPaddresses,username/passwordfortheresourceareshownhere.

Forthisparticularlab,resourcedetailsareasfollows:

CUCMpublisherIPaddress 10.10.20.1Hostname: hq-cucm-pubDomain: abc.incUsername: administratorPassword: ciscopsdtAccess: BrowserandSSH

CUCMSubscriberIPaddress 10.10.20.2Hostname: hq-cucm-sub1Domain: abc.incUsername: administratorPassword: ciscopsdtAccess: BrowserandSSH

10

PresenceServer

IPaddress 10.10.20.17Hostname: hq-cupsDomain: abc.incUsername: administratorPassword: ciscopsdtAccess: BrowserandSSH

Windows2008ADandDNSserverIPaddress 10.10.20.100Hostname: directoryDomain: abc.incUsername: ABC\administratorPassword: ciscopsdt(changepasswordifprompted)Access: RemoteDesktopConnection

11

6 CUCMandCUPConfigurationThefollowdeviceshavebeingpreprvisionedontheUnifiedcommunicationmanagerforconvenience.Thesecanbeusedtoregisterjabberclientsonvariousdevices.

Username Password Type Device DNuser01 cisco1234 JabberforWin/MAC CSFuser001 1001user02 cisco1234 JabberforWin/MAC CSFuser002 1002user03 cisco1234 JabberforWin/MAC CSFuser003 1003user04 cisco1234 JabberforWin/MAC CSFuser004 1004user05 cisco1234 JabberforWin/MAC CSFuser005 1005user06 cisco1234 JabberforIPAD TABUSER006 1006user07 cisco1234 JabberforIPAD TABUSER007 1007user08 cisco1234 JabberforIPAD TABUSER008 1008user09 cisco1234 JabberforIPAD TABUSER009 1009user10 cisco1234 JabberforIPAD TABUSER0010 1010user11 cisco1234 JabberforAndroid BOTUSER011 1011user12 cisco1234 JabberforAndroid BOTUSER012 1012user13 cisco1234 JabberforAndroid BOTUSER013 1013user14 cisco1234 JabberforAndroid BOTUSER014 1014user15 cisco1234 JabberforAndroid BOTUSER015 1015user16 cisco1234 JabberforIPhone TCTUSER016 1016user17 cisco1234 JabberforIPhone TCTUSER016 1017user18 cisco1234 JabberforIPhone TCTUSER016 1018user19 cisco1234 JabberforIPhone TCTUSER016 1019user20 cisco1234 JabberforIPhone TCTUSER016 1020

ThesedevicesarespecificallyforCiscoJabberendpointsthatareconnectedtothesandboxlabi.e.you could be running Cisco Jabber for Windows on the device connect to the sandbox viaAnyconnect.UserscanaddandregisterotherdevicestotheCUCM.However,thesedevicesmustbeconnectedtotheSandboxVLANinordertoregister.

The CUCM and CUP servers are automatically setup to Sync with each other on start up. Anunsuccessful sync will mean issues registering endpoints and using presence. At the start of areservation,itcanbeusefultocheckifthissynchronisationhastakenplacesuccessfully.

1. Browsetothepresenceserver(10.10.20.17)andlogintothe“CiscoUnifiedCMIMandPresenceAdministration”page.

2. GotoDiagnostics->SystemTroubleshooter

12

Figure6.1StartingtheSystemTroubleshooterinCUP

3. Thesystemwillexecuteanumberofchecksandmyrunforafewminutes.Ensurethatalltestsin the “System Troubleshooter”, “Sync Agent Troubleshooter” and “Presence EngineTroubleshooter” are green. If there is an issue with any of these tests, please follow theinstructionsintheSolutioncolumnforthegiventest.

Figure6.2SuccessfulCUPDiagnostics