Video game design employment outlook: Cisco IOS XRv with GNS3 and VMware Fusion

Monday, May 22, 2017

Cisco IOS XRv with GNS3 and VMware Fusion

The title is somewhat misleading as this post goes beyond simply integrating Cisco IOS XRv with GNS3. We will construct a GNS3 lab that illustrates the implementation of mutual route redistribution with EIGRP and OSPF. Some of the material may be redundant from my previous post (Implement a Multivendor OSPF Lab with GNS3 and VMware Fusion), but this post will also include a couple of new gems that werent included in the prior one. Lets get started.

Core components required for this tutorial:

Mac OS X 10.9 (Mavericks)
VMware Fusion 6.0 Professional
GNS3
TunTap (or Set the Maximum Number of TAP Virtual Network Interfaces for Mac OS X)

The following table maps each device to its GNS3 object, hypervisor, and software relationship:

Device	GNS3 Object	Hypervisor	Software
R1	Router c3700	Dynamips	c3725-adventerprisek9-mz.124-15.T14.bin
R2	Router c3700	Dynamips	c3725-adventerprisek9-mz.124-15.T14.bin
XR1	Host	VMware	Cisco IOS XRv
S1	Host	VMware	Microsoft Windows Server 2012 R2 (Server Core)
S2	Host	VMware	Debian 7.4 (codename "wheezy")

SW1 - SW4 are generic GNS3 Ethernet switches, and also note the R1 and R2 devices can be any recent Dynamips-compatible Cisco IOS router image.

1. GNS3 Topology
Create a new GNS3 project. Drag and drop the GNS3 objects onto the blank Workspace. Arrange them so it looks similar to the layout of the network diagram. Configure each of the GNS3 objects with their specific attributes (e.g., hostname and symbol). You will also need to bind TAP network interfaces for the XR1, S1, and S2 GNS3 objects.

Connect the objects with the Add a link tool. The GNS3 Host objects will be using their particular TAP network interface(s) to connect to the Ethernet switches. By connecting a GNS3 Host object to the switch with a TAP network interface, the Dynamips process will create the TAP network interface on the host operating system. We can verify this by running the following commands from the terminal:


$ echo "What is the process ID (pid) for Dynamips? $(pgrep dynamips)"
What is the process ID (pid) for Dynamips? 20643
$ for i in {0..3}; do ifconfig tap$i; done
tap0: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
 ether 7a:18:e1:1f:f3:a8
 media: autoselect
 status: active
 open (pid 20643)
tap1: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
 ether 5e:60:1f:58:5e:61
 media: autoselect
 status: active
 open (pid 20643)
tap2: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
 ether 76:b6:cf:9f:9e:27
 media: autoselect
 status: active
 open (pid 20643)
tap3: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
 ether de:9c:8a:41:3d:4b
 media: autoselect
 status: active
 open (pid 20643)

2. VMware Fusion
The R1 and R2 devices are ready, from the perspective of GNS3 (Dynamips) connectivity, so we will zero in on creating the XR1 virtual appliance and also the server virtual machines (with their associated vmnets).

# 2.1 Virtual Network Switches
Our lab configuration will use host-only network switches. A host-only network (switch) is a network that is completely contained within the host computer. Host-only networking provides a network connection between the virtual appliance/machine and the host system by using a virtual network adapter that is visible on the host operating system. As the network diagram shows, we will be using vmnet10 to vmnet13.

Add a virtual switch with the following steps:

Open the Preferences window for VMware Fusion Professional.
Select the Network tab.
Click the + symbol to add a new virtual switch. Keep the Allow virtual machines on this network to connect to external networks (using NAT) and Provide addresses on this network via DHCP options unchecked to create the host-only virtual switch (vmnet).
Click the Apply button to save the setting.

Close the Preferences window when youre finished creating the virtual switches. We can verify the virtual switches have been created by running the following command from the terminal:


$ for i in {10..13}; do ifconfig vmnet$i; done

# 2.2 XR1
Import the VMware virtual appliance with the following steps:

Click File -> Import... from the VMware Fusion menu bar.
Click the Choose File... button.
Navigate to and select the iosxrv-k9-demo-5.1.1.ova file.
Click the Open button.
Click the Continue button.
Rename the package to XR1.
Click the Save button to save the virtual appliance in the default Virtual Machines folder.
Click the Customize Settings button to modify the virtual appliance settings.

