done

@Ahad:Please share update

updated xml share on teams chat.

Hi Dharmendra,

As discussed License has missing nodeid , please fill it and nodeObjectId has to be ipadress not node name.

XML import done , cehcking the errors based on errors if found any issue will update it here

updated xml shared.
Note- interface type issue is still coming because of interface type not available in updated version.

New models should be created in NEP for nodeinterfaces ... for the remaining to be delivered by 28-1 EOD

NEW LIST TO SHARED TO DHARMENDRA ALSO WRING SERIAL , SPACE IN DESCRIPTION , UNKNOWN INTERFACE TYPE

Hi Dharmendra,

As discussed still more than 4k nodeinterface not parsed , data shown and shared to you via teams chat.

updated xml shared.

to be delivered by 23-1

we need to consider port and NE reports. Ahad has to update the FRS and attach these 2 reports.
To be completed by 23-1 the first half

dev WL - 1.5 days

to be started on 21-1 and Dhamendra to define the WL

HUAWEI IP FEEDBACK

Changes/feedback

1: For NE Name : If the “Subrack ID” column has value 2 than don’t parse that node from NE , because that is repeated with Subrack ID = 1

2: Same rule added for NE id

3: Node shelf doesn't have proper data , blank records for 795 records, for ex: node id : 66-55618

4: In shelf from where model is coming , there is no rule in FRS for that.

5: 76 boards are missing

6: wrong id for board 32-56864/1/1/11/61

7: slotId is missing for 15427 , for ex: 112-63995/1/1/7/0

8: nodeBoardid in nodeinterface report seems wrong , 112-63995/1/1/7_0 , why underscore ?

9: Interface type coming unknown for ex : 112-63995/1/1/7/0/10 , but in dump it is ESPF

saurabh to check the GAPS

As discussed with Ahad , inventory dumps are ok and validation closed.

for Catalogue Jira has been created : ZKU-149

FRS Preparation Jira ZKU-126

WL= 2 mdays

XML Validation
1: All nodes are on Auto Site in XML
2: Naming convention is totally wrong.
3: Dumps are of 23rd October.
4: Main FRS need to be create in a proper way as currently in network element getting multiple records for single node.
5: In others customers we have received NE_REPORT CSV dumps as well where routers details were present .