1 | Advanced Registry Operations Curriculum |
---|
2 | Building Your Virtual NOC |
---|
3 | |
---|
4 | Notes: |
---|
5 | ------ |
---|
6 | * Commands preceded with "$" imply that you should execute the command as |
---|
7 | a general user - not as root. |
---|
8 | * Commands preceded with "#" imply that you should be working as root. |
---|
9 | * Commands with more specific command lines (e.g. "RTR-GW>" or "mysql>") |
---|
10 | imply that you are executing commands on remote equipment, or within |
---|
11 | another program. |
---|
12 | * If a command line ends with "\" this indicates that the command continues |
---|
13 | on the next line and you should treat this as a single line. |
---|
14 | |
---|
15 | Exercises Part I |
---|
16 | ---------------- |
---|
17 | |
---|
18 | 0. Log in to your PC or open a terminal window as the tladmain user. |
---|
19 | |
---|
20 | Some Items to Update in Trac |
---|
21 | ---------------------------- |
---|
22 | |
---|
23 | 1. http://localhost/trac/ |
---|
24 | ---------------------- |
---|
25 | |
---|
26 | Log in to the trac instance as the user "tldadmin" using the password given in |
---|
27 | class. |
---|
28 | |
---|
29 | Fill in a few items on the page... |
---|
30 | |
---|
31 | For instance, try creating an entry to describe the PCs in your subnet. In |
---|
32 | Trac click on "Edit this page" (after you've logged in) at the bottom of the page. |
---|
33 | Go down to the "Network Configuration" section and add some lines that look like this: |
---|
34 | |
---|
35 | * [wiki:PCsGroup1 Group 1 PCs] |
---|
36 | * [wiki:PCsGroup2 Group 2 PCs] |
---|
37 | * [wiki:Routers Routers] |
---|
38 | * [wiki:Switches Switches] |
---|
39 | |
---|
40 | You need the space before each "*" in order for the items to appear as bullets. |
---|
41 | |
---|
42 | Click on "Submit changes". You'll notice the new items are greyed out and have a question |
---|
43 | mark after them. If you click on one of the items you'll be presented with a new page. |
---|
44 | Click on the "Create this page" button and start adding in some information about any of |
---|
45 | the items. |
---|
46 | |
---|
47 | You can use the Network Diagram on the NOC for reference: |
---|
48 | |
---|
49 | http://noc/trac/wiki/NetDiagram |
---|
50 | |
---|
51 | To get more information about your PC, in a terminal window you can do some exploring: |
---|
52 | |
---|
53 | $ df -h [show size of partitions] |
---|
54 | $ fdisk -l [list partitions, see disk size] |
---|
55 | $ top [current running processes and installed RAM] |
---|
56 | $ less /proc/cpuinfo [CPU(s) type and speed] |
---|
57 | $ ifconfig [network interfaces and their addresses] |
---|
58 | |
---|
59 | That is probably enough information. If you wish to see all hardware recognized by |
---|
60 | Linux on your box you can read through the system startup message: |
---|
61 | |
---|
62 | $ dmesg | more |
---|
63 | |
---|
64 | 2. Explore Your Local Network |
---|
65 | -------------------------- |
---|
66 | |
---|
67 | If you are wondering just what is on your local network segment you can do some scanning |
---|
68 | using a tool like nmap. Naturally a tool like nmap is often seen as an attack or potential |
---|
69 | security breach, so use with care. |
---|
70 | |
---|
71 | The address ranges in the classroom are: |
---|
72 | |
---|
73 | Group 1: 192.168.5.128/27 |
---|
74 | Group 2: 192.168.5.160/27 |
---|
75 | Backbone: 192.168.17.0/24 |
---|
76 | |
---|
77 | See what's on your local subnet. Here are a few different ways: |
---|
78 | |
---|
79 | $ sudo nmap -sP 192.168.5.128/27 [use the address range that corresponds to your group] |
---|
80 | $ sudo nmap -v 192.168.5.128/27 |
---|
81 | $ sudo nmap -sV 192.168.5.128 [intensive, takes a while and looks like an attack] |
---|
82 | $ sudo nmap -O 192.168.5.128/27 [detect OS'es] |
---|
83 | |
---|
84 | Nmap is a complex tool. Take a look at it's man pages for some more information: |
---|
85 | |
---|
86 | $ man nmap |
---|
87 | |
---|
88 | If you are monitoring a network segment sometimes it can be useful to run an nmap scan on |
---|
89 | the segment as a reality check to verify that what is on the network is what you think |
---|
90 | should be there. |
---|