NOC(Network and operations centre)

The task of provisioning the csts is done by NOC.By provisioning we

mean the creation of pvc(permanent virtual circuit) w/c is a must for the
users to connect to the n/w.theses pvcs are created for all the csts no
matter w/c DSLAM they are using be it Siemens,UT,Ericsson.

For Siemens---For both static n dynamic csts the pvcs are generated manually.For
dynamic csts the procedure followed is:

Interface atm<interface>point to point

auto_configure ppp
auo_configure ppoe
atm pvc 10053 1 53 aal5autoconfig 0 0 0

For static csts:

Interface atm<interface>point to point
Atm pvc<atm interface><vpi><vci>aal5snap 0 0 0
Ip description SSP_<username>
Ip unnumbered loopback<>
No ip redirects

For Ericsson
Static csts
Interface fast Ethernet<interface><ip>
Ip description SSP_<username >
Ip share_interface fast Ethernet
Ip unnumbered fast Ethernet
Ip source_prefix<ip allotted>
For dynamic csts
The pvcs are not created manually as they are on fast Ethernet.A common VLAN
is defined for all the csts on 1 site and all these connec through this VLAN.

For UT

Static csts

Interface fast Ethernet<interface>

Vlan id <>
Ip description SSP_<username>
Ip unnumbered loopback<>
No ip redirects

Dynamic csts

Interface fast Ethernet <>

 Vlan id< >
Ppoe
Ppoe auto_config
Ppoe profile any default

COMMON ERRORS IN NOC FOR W/C THE CSTS

CALL ON A REGULAR BASIS

ERROR 691

1.Username does not exist

Check for username if it exists in the database.If not then search for it in DSL(north) and encrypt it and push
to LDAP.If it already exists in LDAP then delete it from the database through user deletion and zipnet and
create it again manually.

2.Check for password

Password mismatch
Enter the username in the LDAP and verify if the user is entering the correct username and password.If not
then give the correct password.If yes then verify if it is being authenticated from the server side by giving the
commands mentioned below on the telnet session.

Test aaa ppp <email id> <password>

If he is being authenticated then this means that the user is typing the wrong password.

If not then check whether the pvc has been made and whether its tag is confirmed. Check out if any person is
logged in by typing the following command:

Sh subscribers username <username>

If yes then log out the other subscribers by typing the command mentioned below:

Log out subscribers username<username>

If the problem still persists then check customer login status and delete radius sessions as session hangs out
sometimes.

3. Interface mismatch
Ask for his ip address.
Find out the correct interface through the command mentioned below on the ERX router:

Sh ip route <ip address>

Copy the interface and insert it inside the text box of the dynamic user updation.

4.Check for touchtelindia.net

The spelling of the email address or the field in it may be wrong.

5.Other reasons
a)Local address pool may be missing in LDAP.Give it inside the text box of the option update local pool
along with user id.
b)Package plan may be missing then policies won’t be implemented.So the authentication failure exists.
Put the username in the textbox of option update rate plan.

ERROR 678

1.Check if the pvc has been made or not.If not then make it.
2.If the problem still persists then confirm the tag by locking and unlocking the cards.
Siemens
Making of pvc
1.Ask for the RSU and the tag.
2.Find the RSU in the main DSLAM sheet and copy corresponding interface.
3.Find that particular interface in erx2 notepad in case of interfaces (2/3,3/2,3/3,5/0,5/1) and rest of them in
erx1 notepad.
4.Now change the last 3 digits of the interface by asking the tag and ensure that the total no. of digits are 8.
5.Copy the command from erx notepad and paste it on erx router.
In case of username being created for the first time,fill up the following entries in the CAF:
a)username
b)VPI
c)VCI
d)interface
and encrypt and push to LDAP.Forward it in the OPS or installation as required.

In case of Ericsson and UT

1.Just fill the username.
2.Encrypt and push to LDAP.
3.Forward it to the required deptt.

