PAGE 1

DOS AND DONTS OF METASOLV

PROCESS
For MDF/NIC of SSAS

Abstract
The objective of document IS for updating the knowledge and knowhow for handling Inventory Reservation
Portal to minimize the error ofr Metasolv process

Windows User

Mslvcp.sz@gmail.com

PAGE 2

TABLE OF CONTENTS
Sl.No. Description

Page
No.

Dos and Donts of Metasolv Process

Manual updation of Inventory

CASE STUDY: FAILURE CASES OF CDR ORDER OF SSA

CASE:1 INVENTORY IS ALREADY PRESENT FOR THE S

CASE:2 Inventory Already Present

CASE:3 Warangal Issue: Inventory Already Present

CASE:4 Customer data could not be inserted for Subscriber

ID

CASE:5 Inventory reserved for closed order and again raising

the inventory for another order

CASE:6 MALAPPURAM Inventory Reservation Error

10

10

CASE:7 TUMKUR ISSUE ISSUE activation of service after

terminating orders

11

11

12

12

CASE:8: MALAPPURAM ISSUE: Inventory loading error for VPN

creation
CASE:9 PLAN CHANGE

13

CASE:10 DATA BASE ERROR

13

14

CASE:11 Inventory already present for the Telephone No.

14

15

CASE:12 MALAPPURAM INVALID CARD TYPE

16

16

CASE:13 NELLORE Opening of Multiple Session:

17

17

CASE:14 Malappuram Already Existing Inventory

19

18

CASE:16 STATIC IP CASE

21

13

PAGE 3

1.Dos and Donts of Metasolv Process

DOS
Exchange name should be strictly 6
characters.eg for KHAMMAM SSA the
exchange name should be KHMBPM
DSLAM IP should be /24 Format for eg:
10.236.164.3

DONTS
Exchange name given more than 6
characters (or) even though 6 characters
are given, sometimes appended with
space
DSLAM IPS are same for DSLAMs
connected to same BNG

NAS IP should be /32 for eg:

10.238.76.161/32

NAS IP is unique for BNG wise.Some

times it is given as range for the
DSLAMs connected to one BNG
DSLAM name must be concatenation of DSLAM name and exchange name are
found to be different in the Inventory
Exchange code and DSLAM IP. If exchange
shared by NIC some times appended
code is KHMBPM and DSLAM ip is
with NAS IP
10.236.164.3 then DSLAM Name must be
KHMBPM _10.236.164.3
KHMBPM _10.238.76.161
.

EMS IP should be unique for one DSLAM IP.

EMS IP is different for the same vendor
172.30.66.36 Vendor wise
for exchanges under same SSA
Port numbers should start from 1 and
end with number of port numbers of a
particular DSLAM For eg:
Slot No.
start port no
end port No.
1
1
72
2
1
72

Port no/Slot no some times given as

Slot No.
1
2

start port no
1
73

end port No.

72
144

PAGE 4

City name should be correct, and it should

be the same as given in Clarity and CRM
Module since it is configured across all
the system of ITPC.For Customer
City/Exchange name please verify the data
configured in clarity system and share it to
ITPC for data purity

For example exchange NAME of Bhir

should be given as BHIR not BHID/
CHENGALPET Exchange name should not
be given as Chinglepet.

NAS IP should be given correctly otherwise

It may lead to 691 error. SSA .Nodeincharge can ensure correctness of data
like NAS IP,Inner VLAN

Some SSA Shared BNG IP as NAS IP

NIC should submit ems IP & DSLAM IP

correctly. If ems IP is wrong MP network will
throw an error wrong ems IP. If DSLAM IP is
not given or wrong inventory will not be
available for that exchange.
Please follow the procedure given in the
manual for Inventory Reservation Portal
strictly.

Ems instance is missing for the NSN

DSLAM for most of the SSA inventories.

No inventory option in the Inventory

Reservation Portal should be used only for
the DSLAM Vendor Sterlite & Huwaei
For filling the Templates of DSLAM
INVENTORY please follow the guidelines
published in the BBNW/CORPORATE
OFFICE intranet.

Some times MDF punching the orders for

