Thanks Thanks:  1
Showing results 1 to 3 of 3

Thread: Sites Re-homing in E// RNC

  1. #1
    Member Reputation: 89
    Join Date
    2011-09-14
    Location
    Hell
    Posts
    90


    Default Sites Re-homing in E// RNC

    Does anyone has info, steps, procedures on site re-homing in E******* RNC ?

    Please share...Thanks in advance

  2. # ADS
    Circuit advertisement
    Join Date
    Always
    Location
    Advertising world
    Posts
    Many
     

  3. #2
    Member Reputation: 89
    Join Date
    2011-09-14
    Location
    Hell
    Posts
    90


    Default Re: Sites Re-homing in E// RNC

    Pls share ........

  4. #3
    Member Reputation: 416
    Join Date
    2010-06-16
    Posts
    321


    Default Re: Sites Re-homing in E// RNC

    Quote Originally Posted by deepak187 View Post
    Does anyone has info, steps, procedures on site re-homing in E******* RNC ?

    Please share...Thanks in advance
    You have two parts:
    1. RNCs
    2. transport

    for RNC side: copy all definitions from old to the new RNC. Ignore IuR for a while, if there are IuR definitions,
    (IuR never worked properly so you can do without.)
    Prepare transport (ATM/IP).
    Make sure Mub is available from both RNCs, regardless of transport.

    Halt site on forst RNC, reconnect transport, activate on second.

    If you script all activities using jython, moshell, ncli and simmilar for transport, it can be fast.
    200 sites/hour is decent with good team and well prepared scripts.

    You will not find "cookbook" as no two operators have same ATM/IP network, and it all depends on transport.

    There are some E/// OSS features: it takes more time to read docs as to perform the job.
    This is safe procedure for people who do not understand the task. 10 per night?

    BR
    s52d

  5. Thanks deepak187 thanked for this post

Bookmarks

Bookmarks

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •