Page 1 of 20

Preventive Maintenance Procedure for

Remote Access Servers for NIB “C” Type Nodes Supplied By

M/s ITI Limited to Bharat Sanchar Nigam Limited

(Ref: Tender No. BSNL/DNW/Tech-4601/2003) (PO NoBSNL/DNW/Tech-4601/2003 dated 08.10.2003)

Page 2 of 20

Node Address

Name & Designation of BSNL Node-in-Charge

Name of M/s ITI Engineer

Date of Preventive Maintenance

Page 3 of 20

EQUIPMENT DETAILS (This to be checked from TCM- Total Control Manager )

The above Virtual Front Panel Display the type of card present and the status of the card in the Total control 1000 chassis. 1. Slot 1-12 - Modem card (90 modem each card=3E1) 2. Slot 13-16 - Access router cards 3. Slot 17 - Is NMC card (network management card) 4. Slot 18-19 - Is Power supply unit Note: Each Carrier LED on the modem card represent one E1.

Page 4 of 20

# Below snapshot will show all the card with serial number and software version installed.

Page 5 of 20

DETAILS OF EQUIPMENTS AVAILABLE AT THE SITE (Against the P.O. of RAS for NIB “C” Type of Nodes)

S No Brief name Quantity

1 Chassis

2 DSP Card set (90 port)

3 Access router card

4 NIC with 10/100 port

5 V.35 cable

6 NMC Card

7 Switch/Hub

Page 6 of 20

Preventive Maintenance Procedure for ITI Supplied 3COM RAS A. Physical Inspection before starting of the Preventive Maintenance

1. Check the Status of the LEDs on ARC cards (details of LED and expected results is available in Annexure )

2. Check the Status of the LEDs on DSP cards (details of LED and expected results is available in Annexure )

3. Check for the Status of the LEDs on NMC cards (details of LED and expected results is available in Annexure )

A.1 Observations/Output from RAS for ARC and DSP cards S.No. Observation Test Result Remark

( if any) 1. Use command

‘MONITOR RADIUS’

(i) Press ‘E’

(ii) Press ‘D’

Select a letter for one of the following options: A) Monitor all RADIUS packets B) Monitor all RADIUS authentication packets C) Monitor all RADIUS accounting packets D) Monitor a specific user E) Monitor next session F) Monitor all packets to a specific server G) Monitor resource management packets X) Exit the monitor Check for the authentication status of the next session It gives details of the Access-Request and Access—Accept or Access-Reject vis-à-vis configured Radius. Similarly, one specific user access-request, access-accept/reject ( e.g. nib_test) may be seen.

Page 7 of 20

2. Use command ‘MONITOR PPP’ (i) Press ‘U’ (ii) Press ‘N’

