Our network is separated to several vlans by Cisco 6509. at first we faced problem on DHCP IP address getting during bootup after releasing IP. thanks to Steve the problem was solved using portfast command - refer to following attachment.
Now we still face further issue related to it: Don't release IP first but keep the original IP, then when the client is changed from vlan A to vlan B, they can not log on the network, should first release IP, then renew IP, then relogin to the domain. In addition if use winipcfg to renew IP before release, the system will hold. Re: if only change the port profile from vlan A to vlan B without disconnection of cable, and the system reboot (not turn off power and on), the logon can work, another IP is got - in any other case it failed if not release IP first.
It's confusing us, appreciate for help.
=== attachment for last issue solved ===
Our network is separated into several vlans by Cisco 6509. DHCP service is supported by one NT server in Vlan1. Now the client which connects to Vlan1 port can not get IP address after releasing IP using WINIPCFG, even rebooting. But when in windows98, use WINIPCFG to renew, the IP can be got.
For other clients which have not been connected to Vlans, they connect to the normal HUB which shared with the DHCP NT server. After releasing IP, they can get IP using rebooting.
Re: for other vlans which are different from Vlan1, the clients can not get IP after rebooting. But they can get IP through winipcfg renewing. (the other vlans have been configured to use DHCP IP POOL which is the function of cisco6509)
We are confused on it and the users will be impacted if put them to Vlans as they would be frustrated to use WINIPCFG during boot up of the system.
ssymonds - CISCO SYSTEMS , CCIE
Nov 12, 2001, 3:48am Pacific (1.)
it sounds like perhaps the DHCP requests timeout before the switch port is in an STP forwarding state.
Have you configured 'portfast' on user ports to speed-up STP process ?
Another option (depending on you sw version) is to configure 'set port host' which is a macro-command disabling certain parameters such as trunking/channelling and enabling portfast in effort to get a user port up and forwarding asap.
Important to note is that these commands must -only- be used on single *user* ports please see the following URL for more info:
Win9x DHCP client is a very manual process. It might be easier to teach your users to shut down before restarting on the new VLAN than using winipcfg. Win2k And XP handle this much better by considering each network disconnect as a (most-likely) release.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.