CBRS Overview

The copyright of this document is the property of Nortel Networks. Without the written consent of Nortel Networks, given by contract or otherwise, this document must not be copied, reprinted or reproduced in any material form, either wholly or in part, and the contents of this document, or any methods or techniques available therefrom, must not be disclosed to any other person whomsoever.

EBSC/CBRS EBSC/CBRS Knowledge Transfer Knowledge Transfer NBSS 11.0NBSS 11.0

2

Course Description

EBSC/CBRS Discussion

This discussion is designed for technicians and other personnel requiring the knowledge needed to operate and maintain Nortel Network’s CBRS equipment.

Target audience

Engineers

Switch Technicians

Cell Site Technicians

3

Course Objectives

» Give a system level description of the CBRS Product

» Identify the new elements

» Recognize new and enhanced BCN services

» Discuss changes in the BSS Manager

» Understand MDM functions

» Describe the activities of the EBSC Configuration tool

4

Course Agenda

Day 1

» Lesson 1 - Overview

» Lesson 2 - Architecture

» Lesson 3 –BCN Services

» Lesson 4 – CBRS and the BSS Manager

Day 2

» Lesson 5 – CBRS and the Passport MDM

» Lesson 6 – EBSC Configuration tool

» Lesson 7 – Performance

» Lesson 8 – Alarms


Overview Overview

Lesson 1Lesson 1

6

Lesson 1 Objectives

» Discuss the functions of the CBRS product

» Explain the signal flow through the CBRS

» Identify the CBRS hardware components, shelves and boards

» Describe various CBRS migration paths/configurations

» Describe the timing for the CBRS

7

Product Evolution

SBSData

LPP

SBSVoice

CISBIU

CPDSCDMA Packet

DataSubsystem

CBRSCDMA Backhaul &

RoutingSubsystem

CSVSCDMA Selection &

VocodingSubsystem

CSISCDMA

SignalingSubsystem

BSC Products EBSC Products

8

CBRS (CDMA Backhaul Routing Subsystem)

» Supports layer two routing functions between CDMA subsystems

» Offers a scalable solution by supporting existing CDMA infrastructure

» Contains essential components for migration to full 3G

» Fully compatible with existing DISCO BSC and ATM BSC

9

EBSC/CBRS Enhancements

NORTEL CDMA CIS

TFU 1

TFU 2TFU 2

DISCO 1

DISCO 2

MSP

SBS CabinetBIU Cabinet CIS Cabinet

NORTEL CDMA BIU

CDSU 2

CDSU 1

CDSU 3

CDSU 4

GPSR GPSR

MSPNORTEL CDMA SBS

SBS 1

SBS 4

SBS 3

SBS 2

MSP

BSCBSC

0 1 2 4 6 7

8 9 10

11

13

14

15

EBSCTM EBSCTM

Cable Consolidation and

Multiplexer Chassis (CCMC)

CBRSCBRSTFU replaced by EBSCTMEBSCTM

DISCO replaced by 24pBCNW & 24pBCNW & 11pMSW 11pMSW Functional Functional ProcessorsProcessors

BIU replaced by 11pMSW 11pMSW Functional Functional ProcessorProcessor

24pBCNW FP

11pMSW FP CP3

10

EBSC/CBRS Enhancements

CBRS replaces the following:

» DISCO (Distribution and Consolidation Unit) replaced by 24pBCNW FP & 11pMSW FP

» TFU (Timing Frequency Unit) replaced by EBSCTM

» GPSR (Global Positioning Satellite Receiver) replaced by EBSCTM

» BIU (Backhaul Interface Unit) replaced by 11pMSW FP

» CDSU (Channel Service/ Data Service Unit) replaced by 11pMSW FP

11

CBRS Frame Elements

Breaker Interface Panel

EBSCTM

CCMC

Upper Shelf


EBSCTM EBSCTM

Filter Tray

Cable Trough

BCN and GPS timing to SBS per connector

P77

P78

P79

P80

P51

P52

P53

P54

P55

P56

P57

P58

P59

P60

P61

P62

P63

P64

P65

P66

P67

P68

P68

P70

P71

P72

P73

P74

P75

6 BC CardsP27

P28

P29

P30

P31

P32

P33

P34

P35

P36

P37

P38

P39

P40

P41

P42

P43

P44

P45

P46

P47

P48

P49

P50

6 T1 CardP76

CCMC

Cable Trough

Cable Trough

Cable Trough

0

7

81

1

1

38

1

4

1

515

Lower Shelf

Filter Tray

Cable Trough

CBRS

12

11 Port MultiService Wireless (11pMSW) Function Processor

» Two ports for a pair of DISCOs or BSS Managers – Optical interface (ports 9 & 10)

» One port for T1/E1 channels to BTS– Optical interface (port 8)

» Eight ports for T1 connections to LPP/CIU– Electrical interfaces (ports 0 thru 7)

» Provides APS redundancy to protect loss of signal due to optical line failure

» Configured in active/stand-by redundancy pairs» In a single-frame CBRS configuration, a maximum of

five 11pMSW FPs pairs can be used.» In the multi-frame CBRS configurations, only four

11pMSW FPs pairs can be used per frame. » These pairs are data filled in the following order 2&3,

8&9, 4&5, 10&11, 12&13

13

24 Port BCN Wireless (24pBCNW)

Function Processor» SBS Interface

– All connections to SBS are via CCMC

» Each pair serves up to 24 BCN links between CBRS and SBS

» The 24pBCNW FP interfaces include:– 24 RS-422 electrical ports for connectivity to the SBS

shelves.– 1 RS-485 serial port to EBSCTM.

» The 24pBCNW FP uses GPS timing reference to derive the even-second and chip clocks for the SBS.

» The 24pBCNW FP is provisioned in pairs 1+1 redundancy » The first pair must be installed in slots 6&7 of the

Passport 15000 frame to provide CDMA timing.» The second pair is located in slots 14&15 for growth.

14

Cable Consolidation and Multiplexing Chassis (CCMC)

» The Cable Consolidation and Multiplexing Chassis (CCMC) is located in the top half of the Passport 15000 frame.

» The CCMC manages the connectivity:– From the 24pBCNW FP to the SBS shelves.– From EBSCTM to the 24pBCNW FP.– From the LPP to the 11pMSW FP.

» One CCMC provides sparing for 48 BCN ports and 40 T1 ports.

» Two types of cards are deployed in CCMC:– 8-port BCN Multiplexer card to multiplex the

redundant 24pBCNW FP onto the SBS links.– 8-port T1 Multiplexer card to multiplex the

redundant 11pMSW FP onto the LPP links.

15

CCMC (Cable Consolidation and Multiplexer

Chassis)

BCN links to24pBCNW FP;Labeled P101 to P108

T1 links to 11pMSW FP;Labeled P81-P100

Six BCN cards:Back Connection:Links to SBSLabeled P5-P16

Six T1 cards: Back Connection:Links to LPP Labeled P17-P26

6 T1 Cards

BCN and GPS timing to SBS

P77

P78

P79

P80

P51

P52

P53

P54

P55

P56

P57

P58

P59

P60

P61

P62

P63

P64

P65

P66

P67

P68

P68

P70

P71

P72

P73

P74

P75

6 BCN Cards

P27

P28

P29

P30

P31

P32

P33

P34

P35

P36

P37

P38

P39

P40

P41

P42

P43

P44

P45

P46

P47

P48

P49

P50

P76

per connector

Active Switch Card Shelf

(OC-3 Express Form Factor)

P10

6P

108

P10

2P

104

P10

5P

107

P10

1P

103

P81 P

83

P85

P82 P84

P86

P91 P93

P95

P92

P94

P96

P87

P88

P97

P98

P89

P90

P99

P10

0

CCMCNTPB13AA

16

EBSCTM EBSC Time Module

The following services are provided by the EBSCTM to the CBRS:

» Source of frequency and timing reference signals– Global Positioning System (GPS) Receiver

» 9.8304 MHz frequency outputs to CBRS

» ½ Hz timing outputs

» 10MHz output as an optional BITS input

» ½ Hz output to synchronize test equipment

» 9.8304 MHz output to synchronize user test equipment

17

Timing on the EBSC/CBRS

» GPS timing– Provides timing to the SBS shelves for CDMA timing

– GPS connected to the EBSCTM in each CBRS frame

– 24pBCNW FP timing interface

– Existing legacy BSC GPS antennas can be used

» Network Timing– Provides time accuracy to the backhaul T1s

connected to CBRS

– External BITS source

– Stratum 3 or better

– Internal CP timing available but not recommended

18

CBRS Connectivity / Interfaces

CBRS Connectivity Interfaces Type

DISCO OC3c (11pMSW FP and/or 4pOC3 FP)

BSS Manager OC3c (11pMSW FP and/or 4pOC3 FP)

SBS DISCO and/or BCN (24pBCNW FP)

BTS DISCO, or

T1 to OC3 (11pMSW FP) via Add Drop

Multiplexer, orT1s (with IMH) to OC3 (11pMSW FP) via Add Drop

Multiplexer

CIU DISCO or T1 (11pMSW FP)

ISSHO OC3c (4pOC3 FP),

DS3 (12pDS3Atm FP),

T1 to OC3 (11pMSW FP) via Add Drop

Multiplexer,T1s (with IMH) to OC3 (11pMSW FP) via Add Drop

Multiplexer

BISC OC3c (4pOC3 FP) or OC12c (4pOC12 FP)

19

CDMA (CBRS) Network Block Diagram

10MB Ethernet

GPSBCN LinkT1/E1 (UnC)T1 (Chan)TimingOpticalEthernet

MTMTXX

DMS Bus

ENET

LPP

LPPor

FLIS

DMS Core

SLMComputing

Module

IOCMTM

OAU

DigitalTrunk

Controller

CCS7 Links

T1s

MDM/MDP

BSSM

PP15K

LAN

PDSN FA/HA

AnotherCBRS

BTS or MCBTS

Add Drop Multiplexer

DISCOs

Enhanced

SelectorCards1-12

SBS Shelf

SBSController

Card

SCI-S

SCI-S

CBRS CCMC

EBSCTMEBSCTM

11pM

SW

24pB

CN

W

CP3

4pOC-3

T-1VOICE

TRUNKS

20

Signal Flow through CBRST1

OC-3

T1

T1

BTS

SBS

PDSN FA/HA

CIU MTX

BCN

T1Add Drop Multiplexer

WWW

PSTN

11pMSW

24p BCNW

CCMC

OC-3

DISCO

BSS Manager

OR

BCN

T1

Passport

21

EBSC/CBRS Benefits

» Increased capacity of the BSC– With three frames CBRS delivers 3X capacity

increase over current BSC

» Increased capacity with a smaller physical footprint– Provides 2-10x footprint reduction

» Increased system reliability

» Increased backhaul efficiency with Inverse Multiplexing (IMH)

» Minimizes soft handoff border maintenance

22

New EBSC/CBRS Capacity

» A single 24pBCNW FP can support 4608 simultaneous voice calls plus 144 simultaneous data calls @153.6kbps

» A single CBRS frame can support 9216 simultaneous voice calls plus 288 simultaneous data calls @153.6kbps

» EBSC can be expanded to support 350-450 KBHCA (LPP limitation – call model dependent)

» With three frames, CBRS delivers up to 18K Erlangs and 1008 BTS T1 ports

» MDMs can support up to 30 PP15K chassis

» Each CBRS frame supports up to 48 SBS shelves and 336 T1 ports– For higher capacity, additional frames can be linked

23

EBSC/CBRS Standalone Configuration


EBSCTM EBSCTM

Filter Tray

Cable Trough


P77

P78

P79

P80

P51

P52

P53

P54

P55

P56

P57

P58

P59

P60

P61

P62

P63

P64

P65

P66

P67

P68

P68

P70

P71

P72

P73

P74

P75

6 BC CardsP27

P28

P29

P30

P31

P32

P33

P34

P35

P36

P37

P38

P39

P40

P41

P42

P43

P44

P45

P46

P47

P48

P49

P50

6 T1 CardP76

CCMC

Cable Trough

Cable Trough

Cable Trough

0

7

81

1

1

38

1

4

1

515


EBSCTM EBSCTM

Filter Tray

Cable Trough


P77

P78

P79

P80

P51

P52

P53

P54

P55

P56

P57

P58

P59

P60

P61

P62

P63

P64

P65

P66

P67

P68

P68

P70

P71

P72

P73

P74

P75

6 BC CardsP27

P28

P29

P30

P31

P32

P33

P34

P35

P36

P37

P38

P39

P40

P41

P42

P43

P44

P45

P46

P47

P48

P49

P50

6 T1 CardP76

CCMC

Cable Trough

Cable Trough

Cable Trough

0

7

81

1

1

38

1

4

1

515


EBSCTM EBSCTM

Filter Tray

Cable Trough


P77

P78

P79

P80

P51

P52

P53

P54

P55

P56

P57

P58

P59

P60

P61

P62

P63

P64

P65

P66

P67

P68

P68

P70

P71

P72

P73

P74

P75

6 BC CardsP27

P28

P29

P30

P31

P32

P33

P34

P35

P36

P37

P38

P39

P40

P41

P42

P43

P44

P45

P46

P47

P48

P49

P50

6 T1 CardP76

CCMC

Cable Trough

Cable Trough

Cable Trough

0

7

81

1

1

38

1

4

1

515

Hub

