Wireless Access

Reply
Contributor I

VLAN 1 Operational State Down - Can't Ping Router

Hi


I have a weird issue with 2 4005 controllers.


I have assigned VLAN 1 with an IP of 192.168.1.50 on the primary and 192.168.1.51 on the secondary.

 

I have added the default gateway (router) to both controllers 192.168.1.1

 

On the secondary I can ping the default gateway.

 

On the primary I cannot ping it and it will not show on the router in the binding table with the statically assigned IP.


The VLAN is showing operational state down.  I have tried from the CLI to bring the oper state up by using command interface vlan 1> operstate up but it does not do anything.

 

Super Contributor I

Re: VLAN 1 Operational State Down - Can't Ping Router

Hi

 

Is VLAN 1 tagged or untagged to the right port?

 

The OAW 4005 is a Aruba7005, which firmware are you running?

 

 The command operstate up is normally used on VLAN's that don't have physical ports, like a guest VLAN that only has an SSID attached to it.

 

 

Cheers, Frank
Aruba Partner Ambassador| AMFX#22| ACCX#613| ACMX#733| ACDX#744

If you like my posts, kudo's are welcome. If it solves your problem, please click 'Accept as Solution'
Contributor I

Re: VLAN 1 Operational State Down - Can't Ping Router

Yes it is tagged to the correct port.

 

It is 6.5.4.7

 

Both controllers are running this.

 

The second controller has no issue.

 

Interface IP Address / IP Netmask Admin Protocol VRRP-IP (VRRP-Id)
vlan 1 192.168.1.50 / 255.255.255.0 up down none (none)

 

VlanId IPAddress Adminstate Operstate PortCount Nat Inside Mode Ports AAA Profile Option-82
------ --------- ---------- --------- --------- ---------- ---- ----- ----------- ---------
1 192.168.1.50/255.255.255.0 Enabled Down 2 Disabled Regular GE0/0/2 Pc0-7 N/A Disabled

 


Interface IP Address / IP Netmask Admin Protocol VRRP-IP (VRRP-Id)
vlan 1 192.168.1.51 / 255.255.255.0 up up none (none)

Vlan Status
-----------
VlanId IPAddress Adminstate Operstate PortCount Nat Inside Mode Ports AAA Profile Option-82
------ --------- ---------- --------- --------- ---------- ---- ----- ----------- ---------
1 192.168.1.51/255.255.255.0 Enabled Up 2 Disabled Regular GE0/0/1-0/2 Pc0-7 N/A Disabled

 

Super Contributor I

Re: VLAN 1 Operational State Down - Can't Ping Router

Hi,

 

It looks like the port on the first controller is down.

 

Can you switch the cables between the controllers to see it the problem moves with it?

 

Possible causes:

- bad cable

- broken switchport

- broken port on controller

 

Did you set the ports up as a single port? Or Port-Channel?

 

 

Cheers, Frank
Aruba Partner Ambassador| AMFX#22| ACCX#613| ACMX#733| ACDX#744

If you like my posts, kudo's are welcome. If it solves your problem, please click 'Accept as Solution'
Contributor I

Re: VLAN 1 Operational State Down - Can't Ping Router

Yip I switched the cable still only the second controller works so it is not a cable issue

 

I have tried a different port on the router and doesn't make a difference.

 

I have tried two ports on the controller and it doesn't make a difference.


I cannot get the operational state to change to up no matter what i do

Contributor I

Re: VLAN 1 Operational State Down - Can't Ping Router

OK so i changed the port on the controllers and set up a new VLAN - VLAN 100 on both


The same issue follows.  The first controller stays down and the second comes up.


I use the command and this time it works and it brings VLAN 100 operational state up but I still cannot ping the default gateway.  I can ping the default gateway from the other controller.  Here is the IP ROUTE from the working controller:

 

