0% found this document useful (0 votes)
121 views23 pages

NET201 Lab Experiment # 2 - Configuring and Troubleshooting VLANs and Trunking

This document outlines the procedures for a laboratory exercise on configuring and troubleshooting VLANs and trunking. The objectives are to build a network topology, create VLANs on two switches and assign ports, configure an 802.1Q trunk between the switches, delete the VLAN database, and troubleshoot VLANs. The scenario involves using VLANs and trunks to separate broadcast domains and allow communication between VLANs on different switches.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
121 views23 pages

NET201 Lab Experiment # 2 - Configuring and Troubleshooting VLANs and Trunking

This document outlines the procedures for a laboratory exercise on configuring and troubleshooting VLANs and trunking. The objectives are to build a network topology, create VLANs on two switches and assign ports, configure an 802.1Q trunk between the switches, delete the VLAN database, and troubleshoot VLANs. The scenario involves using VLANs and trunks to separate broadcast domains and allow communication between VLANs on different switches.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 23

NET201: Networking with Lab 2

Configuring and Troubleshooting VLANs and Trunking


Laboratory Exercise # 2

GRADE

Group No. : ____ Signature

Leader : SURNAME, First Name Middle Initial. ___________________


Members :
SURNAME, First Name Middle Initial. ___________________
SURNAME, First Name Middle Initial. ___________________

Date Performed : Day Month Year


Date Submitted : Day Month Year

Engr. Ricrey E. Marquez, CpE, MSCS


(Lab Instructor)
OBJECTIVES AND MATERIALS

Objectives:

After this laboratory, students should be able to:

1. build the network and configure basic device settings,


2. create VLANs and assign switch ports,
3. maintain VLAN port assignments and the VLAN database,
4. configure an 802.1Q trunk between the switches,
5. delete the VLAN database, and
6. troubleshoot VLAN.

Materials:

QUANTITY PART DESCRIPTION


NUMBER
Working Personal Computer (PC)
1 - with Installed Cisco Packet Tracer
Software

Scenario:

Modern switches use virtual local-area networks (VLANs) to improve


network performance by separating large Layer 2 broadcast domains into smaller
ones. VLANs can also be used as a security measure by controlling which hosts
can communicate. In general, VLANs make it easier to design a network to
support the goals of an organization.
VLAN trunks are used to span VLANs across multiple devices. Trunks
allow the traffic from multiple VLANS to travel over a single link, while keeping
the VLAN identification and segmentation intact.
In this lab, you will create VLANs on both switches in the topology, assign
VLANs to switch access ports, verify that VLANs are working as expected, and
then create a VLAN trunk between the two switches to allow hosts in the same
VLAN to communicate through the trunk, regardless of which switch the host is
actually attached to.

Note: The switches used are Cisco Catalyst 2960s with Cisco IOS Release
15.0(2). Other switches and Cisco IOS versions can be used. Depending on the
model and Cisco IOS version, the commands available and output produced
might vary from what is shown in the labs. Also, ensure that the switches have
been erased and have no startup configurations.
PROCEDURES

PART 1 – Configuring VLANs and Trunking

Task 1. Build the Network and Configure Basic Device Settings.


1. Cable the network topology as shown in Figure 2.1 using Packet Tracer network
simulator software.
2. Initialize and reload the router and switch. Note: If configuration files were
previously saved on the router or switch, initialize and reload these devices back
to their default configurations (Reminders: Capture all the outputs since they
part of your data results).
3. Configure basic settings for each switch.
3.1. Console into the switch and enter global configuration mode.
3.2. Execute the basic configuration on each switch such as:
a. Configure the host name as shown in the topology,
b. Disable IP domain lookup,
c. Enable password encryption,
d. Provide enable password (DCE_SW = “dce”, DBA_SW = “dba”)
e. Include message of the day banner (DCE_SW = “This is DCE office,
unauthorized access is strictly prohibited” and DBA_SW = “This DBA
office, unauthorized access is strictly prohibited”)
f. Provide a password for console 0 and virtual terminal type 0 to 15 during
login (DCE_SW = “dcesilver” and DBA_SW = “dbatiger”)
3.3. Configure the IP address listed in the addressing table presented in Table
2.1 for VLAN 1 on the switch.
3.4. Administratively deactivate all unused ports on the switch.
3.5. Copy the running configuration to the startup configuration.
4. Configure PC hosts (Refer to the addressing table (Table 2.1) for PC host
address information)
5. Test connectivity. Verify that the PC hosts can ping one another.
5.1. Can DBA-PC ping DCE-PC1? (yes/no) _____
5.2. Can DBA-PC ping DCE-PC2? (yes/no) _____
5.3. Can DBA-PC ping DBA_SW VLAN1? (yes/no) _____
5.4. Can DCE-PC1 ping DCE-PC2? (yes/no) _____
5.5. Can DCE-PC1 ping DCE_SW VLAN1? (yes/no) _____
5.6. Can DCE-PC2 ping DCE_SW VLAN1? (yes/no) _____
5.6. Can DBA_SW and DCE_SW VLAN1’s? (yes/no) _____