CBRS CBRS CBRS

24

Hybrid Configuration


EBSCTM EBSCTM

Filter Tray

Cable Trough


P77

P78

P79

P80

P51

P52

P53

P54

P55

P56

P57

P58

P59

P60

P61

P62

P63

P64

P65

P66

P67

P68

P68

P70

P71

P72

P73

P74

P75

6 BC CardsP27

P28

P29

P30

P31

P32

P33

P34

P35

P36

P37

P38

P39

P40

P41

P42

P43

P44

P45

P46

P47

P48

P49

P50

6 T1 CardP76

CCMC

Cable Trough

Cable Trough

Cable Trough

0

7

81

1

1

38

1

4

1

515

15K

0 1 2 3 4 5 6 7

8 9

10

11

12

13

14

15

ATM BSC

PP15000

15K

0 1 2 3 4 5 6 7

8 9

10

11

12

13

14

15

ATM BSC

PP15000

BSS Manager

4 DISCOBSC 01

4 DISCOBSC 02

CBRS

25

Hybrid UpgradeNew EBSC/CBRS in addition to ATM switch

» BSC 01 is upgraded to EBSC in a new CBRS frame– Equipped with new function processors– Equipped with CP3– Equipped with CCMC– Equipped with EBSCTM

» BSC 02 remains in ATM BSC frame– Can be upgraded separately later

» CBRS and ATM communicate via ISSHO» Move BSS Manager to new 11p FP on CBRS» Move designated DISCOs to EBSC» Move designated SBSs/BTSs to EBSC» Move network T1s from DISCO to EBSC

26

BSC to EBSC Configuration


EBSCTM EBSCTM

Filter Tray

Cable Trough


P77

P78

P79

P80

P51

P52

P53

P54

P55

P56

P57

P58

P59

P60

P61

P62

P63

P64

P65

P66

P67

P68

P68

P70

P71

P72

P73

P74

P75

6 BC CardsP27

P28

P29

P30

P31

P32

P33

P34

P35

P36

P37

P38

P39

P40

P41

P42

P43

P44

P45

P46

P47

P48

P49

P50

6 T1 CardP76

CCMC

Cable Trough

Cable Trough

Cable Trough

0

7

81

1

1

38

1

4

1

515

15K

0 1 2 3 4 5 6 7

8 9

10

11

12

13

14

15

ATM BSC

PP15000

4 DISCOs

CBRS

27

BSC to EBSC Upgrade(Single BSC)

» Upper chassis of ATM BSC must be vacant

» Existing ATM frame upgraded to CBRS frame– Equipped with new function processors

– Equipped with CP3

– Equipped with CCMC

– Equipped with EBSCTM

» Move BSS Manager to new 11p FP on CBRS

» Move SBSs/BTSs to EBSC

» Move DISCOs to EBSC

» Move network T1s from DISCO to EBSC

28

Dual BSC Configuration

15K

0 1 2 3 4 5 6 7

8 9

10

11

12

13

14

15

ATM BSC

PP15000


EBSCTM EBSCTM

Filter Tray

Cable Trough


P77

P78

P79

P80

P51

P52

P53

P54

P55

P56

P57

P58

P59

P60

P61

P62

P63

P64

P65

P66

P67

P68

P68

P70

P71

P72

P73

P74

P75

6 BC CardsP27

P28

P29

P30

P31

P32

P33

P34

P35

P36

P37

P38

P39

P40

P41

P42

P43

P44

P45

P46

P47

P48

P49

P50

6 T1 CardP76

CCMC

Cable Trough

Cable Trough

Cable Trough

0

7

15K8 9

10

11

12

13

14

15

4 DISCOsBSC 02

4 DISCOsBSC 01

CBRS

29

Dual BSC Configuration1 Legacy BSC and 1 EBSC in single frame

» Only 1 BSC in ATM switch can be upgraded to EBSC

» Upper chassis of ATM BSC must be vacant

» Upper chassis is upgraded with– CCMC

– EBSCTM

» External OC-3 loop back required for ISSHO support

» Recommended for short term deployment only– E.g. when consolidating BSCs into a larger EBSC

30

Two DISCO Back-to-Back Configuration

CBRS


EBSCTM EBSCTM

Filter Tray

Cable Trough


P77

P78

P79

P80

P51

P52

P53

P54

P55

P56

P57

P58

P59

P60

P61

P62

P63

P64

P65

P66

P67

P68

P68

P70

P71

P72

P73

P74

P75

6 BC CardsP27

P28

P29

P30

P31

P32

P33

P34

P35

P36

P37

P38

P39

P40

P41

P42

P43

P44

P45

P46

P47

P48

P49

P50

6 T1 CardP76

CCMC

Cable Trough

Cable Trough

Cable Trough

0

7

81

1

1

38

1

4

1

515

2 DISCOs


ArchitectureArchitecture

Lesson 2Lesson 2

32

Lesson 2 Objectives

» Describe the Passport 15000 adaptation of the CBRS

» Identify the functions of the 11pMSW FP

» Identify the functions of the 24pBCNW FP

» Describe the EBSCTM function

» Explain CDMA timing on the CBRS

» Identify the connections on the CCMC

33

Passport 15000

Front View

Power feed connectors

Rear cooling unit

Front cooling unit

Fabric card x

Fabric card y

Alarm/BITS cardMAC Address card

Lower Chassis

Upper Chassis

Rear View

34

Passport 15000 Features

» High capacity switch

» Greater scalability

» Advanced traffic management

» Multi-purpose switch supporting voice, video and data– In BSC acts as simplified ATM core router

– Allows for co-residency of CBRS and ATM BSC applications

» Fabric cards allow for inter-card communication

» Support for– Electrical and optical interfaces

– BCN Wireless functions

– BTS or T1 ISSHO traffic

– OA&M functions

– Alarm/BITS modules

35

CBRS Application on the PP15K


CBRS


EBSCTM EBSCTM

Filter Tray

Cable Trough


P77

P78

P79

P80

P51

P52

P53

P54

P55

P56

P57

P58

P59

P60

P61

P62

P63

P64

P65

P66

P67

P68

P68

P70

P71

P72

P73

P74

P75

6 BC CardsP27

P28

P29

P30

P31

P32

P33

P34

P35

P36

P37

P38

P39

P40

P41

P42

P43

P44

P45

P46

P47

P48

P49

P50

6 T1 CardP76

CCMC

Cable Trough

Cable Trough

Cable Trough

0

7

81

1

1

38

1

4

1

515

EBSCTM

CCMC

Filter Tray

Cable Trough

CP3 24pBCNW FP

4pOC3 or 11pMSW FP

11pMSW FP

36

CBRS Application on the PP15K» The top chassis contains:

– The CCMC (Cable Consolidation and Multiplexer Chassis)

– Two EBSCTMs (EBSC Time Module)– An EBIP (Enhanced Breaker Interface Panel)– A Fiber Management Panel

» The lower chassis consists of two shelves which include:– Two control processors (CP3)

• Upper shelf card slot 0&1

– Up to fourteen function processors (FPs)• 11pMSW (5 pairs maximum – both shelves)• 24pBCNW (2 pairs maximum – both shelves)• 4p/12pOC-3 (1 pair- lower shelf)

– Two fabric modules– Alarm/BITS module– MAC address module

37

11pMSW FP Connections in the CBRS

CBRS


EBSCTM EBSCTM

Filter Tray

Cable Trough


P77

P78

P79P80

P51P52

P53

P54P55

P56P57

P58

P59P60

P61P62

P63

P64P65

P66P67

P68

P68P70

P71P72

P73

P74P75

6 BC CardsP27

P28

P29

P30

P31

P32

P33

P34

P35

P36

P37

P38

P39

P40

P41

P42

P43

P44

P45

P46

P47

P48

P49

P50

6 T1 Card P76

CCMC

Cable Trough

Cable Trough

Cable Trough

0

7

811

138

1

4

1

515

8 T1 interface to the LPP via CCMC

OC-3/STM – 1 VT mapped interface to BTS/ T-1 ISSHO

OC-3c/STM - 1c interface to DISCO or BSS Manager

Slots 2&3 4&5 8&9,10&11,12&13

DISCO

Add DropMultiplexer

BSSManager

38

11pMSW FP Features/Benefits

» Recovers from a facility (fiber) failure within 50 msec

» Recovers from equipment failure within 100 msec

» Services provided for both ATM protocols and proprietary traffic protocols

» Channelized and unchannelized links

» Speeds from T1 to OC-3

» BCN router

39

11pMSW Conceptual layers» Back plane layer

– Passport 15000 processor inter-card communication– PHY device processors

• Devices that convert optics to STS, VT1.5, DS1

» Transport layer– Network processors that provide

• HDLC (High-level Data Link Control) processing– Inverse Multiplexing on HDLC (IMH)

• Routing functions• Packet switching• Multicasting• Priority queuing mapping

» External links– 2 OC-3 concatenated ports– 1 OC-3 channelized port– 8 T1 unchannelized ports

40

11pMSW FP in a CDMA Network

MDM

BSS Manager

11pM

SW

Passport

CP

OC-3c

OC-3c

OC-3c

T1

ISSHO T1

T1

T1

Ethernet

CIU

DISCOSBSDTC

MTX

DISCO on E/BSC (Network T1)

BTS

41

IMH on the 11pMSW FP in CBRS

» IMH available on the reverse path only in current legacy BSCs– Forward path on the current BSC requires distribution

to appropriate queue by an address router• Requires destination address• Queues are assigned pre-defined address range

» EBSC/CBRS supports both forward and reverse IMH– Eliminates requirement for destination address routing– Packets are distributed to each queue based on

occupancy– Allows for resources to be pooled– Simplifies link management– Increases link capacity– Increases reliability– Throughput limited only by total bandwidth available

across all T1 circuits

42

» CBRS supports Inverse Multiplexing over HDLC on the transmit links to MCBTS or other BSCs for ISSHO.– In legacy multiple T1 configurations, packets are currently

assigned to a particular T1 based on the packet’s destination address.

– In CBRS IMH configuration, packets are evenly transmitted across each link using round-robin scheme for each packet.

Existing BSCBSC

Tx

Tx

Tx

Tx

Tx

Tx

IMH

Rx

Rx

Incoming Packets

Incoming PacketsI

MH

BSC MCBTS

DCG

T1

T1

T1

Tx

Tx

Tx

Rx

Rx

Incoming Packets

Incoming PacketsI

MH

MCBTS

E-F

A-B

C-D

A DE

F

C

B

Address Router

Address Range A-B

Address Range C-D

Address Range E-F

Tx

Tx

TxT1

T1

T1

DCG

New CBRS


43

» IMH specifications include:– A Passport 15000 shelf can have a maximum of 210 IMH

groups.

– There is a maximum of 42 IMH groups per 11pMSW FP.

– Each IMH group can have from 1 to 8 Link subcomponents. However, the MCBTS CM currently only supports up to 6 T1 links.

– Each Link subcomponent is associated with a configured channelized OC3 port.

– The links of an IMH group can be added or removed once the IMH group is created (even after the group is associated to an active BCN service).

– The traffic through each links of an IMH group can be disabled or resumed without impacting the BCN service to which the IMH group is associated with (except that the bandwidth is reduced).


44

» IMH Connectivity:

BTSI FRM

CEMs

MCBTS

CORE

BTSCISSHOPort IMH

BTSPort IMH

BSC

CBRS

BSS Manager

T1 [1..8]

T1 [1..8]


45

Channelized OC-3 Port Link on 11p

» Supports T1 and E1 channels for BTS or T-1 ISSHO traffic

» Supports SONET 8 APS (Automatic Protection Switching)

» Supports external multiplexer ( e.g. Optera or equivalent)

» Channelization from OC-3 to DSO – OC-3 port configured as OC-3

– STS-3 port converted to OC-3

– STS-1 x 3 port are multiplexed into an STS-3

– VT1.5 x28 are multiplexed into STS-1 • Maximum of 84 virtual circuits

– DS-1 port converted into VT1.5• Each DS-1 is mapped into 1 channel with 24 timeslots

» Optical interface @ 155 Mbits

» One channelized port available (third connection)

46

OC-3 and T1 Port Links on 11p

Two(2) OC-3c concatenated ports

» Support BSS Manager or DISCO connections

» Support Mimic APS

» Each element has two connections to CBRS– One connection to 11p in

even slot

– One connection to mate in odd slot

» Optical interfaces @ 155 MBits

Eight (8) T1 ports» Support for CIU

connections– Up to 18 CIUs– Connections through the

CCMC– Same CIU pair must be

connected to the same 11pMSW

– Can be assigned different T1 cards in CCMC

» Unchannelized ports» One (1) connector/8 ports» 8 electrical interfaces @

1.544 Mbits

47

24pBCNW Connections in the CBRS

BCN links are rear connections on CCMC

Slots 6,7 & 14,15

SBS


Filter Tray

Cable Trough


P77

P78

P79

P80

P51

P52

P53

P54

P55

P56

P57

P58

P59

P60

P61

P62

P63

P64

P65

P66

P67

P68

P68

P70

P71

P72

P73

P74

P75

6 BC CardsP27

P28

P29

P30

P31

P32

P33

P34

P35

P36

P37

P38

P39

P40

P41

P42

P43

P44

P45

P46

P47

P48

P49

P50

6 T1 CardP76

CCMC

Cable Trough

Cable Trough

Cable Trough