Manual Creation of the user id

This is done incase javascript error comes up or if the entry is missing in LDAP and after pushing to LDAP
still the same error comes up.The following has to be done to resolve this issue:

1.Go to zipnet.
2.Give username and the region.
3.Click on continue.
4.A form appears.
5.Enter the required entries by seeing the record in DSL (north) CAF.

The following entries are to be filled:

a).First name
b).Middle name
c).Last name
d).Username
e).Password(Account id in CAF)
f). Package plan
g).Mail id [email protected]

6.Click the register button.

7.Check if not its entry is there in LDAP.

LOCK AND UNLOCK (Tag confirmation)

Siemens
1.Goto remote desktop.
2.Click on EMHIX5300 serva del.
3.Click on SNMP port.
4.Find for required region obtained from RSU in the main DSLAM sheet and the ip address given in the main
DSLAM sheet corresponding to the RSU
5.Click on the card for siemens.
6.Now lock the port by clicking on ADSL local.
7.Ask the user if his modem is off or not.If yes then the user’s tag is the one that he told.
8.If not then click on update status.
9.Make the user write all the active ports.
10.Now unlock the port determined through the calculations.
11.Again make the user write all the active ports again.
12.On comparing the 2 lists there will be one port missing which is the correct port of the user.
NOTE:If on locking the user’s tag the modem does not go off then ask him to get his tag confirmed from
MDF.

CARD AND PORT CALCULATION (For siemens)

1.Take the last 3 digits of the tag.

2.Subtract 31 from it as the first 31 cards are used for controlling purposes.
3.Then again subtract the host entry of the previous card from the result.The following is the required port:
For eg:Given tag is S10200
Now the following calculations give the correct port no.
1.200-31=169
2.169 lies in the third card.
3.So 128 is subtracted from 169 and we get 41.
4.Therefore,the 41st port of the third card will be locked and confirmed.

In siemens,there are 15 cards in total with 64 ports in each of the cards.

Slot(card) Card range
1 1-64
2 65-128
3 129-192
4 193-256
5 257-320
6 321-384
7 385-448
8 449-512
9 513-576
10 577-640
11 641-704
12 705-768
13 769-832
14 833-896
15 897-960

COMMISSIONING AND PROVISIONING OF NEW

SITES.
SIEMENS
For commissioning and expansion of new sites,SDH technology is used.SDH gives
an Ethernet drop both at the MSU n the RSU end.
In case of SIEMENS at the rsu end siemens dslam is connected to sdh ddf on w/c an
Ethernet drop has been given by sdh.This sdh ddf is connected to a fibre mgt
system(FMS) w/c passes the optical signal to the MUX whose o/p is an electrical
signal E1.This E1 then passes to ddf(sdh) w/c in turn goes to an DDF n then finally
terminates onto the STM cards of the ATM switch.Once we hve the E1s coming to
the ATM switch,E1s for tht particular siemens dslam at tht particular site are up n the
users connected to tht dslam are now in the n/w.The ATM switch is further connected
to the BRAS(ERX) w/c through the routers goes to the cst’s end.
UT
In case of UT the E1 passes from the DDF(SDH) to the central terminal(CT).On the
central terminal we have the EOE cards.One EOE card can suppor 8E1s.4E1s are
dedicated for 1 site,but at our end 2E1s are used for 1 site and the other 2E1s are
reserved in case there is some traffic.

ERICSSON
In case of ericsson,E1s from the SDH DDF goes to the FE toE1 converter. Thus the
E1s are through and the users for that particular RSU are in the network.

Ethernet drop
It is a 2mb link given by the SDH on both the MSU and the RSU end.This Ethernet
drop is given by the SDH at the RSU(DDF) from where it is brought to the DDF at
the MSU and finally to the ATM switch, EOE cards at the central terminal or to the
FE to E1 converters as the case may be.
 E1 LINE