By default, the virtual appliance is configured with two virtual network adapters. Network Adapter is the management interface (MgmtEth0/0/CPU0/0), and Network Adapter 2 is a traffic interface (Gi0/0/0/0). The management interface wont be used in our lab because we will be accessing the device via the console port connection. Another traffic interface (Gi0/0/0/1) will need to be created for our topology, though.

Add the network adapter with the following steps:

Click the Add Device... button.
Select Network Adapter from the Add Device menu.
Click the Add... button to add the device.
Click the vmnet11 radio button.
Click the Show All button to return to the virtual machine settings menu.

Network Adapter and Network Adapter 2 will also need to be modified from their default configuration. Since we wont be using Network Adapter in our lab, we can set it to connect to the default VMware Fusion host-only virtual network. Network Adapter 2 will use vmnet10 as shown in our network diagram.

Modify the network adapters with the following steps:

Click the Network Adapter menu item.
Click the Private to my Mac radio button.
Click the Show All button to return to the virtual machine settings menu.
Click the Network Adapter 2 menu item.
Click the vmnet10 radio button.
Click the Show All button to return to the virtual machine settings menu.

3GB of memory is allocated for the virtual appliance by default. I prefer to drop this to 2GB. In an upcoming section, we will see how to check the memory usage within IOS XR.

Modify the memory value with the following steps:

Click the Processors & Memory menu item.
Enter 2048 into the Memory field.
Click the Show All button to return to the virtual machine settings menu.
Close the settings window.

The VMware Fusion GUI portion of the virtual appliance configuration is complete. We will need to directly edit the virtual machine configuration file for the remainder.

Note: Its recommended to edit the virtual machine configuration file offline, so close the VMware Fusion application before proceeding to the next step.

Network Adapter 3 has been added with the GUI, but the default model type is incorrect for the virtual appliance. Lets first view the current configuration. My XR1 virtual appliance is located in the default VMware Fusion folder (directory), so I would run the following command from the terminal (Note: The character is for line continuation, so press the return key right after input) :


$ egrep ethernet[0-9].(present|virtualDev)  
> $HOME/Documents/Virtual Machines.localized/XR1.vmwarevm/XR1.vmx
ethernet0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet1.present = "TRUE"
ethernet1.virtualDev = "e1000"
ethernet2.present = "TRUE"

You may notice from the output ethernet2 (Network Adapter 3) is missing the statement with the virtualDev property. We need to add this statement, so it explicitly defines the model type as e1000; just like ethernet0 and ethernet1. We can add the statement by running the following command from the terminal:


$ sed -i.orig /ethernet2.present/a  
> ethernet2.virtualDev = "e1000"$ 
> $HOME/Documents/Virtual Machines.localized/XR1.vmwarevm/XR1.vmx

Lets verify the statement was correctly added by running the following command again from the terminal:


$ egrep ethernet[0-9].(present|virtualDev)  
> $HOME/Documents/Virtual Machines.localized/XR1.vmwarevm/XR1.vmx
ethernet0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet1.present = "TRUE"
ethernet1.virtualDev = "e1000"
ethernet2.present = "TRUE"
ethernet2.virtualDev = "e1000"

A custom virtual serial port has to be created for console port access. This is very similar to how we interface with our virtual routers in GNS3 (Dynamips). Note that 52153 is just an arbitrary TCP port number. Best practice is to select an available TCP port number between 49152 and 65535. Add the serial port device by running the following command from the terminal:


$ cat >> $HOME/Documents/Virtual Machines.localized/XR1.vmwarevm/XR1.vmx << EOF
> serial0.present = "TRUE"
> serial0.yieldOnMsrRead = "TRUE"
> serial0.fileType = "network"
> serial0.fileName = "telnet://127.0.0.1:52153"
> EOF

Verify the configuration by running the following command from the terminal:


$ grep serial $HOME/Documents/Virtual Machines.localized/XR1.vmwarevm/XR1.vmx
serial0.present = "TRUE"
serial0.yieldOnMsrRead = "TRUE" 
serial0.fileType = "network"
serial0.fileName = "telnet://127.0.0.1:52153"

Alternatively, you can make the previous modifications with TextEdit if you prefer. Run the following command from the terminal:


$ open -e $HOME/Documents/Virtual Machines.localized/XR1.vmwarevm/XR1.vmx

The XR1 device configuration is complete for the VMware Fusion section. We can now reopen the VMware Fusion application.

