Cisco Cisco ASR 5000

 

▄  ESS Administration and Reference, StarOS Release 17 

This section describes the internal directory structure of the ESS server. 

The chassis creates individual directories by its name under the base directory. Also, separate sub-directories are created 
for edr and udr under the chassis’ directory. Thus, the directory structure should be similar to the following: 

|_____ <Local data directory > e.g. /less/ess/data 

         | |_____<STX-1> e.g. /less/ess/data/stx-1 

              | | |_____udr 

                  | | | |______temp 

                   | | | |______temp_dest1 

                   | | | |______temp_dest2 

                   | | | |______temp_dest3 

              | | |_____edr 

                  | | | |______temp 

                   | | | |______temp_dest1 

                   | | | |______temp_dest2 

                   | | | |______temp_dest3 

         | |_____<STX-2> e.g. /less/ess/data/stx-2 

              | | |_____udr 

                  | | | |______temp 

                   | | | |______temp_dest1 

                   | | | |______ temp_dest2 

                   | | | |______ temp_dest3 

              | | |_____edr 

                  | | | |______ temp 

                   | | | |______ temp_dest1 

                   | | | |______ temp_dest2 

                   | | | |______ temp_dest3 

The STX-n indicates the name of the chassis.  

In case of cluster environment, the chassis is configured to push the files to central location on shared disk so that active 
ESS cluster nodes will be able to retrieve the files in case of switchover / failover. 

In case of any chassis failure during file transfer, it will push the half-cooked file again. Since chassis is pushing the 
files to ESS, missing of any files is reported by chassis and if some files are deleted due to insufficient disk space, the 
chassis generates an alarm.