Description

This article describes about the configuration commit issue on EX3400 VC caused by 109% usage of /dev/gpt/junos.

Symptoms

Storage usage causing commit issue on the EX3400 VC setup. Below are the sample outputs where fpc 0 is master and fpc 1 is backup.

 

Below error observed while committing the configuration where /dev/gpt/junos using 109% of switch storage.

error: init: write failed: No space left on device
error: configuration check-out failed: daemon file propagation failed

 

root> show chassis alarms

1 alarms currently active

Alarm time              Class Description

2024-05-29 00:51:16 UTC Minor FPC 1 /var partition usage is high

 

root> show system storage all-members

fpc0:

--------------------------------------------------------------------------

Filesystem             Size      Used     Avail Capacity  Mounted on

/dev/gpt/junos          15G      1.4G       13G      109% /.mount

tmpfs                   20M      140K       20M       1% /.mount/tmp

tmpfs                  653M      604K      653M       0% /.mount/mfs

 

fpc1:

--------------------------------------------------------------------------

Filesystem             Size      Used     Avail Capacity  Mounted on

/dev/gpt/junos          15G       11G      3.7G      10% /.mount

tmpfs                   20M      152K       20M       1% /.mount/tmp

tmpfs                  610M      800K      609M       0% /.mount/mfs

 

fpc2:

--------------------------------------------------------------------------

Filesystem       Size   Used   Avail Capacity Mounted on

/dev/gpt/junos     15G   1.4G    13G   10% /.mount

tmpfs          20M   152K    20M    1% /.mount/tmp

tmpfs         653M   676K   653M    0% /.mount/mfs

 

 

Solution

Perform steps mentioned below to fix the storage issue:

 

1. Change the mastership to FPC 1 from FPC 0 using the command "> request virtual-chassis routing-engine master switch" command must be issued from current master.

 

2. Once the FPC1 is becomes master, commit the configuration changes on the present master (FPC 1).

 

3. Reboot the FPC 0 to fix the storage issue.

 

4. Once the reboot is complete, the FPC 0 will rejoin the virtual chassis as backup.

 

5. Verify the storage percentage used by /dev/gpt/junos

 

6. Issue the command "> request virtual-chassis routing-engine master switch" to change the mastership from FPC1 to FPC 0 and see if that fixes the storage and commit issue.

 

7.If above steps doesn't solve the issue, then perform format install on problematic VC member by isolating it from VC.

 

Procedure to format install EX2300 switches: https://supportportal.juniper.net/s/article/EX-How-to-format-install-EX2300s-and-EX3400s-via-USB?language=en_US

Modification History

2024-10-29 : Article Created