User Manual
Table Of Contents
- Cambium
- PMP 450 Planning Guide
- Accuracy
- Copyrights
- Restrictions
- License Agreements
- High Risk Materials
- Safety and regulatory information
- Contents
- List of Figures
- List of Tables
- About This Planning Guide
- PMP support website: http://www.cambiumnetworks.com/support
- Cambium main website: http://www.cambiumnetworks.com/
- Sales enquiries: solutions@cambiumnetworks.com
- Email support: support@cambiumnetworks.com
- Cambium Networks
- 3800 Golf Road, Suite 360
- Rolling Meadows, IL 60008
- Chapter 1: Product description
- Chapter 2: Planning considerations
- Regulatory planning
- Network migration planning
- Site planning
- Link planning
- Analyzing the RF Environment
- Selecting Sites for Network Elements
- Diagramming Network Layouts
- Grounding and lightning protection
- Configuration options for TDD synchronization
- Data network planning
- Security planning
- Isolating APs from the Internet
- Managing module access by passwords
- Filtering protocols and ports
- Port Lockdown
- Isolating SMs
- Filtering management through Ethernet
- Allowing management from only specified IP addresses
- Configuring management IP by DHCP
- Planning for airlink security
- Planning for RF Telnet Access Control
- Planning for RADIUS integration
- Planning for SNMP security
- Ordering components
- Chapter 3: Legal information
- Cambium Networks end user license agreement
- Acceptance of this agreement
- Definitions
- Grant of license
- Conditions of use
- Title and restrictions
- Confidentiality
- Right to use Cambium’s name
- Transfer
- Updates
- Maintenance
- Disclaimer
- Limitation of liability
- U.S. government
- Term of license
- Governing law
- Assignment
- Survival of provisions
- Entire agreement
- Third party software
- Hardware warranty
- Limit of liability
- Cambium Networks end user license agreement
- Chapter 4: Reference information
PMP 450 Planning Guide Glossary
VI
pmp-0047 (December 2012)
Term Definition
indiscards count
Field
How many inbound packets were discarded without errors that would have prevented
their delivery to a higher-layer protocol. (Some of these packets may have been
discarded to increase buffer space.)
inerrors count Field How many inbound packets contained errors that prevented their delivery to a higher-
layer protocol.
innucastpkts count
Field
How many inbound non-unicast (subnetwork-broadcast or subnetwork-multicast)
packets were delivered to a higher-layer protocol.
inoctets count Field How many octets were received on the interface, including those that deliver framing
information.
Intel A registered trademark of Intel Corporation.
inucastpkts count
Field
How many inbound subnetwork-unicast packets were delivered to a higher-layer
protocol.
inunknownprotos
count Field
How many inbound packets were discarded because of an unknown or unsupported
protocol.
IP Internet Protocol defined in RFC 791. The Network Layer in the TCP/IP protocol
stack. This protocol is applied to addressing, routing, and delivering, and re-assembling
data packets into the Data Link layer of the protocol stack. See
http://www.faqs.org/rfcs/rfc791.html
.
IP Address 32-bit binary number that identifies a network element by both network and host. See
also Subnet Mask.
IPv4 Traditional version of Internet Protocol, which defines 32-bit fields for data
transmission.
ISM Industrial, Scientific, and Medical Equipment radio frequency band, in the 900-MHz,
2.4-GHz, and 5.8-GHz ranges.
L2TP over IPSec Level 2 Tunneling Protocol over IP Security. One of several virtual private network
(VPN) implementation schemes. Regardless of whether Subscriber Modules have the
Network Address Translation feature (NAT) enabled, they support VPNs that are based
on this protocol.
Late Collision Field This field displays how many late collisions occurred on the Ethernet controller. A
normal collision occurs during the first 512 bits of the frame transmission. A collision
that occurs after the first 512 bits is considered a late collision. A late collision is a
serious network problem because the frame being transmitted is discarded. A late
collision is most commonly caused by a mismatch between duplex configurations at
the ends of a link segment.
Latency Tolerance Acceptable tolerance for delay in the transfer of data to and from a module.
Line of Sight Wireless path (not simply visual path) direct from module to module. The path that
results provides both ideal aim and an ideal Fresnel zone.