If you answered no to any of the above questions, why were the pings
unsuccessful?
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________

Task 2. Create VLANs and Assign Switch Ports


In task 2, you will create STUDENT, FACULTY, and MANAGEMENT VLANs on both
switches. You will then assign the VLANs to the appropriate interface. The show VLAN
command is used to verify your configuration settings.
1. Create VLANs on the switches.
1.1. Create the VLANs on DBA_SW.
1.2. Create the same VLANs on DCE_SW.
1.3. Issue the show vlan command to view the list of VLANs on DBA_SW.
1.4. Repeat (c) to view the list of VLANs on DCE_SW.

What is the default VLAN? ___________


What ports are assigned to the default VLAN?
________________________________________________________________
________________________________________________________________
________________________________________________________________

2. Assign VLANs to the correct switch interfaces.


2.1. Assign DBA-PC to the STUDENT VLAN.
DBA_SW> en
DBA_SW# conf t
DBA_SW(config)# int fa0/6
DBA_SW(config-if)# switchport mode access
DBA_SW(config-if)# switchport access vlan 10
DBA_SW(config-if)# end
DBA_SW#

2.2. Move the switch IP address VLAN 99 (MANAGEMENT VLAN).


DBA_SW> en
DBA_SW# conf t
DBA_SW(config)# int vlan 1
DBA_SW(config-if)# no ip add
DBA_SW(config-if)# int vlan 99
DBA_SW(config-if)# ip add 192.168.1.11 255.255.255.0
DBA_SW(config-if)# end
DBA_SW#

3. Issue the show vlan brief command and verify that the VLANs are assigned
to the correct interfaces.

4. Issue the show ip interface brief command.

What is the status of VLAN 99? Why?


________________________________________________________________
________________________________________________________________

5. Use the network topology to assign VLANs to the appropriate ports on DCE_SW.
6. Remove the IP address for VLAN 1 on DCE_SW.
7. Configure an IP address for VLAN 99 on DCE_SW according to the addressing
table in Table 2.1.
8. Use the show vlan brief command to verify that the VLANs are assigned to
the correct interfaces.
9. Verify the connectivity using ping command and observe the output.
Is DBA-PC able to ping DCE-PC1? Why?
________________________________________________________________
________________________________________________________________
Is DBA_SW able to ping DCE_SW? Why?
________________________________________________________________
________________________________________________________________

Task 3. Maintain VLAN Port Assignments and the VLAN Database


In task 3, you will change VLAN assignments to ports and remove VLANs from the
VLAN database.
1. Assign a VLAN to multiple interfaces.
1.1. On DBA_SW, assign interfaces from fa0/11 to fa0/24 to VLAN 10 using int
range command.
1.2. Issue the show vlan brief command to verify VLAN assignments.
1.3. Reassign Fa0/11 and Fa0/21 to VLAN 20.
1.4. Use show vlan brief to verify that VLAN assignments are correct.
2. Remove a VLAN assignment from an interface.
2.1. Use the no switchport access vlan command to remove the VLAN
10 assignment to Fa0/24.
DBA_SW> en
DBA_SW# conf t
DBA_SW(config)# int fa0/24
DBA_SW(config-if)# no switchport access vlan
DBA_SW(config-if)# end

2.2. Use show vlan brief to verify that the VLAN change was made.
Which VLAN is Fa0/24 now associated with?
____________________________________________________________
____________________________________________________________
3. Remove a VLAN ID from the VLAN database.
3.1. Add VLAN 30 to interface Fa0/24 without issuing the VLAN command.
DBA_SW> en
DBA_SW# conf t
DBA_SW(config)# int fa0/24
DBA_SW(config-if)# switchport access vlan 30
DBA_SW(config-if)# end

