Archive for February 2014

What is GNS3?

network2

What is GNS3?

GNS3 (Graphical Network Simulator) is an open source software that simulate complex networks while being as close as possible to the way real networks perform. All of this without having dedicated network hardware such as routers and switches.

This software provides an intuitive graphical user interface to design and configure virtual networks, it runs on traditional PC hardware and may be used on multiple operating systems, including Windows, Linux, and MacOS X.

In order to provide complete and accurate simulations, GNS3 actually uses the following emulators to run the very same operating systems as in real networks:

  • Dynamips, the well known Cisco IOS emulator.
  • VirtualBox, runs desktop and server operating systems as well as Juniper JunOS.
  • Qemu, a generic open source machine emulator, it runs Cisco ASA, PIX and IPS

Who can use it?

GNS3 is an excellent alternative or complementary tool to real labs for network engineers, administrators and people studying for certifications such as Cisco CCNA, CCNP and CCIE as well as Juniper JNCIA, JNCIS and JNCIE. Open source networking is supported too.

It can also be used to experiment with features or to check configurations that need to be deployed later on real devices.

Their programs includes exciting features, for instance connection of your virtual network to real ones or packet captures using Wireshark.

Where do I start?

In most situations, to use GNS3 you first need to provide your own copy of a network operating system, like Cisco IOS, PIX, ASA, IPS or Juniper JunOS. GNS3 also suggest ready to use non-copyrighted appliances.

Once you have your operating system, start reading the GNS3 documentation and learn how to use GNS3. Watching video tutorials is also a good way to better understand the program.

Installing GNS3

  • Double click on the installer

gns31

  • Accept the license agreement

gns32

  • Choose Start Menu Folder

gns33

  • Choose Components

gns34

  • Choose Install Location

gns35

  • The installer will launch into the WinPcap Setup Wizard

gns36

  • Accept the License Agreement

gns37

  • Click Install

gns38

  • Click Finish

gns39

  • Next the Wireshark installer will begin

gns310

  • Accept the License Agreement

gns311

  • Choose Components

gns312

  • Select Additional Tasks

gns313

  • Choose Install Location

gns14

  • Next Untick Install WinPcap as it is already installed

gns315

  • Wireshark will now complete

gns316

  • GNS3 Setup will now continue

gns317

  • Enter your email address

gns318

  • Finish and Start GNS3

gns319

  • This is the first screen you will see

gns321

  • As mentioned earlier, you must provide your own Cisco IOS to use with GNS3 due to licensing issues
  • Once you have obtained your own copy of a Cisco IOS for one of the supported platforms, you are ready to continue. Supported platforms are Cisco 7200, 3600 series (3620, 3640 and 3660), 3700 series (3725, 3745) and 2600 series (2610 to 2650XM, 2691)
  • When you open GNS3, You may get a Project Prompt as per below screenprint

gns325

  • On the Edit menu, choose IOS image and hypervisors. Then under the IOS Images tab, click … and then find your Cisco IOS file and click Open. The file will appear as your Image file. Next, click the drop-down arrow next to Platform and choose the platform that corresponds to your IOS file

gns326

  • You may get a message about decompressing the file

gns327

  • Now click the drop-down arrow next to Model and choose the model corresponding to your IOS file. I am using C1700 and a model of C1710For now, we’ll accept the default values that remain. However, there is a very important value called the IDLE PC value that we will want to include. We’ll get to that later. Click the Save button and then the Close button. This will return you to the default GNS3 window
  • If you get a message about Dynamips when you click Save, then go to Tools, Dynamips Server and click on it.. it will start and then prompt you about a Firewall issue which you can select to allow for your network.

gns328

  • Just a note on the IDLE PC value you can see in the screen above. We will need to learn how to find an IDLE PC value for the IOS we are using. This is a very important step. When an IOS is running, it will consume up to 100% of your CPU time. This will cause your computer to become very sluggish and will prevent building more complex topologies. However, if we use an IDLE PC value, we can reduce CPU usage dramatically. It puts the IOS into a sleep state when it is not in active use and wakes it up only when it is necessary.
  • So click on your router in the pane circled below and click the Green Run arrow

