202 Lab Introduction Connecting to the Lab Environment

Transcription

1 202 Lab Introduction Connecting to the Lab Environment Objectives During this v7.1 Deployment lab, each student (from the Blue group or Green group) must verify access (and permissions) to their assigned POD. Each POD includes seven (7) VMs, plus connectivity to an assigned V10000 Appliance (either V or V ). Upon completion of this lab, students will have correctly utilized VMware vcenter Lab Manager tools to validate the initial POD configuration. After each lab is completed, a copy of your VM is automatically saved (and restored, prior to each new lab exercise). Please use the network diagram (and Student Cheat Sheets ) to verify/configure all POD components and network interfaces. An effort was made to ensure the POD implementation matches (or more closely emulates) a real world deployment. For example, each POD combines Router and Appliance(s) hardware and virtual components. The servers and V10000 Appliances used for this training session are hosted by Websense, and deployed within the hotel. Each student pair must complete this lab, and shall be provided a Windows/PC (and assigned a unique pod number, e.g. POD02A). Over the next minutes, each team should login and verify basic services for each VM (7 VMs, total). Please follow each lab exercise in succession, step-by-step, coordinating each task when configuring components.

2 Lab Environment VM Requirements for Deployment Labs VMs Required Software Deployment Operating System Rel File VM Name DC-WSG (Domain Controller DNS, AD wstrain.com) WWS-WSG (v7.1 WWS, SQL Log Server/Websense Manager) 1 GB Windows Server2003 R2 SP2 DC for WSG 4GB Windows Server 2003 R2 SP2 WWS for WSG XP2 Client 1 256M Windows XP w Explorer SP 2 XP CLIENT 1 7 XP2 Client 2 256M Windows XP w Explorer 7 SP 2 XP CLIENT 1 WSG-1 2GB Centos 4.5 WCG for WSG WSG-2 2GB Centos 4.5 WCG for WSG WSG-3 2GB Centos 4.5 WCG for WSG

3 Logging In and Accessing VMs & Pod Components via Lab Manager 1. Click the IE (Desktop) icon to launch Internet Explorer to display the Lab Manager login screen: Figure: VMware vcenter Manager - Login 2. Enter your assigned POD# and (default) password: Example: POD02B Where: xx = POD# Y = A (Blue Group), or Y = B (Green Group) For your enter: Websense1 Note: For these deployment labs, you may choose to modify this password (only). To modify the VMware password, user the Preferences tab (top, right of Lab Manager). Record your POD and credentials Record your vcenter Lab Manager logon credentials, both POD # and Group (Blue or Green). Record your assigned POD/group and Lab Manager password: POD# (Group) Figure: POD#(Group) and password assignments for VMware Access Example: POD02B indicates: Pod number 02 group B group (Green). A = Blue Group B = Green Group

4 Lab Environment Credentials and Keys Throughout these Deployment labs, the following login credentials will be pre-configured. Unless instructed during these exercises, please do not modify these passwords: XP2 Client 1 and XP2 Client 2 Login Credentials: Username administrator Websense1 Active Directory (Native Mode) Login Credentials: Username WSTRAIN1\administrator Websense1 V10000 GUI (appliance management) Login Credentials: Username admin Websense1 Zen Domain Login Credentials: Username root Websense1 DC Login Credentials: Username WebsenseAdministrator Websense1 Websense Manager Login Credentials: Username WebsenseAdministrator Websense1 WCG Management Login Credentials: Username admin (***or administrator) Websense1 *** During client re-direct to a (new) WSG-x proxy, users may need to re-authenticate via their browser as: administrator/websense1 Training Key: For training purposes only, the following subscription key is required to configure each component (WWS, WCG, and V10K): TST7TAVMS5S9Q2R2 Accessing the Environment & Pod Components via Lab Manager 1. Login to your assigned POD. Click Overview (left pane). Notice, the My vcenter Lab Manager, Documentation and Support links, as shown.

5 2. On the left pane, click Workspace and verify Status as Deployed (next to Configuration Names). 3. Notice there are seven (7) VMs in the POD environment, which should be powered-on as indicated below. In the example, the Power Off option appears, indicating the VMs are (currently) powered on : Move your mouse over the pod name. Notice: The drop-down menu provides a list of available options. For example, at the end of this lab you will need to launch the Show Consoles.