Note: Current switch technology no longer requires that the vlan command be
issued to add a VLAN to the database. By assigning an unknown VLAN to a port,
the VLAN adds to the VLAN database.

3.2. Verify that the new VLAN is displayed in the VLAN table.
What is the default name of VLAN 30?
____________________________________________________________

3.3. In the global configuration mode, issue a no vlan 30 command to


remove VLAN 30 from the VLAN database.
3.4. Issue the show vlan brief command. Fa0/24 was assigned to VLAN
30.
____________________________________________________________
Note: Before removing a VLAN from the database, it is recommended that you
reassign all the ports assigned to that VLAN.

Why should you reassign a port to another VLAN before removing the VLAN
from the VLAN database?
________________________________________________________________
________________________________________________________________
________________________________________________________________

Task 4. Configure an 802.1Q Trunk Between the Switches


In task 4, you will configure interface Fa0/1 of DBA_SW to use the Dynamic Trunking
Protocol (DTP) to allow it to negotiate the trunk mode. After this has been accomplished
and verified, you will disable DTP on interface Fa0/1 and manually configure it as a
trunk.
1. Use DTP to initiate trunking on Fa0/1.
The default DTP mode of a 2960 switch port is dynamic auto. This allows
the interface to convert the link to a trunk if the neighboring interface is set to
trunk or dynamic desirable mode.
1.1. Set Fa0/1 on DBA_SW to negotiate trunk mode.
DBA_SW> en
DBA_SW# conf t
DBA_SW(config)# int f0/1
DBA_SW(config-if)# switchport mode dynamic desirable
DBA_SW(config-if)# end
DBA_SW#

Note: You should also receive link status messages on DCE_SW. Check this in
DCE_SW command-line interface (CLI).

1.2. Issue the show vlan brief command on DBA_SW and DCE_SW.
Interface Fa0/1 is no longer assigned to VLAN 1. Trunked interfaces are not
listed in the VLAN table.
1.3. In the global configuration mode, issue the show interfaces trunk
command to view trunked interfaces on each switch. Notice that the mode
on DBA_SW is set to desirable, and the mode on DCE_SW is set to auto.

Note: By default, all VLANs are allowed on a trunk. The switchport trunk
command allows you to control what VLANs have access to the trunk. For this
lab, keep the default settings which allows all VLANs to traverse Fa0/1.

1.4. Verify that VLAN traffic is traveling over trunk interface Fa0/1.
a. Can DBA_SW ping DCE_SW? (yes/no) _____
b. Can DBA-PC ping DCE-PC1? (yes/no) _____
c. Can DBA-PC ping DCE_PC2? (yes/no) _____
d. Can DCE-PC1 ping DCE-PC2? (yes/no) _____
e. Can DBA-PC ping DBA_SW? (yes/no) _____
f. Can DCE-PC1 ping DCE_SW? (yes/no) _____
g. Can DCE_PC2 and DCE_SW? (yes/no) _____

If you answered no to any of the above questions, explain below.


________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________
________________________________________________________________

2. Manually configure trunk interface Fa0/1.


The switchport mode trunk command is used to manually configure a
port as a trunk. This command should be issued on both ends of the link.
2.1. Change the switchport mode on interface Fa0/1 to force trunking. Make
sure to do this on both switches.
DBA_SW> en
DBA_SW# conf t
DBA_SW(config)# int fa0/1
DBA_SW(config-if)# switchport mode trunk
DBA_SW(config-if)# end
DBA_SW#
2.2. Issue the show interfaces trunk command to view the trunk mode in
DCE_SW. Notice that the mode changed from desirable to on.

Why might you want to manually configure an interface to trunk mode instead of
using DTP?
________________________________________________________________
________________________________________________________________
________________________________________________________________

Task 5. Delete the VLAN Database


In task 5, you will delete the VLAN Database from the switch. It is necessary to do
this when initializing a switch back to its default settings.
1. Determine if the VLAN database exists. Issue the show flash command to
determine if a vlan.dat file exists in flash.
Note: If there is a vlan.dat file located in flash, then the VLAN database does not
contain its default settings.
2. Delete the VLAN database.
DBA_SW> en
DBA_SW# delete vlan.dat
Delete filename [vlan.dat]?
Delete flash:/vlan.dat? [confirm]
DBA_SW#