0

7

81

1

1

38

1

4

1

515

CBRS

EBSCTM EBSCTM

48

24pBCNW FP Hardware Functions

» Link interfaces– 24 BCN ports (RS-422)

– 1 RS-485 serial port

» Framing/inverse multiplexing

» Network Processors providing– HDLC processing

– Routing functions

– Packet switching

– Multicasting

– Priority queuing mapping

» Fabric interfaces

» CDMA timing signal distribution

49

24pBCNW FP in a CDMA Network

Shelf 1

DTC SBS

EBSCTM

RS422

RS485

24B

CN

W

MTX

50

24pBSCNW FP Pairs

» Primary Pair– Responsible for control commands and queries to

EBSCTM• RS-485 rear connection to EBSCTM

• RS-232 front connection (for user interface e.g. PC)

– Slots 6 & 7 on upper shelf

– Provides CDMA timing• Chip clock

• Even second clock

» Secondary Pair– Provides CDMA timing

• Chip clock

• Even second clock

– Slots 14 & 15 on lower shelf

51

CDMA Timing Signal Distribution

24pBCNW FP

EBSCTM

1. Request Time Code

2. Time Code Response3. Update Internal Time Reference

5. Build BCN TOD4. Even Second Clock

Signal

6. Broadcast BCN TOD and Chip clock signals

To SBS controllers

ChipClock

52

CBRS FP Configuration Summary


EBSCTM EBSCTM

Filter Tray

Cable Trough


P77

P78

P79

P80

P51

P52

P53

P54

P55

P56

P57

P58

P59

P60

P61

P62

P63

P64

P65

P66

P67

P68

P68

P70

P71

P72

P73

P74

P75

6 BC CardsP27

P28

P29

P30

P31

P32

P33

P34

P35

P36

P37

P38

P39

P40

P41

P42

P43

P44

P45

P46

P47

P48

P49

P50

6 T1 CardP76

CCMC

Cable Trough

Cable Trough

Cable Trough

0

7

81

1

1

38

1

4

1

515

MDM

SBS

CIUBTS

Add DropMultiplexer

CIU

BTS

SBS

Represents Alternate Connection

CBRS All connections canco-exist at the same time

LAN

MDM

DISCO

BSS Manager

BSS Manager

53

CBRS FP Configuration Summary» A BSS Manager can be connected to either the

11pMSW (OC-3 port) or 4pOC-3 FP

» A DISCO can be connected to the 11pMSW (OC-3 port) or 4pOC-3 FP

» SBSs can be connected to either the DISCO (Legacy) or the 24pBSCNW (via CCMC) or both

» BTSs can either be connected to the DISCO (Legacy) or the Add Drop Multiplexer– These devices are in turn connected to the OC-3 port on

the 11pMSW FP

» CIUs can be connected to the T1 ports on the 11pMSW FP (via CCMC) or to a DISCO (Legacy)

» The MDM is connected to the BSS Manager via a LAN

» The MDM is connected to the CP3 of the CBRS via the LAN

54

Timing Inputs to the EBSC/CBRS

BITS

EBSC/CBRS


EBSCTM EBSCTM

Filter Tray

Cable Trough


P77

P78

P79

P80

P51P52

P53

P54

P55

P56P57

P58

P59

P60

P61P62

P63

P64

P65

P66P67

P68

P68

P70

P71P72

P73

P74

P75

6 BC CardsP27

P28

P29

P30

P31

P32

P33

P34

P35

P36

P37

P38

P39

P40

P41

P42

P43

P44

P45

P46

P47

P48

P49

P50

6 T1 CardP76

CCMC

Cable Trough

Cable Trough

Cable Trough

0

7

81

1

1

381

4

1

515

GPS AntennaRear connection

Rear connection

55

EBSCTM Output

» One (1) 9.8304 MHz frequency output for– CDMA chip clock

» ½ Hz timing output for– Even Second timing

– Testing equipment

» One (1) serial communication link for– Control/queries

56

CCMC Front Connections

Active Switch Card Shelf(OC-3 Express Form Factor)

CCMCNTPB13AA

P8

1

P8

3

P8

5

P8

2

P8

4

P8

6

P9

1

P9

3

P9

5

P9

2

P9

4

P9

6

P8

7P

88

P9

7P

98

P8

9P

90

P9

9P

10

0

T1’s to Network Interface 11pMSW FPs

P1

06

P1

08

P1

02

P1

04

P1

05

P1

07

P1

01

P1

03

BCN and GPS timing to SBS interface 24pBCNW FPs

6 BCN Cards6 T1 Cards

per connector

BCN and GPS timing to SBS

P77

P78

P79P80

P51

P52

P53

P54P55

P56

P57

P58

P59P60

P61

P62

P63

P64P65

P66

P67

P68

P68P70

P71

P72

P73

P74P75

P28

P29

P30

P32

P33

P34

P35

P36

P37

P38

P39

P40

P41

P42

P43

P44

P45

P46

P47

P48

P49

P50

P76P31P27

57

CCMC Rear Connections

P5

P6

P7P8

P9

P10P11P12

P13P14P15P16

BCN from SBS Cabinet

P17

P21

P20

P19

P18

P25

P24

P23

P22

P26

T1s to DSX for LPP connections

P4P2

P3GPSTM2

GPSTM1 Alarm

Pow

er A

P0

P1

Pow

er B

58

CCMC T1 Connections

59

CCMC BCN Connections

RearConnections

ToSBS

Cabinets

FrontConnections

To24pBCNW FP

BCN card 0 slot 16

BCN card 1 slot 15

BCN card 2 slot 14

BCN card 3 slot 13

BCN card 5 slot 11

BCN card 4 slot 12

P105

P106

P107

P108

P12

P13

P16

P15

P14

P11

P101

P102

P103

P104

P5

P6

P7

P8

P9

P10

BCN 0-3

BCN 4-7

BCN 8

-11

BCN 12-15

BCN 16-19

BCN 20-2

3

Sam

e as

P10

1

BCN 24-27

BCN 28-31

BCN

32-

35

BCN 36-39

BCN 40-43

BCN 44-4

7

Sam

e as

P10

2Sa

me

as P

105

Sam

e as

P10

6

BCN 0,1,4,5

BCN 2,3,6,7

BCN 8,9,16,17

BCN 10,11,12,13

BCN 14,15,20,21

BCN 18,19,22,23

BCN 24,25,28,29

BCN 26,27,30,31

BCN 32,33,40,41

BCN 34,35,36,37

BCN 38,39,44,45

BCN 42,43,46,47

60

CCMC EBSCTM Connections

Rear CCMC

connection to

EBSCTM1

Rear CCMC

connection to

EBSCTM2

BCN card 0 slot 16

BCN card 1 slot 15

P2

P3

P101

P102

P103

P104

P105

P106

P107

P108

FrontCCMC

Connections To

24pBCNW FP

GPS-A

GPS-B

GPS-B

GPS-A

61

Alarm Loop Connections

P101

P102

P103

P104

P5

P6

P7

P8

P9

P10

BCNCard 1/Slot15

BCNCard 2/Slot14

BCNCard 0/Slot16

Loop A1

Loop B5

Loop B4

Loop B2

Loop A5

Loop A2

Loop B1

Loop A4

Loop B3

Loop B0

Loop A3

Loop A0

Loop A1

Loop B5

Loop B4

Loop B2

Loop A5

Loop A2

Loop B1

Loop A4

Loop B3

Loop B0

Loop A3

Loop A0

BCNCard 3/Slot13

BCNCard 4/Slot12

BCNCard 5/Slot11

P105

P106

P107

P108

P12

P13

P16

P15

P14

P11

Loop B11

Loop B10

Loop B8

Loop A11

Loop A8

Loop B7

Loop A10

Loop B9

Loop B6

Loop A9

Loop A6

Loop B11

Loop B10

Loop B8

Loop A11

Loop A8

Loop B7

Loop A10

Loop B9

Loop B6

Loop A9

Loop A6

Loop A7 Loop A7

FrontCCMC

Connections To

24pBCNW FP

RearConnections

ToSBS

Cabinets

62

EBIP Alarm Connections

BCN Card 5

BCNCard 0

GPS

T1 Card 5

T1Card 0

ALM_C

ALM_NO

ALM_NCP2

P4

P3

3V_ALARM0

3V_ALARM1

ALM_C

ALM_NO

ALM_NC

ALM_C

ALM_NO

ALM_NC

EB

SC

TM

1E

BS

CT

M 2

ALARMTo

EBIP

X 6

63

CCMC Connections Panel

64

CDMA EBSC/CBRS System Diagram

LPP

DMS Core

SLMComputing

Module

IOC MTM

OAU

MTX

DMS Bus

ENET

DigitalTrunk

Controller

LPPor

FLIS

BCN LinkT1/E1 (UnC)T1 (Chan)TimingOpticalEthernet

AnothereBSC/CBRS

MDM/MDP

BSSManager

PP15K

LAN

BTS or MCBTS

Add DropMultiplexer

DISCO

GPS

SBS

SC

I-SS

CI-S

ES

EL

ES

EL

ES

EL

ES

EL

ES

EL

ES

EL

ES

EL

ES

EL

ES

EL

ES

EL

ES

EL

ES

EL

SB

SC

EBSCTM

CCMC

EBIP

CBRS

24pB

CN

W

24pB

CN

W

0 1 2 4 6 7

CP

3

CP

3

8 911pM

SW

11pM

SW

11pM

SW

1

4

1

524pB

CN

W

24pB

CN

W

1

3

4pO

C3

4pO

C3

11pM

SW

11pM

SW

11pM

SW

11pM

SW

11pM

SW

T1Voice Trunks

PDSN FA/HA

PSTN

Internet10MB Ethernet


EBSC BCN ServicesEBSC BCN Services

Lesson 3Lesson 3

66

Lesson 3 Objectives

» Relate BCN functions for the CBRS

» Understand BCN addressing types

» Describe features of the following traffic management tools for the CBRS– Packet Storm Loopback Detection

– Link Utilization Monitoring

– Congestion Control

» Understand the functions of the following:– PNNI

– DISCO Connectivity Audits

– Inverse Multiplexing for HDLC

67

BCN Services

» Provisioned and controlled by BSS Manager and MDM

– BSS Manager provisions BCN services

– MDM provisions the physical ports

» Maintained by FP host processor

68

Scalable Capacity

» Scalable in terms of Erlangs (voice traffic) and ports

» One CBRS frame– Up to 9000 Erlangs

– Up to 420 T1 BTS ports (5 pairs of 11pMSW FP)

– 48 SBS ports (2 pairs of 24pBCNW FP)

» Two CBRS frames– Up to 18000 Erlangs

– 672 T1 BTS ports (8 pairs of 11pMSW FP)

– 96 SBS ports (4 pairs of 24pBCNW FP)

» Three CBRS frames– Up t0 18000 Erlangs

– 1008 T1 BTS ports ( 12 pairs of 11pMSW FP)

– 144 SBS ports ( 6pairs of 24pBCNW FP)

69

EBSC BCN Service Features

» Automatic provisioning of ATM connections to support BCN traffic

» Elimination of CIS and BIU cabinets from BSC

» Improved traffic management– Packet storm loop back detection

– Congestion control mechanisms

– Link Utilization Monitoring

» On demand or spooled statistics data

» Configurable real-time connectivity audit

» Back haul outage detection

70

BCN Address Layouts

DISCO # (6 bits) Port # (7 bits) Entity # (11 bits)

0 0 0 0 0 0 Port # (7 bits) Entity # (8 bits)

Traffic type

Query/Initialization (Q/I) type

‘W’-zone type (aa = 01 | 10)

Broadcast type

bcast addr1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Entity # (13 bits)1 1 1 1 a a

World Zone (11 bits)

0 81623

QueryRange #

71

ATM Cell

BCN – 24 bits

ATM Cell (53 bytes)

48 byte packet

5 Byte Header 48 Byte Payload with BCN address

VPI

VCI

VCI

72

Routing Service for Traffic Frames

» Automatic provisioning of ATM connections – New BCN router – 11pMSW FP– 4pOC-3, 12pOC-3, and 12PDS3 also supported

» BCN traffic frame arrives at FP with one of two cell formats– From a DISCO (OC-3c port) as an encapsulated ATM cell

• DISCO encapsulates the BCN frame into a single 48 byte ATM cell

– Directly from a BTS via a multiplexer like the OPTERA (OC-3)

» Data flow through FP– Devices on FP forward frames to destination indicated

• Uses PP15k backplane

» BCN Route Table (BcnRouteTable)– Dynamic component– Records set of BCN address ranges for EBSC– Each CBRS has its own table

73

VPI and VCI for the EBSC

» VPI allow up to 256 virtual paths– 8 bits in User to Network Interface header

– Each VPI allows up to 65,536 VCIs• 16 bit VCI in header

» VCI is assigned based on the first eight (8) bits of the BCN address ( previously first six bits)– Required since a pair of 24pBCNW are assigned

one traffic range

» EBSC eliminates majority of hard coded VPI/VCI assignments

74

Private Network to Network Interface

» BCN services uses PNNI to setup, maintain and teardown ATM connections between Passports– Underlying BISC (BCN Inter-Shelf Communication)

protocol

» Provides routing and signaling capabilities– Dynamically ( at real-time)

• Exchanges topology and link state information on an ongoing basis

– Enables source routing• Route decided at first node