NSN,ZTE by selecting Vendor type as
UTSTAR and Service Orders got completed
successfully ,but any modification orders
raised for the same completed order, NIB
invoke error will appear.
MDF staff have chosen No inventory
option for UTSTARCOM,ZTE & NSN
DSLAMs by passing Reservation Process
resulting failure of METASOLV PROJECT
For NSN DSLAM card type shared by Node
in charges are ADSL instead of XDSL
resulting to error invalid card type also
Slot No given wrongly some times 1.

PAGE 5

For NSN DSLAM Please note that Slot For NSN DSLAM sometimes the inventory
Numbers will start from 202 or 101 in NSN of NSN Slot shared is single digit eg;1
not from 1.
Reserve one inventory uniquely for one
user id
Open only one session in the Inventory
Reservation Portal avoid opening multiple
tabs for reserving inventory

Shift orders the same port should be

selected which was wired and existing
Please check whether DSLAM Ports Which
is to be assigned to the customer are not
faulty and then raise the order
Before raising the order Please check the
DSLAM link,some times NIB receives
Service Order even for the DSLAM link
failure
Reserve Inventory which correspond to the
Vendor, after reservation of inventory
please export it.

Raising of two Service Orders successively

for the same user id leads to an error
Reservation is already Present
Opening of two tabs of Inventory
Reservation Portal by MDF and exporting
Inventory in one Tab and Manual entry of
Inventory in another Tab by choosing NO
inventory option.
Shift orders for the DSLAM of same port
MDF select new port
MDF without checking the status of port
they are punching the order, if PORT
FOUND TO BE FAULTY They raise Port
Change Order successively.
Dont raise Service Orders for the DSLAM
whose link is down.

Avoid manual updating in the Current

Value of Portal

PAGE 6

2.DONT do Manual updation of Inventory

Dont do any manual updating in the current value field of Clarity Portal Values should
be exported through Inventory Reservation Portal

METASOLV ISSUES DUE TO IMPROPER HANDLING OF INVENTORY

RESERVATION PORTAL

PAGE 7

CASE;1 INVENTORY IS ALREADY PRESENT FOR THE TELEPHONE NO

METASOLV issue
FAQ:
Unable to Reserve BB port via P3 Port reservation Portal in the BB provision order :44092592845 with
phone no:04285-241323. After selecting the available port, Failure report is showing.
[Note:The same customer closed his BB service on 30/12/2014 and again applied the BB provision
req. ]
ERROR MESSAGE

RETRY RESERVATION:
INVENTORY IS ALREADY PRESENT FOR THE TELEPHONE NO:
The error is due to order was closed at clarity end after reserving the
Inventory, and another order raised for the same user id which is showing the
error INVENTORY IS ALREADY PRESENT FOR THE TELEPHONE NO.

SOLUTION;Releasing of Inventory & Re firing of orders

PAGE 8
CASE-2:Inventory Already Present
Request from SDE NIB WGL ON 12TH MARCH 2015
Please Un reserve the inventory against the telephone no. for reconnection.
Order details

for the CDR order 44092564520 of Tel.No. 0870-2569514 .

Problem:There is a reserved inventory with cdr order number:44092454121,

Reason:Multiple order raised with same user id
Solution is :Inventory should be released for the old order.

CASE:3 Warangal Issue: Inventory Already Present

ACTIVITY:MODIFICATION (SHIFT & RECONNECTION)

The following orders showing
Error : INVENTORY IS ALREADY PRESENT FOR TEL_NUM while reserve the inventory. So please Un
reserve the inventory against the telephone no. for shift reconnection
Order details:
1.44092154267 of Tel.No. 0870-2447433
2.44092052607 of Tel.no. 08715-223224
SOLUTION:

The above orders are shift without port change orders, MDF should complete the
Task ( orders) without going for Navigation inInventory reservation portal.Only
for Shift with Port change activities requires selection of Navigation in clarity
portal and reservation of inventory in Inventory reservation portal of P3
SOLUTION: Code movement for the Shift fix has been done successfully in all zones by TCS

CASE:4:Customer data could not be inserted for Subscriber Id

ERROR: 0013:Customer data could not be inserted for Subscriber Id #2015-03-04T14:50:57

PAGE 9
REASON: This is a HDM failure during inserting in their DB due to VAR CHAR
LENGTH IS LONGER THAN SPECIFIED FOR Eg: User id should be 60 CHAR length if
it exceeds resulting the above error
CASE:5 Inventory reserved for closed order and again raising the inventory for
another order
Please check the below cases with Error Inventory is reserved with different CDR NUM. The
inventory reserved in metasolv with complete details are given below. Please let us know if the order
with which the reservation was done is no longer valid or cancelled and if we can go ahead with
changing the order number in Metasolv to the current order

Inventory reserved for closed order and again raising the inventory for another
order
INVENTORY RESERVED IN M6:

Solution: Changing SO No.

FOR EG: SO No33026994274 & sd6473224000_ecdrid , The task completed by modifying SO No; :

33027062286 after confirmation from ITPC.

CASE:6 MALAPPURAM Inventory Reservation Error

PAGE 10
Please resolve the inventory reservation error for the number 04931-222156.Herewith attaching the screen
shot of error msg.
I/V LAN -1199
O/V LAN - 2608
DSLAM IP - 10.236.88.9

The inventory is already present for the telephone number- 04931222156 for user-'us4931222156_scdrid@bsnl.in'.

Please find the screenshot

Please check and instruct accordingly.

The clarity Order no. 44089949588 to which the inventory is reserved in metasolv was cancelled at
Outdoor as customer not ready to take connection that time. Again a new order SO No. 44090865530 for
Broadband provision is issued.
kindly release the inventory already reserved so as to complete the new order.
Solution:
After releasing the Inventory problem resolved.
Case 6a:

Broadband Provision order for the number 04931-222156 with service id 44090865530 not resolved.
User id:- uh4931222156_scdrid
I/V LAN -1199
O/V LAN - 2608
DSLAM IP - 10.236.88.9
As it is urgent and hence it is requested to confirm and resolve the inventory reservation .

As per CDR, order is in MDF Inprogress. looks like the Node in charge has reserved Inventory but not
used Export Inventory to copy values to CDR

CASE:7 TUMKUR ISSUE ISSUE activation of service after terminating orders

PAGE 11
pl activate BB USER ID:tum225347_scdrid with tele no:04182-225347, because delete service order
no=44092011616 was cancelled with referance of the SM DOCKET:SD537170.
And Remedy docket no:HD0000006320824

Sir, this order is completely terminated in P3 since the termination order is complete .Profile is in
Marked For Deletion State in TDS.
Let us know what is the CDR status and if it has to be made active in NIB. Also mention the inventory
details associated with it if any to block the port in metasolv .
This case araises due to activation of service after terminating orders the status gone to Marked for
deletion,This issue can be resolved by deleting the status in TDS and releasing the inventory.

PAGE 12
CASE:8: MALAPPURAM ISSUE: Inventory loading error for VPN creation
Inventory loading error for VPN creation
Please see trailing mails. The error is getting while selecting Vendor as UTSTARCOM for MRXTIR
exchange. While selecting Vendor as NSN for the same exchange, the inventory is properly loading.
REASON: The issue is resolved. It was because of an extra space character in the DSLAM Names of

UTSTARCOM.
Please check and revert if the issue still persists
In case you have used up any UT inv for this, please do let us know so that the port can be consumed
back end to avoid further discrepancies .

COMMON ERROR/ISSUES DISCUSSION:

1. Inventory Available Flag mismatch between CDR and NIB . Reservation is done
through portal but the inv available flag is coming as N
This has been analyzed and reported to CDR. CDR has cited that it is due to
manual updates/wrong action by node in charges and has cascaded to ITPC
2. Order on which Inventory is reserved is being cancelled and another order is
pushed with same inventory
Fix has been deployed at CDR and P3 also has deployed a restriction in Inventory
Reservation Application
3. Wrong/Invalid Values in CDR XML to P3
Fix has been deployed at CDR
4. TCS working on fine tuning the error message of Inv Runtime exception to
restrict this to only webservice time outs and system unavailability. Rest cases,
granule error message will be thrown back to CDR. (Fix in progress, shall be
deployed by tomorrow)
Addition to this below fix is also being worked on to reduce load on operations
Plan Id is not configured for the UserThere should be dynamic mechanism to
update the plan id for the user if it is missed during pre-configuration at the time
of rollout.
Changes are involved both at CDR and NIB in the request XML. (Fix in progress,
shall be deployed.)

