Hughes Network Systems

AiReach Broadband 9000

Network Management
Engineering
Training Course

1 Network Engineering

HUGHES PROPRIETARY II

Course Outline

IP Addressing
Inband Network Management
Router Setup
Other Considerations

Complete Network Management details are available

from Hughes TAC. Request the document titled
AiReach Management Architecture

4 Network Engineering

HUGHES PROPRIETARY II

IP Addressing

5 Network Engineering

HUGHES PROPRIETARY II

Overview
The AiReach Broadband system uses all IP based
protocols for network management
Each hub site (one or more co-located HTs) has its
own subnet
Each sector that each HT controls has its own
subnet RTs within a sector are all on the same
subnet

6 Network Engineering

HUGHES PROPRIETARY II

Overview

7 Network Engineering

HUGHES PROPRIETARY II

Subnet Definitions
EMS subnet: This subnet is where the EMS Server, printers,
client workstations, router and other management center
equipment is located. Typically, this subnet is part of an existing
Data Communications Network (DCN).
Hub Subnet: This subnet is located in the Hub site and contains
all of the HTs and other transmission equipment. Backup HTs
must also have an IP address on the Hub subnet. If the minirouter and hub/switch are managed, they may also be assigned
an address on this subnet.
Air Interface (Sector) subnet: This subnet exists over the air
interface and contains the HT that controls the sector and the
RTs within the sector. This subnet exists only on the primary (or
active) HT; therefore, it is not required to allocate a subnet for
the backup HT.
Each HT acts as the gateway router for its sector.
8 Network Engineering

HUGHES PROPRIETARY II

Subnet Sizing
Hub Subnet:

Subnet (0) and broadcast address (all ones address)

HTs in the Hub Site
Routers, switches and other managed equipment
Technician PC (optional)
It is also suggested to leave room for Backup HTs in case
redundancy is to be added in the future.

Sector Subnet:
Selection of subnet size depends mostly on the number of
RTs per sector
HT that controls the sector must have one address on this
subnet
Sector subnets must be addressable from the EMS

Hub subnet and Sector subnets do not have to be

the same size
9 Network Engineering

HUGHES PROPRIETARY II

Example Subnet Allocations

10 Network Engineering

HUGHES PROPRIETARY II

Example Hub Subnet Host Assignment

11 Network Engineering

HUGHES PROPRIETARY II

Example Sector Subnet Host Assignment

12 Network Engineering

HUGHES PROPRIETARY II

AiReach Management Protocols

13 Network Engineering

HUGHES PROPRIETARY II

Network Management on AB9000

SNMP
Alarm Traps
Detail Status from EMS GUI

FTP
Configuration File
Statistics

BOOTP
IP address assignment

Summary Status (UDP)

Health and Status messages from HT/RT

BSD (UDP)
Broadcast from EMS to hub subnets
Informs HTs about current configuration and software to run

14 Network Engineering

HUGHES PROPRIETARY II

Network Management on AB9000

All network management communication from the EMS to
the network elements (HT and RT) is IP based
Protocol

Type

Direction

Port(s)

SNMP

UDP

Both

Standard

- 161, 162

FTP

TCP

Both

Standard

- 20, 21

Bootp

UDP

NE EMS

Standard

- 67, 68

Summary Status

UDP

NE EMS

Proprietary

- 5000 to 5003
- 5100 to 5102
- 5200 to 5202

BSD

UDP

EMS NE

Proprietary

- 5300

15 Network Engineering

HUGHES PROPRIETARY II

Inband Network Management

16 Network Engineering

HUGHES PROPRIETARY II

Network Management Connectivity

Inband vs. Out-of-band Network Management

R o u te r
E M S S e rv e r

R o u te r

In b a n d
N M C hannel

O u t-o f-b a n d
N M C h a n n e ls

E M S S e rv e r

B ackhaul

E x is t in g
D a ta
N e tw o rk

Backhaul

Backhaul
L in k

M odem
L e a s e d L in e

S w itc h /
M UX

HT

R o u te r

S w itc h /
M UX

RT

HT

H u b s a n d S e c to rs

17 Network Engineering

M odem

RT

H u b s a n d S e c to rs

HUGHES PROPRIETARY II

G -2 4 5 21 C
0 4 /2 3 /0 2

Out-of-Band Management
Default configuration of all new HTs
9800: LAN port 3 is reserved for NM 10BaseT
Useful if there is already a router or some other IP
based connection at the hub site

