2a Network Management

1 Network Engineering HUGHES PROPRIETARY II

Hughes Network Systems

AiReach Broadband 9000

Network Management Engineering

Training Course


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”

HUGHES PROPRIETARY II5 Network Engineering

IP Addressing


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


OverviewEMS

10.130.12.1

DCN

EMS Router

DCN router

Data Network

HS1HTA1 HS1HTD3

HS1A1RT1 HS1A1RTn

EMS subnet

Hub subnet

Sector subnet

10.130.12.0/24

10.130.12.254

10.41.0.30

10.41.0.0/27

10.41.0.24

10.41.0.1

(Note: router & hub/switch not shown for

simplicity)

...

...

10.41.0.16

10.41.1.30

10.41.1.1 10.41.1.n

10.41.1.0/27

E1

AIReach AirInterface


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 mini-router 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.


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


Example – Subnet Allocations

IP Address / 28 Subnet Purpose Sector Subnet (hex)10.41.0. 0-15 HS1 Hub subnet 0A.29.00.0010.41.0. 16-31 HS1 Sector A1 Air Link subnet A 0A.29.00.1010.41.0. 32-47 HS1 Sector B1 Air Link subnet B 0A.29.00.2010.41.0. 48-63 HS1 Sector C1 Air Link subnet C 0A.29.00.3010.41.0. 64-79 HS1 Sector D1 Air Link subnet D 0A.29.00.4010.41.0. 80-95 HS2 Hub subnet 0A.29.00.5010.41.0. 96-111 HS2 Sector A1 Air Link subnet A 0A.29.00.6010.41.0. … 0A.29.00.7010.41.0. 0A.29.00.8010.41.0. 0A.29.00.9010.41.0. 0A.29.00.A0

PMP IP Addressing Example

This example uses four host bits per subnet (/28 mask). This leaves enough room for 13 hosts per subnet. Subnet mask is FF.FF.FF.F0 (255.255.255.240)

The first five subnets are reserved for Hub Site 1. The next group of five subnets are reserved for Hub Site 2 and so on.

Assumptions:

3) Unstructured E1 service2) QPSK modulation on seach sector1) Y cable redundancy for each HT


Example – Hub Subnet Host Assignment

Hostname (Function) Sector10.41.0. 0 HS1 Hub subnet10.41.0. 1 HS1HTA110.41.0. 2 HS1HTA2 (Backup)10.41.0. 3 HS1HTB110.41.0. 4 HS1HTB2 (Backup)10.41.0. 5 HS1HTC110.41.0. 6 HS1HTC2 (Backup)10.41.0. 7 HS1HTD110.41.0. 8 HS1HTD2 (Backup)10.41.0. 910.41.0. 1010.41.0. 1110.41.0. 1210.41.0. 13 (hub/switch)10.41.0. 14 (mini-router)10.41.0. 15 Broadcast

C

D

IP Address / 28

HS1 LAN subnet

A

B


Example – Sector Subnet Host Assignment

10.41.0. 16 subnet subnet10.41.0. 17 HS1A1TS 110.41.0. 18 HS1A1TS 210.41.0. 19 HS1A1TS 310.41.0. 20 HS1A1TS 410.41.0. 21 HS1A1TS 510.41.0. 2210.41.0. 2310.41.0. 2410.41.0. 2510.41.0. 2610.41.0. 2710.41.0. 2810.41.0. 2910.41.0. 3010.41.0. 31 broadcast

HS1 Sector A1 Air Interface IP Address

IP Address / 28

HS1 Sector A1 Air Link subnet

Hostname


AiReach Management Protocols


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



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


Inband Network Management


Network Management Connectivity

EMS Server EMS Server

Router Router

Router

BackhaulExisting

DataNetw ork

Backhaul

BackhaulLink

Inband NM Channel

Out-of-band NM Channels

Switch/MUX

Switch/MUX

HT HTRT RT

G-24521 C04/23/02

Modem

Hubs and SectorsHubs and Sectors

ModemLeased Line

Inband vs. Out-of-band Network Management


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


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


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

E1 TDM NetworkDCN

NM Traffic

Hub Site

HTsEMS

LAN

Router Router w/E1 Interface

Router sub-interface has IP address on MS (Hub) LAN

PPP Bridged link carries IP NM traffic


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.

ATMNetwork

ATM

LAN

LAN

LAN

Hub Site

HT1

HT2

EMSATM

ATM

LAN

LAN Hub

ACU-HT P Gateway

User Traffic

EMS Router/ATM Switch

NM Traffic


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


Router Setup


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


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

Transport NetworkDCN

NM Traffic

Hub Site

HTEMS

IP 10.130.12.1

LAN

Hub Router

Step 1: HT Broadcasts BOOTP Request

Step 2: Router forwards BOOTP Request as unicast to EMS

Step 3: EMS unicasts BOOTP

Reply

Step 4: router sends BOOTP

Reply to HT

Router port with ip helper address 10.130.12.1


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 can’t 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.


Other Consideration


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


Northbound (OSS)


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



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

X11 Standard - 6000

Others as required – telnet, ntp, etc

2a Network Management

Documents

Transcript of 2a Network Management