There may be many instances when reviewing logs in a Scalar i2000 snapshot where the tape drive serial numbers will need to be identified. Resolving the tape drive serial numbers with their physical location in the library is important when verifying device configuration/presentation at the Operating System and Backup Application layers.

 

The Scalari2000 tape library can be configured to present a tape drive(s) physical Serial number or a logical serial number. Depending on the respective log and which implementation (physical or logical) and physical location, the S/N for a specific tape drive can vary in a Scalar i2000 library. Below summarizes examples of snapshot log files that include a tape drive serial number and how to recognize its respective physical and/or logical serial number.

 

 

Below summarizes a list of common log files that can be referenced for the tape drive serial numbers. Although the list intends to include the most commonly referenced log files, it may not include all files that reference serial numbers:

 

            # Includes both Physical and Logical SN by location in Scalari2000

 

            #Where I00xxxx = physical location nexus for respective IOB

            # Includes ONLY SN of Tape Drive SN implemented (Physical or Logical)

            # SN listed by connection path to the IOB regardless of physical location

 

# Where x =numeric value for month of year (1=Jan, 2=Feb, 3=Mar…etc)

            # Includes ONLY Physical SN of Tape Drive

            # SN listed by utilization of media mounts/dismounts

 

 

 

 

The rcs_snapshot.log is a log that records events, configuration and discovery information of the robotics. This log will include both the Physical and Logical SN listings for each drive installed into the library drive locations. This is helpful log to reference when correlating a specific drive location to an event highlighting by either Logical or Physical SN. Once the physical location and SN are confirmed, the other logs relating to that drive (\var\log\adic\I00xxxx\supportDump, \var\log\adic\M000127\0x-tmd_session..etc) can be usefully cross referenced to correlate connectivity or utilization related events. Below shows an excerpt of the \var\log\adic\R000117\snapshot\rcs_snapshot.log. Specifically, the example below highlights an excerpt that begins at a point in the log that can be found by searching on the term “MONITOR> DGetInfo”. This section includes slot by slot information for each drive location and includes the Physical and Logical SNs. This section can also helpful in confirming drive Fibre port WWNs:

 

Note: This example is highlighting sled location 0

 

 

 

The \var\log\adic\I00xxxx logs represent log files for each 6404 or 7404 IOB installed in the Scalari2000. There will be a unique file in the \var\log\adic\ directory for each IOB installed in the system based on it’s physical location in the Scalari2000 library (reference the i2000 Storage & Drive & IO Blade Mapping Tables.xls).

 

During device discovery, each IOB will detect tape drives connected on each IOB Fibre port. Depending on implementation, the tape drive sled will present either the drive brick Physical SN or the Logical SN. The IOB’s view of drive SNs can be captured in the following log sections; fcShowDevs, vpsShow, mapShowDevs, mapShowDatabase). With the exception of mapShowDatabase, these log outputs should never report BOTH Logical and Physical SNs concurrently (action: escalate). Below highlights some examples from the supportDump.log file:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

#### \var\log\adic\M000127\0x-tdm_session.log ####

 

There is a tdm_session.log for each month of the year. The numerical prefix can be used to identify which month of the year the respective file represents. The contents of the file summarizes information regarding media mount and dismount activity for specific media volsers and tape drives. This log file will always reference the tape drive Physical SN regardless of the implementation (Physical or Logical). Here are some example entries showing the tape drive serial numbers highlighted. This log is helpful gaining intuition on which drive SN was being used and what time that may coincide with a specific event or reported issue.