ISR1100 VLAN1 IP Address unreachable unless intf in switch connected

[sabu123]

Hi

So I have an ISR1100 and unless a cable is connected to at least 1 of the switch ports the VLAN 1 IP address is unreachable from the WAN interface.

I have read about the "autostate" function and that has now been removed so I tried the "keepalive" but that doesn't appear to resolve the issue.

I don't really want to have to create a loopback address I just want the IP I have assigned to VLAN1 to be reachable even if the switch has no ports physically connected to another NIC

I come from Mikrotik land so it is unusual to me to see this behaviour although it is well documented on Cisco's there isn't an obvious answer I can find so hoping someone who knows more about Cisco than me can help

Thank you

[MHM Cisco World]

Hi

Two things make this issue 

Vlan need physical port to he up

Vlan need to add to database 

You override first via autostate 

You need to add vlan also I think 

[sabu123]

Hi

I think the autostate feature has been removed as a command because it doesn't appear to be an option whether applied to a physical interface or a VLAN although I do understand this is a hidden option and I have read this option has been removed:

switch(config)#interface gigabitEthernet0/1/0
switch(config-if)#no autostate
                                  ^
% Invalid input detected at '^' marker.

 The ISR is running Cisco IOS XE Software, Version 16.08.01

Thank you

[MHM Cisco World]

I think this SW not support feature of no autostate that why you need to add physical port to vlab to make it UP.

Also why you need vlan to be up if there is no active physical port? It have no meaning.

You can use LO to ping router not Vlan SVI without port 

[sabu123]

Hi

So the reason why I would like it to be reachable is because the address attached to the VLAN is the public IP and it is the one the customer uses to monitor pings etc externally to see if the link is up before they accept the connection and connect their own equipment to the switch. It is also their gateway address when a host is connected to the switch.

So for example here is the VLAN config but I have changed the public IP to be 1.2.3.4 for privacy in this example:

interface Vlan1
 ip address 1.2.3.4 255.255.255.248

This is routed via 10.0.9.225 and 10.0.9.224 at ISP side with the DR pointing to 10.0.9.225

ip route 0.0.0.0 0.0.0.0 GigabitEthernet0/0/0 10.0.9.225

 It all works fine but it is just annoying that Cisco routers seem to insist on making the address unreachable, even though it is assigned to a virtual interface in this case a VLAN which cant go down since its not physical.

Thanks

[MHM Cisco World]

Hi

I will check in lab and send you private message.

Thanks 

MHM