gns331

  • Now it’s time to choose a idlepc value. Be sure you can see the prompt of your router in Putty window. Right-click R1 and choose IDLE PC. GNS3 will spend a moment calculating an Idle PC value

gns332

  • Next it will show you the screen below. If you click the drop-down arrow, you see a list of possible IDLE PC values. Potentially better IDLE PC values are marked with an asterisk. Choose one of the values with an asterisk (in our example, we will choose number 1) and click OK.

gns333

  • If you choose IOS images and hypervisors on the Edit menu, and double-click on the image under the IOS Images tab, you’ll see the new IDLE PC value displayed under Settings

gns334

  • Next Right click on your router (On the icon in the middle panel) and select Console

gns335

  • Now you are ready to have a play! 🙂
  • If you issue the show ip interface brief command as shown, you’ll see the designations.

gns336

  • Carry on seeing what you can do especially if you are doing your CCNA and have exercises you can do. Some examples below
  • The first mode you will be presented with is known as the User Mode or User Exec Mode. This has a limited set of commands
  • enable will take you into the next mode known as Privileged Mode or Privileged Exec Mode useful for looking at the entire configuration, statistics and modules you have attached to the router
  • show ip interface brief will show you the interfaces you have
  • conf t will take you into the Global Configuration Mode
  • interface fastethernet0 will take you into the interface configuration mode
  • line console 0 will allow you to make changes to the console, Telnet or auxiliary ports
  • Ctl+Z will take you back to the previous mode

GNS330

Using WSUS with Microsoft Virtual Machine Manager 2012

shield

What is WSUS?

The Windows Server Update Service (WSUS) enables information technology administrators to deploy the latest Microsoft product updates. By using WSUS, administrators can fully manage the distribution of updates that are released through Microsoft Update to computers in their network. This blog shows an overview of this server role and more information about how to deploy and maintain WSUS via Microsoft Virtual Machine Manager 2012. The WSUS server provides the features that administrators need to manage and distribute updates through a management console. In addition, a WSUS server can be the update source for other WSUS servers within the organization. The WSUS server that acts as an update source is called an upstream server. In a WSUS implementation, at least one WSUS server in the network must connect to Microsoft Update to get available update information. The administrator can determine, based on network security and configuration, how many other servers connect directly to Microsoft Update

Installing WSUS

  • You can choose to install WSUS on a Remote Server
  • You can choose to install WSUS on a VMM Server which is what we are going to do

Installation Considerations:

During the installation process, WSUS will install the following by default:

  • .NET API and Windows PowerShell cmdlets
  • Windows Internal Database (WID), which is used by WSUS unless you configure WSUS to connect to another DB Instance on a separate server to the VMM Server
  • Services used by WSUS, which are:
    • Update Service
    • Reporting Web Service
    • Client Web Service
    • Simple Web Authentication Web Service
    • Server Synchronization Service
    • DSS Authentication Web Service

By default, the WSUS server uses port 8530 for HTTP protocol and port 8531 for HTTPS protocol to obtain updates from Microsoft. If there is a corporate firewall between your network and the Internet, you will have to open these ports on the server that communicates directly to Microsoft Update. If you are planning to use custom ports for this communication, you open those ports instead

Pre Requisites

  • The database server cannot be configured as a domain controller.
  • The WSUS server cannot run Remote Desktop Services.
  • The database server must be in the same Active Directory domain as the WSUS server, or it must have a trust relationship with the Active Directory domain of the WSUS server.
  • The WSUS server and the database server must be in the same time zone or be synchronized to the same Coordinated Universal Time (Greenwich Mean Time) source
  • Check server hardware requirements to enable WSUS role are bound to hardware requirements.
  • Check if you install roles or software updates that require you to restart the server when installation is complete, restart the server before you enable the WSUS server role.
  • Microsoft .NET Framework 3.5/4.0 must be installed on the server where the WSUS server role will be installed. Can be selected when you go through adding roles
  • The NT Authority\Network Service account must have Full Control permissions for the following folders so that the WSUS Administration snap-in displays correctly: This path may not exist until you have installed the IIS role
  • %windir%\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files

wsus

  • %windir%\Temp

wsus00

  • Assign the Local System account to the WSUS Administrators Group

