Switching

Hi All,

I have switch qfx5110 with some JNP-SFPP-10GE-T modules installed.
The modules are recognized by switch correctly.

show chassis hardware | match 10GBASE-T
    Xcvr 0       REV 01   740-123734   2P1CTTAA460E3     10GBASE-T
    Xcvr 3       REV 01   740-123734   2P1CTTAA460E9     10GBASE-T
    Xcvr 4       REV 01   740-123734   2P1CTTAA460EV     10GBASE-T

And I expected them to be available as interfaces starting with xe-0/0/…., like xe-0/0/0, xe-0/0/3 etc.
But show interfaces xe-0/0/0 gives
error: device xe-0/0/0 not found

and the same for 

 show interfaces ge-0/0/0
error: device ge-0/0/0 not found

I found these ports are available with show command as mge interfaces
show interfaces terse | match mge
mge-0/0/0               up  down
mge-0/0/3               up    down
mge-0/0/4               up    down

but mge interface is not suggested as available interface under configuration mode (xe... is suggested instead)
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
  em1                  Interface name
> interface-range      Interface ranges configuration
> interface-set        Logical interface set configuration
  irb                  Interface name
> stacked-interface-set  Stacked interface set configuration
> traceoptions         Interface trace options
  vme                  Interface name
  xe-0/0/0             test

so autocomplete not working for mge in configuration mode, but switch allows to put mge interface manually to configuration like "set interfaces mge-0/0/0 description 123" and saves it to config without any error.

The junos version is 23.4R2-S8.7

Could somebody advise if it is expected and we should proceed with mge in config or it could be fixed (make them available as xe-...) with some newer junos?

Thank you!

Hey,

 it seems like you're expecting autocompletion for any interfaces (at least those visible in `> show interfaces terse`) when using `# set interfaces ?`-but no, that's not the case.
Autocompletion-or rather, a hint-indicates that an interface previously defined in the configuration exists and is displayed in the ? prompt.

What's more, you can try a harmless experiment:
1. In configuration mode (without a final commit, and before exiting with rollback 0!)
  try deleting a real interface (one visible in `terse`) that was previously configured from the candidate configuration

  and immediately check the output list with:
  # set interfaces ?
  you won't find it

  # rollback 0
  # quit

2. Also in configuration mode (without a final commit, and before exiting with rollback 0!), create a nonexistent interface in the candidate configuration, adhering to the following conditions [mge|xe|ge]-fpc/pic/port:
    fpc value outside the range 0..3
    pic value outside the range 0..3
    port value outside the range 0..63

For example:
   set interfaces xe-3/3/63 description TEST

   And immediately check the list:
  # set interfaces ?
   You'll find it!
 
  # rollback 0
  # quit

I think it's now clearer what autocompletion means in configuration mode, specifically for Juniper interface names ;)

Hi!

Thank you much for detailed explanation.

I was pretty sure that hints are based on physical interface presence rather than on existing config for this interface.

Thx once again.

Hi

Hi,

it seems like you're expecting autocompletion for any interfaces (at least those visible in `> show interfaces terse`) when using `# set interfaces ?`-but no, that's not the case.
Autocompletion-or rather, a hint-indicates that an interface previously defined in the configuration exists and is displayed in the ? prompt.

What's more, you can try a harmless experiment:
1. In configuration mode (without a final `commit`, and before exiting with `rollback 0`!)
  try deleting a real interface (one visible in `terse`) that was previously configured from the candidate configuration

  and immediately check the list
  `# set interfaces ?`
  you won't find it

  # rollback 0
  # quit

2. Also in configuration mode (without a final `commit`, before exiting `rollback 0`!), create a nonexistent interface in the candidate configuration, adhering to the following conditions:
    fpc value outside the range 0..3
    pic value outside the range 0..3
    port value outside the range 0..63
   For example:
   `set interfaces xe-3/3/63 description TEST`

   And immediately check the list:
  `# set interfaces ?`
   You'll find it!
 
  # rollback 0
  # quit

I think it's now clearer what autocompletion means in configuration mode, specifically for Juniper interface names ;)