invalid JSON (filename=/var/lib/openmediavault/dirtymodules.json)

When OMV fresh install, we found some bugs such as " invalid JSON (filename=/var/lib/openmediavault/dirtymodules.json)" when saving new setting.

Easy way to fix that only delete or rename file
 
/var/lib/openmediavault/dirtymodules.json

That's work

Add storage Proxmox

1. Create External LVM storage

Extra added hard drives without partitions.
Installation:
SDA is the drive where the proxmox installation is running SDB is the new drive that will be added to the proxmox.
- Open the Proxmox Shell

With fdisk you can find your drives that you want to add, if you are not sure what the device name is for your hard drive that you want to add. 
Type: fdisk -l

Find the "Disk" with no valid partition table. That will be probably your hard drive you want to add.
        "Disk /dev/sdb doesn't contain a valid partition table"
To make a partion on the new drive type the following:

T   - type cfdisk /dev/sdb

Choose the following options:
New - Primary - Specify size in MB Write Quit

Now a physical volume has to be created.
- type pvcreate /dev/sdb1

Create a volume group. The name "Data-Storage" is an example. You can name it anyway you want. Consider a logical name, because this is the name that will be used in the proxmox web interface:

Type: vgcreate Data-Storage /dev/sdb1

Add the storage in ProxMox
 

-       In the webinterface click on the directory Datacenter and then click
        on tab Storage.

-       Click Add – LVM Group

o    Type an ID Name for example data-storage

o    Base Storage: Existing Volume Groups

o    Volume Group: Data-Storage

o    Enabled: Checked
o    Other options should be adjusted accordenly to what you want
      with it. 

Now the extra storage has been added in Proxmox and ready for use.

 

 

 

2. Mounting external HDD to be add to directory backup file

 

Startup the server and run the following from commandline to find the device name for the disk:

1. fdisk -l

This should return something similar to this:

1. Disk /dev/sda: 21.4 GB, 21474836480 bytes
2. 255 heads, 63 sectors/track, 2610 cylinders
3. Units = cylinders of 16065 * 512 = 8225280 bytes
4. 
   
5. Device Boot Start End Blocks Id System
6. /dev/sda1 * 1 2517 20217771 83 Linux
7. /dev/sda2 2518 2610 747022+ 5 Extended
8. /dev/sda5 2518 2610 746991 82 Linux swap / Solaris
9. 
   
10. Disk /dev/sdb: 32.2 GB, 32212254720 bytes
11. 255 heads, 63 sectors/track, 3916 cylinders
12. Units = cylinders of 16065 * 512 = 8225280 bytes
13. 
    
14. Disk /dev/sdb doesn't contain a valid partition table

If it is the first new disk you have added it will more than likely be /dev/sdb as the device name.
Now we partition the disk:

1. cfdisk /dev/sdb

Select the following options:

• New > Primary > Enter (use the size in MB already specified)
• Write
• Quit

Now we format the disk to the ext3 filesystem:

1. mkfs.ext3 /dev/sdb1

Mount the drive to a new folder:

1. mkdir /mnt/backups
2. mount -t ext3 /dev/sdb1 /mnt/backups

Lastly we add the disk to /etc/fstab so it auto-mounts when we reboot the machine:

1. /dev/sdb1 /mnt/backups ext3 defaults,errors=remount-ro 0 1

That’s your drive mounted and ready to be added as backup storage in Proxmox.
To test: reboot the machine and confirm that the drive is still mounted.
 

JUNOS RIP OSPF routes Redistribution

IN FIGURE 1 WE SHOW A TOPOLOGY THAT IS RUNNING OSPF AND RIP. THIS LAB IS DESIGNED ON VMWARE JUNIPER OLIVE. THE GOAL FOR THIS TOPOLOGY IS SIMPLE: ROUTES REDISTRIBUTION BETWEEN ROUTERS. SO LET'S START:

1 Configuration on Juniper 1

1.1 Configure RIP protocol:

[edit]

root@juniper1# set interface em0.0 family inet address 192.168.3.1/24

root@juniper1# set interface em1.0 family inet address 10.1.1.5/24 ('this interface is used for test purposes)

root@juniper1# set protocols rip group small-rip neighbor em0.0

1.2 Configure RIP policy:

Default policy of RIP is to send out no routes unless explicitly

told to do so. In order to begin sending out routes, first write a policy on Juniper 1 that sends the locally connected interface routes into RIP:

[edit]

root@juniper1# set policy-options policy-statement send-connected term 1 from protocol direct

root@juniper1# set policy-options policy-statement send-connected then accept

1.3 Apply the policy to RIP:

[edit]

root@juniper1# set protocols rip group small-rip export send-connected

2 Configuration on Juniper 2:

2.1 Configure RIP protocol on interface em1:

[edit]

root@juniper2# set interface em0.0 family inet address 192.168.1.2/24

root@juniper2# set interface em1.0 family inet address 192.168.3.2/24

root@juniper2# set protocols rip group small-rip neighbor em1.0

2.2 Configure RIP policy:

root@juniper2# set policy-options policy-statement send-connected term 1 from protocol direct

root@juniper2# set policy-options policy-statement send-connected then accept

2.3 Apply the policy to RIP:

[edit]

root@juniper2# set protocols rip group small-rip export send-connected

2.4 Configure OSPF protocol on interface em0:

[edit]

root@juniper2# set protocols ospf area 100 interface em0.0

2.5 Next, Juniper 2 must take the routes it receives from RIP and redistribute them into OSPF, for this purpose create the following policy:
[edit]

root@juniper2# set policy-options policy-statement rip-ospf term 2 from protocol rip

root@juniper2# set policy-options policy-statement rip-ospf then accept

2.6 Apply the policy to OSPF:

[edit]

root@juniper2# set protocols ospf export rip-ospf

2.7 Now, create the policy for routes redistribution from OSPF into RIP :

[edit]

root@juniper2# set policy-options policy-statement send-default term 1 from protocol ospf

root@juniper2# set policy-options policy-statement send-default then accept

2.8) Apply the policy to RIP :

root@juniper2# set protocols rip group small-rip export send-default

3 Configuration on Juniper 3:

3.1) Configure OSPF protocol on interface em0:

root@juniper3# set interface em0.0 family inet address 192.168.1.5/24

root@juniper3# set interface em1.0 family inet address 10.1.1.1/24

root@juniper3# set protocols ospf area 100 interface em0.0

Now, routes from Juniper 1 are advertised to both routers Juniper 2 and Juniper 3. You can test it with ping command.