Wednesday, December 10, 2003
Lab Name_______IP Address of Server______Login Info
=========================================================
Maintenance Lab ___ 10.224.13.10 _______ root/zeus
Lab - 1 ___________ 10.224.17.10 _______ root/instal
Lab - 1 ___________ 10.224.72.10 _______ root/punchau
Gerneric login _:_ admin/admin
Workstation IP: *.*.*.11
Site IP: *.*.*.12
Ogre (if any) IP: *.*.*.9
=========================================================
Maintenance Lab ___ 10.224.13.10 _______ root/zeus
Lab - 1 ___________ 10.224.17.10 _______ root/instal
Lab - 1 ___________ 10.224.72.10 _______ root/punchau
Gerneric login _:_ admin/admin
Workstation IP: *.*.*.11
Site IP: *.*.*.12
Ogre (if any) IP: *.*.*.9
Monday, December 08, 2003
How to build
------------
1. Select your devlopment view - useview
2. setcs -cur -reload (Stuart is working on make files and we need to do this every time we change view)
3. export visual=vi
4. ct edcs (edit config spec)
Uncomment the line with ENCRYPT in it.
5. Modify /projects/access7/patch/Makefile.options
Change the PSF_PRODNAME = a7TrblShoot_M402
Save this file to /projects/access7/Makefile.options
6. Build using the following command from /projects/a7trouble/
clearmake -Vkvr -A /projects/access7/Makefile.options trouble_system | tee Make.log.adisingh2 2>&1
------------
1. Select your devlopment view - useview
2. setcs -cur -reload (Stuart is working on make files and we need to do this every time we change view)
3. export visual=vi
4. ct edcs (edit config spec)
Uncomment the line with ENCRYPT in it.
5. Modify /projects/access7/patch/Makefile.options
Change the PSF_PRODNAME = a7TrblShoot_M402
Save this file to /projects/access7/Makefile.options
6. Build using the following command from /projects/a7trouble/
clearmake -Vkvr -A /projects/access7/Makefile.options trouble_system | tee Make.log.adisingh2 2>&1
Thursday, November 27, 2003
Notes on SS7:
=============
There are 2 forms of signalling:
1 - CAS
2 - CCS
CAS - Channel Associated Signalling - wherein Control (synch, bounding frames) signal + voice&data signals are in same channel. Call set up info (handset lift, busy, ring) have same freq. as human voice. But CAS may suffer from interference; its slow to setup & teardown.
CCS - Common Channel Signalling - wherein control + voice&data signals have seperate channels. So voice trunk is established only when a connection is established. Its faster to setup & teardown. E.g. SS7, Integrated Services Digital Network(ISDN) - Primary Rate Interface (PRI).
PSTN - Public Switched Telephone Network.
ISDN-PRI: A CCS type - Has B & D channels. Bearer or B channels transport voice data. Data channles for control data. In 24 channel ISD, we have 23 B and 1 D channel. Each channel speed is 56 or 64 kbps. Thus net bandwidth is 1.526 Mbps. Signalling is possible even after call has been setup.
SS7: While similar to ISDN-PRI, Signaling System #7 (SS7) uses different messaging for call setup and teardown. SS7 lets any SS7-enabled node to talk to any other, regardless of whether they have direct trunk connections between them.
The preferred mode of signaling for SS7 networks is Quasi-Associated, whereas ISDN-PRI uses Associated Signaling mode.
SIGNALLING MODES:
1 - Associated Signaling—Uses one dedicated path between switches as the signaling link. Examples: ISDN-PRI and E1-CAS.
2 - Non-Associated Signaling—Uses separate logical paths and multiple nodes.
3 - Quasi-Associated Signaling—Uses a minimal number of nodes (preferred for SS7, causes less delay).
SS7
---
SS6, the predeccessor of SS7, was based on a packet-switched, proprietary data network.
SS7 provides a global standard for call setup, routing, and control. SS7 is fast ~ 56-64Kbps.
The first use of SS7 was not for call setup and teardown, but rather for accessing databases. 800 numbers provided a problem for switches in that they could no longer route based on area code. A second "real number" for each 800 number needed to be placed in a centralized database which multiple central offices could access.
The call flow of an 800 number is as follows:
o 800 number dialed, CO switch receives digits and routes the call to a remote database via data link.
o "Real number" is determined from the database via SS7 message packet.
o Database responds with response message packet.
o Database provides routing number for call and billing information.
o CO switch is then able to route the call in the conventional manner
Call setup/teardown is done using the ISDN User Part (ISUP) protocol. Database lookup uses the Transactional Capabilities Application Part (TCAP) protocol. Its possible to access other companies DB using SS7 protocol.
ss7 standards:
1) ITU - TS Standard ...international
2) ANSI Std. - US, Canada
LNP - local number portability
AIN - Advanced Intelligent Network
=============
There are 2 forms of signalling:
1 - CAS
2 - CCS
CAS - Channel Associated Signalling - wherein Control (synch, bounding frames) signal + voice&data signals are in same channel. Call set up info (handset lift, busy, ring) have same freq. as human voice. But CAS may suffer from interference; its slow to setup & teardown.
CCS - Common Channel Signalling - wherein control + voice&data signals have seperate channels. So voice trunk is established only when a connection is established. Its faster to setup & teardown. E.g. SS7, Integrated Services Digital Network(ISDN) - Primary Rate Interface (PRI).
PSTN - Public Switched Telephone Network.
ISDN-PRI: A CCS type - Has B & D channels. Bearer or B channels transport voice data. Data channles for control data. In 24 channel ISD, we have 23 B and 1 D channel. Each channel speed is 56 or 64 kbps. Thus net bandwidth is 1.526 Mbps. Signalling is possible even after call has been setup.
SS7: While similar to ISDN-PRI, Signaling System #7 (SS7) uses different messaging for call setup and teardown. SS7 lets any SS7-enabled node to talk to any other, regardless of whether they have direct trunk connections between them.
The preferred mode of signaling for SS7 networks is Quasi-Associated, whereas ISDN-PRI uses Associated Signaling mode.
SIGNALLING MODES:
1 - Associated Signaling—Uses one dedicated path between switches as the signaling link. Examples: ISDN-PRI and E1-CAS.
2 - Non-Associated Signaling—Uses separate logical paths and multiple nodes.
3 - Quasi-Associated Signaling—Uses a minimal number of nodes (preferred for SS7, causes less delay).
SS7
---
SS6, the predeccessor of SS7, was based on a packet-switched, proprietary data network.
SS7 provides a global standard for call setup, routing, and control. SS7 is fast ~ 56-64Kbps.
The first use of SS7 was not for call setup and teardown, but rather for accessing databases. 800 numbers provided a problem for switches in that they could no longer route based on area code. A second "real number" for each 800 number needed to be placed in a centralized database which multiple central offices could access.
The call flow of an 800 number is as follows:
o 800 number dialed, CO switch receives digits and routes the call to a remote database via data link.
o "Real number" is determined from the database via SS7 message packet.
o Database responds with response message packet.
o Database provides routing number for call and billing information.
o CO switch is then able to route the call in the conventional manner
Call setup/teardown is done using the ISDN User Part (ISUP) protocol. Database lookup uses the Transactional Capabilities Application Part (TCAP) protocol. Its possible to access other companies DB using SS7 protocol.
ss7 standards:
1) ITU - TS Standard ...international
2) ANSI Std. - US, Canada
LNP - local number portability
AIN - Advanced Intelligent Network
Nadime - 26 Nov 2003 - 1400 hours
Where we are in Agilent?
Test & Measurement ==> CSG ==> Operations Support Systems(OSS BU) Business Unit
Under OSS BU we have TSD, CSSD (Tier 1,2 which Interact between customers & us guys @ Tier3) and the OSSD (OSS Service Delivery).
Apart from this Agilent has 2 new divisions called Mac 2 (VoIP) and Mac 3 (3G, UMTS).
Agilent uses Software Packager (HP product to package s/w) for bundling acceSS7, Maintanence Pack or MP (Patches, Hot Fixes etc). The MP308 was released in Aug, 03. The MPs are released every quarter.
The previous acceSS7 version is B.7.10 and he current one is C.7.30. B stands for HP-10 UX while C stands for HP-11 UX.
Agilent uses Labs like Lab-16 to test MPs.
Nadime also discussed about DDTS which is very similar to other DTS systems like bugzilla.
Misc.:
LCR - Low Customer Release - something like a B-release.
SR - Support Release
EVO - Next Major Release
CNS - SS7 over IP
Where we are in Agilent?
Test & Measurement ==> CSG ==> Operations Support Systems(OSS BU) Business Unit
Under OSS BU we have TSD, CSSD (Tier 1,2 which Interact between customers & us guys @ Tier3) and the OSSD (OSS Service Delivery).
Apart from this Agilent has 2 new divisions called Mac 2 (VoIP) and Mac 3 (3G, UMTS).
Agilent uses Software Packager (HP product to package s/w) for bundling acceSS7, Maintanence Pack or MP (Patches, Hot Fixes etc). The MP308 was released in Aug, 03. The MPs are released every quarter.
The previous acceSS7 version is B.7.10 and he current one is C.7.30. B stands for HP-10 UX while C stands for HP-11 UX.
Agilent uses Labs like Lab-16 to test MPs.
Nadime also discussed about DDTS which is very similar to other DTS systems like bugzilla.
Misc.:
LCR - Low Customer Release - something like a B-release.
SR - Support Release
EVO - Next Major Release
CNS - SS7 over IP
Wednesday, November 26, 2003
How to set up the cleartool for a bug fix.
==========================================
I am supposed to solve bug TSDrd72967. At TSD, you need to create a seperate view for it and solve the bug in that vob before integrating it back.
Be advised to create an alias "ct" for cleartool as you will be using it excessively.
To see the present working view use ct pwv like this:
hpqs0725:adisingh$ ct pwv
Working directory view: ** NONE **
Set view: ** NONE **
So we first need to create a view, like this:
newview -p PEP6_fixes -r C.03.60 -ctr TSDrd72967
PEP6_fixes refers to the project. Its a Product Enhancement Package. Something like a enhancement request.
C.03.60 is the release number. -ctr might mean comment or something.
hpqs0725:adisingh$ newview -p PEP6_fixes -r C.03.60 -ctr TSDrd72967
newview [NOTICE]: TSDrd72967 is not in the ASSIGNED state (PENDING).
mkview [INFO]: Created view "adisingh_PEP6_fixes_C.03.60_TSDrd72967" on hpqs0711
mkview [INFO]: Creating tag in NT ClearCase region tsd.nt
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/access7
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/a7trouble
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/NES
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/AppSupp
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/a7follower
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/a7lsm
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/ossgw
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/OSL
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/a7tm
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/Stats
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/XTools
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/p7linkDiscovery
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/p7ctf
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/p7ctfP7ver
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/ConfigMgr
setcs [INFO]: Loading configuration specification
newview [INFO]: Created view adisingh_PEP6_fixes_C.03.60_TSDrd72967
Now select this view by saying useview:
hpqs0725:adisingh$ useview
Select a view
0) Exit
1) adisingh_PEP6_fixes_C.03.60_TSDrd72967
2) draftdocs
3) reldocs
View: 1
setview [INFO]: Setting working directory to /projects/access7.
setview [NOTICE]: TSDrd72967 is not in the ASSIGNED state (PENDING).
setview [INFO]: Defect headline: T25 coredump when stopping CT session
setview [INFO]: Setting ClearCase view context adisingh_PEP6_fixes_C.03.60_TSDrd72967.
NOTE: Your directory get changed somehow.
hpqs0725:adisingh$ pwd
/projects/access7
Our main work is carried out in
hpqs0725:adisingh$ cd ../a7trouble/access7/ts/
hpqs0725:adisingh$ ls
ctDebug inc t01 t24 t26 t28 t60 tac tfa tga
dds t00 t10 t25 t27 t29 tab tca tfb tgb
hpqs0725:adisingh$ cd ts/
hpqs0725:adisingh$ cd t25
hpqs0725:adisingh$ l
Makefile, t25.doc, t2500.c, t2501.c, t2502.c, t2503.c, t2504.c, t2505.c, t2506.c, t2508.c, t2509.c, t2510.c, t2511.c, t2513.c, t2514.c,
t2515.c, t2516.c, t2517.c, t2518.c, t2519.c, t2520.c, t2521.c, t2522.c, t2523.c, t2524.c, t2525.c, t2526.c, t2527.c, t2528.c, t2529.c,
t252a.c, t252b.c, t252c.c, t252d.c, t2530.c, t2531.c, t2532.c, t2533.c, t2534.c, t2535.c, t2536.c, t2537.c, t2539.c, t253a.c, t253b.c,
t2540.c, t2541.c, t2542.c, t2543.c, t2544.c, t2545.c, t2546.c, t2547.c, t2548.c, t2549.c, t2550.c, t2555.c, t2556.c, t2557.c, t2560.c,
t2561.c, t2564.c, t2570.c, t2571.c, t2575.c, t2576.c, t2577.c, t2579.c, t2580.c, t2581.c, t2582.c, t2583.c, t2584.c, t2585.c, t2586.c,
t2587.c, t258a.c, t258b.c, t2590.c, t2592.c, t2596.c, t2597.c, t2598.c, t2599.c, test
To see the visiual details about intergration and branching use xlsvtree like this:
hpqs0725:adisingh$ xlsvtree t2515.c
*A GUI App shows up*
There is a script made by Rick which builds the access7 codebase.
Its ~rg1/bin/buildA7C7.sh
Others:
To see all checked out files
hpqs0725:adisingh$ ct lsco
17-Sep.07:31 smd checkout version "Makefile" from /main/nasa_c.08.00/tsdrd70143/0 (unreserved)
"Add UTDB flag"
19-Nov.10:55 earnshaw checkout version "t2500.c" from /main/nasa_c.08.00/tsdrd72662/0 (reserved)
17-Sep.14:46 smd checkout version "t252a.c" from /main/nasa_c.08.00/tsdrd70143/1 (reserved)
"Pass down UniqueIDs for logical links and let Pgb28 expand them"
To see all checked out files by me
hpqs0725:adisingh$ ct lsco -me
To see history of a file
hpqs0725:adisingh$ cleartool lshist t2533.c
17-Nov.10:05 kingram create version "t2533.c@@/main/nasa_c.08.10/1"
"merge from NASA_C.08.00_I9C"
04-Nov.16:06 kingram create version "t2533.c@@/main/nasa_c.08.10/0"
04-Nov.16:06 kingram create branch "t2533.c@@/main/nasa_c.08.10"
"merge from NASA_C.08.00_I9C"
04-Nov.14:32 kingram destroy sub-branch "nasa_c.08.10" of branch "t2533.c@@/main"
"Destroyed branch "/main/nasa_c.08.10"."
15-Apr.11:04 buildmgr create version "t2533.c@@/main/2" (MAIN_PEP6_T7)
"Merge to main for PEP6_T7"
07-Mar.15:00 rmasson create version "t2533.c@@/main/nasa_c.08.00/3" (C0400_TM_I11E, NASA_C.08.00_I9E, C0400_TM_I11D, NASA_C.08.00_I9D, C0400_SURV_T3B, ...)
To see history of all files
hpqs0725:adisingh$ cleartool lshist
==========================================
I am supposed to solve bug TSDrd72967. At TSD, you need to create a seperate view for it and solve the bug in that vob before integrating it back.
Be advised to create an alias "ct" for cleartool as you will be using it excessively.
To see the present working view use ct pwv like this:
hpqs0725:adisingh$ ct pwv
Working directory view: ** NONE **
Set view: ** NONE **
So we first need to create a view, like this:
newview -p PEP6_fixes -r C.03.60 -ctr TSDrd72967
PEP6_fixes refers to the project. Its a Product Enhancement Package. Something like a enhancement request.
C.03.60 is the release number. -ctr might mean comment or something.
hpqs0725:adisingh$ newview -p PEP6_fixes -r C.03.60 -ctr TSDrd72967
newview [NOTICE]: TSDrd72967 is not in the ASSIGNED state (PENDING).
mkview [INFO]: Created view "adisingh_PEP6_fixes_C.03.60_TSDrd72967" on hpqs0711
mkview [INFO]: Creating tag in NT ClearCase region tsd.nt
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/access7
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/a7trouble
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/NES
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/AppSupp
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/a7follower
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/a7lsm
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/ossgw
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/OSL
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/a7tm
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/Stats
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/XTools
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/p7linkDiscovery
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/p7ctf
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/p7ctfP7ver
mkbranch [INFO]: Created brtype:tsdrd72967 in /projects/ConfigMgr
setcs [INFO]: Loading configuration specification
newview [INFO]: Created view adisingh_PEP6_fixes_C.03.60_TSDrd72967
Now select this view by saying useview:
hpqs0725:adisingh$ useview
Select a view
0) Exit
1) adisingh_PEP6_fixes_C.03.60_TSDrd72967
2) draftdocs
3) reldocs
View: 1
setview [INFO]: Setting working directory to /projects/access7.
setview [NOTICE]: TSDrd72967 is not in the ASSIGNED state (PENDING).
setview [INFO]: Defect headline: T25 coredump when stopping CT session
setview [INFO]: Setting ClearCase view context adisingh_PEP6_fixes_C.03.60_TSDrd72967.
NOTE: Your directory get changed somehow.
hpqs0725:adisingh$ pwd
/projects/access7
Our main work is carried out in
hpqs0725:adisingh$ cd ../a7trouble/access7/ts/
hpqs0725:adisingh$ ls
ctDebug inc t01 t24 t26 t28 t60 tac tfa tga
dds t00 t10 t25 t27 t29 tab tca tfb tgb
hpqs0725:adisingh$ cd ts/
hpqs0725:adisingh$ cd t25
hpqs0725:adisingh$ l
Makefile, t25.doc, t2500.c, t2501.c, t2502.c, t2503.c, t2504.c, t2505.c, t2506.c, t2508.c, t2509.c, t2510.c, t2511.c, t2513.c, t2514.c,
t2515.c, t2516.c, t2517.c, t2518.c, t2519.c, t2520.c, t2521.c, t2522.c, t2523.c, t2524.c, t2525.c, t2526.c, t2527.c, t2528.c, t2529.c,
t252a.c, t252b.c, t252c.c, t252d.c, t2530.c, t2531.c, t2532.c, t2533.c, t2534.c, t2535.c, t2536.c, t2537.c, t2539.c, t253a.c, t253b.c,
t2540.c, t2541.c, t2542.c, t2543.c, t2544.c, t2545.c, t2546.c, t2547.c, t2548.c, t2549.c, t2550.c, t2555.c, t2556.c, t2557.c, t2560.c,
t2561.c, t2564.c, t2570.c, t2571.c, t2575.c, t2576.c, t2577.c, t2579.c, t2580.c, t2581.c, t2582.c, t2583.c, t2584.c, t2585.c, t2586.c,
t2587.c, t258a.c, t258b.c, t2590.c, t2592.c, t2596.c, t2597.c, t2598.c, t2599.c, test
To see the visiual details about intergration and branching use xlsvtree like this:
hpqs0725:adisingh$ xlsvtree t2515.c
*A GUI App shows up*
There is a script made by Rick which builds the access7 codebase.
Its ~rg1/bin/buildA7C7.sh
Others:
To see all checked out files
hpqs0725:adisingh$ ct lsco
17-Sep.07:31 smd checkout version "Makefile" from /main/nasa_c.08.00/tsdrd70143/0 (unreserved)
"Add UTDB flag"
19-Nov.10:55 earnshaw checkout version "t2500.c" from /main/nasa_c.08.00/tsdrd72662/0 (reserved)
17-Sep.14:46 smd checkout version "t252a.c" from /main/nasa_c.08.00/tsdrd70143/1 (reserved)
"Pass down UniqueIDs for logical links and let Pgb28 expand them"
To see all checked out files by me
hpqs0725:adisingh$ ct lsco -me
To see history of a file
hpqs0725:adisingh$ cleartool lshist t2533.c
17-Nov.10:05 kingram create version "t2533.c@@/main/nasa_c.08.10/1"
"merge from NASA_C.08.00_I9C"
04-Nov.16:06 kingram create version "t2533.c@@/main/nasa_c.08.10/0"
04-Nov.16:06 kingram create branch "t2533.c@@/main/nasa_c.08.10"
"merge from NASA_C.08.00_I9C"
04-Nov.14:32 kingram destroy sub-branch "nasa_c.08.10" of branch "t2533.c@@/main"
"Destroyed branch "/main/nasa_c.08.10"."
15-Apr.11:04 buildmgr create version "t2533.c@@/main/2" (MAIN_PEP6_T7)
"Merge to main for PEP6_T7"
07-Mar.15:00 rmasson create version "t2533.c@@/main/nasa_c.08.00/3" (C0400_TM_I11E, NASA_C.08.00_I9E, C0400_TM_I11D, NASA_C.08.00_I9D, C0400_SURV_T3B, ...)
To see history of all files
hpqs0725:adisingh$ cleartool lshist