» Interfaces terminate on either a 4pOC-3 or 4pOc-12 FP

» VPI is 12 bits in PNNI cell header

75

Multicast Nailed Up Relay Point

DISCO PASSPORT DISCO

Virtual ChannelLink

AT

MIF

Back Plane

Relay Point Nailed Up Relay Point

Virtual ChannelLink

Virtual ChannelLink

AT

MIC

Active

Spare

Manually provisioned relay points that connects virtual links together are called nailed up.

AT

MIC

AT

MIC

AT

MIC

AT

MIF

AT

MIF

AT

MIF

76

» Automatic Protection Switching like mechanism (MIMIC APS) is introduced to support a reliable interface between the DISCO and the CBRS. This APS like mechanism was created since the DISCOs do not conform the Passport APS standard.

Mimic APS normal operation:

DISCO

FabricFabric

CBRS

Standby FP

Inactive

ATMIC2

Active

ATMIC1

Active FPWorking OC-3c

line

Protection OC-3c

line

Active Line

Inactive Line

Mimic APS

77

Supported BCN Connection Types for EBSC

» To a BTS– 11pMSW

» To a CIU– 11pMSW

» To a BSS Manager– 11pMSW, 4pOC-3

» To a legacy BCN router or DISCO– 11pMSW, 4pOC-3

» To other CBRS shelves that are part of the logical EBSC– 4pOC-3, 12pOC-3

» ISSHO connections to another BSC– 11pMSW for T1 links, 4pOC-3, 12pDS3

78

BCN Interfaces (BcnIf)

» BCN interfaces supported for the following EBSC CDMA subsystems:– BTS

• BtsBcnIf• Supported only on 11pMSW

– CIU• CiuBcnIf• Supported only on 11pMSW

– ISSHO links• IsshoBcnIf

– Supports BCN over T1 (only on 11pMSW)– Supports BCN over ATM ( both 11pMSW and 4pOC-3)

– DISCO• DiscoBcnIf• Supported only on 11pMSW and 4pOC-3

– BSS Manager• BssmBcnIf

79

Traffic Management

» Packet Storm Loopback Detection and Control Feature– Detects a packet storm due to loopback condition

– Performs appropriate actions to protect affected systems

– Generates a critical alarm

– Locks BCN port• Blocks all ingress and egress packets

– Operator identifies and removes loopback source

» Provisioned by operator on port-by-port basis – Feature must be enabled to work

– NO related action to solve loopback problem• ONLY detects and stops packet storm that results from

loopback

80

Packet Storm» The Packet Storm Loopback Detection and Control

feature protects CDMA Subsystems from being reset due to packet storms on loop back condition.

» The Packet Storm functionality supports on the ingress path of the BTSPort and CIUPort MOs through ‘LoopbackDetectionControl’ attribute.

» When a packet storm loopback is detected on the ingress path, traffic through the affected BCN port is shut down and critical alarm is generated. The operator needs to remove the packet storm loopback source and unlock the affected port to configure the port back to its original state. At this time, the critical alarm is cleared.

81

Packet Storm» Enable/Disable the Packet Storm functionality on a

per port basis only supports through BSS Manager.– To enable the Packet Storm functionality, either set

the field ‘LoopbackDetectionControl’ to ‘ENABLED’ on BTSPort/CIUPort MOs or set the field ‘LOOPDETCTRL’ to ‘Enabled’ in tables 11PMSWBTSPORTS/11PMSWCIUPORTS.

– To disable the Packet Storm functionality, either set the field ‘LoopbackDetectionControl’ to ‘DISABLED’ on BTSPort/CIUPort MOs or set the field ‘LOOPDETCTRL’ to ‘Disabled’ in tables 11PMSWBTSPORTS/11PMSWCIUPORTS.

» When the field ‘LoopbackDetectionControl’ is set via BSS Manager, the value of ‘detectionControl’ attribute under component ‘BtsBcn/n BtsBcnIf/n LoopDetection’ is changed on the Passport 15000.

82

Traffic Management

» Link Utilization Monitoring Feature– Monitors traffic

– Measures link capacity on CIU, BTS, ISSHO DISCO and BSS Manager

– Provides three levels of alarms• Minor, Major, Critical

– Links supported per FP• 11pMSW: BTS, CIU, ISSHO, BSS Manager, DISCO

• 4pOC-3: ISSHO, BSS Manager, DISCO

• 12pDS3: ISSHO

83

Link Utilization» The Link Utilization feature monitors traffics and

measures of how much the link capacity being used.

» The Link Utilization functionality supports on the ingress & egress paths of the BTSPort, CIUPort, ISSHOPort, BSSMPort, and DISCOPort MOs through the attributes:– LinkUtilAlarmThreshold: The thresholds for minor, major,

and critical alarms

– TxAvgLinkUtilization: The average transmit link utilization.

– RxAvgLinkUtilization: The average receive link utilization.

» On IMH configuration for BTS & ISSHO services, the link utilization can only be measured over the whole IMH group.

» The Link Utilization Alarm Threshold (minor, major, critical) can be disabled by setting the corresponding alarm threshold to 100.

84

Link Utilization» When the average link utilization exceeds

configured threshold values for 3 consecutive minutes, an alarm is generated.

Average Link

Utilization

AB

C

D E

F

88%

80%

72%

Time

Threshold values of LinkUtilAlarmThreshold:

-Minor Threshold = 72 %

-Major Threshold = 80 %

-Critical Threshold = 88 %

A: Set Minor alarm

B: Upgrade to Major alarm

C: Downgrade to Minor alarm

D: Upgrade to Major alarm

E: Upgrade to Critical alarm

F: Downgrade to Major alarm

3 mins

85

Traffic Management

» Congestion Control Feature– Protects CBRS from being knocked out of service

due to overload condition• Focuses on nodal congestion control in egress direction

only

– Detects, notifies and alleviates congestion on the following links:• 11pMSW FP: CIU, BTS, ISSHO, DISCO, BSS Manager

• 24pBCNW: SBS

– Uses a two priority queue mechanism• Single-bit priority scheme

• Queue scheduler

• Alarm issued for each

86

Congestion Control» The Congestion Control feature provides the

following functionalities when traffic exceeds the configured thresholds:– Queue packets based on priority scheme.

– Detect developing congestion.

– Discard packets based on priority scheme.

– Generate alarm.

» The Congestion Control functionality supports on the egress path of the BTSPort, CIUPort, ISSHOPort, BSSMPort, DISCOPort, and SBSPort MOs through the following attributes:– TxQueueAlarmThreshold: The egress queue congestion

alarm thresholds.

– TxQueueWeight: The number of packets in the egress queue.

– TxQueueSize: The maximum number of BCN packets which the egress queue can hold.

87

Congestion Control» Congestion Control Alarm Generation & Clearing:

Queue Length

A

B

C

D

E

F

txQueueSize

clearQFullThreshold

txQueueAlarmThreshold

clearQAlarmThreshold

Time-txQueueSize = 127 (default value)

-clearQFullThreshold = calculated as 90% of txQueueSize

-txQueueAlarmThreshold = default to 80% of txQueueSize

-clearQAlarmThreshold = calculated as 90% of txQueueAlarmThreshold

-A & C: Minor alarm generated when queue length goes up and crosses txQueueAlarmThreshold level

-B & F: Minor alarm cleared when the queue length goes down and crosses txQueueAlarmThreshold level

-D : Upgrade to Critical alarm when the queue length exceeds txQueueSize level

-E : Downgrade to Minor alarm when the queue length goes down and crosses clearQFullThreshold level

88

Connectivity Audits MOs

CBS1

CISPrimaryDISCOCSubsystem2

PrimaryDISCOCSubsystem1


Root

BCNPort1

B CN Port2

ConnectivityAudit1


SystemConnectivityAudit1

11pMSWSubsystem5

24pBCNWSubsystem7.0

BTSAggregate

C IU PortEBSC Passport

EBS CTM

ConnectivityAudit1

11pMSWSubsystem6

24pBCNWSubsystem7.1

SBSAggregate

SystemConfiguration1

ConnectivityAudit1

89

Connectivity Audits

» Provides the capability to verify connectivity between the 11pMSW and the following:– Other 11pMSW FPs

– DISCOs

– 24pBCNW FPS

» Uses traffic range BCN addresses

» Provides functionality for:– Initiation of audits from 11pMSW FP

– Provisioning of a neighbor list

– Alarm generation upon connectivity failure• Displayed on BSS Manager

– Backward compatible with DISCO connectivity audit

90

Backhaul Outage Detection Audit

» Real-time connectivity checks– Between BTS and 11pMSW

» Periodic broadcast

» Acknowledgement of reset

» Backwards compatible

91

AtmIf vs. BcnIf Overview

» Prior to eBSC, provisioning for connectivity to a DISCO, a BSS Manager, or to setup ATM ISSHO links on a Passport required the use of AtmIfs.

» In provisioning AtmIfs the operator was required to allocate VPIs and in some cases VCIs.

» Remember: A Vpi.Vci combination will give you a VCC – which is like seperating a big pipe (VPI) into smaller pipes (VCIs). Sometimes you don’t need to breakdown a VPI into smaller pipes and this means that you only need to deal with a VPC.

92


» All connections are uni-directional.

» An ATM switch receives an ATM cell with specific VPI and VCI and routes it to a destination port and gives it a new VPI and VCI value.

» The input VPI.VCI value is the most important value. It describes the destination address of a particular packet.

» The Output VPI.VCI value is unimportant to the DISCO because this newly assigned VPI.VCI value is not used by the DISCO.

93


» Most connections are based on VPI only– inter-DISCO Traffic connections– ISSHO connections

» Some connections use VPI and VCI value– All BSS Manager to Subsystem connections– Subsystem to BSS Manager connections– Inter-DISCO CIU connections– Inter-DISCO Broadcast connections (Paging and TOD)

94

ATMIF vs. BCNIF Overview

• With eBSC the craftsperson is no longer required to provision VPIs or VCIs – with the exception of ATM based ISSHO.

• Note that VPIs and VCIs are still in use, however the new Atm based BcnIfs will automatically allocate connections based on a set of (Bar <-> Vpi.Vci) mapping tables. Please refer to the Mapping Tables section of this document to view the tables.

95

Typical ATMIF provisioned for a Disco

» A typical AtmIf for a Disco contains more than 500 lines of provisioning data vs. ~6 lines for an eBSC DiscoIf.

» All the possible traffic addresses in the network must be represented by individual Vpc or Vcc and each pointing to their corresponding end point(s).

» Provisioning data needs to be engineered carefully to ensure correct endpoints are linked together.

96

Typical ATMIF VPC Mapping

Tm Vpd

Atmif/20

Vpc/132

Tm Vpd

Atmif/22

Vpc/132

Tm Vpd

Atmif/32

Vpc/132

Mnrp Nrp Nrp

> d -p atmif/20 vpc/132 mnrp nexthopAtmif/20 Vpc/132 Mnrp nextHop = Atmif/22 Vpc/131 Nrp, Atmif/32 Vpc/131 Nrpok 2002-09-05 13:00:00.00

DISCO 7 (Atmic 1)

DISCO 33 (Atmic 1)

DISCO 33 (Atmic 2)

Mnrp – Multicast nailed up relay point Atmic cards require multicasting because there is no protection scheme in place (I.e. APS). This is no longer the case with eBSC.

If no multicast is required, then theNrp sub-component will be provisionedinstead of Mnrp and it will only pointto a single destination.

If we want to reach DISCO 33 (subrange 0) we would route through here.

97

Typical ATMIF VCC Mapping

Tm Vcd

Atmif/20

Vcc/248.17920

Tm Vcd

Atmif/21

Vcc/248.17920

Tm Vcd

Atmif/31

Vcc/248.17920

Mnrp Nrp Nrp

> d -p atmif/20 vcc/248.17920 mnrp nexthopAtmif/20 Vcc/248.17920 Mnrp nextHop = Atmif/21 Vcc/248.17920 Nrp, Atmif/31 Vcc/248.17920 Nrpok 2002-09-05 13:00:00.00

If no multicast is required, then theNrp sub-component will be provisionedinstead of Mnrp and it will only pointto a single destination.

DISCO 7 (Atmic 1)

If we want to reach CIU 0 (WZ 35) we would route through here.

DISCO 33 (Atmic 1)

DISCO 33 (Atmic 2)

CIU 0

98

ATMIF vs. BCNIF Mapping Tables

Traffic Range Prefix Start Stop VPC

1 0x040000 0x07FFFF 4, 5, 6, 7

2 0x080000 0x0BFFFF 8, 9, 10, 11

3 0x0C0000 0x0FFFFF 12, 13, 14, 15

4 0x100000 0x13FFFF 16, 17, 18, 19

5 0x140000 0x17FFFF 20, 21, 22, 23

6 0x180000 0x1BFFFF 24, 25, 26, 27

: :

: :

55 0xDC0000 0xDFFFFF 220, 221, 222, 223

56 0xE00000 0xE3FFFF 224, 225, 226, 227

57 0xE40000 0xE7FFFF 228, 229, 230, 231

58 0xE80000 0xEBFFFF 232, 233, 234, 235

59 0xEC0000 0xEFFFFF 236, 237, 238, 239

60 0xF00000 0xF3FFFF 240, 241, 242, 243

DISCO Traffic Addresses (egress)

