timy/EduNetworkBuilder
timy/EduNetworkBuilder
0
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update Create_NetTests - more tests added

Tim Young 2017-08-11 18:28:48 +02:00
parent 70665c30e9
commit 7a9af78b1f
1 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
Create_NetTests.md

@ -16,16 +16,20 @@ The tests are:
* **NeedsRouteToNet** - The device needs a static route built for it. For example: Router0 needs a static route to 192.168.5.0 for this test to be marked as complete. * **NeedsRouteToNet** - The device needs a static route built for it. For example: Router0 needs a static route to 192.168.5.0 for this test to be marked as complete.
* **NeedsUntaggedVLAN ** - The device (switch / server) needs a vlan set up on it, and a specific port marked as "untagged" on a specific vlan. For example: Switch0 needs port 1 untagged on VLAN1 for this test to be marked as complete. * **NeedsUntaggedVLAN** - The device (switch / server) needs a vlan set up on it, and a specific port marked as "untagged" on a specific vlan. For example: Switch0 needs port 1 untagged on VLAN1 for this test to be marked as complete.
* **NeedsTaggedVLAN** - The device (switch / server) needs a vlan set up on it, and a specific port marked as "Tagged" on a specific vlan. For example: Switch0 needs port 1 Taggedon VLAN1 for this test to be marked as complete. * **NeedsTaggedVLAN** - The device (switch / server) needs a vlan set up on it, and a specific port marked as "Tagged" on a specific vlan. For example: Switch0 needs port 1 Taggedon VLAN1 for this test to be marked as complete.
* **NeedsForbiddenVLAN **- The device (switch / server) needs a vlan set up on it, and a specific port marked as "forbidden" on a specific vlan. For example: Switch0 needs port 1 forbiddenon VLAN1 for this test to be marked as complete. * **NeedsForbiddenVLAN**- The device (switch / server) needs a vlan set up on it, and a specific port marked as "forbidden" on a specific vlan. For example: Switch0 needs port 1 forbiddenon VLAN1 for this test to be marked as complete.
* **SuccessfullyPings** - You need to successfully do a ping from one device to another. This ensures that the network routing between the devices is all set up and functional. This is probably the most-used test. For example: PC0 needs to successfully ping PC1 for this test to be marked as complete
* **SuccessfullyPingsAgain** - This was mainly added for the "network loop" test, showing how switches learned the mac address of the device at the far end and learned a "path" to it (when using spanning tree protocol). The second ping goes along the path without a spray of packets taking down the network. You may have other uses for this, but it will not happen much. Example: PC0 sucessfully pings again PC1 for this test to be complete.
* **SuccessfullyArps** - Arp is not used much in this. Initially, EduNetworkBuilder actually used ARP to find the MAC address of local machines. While it was true to life, it was very confusing to people. So ARP is currently relegated to the background. But, the test is still here. You can right-click and do an ARP test on something if you want. And, this test will be successful when you successfully do it. Example: PC0 successfully does an ARP request for PC1.
* **SuccessfullyDHCPs** - This test succeeds when a computer successfully gets a DHCP IP address from the specified server, firewall, etc.
* SuccessfullyPings,
* SuccessfullyPingsAgain,
* SuccessfullyArps,
* SuccessfullyDHCPs,
* HelpRequest, * HelpRequest,
* ReadContextHelp, * ReadContextHelp,
* FailedPing, * FailedPing,