How to add new interfaces on Juniper SRX chassis cluster

There are many good JUNOS articles on setting up the Juniper SRX chassis. But I just want to summarize the steps on how to add new interfaces to existing chassis cluster. In other words, the following pre-requites are complete as follows:

1. Configuring Chassis Cluster information on both nodes e.g. set chassis cluster-id 1 node 0 
2. Configuring Redundancy Groups (RG) and specify which node should be the primary node for each RG. e.g. set chassis cluster redundancy-group 1 node 0 priority 200. This is also where you determine whether it is a Active-Passive or Active-Active setup
3. Configuring Out-of-Band management interface for fxp0 - optional
4. Configuring Virtual Routing instances (a.k.a VRF-lite in Cisco networking) - optional 
5. Configure the number of Redundant Interfaces using "set chassis cluster reth-count n" where n is the number of reth.
6. Configuring Redundant Interface (reth) using at least one interface from each node
7. Configuring control link using fxp1 interface where configuration synchronization takes place between 2 nodes 
8. Configuring fabric interface (fabn where n denotes the node id) consisting of at least one ethernet interface from each node
9. Successful cluster setup!

After you have established the cluster successfully, you may wish to add more interfaces to it. The additional steps are as follows:

Step1: Increase the reth count by using

• set chassis cluster reth-count n where n is the new number of reth interfaces

Step 2: Identify 2 similar interfaces (one from each node e.g. ge-0/0/2 and ge-8/0/2) to form a new reth. e.g. 

• set interfaces ge-0/0/2 gigether-options redundant-parent reth2
• set interfaces ge-8/0/2 gigether-options redundant-parent reth2

Step 3: Configure new reth2 by heading to "edit interfaces reth2"

• Enable VLAN tagging if you intend to use VLAN: "set vlan-tagging"
• Create new sub-interface: "set unit nnn vlan-id " where nnn is any sub-interface number.
• Assign IP address to sub-interface: "set unit nnn family inet address 1.1.1.1/24" 
• Return to top level edit: "top"

Step 4: Assign this interface to the virtual routing instance

• set routing-instances interface reth2.nnn

Step 5: Assign this interface to the appropriate security zone

• set security zones security-zone interfaces reth2.nnn

Step 6: Check new configurations and commit

• top
• show | compare rollback 0
• commit

Debugging JUNOS for Cisco dude

In Cisco IOS, you would use debug statement for troubleshooting. How would you do it in JUNOS?

For example, if you were troubleshooting SNMP in Cisco IOS, you would do this:
#debug snmp detail
#term mon

As for JUNOS,
> edit
# edit snmp
# set traceoptions flag all
# set traceoptions file debug-snmp
[Unlike Cisco IOS, you need to commit the changes first]
# top
# commit
[It will start the debugging in next statement]
# run monitor start debug-snmp
[Lots of debugging messages and when you're done, stop it]
# run monitor stop
# delete snmp traceoptions
# commit