For Disco Traffic Addresses, only VP switching is used. i.e., each Traffic range is mapped into 4 separate VPIs (or subranges). The following mapping is used:

Table 1 - BcnDiscoAtmIf Traffic Address Mapping (same as legacy)

DISCO

99

DISCO CIU World Zone Addresses (egress)

For CIU World Zone addresses use VC switching, i.e, use the following mapping:

CIU Start Stop Start VPI.VCI Stop VPI.VCI

CIU Pair 1 0xF80600 0xF80601 248.1536 248.1537

CIU Pair 2 0xF80700 0xF80701 248.1792 248.1793

CIU Pair 3 0xF80800 0xF80801 248.2048 248.2049

CIU Pair 4 0xF80900 0xF80901 248.2304 248.2305

CIU Pair 5 0xF80A00 0xF80A01 248.2560 248.2561

CIU Pair 6 0xF80B00 0xF80B01 248.2816 248.2817

CIU Pair 7 0xF80C00 0xF80C01 248.3072 248.3073

CIU Pair 8 0xF80D00 0xF80D01 248.3328 248.3329

CIU Pair 9 0xF80E00 0xF80E01 248.3584 248.3585

Table 2 - BcnDiscoAtmIf CIU World Zone Address Mapping for World Zone 33 (same as legacy)


100

CIU Start Stop Start VPI.VCI Stop VPI.VCI

CIU Pair 1 0xF84600 0xF84601 248.17920 248.17921

CIU Pair 2 0xF84700 0xF84701 248.18176 248.18177

CIU Pair 3 0xF84800 0xF84801 248.18432 248.18433

CIU Pair 4 0xF84900 0xF84901 248.18688 248.18689

CIU Pair 5 0xF84A00 0xF84A01 248.18944 248.18945

CIU Pair 6 0xF84B00 0xF84B01 248.19200 248.19201

CIU Pair 7 0xF84C00 0xF84C01 248.19456 248.19457

CIU Pair 8 0xF84D00 0xF84D01 248.19712 248.19713

CIU Pair 9 0xF84E00 0xF84E01 248.19968 248.19969

Table 3 - BcnDiscoAtmIf CIU World Zone Address Mapping for World Zone 35 (same as legacy)

DISCO CIU World Zone Addresses (egress)


101

Table 4 - BcnDiscoAtmIf BSSM World Zone Address Mapping for World Zone 1 (same as legacy)

DISCO BSS Manager World Zone Addresses (egress)

For BSS Manager World Zone Addresses, use the following VC mapping:

BSSM Address VPI VCI

BSS Manager 0XF40100 244 256

BSSM Address VPI VCI

BSS Manager 0XF44100 244 16640

Table 5 - BcnDiscoAtmIf BSSM World Zone Address Mapping for World Zone 3 (same as legacy)


102

Table 6 - BcnDiscoAtmIf Query/Initialization Address Mapping (same as legacy)

DISCO Query/Initialization Addresses (egress)

For Query/Initialization addresses, use the following VC mapping:

DISCO Q range # DISCO Q Address Low

DISCO Q Address High

VPI VCI

1 0x08000 0x0FFFF 3 81

2 0x10000 0x17FFF 3 82

3 0x18000 0x1FFFF 3 83

4 0x20000 0x27FFF 3 84


103

Table 7 - BcnDiscoAtmIf Broadcast Address Mapping (same as legacy)

DISCO Broadcast Addresses

For each broadcast address ingress setup request, we have to map the broadcast address to a VPI/VCI pair and set up the ingress path with the DEI provided.

Destination Broadcast Address VPI VCI

Multicast file distribution 0xFFFFF0 255 65520

unused 0xFFFFF1 255 65521









unused 0xFFFFFA 255 65530

unused 0xFFFFFB 255 65531

Time Of Day (TOD) 0xFFFFFC 255 65532

unused 0xFFFFFD 255 65533

BTS Paging 0xFFFFFE 255 65534

unused 0xFFFFFF 255 65535

VPI = 255 (first byte of broadcast address) VCI = last 2 bytes of the broadcast address.


104

Table 8 - BcnBssmAtmIf Traffic Address Mapping

BSS Managaer DISCO Traffic Addresses (Ingress)

Disco Traffic Addresses are used for setting up ingress paths to other subsystems on the EBSC. Use the following VC mapping:

BSS Manager

Traffic Range Prefix Start Stop VPI VCI (ebsc) VCI (legacy)

1 0x040000 0x04FFFF 3 304 201

1 0x050000 0x05FFFF 3 305

1 0x060000 0x06FFFF 3 306

1 0x070000 0x07FFFF 3 307

2 0x080000 0x08FFFF 3 308 202

2 0x090000 0x09FFFF 3 309

2 0x0A0000 0x0AFFFF 3 310

2 0x0B0000 0x0BFFFF 3 311

: : : : :

60 0xF30000 0xF3FFFF 3 543 260


105

Table 9 - BcnBssmAtmIf CIU World Zone Address Mapping (same as legacy)

BSS Manager CIU World Zone Addresses (Ingress)

CIU World Zone addresses is used for setting up Ingress path to CIU. Use the following VC mapping for both world zone #33 and #35

VPI VCI

3 80

BSS Manager World Zone Addresses (Egress)

For other subsystems to communicate with the BSS Manager, use the following mapping to set up the egress path for the BSS Manager world zone number

VPI/VCI Mapping for WZ to BSS Manager Communication

CBRS VPI VCI (CBRS)

WZ 3 110

loopback 2 2

Disco # VPI VCI (Atmic1) VCI (Atmic2)

1 3 111 121

2 3 112 122

3 3 113 123

4 3 114 124

loopback 2 2 2

Table 10 – VPI/VCI Mapping for CBRS Table 11 – VPI/VCI Mapping for legacy


106

Table 12 - BcnBssmAtmIf Broadcast Address Mapping for DISCO (new to CBRS)

BSS Manager Broadcast Addresses (Ingress)

To set up ingress paths to the broadcast addresses, use the following mapping:

BSSM

Destination Broadcast Address VPI VCI (ebsc) VCI (legacy)

Multicast file distribution 0xFFFFF0 3 550 Not used

Time Of Day (TOD) 0xFFFFFC 3 562 100

BTS Paging 0xFFFFFE 3 564 Not used


107

Table 13 - BcnBssmAtmIf Query/Initialization Address Mapping for DISCO (same as legacy)

BSS Manager Query/Initialization Addresses (Ingress)

To set up ingress paths to the Query/Initialization addresses, use the following mapping:

BSSM

DISCO Q range #

DISCO Q Address Low


VPI VCI

1 0x008000 0x00FFFF 3 81

2 0x010000 0x017FFF 3 82

3 0x018000 0x01FFFF 3 83

4 0x020000 0x027FFF 3 84

i.e.,VPI = 3VCI = DISCO Query Range + 80


108

Table 14 - BcnBssmAtmIf Query/Initialization Address Mapping for 11pMSW / 24pBCN (new to CBRS)

BSS Manager Query/Initialization Addresses (Ingress)

To set up ingress paths to the Query/Initialization addresses, use the following mapping:

BSSM

DISCO Q range #

QueryInitEBscId

EBSC Query Address Low

EBSC Query Address High

DISCO Q Address Low


VPI VCI

5 1 0x01028000 0x0102FFFF 0x028000 0x02FFFF 3 601

5 2 0x02028000 0x0202FFFF 0x028000 0x02FFFF 3 602

: : : : : : : :

5 32 0x20028000 0x2002FFFF 0x028000 0x02FFFF 3 632

i.e.,VPI = 3VCI = DISCO Query Range + 600



CBRS and the BSS CBRS and the BSS ManagerManager

Lesson 4Lesson 4

110

Lesson 4 Objectives

» Explain the roles of the MDM and the BSS Manager in the CBRS

» Recognize new CBRS managed objects

» Describe new BSS Manager tools for the CBRS

111

BSS Manager and the CBRS

112

The BSS Manager for the CBRS

» The BSS Manager includes OA&M integration of CBRS FP cards with CDMA system– Fault/Alarm Management

– Configuration Management

» The BSS Manager can be connected to either of the following :– 11pMSW function processor (OC-3c port)

– 4pOC-3 function processor

» The BSS Manager has a new standalone GUI for EBSC port map MOs (Managed Objects)

» The BSS Manager can support up to 650 cell carriers

» Only CDMA services configured in BSS Manager– Hardware commissioning and provisioning via the

MDM

113

MDM and BSS Manager Interaction

PP15K

MDM Server

MDM Gatewa

y

MDM Client

Core BSS Manager

LAN Network

BSS Manager

114

Data Paths

Traffic data

Event Reports

Configuration Data

BSS Manager MDM

CBRS

115

OA&M Integration» OA&M provides the following functionalities on the

Enhanced BSC FPs:– Fault & Alarm Management (FM)– Configuration Management (CM)– Performance Management (OM)– Security Management (SM)

» The key elements in CBRS OA&M integration includes:– The BSS Manager– The MDM (Multi-service Data Manager)– The MDP (Management Data Provider)

SMOMCMFMFunction Processor

MDMMDPBSSMBSSM11pMSW FP

MDMMDPBSSMBSSM24pBCNW FP

MDMMDPMDMMDM4pOC3 FP

MDMMDPMDMMDM4pOC12 FP

MDMMDPMDMMDM12pDS3Atm FP

116

OA&M Integration» BSS Manager

– Is the centralized OA&M processor in CDMA network

– Configured in redundant mode on a SUN ES450 Solaris 2.8 platform.

– Used to configure CDMA services only.

» Multi-service Data Manager (MDM)– Previously known as NMS (Network Management

System).

– Is the OA&M entity for the Passport 15000.

– Configured in redundant mode on a SUN Solaris 2.8 platform.

– Used for hardware commissioning and provisioning of CBRS Functional Processors.

– Has the ability to communicate with multiple Passport 15000 and with multiple BSS Managers.

117

OA&M Integration» Management Data Provider (MDP)

– Is a bulk data collection and processing system for network accounting and statistical information.

– Run on the same SUN Solaris platform where MDM is configured

– Used to collect spooled OMs from all Passport 15000 in CBRS.

– There is no interaction between BSS Manager and MDP.

» The MDM/MDP workstations are connected to the BSS Managers via LAN, in a trusted workstation mode.

» Three ways to launch the MDM GUI:– From the BSMCI Tool, type command ‘startmdm’

– From the ‘Tools’ pull-down menu of the BSS Manager

Navigator, select ‘Start the MDM’

– From the ‘Applications’ tab of the BSMControl, select

‘MDM – Start the MDM’

118

Addressing Mechanism• Traffic Address Mechanism changes:

– One traffic address range allocated for each 11pMSW FP.

– One traffic address range is broken down into two sub-traffic ranges, allocated to two 24pBCNW FP pairs.

• Q/I Address Mechanism changes:

– The first four query ranges are used for DISCOs

– The fifth query range is used for 60 Functional Processors (due to the limitation of 60 traffic range numbers).

• Worldzone Address Mechanism:

– No changes made to the WorldZone address mechanism for CBRS

• Broadcast Address Mechanism changes:

– One address is used for Time of Day, one address is used for BTS paging, one address is used for Multicast File Distribution, the remaining addresses are unused.

119

BSMControl Modifications

» Modification on the ‘KACN’ Tab Interface:– The ‘EBSC ATM Configuration’ button is created to allow

the configuration and routing mechanisms of the ATM card to the Passport 15000, based on the new addressing mechanism.

120


» Modifications on the ‘Config’ Tab Interface:– The button ‘Set up MDM configuration information’ is created

to allow MDM Configuration setup.

– The BSS Manager needs to be stopped when the MDM configuration is changed. The button ‘Write to configuration file’ should also be selected before the BSS Manager is started.

121


– Information required to set up MDM connection include: • The IP address or host name of the MDM servers

• The MDM userid & password

• The MDM Passport Group ID & password

122

Bsmcontrol Applications

123

MDM Launch from BSMControl

124

EBSC Hierarchy in BSS Manager

125

New EBSC Managed Objects

» EnhancedBSC– Parent MO for EBSC

» Passport– Logical parent to EBSC new function processors

» EBSCHardware– Flags hardware alarms

» TimeODay– Holds the Time Of Day information

» 11pMSWSubsystemX

» 24pBCNWSubsystemX,Y

126

11pMSW FP Expanded View

127

New MOs for 11pMSW FP

» 11pMSWSubsystemX– Top level MO

– For a single 11pMSW subsystem

» 11pMSWPortMap– Maps CDMA services to the physical ports of 11pMSW

– Analogous to BCNPortMap in Primary DISCO

» BTSAggregate– BTSs with same destination traffic range number (DISCO

number)

» BTSPort– One (1) BCN traffic address range assigned per 11pMSW

• 120 BTSs per 11pMSW

» CIUPort– Connected to any of the copper T1 of the 11pMSW

128

More New MOs for 11p

» DiscoPort– Contains parameters to configure a OC-3c port with

DISCO attached– Mate DISCO is required to communicate with mate CIU

» IMH– Represents parameters to configure IMH

» Connectivity Audit– Displays information about

DISCOs/11pMSWs/24pBCNWs in the neighbor list

» BSSMPort– Contains parameters to configure a OC_3c port for BSS

Manager

» ISSHO– Contains parameters to setup an ISSHO connection on

OC-3 channelize port– Maximum of 60 ISSHO ports

129

Complete EBSC View with 24pBCNW

