Cisco Cisco Packet Data Gateway (PDG)

 

▄  VPC-VSM System Administration Guide, StarOS Release 19 

The local VPC file system is made up of files that are stored on the following: 



 

/flash – Flash memory allocated as vHDD-1 via the hypervisor is the default storage media for the StarOS 

image, CLI configuration, and crash log files used by the system. 



 

/hd-raid – This is the storage space allocated as vHDD-2 by the hypervisor. It is used to store CDRs (Charging 

Data Records) and UDRs (Usage Data Records). 

The following file types can be located in the local file system: 



 

Operating System Software Image File: This binary file type is identified by its .bin extension. This file is 

StarOS and is loaded upon startup or reloading. This is an executable, read-only file that cannot be modified by 
end users. 



 

CLI Configuration File: This file type is identified by its .cfg extension. These are text files that contain CLI 

commands that work in conjunction with the StarOS image. They determine services to be provided, hardware 
and software configurations, and other functions performed by the system. The files are typically created by the 
end user. You can modify the files both on and off-line and use descriptive long filenames. 



 

System File: Only one file identified by a .sys extension is used by StarOS. The boot.sys file contains system-

specific information, which describes how the system locates, and in what priority it loads, file groups (paired 
.bin and .cfg files) from its boot stack. 



 

Abridged Crash Log: The abridged crash log, identified by its crashlog filename, contains summary 

information about software or hardware failures that occur on the system. This file is located in the 
/flash/crsh2/ directory on the device. You can view the contents of this file through the CLI, but you cannot 
modify the file. 

StarOS uses the boot.sys file to store the prioritized boot stack parameters and file groups the system uses during 
startup. Modify this file only through StarOS CLI commands and not through external means. Boot parameters contain 
information StarOS needs to locate the StarOS image file, including: 



 

bootmode: This setting is typically configured to normal, and identifies how StarOS starts. 



 

boot stack information: The boot stack is made up of prioritized file group entries that designate the StarOS 

image file and the CLI configuration file to load. 

When VPC is started for the first time, the boot.sys file is configured to use the normal boot mode and load the StarOS 
image from the /flash directory. 

There is no CLI configuration file contained on the local file system. This causes StarOS to automatically start its CLI-
based Quick Setup Wizard upon the first successful boot. Refer to the Getting Started chapter for more information on 
using the Quick Setup Wizard.