Why Gemfury?
Push, build, and install
RubyGems
npm packages
Python packages
Maven artifacts
PHP packages
Go Modules
Debian packages
RPM packages
NuGet packages
koyuawsmbrtn / PacketTracer deb
Repository URL to install this package:
|
Version:
8.2.2 ▾
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Configuring PCs</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link rel="stylesheet" type="text/css" href="styleNormal.css">
</head>
<body><div id="main-content" tabindex="0">
<p class="MainHeading1"> Configuring Network Controllers</p></div>
<hr>
<div tabindex="0">
Cisco Packet Tracer supports a simplified version of the Network Controller device.
</div>
<div tabindex="0">
<p class="MainHeading2">Overview</p>
</div>
<div tabindex="0">
<p>
Network Controller (NC) devices provides a means to manage, monitor and configure supported network devices via a graphical user interface and APIs.<br/>
</p>
</div>
<div tabindex="0">
<p class="MainHeading3">Where Is It?</p>
</div>
<div tabindex="0">
Network Controller can be found in the End Devices category on the device palette as shown below:
</div>
<p class="myPic">
<img src="images/netcon-comp-box.PNG" width="500em"/>
</p>
<div tabindex="0">
<p class="MainHeading3">Basic Configuration</p>
</div>
<div tabindex="0">
<p>
On a basic level, you can configure the Global Settings and Interface Settings of a Network Controller just like you can do on a regular PC. In addition the controllers can be accessed from outside Packet Tracer via HTTP REST APIs. This feature is called Real World Access. Its use and configuration will be explained in detail in sections that follow.
</p>
</div>
<div tabindex="0">
<p class="MainHeading3">Connecting It</p>
</div>
<div tabindex="0">
Using Network Controller in a network is customarily done by using its web interface accessible from a web browser on a PC connected to the controller. Below is shown simple way to connect a PC with the NC device. There are two physical ethernet interfaces on the controller. In a typical setup, one interface will be used for access and management of the NC while the other interface is for the controller to connect with and control the managed network.
</div>
<p class="myPic">
<img src="images/netcon-connect-simple.PNG" width="300em"/>
</p>
<div tabindex="0">
<p>
Users are encouraged to investigate various NC features by exploring this and other related sample files, that are part of your installation of Cisco Packet Tracer application. Some of the main features and interactions with NC are documented in more detail below.
</p>
<br/>
</div>
<div tabindex="0">
<p class="MainHeading2">Configuration and Management Using Web Interface</p>
</div>
<div tabindex="0">
<br/>
In a basic use case, however, users would want to access and manage their network controllers using a web interface. In order to access this interface, open the Web Browser on a PC connected to the controller and navigate to the controller's IP address in the browser's URL input. Basic network connectivity must be present beforehand.
</div>
<p class="myPic">
<img src="images/netcon-access-pc-wbrowser.PNG" width="700em"/>
</p>
<div tabindex="0">
<p class="MainHeading3">Initial Configuration</p>
</div>
<div tabindex="0">
Accessing and managing Network Controllers using the web interface requires the user to have an "administrator"-level user account on the NC. When accessing the NC web interface for the first time, you will be asked to do an initial setup by creating such an account, as presented below
</div>
<p class="myPic">
<img src="images/netcon-gui-initial-setup.PNG" width="837"/>
</p>
<div tabindex="0">
Use <strong>Username</strong>, <strong>Password</strong>, <strong>Confirm Password</strong> to enter your account attributes and click <strong>SETUP</strong> to create the new account.
<p>
Most NC network samples shipped with PT use user name "admin" and password "cisco", as the main administrator user account for their Network Controllers. <br/>
</p>
<p>
</div>
<div tabindex="0">
<p class="MainHeading3">Dashboard and Basic Navigation</p>
</div>
<div tabindex="0">
Having created this initial user account, accessing NC in the future will present you with a login screen in order to gain access to the rest of the controller's management interface, that start with a <em>Dashboard</em> view shown below
</p></div>
<p class="myPic">
<img src="images/netcon-dashboard.PNG" width="837"/>
</p>
<div tabindex="0">
Clicking on the <em>Dashboard Menu</em> button
</div>
<p class="myPic">
<img src="images/netcon-dashboard-menu-button.PNG"/>
</p>
<div tabindex="0">
opens a menu from which you can access various management and monitoring functions of the Network Controller
</div>
<p class="myPic">
<img src="images/netcon-dashboard-menu.PNG" width="837"/>
</p>
<div tabindex="0">
Likewise, clicking on the User name, <em>admin</em> in the case, below
</div>
<p class="myPic">
<img src="images/netcon-user-menu-button.PNG"/>
</p>
<div tabindex="0">
opens a menu from where NC administrators can perform User Management and Logout.
</div>
<p class="myPic">
<img src="images/netcon-user-menu.PNG" />
</p>
<div tabindex="0">
<p>
Each of the information panels on the Dashboard has <img src="images/netcon-dashboard-panel-gear-button.PNG" /> icon allowing direct access that that panel's section of Network Controller management interface. This can be used as an alternative to using dashboard menu button described above. <br/>
</p>
</div>
<br/>
<div tabindex="0">
<p class="MainHeading2">Provisioning</p>
</div>
<div tabindex="0">
<p>In this section you can add devices to the controller, discover new devices on the network and create global credentials used for accessing said devices. To access these features you would select <em>Provisioning</em> from the main menu on Dashboard as shown below</p></div>
<p class="myPic">
<img src="images/netcon-dashboard-menu-provisioning.PNG" width="300em"/>
</p>
<br/>
<div tabindex="0">
<p class="MainHeading3">Discovery</p>
</div>
<div tabindex="0">
In order to see status for existing device discovery processes, select <em>Discovery</em> on the navigation bar.
</div>
<p class="myPic">
<img src="images/netcon-gui-discovery.PNG" width="1200em"/>
</p>
<br/>
<div tabindex="0">
<p>You can create a new discovery process by clicking on <img src="images/netcon-gui-discovery-add-button.PNG" width="100em"/> button. In the UI panel that opens, you will be able to configure a new discovery process based on <em>CDP</em> or <em>IP address range</em>.</p>
<br/>
</div>
<div tabindex="0">
<p class="MainHeading2">Assurance</p>
</div>
<div tabindex="0">
<p>In this section you can take account of network devices, health of the network, view network topology and run path traces between hosts on the network. To access these features you would select <em>Assurance</em> from the main menu on Dashboard as shown below</p></div>
<p class="myPic">
<img src="images/netcon-dashboard-menu-assurance.PNG" width="300em"/>
</p>
<div tabindex="0">
This will take you to a view showing overall health of the network.
</div>
<p class="myPic"> <img src="images/netcon-gui-assurance-overall.PNG" width="1000em"/> </p>
<br/>
</div>
<div tabindex="0">
<p class="MainHeading3">Hosts</p>
</div>
<div tabindex="0">
<p>Clicking on HOSTS in the nagivation bar brings you the list of all network hosts the controller is "aware" of.</p> </div>
<p class="myPic"> <img src="images/netcon-gui-assurance-hosts.PNG" width="1000em"/> </p>
<br/>
<div tabindex="0">
<p class="MainHeading3">Topology</p>
</div>
<div tabindex="0">
<p>Likewise, TOPOLOGY in the nagivation bar will show all managed devices and their connections.</p> </div>
<p class="myPic"> <img src="images/netcon-gui-topology.PNG" width="1000em"/> </p>
<div tabindex="0">
In order to see information about a particular device you click on that device icon and that will open up the device information panel to the right of the graphical topology view above. The information shown above is for device named <strong>R3</strong>.</div>
<br/>
<br/>
<div tabindex="0">
<p class="MainHeading3">Path Trace</p>
</div>
<div tabindex="0">
<p>PATH TRACE - allows to trace traffic paths between interfaces of your choice. The view below shows initial screen where you can add new path traces by clicking <img src="images/netcon-gui-path-trace-add-button.PNG" width="80em"/>
</p></div>
<p class="myPic"> <img src="images/netcon-gui-path-trace.PNG" width="1000em"/> </p>
<div tabindex="0">
<p>After you click on the path you created, the results of that path trace show as follows</p>
</div>
<p class="myPic"> <img src="images/netcon-gui-path-trace-result.PNG" width="1000em"/> </p>
<br/>
<div tabindex="0">
<p><em>Due to limitations in PT, not all routes and interfaces of a path trace will be known.</em></p></div>
<br/>
<div tabindex="0">
<p class="MainHeading2">Policy</p>
</div>
<div tabindex="0">
<p>In order to configure policy settings use Policy item on the main dashboard menu</p>
</div>
<p class="myPic"><img src="images/netcon-dashboard-menu-policy.PNG" width="300em"/></p>
<br/>
<div tabindex="0">
<p class="MainHeading3">QoS</p>
</div>
<div tabindex="0">
<p>Here is an example of QoS configuration, using this interface </p>
</div>
<p class="myPic"><img src="images/netcon-gui-policy-qos.PNG" width="1000em"/></p>
<div tabindex="0">
<p>The Network Settings section will allow configuration of global settings for each managed device to ensure all devices use the same values. For example, DNS, NTP, and various other settings can be applied globally on all managed devices. </p>
<p><em>Refer to your curriculum for the relationship between QoS Scopes and Policies, and various other technology specific configurations.</em></p></div>
<br/>
<div tabindex="0">
<p class="MainHeading2">API Documentation</p>
</div>
<div tabindex="0">
Various features and information state available on Network Controller devices can be accessed programmatically via extensive REST API over HTTP. General API documentation can be accessed from NC dash board menu via <strong>API Docs</strong> menu item as shown above. This help also provides full content identical to said <a href="./NetconRestAPI/index.html">API Documentation</a>.</div>
<p class="myPic">
<img src="images/netcon-api-docs.PNG" />
</p>
<div tabindex="0">
<p>
To describe briefly the documentation interface please refer to the <em>numeral</em> markings in the above image. The numbered items are described below <br/>
<ol>
<li>
<em>API category.</em> Examples above include TICKETS, ASSURANCE and FLOW ANALYSIS. Each category lists API operation included. For instance, TICKETS category has only two operations: <em>addTicket</em> and <em>deleteTicket</em>.
</li>
<li>
<em>Operation name</em>, followed by brief description of its function.<br/>
</li>
<li>
<em>HTTP method</em>, that is used to access this function. In the above case, addTicket API must be accessed using HTTP POST.<br/>
</li>
<li>
<em>Base URL</em> used to perform this operation. In the above: <strong>/ticket</strong> <br/>
</li>
<li>
<em>curl</em> example. This is useful for making quick experiments with the APIs using this popular HTTP access tool. Note the format using {IP}:{PORT} format. <br/>In most simple cases your URLs will take a form of: <strong>http://localhost:{PORT}/{API BASE URL}</strong><br/> Concrete examples of using these URLs for accessing NC functions are provided in sections that follow.
</li>
<li>
<em>Parameters.</em> This segment will describe parameters, if any, that can be supplied to the API operation at hand. In the above example, parameters for this POST HTTP request will need to be supplied as JSON document in the HTTP request body. JSON schema is given below. As you can see, in order to get a ticket, ones input might look as follows:<br/>
<pre>
{
"username" : "admin99",
"password" : "d0ntsayit~75"
}
</pre>
Note! Parameter Name <em>user</em> is only useful in cases where this API is used through a functional interface, that can be generated by tools like Swagger. In this case, <em>user</em> will be the name of a parameter received by the function <em>addTicket</em>. Discussion of this case is outside the scope of this document.
</li>
<li>
<em>Responses: Success</em><br/>
This segment usually describes successful responses from a given operation. Successful responses will return JSON according to their documented Schema. <br/>
In case of <em>getTicket</em> above, the JSON data returned by successful 200 response will match the schema shown above. Here is an example of such response
<pre>{
"response": {
"idleTimeout": 900,
"serviceTicket": "NC-5-9b777a75c7bf4bea9317-nbi",
"sessionTimeout": 3600
},
"version": "1.0"
}</pre>
</li>
<li>
<em>Responses: Other</em><br/>
This segment usually describes responses that do not return any data or return errors. Here is an examples of a 401 error for the above getTicket operation one would receive when they specify a non-existent username in request parameters. <br/>
<pre>
{
"response": {
"detail": "Bad credentials",
"errorCode": "TICKET_BAD_USER",
"message": "User account is not found. Create a user account before requesting a ticket."
},
"version": "1.0"
}
</pre>
</ol>
</p>
</div>
<div tabindex="0">
<p class="MainHeading3">Example: Python Scripting in Programming Tab</p>
</div>
<div tabindex="0">
One way to access Network Controller from a PT PC device is to use its Programming Tab. Here's an example of a Python program one can find in a sample file named <strong>programming.pkt</strong><br/>
<pre class="code">
from http import *
from time import *
import json
securityUrl = "http://10.1.1.2/api/v1/ticket"
securityData = json.dumps({"username": "test","password": "test"})
securityHeader = json.dumps({"content-type": "application/json"})
getUrl = "http://10.1.1.2/api/v1/inventory/network-device/count"
postUrl = "http://10.1.1.2/api/v1/flow-analysis"
postData = json.dumps({ "sourceIP": "10.1.1.1", "destIP": "10.1.1.1" })
def onHTTPDone(status, data):
print("status: " + str(status))
print("data: " + data)
def gotToken(status, data):
print("status: " + str(status))
print("data: " + data)
result = json.loads(data)
print("token: " + result["response"]["serviceTicket"])
http1 = HTTPClient()
http1.onDone(onHTTPDone)
http1.open(getUrl);
http2 = HTTPClient()
http2.onDone(onHTTPDone)
postHeader = {}
postHeader['content-type'] = 'application/json'
postHeader['x-auth-token'] = result["response"]["serviceTicket"]
http2.postWithHeader(postUrl, postData, json.dumps(postHeader));
def main():
http = HTTPClient()
http.onDone(gotToken)
http.postWithHeader(securityUrl, securityData, securityHeader)
# don't let it finish
while True:
sleep(3600)
if __name__ == "__main__":
main()
</pre>
<br/>
</div>
<div tabindex="0">
<p class="MainHeading3">Example: Python Scripting in Programming Tab Using 'requests' Module</p>
</div>
<div tabindex="0">
A popular way to interact with web APIs in Python is to use a <em>requests</em> module. PT Programming Tab provides this module as a built-in.
Sample file <strong>programming_with_python_requests.pkt</strong> provides such an example, which is shown below<br/>
<pre class="code" >
from http import *
from time import *
import json
import requests
getUrl = "http://10.1.1.2/api/v1/inventory/network-device/count"
postUrl = "http://10.1.1.2/api/v1/flow-analysis"
securityUrlReq = "http://10.1.1.2/api/v1/ticket"
securityDataReq = {"username": "test","password": "test"}
securityHeaderReq = {"content-type": "application/json"}
postDataReq = { "sourceIP": "10.1.1.1", "destIP": "10.1.1.1" }
def main():
print( "Getting a ticket ..." )
r = requests.post(securityUrlReq, data=json.dumps(securityDataReq), headers=securityHeaderReq, timeout=30)
print( r.status_code )
result = r.json()
print( result )
ticket = result["response"]["serviceTicket"]
print("ticket: " + ticket)
print( "Access without a ticket ..." )
r = requests.get(getUrl)
print( "OK: %s"%(r.ok,) )
print( r.text )
print( "Access using a ticket ..." )
postHeader = { 'x-auth-token' : ticket }
r = requests.post(postUrl, json=postDataReq, headers=postHeader);
print( r.status_code )
print( r.json() )
# don't let it finish
while True:
sleep(3600)
if __name__ == "__main__":
main()
</pre>
<br/>
</div>
<div tabindex="0">
<p class="MainHeading3">Real World Access</p>
</div>
<div tabindex="0">
As briefly mentioned at the beginning of this page, users can also access Network Controllers via HTTP REST API using real world tools like <em>curl</em> or <em>programs, written in a programming language of your choice</em>.
For this purpose, use <strong>Access Enabled</strong> to start/stop the HTTP server. Use <strong>HTTP Port</strong> edit box to set the server port. Note, that allowed port numbers range from 1024 to 65535. <strong>Server Status</strong> gives current status of the server.<br/>
<p>
When <strong>Enable External Access for Network Controller REST API</strong> is disabled in Preferences, the settings in this configuration panel will become <em>read-only</em>.
</p>
</div>
<p class="myPic">
<img src="images/config_NetworkController_RealWorld.PNG" width="837"/>
</p>
<br/>
<div tabindex="0">
Provided the real world HTTP port on the network is enabled and the server is listening on a port PORT, one can access network controller REST API using the following base URL:<br/>
<pre class="code">
http://localhost:PORT/api/v1
</pre>
<p>For the configuration settings above, for instance, the URL for adding a ticket will be: <br/><strong>http://localhost:58000/api/v1/ticket</strong></p>
<p><em>Note: For security purposes, Packet Tracer Network Controllers will only allow HTTP access from your real PC from the localhost. Remote connections will be refused.</em></p>
<br/>
</div>
<div tabindex="0">
<p class="MainHeading3">Example: Using <em>curl</em></p>
</div>
<div tabindex="0">
To simplify experiments with real world access to NC, first load a sample sample file <strong>netcon.pkt</strong> and enable the real world access port on the network controller. We assume below that the port is 58000, but you will need to use the value you have enabled if it is different. Now, switch to a CLI or terminal application on your host OS and enter the following at the prompt:<br/>
<pre class="code">
curl -X post localhost:58000/api/v1/ticket -H "content-type: application/json" --data "{\"username\":\"admin\",\"password\":\"cisco\"}"
</pre>
and you should be able to get a JSON response similar to
<pre class="code">
... curl statistics ...
{
"response": {
"idleTimeout": 900,
"serviceTicket": "NC-34-de50f79c8dab4bb4b478-nbi",
"sessionTimeout": 3600
},
"version": "1.0"
}
</pre>
<br/>
</div>
<div tabindex="0">
<p class="MainHeading3">Using <em>Python</em> scripts</p>
</div>
<div tabindex="0">
<p>The example above, using Python <em>requests</em> module inside Programming Tab, can be used as a template for using it in a real world access scenario. For this to work, you would need to change all URLs, used in that sample, to the URL style shown in the <em>curl</em> example above. This is left as an exercise for the user.</p>
<br/>
</div>
</body>
</html>