The bold words specify the necessary commands. The non-bold words specify the variable used for the example. When assigning an IP address to the switch, it is recommended to assign it to the VLAN. If you assign an IP address to an physical port or LAG, only a device connected to that port or LAG will be able to manage the switch.
The hostname command is optional when assigning an IP address. For initial configuation, you could simply use the following commands:
console(config)# interface vlan 1
console(config-if)# ip address dhcp
The 5324 can keep 2 different certificates. To generate a certificate and store it as number 1, you would use the following command:
If you did not remove the ip address configuration from the physical port before assigning it to the VLAN, this will cause a problem. A port that has been assigned an IP address will no longer participate in layer 2 functions.
To remove the possibility of any previous configurations causing problems, I would suggest the following:
Delete the startup config using the command "delete startup"
Reboot the switch using the "reload" command
Configure a local user called admin with password admin and level 15 privileges using the command "username admin password admin level 15"
Configure the ip address on VLAN 1 using the command "ip address dhcp"
The switch should have no problem pulling an ip address from the DHCP server.
console# con console(config)# username admin password admin level 15 console(config)# interface vlan 1 console(config-if)# ip address dhcp console(config-if)# ex console(config)# ex console# show ip interface
Gateway IP Address Type Activity status ----------------------- -------- -----------------------
IP Address I/F Type ----------------------- ---------------------- --------- 0.0.0.0/32 vlan 1 DHCP
console#
Still no joy. I have link and activity lights (blinking) on the port).
Also, how does a newly signed certificate file get onto the switch in order to be imported?
You have the necessary configuration on the switch to acquire an IP address via DHCP. Verify that the port to which the DHCP server is connected is up and forwarding and check the IP address again using the "show ip interface" command. If the switch is still not getting an IP address, there is something either blocking the requests or the DHCP server is not configured properly.
If the DHCP server is on the other side of a router, you need to configure the router to forward the requests to the DHCP server. Broadcasts do not cross a router by default. Once the router is configured, you would need to define a scope for this subnet on the DHCP server.
To import a certificate, you would manually enter the encrypted text created by the signed certificate.
In trying to sort out the exact issues, Ive physically connected the 5324 directly to a port on my netgear FVS318 router. The router is also my dhcp server. Nonetheless, I am unable to acquire an IP address (see below). I dont believe the router is blocking any DHCP requests since it has been issuing IP addresses happily to all the network users for some time now.
console# con console(config)# console(config)# console(config)# console(config)# interface vlan 1 console(config-if)# ip address dhcp console(config-if)# ex console(config)# ex console# show ip interface
Gateway IP Address Type Activity status ----------------------- -------- -----------------------
IP Address I/F Type ----------------------- ---------------------- --------- 0.0.0.0/32 vlan 1 DHCP
console#
So, for the time being, Im using a static IP because I cant spend more time on this. I would like to know wht the issue is nonetheless (if any).
So, any further ideas as to why I ccant get the switch to acquire its IP over DHCP? One thing I thought of was whether or not I should pre-allocate an Ip on the router using the switchs MAC address for the vlan 1. How do I find the MAC for this interface?
GregG1
2 Intern
•
812 Posts
0
November 12th, 2004 11:00
<ADMIN NOTE: Broken link has been removed from this post by Dell>
cvandusen
25 Posts
0
November 12th, 2004 13:00
Gateway IP Address Type Activity status
----------------------- -------- -----------------------
IP Address I/F Type
----------------------- ---------------------- ---------
0.0.0.0/32 vlan 1 DHCP
The IP is still invalid (0.0.0.0/32). Am I missing something?
GregG1
2 Intern
•
812 Posts
0
November 12th, 2004 14:00
cvandusen
25 Posts
0
November 12th, 2004 14:00
Here is what I tried:
delete startup
reload (deleting the flash file)
console> en
console# con
console(config)# username admin password admin level 15
console(config)# interface vlan 1
console(config-if)# ip address dhcp
console(config-if)# ex
console(config)# ex
console# show ip interface
Gateway IP Address Type Activity status
----------------------- -------- -----------------------
IP Address I/F Type
----------------------- ---------------------- ---------
0.0.0.0/32 vlan 1 DHCP
console#
Still no joy. I have link and activity lights (blinking) on the port).
Also, how does a newly signed certificate file get onto the switch in order to be imported?
Charlie
GregG1
2 Intern
•
812 Posts
0
November 12th, 2004 17:00
cvandusen
25 Posts
0
November 13th, 2004 08:00
Hi,
In trying to sort out the exact issues, Ive physically connected the 5324 directly to a port on my netgear FVS318 router. The router is also my dhcp server. Nonetheless, I am unable to acquire an IP address (see below). I dont believe the router is blocking any DHCP requests since it has been issuing IP addresses happily to all the network users for some time now.
console# con
console(config)#
console(config)#
console(config)#
console(config)# interface vlan 1
console(config-if)# ip address dhcp
console(config-if)# ex
console(config)# ex
console# show ip interface
Gateway IP Address Type Activity status
----------------------- -------- -----------------------
IP Address I/F Type
----------------------- ---------------------- ---------
0.0.0.0/32 vlan 1 DHCP
console#
So, for the time being, Im using a static IP because I cant spend more time on this. I would like to know wht the issue is nonetheless (if any).
So, any further ideas as to why I ccant get the switch to acquire its IP over DHCP? One thing I thought of was whether or not I should pre-allocate an Ip on the router using the switchs MAC address for the vlan 1. How do I find the MAC for this interface?
Thanks
Charlie