18 Network Engineering

HUGHES PROPRIETARY II

Inband Network Management

TDM

Support for PPP or Cisco HDLC

Bandwidth is configurable from 64K to 2MB
E1 port 1 is dedicated to NM or can share traffic
One HT acts as Gateway for multi-sector hub sites

ATM
Protocol or VC encapsulation
Configurable on STM-1/OC3c or E3/DS3 ports
Choice of Gateway HT (single NM PVC) or separate PVC for
each HT in multi-sector hub sites

VLAN
Dedicated VLAN for Network Management

HT Redundancy supported in all cases

19 Network Engineering

HUGHES PROPRIETARY II

TDM Inband Network Management

Management Traffic is carried over the same TDM network
as the user traffic - in-band
PPP link to router over E1.
Gateway HT at Hub Site can bridge IP traffic to other HTs
in the site.
If traffic is inserted on the NM E1, it must be extracted
with a TDM MUX prior to the router

20 Network Engineering

HUGHES PROPRIETARY II

ATM Inband Network Management

LAN traffic from the Hub Site is placed into an ATM PVC
using LAN to ATM Bridging
Gateway HT at Hub Site can bridge IP traffic to other
HTs in the site.

21 Network Engineering

HUGHES PROPRIETARY II

NM Capacity Considerations
The AiReach system can be managed with as little as
64kbps between the EMS and each Hub Site
The recommended minimum for small hub sites is
128kbps
For larger Hub Sites (for example four sector with
1:1 redundancy) 256kbps is recommended
Less bandwidth means:
Configurations and software will take longer to
download
EMS Detail Status & Control screens will be slower
Statistics upload will be slower

22 Network Engineering

HUGHES PROPRIETARY II

Router Setup

23 Network Engineering

HUGHES PROPRIETARY II

Router Setup
IP Directed Broadcast
Required for subnet directed broadcast messages
form EMS to each Hub site

BOOTP Forwarding
HTs send a BOOTP broadcast message to get IP
assigned
Router must forward to EMS

Routing Protocols
OSPF
Static Routes

24 Network Engineering

HUGHES PROPRIETARY II

BOOTP
BOOTP is a protocol similar to DHCP
HT and RT network elements use BOOTP to get their
IP addresses from the EMS
It is necessary to configure a helper address in the
DCN routers to route the BOOTP message from the
Hub Subnet to the EMS

25 Network Engineering

HUGHES PROPRIETARY II

Routing Protocol Support

Static Routing Highly Recommended
IRDP
Proxy ARP

OSPF Open Shortest Path First

OSPF region should only include Hub Router and HTs. Never
include the HTs in part of a large OSPF area.

The routing protocol is selected at the time of the EMS

Installation. It cant be changed once the first Hub site is
created in the database.
All Hubs in the network will use the same routing protocol.
Disable Spanning-tree and other proprietary protocols on
the interfaces used for AIReach.

26 Network Engineering

HUGHES PROPRIETARY II

Other Consideration

27 Network Engineering

HUGHES PROPRIETARY II

Other Things to Consider

NEVER communicate with the AiReach Network
Elements with anything other than the EMS.
Most Network Management solutions must be
specifically engineered to fit into the existing DCN
Router configurations
Firewall settings to allow required protocols
Transport Networks (where the in-band part is)

Support for the following should be part of your

enterprise computing solutions. If not, alternate
solutions may be required.
Time synchronization (NTP)
Full system backups
28 Network Engineering

HUGHES PROPRIETARY II

Northbound (OSS)

29 Network Engineering

HUGHES PROPRIETARY II

OSS Interface
The EMS includes an SNMP Interface that provides:
Alarm Forwarding
Service Configuration
Admin tasks reports, time sync, etc

MIB is available on EMS software release CD-ROM

Nokia NetAct OSS is supported
Refer to the following document for full details
AiReach Broadband 9000
Element Management System (EMS)
OSS Interface Control Document
HNS-13883

30 Network Engineering

HUGHES PROPRIETARY II

Network Management on AB9000

All network management communication from the EMS to
northbound interfaces (OSS) is IP based
Protocol

Type

Port(s)

SNMP

UDP

Standard

- 161, 162

FTP

TCP

Standard

- 20, 21

Standard

- 6000

X11

Others as required telnet, ntp, etc

31 Network Engineering

HUGHES PROPRIETARY II