0% found this document useful (0 votes)
121 views8 pages

IXRE Scripting Process

The IXRE cutover process involves confirming site readiness, backing up nodes, and ensuring the availability of the IXRE script before migration. There are three configuration types for migration, each with specific steps for connecting existing routers to the IXRE. Key requirements include checking current IXRE status, generating scripts if necessary, and following detailed connectivity and testing procedures for various node types during the migration process.

Uploaded by

Gaurav Singh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
121 views8 pages

IXRE Scripting Process

The IXRE cutover process involves confirming site readiness, backing up nodes, and ensuring the availability of the IXRE script before migration. There are three configuration types for migration, each with specific steps for connecting existing routers to the IXRE. Key requirements include checking current IXRE status, generating scripts if necessary, and following detailed connectivity and testing procedures for various node types during the migration process.

Uploaded by

Gaurav Singh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

IXRE CUTOVER PROCESS: -

 Before proceeding IXRE cutover make sure Site is nested for SI and we have confirmation and communication
with FE to start cutover.
 Take all nodes DCGK and backup on ENM.
 Make sure IXRE script is available before migration.
 Involve Leads for IXRE Migration

IXRE CONFIGURATION TYPES:


There are three of Existing router configuration is available and having below process to migrate.

1. SAR(( 7705 SAR-F)+SAS-Mxp(7210 SAS-Mxp) >>>>IXRE + Existing SAR( 7705 SAR-F):


 In this case main router SAS-Mxp will migrate with IXR-e & same SAR-F router will be used for GSM as extended
router.

2. Only SAR on site:

 In this case all GSM/UMTS/LTE/NR nodes are on SAR and will migrate with 2 different routers.
 SAR>>>>IXR-e + SAR
3. Only SAS-MXP on site:
 In this case NO GSM will be on site and SAS-Mxp will migrate with IXR-e

Requirements:

1.Check current IXRE and same confirm with FE on mail.

 Slipped  go to current AAV  CSR Type

 Login IXRE Router


a) Login current router

ssh [email protected] Password -> Integer@321


i. get router IP from slipped.
ii. CSR OAM router is main router Ip Example :11.167.214.188 and adding 1 value on IP
Example :11.167.214.189 will be for extended router(GSM Router).

b) check main and extended router by using command >>> show chassis
i. Main router

ii. Extended router

NOTE: IF site is already in IXRE no need to proceed.

2.ASK FE to fill below data and provide before proceeding for migration.

3.If script is not available need to generate IXRE script from pronghorn tool.
 Create Project with Site in https://pronghorn.internal.t-mobile.com/XG-CSR-Provisioning/#/
 Select options as per existing router and new router input from FE details from FE.
 Green field deployment will be yes only for 1st integration, In case of NO pre-existing router.
 10G AAV for main router input AAV >>>YES, FE should have fiber black haul, NO >>If copper back haul.
 IXRE HW version needs to select V1 >>GPS GRAND MASTER, V2 >>if internal GNSS is used.

 Click on device sync.

 Don’t do MAD router configuration for GSM extended router at the time of IXRE script generation.
(SKIP This step)
 MAD Router configuration will be executed if Extended router will be NEW or FE is using existing SAR
IXRE which is having all router configuration. As per below case only. FE will use existing IXRE which is
having all not configuration ,not only GSM.

 Click on DRY RUN then Export. (Don’t click on Download SW)


 Once you will click on Export then you will get script IXRE script pop up download option.
 Download IXRE script and share to FE.
 Click on GENERATE script for Extended router. (Fe will have login for ANPS tool for get extended router script if
needed.)

4.Once FE will load IXRE script and ready for migration. Follow below check points before migration:

 Check all BBU transports status. >> command >> get EthernetPort= >>>
 If Legacy is on 5216 >>TN-A is for transport, then It’s on electrical transport cable and will remain on 1G
No need to change port and upgrade to 10G.
 If nodes are on 6630, Transport should must be connected on TN_A/TN_B.
 If 6648 is available, it’s on TN_B/TN_IDL_B.

Example:

6648: -

6630: -

5. all tech GSM/UMTS/LTE/MMBBs once FE will be ready to confirm.

6.confirm with FE will connect New IXRE AAV back haul cable to IXRE port 1/1/1 input port.

7.once FE will connect AAV cable to IXRE .check IXRE connectivity to login with same CSR OAM IP.
 Login to IXRE and run command>>> show chassis
You will be seeing IXRE on router type.
If unable to login ask FE to check cable connection and involve Leads

1. Now we will have to go with test and execute method for all nodes.
(1) Legacy:
 Ask FE to not connect ant GSM/UMTS/MMBB nodes on IXRE.
 Ask FE to connect only Legacy BBU transport cable to IXRE port 1/1/3.
 Wait for some time to get legacy connectivity.
 Once you will get connectivity, please run Pre-IXRE port speed up.

 Once script executed you will lost connectivity from node, due to now transport is updated to
10G capability.
 Ask FE to connect legacy on IXRE port 1/1/4, that is reserved for legacy 5216/6630.
 Once FE will connect Legacy on 1/1/4 then you will get the connectivity.
 After getting connectivity, please RUN post Post_IXRE_LTE_TN_Update_V1.0 script.
 After run script check MME, cells and BBU port starts.

ssssssssssss

NOTE: IF legacy is 5216/6630 with TN-A transport port.

Check Router port speed for 1/1/4 and change it to 1G.

Command :- configure port 1/1/4 ethernet speed 1000

(2) MMBB600: If available, please repeat above steps with same to MMBB node.
 Only needs to connect MMBB600 BBU to IXRE 1/1/25.
 On MMBB node use Post_IXRE_Cut_MMBB_TN_Update_V1.0 after getting connectivity.
(3) UMTS:
 Ask FE to connect UMTS on IXRE port 1/1.3 that is reserved for UMTS 1G port.
 NO need to run any script.
 Once FE will connect transport cable check connectivity and unlock cells.
(4) GSM:
 Ask FE to connect GSM Extended router on IXRE port 1/1/2 that is reserved for GSM extended
router 1G port.
 if you are not getting connectivity please reach to Leads immediately.

You might also like