AP Hardware Overview

5/1/2012

FMM Frames

800 Server

400 Server

410 Server

Flexent Mobility Manager Elements

(A Server)

(B Server)

System Control Panel

Example of A and B-Server System Control Panels

800S B Server

400S A Server

System Status Panel LEDs 800 Server

System Status Panel LEDs 400 Server

CP1500
The model CP1500 CPU card is used as a host CPU. Model CP1500 can be installed in either the 400S server or 800S server. A specific slot is reserved for the CPU card in both the 400S server (slot 3) and the 800S server (slot 1), indicated by a red card cage slot.

Model CP1500 provides the following interfaces:

2 10/100 Mbps Ethernet 2 serial (RS-232)

The two Ethernet ports (hme0 and hme1) are used to connect to the FMM-APCC dual-rail LAN.

CPU 1500 Card

Front Card

Cabling of CPU rear transition card (800S server)

CPU Front Card

CPU Rear Card

CP2140
The model CP2140 CPU card is also used as a host CPU. Model CP2140 is an upgrade to model CP1500 and can be installed in any of the following server types:
410S server 810S server 400S server (field upgrade of host CPU)

A specific slot is reserved for the CPU card in both the 4x0S servers (slot 3) and the 800S server (slot 1), indicated by a red card cage slot. When installed in a 410S server or 810S server, the CPU card has one PMC site, which is used as the connection for the PMC interface module (PIM) on the CPU rear transition card. The PMC functionality is not available when the CPU card (model CP2140) is installed in a 400S server or 800S server. Model CP2140 provides the following interfaces:
2 10/100 Mbps Ethernet 2 serial (RS-232) 1 SCSI The two Ethernet ports (eri0 and eri1) are used to connect to the FMM-APCC dual-rail LAN.

2140 CPU

CP2160
The CPU card (model CP2160) is used as a satellite CPU, which unlike the host CPU, does not require a battery to support the Real Time Clock function. The satellite CPU provides additional CPU processing power within an FMM-AP frame and reduces the amount of floor space needed to deliver that processing power. Satellites are used for memory-intensive applications. They are not used for distributed multiprocessing or for disk-intensive applications. Satellites mount the Solaris operating system via NFS from the host CPU within the same drawer.
Model CP2160 can be installed in either a 410S server, in slots 4 and 5, or in an 810S server, in slots 2 - 7. It has two PMC sites, which are used as the connection for the PIMs on the CPU rear transition card.
Model CP2160 provides the following interfaces:
2 10/100 Mbps Ethernet 1 serial (RS-232) 1 USB

The two Ethernet ports (eri0 and eri1) are used to connect to the FMMAPCC dual-rail LAN.

Model CP2160 CPU Card with ethernet and T1/E1 PMC Cards

Hard Disk Drives

The hard disk drives in both the 400S server and 800S server are located in a specific slot behind the drive bay cover on the system. The hard disk drive used in the 800S server is the same as that used in the 400S server, with the 800S server having two drives where the 400S server has one. Each hard disk drive has its own latching mechanism to ensure a positive lock with the chassis. The hard disk drives used in 400S or 800S servers are 36 GB drives. The drives used in 410S and 810S servers are 73 GB drives. The label on the latching mechanism of the drive handle includes the capacity of the drive (36 GB or 73 GB) to differentiate 400S and 800S servers from 410S and 810S servers. Important! The hard disk drives used in 410S and 810S servers are not the same as the hard disk drives used in 400S or 800S servers. Pay attention to the labels on the latching mechanism of the handles of the drives.

Alarm Card

410 Server 800 Server 400 Server

Alarm Cards
The alarm card provide significant reliability, availability, and serviceability (RAS) functions. The alarm card has its own CPU, a Motorola MPC850 processor, plus its own real-time operating system and application software.

Alarm Cards
The alarm card and its accompanying software perform the following functions on the FMM-AP:
enables you to power on and off the FMM-AP from a remote console notifies an administrator in the event of a component failure gives a hard or soft reset of the CPU board interacts with the network management software on the server to indicate changes in system state

The alarm card has the following remote interfaces: 2 RS-232 serial interfaces 1 10 Mbps Ethernet port (Ethernet port 1) 1 10/100 Mbps Ethernet port (Ethernet port 2, R2 alarm card only) 1 DB-15 alarm port

Alarm Card for 800 Server

The alarm card for the 800S server is different from the alarm card used in the 4x0S servers, so the alarm cards are not interchangeable between the two types of servers. In the 800S server, the alarm card is a singlewide 6U card (a U is a unit of measure equal to 1.75 inches or 44.45 mm); in the 4x0S servers, the alarm card is a double-wide 3U card.

Alarm Card for 4xx Server

The alarm card for the 400S server (R1) is different than the alarm card for the 410S server (R2), so R1 and R2 alarm cards are not interchangeable between 400S and 410S drawers. The easiest way to distinguish R1 and R2 alarm cards is by the number of Ethernet ports: R1 alarm cards have only one Ethernet port; R2 alarm cards have two Ethernet ports. The alarm card for the 400S server (R1) has no rear transition card (all connections are made to the alarm card itself), whereas the alarm card for the 410S server (R2) does have a rear transition card.

R2 Alarm Card
In R2 servers, the R2 alarm card takes over the tasks of alarm, maintenance state, and environmental monitoring of drawer components that are performed by the CPU in R1 servers. In addition, the R2 alarm card can operate in either R1 mode or R2 mode.
In R1 mode, an R2 alarm card operates as follows: supports RCC WatchDog control of the CPU performs power control and executes CLI commands at the drawer level supports the R1 alarm card Remote System Control (RSC) set of commands, with minor exceptions (consolehistory and loghistory are not supported) In R2 mode, an R2 alarm card operates as follows: does not respond to RCC WatchDog control exercises power control and executes CLI commands at the slot level, to allow for separate action on the host CPU, satellite CPU, and I/O cards supports a new CLI with a new set of commands (the rscadm utility is not supported in R2 mode)

Combo Card and Combo Card with RS232

qfe1 qfe0

Interphase 6535 T1/E1 Card

Front View

Back view

RCC Shelf
The Reliable Clustered Computing (RCC) shelf provides components that monitor, recover, and maintain the FMM-APs. Key among these components are the following:
the WatchDog pack (BMR6B) (R1 or R1SR frames in R1 mode only) the Power Converter pack (BMR5) (R1 or R1SR frames in R1 mode only) reliability software

Important! The RCC hardware components (WatchDog and Power Converter packs) are present but not used in R1SR frames that operate in R2 mode. They are not present in Universal frames. In R1SR frames that operate in R2 mode and in Universal frames, the functions previously performed by the WatchDog are performed by the servers alarm card and by new RCC integrity software.

RCC Shelf

WatchDog Pack (BMR6B)

The WatchDog is responsible for ensuring the availability of the FMM-APs by detecting failures and initiating graceful or hard failovers to a mate FMM-AP. It performs these functions as follows:
The FMM-APs in an FMM-APF exchange heartbeat and state information with the WatchDog. State changes are directed from the WatchDog to the FMM-APs over an RS-232 path.

In addition to monitoring FMM-APs, the WatchDog controls FMM-AP power. You access this power control from the FMS Local Maintenance Terminal (LMT) Emergency Interface (EI). For details about the LMT EI, refer to the FMS LMT Users Guide (401-710-221).

WatchDog Interface
Each GNP-AP has an RS-232 connection to the WatchDog. NGNAP has RCC WatchDog, but evolving to FMS Alarm Card WatchDog. An AP is promoted to ACTIVE when told to go ACTIVE by the WatchDog. (During Initialization.) An AP exchanges heartbeats with the WatchDog and must heartbeat 3 times in a Heart Beat

Heartbeats may carry other information such as state information and/or sequence numbers. (But dont get too complicated, or it wont be a heartbeat.)

Cajun HUB

400 Connections to HUB

800 Connections to HUB

OMP
Straight

FMS Base Cabinet

Ethernet Switch B
11 21 22 23 24 15 16 17 18 19

FMS-AP Frame 4
10 20

PCI2

PCI4

GNP-AP Frame 1
D-21 HUB A OUT HUB B OUT

Straight Crossover

Ethernet Switch A
11 21 22 23 24 15 16 17 18 19

Crossover
10 20

HUB A IN HUB B IN

GNP-AP Frame 2
D-21 HUB A OUT HUB B OUT

GNP-AP Frame 3
D-21 HUB A OUT HUB B OUT

FMS-AP Frame 5
FIP B

Crossover

Crossover

Crossover

17

Crossover

Crossover FIP A Crossover

17

HUB A IN HUB B IN

HUB A IN HUB B IN

1 Base Frame 5 GNP Frames 22 Other ( Growth 1xEv-D0, RNC ) 28 Frames Total

Frame Interface Panel ( FIP ) for Base Frame

Frame Interface Panel ( FIP ) for Growth Frame

Frame Interface Panel

The Frame Interface Panels, located in the rear of the FMM-APF, provide the interconnectivity between FMM-APF elements and external Flexent/AUTOPLEX network elements. For example, the Ethernet cable from the EINE for the FMM-AP is connected to the ENET0 connector for the Combo with RS-232 card on the Frame Interface Panel and then, through internal wiring within the FMM-APF, connected to Ethernet port 0 (qfe0) on the Combo with RS-232 card of the associated FMM-AP. The upper Frame Interface Panel (FIP) is located below the MFFU and serves the components in the upper half of the frame. The lower FIP is located between the two server shelves and serves the components in the lower half of the frame.

Maintenance Interface Panel

For Base Frame

For Growth Frame

DB-9F

2 Serial Null Modem Cables (RS-232)

DB-9F

Ethernet Cable (RJ-45)

LMT accesses Frame Components

Reference Documentation
Flexent Application Processor Cluster (APC) OA&M 401-710-101 Flexent Element Management System (EMS) User's Guide - 401-710-110 Flexent Mobility Server (FMS) Local Maintenance Terminal (LMT) User's Guide - 401710-221 Flexent Mobility Manager Application Processor Cluster OA&M - 401-710-201 Flexent Mobility Manager Call Processing and Database Nodes OA&M - 401-710-209 Flexent Mobility Manager Database Management System OA&M - 401-710-203 Flexent Mobility Manager Home Location Register/Visitor Location Register OA&M 401-710-204 Flexent Mobility Manager Overview and Migration Description - 401-710-200 Flexent Mobility Manager Read-Only Printer OA&M - 401-710-202 Flexent Mobility Manager Signaling System 7/Direct Link Node OA&M - 401-710-205 Flexent Mobility Manager Status Display Process OA&M - 401-710-207 Flexent Mobility Manager TI Reference Guide - 401-710-211 Flexent Mobility Manager Technician Interface Implementation - 401-710-210 Flexent Mobility Manager Voice Channel Administration OA&M - 401-710-206 Radio Cluster Server and Flexent Mobility Manager Radio Cluster Server OA&M 401-710-102 High Speed Links Between the 5ESS Switch DCS and ECP/FMM-AP 401-612-739

1xEV-DO RNC R1SR Frame

FMS Sun 410S Application Processor (AP)
2, 4, 6 or 8 APs per frame SUN sparc processors running Solaris Perform call control & signal processing
MFFU RCC Shelf
Gig-E Module
TP Cards

Traffic Processor (TP)

2 TPs per AP drawer PowerPC processors running VxWorks Performs RLP & PCF processing Force TP690, Artesyn 752i

A1 1 U B

A3 2 U B

A5 3 U B

A7 4 U B

Layer 2 Hubs

Redundant 48 port Cajun P334T Layer 2

Switches
Copper Fast-Ethernet intra-frame connectivity Fiber Gig-Ethernet module aggregates external connections

410S APs (A-servers)

Gig-E Module

A2

A4

A6

A8

Reliable Clustered Computing (RCC) hardware

manages frame integrity Standard 5E cabinet with MFFU

1 L A

2 L A

3 L A

4 L A

1xRNC Frames

AP Software Overview

5/1/2012

AP-Software
rcs modcell/microcell/onebts Application (RCS)

platform rcc

Flexent AP (All APs)

GIU
HP OS

FMM-Software
Applications ( ROP, Database, VCA, HVLR, RCS, CDN, HSL/DLN, SP ) ngn_platform fms_rcc

MM-AP (All APs)

bundle
Sun Solaris OS

FMM-AP Bundle
A bundle is a collection of software packages combined in a self-extracting file. Packages, each of which includes a set of related files, are installed by executing the bundle file. This type of self-extracting installation is standard on Windows PCs but is new to the UNIX machines. The FMM-AP bundle is a collection of packages considered essential for any application that runs on an FMM-AP. For example, the FMM-AP bundle includes: device drivers, such as drivers for the Ethernet, serial, and T1/E1 interfaces utilities for setting up the .profile and shell environment for MM-AP users utilities for doing FMM-AP software updates and generic retrofits utility for FMM-AP performance monitoring