wsus0 Installation

  • Open Server Manager and click Add Roles

wsus1

  • Select Role based or feature-based installation

wsus2

  • Select your destination server

wsus3

  • Put in tick in Windows Server Update Services. It will automatically tick IIS as well

wsus4

  • Accept the default feature install

wsus5

  • Make sure you also tick .NET Framework 3.5 Features

wsus6

  • Click Next on Web Server Role (IIS)

wsus7

  • On Select Role Services you will need the following
  • Performance > Dynamic Content Compression
  • Security > Windows Authentication
  • Application Development > All ASP’s selected
  • Management Tools > IIS6 Management Compatibility

wsus8

  • Click Next on the Windows Server Update Services Page

wsus9

  • Untick WID Database and tick WSUS Services and Database
  • I chose Database as I have set up an instance on a separate Windows Server 2012 SQL Server and I am interested in testing the connectivity!

wsus10

  • You will need to create a folder for the WSUS Downloads then enter the path
  • In my case I just chose c:\WSUS

wsus11

  • Put in your SQL Database Server name and Instance.
  • In my case this is dacvsql002\WSUS

wsus12

  • Click Check Connection. Hopefully it should say Successfully connected to server

wsus13

  • Check the final summary and put a tick in Restart Destination Server

wsus14

  • Click Install and wait for it to finish and you should see the below screen

wsus15

  • Note it says Further Configuration is required
  • Click on Launch Post Installation Tasks and you will likely get an error message as per below

wsus17

  • The Log file says

wsus18

  • In order to resolve this, you need to open PowerShell as an Administrator and change to the directory where WSUSUtil is typically located in c:\Program Files\Update Services\Tools and run the following command

wsus19

  •  Once complete you should see the below screen

wsus20

  •  I then rebooted at this point and in this time, I logged into my SQL Server to check the Database had been created under my instance dacvsql002\WSUS

WSUS48

  • When the server is back up, click the Windows Key and Q and click on Windows Update Services
  • You can now configure WSUS by using the WSUS Configuration Wizard or you can cancel this and open the WSUS Console and configure the Options

wsus21

  • I cancelled and went through the options as per below
  • Click Options

wsus22

  • Update Source and Proxy Server

wsus23

  • Products

wsus24

  • Classifications

wsus25

  • Update Files

wsus26

  • Update Languages

wsus27

  • Synchronisation Schedule

wsus28

  • Update Rules

wsus29

  • Advanced

wsus30

  • Computers

wsus31

  • Server Cleanup Wizard

wsus32

  • Reporting Rollup

wsus33

  • Email Notification

wsus34

  • Microsoft Update Improvement Program

wsus35

  • Personalization

wsus36

  • And finally you have the option here to run through the configuration wizard which you have seen in an earlier screenprint

wsus21

  • Now we need to add the Windows Server Update Server to VMM
  • In the VMM Console, open the fabric workspace
  • Click Add Resources > Update Server

wsus37

  • Add Windows Server Update Services (WSUS) Server
  • Enter in the relevant details as per below
  • It will let you know if you can’t use a User Account
  • Click Add when complete

wsus38

  • A job window will then pop up showing you what’s going on

wsus39

  • To verify that the WSUS Server was added to VMM successfully go to the Fabric Workspace > Expand Servers > Click Update Server.
  • The Results pane should show the WSUS Server

wsus40

  • In the library workspace, on the library pane, expand Update Catalog and Baselines and then click Update Catalog. The results pane displays all the available updates

wsus47

  • After you add the Update Server to VMM, you can configure a proxy server for synchronisation and change the update categories, products and supported languages that WSUS synchronises by updating the properties of the update server in VMM.
  • Open the Fabric Workspace > Expand Servers > Click Update Server
  • Right click on the Update Server in the results pane and select Properties

wsus41

  • Next you will see the Proxy Server

wsus42

  • Next you will see the Update Classification

wsus43

  • Products

wsus44

  • Languages

wsus45

  • To manually synchronise updates in VMM, in the Fabric workspace, on the Fabric pane, expand servers and then click Update Server. You can then Synchronise. See highlighted screenprint below

wsus46

Microsoft TechNet Site for more information

http://technet.microsoft.com/en-gb/library/gg675084.aspx