01-03-2017 01:16 PM
Hello all;
I have an Access Point enginius 2610, connected directly to cisco 877 router Port F2. Seems that the router isn't recognizing the mac of the Access Point, and is always putting the port in down state.
Access point:
IP: 10.0.0.2 Mac:0002.6f57.8e14
Here is some commands:
sh arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.0.0.1 - 0015.6388.39d3 ARPA Vlan2
Internet 10.0.0.2 0 Incomplete ARPA
Internet 10.0.0.3 10 000e.2ece.63c9 ARPA Vlan2
Internet 192.168.1.1 - 0015.6388.39d3 ARPA Vlan1
Internet 192.168.1.68 1 e89a.8ff6.e262 ARPA Vlan1
Internet 192.168.1.253 3 0021.918d.7d6b ARPA Vlan1
Internet 192.168.1.254 6 9c97.268e.ed14 ARPA Vlan1
sh ip int brief
Interface IP-Address OK? Method Status Protocol
ATM0 unassigned YES NVRAM administratively down down
FastEthernet0 unassigned YES unset up up
FastEthernet1 unassigned YES unset up up
FastEthernet2 unassigned YES unset down down
FastEthernet3 unassigned YES unset up up
NVI0 unassigned YES unset administratively down down
Vlan1 192.168.1.1 YES NVRAM up up
Vlan2 10.0.0.1 YES NVRAM up up
term mon
*Jul 7 03:57:57.027: %LINK-3-UPDOWN: Interface FastEthernet2, changed state to down
*Jul 7 03:58:00.140: %LINK-3-UPDOWN: Interface FastEthernet2, changed state to down
*Jul 7 03:58:06.577: %LINK-3-UPDOWN: Interface FastEthernet2, changed state to down
*Jul 7 03:58:11.002: %LINK-3-UPDOWN: Interface FastEthernet2, changed state to down
*Jul 7 03:58:13.487: %LINK-3-UPDOWN: Interface FastEthernet2, changed state to down
*Jul 7 03:58:19.620: %LINK-3-UPDOWN: Interface FastEthernet2, changed state to down
*Jul 7 03:58:22.569: %LINK-3-UPDOWN: Interface FastEthernet2, changed state to down
How can i solve this?
regards;
01-05-2017 03:45 AM
- Besides 'term mon' could you also have a look at the complete logs of the router as in
# show loggging
M.
01-07-2017 10:31 AM
sh logging
Syslog logging: enabled (0 messages dropped, 2 messages rate-limited,
0 flushes, 0 overruns, xml disabled, filtering disabled)
No Active Message Discriminator.
No Inactive Message Discriminator.
Console logging: level debugging, 108 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: disabled, xml disabled,
filtering disabled
Logging Exception size (4096 bytes)
Count and timestamp logging messages: disabled
Persistent logging: disabled
No active filter modules.
ESM: 0 messages dropped
Trap logging: level informational, 108 message lines logged
lcastro#sh arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.0.0.1 - 0015.6388.39d3 ARPA Vlan2
Internet 10.0.0.2 0 Incomplete ARPA
Internet 10.0.0.4 0 Incomplete ARPA
Internet 10.0.0.12 0 e0ca.9470.d200 ARPA Vlan2
Internet 10.0.0.14 1 b452.7e94.3baf ARPA Vlan2
Internet 192.168.1.1 - 0015.6388.39d3 ARPA Vlan1
Internet 192.168.1.254 1 9c97.268e.ed14 ARPA Vlan1
sh ip int brief
Interface IP-Address OK? Method Status Protocol
ATM0 unassigned YES NVRAM administratively down down
FastEthernet0 unassigned YES unset up up
FastEthernet1 unassigned YES unset up up
FastEthernet2 unassigned YES unset up up
FastEthernet3 unassigned YES unset up up
NVI0 unassigned YES unset administratively down down
Virtual-Access1 unassigned YES unset down down
Virtual-Template1 192.168.1.1 YES TFTP down down
Vlan1 192.168.1.1 YES NVRAM up up
Vlan2 10.0.0.1 YES NVRAM up up
01-07-2017 11:16 AM
The original post had this line
FastEthernet2 unassigned YES unset down down
If FastEth2 is down then that explains why the router is not recognizing the mac of the access point.
The more recent post has this line
FastEthernet2 unassigned YES unset up up
If FastEth2 is now up then perhaps the router now recognizes the connection of the access point? Other than show arp how are you checking for the connection of the access point?
Would you post the configuration of interface FastEth2?
HTH
Rick
01-08-2017 09:45 AM
Helo;
Thanks a lot Richard. I have solved the problem, adding
duplex full
speed 10
In port configuration.
Regards
01-08-2017 11:51 AM
Thank you for posting back to the forum to let us know that you solved the problem by changing port parameters for speed and duplex. I am glad that you were able to get the problem worked out.
HTH
Rick
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide