Skip to main content
MontanaMike
New Member
July 21, 2020
Question

MGMT Interface on "Internal"

  • July 21, 2020
  • 2 replies
  • 10917 views

Stupid question that I've been beating my head against.  My new FS (1048E running v6.4.2) has a dedicated mgmt interface but I don't want to use it and would rather have mgmt allowed on any interface that is up/connected to the network and essentially has a management IP address assigned globally.  On my old switches I'd assign an IP address to a VLAN and allow mgmt protocols.  Pretty simple.  I've followed the instructions in the admin guide for both "models with dedicated" and models without but am stumbling at the part where after configuring the "internal" interface (ip address, allowed access, etc) it wants me to "create a new interface to be used for management" and assign an address to it...which it won't allow because the mgmt address is in use by the "internal" interface.

 

config system interface      edit internal          set ip 172.16.1.50/24          set allowaccess ping https ssh          set type physical          set secondary-IP enable               config secondaryip                   edit <id>                       set ip <IP_address_and_netmask>                       set allowaccess <access_types>                  next             end

        next edit MGMT1          set ip 172.16.1.50/24          set allowaccess ping https ssh          set interface internal          set vlanid 1          set secondary-IP enable                config secondaryip                edit <id>                set ip <IP_address_and_netmask>               set allowaccess <access_types>        end  end

that results in the obvious error of a duplicate IP.  I can't seem to turn it up unless it's on the dedicated mgmt port which I don't want. Any suggestions would be appreciated.

    2 replies

    brycemd
    New Member
    July 21, 2020

    Create a new interface and assign to the VLAN you want it on:

     

    edit 1

    set ip x.x.x.x

    set allowaccess https ping

    set vlanid x

    MontanaMike
    New Member
    July 21, 2020

    brycemd wrote:

    Create a new interface and assign to the VLAN you want it on:

     

    edit 1

    set ip x.x.x.x

    set allowaccess https ping

    set vlanid x

     

    I've done that and still nothing assuming the new interface has the IP I want to use for the mgmt interface. FS1 # config system interface FS1 (interface) # edit name    Name. internal   static   0.0.0.0 0.0.0.0  up   physical mgmt   static   0.0.0.0 0.0.0.0  up   physical netmgmt   static   172.16.1.50 255.255.255.0  up   vlan

    brycemd
    New Member
    July 21, 2020

    Not really sure, that's what I always do and I've never had an issue with it.

     

    Are you attempting to access from same VLAN? Maybe missing a gateway?

     

    I guess can you show the config for netmgmt

    mhepburn_FTNT
    Staff
    Staff
    August 17, 2020

    Try enabling "allow-subnet-overlap" in system.global: config sys global

    set allow-subnet-overlap enable end Be careful with it though, it's not used often so there could be some problems running with duplicate IPs.