Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

AP 1310 stuck in bridge: mode. cant assign IP

I have a 1310

its in bridge: mode after i lost the password and deleted all files from it per some pw recovery link i saw.

i assigned an IP, SM, DR and the device isnt accessible to be pinged etc. Step 6 just times out.

(see https://supportforums.cisco.com/docs/DOC-8091)

Step 6 Enter the tar command to load and inflate the new image from your TFTP server. The command must include this information:

tar -xtract tftp://192.168.130.222/images/c350-k9w7-tar.122-13.JA1.tar flash:

the lights are red, yellow, red and orange (left to right top to bottom).

also when i do this i get that:

bridge: dir flash0

unable to stat flash0/: permission denied

9 REPLIES
Gold

Re: AP 1310 stuck in bridge: mode. cant assign IP

If you are getting permission denied to the flash it sounds like you need to initilize the flash.

ap:flash_init

After you init the flash then see if you can do a dir and see the flash.  You may need to init tftp too.

New Member

Re: AP 1310 stuck in bridge: mode. cant assign IP

hi Dan

i tried and its still the same but i see now different commands yield different results.

bridge: flash_init

Initializing F..The flash is aized.


bridge: dir


List of filesystems currently registered:


               flash[0]: (read-write)

              xmodem[1]: (read-only)

                null[2]: (read-write)

                td-only)



bridge: dir flash:

Directory of flash:/


3    -rwx  73                       env_vars


7739904 bytes available (1536 bytes used)


bridge: dir flash0

unable to stat flash0/: permission denied

my main problem still stands - i cant get the IP to "take", after setting the 3 values i cant ping the 1310.
i ran all init commands did a reset too.
the LED's changed. now i only have a green on the S.
which is better then what i had before...

Gold

Re: AP 1310 stuck in bridge: mode. cant assign IP

OK, so the flash would now be available to take the image.

Can you post the output of what you are typing to set the IP info?  The commands are case sensitive but should work.

New Member

Re: AP 1310 stuck in bridge: mode. cant assign IP

i thought this might be strange but there is no output...

i enter the commands and return and there is just a bridge: prompt on the following line:

bridge: set IP_ADDR 172.16.3.103


bridge: set NETMASK 255.255.248.0


bridge: set DEFAULT_ROUTER 172.16.3.18 (this is my PC with the TFTP server on it etc.)

Gold

Re: AP 1310 stuck in bridge: mode. cant assign IP

Those commands look right, did you try doing an ether_init?

New Member

Re: AP 1310 stuck in bridge: mode. cant assign IP

yes. i did all the inits the "?" displays

New Member

Re: AP 1310 stuck in bridge: mode. cant assign IP

i ran the etest series and i think theres a HW problem?

bridge:  etest 7

transmitting test, see if we can send packet



[Packet Transmit: port 0]

        sending 1200 bytes:


    0080 00a0 1032 0014 69f9 3584 1234 1235


    1236 1237 1238 1239 123a 123b 123c 123d



etest_sendpkt: ERROR: packet 1ecef08 sent failed

        etest_sendpkt() failed.

        sending 1200 bytes:


    0080 00a0 1032 0014 69f9 3584 04b0 1235


    1236 1237 1238 1239 123a 123b 123c 123d



etest_sendpkt: ERROR: packet 1ecef08 sent failed

        etest_sendpkt() failed.

-- MORE --

        sending 1200 bytes:


    0080 00a0 1032 0014 69f9 3584 04b0 1235


    1236 1237 1238 1239 123a 123b 123c 123d



etest_sendpkt: ERROR: packet 1ecef08 sent failed

        etest_sendpkt() failed.

        sending 1200 bytes:


    0080 00a0 1032 0014 69f9 3584 04b0 1235


    1236 1237 1238 1239 123a 123b 123c 123d



etest_sendpkt: ERROR: packet 1ecef08 sent failed

        etest_sendpkt() failed.

        sending 1200 bytes:


    0080 00a0 1032 0014 69f9 3584 04b0 1235


    1236 1237 1238 1239 123a 123b 123c 123d

-- MORE --



etest_sendpkt: ERROR: packet 1ecef08 sent failed

        etest_sendpkt() failed.

        sending 1200 bytes:


    0080 00a0 1032 0014 69f9 3584 04b0 1235


    1236 1237 1238 1239 123a 123b 123c 123d



etest_sendpkt: ERROR: packet 1ecef08 sent failed

        etest_sendpkt() failed.

        sending 1200 bytes:


    0080 00a0 1032 0014 69f9 3584 04b0 1235


    1236 1237 1238 1239 123a 123b 123c 123d



etest_sendpkt: ERROR: packet 1ecef08 sent failed

        etest_sendpkt() failed.

        sending 1200 bytes:

-- MORE --


    0080 00a0 1032 0014 69f9 3584 04b0 1235


    1236 1237 1238 1239 123a 123b 123c 123d



etest_sendpkt: ERROR: packet 1ecef08 sent failed

        etest_sendpkt() failed.

        sending 1200 bytes:


    0080 00a0 1032 0014 69f9 3584 04b0 1235


    1236 1237 1238 1239 123a 123b 123c 123d



etest_sendpkt: ERROR: packet 1ecef08 sent failed

        etest_sendpkt() failed.

        sending 1200 bytes:


    0080 00a0 1032 0014 69f9 3584 04b0 1235


    1236 1237 1238 1239 123a 123b 123c 123d


-- MORE --


etest_sendpkt: ERROR: packet 1ecef08 sent failed

        etest_sendpkt() failed.

transmit: completed.



                        RECEIVED                           SENT
                        ==========                         ======
good frame bytes :          0                                   0
good frames      :          0                                   0
broadcast frames :          0                                   0
multicast frames :          0                                   0
dropped frames   :          0                                   0
pause frames     :          0                                   0

error frames     :          0                                   0
CRC error frames :          0                                   0

overrun frames   :          0   underrun frames      :          0
runt frames      :          0   deferred frames      :          0
in range errors  :          0   single collisions    :          0
out range errors :          0   multiple collisions  :          0
align errors     :          0   late collisions      :          0
-- MORE --
short event      :          0   excessive collisions :          0
too long frames  :          0   carrier sense errors :          0
bad frames       :          0   bad previous frames  :          0
                                signal quality errors:          0

        Total Tx/Rx bytes:           0


other errors:
==================================
        Total MAL rx sys error          0
        Total MAL tx sys error          0
        Total MAL rx de error           0
        Total MAL tx de error           0
        Total MAL EMAC  error           0

New Member

Re: AP 1310 stuck in bridge: mode. cant assign IP

The issue I was having was due to the unpingable nature of the bridge: mode. I thought it wasn’t connecting. along with folder vs. file name error it made me think there was no connection.

I followed the procedure in a dry manner and was successful.

Thank you

New Member

Re: AP 1310 stuck in bridge: mode. cant assign IP

The issue I was having was due to the unpingable nature of the bridge: mode. I thought it wasn’t connecting. along with folder vs. file name error it made me think there was no connection.

I followed the procedure in a dry manner and was successful.

Thank you

1237
Views
4
Helpful
9
Replies