DCE_SW> en
DCE_SW# delete vlan.dat
Delete filename [vlan.dat]?
Delete flash:/vlan.dat? [confirm]
DCE_SW#

3. Issue the show flash command to verify that the vlan.dat file has been
deleted.
To initialize a switch back to its default settings, what other commands are
needed?
________________________________________________________________
________________________________________________________________
________________________________________________________________
4. Save your Packet Tracer file as NET201 Lab 2a – Group#

PART 2 – Troubleshooting VLAN Configurations

Task 1. Build the Network and Configure Basic Device Settings


In task 1, you will set up the network topology and configure the switches with some
basic settings, such as passwords and IP addresses. Preset VLAN-related
configurations, which contain errors, are provided for you for the initial switch
configurations. You will also configure the IP settings for the PCs in the topology.
1. Cable the network topology as shown in Figure 2.2.
2. Configure PC hosts.
3. Initialize and reload the switches as necessary.
4. Configure basic settings for each switch.
4.1. Disable DNS lookup.
4.2. Configure the IP address according to the addressing table in Table 2.2 and
Table 2.3.
4.3. Assign (“dcesilver” at DCE_SW and “dastegreen” at DASTE_SW) as the
console and vty passwords and enable login for console and vty lines.
4.4. Assign (“dce” at DCE_SW and “daste” at DASTE_SW) as the privileged
EXEC password.
4.5. Configure logging synchronous to prevent console messages from
interrupting command entry.
5. Load switch configurations. The configurations for the switches DCE_SW and
DASTE_SW are provided for you. There are errors within these configurations,
and it is your job to determine the incorrect configurations and correct them.
From global configuration mode, copy and paste the switch configuration below.
5.1. DCE switch with error configuration:
vlan 10
name STUDENTS
vlan 2
!vlan 20
name FACULTY
vlan 30
name GUEST
interface range fa0/1-24
switchport mode access
shutdown
!interface fa0/1
!switchport mode trunk
!no shutdown
interface range fa0/7-12
!interface range fa0/6-12
switchport access vlan 10
interface range fa0/13-18
switchport access vlan 2
!switchport access vlan 20
interface range fa0/19-24
switchport access vlan 30
end

5.2. DASTE switch with error configuration:


vlan 10
name STUDENTS
vlan 20
name FACULTY
vlan 30
name GUEST
interface fa0/1
switchport mode trunk
switchport trunk allowed vlan 1,10,2,30
!switchport trunk allowed vlan 1,10,20,30
interface range fa0/2-24
switchport mode access
shutdown
!interface range fa0/6-12
!switchport access vlan 10
interface range fa0/13-18
switchport access vlan 20
interface range fa0/19-24
switchport access vlan 30
shutdown
end

6. Copy the running configuration to the startup configuration.

Task 2. Troubleshoot VLAN 10


In task 2, you must examine VLAN 10 on DCE_SW and DASTE_SW to
determine if it is configured correctly. You will troubleshoot the scenario until connectivity
is established.
1. Troubleshoot VLAN 10 on DCE_SW.
1.1. Can DCE-PC ping DCE-PC1? (yes/no) _____
1.2. After verifying that DCE-PC was configured correctly, examine the
DCE_SW switch to find possible configuration errors by viewing a summary
of the VLAN information. Enter the show vlan brief command.
Are there any problems with the VLAN configuration?
________________________________________________________________

1.3. Examine the switch for trunk configurations using the show interfaces
trunk and the show interfaces fa0/1 switchport commands.

Are there any problems with the trunking configuration?


________________________________________________________________
1.4. Examine the running configuration of the switch to find possible
configuration errors. Are there any problems with the current configuration?

Are there any problems with the current configuration?


________________________________________________________________
________________________________________________________________

1.5. Correct the errors found regarding Fa0/1 and VLAN 10 on DCE_SW.
DCE_SW> en
DCE_SW# conf t
DCE_SW(config)# interface fa0/1
DCE_SW(config-if)# no shutdown
DCE_SW(config-if)# switchport mode trunk
DCE_SW(config-if)# interface fa0/6
DCE_SW(config-if)# no shutdown
DCE_SW(config-if)# switchport access vlan 10
DCE_SW(config-if)# end
DCE_SW#

