When hitting the questionmark inside of edit mode, indeed it will only display the interfaces that are defined in the current config. See below, first I type a questionmark with no interfaces defined, and then I define 1 interface and repeat:
{master:0}[edit]
user@switch# show interfaces
{master:0}[edit]
user@switch# edit interfaces ?
Possible completions:
<[Enter]> Execute this command
<interface-name> Interface name
> interface-range Interface ranges configuration
> interface-set Logical interface set configuration
> traceoptions Interface trace options
| Pipe through a command
user@switch# set interfaces ge-0/0/0.0 family ethernet-switching
{master:0}[edit]
user@switch# set interfaces ?
Possible completions:
<interface-name> Interface name
+ apply-groups Groups from which to inherit configuration data
+ apply-groups-except Don't inherit configuration data from these groups
ge-0/0/0 Interface name <<<<<<
> interface-range Interface ranges configuration
> interface-set Logical interface set configuration
> traceoptions Interface trace options
If you want to see the actual installed SFP modules detected, you can run the "show interfaces terse" from operational mode.
{master:0}[edit]
user@switch# run show interfaces terse
Interface Admin Link Proto Local Remote
ge-0/0/0 up down
gr-0/0/0 up up
pfe-0/0/0 up up
pfe-0/0/0.16383 up up inet
inet6
pfh-0/0/0 up up
pfh-0/0/0.16383 up up inet
ge-0/0/1 up down
xe-0/0/2 up down
xe-0/0/2.16386 up down
xe-0/0/3 up down
xe-0/0/3.16386 up down
xe-0/0/4 up up
xe-0/0/4.16386 up up
xe-0/0/5 up up
xe-0/0/5.16386 up up
bme0 up up
<...snip...>
Also, for VC it is not needed to do commit syncronize, as there is 1 config that is replicated automatically upon commit to all members. The commit syncronize is really for chassis that have multiple physical REs (like EX9200).
When in VC, all the managment and console ports on all of the members will just refer back to the current master. So no need to use another port for management.