FMM-AP fms_rcc
The fms_rcc software package provides a high availability software infrastructure that works with the WatchDog to perform the following functions: monitoring and controlling the reliability of applications that run on the FMMAPs maintaining state and resource information directing fault recovery actions Important! In R1SR frames that operate in R2 mode where the WatchDog is present but not used, and in Universal frames, which do not include a WatchDog, the fms_rcc package includes new RCC integrity software that performs the functions previously performed by the Watchdog.

Reliable Cluster Computing (RCC)

Provides a high-availability software platform that works with the WatchDog/Maintenance Module to perform: Monitoring and controlling the reliability of applications that run on the APs. Maintaining state and resource information directing fault recovery actions. RCC runs as a single finite state machine. Maintains state information in ASCII files that are shared by all machines in the cluster (systemfile and APcluster.)

Controls a set of machines and the processes that run on them.

Reliable Cluster Computing (RCC) provides System Integrity:

Provides regular heartbeats to the WatchDog. Sends state and configuration information to the WatchDog on startup. Sequences the startup and recovery of the machine. Manages the movement of processes or shared resources between machines in a cluster. Controls the movement of virtual cluster virtual machines between ACTIVE/STANDBY. Detects hung or insane processes through a periodic check-in mechanism. RCC also provides Resource monitors

FMM-AP ngn_platform
The FMM-AP supports software (that is, the ngn_platform software package) provides a software infrastructure that performs the following functions:
enabling technician commands to be processed reporting status to the Element Management System (EMS)

FMM Application software

The applications that can reside on FMM-APs include the following: Flexent Mobility Manager Alarm Scanning (FMM-AS) Flexent Mobility Manager Call Processing and Database Nodes (FMM-CDN) Flexent Mobility Manager Database Management System (FMMDBMS) Flexent Mobility Manager Home/Visitor Location Register (FMM-HVLR) Home/Visitor Location Register Integrity Monitor (HVLR-IM) Flexent Mobility Manager Radio Cluster Server (FMM-RCS) Flexent Mobility Manager Read-Only Printer (FMM-ROP) Flexent Mobility Manager Signaling System 7/Direct Link Node (FMMSS7/FMM-DLN) Flexent Mobility Manager Ring Data Base Update (FMM-RDBU) Flexent Mobility Manager Status Display Process (FMM-SP) Flexent Mobility Manager Technician Interface (FMM-TI) Flexent Mobility Manager Translations (FMM-TR) Flexent Mobility Manager Voice Channel Administration (FMMVCA)

Software Updates

Flexent AP Software Update

Flexent AP
GIU Platform Package RCC Package

MM-AP
- Bundle - NGN_Platform Package - FMS_RCC Software Package

GNP AP Software Update

SOFTWARE UPDATE
Golden Image Update (GIU) consists of: patches to the HP OS and drivers (i.e 200020423)

Platform Package (APXX.0.00YYz) (i.e XX=Release YY=SUlevel z=craft/temp

AP19.0.0005b)

Reliable Cluster Computing (RCC) XXXXXX

(i.e. 062120)

FMM- Software Update

Bundle Package (i.e. 200301180855R200_NGN.bun)
consists of :
Solaris Operating System (Solaris 2.8 currently) Various Lucent Software packages including I/O drivers etc. Software Update Release Notes refer to it as bundle

Reliable Cluster Computing (FMS_RCC) XXXXXX (i.e. 062120)

Software package running on the FMM-AP along with the Watch Dog Module located in the RCC Shelf provides the High-Availability capabilities. Has dependencies with NGN Platform Package.

FMM Software Update

NGN Platform Package (APXX.0.00YYz) XX=Release YY=SUlevel z=craft/temp Autoplex related software Will Change with EACH Software Update/Generic Retrofit. Has dependencies with other Software packages running on the FMM-AP. Each NGN Platform Package is Compatible with specific RCC package and ECP Generic. cat /ap/platform/new/data/RccCompatible

AP Software Update
At AP:/var/spool/ap/pkg

rcc platform XXXXXX APXX.0.00YYz RCC.pkg FXX00DDGA.00

modcell

rcs
FXX00DDGA.00 FXX00DAGA.00 modcell.pkg rcs.pkg rcs.pkg

microcell

FXX00DAGA.00

platform.pkg

microcell.pkg

FMM Software Update

Bundle goes to /var/flx/bun

At MM-AP:/var/spool/ap/pkg

fms_rcc ngn_platform XXXXXX APXX.0.00YYz RCC.pkg FXX00DDGA.00

modcell

ngn_rcs
FXX00DDGA.00 FXX00DAGA.00 modcell.pkg ngn_rcs.pkg ngn_rcs.pkg