130

New MOs for 24pBCNW» 24BCNWSubsystemX.Y

– Top level MO– X represents the traffic range number assigned– Y represents the subsection (0-1) of traffic range

» 23pBCNWPortMap– Maps the hardware RS422 port to SBS

» EBSCTM – Represents the EBSCTM in the Passport

» SBSAggregate– SBS ports having same traffic range prefix (DISCO

number)

» SBSPort– One instance for each physical SBS serviced by this

24pBCNW

» Connectivity Audit– Information about DISCOs in neighbor list

131

CBRS Tools» New tools supported in CBRS include:

– The Enhanced BSC Port Map Viewer Tool

– The Data Audit Tool

– The MDM Configuration Validation Tool

– The ISSHO Fixed to Balanced Tool

– The Enhanced BSC Configuration Tool

132

Enhanced BSC Port Map Viewer Tool» This GUI tool shows the port configuration data defined in

11pMSWPortMap & 24pBCNWPortMap MOs.

– BTSPort, CIUPort, ISSHOPort, DISCOPort, BSSMPort, IMH, and SBSPort.

» To launch the tool, from the ‘Tools’ pull-down menu of the BSS Manager Navigator, select ‘Enhanced BSC Port Map Viewer’.

» BTSPort View Information:

133

Enhanced BSC Port Map Viewer Tool» CIUPort View Information:

» ISSHOPort View Information:

134

Enhanced BSC Port Map Viewer Tool» DISCOPort View Information:

» BSSMPort View Information:

135

Enhanced BSC Port Map Viewer Tool» IMH View Information:

» SBSPort View Information:

136

Data Audit Tool• The Data Audit Tool audits CDMA service components

related to 11pMSW and 24pBCNW.

• The tool provides a report (in text file format) for inconsistencies between the configuration in the BSS Manager and the Passport 15000.

• The tool will not generate alarms or fix any inconsistencies being found.

• To launch the tool, from the BSS Manager prompt, type: ‘ebscDataAudit –p <Passport_name> -s <[11p, 24p, all]>’

• To list various options provided by the tool, type: ‘ebscDataAudit –h’.

• The audit report is stored in directory /opt/bsm/adm/cfds

137

MDM Configuration Validation Tool• Provide MDM Configuration Validations:

– Validate MDM license– Validate the local hosts file– Validate the local MDM processes– Validate the connectivity of the primary MDM– Validate the connectivity of the secondary MDM

• A potential solution will be displayed if problems are encountered during the validation process.

• To launch the tool, from the BSS Manager prompt, type: ‘ValidateMDMSetup’.

• To list various options provided by the tool, type: ‘ValidateMDMSetup –h’.

138

ISSHO Fixed to Balanced Tool• This GUI tool allows the user to reconfigure ISSHO

BCNPorts on legacy DISCOs for load balancing.

• The tool functionality includes:– Modify the address ranges on a legacy DISCO BCNPorts to

allow ISSHO traffic received from an IMH group.– Delete scripts & log files created by the tool.

• The DISCO subsystem status must be ‘APPRunning’ and ISSHOPort must be Unlock/Coupled/Enabled for this tool purpose.

• To launch the tool, from the BSS Manager prompt, type: ‘isshofixtobal’.

139

Additional Tools» Commissioning Manager

– CLI

– GUI

– Modified for CBRS to use “Traffic Range” and add a PortNum field

140

BSMCI Tables for EBSC

New BSMCI tables Modified BSMCI tables

PASSPORTINV MACROBTSINV

11PMSWINV MINIBTSINV

11PMSWBTSPORTS METROINV

11PMSWCIUPORTS PDB

11PMSWBSSMPORTS SBSINV

11PMSWISSHOPORTS

11PMSWDISCOPORTS

REACHABLEWORLDZONELIST

11PMSWIMH

11PMSWIMHLINKS

24PBCNWSBSPORTS

24PBCNWINV

CONNAUDITSYSSETTINGSLIST

SHAREDNEIGHBORLIST

141

New MOs / BSMCI Tables» ‘EnhancedBSC’ is the parent MO of the Enhanced BSC» Adding Enhanced BSC MOs in the Operational Tree via the CLI

scripts and the BSS Manager Navigator (Drag & Drop) are not supported for CBRS.

» All Enhanced BSC MOs in the BSS Manager must be configured through BSMCI tables.

» MOs created as part of the Passport 15000 include:

BSMCI Table Managed Objects

• Passport MO

• EBSCHardware MO

• SubsystemAlarm MO

• TimeOfDay MO

An entry is datafilled in table PASSPORTINV created

142

• MOs created as part of the 11pMSW FP include:

New MOs / BSMCI Tables

BSMCI Tables Managed Objects

• 11pMSWSubsystem MO

• 11pMSWPortMap MO

• BTSAggregate MO

• ConnectivityAudit MO


An entry is datafilled in table 11pMSWINV created

• BTSPort MO

• CIUPort MO

• ISSHOPort MO

• BSSMPort MO

• DISCOPort MO

• IMH MO

An entry is datafilled in tables 11PMSWBTSPORTS created

11PMSWCIUPORTS created

11PMSWISSHOPORTS created

11PMSWBSSMPORTS created

11PMSWDISCOPORTS created

11PMSWIMH

11PMSWIMHLINKS

created

143

• MOs created as part of the 24pBCNW FP include:New MOs / BSMCI Tables

• MO created as part of the ConnectivityAudit include:


• SystemConnectivityAudit MOTable SHAREDNEIGHBORLIST

Table CONNAUDITSYSSETTINGSLIST


• 24pBCNWSubsystem MO

• 24pBCNWPortMap MO

• SBSAggregate MOs

• EBSCTM MO

• ConnectivityAudit MO


An entry is datafilled in table 24PBCNWINV created

• SBSPort MO

An entry is datafilled in table 24PBCNWSBSPORTS created

144

Enhanced BSC Hierarchy in BSS Manager

CBS

CIS

MTXSubsystem

SystemConfiguration SystemConnectivityAudit

SBSCSubsystem

PrimaryDISCOSubsystemX

EnhancedBSC Passport

11pMSWSubsystemX

EBSCHardware

TimeOfDay

SubsystemAlarm

24pBCNWSubsystemX.Y1,1

1,3

1

1,5

1

1

1,2

Parent MO of Enhanced BSC

MO created by table PASSPORTINV

MO created by table 11pMSWINV

MO created by table 24pBCNWINV

Existing MO in legacy BSC

X =DISCO Traffic Range = [1 .. 60]

Y = Sub-traffic Range = [0 .. 1]

BSM

MetroBTS

MacroBTS

MiniBTS MiniBTSSubsystem

BTSSubsystem

MCBTSSubsystem

Cells

SBSs

SubsystemAlarm

TFUSubsystemTFUs

145

11pMSW FP MO Hierarchy in BSS Manager

11pMSWSubsystemX

CIUPort

BSSMPort

DISCOPort

BTSAggregate

ISSHOPort

1

0,17

1,2

1,2

1,60

MO created by table 11PMSWINV

MO created by table 11PMSWBTSPORTS

MO created by table 11PMSWCIUPORTS

MO created by table 11PMSWISSHOPORTS

MO created by table 11PMSWBSSMPORTS

11pMSWPortMap

IMH

SubsystemAlarm

BTSPort

ConnectivityAudit

MO created by table 11PMSWDISCOPORTS

MO created by table 11PMSWIMH

1,42

1,127

1

1

1

146

24pBCNW FP MO Hierarchy in BSS Manager

24pBCNWSubsystemX.Y

MO created by table 24PBCNWINV

MO created by table 24PBCNWSBSPORTS

EBSCTM

SBSAggregate1

1,2

24pBCNWPortMap

SubsystemAlarm

SBSPort

ConnectivityAudit

0,11

1

1

1

SBSAggregate1

SBSPort

ConnectivityAudit

0,11

1

Note: Only the Primary 24pBCNW FP pair has direct contact with the EBSCTM MO

147

BSMCI Tables Dependency• BSMCI tables of the Enhanced BSC are dependent to each

other (except table PASSPORTINV is independent).

PASSPORTINV

11PMSWINV

24PBCNWINV

11PMSWBTSPORTS

11PMSWCIUPORTS

11PMSWISSHOPORTS

11PMSWBSSMPORTS

11PMSWDISCOPORTS

11PMSWIMH 11PMSWIMHLINKS

REACHABLEWORLDZONELIST

24PBCNWSBSPORTS

Note: The BSMCI table dependencies in this figure are from left to right.

148

New BSMCI Tables• Table PASSPORTINV: Represents the physical Passport 15000 shelf

• Table 11PMSWINV: Represents the 11pMSW FP pair in the Passport

Field Name Range Default Value Related MO: Attribute

Brief Fields

PPNAME string - Passport:InstanceDisplayName

PPNODEID string - Passport:PassportNodeId

CIUWZONE 1..35 33 EnhancedBSC:CIUWorldZonePrefix

Full Fields

QINITRANGE 5..7 5 Passport: QueryInitRange


Brief Fields


TRAFFICRANGE 1..60 - 11pMSWSubsystem:PassportNodeId

LPNUM1 1..15 - 11pMSWSubsystem:LPNumber1

LPNUM2 1..15 - 11pMSWSubsystem:LPNumber2

LAPSNUMCHAN 0..15999 - BTSAggregate:InterfaceName

149

New BSMCI Tables• Table 11PMSWBTSPORTS: Provide info on OC3 T1 port (BTS).

Field Name Range Default Related MO: Attribute

Brief Fields

TRAFFICRANGE 1..60 - 11pMSWSubsystem:InstanceDisplayName

PORTNUM 1..127 - BTSPort:InstanceDisplayName

INTFNAME string - BTSPort:InterfaceName

ADMINFIELD string none BTSPort:AdminField

Full Fields

LOOPDETCTRL Enabled/Disabled - BTSPort:LoopbackDetectionControl

LUTILALMTMIN 0..100 72 BTSPort:LinkUtilAlarmThreshold[0]

LUTILALMTMAJ 0..100 80 BTSPort:LinkUtilAlarmThreshold[1]

LUTILALMCRI 0..100 88 BTSPort:LinkUtilAlarmThreshold[2]

TXQALMT1 0..100 80 BTSPort:TxQueueAlarmThreshold[0]

TXQALMT2 0..100 80 BTSPort:TxQueueAlarmThreshold[1]

TXQWEIGHT1 1..127 80 BTSPort:TxQueueWeight[0]

TXQWEIGHT2 1..127 2 BTSPort:TxQueueWeight[1]

TXQSIZE1 1..127 127 BTSPort:TxQueueSize[0]

TXQSIZE2 1..127 127 BTSPort:TxQueueSize[1]

150

New BSMCI Tables• Table 11PMSWCIUPORTS: Provide info on T1 ports for CIU.


Brief Fields


CIUNUM 0..17 - CIUPort:InstanceDisplayName

PORTNUM 1..127 - CIUPort:PortNumber

INTFNAME string - CIUPort:InterfaceName

ADMINFIELD string none CIUPort:AdminField

Full Fields

LOOPDETCTRL Enabled/Disabled - CIUPort:LoopbackDetectionControl

LUTILALMTMIN 0..100 72 CIUPort:LinkUtilAlarmThreshold[0]

LUTILALMTMAJ 0..100 80 CIUPort:LinkUtilAlarmThreshold[1]

LUTILALMCRI 0..100 88 CIUPort:LinkUtilAlarmThreshold[2]

TXQALMT1 0..100 80 CIUPort:TxQueueAlarmThreshold[0]

TXQALMT2 0..100 80 CIUPort:TxQueueAlarmThreshold[1]

TXQWEIGHT1 1..127 80 CIUPort:TxQueueWeight[0]

TXQWEIGHT2 1..127 2 CIUPort:TxQueueWeight[1]

TXQSIZE1 1..127 127 CIUPort:TxQueueSize[0]

TXQSIZE2 1..127 127 CIUPort:TxQueueSize[1]

151

New BSMCI Tables• Table 11PMSWISSHOPORTS: Represents ISSHO interfaces


Brief Fields


PORTNUM 0..17 - ISSHOPort:InstanceDisplayName

EGRESSTRLIST 59:1..60 - ISSHOPort:EgressTrafficRangeList

INTFNAME string - ISSHOPort:InterfaceName

ADMINFIELD string none ISSHOPort:AdminField

Full Fields

LUTILALMTMIN 0..100 61 ISSHOPort:LinkUtilAlarmThreshold[0]

LUTILALMTMAJ 0..100 68 ISSHOPort:LinkUtilAlarmThreshold[1]

LUTILALMCRI 0..100 75 ISSHOPort:LinkUtilAlarmThreshold[2]

TXQALMT1 0..100 80 ISSHOPort:TxQueueAlarmThreshold[0]

TXQALMT2 0..100 80 ISSHOPort:TxQueueAlarmThreshold[1]

TXQWEIGHT1 1..127 80 ISSHOPort:TxQueueWeight[0]

TXQWEIGHT2 1..127 2 ISSHOPort:TxQueueWeight[1]

TXQSIZE1 1..127 127 ISSHOPort:TxQueueSize[0]

TXQSIZE2 1..127 127 ISSHOPort:TxQueueSize[1]

152

New BSMCI Tables• Table 11PMSWBSSMPORTS: Represents BSS Manager interface component


Brief Fields