# 2.3 S1 and S2
The inclusion of the server operating systems is optional. I decided to add them to the topology to make it a more authentic lab and also provide some additional verification tools. I will not include the installation process of the operating systems as its beyond the scope of the tutorial.

S1 has the following VM hardware profile:

Component	Value
Processors	1 processor core
Memory	1024 MB
Network Adapter	Custom: vmnet12
Hard Disk (SCSI)	60 GB (thin)
CD/DVD (SATA)	WIN2012_R2.iso
Sound Card	Remove Sound Card
USB & Bluetooth	Remove USB Controller
Printer	Remove Printer Port

And S2 has the following VM hardware profile:

Component	Value
Processors	1 processor core
Memory	256 MB
Network Adapter	Custom: vmnet13
Hard Disk (SCSI)	20 GB (thin)
CD/DVD (IDE)	debian-7.4.0-amd64-netinst.iso
Sound Card	Remove Sound Card
USB & Bluetooth	Remove USB Controller
Printer	Remove Printer Port

3. Bridge Interfaces
Ive gone into a little more detail of this in previous posts, but a bridge interface is simply the glue that brings VMware Fusion and GNS3 together from a network connectivity standpoint.

The only real downside to using a bridge interface is the maintenance required when launching GNS3 projects with VMware Fusion virtual machines/appliances. Each bridge interface needs to be created (or rebuilt) with its members (TAP and vmnet) to establish full network connectivity. To clarify, the following commands would need to be (re)entered for our lab if we didnt have a better solution:


$ sudo ifconfig vmnet10 down
$ sudo ifconfig vmnet10 inet delete
$ sudo ifconfig bridge0 create
$ sudo ifconfig bridge0 addm tap0
$ sudo ifconfig bridge0 addm vmnet10
$ sudo ifconfig bridge0 up
$ sudo ifconfig vmnet11 down
$ sudo ifconfig vmnet11 inet delete
$ sudo ifconfig bridge1 create
$ sudo ifconfig bridge1 addm tap1
$ sudo ifconfig bridge1 addm vmnet11
$ sudo ifconfig bridge1 up
$ sudo ifconfig vmnet12 down
$ sudo ifconfig vmnet12 inet delete
$ sudo ifconfig bridge2 create
$ sudo ifconfig bridge2 addm tap2
$ sudo ifconfig bridge2 addm vmnet12
$ sudo ifconfig bridge2 up
$ sudo ifconfig vmnet13 down
$ sudo ifconfig vmnet13 inet delete
$ sudo ifconfig bridge3 create
$ sudo ifconfig bridge3 addm tap3
$ sudo ifconfig bridge3 addm vmnet13
$ sudo ifconfig bridge3 up

That is very inefficient, so I created a Bash shell script that takes care of the bridge interface operations for GNS3 labs with VMware Fusion. Lets see how we can put it into action.

# 3.1 Download the script file
My main GNS3 folder is located in my Documents folder (refer to GNS3 Base Configuration section), so I would download the create-bridge-netif.sh script file by running the following command from the terminal:


$ curl -Lo $HOME/Documents/GNS3/create-bridge-netif.sh http://goo.gl/53dTGQ

# 3.2 Create a copy of the script file
Ideally, the original create-bridge-netif.sh shell script file should only be used as a template. Each GNS3 project will have its own tailored shell script file that aligns with its specific topology. For example, I named my GNS3 project redistribution-lab. I would then create a copy of the original script file, and save it to the redistribution-lab project directory, by running the following command from the terminal:


$ cp $HOME/Documents/GNS3/create-bridge-netif.sh 
> $HOME/Documents/GNS3/Projects/redistribution-lab/create-bridge-netif-redist-lab.sh

# 3.3 Modify the GNS3 project script file
We will first navigate into the GNS3 project directory, for our current lab, by running the following command from the terminal:


$ cd $HOME/Documents/GNS3/Projects/redistribution-lab

Open the script file with a text editor. If you prefer to use a command line text editor, run the following command from the terminal:


$ nano create-bridge-netif-redist-lab.sh

Or if you prefer to use TextEdit, then run the following command from the terminal:


$ open -e create-bridge-netif-redist-lab.sh

The only section we may need to touch is the bottom portion of the script. For example, the bridge0 thru bridge3 blocks match up with our topology, but we dont need the bridge4 or bridge5 interface for this lab. We can either "comment them out" or delete them. For my example, I will "comment them out":


...