CASE:9 :PLAN CHANGE

PAGE 13
Pl.check and cofirm whether the dslam speed profile updation for plan change orders
is required in case of above 2Mbps Plans or 8Mbps Plans.In the recent discussions,
it is suggested to avoid p3 url selection for plan change orders where port change is
not required and hence mention how the dslam speed profile is updated for higher
speed plans.
SOLUTION:
In case of plan change, the speed profiles of old plan and new plan are compared at NIB
and in case of change for higher plan the request is sent to ASAP (Multiplay) for profile
updation.

CASE:10:DATA BASE ERROR

In following cases when we go to P3 portal and click on "GET VENDOR"

AN ERROR PROMPT namely "DATABASE ERROR" appears
and we are unable to proceed further.
phone no
0233-2621438
0233-2377621
0233-2333907
0233-2330793
0233-2624252

type of order
BB PROVISIONING
BB PROVISIONING
BB PROVISIONING
BB PROVISIONING
SHIFT BB RECONNECT

clarity order no
22048980544
22048959188
22048961087
22049007399
22048923586.

The screen shot of the error is also attached for reference

PAGE 14
1.

Solution:This error is due to slowness of Metasolv DB.

CASE:11 Inventory already present for the Telephone No.

Sir,
Rajkot SSA No. 0281-2570414 It is not going in to the error in BB INVOKE NIB stage
but when completed MDF task it goes to NIB DONE into INPROCESS after few
minutes it returns back to MDF task please resolve the problem urgently.
Re-trying reservation with different port fails and same port does not shows in
INNER VLAN.

PAGE 15

For this order and telephone number there was a reservation with service user
id mr2812451124_wcdr@bsnl.in and again they are trying to do a reservation with diff
user id which is why it is failing.
let us know How is the service user id changed and shd we unreserve this inv?

,
This is again a case of manual update of User Id,
Please note that manual update of user ids is causing these errors in the order flow.
From the audit result of service_order_attributes table, Service Order No 22048706067
has two values for BB_USER_ID whose initial value is mr2812451124_wcdr and the
same is changed to pj2812570414_wcdr from the terminal TASNIM-PC by the
user B199803817 . Hence two requests for the same order with different user Ids.
Please find the screenshot for the same.. For this order and telephone number there was a
reservation with service user id mr2812451124_wcdr@bsnl.in and again they are trying to do a
reservation with diff user id which is why it is failing.
let us know How is the service user id changed and shd we unreserve this inv

PAGE 16
SOLUTION:
UNRESERVE THE INVENTORY.

CASE:12.MALAPPURAM INVALID CARD TYPE

1. CDR # :44090750633
Dlam IP: MRXATV_10.236.82.24
Port : 37
Slot: 205
Inner vlan: 236
Outer vlan: 2324
Card Type: ADSL
2. CDR # : 44090449895
Dlam IP: MRXATV_10.236.82.24
Port : 32
Slot: 206
Inner vlan: 303
Outer vlan: 2324
Card Type: ADSL
3. CDR # : 44090443105
Dlam IP: MRXATV_10.236.82.24
Port : 35
Slot: 205
Inner vlan: 234
Outer vlan: 2324
Card Type: ADSL
1. CDR # :44090750633
Dlam IP: MRXATV_10.236.82.24
Port : 37
Slot: 205
Inner vlan: 236
Outer vlan: 2324
Card Type: ADSL
MP UPDATE : Please change card type as XDSL and refire the order
2. CDR # : 44090449895
Dlam IP: MRXATV_10.236.82.24
Port : 32
Slot: 206
Inner vlan: 303
Outer vlan: 2324
Card Type: ADSL
MP UPDATE : Please change card type as XDSL and refire the order
3. CDR # : 44090443105Dlam IP: MRXATV_10.236.82.24
Port : 35
Slot: 205
Inner vlan: 234
Outer vlan: 2324

PAGE 17
Card Type: ADSL
MP UPDATE : Please change card type as XDSL and refire the order

CASE:13 NELLORE,:Opening of Multiple Session:

Pl.resolve the following order failed in cdr for completion with the below given error
message.
44091032357 :: NIB FAILURE :9-Failure Inventory Check#
for the telephone number : 0861-2304499
The problem is identified to be wrong values from CDR in the request.
Pls REFER SCREEN SHOT

