Assigning IP address to AP1231-G

[kralle840]

I'm trying to assign a IP address to my AP. I connect the AP directly to my computer (no DHCP). IPSU doesn't work. I switch my computer's address to 10.0.0.2 (AP is reseted to the default values) but still can't even ping the AP with 10.0.0.1 (should be the default value!). I get access to the AP via telnet. Looking at the IP configuration ('show ip interface brief') gives me 'IP address unassigned'.

I assigned an IP address via telnet and that works.

But this way is to complex. I have a customer in Singapore who needs help. I can't explain him from Germany how to use the telnet connection, etc...

Please help!

[thisisshanky]

THe iP address is assigned to the BVI interface and not the Dot11radio or Ethernet interface. Look under show ip interface brief and see if BVI interface has an ip address. Default is 10.0.0.1.

You could also start over by pressing the mode button to clear configs to factory defaults. This should reset the AP to 10.0.0.1 address. Then you can use IPSU to set the ip address. You can note the mac-address of AP from the back side sticker.

[v8625]

There seems to be misunderstanding. I see about a dozen instances of the same question - and it does not seem that anyone understands it completely in order for it to be answered.

I am having the same issue so I'll try and expain again - I have a an AIR-AP1231G-A-K9. I have connected an Ethenet cable from a Windows PC to its Ethernet port and set up the computer's network address to 10.0.0.2 in 255.0.0.0 subnet. I reset the AP and reboot the PC, and try to connect to AP using IPSU and set the IP address - only to get the error message "device does not answer for SET IP." Can't telnet to it either.

What else did I forget during the network setup part?

[enkrypt2000]

If you dont have a switch between the Windows PC and the Access point you shouldn't be using a standard ethernet cable. You need a crossover cable.

[v8625]

I am. I mean, I am using a crossover cable. And I can't even ping the AP. I tried every combination of IP/subnet I could think of - the subnets 255.255.255.224 and 255.0.0.0 and it's still cold. I ordered AIR-CONCAB1200 cable for console - my last remaining option. I don't know what else to try if I can't bring this thing alive via console. I feel kind of angry at Cisco - I am sure I can miss something obvious - anybody can - but I've been struggling with this thing for some time now - I might not be the sharpest tool in the box, but I am not that dumb either. So if I can't figure it out for so long, maybe it is not such a great product?

Again, IPSU returns only errors, arp -a says no arp entries, ping says request timed out, and relnet says something about no such host.

[Philip D'Ath]

Just thinking about the startup scenario here.

It will probabably take 2 to 3 minutes after power on before the AP will start responding to 10.0.0.1. Are you waiting this long?

The AP needs to go through its normal boot, self test, and then a spanning tree negotiation.

[enkrypt2000]

This whole thing doesn't sound right. I was learning towards your browers configuration. If you can Telnet to the AP from the computer but you can't ping the IP then you shouldn't be able to telnet then. I would throw a switch in the mix and see what happens.

[Philip D'Ath]

Your right.

If they can telnet but not ping then they have IP connectivity. Something is selectively dropping packets.

Any chance your running personal firewall software? XPSP2 Firewall? If so, try disabling the personal firewall temporarily.

[v8625]

Actually, my case is slightly different from the original poster - a guy in Germany who has a client in Singapore. He said he was able to telnet to AP, but was unable to use IPSU.

I was never able to telnet. That would definitely not make sense - if you can connect to something via TCP/UDP port 23, you should be able to ping that thing via ICMP.

Again, in summary, I can't ping it, I can't telnet to it, I can't get IPSU to recognize it, and it's not transmitting any info - arp -a returns nothing. Basically, it does not return a single packet no matter what you send to it.

My natural reaction is that it is the wrong address and/or wrong subnet, or some other settings that I missed. This is why I've eben checking and rechecking everything.

1. Expecting tat the AP's IP is 10.0.0.1 I set Ethernet adaptet on Windows machine to IP 10.0.0.2 in what I think is the appropriate subnet - 255.255.255.224 (I did try the default 255.0.0.0 as well). I leave the default gateway blank and leave the DNS entries blank.

2. I connect "crossover" CAT5 cable (tried straight one, too) from Ethernet port on Windows machine to Ethernet port on AP. Blinking amber lights on both ethernet ports show some activity during negotiation phase until the two fully connect and the lights go green showing 100mbps connection (I am talking about small lghts on ethernet port connectors themselves).

3. I reboot Windows machine just to make sure the new IP address sets in. Windows XP SP2 is disabled on this machine. Kerio sofware Firewall is disabled as well.

4. I press Mode button on AP and plug in the power while still holding Mode button, then release it whgen the Status light (the one in the middle) turns solid amber indicating the start of board initialization test. I wait until it goes through the whole routine - all three lights go green and so on - until the Ethernet LED on the unit itself (the first one from the top) goes solid green and Status light (the one in the middle) goes blinking green.

5. I open a command prompt in Windows. By this time the AP has been up for good 3-4 minutes. And here is what I get:

- arp -a gives me No ARP Entries Found

- telnet 10.0.0.1 gives me Cannot open connection to the host, on port 23: Connect failed

- ping 10.0.0.1 gives me Request timed out

- IPSU obviously tells me that it can't connect to it either - neither retrieve not set the IP.

I ordered AIR-CONCAB1200 cable, which I expect to get in a few days. If that does not help me, I would assume this thing to be damaged. The unit is brand new out of the box.

I mean, I would keep trying until I get this console cable, but I just don't know what else to try.

[kralle840]

Hi, this is the guy from Germany again.

I solved the problem. But not via IPSU,TCP/IP. I soldered a console-cable and connected to the AP via Hyper Terminal.

Then I found out the following:

My AP had no!! default IP-address! (Normally it has to be 10.0.0.1, but not on my AP, the value was zero). That was the reason why I couldn't connect to it. Then I configured the AP via HyperTerminal and could connect to it via TCP/IP.

I discussed that with a guy from cisco. I told him that my AP seems to have 'wrong' default values (at this time I have 3 more APs with the same 'problem').But he had no idea. In my opinion it looks like a 'bug' in the firmware.

Here is the output of 'show ip configuration brief' via console port:

ap>show ip interface brief

Interface IP-Address OK? Method Status Prot

ocol

BVI1 unassigned YES DHCP up up

Dot11Radio0 unassigned YES TFTP up up

FastEthernet0 unassigned YES other up down

The IP-address of BVI1 should be '10.0.0.1' and not 'unassigned'.

Hope that helps.

Ralph

[v8625]

Now that makes perfect sense. Somehow it even made me feel a little better - so I am not that dumb... The only remaining question is should I wait till I get that AIR-CONCAB1200 console cable (my soldering skills are probably not as sharp as Ralph's), or should I just return the darn thing to vendor. I mean, who knows what else can be screwed up with this thing besides buggy firmware.

Or could it be just the latest "feature" added by Cisco "for extra security?" How come there is no mention of that anywhere then?

Ralph, does everything else work fine?

Regards.