## bridge0
bridge="bridge0"
tap="tap0"
vmnet="vmnet10"
create_bridge

## bridge1
bridge="bridge1"
tap="tap1"
vmnet="vmnet11"
create_bridge

## bridge2
bridge="bridge2"
tap="tap2"
vmnet="vmnet12"
create_bridge

## bridge3
bridge="bridge3"
tap="tap3"
vmnet="vmnet13"
create_bridge

## bridge4
#bridge="bridge4"
#tap="tap4"
#vmnet="vmnet14"
#create_bridge

## bridge5
#bridge="bridge5"
#tap="tap5"
#vmnet="vmnet15"
#create_bridge

Make sure to save the file when youre finished with the edits. For nano: control + o (save), press the return key to confirm, and then control + x (exit) the nano text editor.

# 3.4 Run the script
Before we can run the script, we need to make it executable by giving ourself the execute permission for it. Run the following command from the terminal:


$ chmod u+x create-bridge-netif-redist-lab.sh

And finally, lets run the script to create our bridge interfaces for this lab. Run the following command from the terminal (user account password required to temporarily elevate privileges via sudo):


$ ./create-bridge-netif-redist-lab.sh
Password: <your_user_account_password>
INFO: The bridge0 network interface is available.
INFO: The bridge1 network interface is available.
INFO: The bridge2 network interface is available.
INFO: The bridge3 network interface is available.

We can verify the bridge interfaces are created, and the correct members are included, by running the following command from the terminal:


$ for i in {0..3}; do ifconfig bridge$i | egrep bridge|member; done
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
 member: tap0 flags=3<LEARNING,DISCOVER>
 member: vmnet10 flags=3<LEARNING,DISCOVER>
bridge1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
 member: tap1 flags=3<LEARNING,DISCOVER>
 member: vmnet11 flags=3<LEARNING,DISCOVER>
bridge2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
 member: tap2 flags=3<LEARNING,DISCOVER>
 member: vmnet12 flags=3<LEARNING,DISCOVER>
bridge3: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
 member: tap3 flags=3<LEARNING,DISCOVER>
 member: vmnet13 flags=3<LEARNING,DISCOVER>

The beauty of a script. This topology only includes four bridge interfaces, but just think if we had to manually create/rebuild a dozen bridge interfaces, each and every time, at the start of a lab. Ouch. So, for future reference, a typical workflow would look like the following with GNS3 labs that include VMware Fusion:

Open the GNS3 application.
Create/Load a GNS3 project that includes Host (and/or Cloud) objects with TAP interfaces.
Open the VMware Fusion application (host vmnet virtual network adapters will be created).
Run the GNS3 project "create bridge interfaces" script.
Start the router(s) in GNS3 (Dynamips).
Start the virtual machine(s) and/or virtual appliance(s) in VMware Fusion.
Access the virtual devices.

4. Basic Device Configuration
With the GNS3 and VMware sections complete, its time to access and configure each device.

# 4.1 R1
Start R1 in GNS3. Identify the console port number for R1 in the GNS3 management console with the list R1 command.

Establish a console port connection to the R1 device via telnet. Run this command from a new terminal window (tab):


$ telnet 127.0.0.1 2101

Configure the Fast Ethernet interfaces and bring them up.


R1# conf t
R1(config)# int f0/0
R1(config-if)# ip addr 172.17.3.1 255.255.255.0
R1(config-if)# duplex full
R1(config-if)# speed 100
R1(config-if)# no shut
R1(config-if)# int f0/1
R1(config-if)# ip addr 172.17.4.254 255.255.255.0
R1(config-if)# duplex full
R1(config-if)# speed 100
R1(config-if)# no shut
R1(config-if)# end

Save the running configuration to local NVRAM.


R1# copy run start

# 4.2 XR1
Start XR1 in VMware Fusion, and establish a console port connection to the virtual appliance via telnet. Run this command from a new terminal window (tab):


$ telnet 127.0.0.1 52153

Set a privileged username and password. For my example:


!!!!!!!!!!!!!!!!!!!! NO root-system username is configured. Need to configure root-system username. !!!!!!!!!!!!!!!!!!!!

 --- Administrative User Dialog ---


 Enter root-system username: marc
 Enter secret: marc
 Enter secret again: marc

Then login.


Please login with any configured user/password, or cisco/cisco


User Access Verification

Username: marc
Password: marc

Lets get some basic information before we begin the configuration.