1.6. Verify the commands had the desired effects by issuing the appropriate
show commands such as show interfaces trunk and show vlan
brief.

Can DCE-PC ping DASTE_PC1?


________________________________________________________________

2. Troubleshoot VLAN 10 on DASTE_SW.


2.1. Using the previous commands, examine the DASTE_SW switch to find
possible configuration errors.

Are there any problems with the current configuration?


________________________________________________________________

2.2. Correct the errors found regarding interfaces and VLAN 10 on


DASTE_SW.
DASTE_SW> en
DASTE_SW# conf t
DASTE_SW(config)# interface range fa0/6-12
DASTE_SW(config-if)# switchport access vlan 10
DASTE_SW(config-if)# interface fa0/11
DASTE_SW(config-if)# no shutdown
DASTE_SW(config-if)# end
DASTE_SW#

Can DCE-PC ping DASTE-PC1? (yes/no) _____

Task 3. Troubleshoot VLAN 20


In task 3, you must examine VLAN 20 on DCE_SW and DASTE_SW to
determine if it is configured correctly. To verify functionality, you will reassign DCE-PC
into VLAN 20, and then troubleshoot the scenario until connectivity is established.
1. Assign DCE-PC to VLAN 20.
1.1. On DCE-PC, change the IP address to 192.168.20.2 /24 with a default
gateway of 192.168.20.1.
1.2. On DCE_SW, assign the port for DCE-PC to VLAN 20. Execute the
commands needed to complete the configuration.
1.3. Issue a show vlan brief to verify that the port for DCE-PC has been
assigned to VLAN 20.
Can DCE-PC ping DASTE-PC2? (yes/no) Why?
________________________________________________________________
________________________________________________________________

2. Troubleshoot VLAN 20 on DCE_SW.


2.1. Using the previous commands, examine the DCE_SW switch to find
possible configuration errors.
Are there any problems with the current configuration?
________________________________________________________________
________________________________________________________________
________________________________________________________________
2.2. Correct the errors found regarding VLAN 20.
DCE> en
DCE_SW# conf t
DCE_SW(config)# no vlan 2
DCE_SW(config)# vlan 20
DCE_SW(config-vlan)# name FACULTY
DCE_SW(config)# int range fa0/13-18
DCE_SW(config-if-range)# switchport access vlan 20
DCE_SW(config-if-range)# end
DCE_SW#

Can DCE-PC ping DASTE-PC2? (yes/no) Why?


________________________________________________________________
________________________________________________________________
________________________________________________________________
3. Troubleshoot VLAN 20 on DASTE_SW.
3.1. Using the previous commands, examine the DASTE_SW switch to find
possible configuration errors.
Are there any problems with the current configuration?
________________________________________________________________
________________________________________________________________
3.2. Correct the errors found regarding VLAN 20. Issue the commands used
below.
DASTE_SW> en
DASTE_SW# conf t
DASTE_SW(config)# int fa0/18
DASTE_SW(config-if)# no shutdown
DASTE_SW(config-if)# exit
DASTE_SW(config)# int fa0/1
DASTE_SW(config-if)# switchport trunk allowed vlan remove 2
DASTE_SW(config-if)# switchport trunk allowed vlan add 20
DASTE_SW(config-if)# end
DASTE_SW#

Can DCE-PC ping DASTE-PC2? (yes/no) Why?


________________________________________________________________
________________________________________________________________
________________________________________________________________

Note: It may be necessary to disable the PC firewall to ping between PCs.

4. Save your Packet Tracer file as NET201 Lab 2b – Group#

NETWORK TOPOLOGY DIAGRAM

Figure 2.1. Switch environment network diagram for Part 1

Figure 2.2. Switch environment network diagram for Part 1


DATA RESULTS

Table 2.1. Summary of network device interface IP addresses


SUBNET DEFAULT
NETWORK DEVICE INTERFACE IP ADDRESS
ADDRESS GATEWAY
DBA_SW VLAN 1 192.168.1.11 255.255.255.0 NA
DCE_SW VLAN 1 192.168.1.12 255.255.255.0 NA
DBA-PC NIC 192.168.10.3 255.255.255.0 192.168.10.1
DCE-PC1 NIC 192.168.10.4 255.255.255.0 192.168.10.1
DCE-PC2 NIC 192.168.20.3 255.255.255.0 192.168.20.1