6 4. Right-click on each VM Name (e.g. DC) to display the drop down menu. At this time, click Power On to start any VMs not already on. Next, click Open to open a VM. 5. Next, beginning with the DC VM, select each VM Console and login (one-by-one) to ensure they will open and access is enabled. If you were not able to access each VM Console, clear the IE cache and refresh the screen. If you are still unable to login to each VM Console, immediately notify the instructor. Then, log-off VMware vcenter Lab Manager and logon, again. Note: To release your mouse and exit the WSG-x VMs, press <Ctrl - Alt>

7 6. Review (briefly) the drop-down menu selections (Note: Please do not perform each command listed below): Power On Can be used to power-on all VMs within the set. During power on, the VMs will appear busy for a few minutes. (If VM is powerd On, then power off appears in the drop down menu) Open Opens all your VMs for viewing - You can select (or power on) individual VM Consoles History Verify the deployment date/time matches your configuration requirements (for kick-off, deployments were created beginning 12/28/09 up to the date of this training). Show Consoles By far the most popular! Use show consoles to view all consoles in a near full screen sizing (after a minute or two, scroll down/up to view each console screen). To go to full screen on console, select your console (e.g. XP Client 1 VM). Select Pop out console. In the pop out console select full screen. To escape type <ctrl alt>

8 There are other functions, listed below. The shaded features are not available to the student. Ctrl-Alt-Delete Sends this signal to VM Note: Within each Windows VM, to reboot a VM or access the Task Manager, press: <Ctrl-Alt-Insert>. Within each Linux VM, pres <Ctrl-Alt> to release mouse. Suspend/Resume Suspends current VM frees resources but keeps state Reset Hard Reset of VM Snap Shot Takes a snapshot of the current environment Shut Down Runs Shutdown on VM Power Off - Powers Off VM Properties Properties of this VM 7. Next, launch the WSG-3 VM (console) and login with the following credentials: root/websense1

9 8. Ensure the gateway is running: # /opt/wcg/wcgadmin status If not, restart services: /opt/wcg/wcgadmin restart To exit WSG-3 and release your cursor, press <Ctrl - Alt>. Select the WSG-2 VM Console (this is important any time you are accessing the WSG-x VMs) 9. At this time, from the drop-down menu launch Show Consoles, as described previously. Displays a full screen console window for each VM (Note: May take a minute, then scroll down/up to view each console screen). Ensure all VMs are up and (basic) services are running (e.g. DC is up and names are resolving). Note: In future labs, we will validate the proxy/filter features of the POD. 10. From the XP Client 1 VM console, launch IE and verify you are able to view internet web pages (e.g. Validate all systems and interfaces You should NOT need to ping each interface: If you have problems configuring your POD, the table below will assist you to ensure connectivity to all POD components (all interfaces. 1. If you need to troubleshoot the POD, open a Command window, and perform the following tests using both XP2 Client 1 VM and XP2 Client 2 VM: The results should be yes for all tests. If not, immediately notify your instructor which interface has failed, and then troubleshoot the problem.

10 System/Interface IP (VLAN) Ping from XP2 Client 1? (yes) Ping from XP2 Client 2? (yes) DC WWS-WSG WSG XP2 Client V (C) V (C) Cisco 3550 fe0/ WSG WSG Cisco 3550 fe0/ XP2 Client Cisco 3720 fe1/ V (P1) V (P2) V (P1) V (P2) Cisco 3550 fe1/ Internet yahoo.com