RP/0/0/CPU0:ios# who
Tue Mar 18 19:47:04.431 UTC
 Line User Service Conns Idle Location
* con0/0/CPU0 marc hardware 0 00:00:00


RP/0/0/CPU0:ios# sh ver br
Tue Mar 18 19:48:59.583 UTC

Cisco IOS XR Software, Version 5.1.1[Default]
Copyright (c) 2014 by Cisco Systems, Inc.

ROM: GRUB, Version 1.99(0), DEV RELEASE

ios uptime is 4 minutes
System image file is "bootflash:disk0/xrvr-os-mbi-5.1.1/mbixrvr-rp.vm"

cisco IOS XRv Series (Pentium III Stepping 6) processor with 2096702K bytes of memory.
Pentium III Stepping 6 processor at 2757MHz, Revision 2.174
IOS XRv Chassis

2 GigabitEthernet
1 Management Ethernet
96050k bytes of non-volatile configuration memory.
866M bytes of hard disk.
1866736k bytes of disk0: (Sector size 512 bytes).


RP/0/0/CPU0:ios# sh ipv4 int br
Tue Mar 18 19:50:06.878 UTC

Interface IP-Address Status Protocol
MgmtEth0/0/CPU0/0 unassigned Shutdown Down
GigabitEthernet0/0/0/0 unassigned Shutdown Down
GigabitEthernet0/0/0/1 unassigned Shutdown Down


RP/0/0/CPU0:ios# sh memory summary
Tue Mar 18 19:50:49.525 UTC
Physical Memory: 2047M total (770M available)
 Application Memory : 1914M (770M available)
 Image: 69M (bootram: 69M)
 Reserved: 64M, IOMem: 0, flashfsys: 0
 Total shared window: 15M

Check resource usage per process with ptop. Press the ? key for help.


RP/0/0/CPU0:ios# monitor processes


256 processes; 1216 threads; 1081 timers, 6048 channels, 9662 fds
CPU states: 99.2% idle, 0.5% user, 0.1% kernel
Memory: 2047M total, 770M avail, page size 4K

 JID TIDS Chans FDs Tmrs MEM HH:MM:SS CPU NAME
 1128 12 39 49 9 20M 0:00:00 0.00% ipv6_rib
 1160 15 58 142 29 20M 0:00:00 0.00% l2vpn_mgr
 1127 18 44 49 9 16M 0:00:00 0.00% ipv4_rib
 321 10 22 73 5 14M 0:00:00 0.00% parser_server
 1144 15 49 97 23 13M 0:00:00 0.00% pim6
 1141 10 37 78 19 11M 0:00:00 0.00% igmp
 1143 16 53 99 23 11M 0:00:00 0.00% pim
 1142 9 32 54 17 11M 0:00:00 0.00% mld
 1126 4 24 35 9 9M 0:00:00 0.00% statsd_manager_g
 365 3 16 29 6 9M 0:00:00 0.00% statsd_manager_l

Set the hostname and domain name.


RP/0/0/CPU0:ios# conf
RP/0/0/CPU0:ios(config)# hostname XR1
RP/0/0/CPU0:ios(config)# domain name corp.example.com

Configure the GigE interfaces and bring them up.


RP/0/0/CPU0:ios(config)# int g0/0/0/0
RP/0/0/CPU0:ios(config-if)# ipv4 addr 172.17.3.254/24
RP/0/0/CPU0:ios(config-if)# no shut
RP/0/0/CPU0:ios(config-if)# int g0/0/0/1
RP/0/0/CPU0:ios(config-if)# ipv4 addr 10.16.2.1/24
RP/0/0/CPU0:ios(config-if)# no shut
RP/0/0/CPU0:ios(config-if)# exit

Set some lab options and commit the configuration changes.


RP/0/0/CPU0:ios(config)# domain lookup disable
RP/0/0/CPU0:ios(config)# line console exec-timeout 0 0
RP/0/0/CPU0:ios(config)# commit
RP/0/0/CPU0:ios(config)# end

Verify the IPv4 configuration for the interfaces.


RP/0/0/CPU0:XR1# sh ipv4 int br
Tue Mar 18 19:53:22.355 UTC

Interface IP-Address Status Protocol
MgmtEth0/0/CPU0/0 unassigned Shutdown Down
GigabitEthernet0/0/0/0 172.17.3.254 Up Up
GigabitEthernet0/0/0/1 10.16.2.1 Up Up