NIB has received "No Inventory" from CDR in the inventory details. NIB expects blank tags in case
inventory is not available.
Please find the attached screenshot and check
Please check the following request. Ideally <CardNum> and <PortNum> tags should be
empty. No string should be sent in the mentioned tags.
<21 Feb 2015 16:06:34:255> ****Request XML****<InvResvChkReq
xmlns="http://www.bsnl.com/InvResvChkReq.xsd">

PAGE 18
<CDROrderNumber>44091032357</CDROrderNumber>
<TelephoneNumber>8612304499</TelephoneNumber>
<ServiceUserID>pd8612304499_scdrid@bsnl.in</ServiceUserID>
<ExchangeName>NLRNWB,Nellore</ExchangeName>
<DSLAMName>No Inventory</DSLAMName>
<CardNum>No Inventory</CardNum>
<PortNum>No Inventory</PortNum>
<ServiceId>111</ServiceId>
<PlanID>100060231</PlanID>
<Activity>Create</Activity>
<Action>RESERVED</Action>
</InvResvChkReq>
REASON:
After proper analysis on the audit history of the order 44091032357 , we have identified
the below scenario.
In the MDF task , Inventory Reservation Portal is accessible and No Inventory was
selected by the user.
Double clicking on the link will open the Portal in 2 tabs.
Inventory data was punched manually and the task was closed. ( Task closed at
2/14/2015 17:59 ).
BB_OUTDOOR task moved to INPROGRESS state at 2/14/2015 18:01.
Since the portal is open in another tab, again No Inventory was selected and inventory
got exported to Clarity overwriting the current values (This happened at 2/14/2015
18:02).
Validations on these attributes are fired only in MDF task, and by this time MDF task was
already closed.
Hence inventory values as 'No Inventory' were sent in the XML also.
Fix from CDR ::
When Export Inventory on the Portal is clicked, Clarity Web service will be invoked. We
will have an additional check that values will be updated only if the MDF task is inprogress.
If MDF task is not progress, WS will through an error that 'Cannot update Inventory. MDF
task is not in-progress'.
Please let us know if we can go ahead with these changes.
This fix was moved during yesterday's downtime. No issues have been observed so far.

CASE:14 MRX Already Existing Inventory

PAGE 19
Dear TCS team,
Issue with inventory reservation case of 0494-2681080, SO no. 44090996353 not resolved.

The inventory details is already present for the telephone number -'0494-2681080' for
user -'ba4942681080_scdrid@bsnl.in'

Please find the screenshot.

Please find below the cause of the issue

There was a fault order raised on CDR with order number 44090736000.
Inventory was reserved from Portal . Pls see the reservation request in Metasolv
below

PAGE 20

But looks like the user hasn't used Export Inventory and copied it in Clarity and there is
no Invoke NIB request. See the order details in clarity below

So the inventory has remained in "Reserved' State only in Metasolv.

, Kindly get the info cascaed to the node in charges to avoid these mistakes
which will be difficult to capture in the flow down the line and these kind of
issues would be seen

PAGE 21
Inventory is unreserved now. Please proceed with the order

CASE:16STATIC IP CASE
In Clarity, "Plan change with IP Allocation" order is pending at the task "NIB_DONE"
since 10/02/2015 due to the error"NIB FAILURE: THE IP ALLOCATED HAS FAILED
VALIDATION.PLEASE ALLOCATE A DIFFERENT IP AND RESET THE TASK."
We are able to change the Static IP in clarity and the order is again saved with New Static
IP: 59.90.86.125. Still it is pending and the order details are mentioned below.
Service Order No: 44090721809
Phone No: 04294-260505
Old Static IP: 59.90.86.112
New Static IP: 59.90.86.125
The first IP is in Reserved State in Metasolv so the request has failed.
Second IP is free but we don't find a request in our logs with this IP. Can you check if it is
fired to NIB. Else pls refire IPAvailability and let us know if the issue persists.
Currently NIB task is in progress since 17-FEB-15 21:06:18.
IP value on the order as of now is 59.90.86.125.
Please see the request received from CDR. Even today it is refired. The IP received
is 59.90.86.112 and not the changed one.

Solution: change the IP and refire