PORTNUM 1..2 - BSSMPort:InstanceDisplayName

INTFNAME string - BSSMPort:InterfaceName

ADMINFIELD string none BSSMPort:AdminField

Full Fields

LUTILALMTMIN 0..100 61 BSSMPort:LinkUtilAlarmThreshold[0]

LUTILALMTMAJ 0..100 68 BSSMPort:LinkUtilAlarmThreshold[1]

LUTILALMCRI 0..100 75 BSSMPort:LinkUtilAlarmThreshold[2]

TXQALMT1 0..100 80 BSSMPort:TxQueueAlarmThreshold[0]

TXQALMT2 0..100 80 BSSMPort:TxQueueAlarmThreshold[1]

TXQWEIGHT1 1..127 80 BSSMPort:TxQueueWeight[0]

TXQWEIGHT2 1..127 2 BSSMPort:TxQueueWeight[1]

TXQSIZE1 1..127 127 BSSMPort:TxQueueSize[0]

TXQSIZE2 1..127 127 BSSMPort:TxQueueSize[1]

153

New BSMCI Tables• Table 11PMSWDISCOPORTS: Represents DISCO Interface components


Brief Fields


DISRANGE 1..60 - DISCOPort:TrafficRangePrefix

REACHTRLIST 58:1..60 - DISCOPort:ReachableTrafficRangeList

LAPSNUMCON 0..15999 - DISCOPort:InterfaceName

ADMINFIELD string none DISCOPort:AdminField

Full Fields

LUTILALMTMIN 0..100 61 DISCOPort:LinkUtilAlarmThreshold[0]

LUTILALMTMAJ 0..100 68 DISCOPort:LinkUtilAlarmThreshold[1]

LUTILALMCRI 0..100 75 DISCOPort:LinkUtilAlarmThreshold[2]

TXQALMT1 0..100 80 DISCOPort:TxQueueAlarmThreshold[0]

TXQALMT2 0..100 80 DISCOPort:TxQueueAlarmThreshold[1]

TXQWEIGHT1 1..127 80 DISCOPort:TxQueueWeight[0]

TXQWEIGHT2 1..127 2 DISCOPort:TxQueueWeight[1]

TXQSIZE1 1..127 127 DISCOPort:TxQueueSize[0]

TXQSIZE2 1..127 127 DISCOPort:TxQueueSize[1]

154

New BSMCI Tables• Table REACHABLEWORLDZONELIST:

– Represents information of CIU and BSSM connections to DISCO which is hanging off the 11pMSW FP.

• Table 11PMSWIMH: Represents info about the IMH groups.


Brief Fields

DISPORTNUM 1..4 - DISCOPort:InstanceDisplayName

REACHWZONE 1..35 - DISCOPort:ReachableWorldZoneList

REACHCIULIST 18:0..17 - DISCOPort:ReachableWorldZoneList


Brief Fields

TRAFFICRANGE 1..60 none 11pMSWSubsystem:InstanceDisplayName

IMHNUMBER 1..210 none IMH:InstanceDisplayName

PROJLINKS 1..8 - IMH:ProjectedNumberOfLinks

ADMINFIELD string none IMH:AdminField

155

New BSMCI Tables• Table 11PMSWIMHLINKS: Represents info about each T1 link in an IMH MO

• Table 24PBCNWINV: Represents 24pBCNW FP pair in Passport.


Brief Fields

TRAFFICRANGE 1..60 none 11pMSWSubsystem:InstanceDisplayName

IMHNUMBER 1..210 none IMH:InstanceDisplayName

INSTANCENUM 1..8 none IMH:IMHLinks

IMHLINK string none IMH:IMHLinks


Brief Fields


TRAFFICRANGE 1..60 - 24pBCNWSubsystem:InstanceDisplayName

SUBTRNUM 0..1 - 24pBCNWSubsystem:InstanceDisplayName

LPNUM1 1..15 - 24pBCNWSubsystem:LPNumber1

LPNUM2 1..15 - 24pBCNWSubsystem:LPNumber2

156

New BSMCI Tables• Table 24PBCNWSBSPORTS : Represents SBS Interface component


Brief Fields

TRAFFICRANGE 1..60 - 24pBCNWSubsystem:InstanceDisplayName

SUBTRNUM 0..1 - 24pBCNWSubsystem:InstanceDisplayName

PORTNUM 0..23 - SBSPort:InstanceDisplayName

ADMINFIELD string none SBSPort:AdminField

Full Fields

TXQALMT1 0..100 80 SBSPort:TxQueueAlarmThreshold[0]

TXQALMT2 0..100 80 SBSPort:TxQueueAlarmThreshold[1]

TXQWEIGHT1 1..127 80 SBSPort:TxQueueWeight[0]

TXQWEIGHT2 1..127 2 SBSPort:TxQueueWeight[1]

TXQSIZE1 1..127 127 SBSPort:TxQueueSize[0]

TXQSIZE2 1..127 127 SBSPort:TxQueueSize[1]

157

New BSMCI TablesNew BSMCI Tables• Table SHAREDNEIGHBORLIST: Represents the list neighbors for connectivity audits

• Table CONNAUDITSYSSETTINGSLIST: Represents the connectivity audit settings for each traffic range


Brief Fields

DISCONUM 1..60 none SystemConnectivityAudit:SystemConnectivityAuditSettings

BSCID string none SystemConnectivityAudit: SystemConnectivityAuditSettings


Brief Fields

TRAFFICRANGE 1..60 - SystemConnectivityAudit

AUDITACTIVEATMIC ACTIVATED, DEACTIVATED

- SystemConnectivityAudit

AUDITINACTIVEATMIC ACTIVATED, DEACTIVATED


ATMICSWOVER ACTIVATED, DEACTIVATED


NEIGHBOURLISTSELECTION SharedList, MateDISCO


158

Existing Tables Modification» The following existing BSMCI tables are modified to support BTSs

connected to the 11pMSW FP:

– Table MINIBTSINV

– Table MACROBTSINV

– Table METROINV

– Table PDB

» Modifications in these tables include:

– Change fieldname ‘DISCO’ to ‘TRAFFICRANGE’

– Change fieldname ‘BCNPORT’ to ‘PORTNUM’, value [1..127]

– Add new fieldname ‘CONNTYPE’, value [DISCO, 11PMSW]

159

Existing Tables Modification» The table SBSINV is modified to support SBSs connected to the

24pBCNW FP.

» Modifications in table SBSINV include:

– Change fieldname ‘DISCO’ to ‘TRAFFICRANGE’

– Change fieldname ‘BCNPORT’ to ‘PORTNUM’

– Add new fieldname ‘SUBTRNUM’, value [0,1]

– Add new fieldname ‘CONNTYPE’, value [DISCO, 24PBCNW]

• If CONNTYPE = DISCO, then:

TRAFFICRANGE = DISCO number

SUBTRNUM will be ignored

PORTNUM = [1..96]

• If CONNTYPE = 24PBCNW, then:

TRAFFICRANGE = 24pBCNW number

SUBTRNUM = 24pBCNW sub-traffic range

PORTNUM = [0..23]


CBRS and the MDMCBRS and the MDM

Lesson 5Lesson 5

161

Objectives

» Recognize MDM functions

» Understand how the MDM gateway works

» Describe the purpose of the MDP

162

Passport MDM in the EBSCEBSC#1

EBSC #2

Ethernet

MDM

CBRS


EBSCTM EBSCTM

Filter Tray

Cable Trough


P77

P78

P79

P80

P51P52

P53

P54

P55

P56P57

P58

P59

P60

P61P62

P63

P64

P65

P66P67

P68

P68

P70

P71P72

P73

P74

P75

6 BC CardsP27

P28

P29

P30

P31

P32

P33

P34

P35

P36

P37

P38

P39

P40

P41

P42

P43

P44

P45

P46

P47

P48

P49

P50

6 T1 CardP76

CCMC

Cable Trough

Cable Trough

Cable Trough

0

7

81

1

1

381

4

1

515

CBRS


EBSCTM EBSCTM

Filter Tray

Cable Trough


P77

P78

P79

P80

P51P52

P53

P54

P55

P56P57

P58

P59

P60

P61P62

P63

P64

P65

P66P67

P68

P68

P70

P71P72

P73

P74

P75

6 BC CardsP27

P28

P29

P30

P31

P32

P33

P34

P35

P36

P37

P38

P39

P40

P41

P42

P43

P44

P45

P46

P47

P48

P49

P50

6 T1 CardP76

CCMC

Cable Trough

Cable Trough

Cable Trough

0

7

81

1

1

381

4

1

515

LAN

BSSManager

BSSManager

BSSManager

BSSManager

163

Overview» Workstation based

» Network management system

» Provides OA&M functions for Passport 15K frames– Fault management

– Configuration management

– Security management

– Performance management

– Accounting

» MDM 13.3 release for NBSS 11.0

» GUI

» Previously known as Network Management System (NMS)

» Able to configure and troubleshoot Passport 15K frame, shelves and function processors

164

New Requirements for the EBSC MDM

» Solaris 2.8

» Redundant configuration (Active/Redundant)– Supports redundant BSS Managers for 11pMSW

and 24pBCNW

– Supports higher capacity/load on MDM hardware

» Other Passport functions not supported on CBRS MDM

» Multiple Passport 15K frames supported

» Each server requires one Ethernet port/ IP address

165

MDM Gateway in the BSS Manager

MDM GATEWAY

BSS ManagerMDM

SERVER

SSSSERVER

ProtocolConverter

ASCII QMIP

166

EBSC Configuration Path

BSS Manager Core/SSS

MDM Gateway

MDM ClientProcess MDM Server

CP-3

1

2

34

5

6

7

89

10

BSS Manager

MDM

PP15K/CBRS

EBSC FP

167

EBSC Event Reporting

BSS Manager Core/SSS

MDM Gateway

MDM ClientProcess

MDM Server

CP-3

4

3

1

2

ba

BSS Manager

MDM

PP15K/CBRS

EBSC FP

5

168

Alarm Display

169

MDP

» Collects accounting data

» Collects performance data

» Converts data to BDF or EBCDIC format

» Transfer files to customer host

» Can generate network component outage and availability reports


EBSC Configuration ToolEBSC Configuration Tool

Lesson 6Lesson 6

171

Objectives

» Describe the activities performed by the EBSC Configuration Tool

» Relate tool restrictions

» Understand the usage of the tool in configuring and managing ports/links

» Understand how to manage batch and log files created by the tool

172

Starting the EBSC Configuration Tool

Only one instance of the tool can be spawned at any given time.

173

Main Screen

174

Configuration Tool Activities

» Add ports

» Move subsystems or ports

» Delete ports

» Manage T1 links on BTS and ISSHO ports

» Manage batch files created by the tool

» Manage log files created by the tool

– A users guide can be found in NTP 411 - 2133 - 936

175

General Screen Layout

Screen titleInstructions

Status Bar

Progress IndicatorControl buttons

176

Tool Restrictions

» No Command line version of the tool

» BSS Manager must be up and running for tool to operate

» Passport interfaces need to be setup previous to running tool

» Tool can not provision any components on Passport directly

» Tool generates BSMCI and CLI scripts which means coordination is required for the BSS Manager database

» Tool does not reconfigure subsystems that are moved

» For SBS and BTS scripts, the user must make sure the SBS or BTS is working

» Able to run only one instance of the tool at a time

» Non-EBSC systems do not have access to this tool

177

EBSC Configuration Tool Diagram

CBRS

MDMGUI Tool

BSMCI CLI

MDM Queue

User

1

2 3 6

4

5

7 8 9

178

Port/Subsystem Management

179

Add Ports: Step 1 of 5

180

Add BTS Port: Step 2 of 5

181


182


183


184

Manage T1 Links

185

Manage T1s: Select Ports

186

Manage T1s: Configure Data

187

Sample Batch file

#This batch file was auto-generated by EBSC Configuration Tool#Batch file Purpose: Create a BTS port – single T1table 11PMSWBTSPORTadd 40 1 “laps/12130 sts/0 vt1dot5/1,2 ds 1 chan/0” *quit

188

Batch File Management

189

Batch and Log File Locations

» Batch File location– Created files are in “/opt/bsm/scripts/ebsc_config”

directory

– Executed files are in “/opt/bsm/scripts/ebsc_config/executed” directory

» Log files location

– Logs found in “/opt/bsm/log/ebsc_config” directory

– Debug log files found in “/opt/bsm/log/bsmdbg” directory

190

Delete Ports/Subsystem

191

Delete Ports: Selection

192

Move DISCO Subsystems

193

Move CIUs


EBSC EBSC Performance

Lesson 7Lesson 7

195

Objectives

» Understand the Operational measurements for CBRS

» Understand how CBRS and MDP fit together

196

EBSC Performance» BCN Statistics

» The following lists the statistics that are collected at each BCN interface on the 11pMSW, 24pBCNW, and the 4pOC3. The enhancements to collect BCN stats for ATM-based ISSHO links are only applicable to the 4pOC3 card and not to the 11pMSW. Exceptions for ATM-based BCN interfaces are as noted.

– txPackets

– rxPackets

– txOctets -This attribute is not applicable and is not displayed for ATM based BCN interfaces.

– rxOctets - This attribute is not applicable and is not displayed for ATM based BCN interfaces.

– txPacketDiscards

– txPacketDiscardPriority1

– txPacketDiscardPriority2

– rxPacketDiscards