E1 is the European format for digital transmission. E1 carries signals at 2 Mbps (32
channels at 64Kbps, with 2 channels reserved for signaling and controlling)

EOE CARDS
The cards on which the E1s for UT are terminated are known as the EOE cards i.e
Ethernet to E1.There is fibre connectivity between the EOE cards at the MSU end and
the EOE cards at the RSU end.One EOE card supports 8E1s.4E1s are dedicated for 1
site.But only 2E1s are used for 1 site.The other 2E1s are reserved in case there is
some traffic.

TYPES OF DSLAMS /CARDS

Bharti uses cards from 3 different vendors:

1.SIEMENS
2.UT
3.ERICSSON

SIEMENS
There are 3 types of cards:
LD
MHD
HD

1.LD:These support cards that have 2 slots of 32 ports each. Siemens have stopped
making these cards.
2.MHD:These support cards have 4 slots of 64 ports each.
3.HD:These support cards have 15 slots of 64 ports each.

IMA CARDS(ATM INVERSE MULTIPLEXING

CARDS)
The controller card in siemens is known as the CLUIMA card.It is the brain of the
siemens.This card has got all the softwares installed on it. A CLUIMA card can support
63 E1s.
The IMA card enables the XpressPass 140 to perform inverse multiplexing and
inverse de-multiplexing operations over the ATM network. It provides the ollowing
functionality:
 • The card can be used either as an IMA card or as a standard low speed ATM card.
• The card can function either as an NNI or a UNI card.
• Each IMA card supports up to 4096 connections, and up to four IMA groups.Each
IMA group can be comprised of one to eight ports (the maximum number of card ports)
and can contain spare links to use less than the total bandwidth available.
• IMA groups and their parameters can be managed dynamically, without disrupting
node traffic.
 Each IMA card can support upto 64E1’s which are made to come from the JACK
PANEL.
• These 64E1’s are then made to be aggregated in a thick cable which is patched
further in the data distribution frame.
• A connection from the IMA is made to the STM card from which optical fibres
OC-3 are terminated at the erx.

POSU (SPLITTER CARDS)

The splitter units are deployed as demultiplexers and each splitter unit has 16 or 32
interfaces.
There is another card known as the POSU card which acts as a low pass filter i.e it
segregates the voice and the data.A POSU card has got 32 ports.

The ADSL interfaces of the DSLAM are connected via the POSUs inserted in the splitter
subracks.
The splitters (POSU, POSN) are purely passive units which do not require a power
supply. Thus, availability of the narrowband services is not affected by any disturbances
in the broadband system.
.

32-port splitter subrack slot allocation

Another card known as the UPA card is used for signal management.

SUADSL cards are the ones on which all the subscribers are running.This is the card
through which the users connect to the internet.For 1 SUADSL card 2 POSU cards
are required.

UT
Cards for UT are known as the IPADSL on which the subscribers are running.There
are some voice cards as well like the PRI,BRI and FXS cards.The IPADSL cards
have got 24 ports each.ICM card is the controller card and it is the brain of UT.Other
cards that are used are FXS which is a voice card and an other is EOE card if the site
is running on EOE but if the site is running on microlan then there is no EOE
card.SCM is another card that is used for signal management.

ERICSSON

The Ericsson cards have 12 slots each of 24 ports. The various cards are mentioned
below:
1.EXN104
This card is a FE to E1 converter.It converts the data at 100mbps to data at 2mbps.

2.EDN312X17
 This card acts as a DSLAM i.e multiplexes the data and it also acts as a passive filter
segregating the voice and the data. These are the cards on which the subscribers are
running.

3.ECN320
It acts as a controller and a layer2 switch. This is the brain of Ericsson. This controller
card has got certain features like for example it acts as a DHCP, DNS, SNMP and it
also has a physical memory for the software.

4.ESN310
This card acts as a layer2 switch and works on PPPOE connection i.e power over
Ethernet.

5.EPN210
This is the power card and thus provides power to the various other cards.