Table 2.2. Summary of network device interface IP addresses


SUBNET DEFAULT
NETWORK DEVICE INTERFACE IP ADDRESS
ADDRESS GATEWAY
DCE_SW VLAN 1 192.168.1.2 255.255.255.0 NA
DASTE_SW VLAN 1 192.168.1.3 255.255.255.0 NA
DCE-PC NIC 192.168.10.2 255.255.255.0 192.168.10.1
DASTE-PC1 NIC 192.168.10.3 255.255.255.0 192.168.10.1
DASTE-PC2 NIC 192.168.20.3 255.255.255.0 192.168.20.1

Table 2.3. Summary of Switch Port Assignment Specifications


INTERFACE PORT ASSIGNEMENT DEFAULT GATEWAY
Fa0/1 802.1Q Trunk NA
Fa0/6-12 VLAN 10 - STUDENTS 192.168.10.0 /24
Fa0/13-18 VLAN 20 - FACULTY 192.168.20.0 /24
Fa0/19-24 VLAN 30 - GUEST 192.168.30.0 /24

Part 1 - Configuring VLANs and Trunking

Task 1. Set Up the Topology and Initialize Devices (CLI commands, results, or
answers to some question)
Task 2. Configure Basic Device Settings and Verify Connectivity (CLI
commands, results, or answers to some question)

Task 3. Configure Basic Device Settings and Verify Connectivity (CLI


commands, results, or answers to some question)

Task 4. Configure Basic Device Settings and Verify Connectivity (CLI


commands, results, or answers to some question)

Task 5. Configure Basic Device Settings and Verify Connectivity (CLI


commands, results, or answers to some question)

Part 2 - Troubleshooting VLAN Configurations

Task 1. Set Up the Topology and Initialize Devices (CLI commands, results, or
answers to some question)

Task 2. Configure Basic Device Settings and Verify Connectivity (CLI


commands, results, or answers to some question)

Task 3. Configure Basic Device Settings and Verify Connectivity (CLI


commands, results, or answers to some question)
DATA ANALYSIS / OBSERVATIONS

NOTE: Discussion must be based on the data gathered from data results or
observation supported by review of literature with proper reference or author in-
text citation in APA format. Do not copy-paste instead paraphrase it. Data
analysis must be minimum of 2 pages.
QUESTIONS AND ANSWERS

Questions:

1. In Part 1 of your lab exercise, what is needed to allow hosts on VLAN


10 to communicate to hosts on VLAN 20?
2. What are the primary benefits that an organization can receive through
effective use of VLANs?
3. Why is a correctly configured trunk port critical in a multi-VLAN
environment?
4. Why would a network administrator limit traffic for specific VLANs on a
trunk port?

Answers:
CONCLUSION

NOTE: Discussion must be based on the lab objectives supported by review of


literature with proper reference or author in-text citation in APA format. Do not
copy-paste instead paraphrase it. Discuss the implication of findings per
objective (per paragraph). Conclusion must be minimum of 2 pages.
REFERENCES

NOTE: Sample APA format for reference cited only!

Books:

Andreasen, N. C. (2001). Brave new brain: Conquering mental illness in the era
of the genome. Oxford, England: Oxford University Press.

Copstead, L., & Banasik, J. (2005). Pathophysiology (3rd ed.). Philadelphia, PA:
Saunders.

Electronic Books:

Atkin, M. (Reporter). (2008, November 13). Bermagui forest disputed turf. The
Hack Half Hour. Retrieved from http://www.abc.net.au/triplej/hack/notes/

Cooper, D. (2009, March 31). Native ant may stop toad in its tracks. ABC
Science. Retrieved August 15, 2017 from http://www.abc.net.au/science/articles/
2009/03/31/2530686.htm?site=science&topic=latest

Print Journals:

Potente, S., Anderson, C., & Karim, M. (2011). Environmental sun protection and
supportive policies and practices: An audit of outdoor recreational settings in
NSW coastal towns. Health Promotion Journal of Australia, 22, 97-101.

Electronic Journals:

Jackson, D., Firtko, A., & Edenborough, M. (2007). Personal resilience as a


strategy for surviving and thriving in the face of workplace adversity: A literature
review. Journal of Advanced Nursing, 60(1), 1-9. doi:10.1111/j.1365-
2648.2007.04412.x

You might also like