– rxBroadcastPacketDiscard - This attribute is not applicable and is not displayed for ATM based BCN interfaces.

» Internal statistics are tracked by the BCN interface as soon as it is created. Counters are initially set to zero. The next DCS probe occurs sometime between 0 and 15 minutes after the BCN interface instance is successfully provisioned. Spooled statistics are based on the available gathered data and averages are calculated over the collection interval.

» After a BCN interface is deleted, any residual DCS probe that occur for that interface is ignored. The statistics data collected by the BCN interface that was deleted during the collection interval is lost.

197

EBSC Performance» 11pMSW Functional Processor Operational Measurements

» There are five port types that are provisionable on the 11pMSW FP: BTS, DISCO, ISSHO (non-ATM-based), CIU, and BSS Manager. Each of these interfaces collects BCN statistics.

» The statistics records generated may include all or a subset of the attributes related to BCN services. The type of BCN interface determines the set of attributes included in the statistics record; the ATM-based BCN interfaces use a subset of all of the available attributes.

» The statistics that are spooled are based on the attributes that can be displayed on demand via the Display command.

198

EBSC Performance» Non-ATM Interfaces

– The following table indicates the statistics record common to the BTS, CIU and non-ATM based ISSHO interfaces. The statistics that are calculated internally for these interfaces, based on the BCN statistics previously mentioned, are underlined

Note: If the BTSPort is configured as an IMH group, the statistics will be for all of the T1’s in that group.

Non-ATM Interfaces BTS, CIU, and ISSHO

txPackets txOctets rxPackets rxOctets

txPeakLinkUtilization rxPeakLinkUtilization txAvgLinkUtilization rxAvgLinkUtilization

txMinLinkUtilization rxMinLinkUtilization txPeakPacketRate txPeakThroughput

txAvgPacketRate txAvgThroughput rxPeakPacketRate rxPeakThroughput

rxAvgPacketRate rxAvgThroughput txPacketDiscards txPacketDiscardPriority1

txPacketDiscardPriority2 rxPacketDiscards rxBroadcastPacketDiscard

199

EBSC Performance» ATM Interfaces

– The following table lists the statistics record common to the BSS Manager, and DISCO interfaces. The statistics that are calculated internally for these interfaces, based on the BCN statistics previously described, are underlined. Note that the txOctets, rxOctets, and rxBroadcastPacketDiscard attributes are not applicable to ATM-based interface.

ATM Interfaces BSS Manager and DISCO

txPackets txPeakLinkUtilization txAvgLinkUtilization txMinLinkUtilization

txPeakPacketRate txAvgPacketRate txPacketDiscards txPacketDiscardPriority1

txPacketDiscardPriority2 rxPackets rxPeakLinkUtilization rxAvgLinkUtilization

rxMinLinkUtilization rxPeakPacketRate rxAvgPacketRate rxPacketDiscards

200

EBSC Performance» 24pBCNW Functional Processor OM’s

– The same BCN statistics that are available for the 11pMSW FP are available for the 24pBCNW FP, with the exception that the link utilization feature is not available for this card and therefore there are no link utilization statistics. The following table lists the BCN statistics that are reported in the spooled statistics record.

24pBCNW Functional Processor – SBS Ports

txPackets txOctets rxPackets rxOctets

txPeakPacketRate txPeakThroughput txAvgPacketRate txAvgThroughput

rxPeakPacketRate rxPeakThroughput rxAvgPacketRate rxAvgThroughput

txPacketDiscards txPacketDiscardPriority1 txPacketDiscardPriority2 rxPacketDiscards

rxBroadcastPacketDiscard

201

EBSC Performance» 4pOC3 Functional Processor OM’s

– The BCN services for the 4pOC3 card have been enhanced to collect BCN-related statistics. The statistics that are available are the same as for ATM-based links on the 11pMSW, including statistics for BSS Manager, DISCO, and ATM-based ISSHO links.

4pOC3 Functional Processor - BSS Manager, DISCO and ATM-ISSHO ports

txPackets txPeakLinkUtilization txAvgLinkUtilization txMinLinkUtilization

txPeakPacketRate txAvgPacketRate txPacketDiscards txPacketDiscardPriority1

txPacketDiscardPriority2 rxPackets rxPeakLinkUtilization rxAvgLinkUtilization

rxMinLinkUtilization rxPeakPacketRate rxAvgPacketRate rxPacketDiscards


EBSC AlarmsEBSC Alarms

Lesson 8Lesson 8

203

Alarms» The Alarms can be found in NTP NN-20000-901

» SBS Aggregate» SBS Port» ISSHO Port» IMH» EBSCTM» EBSCHardware» DISCO Port» Connectivity Audit» CIU Port» BTS Port» BTS Aggregate» BSS Manager Port» BCN Port» Time Of Day

204

SBS Aggregate Alarms» LNS operation error. Recommended operator

action: delete the component» MSG - Multicast Channel Overflow in TSP

205

SBS Port Alarms» BCN traffic congestion for priority 1 transmit queue » BCN traffic congestion for priority 2 transmit queue» Datapath setup failure. Examine the following failed entries

<entries>» Failed to allocate Egress Broadcast connection. Examine the

following failed entries <entries>» Failed to communicate with the BRM, recommend to delete the

service component» LNS operation error. Recommended operator action: delete the

component» MSG - A total of <n> packets received were discarded since the

last DCS collection interval» MSG - A total of <n> packets were not transmitted because they

were discarded since the last DCS collection interval» MSG - Error detected while deallocating all connections» MSG - Failed to add egress routes for this BcnIf. Probable cause:

Duplicate BcnIf configuration data. Please examine the following failed entries <entries>

» MSG - Failed to deallocate Egress Broadcast connection. Examine the following failed entries <entries>

» MSG - Failed to set up far end Ingress connections. Examine the following failed entries. Remote Card Number <card number> <entries>

» MSG - Failed to update Ingress Broadcast Filter» Setup failure. Delete the service component

206

ISSHO Port Alarms» BCN traffic congestion for priority 1 transmit queue» BCN traffic congestion for priority 2 transmit queue

» Could not set up ISSHO TDM port for IMH

» Datapath setup failure. Examine the following failed entries <entries>

» Failed to communicate with the BRM, recommend to delete the service component

» LNS operation error. Recommended operator action: delete the component

» MSG - A total of <n> packets received were discarded since the last DCS collection interval

» MSG - A total of <n> packets were not transmitted because they were discarded since the last DCS collection interval

» MSG - Error detected while deallocating all connections

» MSG - Error detected while deallocating the connection for DISCO number <disco number>

» MSG - Failed to add egress routes for this BcnIf. Probable cause: Duplicate BcnIf configuration data. Please examine the following failed entries <entries>



» Receive link utilization exceeded the <minor/major/critical> threshold for 3 consecutive minutes

» Setup failure. Delete the service component

» Transmit link utilization exceeded the <minor/major/critical> threshold for 3 consecutive minutes

207

IMH Alarms» Links are down. Please check and resolve problems with the

Chan components used by the IMH links» Request to change projectedNumberOfLinks rejected.

<cause> <recommended response>

208

EBSCTM Alarms» EBSCTM Mode is: <mode>. EBSCTM has an antenna fault» EBSCTM Mode is: <mode>. EBSCTM has a hardware fault» EBSCTM Mode is: <mode>. EBSCTM in holdover for over

<elapsed time> » EBSCTM Mode is: <mode>. EBSCTM is powering up» EBSCTM Mode is: <mode>. EBSCTM temperature

above/below normal range

209

EBSCHardware MO Alarms» Link to LP/<n> CDMACS/<n> is down» Link to Dlep/<n> RS485/<n> is down» Loss of Clock condition has been detected (lvdsClkAlarm).

Check the cabling and termination panel. » Loss of Signal condition has been detected (lvdsLosAlarm).

Check the cabling and termination panel

210

DISCO Port Alarms» BCN traffic congestion for priority 1 transmit queue. Address type: Broadcast» BCN traffic congestion for priority 1 transmit queue. Address type: Query Init

» BCN traffic congestion for priority 1 transmit queue. Address type: Traffic range

» BCN traffic congestion for priority 1 transmit queue. Address type: WorldZone

» BCN traffic congestion for priority 2 transmit queue. Address type: Broadcast

» BCN traffic congestion for priority 2 transmit queue. Address type: Query Init

» BCN traffic congestion for priority 2 transmit queue. Address type: Traffic range

» BCN traffic congestion for priority 2 transmit queue. Address type: WorldZone











211

Connectivity Audit Alarms» Active to Active (AA) Connection Failure with Traffic Ranges:

<traffic range N> <bscId N> VPI(< remote> / <local> vpi-pairs), ...

» Active to Active (AA) Transmit Failure with Traffic Ranges: <traffic rangeN> <bscIdN> VPI (<remote-vpi1>, ...)

» Active to Inactive (AI) Connection Failure with Traffic Ranges: <traffic range N> <bscIdN> VPI(< remote> / <local> vpi-pairs), ...

» Active to Inactive (AI) Transmit Failure with Traffic Ranges: <traffic rangeN> <bscIdN> VPI (<remote-vpi1>, ...)

» Active Side Connectivity Audit Disabled» Datafill Failure with Traffic Ranges: <traffic ranges>» Inactive to Active (IA) Transmit Failure with Traffic Ranges:

<traffic rangeN> <bscIdN> VPI (<remote-vpi1>, ...)» Inactive to Inactive (II) Transmit Failure with Traffic Ranges:

<traffic rangeN> <bscIdN> VPI (<remote-vpi1> ...)» Inactive Side Connectivity Audit Disabled» No Route Found to BCN Routers (Traffic Range#, Vpi): <traffic

range #, vpi>» Total Ping Failure

212

CIU Port Alarms» BCN traffic congestion for priority 1 transmit queue » BCN traffic congestion for priority 2 transmit queue


» Failed to allocate Egress Broadcast connection. Examine the following failed entries <entries>


» LNS operation error. Packet Storm Loopback Detection will not work properly




» MSG - CIU mate setup failure




» MSG - Failed to <lock/unlock> TDM port. Consider deleting the component


» MSG - Failed to update Ingress Broadcast Filter

» Packet Storm Loopback detected. The BCN port is locked. Transmit and receive messages are dropped




213

BTS Port Alarms» BCN traffic congestion for priority 1 transmit queue » BCN traffic congestion for priority 2 transmit queue


» Failed to allocate Egress Broadcast connection. Examine the following failed entries <entries>


» LNS operation error. Packet Storm Loopback Detection will not work properly







» MSG - Failed to <lock/unlock> TDM port. Consider deleting the component


» MSG - Failed to update Ingress Broadcast Filter

» Packet Storm Loopback detected. The BCN port is locked. Transmit and receive messages are dropped




214

BTS Aggregate Alarms» LNS operation error. Recommended operator action: delete

the component» MSG - Multicast Channel Overflow in TSP

215

BSS Manager Port Alarms» BCN traffic congestion for priority 1 transmit queue » BCN traffic congestion for priority 2 transmit queue » Datapath setup failure. Examine the following failed entries

<entries>» Failed to communicate with the BRM, recommend to delete the

service component» LNS operation error. Recommended operator action: delete the

component» MSG - A total of <n> packets received were discarded since the

last DCS collection interval» MSG - A total of <n> packets were not transmitted because they

were discarded since the last DCS collection interval» MSG - Failed to add egress routes for this BcnIf. Probable cause:

Duplicate BcnIf configuration data. Please examine the following failed entries <entries>

» MSG - Failed to set up far end Ingress connections. Examine the following failed entries. Remote Card Number <card number> <entires>


» Setup failure. Delete the service component» Transmit link utilization exceeded the <minor/major/critical>

threshold for 3 consecutive minutes

216

BCN Port Alarms» Message storm detected. BCN port is degraded---All

broadcast messages are blocked » Message storm detected. BCN port is degraded---All

broadcast messages have been blocked for the past x hours » Message storm detected. BCN port is disabled---All

messages are blocked » Port COPIM Buffer Overflow» Port Device Not Accessible» Port Device Not Initialized» Port DISPIM Packet Buffer Overflow» Port DISPIM Transmit Packet Loss» Port Fault Unknown» Port HDLC Receive Clock Failure» Port HDLC Transmit Clock Failure» Port Receive CRC Error

217

Time Of Day Alarms» BcnTod Alarm - The Following Cards Do Not Have Even

Second Interrupt: <card number>

218

Glossary– APS – Automatic Protection Switching– BCN – Base Station Communication Network– BISC – BCN Inter-Shelves Communication– BIU – Backhaul Interface Unit– CBRS – CDMA Backhaul & Routing Subsystem– CCMC – Cable Consolidation and Multiplexing Chassis– CDSU – Channel Data Service Unit– CIS – CDMA Inter-connect System– DISCO – Distribution / Consolidation Bus– EBSCTM – EBSC Timing Module– EMI – Electro Magnetic Interference– GPS – Global Positioning System– HDLC – High-speed Data Link Control– IMH – Inverse Multiplexing Over HDLC– LAN – Local Area Network– LPP – Link Peripheral Processor– MDM – Multi-service Data Manager– MDP – Management Data Provider– MO – Managed Objects– NMS – Network Management System– P-RDI: Path Remote Defect Indicator– Q/I – Query / Initialization– SBS – Selector Bank Subsystem– TFU – Timing Frequency Unit

Documents

CBRS Overview