ATM SWITCH

SURPASS hiD 3100

Key Benefits and Features

Optimize your access networks to dramatically reduce expenses, add new services to
increase revenues, and enable evolution to protect investments. The SURPASS hiD 3100
high-speed family is a versatile.

Multi-service switching platform that provides unrivaled port density and service
flexibility. The SURPASS hiD 3100 provides total flexibility of services and
applications. Both high-speed systems use the same software and service cards,
dramatically reducing operational costs.

Applications

High density broadband concentration

Streamlined 3G/2G mobile transport
Intelligent digital video broadcasting
Optimized Triple Play over DSL services
End-to-end managed multi-services
DATABASES, REPORTS AND RECORDS

We use 2 types of databases.One is on windows and the other is on solaris.Oracle

and java are installed on these operating systems.The ip address for windows
database is 172.18.201.18 and the ip address for solaris database is
172.18.200.31.The CDR files are stored in oracle database and a script ran by us
queries the cdr files.

The various kinds of lists that are generated using the LDAP dump are as follows:

Package list:
In this list we have the information of all the packages on which users are
running.We get to know the no. of users on each package.We take all this
information from the LDAP dump like the no. of users on each package in each
region.We also define the policies for each package in this list.But there are
certain packages which are used just for testing and so no policy is defined for
such packages.

Policy list
Another is the policy list which is created as n when required.this list shows the
policy that is binded with each package.The committed and the peak bandwidth
and the rate limits are also defined in this policy list using the LDAP dump.

Bandwidth list
This list shows how many csts are having the bandwidth greater than 256 and less
than 256 in each region.These lists are generated once in a month.

For MP csts

The records of the MP csts are generated in the LDAP at the Delhi centre.The MP
csts run on FE technology.Reports for these csts are generated once in a
week.Another list is generated which shows all the static csts of MP running on
6/7 interface.

Another list is generated which shows whether a package is time based or usage
based.This information is required while billing as the cst is billed depending
upon whether the package is time based or usage based.

A list which gives information abt the various pools that have been defined is also
generated.This list tells us how many csts are defined in each pool,how many ips
are being used and how many ips are free at any given moment in a particular
pool.

Each cst’s password history can also be found out from the LDAP dump.
If a particular cst is port binded then we can take out the records which tell us
which cst in a particular area is port binded and to which interface.A script is ran
which reads the description field.This script gives the information about the
interfaces binded to the different csts in one particular area.During shifting the
description field is changed to roaming by running another script.After the
shifting has been done,the cst is port binded to another interface by running
another script.

The CDR files are generated on the RADIUS and they are processed according to
a program.These files are then inserted in the database for :
1.Billing issues
2.To check the ip details in case of CBI inquiry
3.To check if correct packages are binded to the csts.

In LDAP only the following 4 commands can be executed.

1.Add
This command is used to add a new attribute like a new package for the cst can be
added using this command.
2.Search
This command is used to search the cst details using his username as the
username is unique for each cst.
3.Delete
This command is used to delete a particular attribute as and when required.
4.Modify
This is used to modify a particular attribute of the cst like his
package,username,password etc.

CDR FILES
CDR(call data records)---The CDR files are generated on the radius n 2 files are
generated everyday. They contain the following information:

1.username
2.ip address
3.status(start,stop,interim)
4.package being used by the cst
5.policy applied
6.interface given to the cst

LOG FILES

There are 3 types of log files:

 1.ssp_error--- These are generated on the SDX.Errors regarding policy,package
n authentication failures are maintained in this file.This file gets updated on a
daily basis.

2.ssp_debug---- This is also generated on the SDX..This file maintains the

different errors that come up from time to time.This file identifies the errors n
why these errors came up.

3.auth log files----These files are used to keep track of the csts those who are
getting error 691 in case of authentication failure.These tell us whether the cst is
accepted or rejected depending upon the username he is using. Or the interface
being used. The auth log file maintains the following fields:

1.date
2.time
3.bras1 or bras2
4.username
5.accepted/rejected
6.ip address
7.interface

CUSTOMER QUERIES

The csts come up with different queries from time to time.The various queries are

1.if a cst cannot view his usage online

2.usage is unexpectedly high
3.cst plan has been changed even though he never placed ne request for the same

Websites n their usage

1. North.airtel_broadband.com/addnew_admin.jsp-This website is used to add,delete

a cst,to update the rate plan and the port number,to check user details in ldap.

2.There is another website to view the MRTG(multi router traffic gropher) graphs of
all the devices.The site is http://172.18.200.40/cgi-bin/routers2.cgi

3.. 172.18.200.19/nocportal.jsp-In this site we have the following:

OSS
LAST LOGIN
ERX
ERX UTILIIES
 SMS
NOC INDEX
MDF INDEX
LDAP
In OSS we have the bcc deptt w/c has the following rights
1.upload file for barring n unbarring
2.view-uploaded files
3.view barred csts
4.view unbarred csts
5.view terminated csts
6.search by acct no.,username n interface
7.bar a single cst
8.self unbarred csts yet to be approved
9.self barred csts approved
10.self unbarred csts rejected
11.monthly usage of csts with usage based plans
12.view e-bills from cdr’s

In Customer Care we have the following:

Categories of Customers
1 View terminated (deleted) customers
2 View barred customers
3 View un-barred customers
4 View customers with rejected cheques
5 View Self unbarred customers approved
6 Self unbarred customers yet to be approved
7 Search
8 Error 691

In Fault Repair we have:

Check Login with password

 
Check customer login status
 
Change Password
 
Error 691
 
Check User Package in LDAP

In E-bill we can view the bill of the cst from start date to stop date.

In TAC we have the following:

Check Login with password
 
Search for IPs routed in ERX
 
Check customer login status
 
Logged in Customers
 
Search Bar / Unbar
 
Change Password
 
Static Information
 
Error 691

In MP WE HAVE THE FOLLOWING INFORMATION:

Check Login with password
 
Check customer login status
 
Change Password
 
No of Customers logged in ERX1
 
No of Customers logged in ERX2
 
User Deletion
 
Error 691
 In Punjab we have the following:
Check Login with password
 
Update Rate Plan
 
Change Password
 
No of Customers logged in
 
Check user in LDAP
 
Error 691

The installation guys can view the details using the caf no.,touchtel no.and user
i.d.
We can also view the pwd change history of the cst.

In Last Login we can jst view when the cst was logged in the last time.

In ERX we can view the following:

Static interface
Dynamic interface
Shut interface
Vpn
Search by interface,ip,username

In ERX utilities we can view the following:

Port summary
Utilization

In NOC Index we have the following:

1. User Deletion
2 Static User Updation
3 List Static Users
4 Update Rateplan
5 IP(/24) list
6 IP Details Table
7 Dynamic User Updation(Port
 Binding)
8 Error 691
9 Update Local Pool

In ldap we can view cst details by outing the username n the location. The details
appear in the following format:

User Details in LDAP

businessCategory none
anonymous FALSE
preferredLanguage none
homePhone none
givenName dinesh
postalCode none
objectClass umcUser
facsimileTelephoneNumber none
uniqueID dinesh_del
Mail none
Cn dinesh
Initials none
telephoneNumber none
Street none
L none
postalAddress none
Sn saini
userPassword 12345
description roaming
usedService serviceName=access,o=Services,o=UMC
Uid dinesh_del
objectClass umcRadiusPerson
serviceName access
aaaReply Class=2,uid,access
radiusClass 2,uid,access
localAddressPool combo128
userPassword 12345
sspState SUBSCRIBED
sspAction ACTIVATE_ON_LOGIN
objectClass sspserviceprofile
serviceName DSL-Home128
BILLING AND MEDIATION

Arbour is where the billing is done.Arbour collects the information from the CDR
files,formats it according to its requirement and then uses this information to
generate the bill at the end of the month.The csts are billed depending upon the
package they are using.There are 2 types of packages :

1.Usage based package –The cst is billed depending upon the usage i.e the amt of
data he has uploaded n downloaded.
2.Time based package—The cst is billed depending upon the time for w/c he was
logged in.i.e the time for w/c the user used the internet.

Csts are also billed depending on whether they are static or dynamic.
Static csts are billed depending upon the interface they are using where as the
dynamic csts are billed depending upon the username.

BARRING AND UNBARRING OF CUSTOMERS

A cst is barred if the due date for the bill to be paid has passed.The procedure for
barring is as follows:
The billing deptt. Sends some information like the acct no.,amt due and the
username to the technical deptt. Using this information a script is run in the ldap
w/c changes the cst’s package to DSL BARREDdue to w/c the cst is able to view
only some sites for example the site to view his usage online.

The cst pays the bill,menions his cheque no.,amt due and name of the bank.This
unbars the cst for 2 days automatically.If this information is found fake then the
cst is barred again.

Now once the cst has made the payment the bcc deptt. sends this information and
a script is in the ldap w/c picks up the old package from the database n tht
package is now applied against tht cst.So now the cst’s package is again changed
from DSL BARRED to his original package i.e the cst is unbarred n can make full
use of the internet connection.
 Mediation Process
The mediation server filters out the unwanted data.All the billing information goes to the
arbour through the mediation server.The CDR file in the mediation server has got 28
fields.Some of the unwanted fields are dropped in the mediation field and by the time the
files reach the arbour only 5 fields are left.It has to be defined in the mediation server as
to which data is important and which is not.Package information is the most important so
a file in the mediation server is dropped if it does not have the package information.

Flow of Package Configuration

1. Request comes from Marketting to DSL NOC.

2. DSL NOC configure package in LDAP. send request to RA
3. RA validate and send request to Local IT.for configuration in mediation. and
send request to configure in arbour.
4. Local IT validate that name again and send request to CSO for configuration.
5. CSO configure the name in mediation.
6. IT configure the marketing name & LDAP name in CAF

Format :
Package name=10260=D=S
Package name=10261=V=K

10260 duration based

10261 volume based

D duration
V volume

S second
K kilo byte

Flow of CDR file transfer

1) File transfer from RADIUS to 172.19.4.1

2) File transfer from 172.19.4.1 to Mediation server 1(first level mediation)
3) There are two first level mediation server for failure recovery.
 4) From first level mediation server it transfer to Mediation Main again there are two
server for mediation main.
5) Mediation main is in HA (High Active) mode.
6) After data filtering it stores in the storage server.
7) Storage server is of SAN size 13 TB.
8) The data is again transfer to 172.19.4.1
9) The data is sent to BBNL for WEB Display. and To Arbour .
10) BBNL runs SQL Loader for data loading in server.
11) In Arbour data is divided in to two parts Rating wise: Billed & Suspense.
12) For Suspense data there is some reconciliation process MIUB.
13) There is write off in case of waiver to customer.

Difference between Mediation & Arbour

 Mediation is just filtering the CDR file to the appropriate data recognizable by
Arbour.
 Arbour is a billing system which understands the chargeable criteria. (i.e 5 rs for 1
Hour or 5 rs for 100 kb.)in respect of time & data.
 There is rejection in both case
 Mediation rejects the non billable records.
 Arbour rejects the billable records which has no owner means customer name is
not defined.
 XACCT is our mediation server.
 Arbour is of CNG Systems.

Rejection Process of Mediation

 The records without Stop & Interim records.

 The records where acct_session_id not starting from Zip or DSL.
 The records in which there is any package name not configured in Mediation.

Rejection Process of Arbour

 The records in which username is not binded by account id in case of dynamic.

 The records in which interface is not binded by account id in case of Static.