11 *3725 fe 2/0 * xx Figure: POD Connectivity Checklist *Where xx is the unique POD # assigned by the instructor for these sessions. For example: = POD #1, and = POD #10 Verify WSG-1, WSG-2 and WSG-3 Network Interfaces From each WSG-x VM, we have verified services are running. Next, ensure connectivity to each gateway, as indicated: WSG-1 WSG-2 WSG-3 IP Address Subnet Mask Default G/W DNS Only if you suspect network connectivity problems on your POD, then continue the following steps. Otherwise, please proceed to the next section. On each of the WSG-x VMs (WSG-1, WSG-2, and WSG-3 VMs): 1. From each WSG-x VM, login using the credentials: root/websense1 2. From WSG-1, WSG-2, and WSG-3 VMs, verify network settings and ping the WWS VM and each client. 3. Enter the following commands to verify your network connectivity: ifconfig eth0 - This should display the IP address and subnet mask configured above ping Verify connectivity to the DC (Press Ctrl+C to terminate) ping Validate connectivity to an external IP address (Press Ctrl+C to terminate) ping download.websense.com - This checks DNS resolution. (Press Ctrl+C to terminate) If the commands fail, notify your instructor, and then proceed as follows: Enter the command setup Select Network configuration and Yes to continue Enter the details as described above Quit from the Setup utility Enter the command service network restart Enter the command ifconfig to confirm your network settings Enter the command cat /etc/resolv.conf to confirm your DNS setting

12 Enter the command cat /etc/sysconfig/network to confirm your default gateway setting Verify Date/Time on WSG-1, WSG-2, and WSG-3 To ensure correct operations of the WCG throughout these labs, the date and time on WCG must match the WWS (e.g. database downloads, etc.). From WSG-1, WSG-2, and WSG-3 VMs, perform the following steps to ensure the date/time matches the WWS VM: 1. First, ensure you can ping your WWS VM from each WSG-x VM. Enter the command: ping Next, verify the current date/time, entering the command: date 4. If the output on each WSG VM does not match the date and time as the WWS VM, enter the following command: date MMDDhhmmYYYY Where: MM = 2-digit month; DD = 2-digit daya; hh = 2-digit hour; mm = 2-digit day, and YYYY = current year Configuring an NTP server is recommended to ensure system clocks remain synchronized using a trusted, reliable (external) source. For example, during these labs you may choose to configure the NTP server as: Verify Connectivity between WWS and WSG VMs From the WWS VM, verify connectivity between each of the WSG VMs. The results should be yes for all tests. System/Interface IP (VLAN) Ping from WWS ( )? WSG WSG WSG

13 Figure: WWS and WSG Connectivity Checklist (OPTIONAL) Verify Disk space available: All VMs and DomU s 1. To ensure each POD is pre-configured properly, verify all VMs and Domu s have the required disk space to perform lab exercises. # df k (determine if less than 90% used space on the root filesystem) Other clean-up: No residual (old) WS database files or failed.xfr files and WS Database (s) pre-installed (updated after Jan 2, 2009 to ensure fresh version) (OPTIONAL) V10000 Domains: V10000 DomUs (WCG & Filter Svc) Refer to tables, below, for detailed IP Address for each V10000 interface. Dom 0: Appliance management functions (Patch, SSH, Serial, etc.) DomUs: Modules (WCG, NA, Filter, etc.) Figure: V10000 Dom0 and DomUs (WCG, and Filter/Policy, etc.) During the V10000 Sections of Lab 2 and Lab 3, we ll prepare our DomU s (WCG & Filtering), before validating on-box, then off-box services. Figure: V10000 DomUs (WCG and Services: Filter, Policy, User, etc.) Appliances: V & V Access to the V10000 DomUs can be accomplished from XP Client 1 VM through the IE browser. Example URLs: or

14 Deployment Consideration: Without remote access through DRAC, if a remote administrator performs a shutdown of the Appliance, physical access may be required (i.e. local access to the V10000), for example: A) Press power on and/or B) Manually re-insert the Recovery DVD (i.e. re-insert the tray) after firstboot. For example: Performing a Shutdown V10000 may require physical access to the Appliance to re-apply power, and re-boot the V10000 system unit. Figure: V10000 Shutdown - May require physical access to Power-On Intro Lab Conclusion Please notify the instructor you have completed this lab. If you are correctly accessing all VM Consoles and have verified connectivity, this concludes the Lab 2 exercises. Up to this point, you have verified login for all seven VMware consoles, and network connectivity for all POD components NOTE: If time permits, you may continue to examine the POD using the OPTIONAL exercises, above.