Enable Cisco Discovery Protocol (CDP) and save the configuration.


RP/0/0/CPU0:XR1# conf
RP/0/0/CPU0:XR1(config)# cdp
RP/0/0/CPU0:XR1(config)# int g0/0/0/0
RP/0/0/CPU0:XR1(config-if)# cdp
RP/0/0/CPU0:XR1(config-if)# int g0/0/0/1
RP/0/0/CPU0:XR1(config-if)# cdp
RP/0/0/CPU0:XR1(config-if)# commit
RP/0/0/CPU0:XR1(config-if)# end

Verify data link layer connectivity with R1.


RP/0/0/CPU0:XR1# sh cdp neigh g0/0/0/0 detail
Tue Mar 18 19:56:06.894 UTC

-------------------------
Device ID: R1
SysName :
Entry address(es):
 IPv4 address: 172.17.3.1
Platform: Cisco 3725, Capabilities: Router Switch IGMP
Interface: GigabitEthernet0/0/0/0
Port ID (outgoing port): FastEthernet0/0
Holdtime : 150 sec

Version :
Cisco IOS Software, 3700 Software (C3725-ADVENTERPRISEK9-M), Version 12.4(15)T14, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Tue 17-Aug-10 12:08 by prod_rel_team

advertisement version: 2
Duplex: full

# 4.3 R2
Start R2 in GNS3. Identify the console port number for R2 in the GNS3 management console with the list R2 command, and establish a console port connection to the R2 device via telnet. Run this command from a new terminal window (tab):


$ telnet 127.0.0.1 2102

Configure the Fast Ethernet interfaces and bring them up.


R2# conf t
R2(config)# int f0/0
R2(config-if)# ip addr 10.16.2.254 255.255.255.0
R2(config-if)# duplex full
R2(config-if)# speed 100
R2(config-if)# no shut
R2(config-if)# int f0/1
R2(config-if)# ip addr 10.16.1.1 255.255.255.0
R2(config-if)# duplex full
R2(config-if)# speed 100
R2(config-if)# no shut
R2(config-if)# end

Save the running configuration to local NVRAM.


R2# copy run start

Verify network connectivity with XR1.


R2# ping 10.16.2.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.16.2.1, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 12/19/40 ms

And display the ARP cache.


R2# sh arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.16.1.1 - c201.b5c4.0001 ARPA FastEthernet0/1
Internet 10.16.2.1 1 000c.29a9.745a ARPA FastEthernet0/0
Internet 10.16.2.254 - c201.b5c4.0000 ARPA FastEthernet0/0

# 4.4 S1
Start S1 in VMware Fusion. Windows Server 2012 R2 has been installed in Server Core mode, and only the command shell is available after signing in. We will do our configuration with PowerShell, so run the following command from the command shell (in the VMware console):


C:> start powershell

Set the IPv4 configuration for the network adapter.


PS> Get-NetAdapter | Set-NetIPInterface -Dhcp Disabled
PS> Get-NetAdapter | New-NetIPAddress -AddressFamily IPv4 -IPAddress 172.17.4.11 -PrefixLength 24 -Type Unicast -DefaultGateway 172.17.4.254

Verify the configuration.


PS> Get-NetIPConfiguration

Enable the firewall rule to allow ICMPv4 echo requests.


PS> Set-NetFirewallRule FPS-ICMP4-ERQ-In -Enabled True

Change the computer name and reboot for the change to take effect.


PS> Rename-Computer -NewName s1 -Restart -Force

After signing back in after the reboot, check basic network connectivity with the gateway.


PS> ping 172.17.4.254

# 4.5 S2
Start S2 in VMware Fusion, and login as the root user (in the VMware console).

Set the IPv4 configuration for the eth0 interface. Edit the /etc/network/interfaces file with your preferred text editor.


# vi /etc/network/interfaces


# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet static
 address 10.16.1.12
 netmask 24
 gateway 10.16.1.1

Bring the eth0 interface down, and then back up, to enable the changes.


# ifdown eth0 && ifup eth0

Verify the configuration.


# ip addr sh eth0

Check basic network connectivity with the gateway.


# ping -c 5 10.16.1.1

5. EIGRP
Weve established (and verified) network connectivity among the adjacent devices, so the next step i

Video game design employment outlook

Monday, May 22, 2017

Cisco IOS XRv with GNS3 and VMware Fusion

Cisco IOS XRv with GNS3 and VMware Fusion

No comments:

Post a Comment