Unsolved
This post is more than 5 years old
4 Posts
0
44363
April 22nd, 2004 17:00
5224 vlan ip address failure
Hi there--
I am a longtime Cisco customer. I have 20 Cisco 3524XL's in the shop. I bought 4 Dell 5224 to start some Gigabit in the network.
Our management VLAN is vlan 2. We don't use Vlan 1 and don't like to because everyone and their brother seems to.
I logon the Dell CLI, I add vlan 2 to the vlan database (along with the other vlans we use)
conf
int vlan 2
ip address 172.16.20.9 255.255.255.0
I get this error "Failed to set the IP address mode as user define mode on VLAN 2"
We are a Cisco VoIP house too. A normal port on my Cisco 3524XL might look like this:
interface FastEthernet0/4
description Connection to IP Phone
switchport trunk encapsulation dot1q
switchport trunk native vlan 3 (our normal data vlan)
switchport mode trunk
switchport voice vlan 10 (our voip phone vlan)
So, that's what I want to replicate to my Dell 5224.
Thoughts on this? About to ship the Dell 5224 back. Please make me feel warm and fuzzy like I should with a $2,000 switch.
--DW
0 events found
GregG1
2 Intern
•
812 Posts
0
April 22nd, 2004 17:00
The 5224 is only capable of binding an IP address on one VLAN. When you assign the IP address to another VLAN, it removes it from VLAN 1. Before moving the IP address to a new VLAN, however, you must configure an untagged member on that VLAN (which makes sense because, without a member on VLAN 2, you would not be able to manage the switch).
I would suggest creating an untagged member on VLAN 2:
config
int eth 1/1
switchport allowed vlan add 2 untagged
switchport native vlan 2
switchport allowed vlan remove 1
Once this is done, you can move the IP address to VLAN 2.
As for the VoIP configuration, you would need to configure a port something like this:
interface ethernet 1/4
switchport allowed vlan add 3 untagged
switchport native vlan 3
switchport allowed vlan remove 1
switchport allowed vlan add 10 tagged
You cannot explicitly tag the native VLAN, as it is implied. If the trunking is not working properly, try adding the following commands to the interface:
switchport mode trunk
switchport acceptable-frame-types tagged
hunterdw
4 Posts
0
April 22nd, 2004 17:00
So, with my Cisco's... I have an IP address on VLAN2, but I have absolutely ZERO ports on VLAN2. Just the bound IP address. I can manage it just fine.
Are you saying that with the 5224, I cannot do that? I have to have at least one port on vlan2 in order to manage it? That's a "waste" of a port, or at least I'd have to trunk a port that I may not want to trunk in order to get what I have already with the Cisco.
GregG1
2 Intern
•
812 Posts
0
April 22nd, 2004 18:00
hunterdw
4 Posts
0
April 22nd, 2004 20:00
Cisco config - this works just fine with our Cisco 7940 phones
interface FastEthernet0/4
description Connection to IP Phone
switchport trunk encapsulation dot1q
switchport trunk native vlan 3
switchport mode trunk
switchport voice vlan 10
no ip address
spanning-tree portfast
!
Dell config - This does not work. Phone stuck at "Configuring IP'
interface ethernet 1/3
switchport allowed vlan add 3 untagged
switchport native vlan 3
switchport allowed vlan remove 1
switchport acceptable-frame-types tagged
switchport mode trunk
switchport allowed vlan add 3,10 tagged
!
Thoughts?
My trunk port on Cisco...
interface FastEthernet0/22
switchport trunk encapsulation dot1q
switchport trunk native vlan 999
switchport mode trunk
no ip address
!
My trunk port on Dell...
interface ethernet 1/24
switchport allowed vlan add 999 untagged
switchport native vlan 999
switchport allowed vlan remove 1
switchport acceptable-frame-types tagged
switchport mode trunk
switchport allowed vlan add 2-3,10,999 tagged
Interestingly enough, I can get an IP address for my laptop through the Phone... so, the phone talks to the network, but that ip is on vlan 3, our data network (192.168.1.x) The phone needs to get it's IP through the voice vlan, vlan 10 (172.16.10.x).
hunterdw
4 Posts
0
April 23rd, 2004 19:00
Problem resolved.
Both the Cisco and Dell switches were configured correctly.
The real problem was the Cisco Discovery Protocol (CDP) that the phone uses.. I had to manually update the phones to look to vlan 10 (my voice vlan) for the admin vlan id. That changed the operational vlan id. 10-15 seconds later I'm back up and running.
Thank you for your help.
--DW