8/2/2019 Notas SGSN

1/19

RSG (Remote Support Gateway)IP: 146.250.58.38

User: egabsamPassword: BBmHvf3t

GTT2User: egabsamPassword: BBmHvf3t

SGSNUser: GNOCPassword: ericsson123

su wpp_admin

Libreria SGSN-MME 2010A CP03

Name:- vinod KumarEmail:-vinod81in@yahoo.co.inGSM:-+5215530567863

Name: Ismael GonzalezEmail: ismael.gonzalez@ericsson.com

GSM:55-27-05-10-55

Name: Roberto de Jesus UrbinaEmail: roberto.de.jesus.urbina@ericsson.comGSM: 22-23-23-20-92

8/2/2019 Notas SGSN

2/19

Hardware components

Magazines (1)o Magazine 1

o Magazine 2

o Magazine 3 (optional)

PIUs (Plug In Unit) (2)

Backplane (3)

Magazines

The SGSN-MME cabinet houses two or, optionally, three magazines. Each magazine carries amaximum of 21 PIUs interconnected through the backplane.

PIUs

The magazine identification are set on the two Power and Ethernet Boards (PEBs) in the magazinesupervised by all PIUs. A mismatch between the settings in the two PEBs in the magazinegenerates an alarm.

http://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0666.htm#chlMagazines#chlMagazineshttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0666.htm#chlPius#chlPiushttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0666.htm#chlBackplane#chlBackplanehttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0666.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0666.htm#TOP#TOPhttp://edw//alex?ac=image&fn=35_22102-AXB25005_8Uen.H-sgsn_cabinet_3mag_r3.eps.pdfhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0666.htm#chlPius#chlPiushttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0666.htm#chlBackplane#chlBackplanehttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0666.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0666.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0666.htm#chlMagazines#chlMagazines

8/2/2019 Notas SGSN

3/19

Backplane

The backplane of a magazine provides dual redundant power distribution as well as dualredundant Ethernet connections to all slots in the magazine.

Software

The SGSN and the MME software are both divided into two main parts; the platform and theapplications.

The platformconsists of Operating Systems (OSs), a Distributed Processing Environment(DPE), and application support such as connectivity involving drivers for the IP, Frame Relay,SS7 protocol stacks, and SCTP.

On application level, the software is divided into a control system and a transmissionsystem interconnected through the backplane as illustrated in Figure 29.

Figure 29 SGSN-MME Software Architecture on Application Level

SGSN

MME

The platform (OS, DPE, Apps)

The application

Control system

Transmission system

Executes on all PIUs

http://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0666.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#figSgsnSoftwareArchitecture#figSgsnSoftwareArchitecturehttp://edw//alex?ac=image&fn=35_22102-AXB25005_8Uen.H-sw_arch.eps.pdfhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0666.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#figSgsnSoftwareArchitecture#figSgsnSoftwareArchitecture

8/2/2019 Notas SGSN

4/19

Control System

The control system is designed to process high-level protocols and to control payloadrouting in the transmission system. It handles traffic control activities, such as mobility andsession management and high-level protocol processing; system-internal control activities, such

as recovery, distribution, and O&M; and adaptation activities, such as transmission systemdrivers.

The control system consists of a number of APs interconnected through the backplane, see Figure30.

Figure 30 SGSN-MME Control System Architecture

The central AP (AP/C) handles the central functions of the control system and runs on the PIU thatserves as active NCB. The remaining AP PIUs host one local AP each and form a genericprocessing pool in order to provide shared load handling.

3.2 Transmission System

The transmission system enables high-performance and high-efficiency payload routing betweenthe SGSN and other GPRS backbone and radio network nodes.

The transmission system includes:

Forwarding and routing of all payload traffic between the Radio NetworkController (RNC) or Base Station Controller (BSC) and the Gateway GPRS SupportNode (GGSN) Forwarding and routing of SS7 traffic Termination of the lower protocols of all interfaces

The transmission system consists of a number of DPs, IP routers, SS7, and SCTP front ends asillustrated in Figure 31.

http://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#figSgsnControlSystemArchitecture#figSgsnControlSystemArchitecturehttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#figSgsnControlSystemArchitecture#figSgsnControlSystemArchitecturehttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#figSgsnTransmissionSystemArchitecture#figSgsnTransmissionSystemArchitecturehttp://edw//alex?ac=image&fn=35_22102-AXB25005_8Uen.H-cont_sys_arch_r2.eps.pdfhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#figSgsnControlSystemArchitecture#figSgsnControlSystemArchitecturehttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#figSgsnControlSystemArchitecture#figSgsnControlSystemArchitecturehttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#figSgsnTransmissionSystemArchitecture#figSgsnTransmissionSystemArchitecture

8/2/2019 Notas SGSN

5/19

Figure 31 SGSN-MME Transmission System Architecture

3.3 Software Components

Each software component in the SGSN-MME is described below. The common softwarecomponents are used in both SGSN and MME.

3.3.1 Common Software Components

ApplicationProcessor

The AP handles traffic control activities, such as mobility and sessionmanagement and high-level protocol processing; system-internal control

activities, such as recovery, distribution, and O&M; and adaptation activities,such as transmission system drivers.

Boot ServerThe Boot Server provides node internal boot services in the SGSN-MME, forexample Trivial File Transfer Protocol (TFTP) and Dynamic Host ConfigurationProtocol (DHCP) services.

File ServerThe File Server provides node internal disk storage in the SGSN-MME, forexample, Network File System (NFS) service.

IP Router

The IP routers determine the optimal routing paths and handle transport of IPpackets through the General Packet Radio Service (GPRS) and Evolved PacketSystem (EPS) networks. This can as an example be O&M traffic, SS7 over IP

traffic and all MME traffic.

IP routers are distributed over the router PIUs; although several routers canshare the same router PIU, each IP router serves its own Virtual PrivateNetwork (VPN).

LI Device The Lawful Interception (LI) device supports the LI function.

SCTP Front EndThe SCTP front end handles and terminates the SCTP associations. It alsosupports the SS7 back end for SS7 over IP and the SCTP device for the S1-APand Diameter protocols.

http://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#TOP#TOPhttp://edw//alex?ac=image&fn=35_22102-AXB25005_8Uen.H-trans_sys_arch.eps.pdfhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#TOP#TOP

8/2/2019 Notas SGSN

6/19

3.3.2 SGSN Specific Software Components

Charging Device

The charging device collects charging information for Charging Data Record(CDR) based charging and Customized Applications for Mobile networkEnhanced Logic (CAMEL) based charging. The generated SGSN - ChargingData Records (S-CDRs) are forwarded to the NCB for persistent storingand to the local AP for transport by GPRS Tunneling Protocol Prime

MS Device

Each MS device represents a number of MSs. When a new MS enters the GSM,the MS device for the connection is selected based on the MS identity. Thisallows an evenly distributed load.

The MS device handles the connection-oriented part of BSSGP, the Logical LinkControl (LLC) protocol, and the Subnetwork Dependent Convergence Protocol(SNDCP) over the Gb interface. In addition, Mobility Management services arepartly allocated to the MS device.

SS7 Back EndThe SS7 back end represents the upper layers in the SS7 stack, and handlesSS7 traffic, registration and deregistration of SS7 users as well as providingthe SS7 user with information on the status of local and remote subsystems.

SS7 DeviceThe SS7 device is a traffic-forwarding device which keeps an associationbetween established SCCP connections or Transaction Capabilities ApplicationPart (TCAP) dialogs and the corresponding MS representations on the APs.

Software Redundancy

The software components are distributed over the SGSN-MME in such a way as to achieve loadsharing and redundancy on the software level. If a software component fails, another of the sametype will take over the processing until the failing software component is back in service.

Revisar la lista de BSCs

The list_bsc command lists all the existing BSCs.

The optional operands specify the objects and values to list, according to the following:

gsh list_bsc

ps Class Identifiers |---------------------------------A bsc -bsc BSC101

http://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0708.htm#TOP#TOP

8/2/2019 Notas SGSN

7/19

A bsc -bsc BSC102A bsc -bsc BSC103A bsc -bsc BSC103-LethemA bsc -bsc BSC104A bsc -bsc BSC105

1. Revisar las NSE (Network Service Entity) de las BSCs

list_nses [-a]

The list_nses command lists the identifiers of all existing NSEs. When using this command

Without the operand a , only the NSEs used for Gb over Frame Relay are displayed.

With the operand a, all NSEs including NSEs used for Gb over IP and NSEs used for Gb

over Frame Relay, are displayed. Each NSE is followed by the type of carrier protocol(Frame Relay or IP).

gsh list_nses

2. Verificar las NSVCs (Network Service Virtual Connection) conectadas a lasNSE y a que BSC pertecen

Cada NSE corresponde a una BSC

gsh get_nse 1 (1 to 6, dependiendo de las NSEs enlistadas anteriormente)

NSEI : 1Connected BSC : BSC101

NS-VCs : 121,124,131,141,151 (NSVCs que pertecen a esta NSE)

3. Verificar la lista de NSVCs (Network Service Virtual Connection)

The list_nsvcs command lists the identifiers of all existing NS-VCs.

gsh list_nsvcs

151161122153

124162143135144131154155142163

8/2/2019 Notas SGSN

8/19

152121123133134141

132164

4. Verify all the NSVC status for the all NSVS status should be de-blockedand alive if it is not standard then need to take the action or escalate tothe concern team.

The get_nsvc CLI command displays the attributes of an NS-VC.

gsh get_nsvc 121 (Revisar todas las NSVCs)

NS-VCI : 121

NSEI : 1

Board : NE/Magazine 2/Slot 2 (PIU (Plug-In Unit))

Equipment Identifier (M,S,P,F) : 2,2,1,1 (Magazine, Slot, SubBoard, and ProcessingModule)

E1/T1 trunk : 1 (parameter specifies the trunk number of the interface board)

Fraction : 1 (A fraction is a channel that consists of one or more time slots.Valid values for a fraction depends if it is run in channelized or non-channelized mode)

DLCI : 121 (Data Link Connection Identifier)

Blocking State : deblocked (Indicates that the NS-VC is allowed for BSSGP traffic)

Operational State : alive (Indicates that the NS-VC is able to provide communicationbetween peer NSEs)

Verify if there are some Blocked cell in the BSCs if there is block cell/sites then need toescalate to Concern team. All the sites status should beavailable and de-blockedstate.

gsh list_bvcs -nse 1 (1 a 6, dependiendo del numero de NSEs)

orgsh list_bvcs -bsc BSC106 (Revisar todas las BSC enlistadas en el punto 1)

PTP BVC [NSEI-BVCI] Cell [MCC-MNC-LAC-RAC-CI] Operational State Blocking State BSC Name

1-15 738-002-100-1-513 available deblocked BSC1011-32 738-002-100-1-1051 available deblocked BSC1011-64 738-002-100-1-211 available deblocked BSC1011-96 738-002-100-1-1483 available deblocked BSC1011-112 738-002-100-1-1492 available deblocked BSC101

8/2/2019 Notas SGSN

9/19

1-128 738-002-100-1-483 available deblocked BSC1011-160 738-002-100-1-1513 available deblocked BSC101...

Verify List Active Alarms id is there any major and critical alarms then escalate to concernteam

gsh list_alarms

43624 nsNsUnblockRetriesExceeded 2011-10-18 15:45:34 mbv_GbConfigurationmajor communications 1710073628 NS Unblock hasnot been responded from BSS for NS-VC number 133.

43747pmSupThresholdCrossedMaj 2011-10-19 14:54:33 measTypeIndex 1major qos 1715753751 The value ofmeasurement type bssgpStatusBvcUnknown has reached its threshold.

43845nocSupervisedMeasMin 2011-10-20 16:33:18 noc_alarmServiceminor processing 1722033849 Measurement typegprsMmSgsnUnsuccessfulAttachRequests has exceeded its threshold.

NOTA: Las alarmas por contadores no se tienen que reportar por que automticamente al llegar aun valor preestablecido estas se reestablecen.

Verify WHO is connected on the Equipment

who

Verify CPU Utilization counters IBXXs Boards every Hrs Counter value should be change

as per the Utilization.pdc_counters.pl -n5 -c SYS. -ti

En esta opcin se muestran los contadores por las ltimas 5 horas, aqu se debe revisar que loscontadores no se congelen y que tampoco se desborden o se caigan repentinamente.

============================================================Month: Oct PDC Counter Values

Counter Name 10/20 16:00 10/20 15:00 10/20 14:00 10/2013:00 10/20 12:00============================================================

GTPP.CdrTransfReq.1 : 3079087 3067325 3056134 30457883034921GTPP.CdrTransfReq.2 : 639 639 639 639639MM.AttNormalIntraSgsnRaUpdate.G.73800200100001 : 863446 859346 855429851446 847500MM.AttNormalIntraSgsnRaUpdate.G.73800200101001 : 111227 110671 110034109349 108635MM.AttNormalIntraSgsnRaUpdate.G.73800200101002 : 216537 215468 214525213360 212182

8/2/2019 Notas SGSN

10/19

MM.AttNormalIntraSgsnRaUpdate.G.73800200102002 : 414443 413204 411921410631 409209MM.AttNormalIntraSgsnRaUpdate.G.73800200103001 : 1332072 1325876 13201241314022 1308019MM.AttNormalIntraSgsnRaUpdate.G.73800200104001 : 344864 343595 342401341129 339996

MM.AttNormalIntraSgsnRaUpdate.G.73800200104002 : 284474 283554 282768281847 281118MM.AttNormalIntraSgsnRaUpdate.G.73800200105001 : 398148 396239 394082391806 389518MM.AttNormalIntraSgsnRaUpdate.G.73800200105002 : 850370 848058 845514843041 840547

Verify the links utilization and attached/active subscribers status always should be somecounts if not then need to escalate to concern team.

eci stats

This tool can display

This command can be used to find out in which state a given subscriber is. It is very useful foranalyzing further hanging subscribers. Subscribers that are unable to activate PDP contexts/EPSbearers or subscribers unable to attach, can be debugged with this command.

stats This option displays connection statistics for SGSN-MME.

dist This option displays distribution of connections over APs.

list This option prints a list of subscribers in SGSN-MME.

details This option prints connection details for a given subscriber.help This option displays instructions.

NOTA: Los valores de eci stats no deben estar en cero.

Verify Context distribution on GPB boards

eci dist

This command prints a summary of the connection state, the external IDs and the context

location for the specified connection.

The connection can be identified by Cid or any of its external IDs like IMSI, MSISDN, TLLI, PTMSIor TMGI.

Optionseci details -cid [Cid] | -imsi [IMSI] | -msisdn [MSISDN] | -tlli [TLLI] | -ptmsi [PTMSI] | -tmgi[TMGI]

8/2/2019 Notas SGSN

11/19

This is eci version 1.0.0 operating on an SGSN/MME '10A-00-05' (WG).Distribution of SGSN-G connections over GPBs:

GPB active attached idle unstable total replica---------------------------------------------------------------------------------

1.10.2.1 217 2309 2972 12 5510 ( 11.1 %) 2549 ( 11.2 %)1.12.2.1 198 2326 2966 7 5497 ( 11.0 %) 2490 ( 10.9 %)1.13.2.1 210 2354 3016 7 5587 ( 11.2 %) 2499 ( 11.0 %)1.14.2.1 216 2338 3071 7 5632 ( 11.3 %) 2510 ( 11.0 %)1.15.2.1 218 2320 3126 8 5672 ( 11.4 %) 2583 ( 11.4 %)1.16.2.1 202 2294 3028 8 5532 ( 11.1 %) 2510 ( 11.0 %)1.19.2.1 0 0 0 0 0 ( 0.0 %) 0 ( 0.0 %)1.20.2.1 0 0 0 0 0 ( 0.0 %) 0 ( 0.0 %)1.8.2.1 208 2333 2957 12 5510 ( 11.1 %) 2508 ( 11.0 %)1.9.2.1 213 2228 2998 6 5445 ( 10.9 %) 2556 ( 11.2 %)2.20.2.1 211 2276 2986 4 5477 ( 11.0 %) 2542 ( 11.2 %)---------------------------------------------------------------------------------Sum 1893 20778 27120 71 49862 22747

Verify the check point backup active SC (software configuration) and default SC should be same ifnot then escalted to concern team.

gsh get_active_sc

gsh get_active_scReleaseName : cxp9011380_8r11b11_0_0_mergedCheckpointName: AfterMigrationallOK

gsh get_default_scReleaseName : cxp9011380_8r11b11_0_0_mergedCheckpointName: AfterMigrationallOK

gsh get_next_scReleaseName : cxp9011380_8r11b11_0_0_mergedCheckpointName: AfterMigrationallOK

Verify next restart, last restart and default/active SCs

Entrar como Super User su

listSCs

Check which SCs that are available by performing

8/2/2019 Notas SGSN

12/19

# listSCs

cxp9011380_8r11b11_0_0 (10A-00-00), 2011-08-28 21:20:42, Obsoletecxp9011380_8r11b11_0_0_merged (10A-00-05), 2011-08-28 21:20:56, InstalledCompletedBasiccfg300820112015, 2011-08-30 20:15:51, CheckpointCompletedCOnfigwithGomBeofreSS7, 2011-08-30 22:10:33, CheckpointCompleted

IncompleteGomWithSS7, 2011-08-30 22:30:31, CheckpointCompleted

GomGnGrConfig, 2011-08-31 16:04:50, CheckpointCompletedGomGnGrGbFRConfig20110831, 2011-08-31 19:39:35, CheckpointCompletedGomGnGrconfignolic, 2011-09-01 16:02:52, CheckpointCompletedGomGnGrIuuCfg, 2011-09-01 19:09:57, CheckpointCompletedGomGnGrIuCfg, 2011-09-01 19:46:12, CheckpointCompletedWIthIPSPDown, 2011-09-02 14:14:35, CheckpointCompletedGbFRWIthIPSPDown, 2011-09-03 11:50:35, CheckpointCompletedGbFRGomGnwithIPSPDown, 2011-09-03 21:33:02, CheckpointCompletedGomGnGbFRSTPok, 2011-09-04 18:16:24, CheckpointCompletedBackup, 2011-09-06 19:34:20, CheckpointCompleted

AttachWorkingDNSChange, 2011-09-07 20:32:29, CheckpointCompletedAttachPDPWorkOk, 2011-09-08 22:23:17, CheckpointCompletedAttachPDPOkImsins, 2011-09-09 19:26:58, CheckpointCompletedwithimsicnahges, 2011-09-09 22:13:56, CheckpointCompletedWithIMSILACRAC, 2011-09-10 14:32:56, CheckpointCompletedbeforelicense, 2011-09-12 13:18:53, CheckpointCompletedGbmodify, 2011-09-13 14:18:05, CheckpointCompletedGbFRModifyCostOSPFGom, 2011-09-13 18:47:01, CheckpointCompletedBeforeSS7red, 2011-09-13 18:58:43, CheckpointCompletedAfterSS7redNoStaticRoute, 2011-09-14 11:49:11, CheckpointCompletedBeforeLiceAfterSS7FullOSPF, 2011-09-14 15:56:56, CheckpointCompletedafterlicense, 2011-09-15 11:21:38, CheckpointCompleted

AfterLicenseAllOk, 2011-09-20 18:05:15, CheckpointCompletedEmergencyState, 2011-09-22 11:56:15, CheckpointCompletedGnIpChange, 2011-09-26 17:35:17, CheckpointCompletedAfterNewLic, 2011-09-27 11:44:32, CheckpointCompletedlocalokroamerfailbeforeuch1to0, 2011-09-28 12:43:10, CheckpointCompletedLocalRoamerOksendudt, 2011-09-28 17:08:30, CheckpointCompletedbeforeSNMP, 2011-10-04 12:28:39, CheckpointCompleted (LastBooted)ImsiModified20101040, 2011-10-05 10:32:40, CheckpointCompletedImsiCreated20111005, 2011-10-05 11:44:50, CheckpointCompletedE1T1Configdelete20111005, 2011-10-06 10:01:19, CheckpointCompletedAfterMigrationallOK, 2011-10-13 10:48:46, CheckpointActive(Next,LastActivated,Permanent)

8/2/2019 Notas SGSN

13/19

5. Verify the charging (CDR) files in the SGSN. CDR files should begenerated in the SGSN and move to the EMM/Billing Server on dailyBasis in ready/tmp dir if not then Escalate to Concern team

# cd /charging/chsLog/ready

# ls lrt (si se usa ll no saldrn los resultados de forma cronolgica)

-rw-rw-rw- 1 root root 696964 Oct 20 15:32 chsLog.86-rw-rw-rw- 1 root root 788771 Oct 20 15:47 chsLog.87-rw-rw-rw- 1 root root 753241 Oct 20 16:02 chsLog.88-rw-rw-rw- 1 root root 735469 Oct 20 16:17 chsLog.89-rw-rw-rw- 1 root root 739798 Oct 20 16:32 chsLog.90-rw-rw-rw- 1 root root 739709 Oct 20 16:47 chsLog.91-rw-rw-rw- 1 root root 744184 Oct 20 17:02 chsLog.92

NOTA: Debe de haber un registro por da.

En la carpeta /charging/chsLog/tmp se encuentra el archivo que actualmente se esta

escribiendo.

# cd ../tmp/# ls -lrttotal 4-rw-r--r-- 1 root root 13 Oct 20 17:02 chsLog.index-rw-r--r-- 1 root root 137049 Oct 20 17:02 chsLog.93

6. Check the Mobility logs files ready/tmp logs file in the logs file, ifthere are lots attached failures then need to Escalate to concernteam. Normally 1 or maximum 2 file has to be generate every daybased on subscribers if SGSN generating more than 1 or 2 file thenits not normal situation need to Escalate to Concern team.

/logs/mobility_event_log/readyls-lrt

total 4920-rw-rw-rw- 1 root root 999954 Oct 20 06:22 mobility_event_log.2-rw-rw-rw- 1 root root 999627 Oct 20 13:38 mobility_event_log.3-rw-rw-rw- 1 root root 999784 Oct 20 19:25 mobility_event_log.4-rw-rw-rw- 1 root root 999927 Oct 21 02:42 mobility_event_log.5-rw-rw-rw- 1 root root 999600 Oct 21 09:52 mobility_event_log.1

Leer las ltimas entradas del registro que se esta escribiendo actualmente

cd ../tmp/ls -lrt

total 32-rw-r--r-- 1 root root 12 Oct 21 09:52 mobility_event_log.index-rw-r--r-- 1 root root 238584 Oct 21 10:00 mobility_event_log.#

tail -f mobility_event_log.#

======== MOBILITY EVENT (G): ATTACH REJECT =========

8/2/2019 Notas SGSN

14/19

Time : 2011-10-21 11:16:01Node : e_Erlang__Global_pm1_9_2_1@eqm01s09p2GMM Cause : Network Failure (#17)Details : Timeout when communicating with external nodeAttach : imsi_type, gprs_attachIMSI : 234308318064438

PTMSI : N/ARA New : 73800200105002RA Old : 738_0165534255Cell ID : 251HLR addr : TT=0, NP=7, ES=1, NAI=4, Addr=447953318064438

Syntax tail

tail [options]

The following example shows the last 20 lines of filename:

tail -n 20 filename

This example shows the last 15 bytes of all files starting with foo:

tail -c 15 foo*

This example shows all lines of filename from the second line onwards:

tail -n +2 filename

tail has a special command line option -f (follow) that allows a file to be monitored. Itdisplay the last few lines. As new lines are added to the file by another process, tail

updates the display.

tail -f

Luego se debe revisar el contenido de las carpetas /ready y /tmp,en /tmp se deben revisar las ltimas entradas de este registro.

/logs/session_event_log/cd ready/

lltotal 992drwxrwxrwx 2 root root 4096 Oct 11 12:29 .drwxr-x--- 4 root gsnuser 4096 Aug 30 18:00 ..-rw-rw-rw- 1 root root 999756 Oct 11 12:29 session_event_log.1

cd ../tmp/ll

total 444drwxr-xr-x 2 root root 4096 Oct 11 12:29 .

http://en.wikipedia.org/wiki/Process_(computing)http://en.wikipedia.org/wiki/Process_(computing)

8/2/2019 Notas SGSN

15/19

drwxr-x--- 4 root gsnuser 4096 Aug 30 18:00 ..-rw-r--r-- 1 root root 434259 Oct 21 11:02 session_event_log.2-rw-r--r-- 1 root root 12 Oct 11 12:29 session_event_log.index

tail -f session_event_log.2

Time : 2011-10-21 11:02:46

======== SESSION EVENT (G): MS INITIATED ACTIVATE REQUEST =========Time : 2011-10-11 12:29:40Node : e_Erlang__Global_pm1_9_2_1@eqm01s09p2IMSI : 302720216019489MSISDN : 14168178300SM Cause : Missing or unknown APN (#27)Details : APN Resolving errorAPN Req. : blackberry.netAPN Sub. : blackberry.netAPN Used : blackberry.net.mnc720.mcc302.gprs

MOBILITY EVENT

The mobility management printout is a log file named Mobility Event Log. All attach rejectmessages that occur due to network failure.

The wrap time is 2 hours and this log file is deleted after 5 days.

La administracin de la movilidad (Mobility Management) en la SGSN mantiene la ubicacin(Routing Area (RA)) de la MS (Mobile Station), lo que permite que la MS se mantenga registradaen la red, ya que estas suelen cambiar de posicin. En otras palabras la red debe conocer laubicacin de la MS para mantener la conectividad

During the collection of measurements, the results are stored in a temporary directory. This(ASCII) format log file can be viewed using UNIX commands.

Format

Table 1 Mobility Event Log File for SGSN in ASCII Format

Time: YYYY-MM-DD HH:MM:SS

Node: [Any combination of characters a-z, A-Z, 09, _,-,$, @ and # ] String of characters.

GMM cause: Strings of characters which contain the slogan and cause codeDetails: Strings of characters to describe the breakdown of the failure reasons

Attach: Strings of characters which contain the parameter name

IMSI: [515] INTEGER

PTMSI: [10] INTEGER

RA New: [515] INTEGER

RA Old: [515] INTEGER

Cell ID: [15] INTEGER

http://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0231.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0231.htm#TOP#TOP

8/2/2019 Notas SGSN

16/19

This field only appliesto GSM.

HLR addr: [215] INTEGER

SESSION EVENTS

The session management printout is a log file named Session Event Log. All MS (Mobile Station)-initiated activate Packet Data Protocol (PDP) contexts that are rejected due to missing orunknown Access Point Name (APN), unknown PDP address, network failure, or requested serviceoption not subscribed are stored in this log file. Also all UE-initiated activate default bearercontexts that are rejected due to a missing or unknown APN or network failure are stored in thislog file.

During the collection of measurements, the results are stored in a temporary directory. ThisAmerican Standard Code for Information Interchange (ASCII)-format log file can be viewed usingUNIX commands.

GPRS session management en la SGSN establece y maneja la conexin entre la Mobile Station yel Packet Data Network (PDN) a travs del Gateway (GGSN)

Un inicio de sesin se realiza en la MS, SGSN y GGSN para uno o mas PDP (Packet Data Protocol)

Figure 1 Logical View of a Session

Bearer = portador

PDN.- Packet Data NetworkPDP.- Packet Data Protocol

MS.- Mobile Station

http://edw//alex?ac=image&fn=38_22102-AXB25005_8Uen.E1-LogicalViewOfSession.eps.pdf

8/2/2019 Notas SGSN

17/19

Format

The session_event_log file format for a missing or unknown APN (session management Cause#27) is shown in Table 1.

Table 1 Session Event Log File in ASCII Format for Missing or Unknown APN

Time: YYYY-MM-DD HH:MM:SS

Node: [Any combination of characters a-z, A-Z, 09, _,-,$, @, and # ] in a string

IMSI: [515] INTEGER

MSISDN String of integers

SM Cause: Strings of characters

Missing or Unknown APN (#27)

Details Strings of characters

GGSN Addr. or RNC

Addr.:

Internet Protocol (IP) address in dotted-decimal format:

a.b.c.d

APN Req: One or more labels separated by dots referring to a valid Domain NameSystem (DNS) name or domain

APN Sub: One or more labels separated by dots referring to a valid DNS name ordomain

APN Used: Three labels separated by dots:

mnc.mcc.gprs(1)

NOTA: si se requiere saber ms a fondo de que problema se traba podemos verlo con el siguientecomando:gsh get_imsins [imsi](donde en [imsi] solo se usan los primeros 5 6 nmeros)

e.g.gsh get_imsins -imsi 50501

Parameter Active Data Planned Data------------------------------------------------------------timestamp 20111005114354 _planState _ _rs visitor _dn mnc001.mcc505.gprs _

np e214 _ac true _na international _rd 5 _ad 61408 _m1 Australia Telstra _m2 NULL _m3 NULL _eplp NULL _

http://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0237.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0237.htm#Tab1#Tab1http://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0237.htm#tnote1-1#tnote1-1http://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0237.htm#TOP#TOPhttp://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0237.htm#Tab1#Tab1http://c/Users/esaivaz/AppData/Local/Temp/ALEX_TMP/1004/alex0237.htm#tnote1-1#tnote1-1

8/2/2019 Notas SGSN

18/19

rn NULL _hn NULL _s8 gtp _gcc NULL _wcc NULL _lcc NULL _

smsc UNDEFINED_VALUE _qpml UNDEFINED_VALUE _

7. Check the ISP logs file in the logs file need to check heart beatshould be there for pdp/sau and check if there is any hardwareequipment loss or nodes restart in NCL if yes then escalate toconcern team.

ISP (In Service Performance logs)

/Core/logtail -f isp.log

ISP (Internet Service Providers)

2011-10-19 06:14:20 UTC-0400;sau;;21300,heartbeat;CXS101289_4_R1H07(10A-00-05)2011-10-19 06:14:20 UTC-0400;pdp;;1400,heartbeat;CXS101289_4_R1H07(10A-00-05)2011-10-19 19:14:20 UTC-0400;sau;;23200,heartbeat;CXS101289_4_R1H07(10A-00-05)2011-10-19 19:14:20 UTC-0400;pdp;;2400,heartbeat;CXS101289_4_R1H07(10A-00-05)2011-10-20 08:14:20 UTC-0400;sau;;22300,heartbeat;CXS101289_4_R1H07(10A-00-05)2011-10-20 08:14:20 UTC-0400;pdp;;1700,heartbeat;CXS101289_4_R1H07(10A-00-05)2011-10-20 21:14:20 UTC-0400;sau;;22900,heartbeat;CXS101289_4_R1H07(10A-00-05)2011-10-20 21:14:20 UTC-0400;pdp;;2200,heartbeat;CXS101289_4_R1H07(10A-00-05)2011-10-21 10:14:20 UTC-0400;sau;;22700,heartbeat;CXS101289_4_R1H07(10A-00-05)2011-10-21 10:14:20 UTC-0400;pdp;;2000,heartbeat;CXS101289_4_R1H07(10A-00-05)

8. Verify the SCTP (Stream Control Transmition Protocol) connection.All the available connection should be in active state if not thenescalate to concern team

gsh show_ss7_sys_statallsp

The show_ss7_sys_statallsp command requests the status of all the configured remote signalingprocesses, both remote IP (Internet Protocol) Server Processes (IPSPs(IP Server Process)) andremote SG (Signaling GAteway) Processes (SGPs).

RemoteSpID/RemoteSgpID 40041LocalAsID 4740LocalSpID 39041Status Active

8/2/2019 Notas SGSN

19/19

RemoteSpID/RemoteSgpID 40031LocalAsID 4740LocalSpID 39031Status Active

9. Verify the SS7/HLRs connection all the available connection shouldbe in allowed state if not then Escalate to concern team

gsh list_ss7_sccp_remote_point

The list_ss7_sccp_remote_point command lists SCCP (Signaling Connection Control Part)remote signaling points. The operator can choose to display the SCCP remote signaling points inthe active configuration, the planned configuration, or both.

ps Class Identifiers |------------------------------------------------------A ss7_sccp_remote_point -net CN -dpc 14954A ss7_sccp_remote_point -net CN -dpc 14956A ss7_sccp_remote_point -net CN -dpc 14959A ss7_sccp_remote_point -net RAN -dpc 16383

gsh show_ss7_sccp_remote_point_stat -net CN -dpc 14954 -nid 0

NodeID 0OPC 4739

DPC 14954DPC Status AllowedCongestionLevel 0

gsh show_ss7_sccp_remote_point_stat -net RAN -dpc 16383 -nid 1 (0 2G, 1 - 3G

NodeID 1OPC 4739DPC 16383DPC Status Prohibited