I have a network which has recently been subject to a power failure.
Upon re-powering switch (3560G), ap (1252), router (netgear), and servers (Windows 2k3, 2k8), I am unable to get a DHCP ip address on any except the native vlan (wired and wireless). I am able to assign an ip address manually in both wired and wireless modes on my test laptop, but if the laptop is set to retrieve an address using DHCP, it times out and gets an address in 169.254.x.x (APIPA).
The 3560G switch has 3 vlans:
The Vlans as defined on the switch include the command ip helper-address (see below):
interface Vlan1 ip address 192.168.5.16 255.255.255.0 ntp broadcast ! interface Vlan15 ip address 192.168.15.2 255.255.255.0 ip helper-address 192.168.5.5 ntp broadcast ! interface Vlan25 ip address 192.168.25.2 255.255.255.0 ip helper-address 192.168.5.5 ntp broadcast ! ip default-gateway 192.168.5.1 ip classless ip route 0.0.0.0 0.0.0.0 192.168.5.1
The server at 192.168.5.5 has multiple DHCP scopes defined (one for each vlan). The default gateway at 192.168.5.1 is a netgear router
If you do not like CLI, you can use the Cisco Network Assistant - this gui based tool is awesome.
Is the problem that the switch is not forwarding the bcast packets or that the DHCP server does not know how to respond? It might be helpful if you tie this to an individual port config, vlan, server, etc ...
Sx550X, Sx350X, Sx250: PSE will Supply Power to Catalyst PSE Ports
May 31, 2016
June 5, 2017
Configure Remote Network Monitoring (RMON) Events Control Settings on a Switch through the Command Line Interface (CLI)
Remote Network Monitoring (RMON) was developed by the Internet Engineering Task Force (IETF) to support...