microcell

FXX00DAGA.00

ngn_platform.pkg

microcell.pkg

Install Activity on MM-APs

clean up - Removes ngn_platform and fms_rcc packages that are not being used from /var/spool/ap/pkg directory. Uses the appkgunload command. Removes the bundle not being used from /var/flx/bun with appkgunload command. - Transfers the ngn_platform, fms_rcc and Bundle software packages from the OMP to the MM-APs, uses the appkgtrans command. - Installs the fms_rcc and the ngn_platform software packages, uses the apinstall command. Executes the bundle to install it. - This step performs a flxapply.

transfer

install

prepare

Activate activity on MM-APs pre 54

backup ( pre_act) - Makes a backup of the current software before the activation of the new software load, uses the apbackup command. - Inhibits the RCV and Audits from the 800 Servers. If the site has CDN IVs it will also inhibit them, uses TICLI inh command - Perfroms a switchover of the applications that are active on this AP, uses TICLI switchover command - Removes the AP using the TICLI rmv command. - Offlines the AP, apoffline command - Activates the bundle, fms_rcc, ngn_platform and dbms_data, uses the apactivate command. - Reboots the AP.

inhibit

switchover

remove offline activate

reboot

Activate activity on MM-APs post 54

aponline restore allow backup (post_act) - Brings the MM-AP online, uses the aponline command. - Restores the MM-AP server to service, uses the TICLI command rst: ap XX - allows the applications on the APs, using the TICLI alw command. - Makes a backup of the new activated software load, uses the apbackup command. - Performs a status on the AP to see active alarms, uses TICLI op:ap xx,alarm command.

query

AP unix shell
The AP OA&M commands that are issued from the unix shell on the AP are on the path, so just type them--they are: aponline takes an AP from offline to init state. This will always result in a machine reboot.. apoffline takes machine from any state to offline. This command usually takes a while, and in some unusual circumstances may fail. apstatus reports the AP RCC status, but reports only Unavailable (when pmon is not running), Offline (when the AP is offline), and Online (for all other states). A more useful status query is RCCcstat, which gives the RCC status of all APs in the cluster.

Software installation commands

Usage: apinstall appkgrm appkgtrans apactivate apbackout appkginfo appkgchk -p package [-d directory] [-v version] [-s server] [-q] -p package [-D directory] [-v version] [-s server] [-q] -p package [-d directory] [-v version] [-s server] [-q] [-D directory] [-l login] [-z password] -p package [-s server] [-q] -p package [-s server] [-q] -p package [-D directory] [-v version] [-s server] [-q] -p package [-D directory] [-v version] [-s server] [-q]

-p the name of the package(s). + A group of packages may be selected by surrounding the group in quotes, or by the repeated use of the '-p' option. -d the name of the directory where the package(s) are found. -D the name of the directory where the package(s) are put. -v the version number of the package(s). -s the server's uname (remote for appkgtrans; local for all other). -q request quiet (non-interactive) installation service. When '-d' '-D' or '-v' precedes '-p' it is global. When '-d' '-D' or '-v' comes after '-p' it is specific to that package.

apinstall unbundles software from its package and places individual files in appropriate directories on the AP. For platform and rcc packages, makes new software ready for activation. appkgrm Removes unbundled software package from the AP. Can be used to produce the effect of a commit:ap command when the AP is offline. appkgtrans Transfers software package from the OMP to the AP. apactivate Rearranges software files and directories so that the desired version becomes the running version. Usually used to complete a software update if the AP is offline. apbackout Changes the backout version of the platform software to the default version, and changes the default version to the new version. Used to backout an SU if the AP is offline. appkginfo Can be used to find out what packages have been installed. appkgchk Compares the checksums from the pkgmap file for a package with the checksums of all the installed files. apdelcellsw Used to delete installed rcs and microcell packages when they are no longer needed. Note that apbackup should be run after using this command

FMM-AP Software bundle

Install Packages - Bundle
Operating System updates/Lucent FMS related patches.flxbuninfo to see information on installed/uninstalled bundles. ap21:root > flxbuninfo
200204051217R180_NGN 2002 200205300231R180_NGN 12:30:22 2002 200206280732R180_NGN 17:42:02 2002 bundle installed successfully Fri Jun 7 12:59:29

bundle installed successfully Thu Jul 11

bundle installed successfully Tue Jul 16

To install a new bundle

