TP-Link EAP225-Wall Omada Controller Software 3.0.5 Windows/Linux User Guide - Page 8

Determine the Network Topology, 1.1.1 Management on the local Network

Get TP-Link EAP225-Wall PDF manuals and user guides View all TP-Link EAP225-Wall manuals
Add to My Manuals
Save this manual to your list of manuals

Page 8 highlights

1.1 Determine the Network Topology There are two methods centrally manage EAPs via Omada Controller: ·Management on the Local Network ·Management via Cloud Access Determine your management method according to your need and refer to the following introductions to build your network topology. 1.1.1 Management on the local Network There are two kinds of network topologies to centrally manage EAPs on the local network: ·Omada Controller and EAPs are in the same subnet. ·Omada Controller and EAPs are in different subnets. Determine your management method according to your need and refer to the following introductions to build your network topology. Management in the Same Subnet If your Omada Controller and EAPs are in the same subnet, refer to the following network topology. A router acts as a DHCP server to assign IP addresses to EAPs and clients. Omada Controller should be installed on one host, which is called as Controller Host. The other hosts in the same LAN can access the Controller Host to manage the network. Taking the following topology as an example, you can enter "https://192.168.0.100:8043" in a web browser on Host B to visit the Omada Controller interface on Host A. It's recommended to set a static IP address to the Controller Host for the convenient login to the Omada Controller interface. 2

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
2
1.1
Determine the Network Topology
There are two methods centrally manage EAPs via Omada Controller:
·
Management on the Local Network
·
Management via Cloud Access
Determine your management method according to your need and refer to the following
introductions to build your network topology.
1.1.1
Management on the local Network
There are two kinds of network topologies to centrally manage EAPs on the local network:
·
Omada Controller and EAPs are in the same subnet.
·
Omada Controller and EAPs are in different subnets.
Determine your management method according to your need and refer to the following
introductions to build your network topology.
Management in the Same Subnet
If your Omada Controller and EAPs are in the same subnet, refer to the following network topology.
A router acts as a DHCP server to assign IP addresses to EAPs and clients. Omada Controller
should be installed on one host, which is called as Controller Host. The other hosts in the same
LAN can access the Controller Host to manage the network. Taking the following topology as an
example, you can enter “https://192.168.0.100:8043“ in a web browser on Host B to visit the Omada
Controller interface on Host A. It's recommended to set a static IP address to the Controller Host
for the convenient login to the Omada Controller interface.