Ref.#
Feature
Test Description
Detailed Steps
Expected Results
1.1
VicSmart
Router
This test will establish baseline
speed for comparison
1.
To be completed by ST
Out of hours implement an onsite 2.
test where a device is plugged
directly into the Admin & Curric
3.
WAN ports on the router and some
speed tests conducted.
4.
Configure laptop with static IP address in
network range
Pass/Fail
Plug directly into curriculum port
Run ping test and internet speed tests
during and after school hours
Run Iperf test
http://broadband.doe.wan/bwtest/
5.
1.2
VicSmart
Router
-Latency
-Traffic Flow
This test will check latency and
network interfaces on router higher latencies may lead to a
perception of general network
slowness, especially when
browsing web pages involving the
loading of multiple images.
Test will also involve monitoring
traffic volume to and from the
router across the Wide Area
Network and compare results with
like schools checking for P2P
activity
1.
Log into BBportal
2.
Run router tools scripts for site
Vicsmart Link Latency 7.24ms during school time
No evidence of P2P traffic
Compared to “like” school which had latency of 10.64ms
PASS
Latency marginallylower than Department average of
approximately 8ms
1.3
VicSmart
Router
-NAT
- Configuration
on router
-Device failures
Test will check correct operation of 1. Log into BBportal
NAT configuration on the Vicsmart
router by attempting to connect to 2. Run router tools scripts for site
upstream proxy using vlan100 as
source interface and loopback200
(curriculum) interface.
Automatically check Configuration
on router
Test obtains a copy of the running
configuration, and check it for
correct configuration of the
following:
◦vlan (admin/curric) interfaces
◦loopback (internet/NAT) interfaces
◦access control lists, which govern
how traffic hitting an interface is
filtered
Review inbound and outbound
traffic volumes and check for
interruption in traffic which may
indicate device failures
Ref.# Feature
2.1
Test Description
Core and Edge
This test checks the link from VicSmart
Switch
router to Core Switch to ensure correct
Autonegotiation configuration of Speed, Duplex and Autonegotiation. Port statistics that show a
large amount of alignment errors, frame
check sequence (FCS), or late-collisions
errors, might mean a speed or duplex
mismatch.
Detailed Steps
1.
2.
3.
4.
5.
Log into web interface for
core switch
Review port statistics
Verify the status of all ports
on switch
Checked for Packet Error
Checked for Autonegotiation
and Network Interface Cards
Expected Results
Port Status OK
Bandwidth and Packet Error eg
A common issue occurs when duplex and
speed settings are mismatched between
two switches, between a switch and a
router, or between the switch and a
workstation or server. Mismatches can
happen when manually setting the speed
and duplex or from autonegotiation issues
between the two devices
2.2
2.3
Core and Edge
Switch
-STP Loops
-Ping times to
clients
Core and Edge
Switch
This test will check for Spanning Tree
Loops
STP loops can cause serious
performance issues that look like port or
interface problems.
1.
A unidirectional link can cause loops. It
occurs when the traffic sent by the switch
is received by the neighbor, but the traffic
from the neighbor is not received by the
switch. A broken cable, other cabling
problems, or a port issue could cause this
one-way communication.
4.
This checks for any evidence of fan
failures or overheating
2.
3.
Log into web interface for
core switch
Review port statistics
Checked for STP loops by
enabling UniDirectional Link
Detection
Ran ping
1. Log into web interface for core
switch
Check for POE and temperature issues eg
Pass/Fail
-Device
Performance
PoE (Power over Ethernet) utilization will
indicate if there
PoE Issues will cause WAPS to cycle up
and down. A console cable and SSH
session will reveal this behavior on a
WAP
2. Review port statistics
3. Checked for PoE, Fan and
temperature issues
4. Ran ping
Ref.# Feature
Test Description
Detailed Steps
Expected Results
3.1
Core Server
-Connectivity
Test to Check the auto negotiation settings
on servers and connectivity
Ran ping to users PC
1. Remotely Log into host web server
Control Panel > System > Device
Manager> Review NICs settings and
driver version
Run CMD and Ping core switch and ping
remote client
Auto-negotiation ?
Drivers Run ?
Ping is ?ms
Time for (9 MB file transfer)?
Test run on
Test Time: ?
line speed is ?
download speed is ?
3.2
Core Server
-Network
Monitor
Analysis of network traffic loss and
performance
Ping response
•Browser Provides statistics related to the
Computer Browser service, which is used to
browse network resources.
•Network Interface provides counters for all
network traffic sent to and from a single
network adapter. These counters are the
most reliable way to measure total network
utilization. Network Interface counters also
provide information about errors.
Server Provides statistics related to sharing
files and printers, including bandwidth used
and the number of errors. Use these
counters when troubleshooting file and
printer sharing from the server.
TCPv4 provide information about TCP
connections. Of particular interest for
troubleshooting are the Connection Failures,
Connections Active, and Connections
Established counters.
Remotely Log into host web server
Control Panel > System > Device
Manager> Review NICs settings and
driver version
Run CMD and Ping core switch and ping
remote client
Click Start, right-click Computer, and
then click Manage.
.Expand System Tools, expand
Performance, and then expand
Monitoring Tools. Click Performance
Monitor.
Add counters to the real-time graph by
clicking the green plus sign on the
toolbar.
Server NICs performance?
Checked DNS/DHCP errors and general
event log
Remotely Log into host web server
Run > eventvwr
DNS/DHCP folder
Monitoring via Performance monitor indicated ?
DNS/DHCP logs?
3.3
Core Server
Services
Ping results ?
Performance monitor counters during peak school
period (10am -11am) indicated ?
Pass/Fail
3.4
Core Server
Checked scheduled downloads of updates
Scheduled to ensure out of hours
Tasks
Ref.# Feature
Test Description
Detailed Steps
4.1
EduPass
Test to Check the auto
-Connectivity negotiation settings on
servers and
connectivity
Ran ping to users PC
Log into eduPaSS
Tools > Ping Test
4.2
EduPass
Network
logs
1.
Analysis of network
traffic loss and
performance to
examine proxy server
logs
This page contains a
collection of graphs
detailing traffic
conditions as recorded
by the server. For all
graphs, graphs show
traffic on the given
interface, in both the
incoming and outgoing
directions. The
maximum, minimum,
current and average
speed per second is
also displayed on a
graph by graph basis.
The data for these
graphs is correlated
every 30 minutes.
Remotely Log into host web server
Run > taskschd.msc
2.
Log into
EduPass
Review Server
status - traffic
graphs looking
for any extreme
fluctuation,
demands
Expected Results
When do pdates occur out of school hours on host
server?
Pass/Fail
4.3
EduPass
Services
4.4
EduPass
Checked scheduled
Device
downloads of updates
Performa to ensure out of hours
nce
Checked temperature
within normal
operating range
Check Proxy Services
performance
Checked memory
usage
1.
Log into EduPaSS
server
2. Validated Network
Settings
3. Checked cache
management
settings
4. Confirmed Proxy
access controls
5. Checked Time
settings
6. Checked expired
certificates
Reviewed usage logs of
your web proxy server.
Memory: This is the
output of the 'free'
command. It shows the
amount of memory used
for programs, disk buffers
or cache.
Disk usage: This shows
how the file systems of
the SmoothWall box are
set up. This is the output
of the Linux command df
-m.
Uptime and users: This is
the output of the 'w'
command. Shown is the
number of users logged
in (via ssh or the
console).
Interfaces: This is the
output of the 'ifconfig'
command. This shows
All performance setting at default level
network interface
information.
Routing: This shows the
routing table and is the
output of the Linux
command route -n.
4.5
EduPass
Checked WAP usage
WAP
statistics to monitor
Performa load on WAPS
nce
Ref.# Feature
5.1
Test Description
EduStar.Net Analysis of network
Controller
summary information
-Connectivity performance to
determine areas of
high connectivity and
issues with
WAPS Cisco WCS
Navigator monitors the
operational status (up
or down) of each
individual Cisco WCS
management platform
and can initiate
configurable alarms
when it detects that a
connected Cisco WCS
is nonoperational. Its
network summary
screen displays
outstanding alarms,
fault summaries, client
counts, and a status
Monitoring of WAP
traffics
Detailed Steps
3.
Log into WCS
for school and
review
outstanding
alarms, fault
summaries,
client counts,
and a status
count of each
Cisco WAP
during 3 low
peak and high
peak periods
Expected Results
Pass/Fail
count of each Cisco
WCS management
platform, including all
connected Cisco
Aironet lightweight
access points, Cisco
wireless LAN
controllers, Cisco
Wireless Location
Appliances, and
802.11 clients
Ref.# Feature
6.1
6.2
WAN WAP
Performance
WAN Client
Performance
Ref.# Feature
7.1
Client
Connectivity
Test Description
Detailed Steps
Expected Results
Test to check throughput and
coverage by measuring signal to
noise ratio
1.
Using notebook roam around school record S/N ratios and
record on map
Review results concentrating on increasing number of WAPS
in areas of high volume and adjusting for increased throughput
To be completed by ST
Test
1.
2.
3.
Log onto netbook
Record Capability of Wireless card (2.4 or 5 Ghz)
Run speedtest on wireless
To be completed by ST
Test Description
2.
Detailed Steps
Test to Check the auto negotiation
settings on servers and connectivity
Ran ping to users PC
Make adjustments for WAPS in areas
of high traffic volume
Expected Results
1.
Configure laptop with static IP
address in network range
2.
Plug directly into curriculum port
3.
Run ping test and internet speed tests
4. Ultranet access speed
Pass/Fail
Broadband Speed Test Results ?
Ping speed to router is ?ms
Ping Speed to google ?ms
Ultranet login time
Pass/Fail
7.2
Client
Connectivity
Analysis of network traffic loss and
performance
1.
2.
3.
4.
5.
Log into client Control Panel > System > Device Manager>
Review NICs settings and driver version
Run CMD and Ping core switch and ping remote client
Click Start, right-click Computer, and then click Manage.
.Expand System Tools, expand Performance, and then expand
Monitoring Tools. Click Performance Monitor.
Add counters to the real-time graph by clicking the green plus
sign on the toolbar.