cd /var/flx/bun chmod +x XXXXXXXXXXXXRXX0_NGN.bun ./ XXXXXXXXXXXXRXX0_NGN.bun

FMM-AP Software bundle

Bundle Activation (AP must be offline) Allows OS related patches to be applied. Depending upon the SU level, takes long time. May require reboot of the FMM-AP.

To activate the bundle flxactivate -v r Allows user to activate an installed bundle. It is possible that you may have nothing to activate. If needed, during the flxactivate -v the system may reboot. flxactivate -v will continue to do its work after the system comes back up.

FMM-AP Software bundle

To monitor flxactivate progress: Enter:

tail f var/flx/logs/FMSsugr/latest
To find out if there are packages that need to be activated from previous bundles or if the current flxactivate is finished. Enter:

flxactivate n
output: flxactivate: NOTICE: dry run mode - system will not be changed flxactivate: There are no packages to activate or deactivate. If the output is different than that above, then flxactivate v -r needs to be run again.

flxsustatus will also give status of the latest flxactivate

Bundle & Packages

Each Bundle contains many packages.
FMSvdisk, NGNsugr, FMSsugr etc. The package provide many different items needed for the ngn_platform Software to work.

Installation of the bundle does the following:

It checks for the currently installed version of a package. Installs it if new version of the package is being delivered in the SU, else, package is skipped. Creates new links so that flxactivate can do the activation. Packages are installed based upon type of the server and the application it is CONFIGURED to run

Installed under /flx/PACKAGE_NAME

FMM-AP ngn_platform
platform/ ngn_platform installation
Installed on AP/FMM-AP under /ap/platform/new Installation of new platform/ngn_platform will be denied if: Previous software has not been committed. Another platform is already installed (the new directory is already under /ap/platform/new) Command was mistyped

/ap/platform new default backout

GNP & FMM AP platform activation

platform/ngn_platform Activation
Moves new ngn_platform from /ap/platform/new to /ap/platform/default Moves old ngn_platform from /ap/platform/default to /ap/platform/backout It also modifies various other configuration files that require updates. Works differently than the ngn_platform activation MORE THAN JUST A DIRECTORY MOVE.

GNP & FMM AP RCC installation

rcc/fms_rcc Installation
Does not hurt to install it again New fms_rcc package is installed under /opt/rcc/su

/opt/rcc su default backout

FMS_RCC package is different from Flexent GNPAPs May have the same version number, but compiled for either Solaris or HP Unix.

To remove old savesets and packages

Old AP platform/rcc or FMM ngn_platform/fms_rcc Packages /var/spool/ap/pkg/platform /var/spool/ap/pkg/rcc /var/spool/ap/pkg/ngn_platfor m /var/spool/ap/pkg/fms_rcc /var/spool/ap/apxx/apbkup appkgunload p platform appkgunload p rcc appkgunload p ngn_platform appkgunload p fms_rcc rm r 20030113

apbackupsavesets

Cell Generics Packages

/var/spool/ap/pkg/modcell /var/spool/ap/pkg/rcs /var/spool/ap/pkg/microcell /var/spool/ap/pkg/ngn_rcs

appkgunload p modcell appkgunload p rcs appkgunload p microcell appkgunload p ngn_rcs

apdelcellsw

Installed Cell Generics

Software Update Automation (SUA) SUA log files at the OMP

- For GNP-AP - For MM-AP /opt/sua/log/APlog /opt/sua/log/MM-APlog

The log below shows a more detailed description of whats happening during all activities while the SUAGUI is performing tasks on MM-APs /var/ap/platform/logs/swadm/sugrDBG.log

LOG FILES
Log file associated with Bundle: /var/flx/logs/FMSsugr/latest Log files associated with platform/ngn_platform and rcc/fms_rcc and SUA /var/ap/platform/logs/admin/sugr.log Use UNIX tail f command on either log file to monitor progress

Other Useful Logs

RCC log files cd /opt/rcc/default/var ls rccout.log rccout.log.old Admin log files
cd /var/ap/platform/logs/admin cat XXXXXXXX.ADM (ei. 20030318.ADM)

UX Log files cd /var/ap/platform/logs/ux ls XXXXYYZZ.PERF XXXXYYZZ.ERR XXXXYYZZ.DBG Hardware Messages cat /var/adm/messages

XXXX= year YY=month ZZday

Other directories where outdated files can be removed

/usr/tmp /var/tmp /var/adm/crash (core files) crash.X (x= number) this is a directory /var/flx/bun ( For FMM only )