Specifications

Summit WM Getting Started Guide, Software Version 5.1 43
3 Physical ports configuration
This chapter describes how to configure the Summit WM Controller’s physical ports.
The topics in this chapter are organized as follows:
● Physical data ports overview
● Configuring physical data ports
Physical data ports overview
Port configuration defines the administrative state of each interface. By default, the data interface states
are disabled. You must enable each of the data interfaces individually. A disabled interface does not
allow data to flow (receive/transmit).
You can define the data ports to function as one of the following three types:
● Host Port – You must use a Host Port definition to connect the Access Points with dynamic routing
disabled. The dynamic routing is disabled to ensure that the port does not participate in dynamic
routing operations to advertise the availability of WM Access Domain Services (WM-AD) hosted by
the WM. Host ports may still be used as the target for static route definitions.
● Third-party AP Port – You must use a Third-party AP Port definition for a port to which you will be
connecting the third-party APs. The third-party APs must be deployed within a segregated network
for which the Summit WM Controller becomes the single point of access to the network. When you
define a port as the third-party AP port, the interface segregates the third-party AP from the
remaining network. Only one port can be configured for the third-party APs.
● Router Port – You must use a Router Port definition for a port that you will be connecting to an
upstream, next-hop router in the network. When you define a port as the router port, the system
knows that the particular interface is eligible to participate in dynamic routing protocol exchanges.
The Summit WM Controller supports OSPF as the dynamic routing protocol.
The Summit WM Controller is shipped from the factory with all of its data ports set-up as host ports.
You must set-up or configure how each port should function.
If the interface is directly attached to an existing VLAN trunking port, you must specify which VLAN
the port belongs to by tagging the VLAN ID to the port. When you tag the VLAN ID to the port, all
packets associated with the port would be tagged with the corresponding VLAN. This enables the
Summit WM Controller to directly connect to a VLAN network without the need to remove VLAN tags
at the connection port.
NOTE
Only the following models support VLAN:
• Summit WM2000 Controller
• Summit WM2000 Controller
• Summit WM20 Controller