Select a letter for one of the following options: C) Monitor PPP Call Events. I) Monitor a specific interface. N) Monitor the next session that starts up. U) Monitor a specific user. T) Monitor a specific calling number. X) Exit the monitor. Please Enter Your Choice : To see the authentication details for the specific users. ( e.g. One can see the session from one specific user like ‘nib_test’ then enter this in the user_name field and connect with ‘nib_test’ and see the result Check for the Next session from any user that starts up. that starts up

3. Show all active interface

This command shows the setting configuration for all active interfaces.

4. Show all interfaces This commands display all configured IP networks

5. list ip pools To see the details of the configured IP Pools on the ARC cards The ‘state’ should be ‘public’.’

Page 8 of 20

6. list interfaces

This command line on the ARC shows Operation status and Admin Status of Modems on ARC Operation status indicates the ARC has the communication with the modem cards. Administrative Status indicates the user-defined status of the interface. In order to calls, the status of the both should be UP.

(i) If there is Operation Status is down for any interface then there is a packet bus problem. Check to see if the card is there in the slot and that its RUN/FAIL light is green.

(ii) If the Admin Status is down for any interface then the modem is not enabled.

7. Sh version Displays the ARC software version

8. Sh cpu utilization This command displays an estimate of the router card’s CPU usage over various intervals.

9. sh system It shows the Software version and other details like

(i) System Descriptor (ii) Object ID (iii) System Up time (iv) System name (v) System location (vi) System Version etc.

10. show board crashdump

It is a diagnostic tool for displaying information about a previous system crash stored in EEPROM This is useful for debugging purposes only

11. Show statistics This set of commands display statistical call and modem information. Call_disconnect_eason Call_duration Call_statistics Call_per_hour Modem_utilization

Page 9 of 20

12 sh board Setting It shows the Hardware information of the ARC Card

13 sh memory It shows the ARC memory status.

14 list dns servers This command displays the information of the DNS servers already configured.

15 Show Statistics call_statistics

This commands gives the summary detail of Summary of Successful calls and Unsuccessful calls

Following Cards with Serial Nos. tested and found OK. The output of various commands attached */seen.

1. 2. 3. 4. 5.

• In view of network security the output of various commands shall not be handed over to M/s ITI engineer, however the output must be checked at the node itself by the M/s ITI engineer for any problem.

Page 10 of 20

B. Observations/Output from RAS for ARC and DSP cards after completion of Preventive Maintenance

1. Check for the Authentication and browsing for all the Services Configured on the Equipment ( e.g. Netone ).

2. Ping for the any site like ‘www.yahoo.com’ 3. Use command traceroute ‘Radius Server’ (Here Radius IP will be used for the Radius server

marked for the location.

PREVENTIVE MAINTANENCE REPORT ( see the example below)

Remarks ( if any)

1 Address of Location NMC, DNW, New Delhi

2 No. of Chassis at the node 2

E1 configured for Dial up ( Give detail for each chassis): ( e.g. Chassis 1 : E1 R2-- 6 No.) Chassis 2: E1 R2-- 10 No.) 9

3 No of configured E1-PRI : ( Give detail for each chassis): 4

4 4

No of DSP Cards Software Version : 2.1.9

5 10 Provide IP detail

6

No of Hiper ARC cards & software version 5.0.9

7 5 Provide IP detail

No of NMC cards & software version 6.2.17

8 Avg Chassis Temperature 26

9 Working Condition of Chassis (Remarks) All chassis are found to be working fine / Other Remarks

Remarks, if any ( for overall)

Page 11 of 20

BSNL Node –in-Charge M/s ITI Ltd Engineer

Name

Designation

Signature

Date

Page 12 of 20

ANNEXURE LED Status Test for Modem card ( DSP Card):

Copyright © 2003, UTStarcom Corporation

�����������

2-16

Carrier LEDAlarm LED

Loopback LED

Run/Fail LED

(Modem) Fault LED

(Modem) Utilization % LEDs

100908070605040302010

HiPerDSP

RN/FL

CAR

ALM

LPBK

100%

0%

FAULT

+

+

UTIIZATION

Page 13 of 20

Copyright © 2003, UTStarcom Corporation

����� ���������

2-10

DSPMultispan

NACNIC

+

1 2

43

RN/FL

CAR

ALMLPBK/DALM

CAR

ALMLPBK/DALM

100%

0%

FAULT

+

+

UTIIZATION

SPAN

Run/Fail NIC and NAC LEDs

(Modem) Fault LED

Carrier AlarmLoopback / D-channel Alarm

Spans 1 and 2 LEDs

Latch top and bottomSecuring screw top and bottom

(Modem) Utilization % LEDs

100%

50%

00%

Spans 3 and 4 LEDsCarrier

AlarmLoopback / D-channel Alarm

Page 14 of 20

Modem Card ( DSP Card) - LED

DSP Multispan LED Status and Trouble Shooting

DSPMultispan

NACNIC

+

1 2

43

RN/FL

CAR

ALMLPBK/DALM

CAR

ALMLPBK/DALM

100%

0%

FAULT

+

+

UTIIZATION

SPAN

Run/Fail NIC and NAC LEDs

(Modem) Fault LED

(Modem) Utilization % LEDs

100%

50%

00%

Spans 3 and 4 LEDsCarrier

AlarmLoopback / D-channel Alarm

1.RN/FLGreen> Card has completed the Power On SelfTest (POST)Flashing green> Diagnostics runningRed> Card failedFlashing orange> Flash programming

2.CAR Off > Card has received no signal or poor signalGreen > Card has received good carrierRed > Card has received bad carrierYellow> Card has received remote alarm

3. ALM off >No alarm or remote frame alarm (RFA)red >Alarm present

4.LPBK Off > Span is , or E1/R2, with no D-channel GreenGreen> D-channel is up (PRI mode) Red > D-channel is down (PRI mode)Yellow> Loopback test in progress (all modes)

5.FAULTGreen> All modems are functioningYellow> There is a problem in one or moremodemsRed > There is a critical problem in one or more modems

6.UTILIZATIONOff > Modems are not in useGreen> Modems in use.

LEDs indicate the percentage ofmodems in use.

(a) DSP Multispan NAC LED description LED Color Description RN/FL Green The card has completed the Power on Self Test (POST) ______________________________________________________________ Flashing green Diagnostic running or download complete

Red Card Failed

Flashing yellow Flash Programming

Page 15 of 20

CAR Off The card has received no loss or received poor signal. ____________________________________________________________________________ green Card has received good carrier.

Red Card has received bad carrier.

Flashing yellow Card has received remote alarm.

ALM Off NO Alarm or Remote Fail Alarm. ____________________________________________________________________________ RED Alarm Present

Page 16 of 20

ARC Card LED Details

(a) ARC RUN/ FAIL LED during Normal Operation LED Description Off Power Off Green Power ON Red Critical Failure

Copyright © 2003, UTStarcom Corporation

��������������

HiPerAccessRouterCard

RN/FL

LAN TX

LAN RX

WAN TX

WANRX

STAT 1

STAT 2

STAT 3

Run/Fail

LAN TransmitLAN Receive

Not usedNot used

Not usedNot usedNot used

2-31

RedRed (flashing)GreenAmber (flashing)Off

Interface failureCollision (1 flash per error)Transmitting packetsMany collisions, network busyIdle

LAN TX (transmit) LED

RedRed (flashing)GreenOff

Interface failureCollision errorReceiving packetsIdle

LAN RX (receive) LED

Same LED indications ARC and HiPer ARC

Page 17 of 20

(b) ARC RUN/ FAIL LED during Start UP and S/W downloads LED Description Red During POST Test Amber (flashing slowly) Checking for Software downloads. Green (flashing Rapidly) Loading an application into RAM Green Power cycle is finished and card is operational

(c) ARC LAN TX LED Description LED Description Red Interface Failure Red(flashing) Collision (One Flash per Error) Amber (flashing) Multiple Collision, Network busy OFF Idle

(d) ARC LAN RX LED Description LED Description Red Interface Failure Red (flashing) Collision Error Green Receiving Packets OFF Idle

Page 18 of 20

NMC Card LED Details

(a) NMC RUN/ FAIL LED Diagnostics LED Color Condition Description Solid Green Normal The NAC is functioning properly Flashing Red & Green Non-Critical Failure A non-critical is an error that occurs when the NMC can’t communicate with another NMC. To find out which NAC the NMC is not able to communicate with check for RN/FL of the other NAC

Copyright © 2003, UTStarcom Corporation

� ������������ �

2-40 to 2-43

Run/Fail

Hub StatusLAN TransmitLAN Receive

4-characterLED display

RN/FL

HUBSTATUSLANTXLANRXWANTXWANRX

NMC

HUBNUMBER/STATUS

RAS1

WAN TransmitWAN Receive

GreenFlash greenRedFlash red/green

NormalTesting or SDL in progressCritical failureNMC NIC failure

RN/FL LED

GreenRedFlash red

NormalCritical failureManagement bus failure

HUB Status LED

OffGreen

No traffic in/out NIC LAN portTraffic in/out NIC LAN port

LAN TX or RX

OffGreen

No traffic in/out NIC W AN portTraffic in/out NIC W AN port

W AN TX or RX

Customer configurableHUB Number/Status

Same LED indications NMC and HiPer NMC

Page 19 of 20

Solid Red Critical Failure A critical failure is one that will keep the NAC from executing its functions Remove the card and reinstall it.

(b) NMC LAN LED Diagnostics LAN TX LAN RX Condition Description Flashing Green Flashing Green NAC is transmitting The LAN Status is operational and receiving the data OFF Flashing Green Improper network NMC is on the n/w but not configuration configured properly. OFF OFF No network This is normal if there is no traffic activity on the network. If it is suspected that there is LAN connectivity problem , issue the PING command to NMC from the remote site.

(c) NMC WAN LED Diagnostics WAN TX WAN RX Condition Description Flashing Green Flashing Green NAC is transmitting The WAN Status is operational and receiving the data OFF Flashing Green Improper network NMC is on the network but is not configuration configured properly. Verify that the NMC local WANIP IP protocol settings are correct. PING command to NMC from the remote site. OFF OFF No network This is normal if there is no traffic activity on the network. If it is suspected that there is WAN connectivity problem , issue the PING command to NMC from the

Page 20 of 20

remote site. If the NMC is attached to the network then you will receive the response.

(d) NMC HUB ST LED during Normal Operation LED Color Condition Description Solid Green Chassis Normal The chassis is functioning normaly Flashing Red & Green Non-Critical Failure A non-critical is an error that occurs when the NMC can’t communicate with another NMC. To find out which NAC the NMC is not able to communicate with check for RN/FL of the other NAC Solid Red Chassis Critical Failure This is any error NMC identifies potentially

harmful. (i) High Chassis temperature. (ii) Fan Tray Failure (iii) Power Supply failure (iv) improper NIC-NAC match-up

Flashing Red Management Bus Failure The NMC can’t communicate with card in the chassis