Annex6 MW NMS Solution for Life V2.0

Embed Size (px)

Citation preview

  • 7/30/2019 Annex6 MW NMS Solution for Life V2.0

    1/12

    Huawei Confidential

    www.huawei.com

    Huawei MW NMS solution for-- Ukraine Life:)

  • 7/30/2019 Annex6 MW NMS Solution for Life V2.0

    2/12

    Huawei Confidential Page 2

    Content

    SWAP areas

    Network Topology and characteristics

    Microwave Network DCN plan

    Description of DCN Network design

    Requirements for Astelit

  • 7/30/2019 Annex6 MW NMS Solution for Life V2.0

    3/12

    Huawei Confidential Page 3

    KievLugansk

    Kharkov

    DnepropetrovskDonetsk

    ZaporozhyeMykolaiv

    Chernigov

    Sumy

    Poltava

    Cherkasy

    Kirovograd

    Crimea

    KhersonOdessa

    Uzhorod

    Lutsk

    Zhytomir

    Vinnyttsa

    Kiev

    Rovno

    Lvov

    Ivano-

    Frankovsk

    Chernovtsy

    TernopilKhmelnytskyi

    Ericsson Areas

    SWAP AREAS

    Nokia Areas

    Huawei Areas

  • 7/30/2019 Annex6 MW NMS Solution for Life V2.0

    4/12

    Huawei Confidential Page 4

    MW Network Topology and characteristics

    Kiev

    T2000

    SOUTH REGION

    WEST REGION

    BSC

    OPT Node

    MW

    Fiber

    There is NO MW link between region and Kiev

    We do have EMS6 board on each OPT node IF we want use EMS6 transmits NMS data by OPT network,the signal format must be VC12 NOT E1,and both sidemust be RTN620

  • 7/30/2019 Annex6 MW NMS Solution for Life V2.0

    5/12

    Huawei Confidential Page 5

    Microwave Network DCN plan

    T2000

    LAN Switch

    OPT/VC1

    2network

    convertor

    convertorNMS Center

    GNE SCC ETH -> EMS6 FE -> VCTRUNK over PDH/SDH Network -> EMS6 FE ->FO/OMC Site L2 SW FE -> LAN connected to T200

    Fiber

  • 7/30/2019 Annex6 MW NMS Solution for Life V2.0

    6/12

    Huawei Confidential Page 6

    Description of DCN Network design

    For General OPT Node

    T2000LAN Switch

    NMS center

    1 Use network cable make physics connection between SCC and EMS62 Make the logistic connection between EMS6 and SD1 NMS data into VC12 3 Send back VC12 to NMS Center through OPT network4 Use NMS centers RTN600 converter VC12 into NMS data by EMS65 make physics connection between SCC and EMS6

    OPT Node

    MW

    RTN600

    OPT/VC1

    2

    network

    Fiber Fiber

  • 7/30/2019 Annex6 MW NMS Solution for Life V2.0

    7/12

    Huawei Confidential Page 7

    Description of DCN Network design

    For Special OPT Node

    T2000LAN Switch

    NMS center

    OPT Node

    MW

    OPT/VC12network

    OPT/VC12network

    OPT/VC12network

    For save consumersVC12 we collect thedata and use L2switch function totogether it

  • 7/30/2019 Annex6 MW NMS Solution for Life V2.0

    8/12

    Huawei Confidential Page 8

    Description of DCN Network design

    For Special OPT NodeOPT Node

    MW

    In some area , one OPT node only support small chain, we canUse one OPT node collect nearby others OPT nodes NMS dataFor save consumers VC12

    1 Use network cable make physics connection between SCC and EMS6

    2 Make the logistic connection between EMS6 and SD1 NMS data into VC12 3 Use RTN600 collect the data and use L2 switch function to together it3 Send back VC12 to NMS Center through OPT network4 Use NMS centers RTN600 converter VC12 into NMS data by EMS65 make physics connection between SCC and EMS6

  • 7/30/2019 Annex6 MW NMS Solution for Life V2.0

    9/12

    Huawei Confidential Page 9

    EMS6/SCC Board Function Introduction

    NM

    interface

    NM HUB

    interface

    SCC

    RTN620 RTN620

    RTN620

    T2000

    RTN can be connected through the network ports.

    RTN620RTN620

    VC12Network

    EMS6T2000

    Both side Need to be RTN 600

    1 provide L2 Switch function

    2 provide 8 VCTRUNK3 provide VB Virtual brdige

  • 7/30/2019 Annex6 MW NMS Solution for Life V2.0

    10/12

    Huawei Confidential Page 10

    IP Plan and NE ID Rule for LIFE project

    We make IP plan and ID plan according to existing site name,

    because it will be easy to create and rememberID plan Rule:

    We use extended id represents different region and basic id according existing site namedirectly for example LK2001, if LK code is 65 this site IDU id will be extended id :65 ,basic id 2001. we also add a first digit for situation that one site has several IDUs , forexample LK2001 site has 3 subracks for first IDU basic id is 2001,for second IDU id is 12001.third IDU id is 22001 and so on. our basic id value range is 1 to 49136, extended id value range

    is 1 to 254,it should be enough for whole network.

    IP plan Rule:

    Every IDUs ip is doesn't matter to consumer except GNEs, we will set GEN's ip address base

    on consumer's request for general NE, we make rule as follow

    All NE ip start with 129.AA.BB.CC AA means region code ,BB and CC means site name's firsttwo digits and last two digits for example LK2001 we create ip address is 129.65.20.01 assame as id rule, we also prepare for special situation that one site has several IDUs. for secondand third IDU , we change last two digits to three digits and start with 100. for example thesecond IDU ip address is 129.65.20.100,the third IDU ip address is 129.65.20.101 and so on.

  • 7/30/2019 Annex6 MW NMS Solution for Life V2.0

    11/12

    Huawei Confidential Page 11

    Requirements for Astelit

    VC12 between OPT Nodes ,

    VC12 between region and Kiev

    OPT interface for OPT Nodes

    OPT interface for NMS Center

    RTN600 FOR NMS Center

  • 7/30/2019 Annex6 MW NMS Solution for Life V2.0

    12/12

    Huawei Confidential

    www.huawei.com

    Thank You!