Gateway of last resort is Imported from DHCP to network 0.0.0.0 at cost 10
Gateway of last resort is Imported from CELL to network 0.0.0.0 at cost 10
Gateway of last resort is Imported from PPPOE to network 0.0.0.0 at cost 10
Gateway of last resort is 192.168.33.1 to network 0.0.0.0 at cost 10
Gateway of last resort is 192.168.1.1 to network 0.0.0.0 at cost 1
S* 0.0.0.0/0 [0/1] via 192.168.1.1*

C 192.168.1.0/24 is directly connected, VLAN100

 

 

And non working:


Gateway of last resort is Imported from DHCP to network 0.0.0.0 at cost 10
Gateway of last resort is Imported from CELL to network 0.0.0.0 at cost 10
Gateway of last resort is Imported from PPPOE to network 0.0.0.0 at cost 10
Gateway of last resort is 192.168.33.1 to network 0.0.0.0 at cost 10
Gateway of last resort is 192.168.1.1 to network 0.0.0.0 at cost 1
S* 0.0.0.0/0 [0/1] via 192.168.1.1*

C 192.168.1.0/24 is directly connected, VLAN100

 

 

 

Super Contributor I

Re: VLAN 1 Operational State Down - Can't Ping Router

Hi

 

If you issue a write erase all on the first controller and do a complete fresh setup and still it doesn't work then contact TAC, maybe you have a faulty controller.

 

 

Cheers, Frank
Aruba Partner Ambassador| AMFX#22| ACCX#613| ACMX#733| ACDX#744

If you like my posts, kudo's are welcome. If it solves your problem, please click 'Accept as Solution'
Contributor I

Re: VLAN 1 Operational State Down - Can't Ping Router

OK so i have set up another vlan with a local network.

 

192.168.33.1 and 192.168.33.2 just plugged into a switch and they can ping each other etc.  I don't think it is a faulty controller

Super Contributor I

Re: VLAN 1 Operational State Down - Can't Ping Router

Hi

 

Can you sned a picture on how the connections are setup now?

 

did you disable Spanning-tree on the controllers? If they are connected by a single connection switch off spanning tree. but please take care not to create loops.

 

 

 

Cheers, Frank
Aruba Partner Ambassador| AMFX#22| ACCX#613| ACMX#733| ACDX#744

If you like my posts, kudo's are welcome. If it solves your problem, please click 'Accept as Solution'
Contributor I

Re: VLAN 1 Operational State Down - Can't Ping Router

Gateway of last resort is Imported from DHCP to network 0.0.0.0 at cost 10
Gateway of last resort is Imported from CELL to network 0.0.0.0 at cost 10
Gateway of last resort is Imported from PPPOE to network 0.0.0.0 at cost 10
Gateway of last resort is 192.168.33.1 to network 0.0.0.0 at cost 10
Gateway of last resort is 192.168.1.1 to network 0.0.0.0 at cost 1
S* 0.0.0.0/0 [0/1] via 192.168.1.1*
C 192.168.33.0/24 is directly connected, VLAN9
C 192.168.1.0/24 is directly connected, VLAN100
C 192.168.33.4/32 is an ipsec map default-psk-redundant-master-ipsecmap

 

 


Codes: C - connected, O - OSPF, R - RIP, S - static
M - mgmt, U - route usable, * - candidate default, V - RAPNG VPN/Branch

Gateway of last resort is Imported from DHCP to network 0.0.0.0 at cost 10
Gateway of last resort is Imported from CELL to network 0.0.0.0 at cost 10
Gateway of last resort is Imported from PPPOE to network 0.0.0.0 at cost 10
Gateway of last resort is 192.168.33.1 to network 0.0.0.0 at cost 10
Gateway of last resort is 192.168.1.1 to network 0.0.0.0 at cost 1
S* 0.0.0.0/0 [0/1] via 192.168.1.1*
C 192.168.33.0/24 is directly connected, VLAN9
C 192.168.1.0/24 is directly connected, VLAN100
C 192.168.33.3/32 is an ipsec map default-psk-redundant-master-ipsecmap

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: