1. How are you setting up the switch to make 300 your management VLAN? Are you using this command?
The following example sets VLAN 300 as management VLAN
console(config)#ip address vlan 300
2. General Links consist of a combination of VLAN Trunk and Access Links.
General Links can have both tagged and untagged frames, However, all frames sent to a specific VLAN must be tagged. All untagged frames are sent to the native VLAN. The native VLAN still applies to the General LINK. While it is possible to have multiple untagged vlans on a General link, you can only have ONE (1) PVID. The PVID represents the native VLAN. While untagged traffic may be sent via several untagged VLANs, returning untagged traffic will only be received by the PVID and therefore will NOT be forwarded to a specific VLAN. General links are mostly used today for legacy equipment. However, on the PowerConnect 62xx series switches, you must use General mode if you want to allow management traffic onto the switch over the PVID. If you use Trunk mode, you will not have the default VLAN on those ports. The ports will only allow tagged traffic.
Here are the commands allow multiple VLANs across port 1/g48
console# configure
console(config)# interface ethernet 1/g48
console(config-if)# switchport mode general
console(config-if)# switchport general allowed vlan add 400 tagged
console(config-if)# switchport general allowed vlan add 401 tagged
console(config-if)# end
I see you have general mode configured on all the interfaces. Typically you would configure access ports where you have a workstation or VLAN unaware device. The access port tags the traffic.
Access Links connect VLAN unaware devices to the port of a VLAN-aware switch. All frames on access links are untagged. The VLAN switch adds tags to received frames, and removes tags when transmitting frames. End users and VLAN-unaware workstations commonly reside on access links. By Default all ports are in ACCESS mode assigned to the default VLAN (VLAN 1). Ports set to Access mode belong to one VLAN only.
Per your suggestions, I have entered the new programming to the switch. However, it got worst!
VLANS 30,31,40, and 41 are just to keep a certain traffic in the switch. I do not want these vlans to be able to communicate outside of the switch.
However, VLANs 300, 400, and 401 needs to communicate to other similar vlans. VLAN 300 is used on our network to manage all network switches. VLANS 400 and 401 are for workstations, etc.
Below, I have included a current config with the changes you have suggested on the previous post.
Also since VLAN 300 is your native you probably want to add it as untagged on the fiber port 48.
console(config)# interface ethernet xxx
console(config-if)# switchport mode general
console(config-if)# switchport general allowed vlan add 300 untagged
You can run a specific command on port 48 also to exclude VLANs 30,31,40, and 41 like this.
console(config-if)# switchport general allowed vlan remove 30
console(config-if)# switchport general allowed vlan remove 31
console(config-if)# switchport general allowed vlan remove 40
console(config-if)# switchport general allowed vlan remove 41
Are you wanting VLAN 30,31,40, and 41 to be able to communicate with each other on the specific switch? If not then you would not need routing enabled for those VLANs.
What device is connected on the other end of your fiber port 48? You will need similar commands setting up a trunk/general mode allowing the same VLANs.
Ok, I made some progress. The two most important VLANs 400 and 401 are working. However, no matter what I have tried, VLAN 300 does not wants to be the default one which it would be the Management VLAN.
I even tried entering the command on port 48 switchport general allowed vlan add 300 untagged, and it did not work. Then, I used another command switchport general allowed vlan add 300 tagged, and it did not work. But, as soon as I entered the command ip address vlan 1, the ip address to manage the switch started to work.
I noticed on the switch configuration it continues to show VLAN 1 as the default VLAN. Even if I have made ip address VLAN 300, the switch does not seem to believe that VLAN 300 is the management VLAN.
How can I convince the switch to change the default VLAN from 1 to 300?
On a side note, I have the two switches 6248 on stack mode. I am not sure if the cables are setup correctly. Right at the moment, the cables goes from the back port No 1 to second switch port No 1, and the same thing applies to port No 2 for both switches. is this a correct configuration, and do I have to do any additional steps in the software part?
For some reason, if I have a computer connected on switch number 2, the computer cannnot talk on the network. But, if the computer is connected to switch number 1, then everything works fine.
You would want a stacking cable connecting from XG1 port of switch 1 to XG2 port on switch 2. Then the second cable would connect from XG1 port of switch 2 to XG2 port of switch 1. The would create and "X" as they crossover each other.
ok, looking at the picture you have provided, and comparing to what I have done, I have two 6248 switches. On the first switch, bay 1 should be connected to bay 2 on the second switch. Then, on the second switch I should just leave alone.
At the time of buying the two switches and the stack modules, two cables were provided. I was under the impression that I had to use both cables.
You can stack up to 12 PowerConnect 6224 and/or 6248 switches, supporting up to 576 front panel ports. Create a stack by connecting adjacent units using the stacking ports on the left side of the switch rear.
See Figure 4-13.
1. Connect one of the short stacking cables into either of the stacking ports of the top switch and the switch directly below it. Install a separately purchased stacking module in rear "Bay 1" of each of the switches in the stack.
2. For each switch in the stack, connect one of the short stacking cables from stacking port one on the switch to stacking port two on the next switch.
3. If necessary, use a separately purchased, long (3 meter) stacking cable to connect the switches. Repeat this process until all of the devices are connected.
4. Use the remaining stacking cable to connect the remaining free ports, one each on the top and bottom switches.
If you are using a stacking port module in “Bay 1” on both switches then no further software changes are needed. Stacking is discussed starting on page 62 of the User Guide.
<ADMIN NOTE: Broken link has been removed from this post by Dell>
As far my other vlans, vlan 30, and 31, I added some ip addresses to handle local switch network routing. But, I can't seem to ping the address from the switch to the VLANs ip addresses.
You might take a look at the routing table. Make sure the subnets are listed as connected. Make sure you have routing enabled globally and on the specific VLAN.
console# show ip route
Can you ping the VLAN ip address from a PC connected to a port that is configured with switchport access. Don't forget the default gateway of the PC would be the IP address configured on the VLAN interface.
DELL-Willy M
802 Posts
0
September 20th, 2012 16:00
1. How are you setting up the switch to make 300 your management VLAN? Are you using this command?
The following example sets VLAN 300 as management VLAN
console(config)#ip address vlan 300
2. General Links consist of a combination of VLAN Trunk and Access Links.
General Links can have both tagged and untagged frames, However, all frames sent to a specific VLAN must be tagged. All untagged frames are sent to the native VLAN. The native VLAN still applies to the General LINK. While it is possible to have multiple untagged vlans on a General link, you can only have ONE (1) PVID. The PVID represents the native VLAN. While untagged traffic may be sent via several untagged VLANs, returning untagged traffic will only be received by the PVID and therefore will NOT be forwarded to a specific VLAN. General links are mostly used today for legacy equipment. However, on the PowerConnect 62xx series switches, you must use General mode if you want to allow management traffic onto the switch over the PVID. If you use Trunk mode, you will not have the default VLAN on those ports. The ports will only allow tagged traffic.
Here are the commands allow multiple VLANs across port 1/g48
console# configure
console(config)# interface ethernet 1/g48
console(config-if)# switchport mode general
console(config-if)# switchport general allowed vlan add 400 tagged
console(config-if)# switchport general allowed vlan add 401 tagged
console(config-if)# end
I see you have general mode configured on all the interfaces. Typically you would configure access ports where you have a workstation or VLAN unaware device. The access port tags the traffic.
Access Links connect VLAN unaware devices to the port of a VLAN-aware switch. All frames on access links are untagged. The VLAN switch adds tags to received frames, and removes tags when transmitting frames. End users and VLAN-unaware workstations commonly reside on access links. By Default all ports are in ACCESS mode assigned to the default VLAN (VLAN 1). Ports set to Access mode belong to one VLAN only.
console# configure
console(config)# interface ethernet xxx
console(config-if)# switchport mode access
console(config-if)# switchport access vlan xxx
console(config-if)# end
Hope this helps,
Keep us updated if you can.
lions1855
11 Posts
0
September 21st, 2012 06:00
Per your suggestions, I have entered the new programming to the switch. However, it got worst!
VLANS 30,31,40, and 41 are just to keep a certain traffic in the switch. I do not want these vlans to be able to communicate outside of the switch.
However, VLANs 300, 400, and 401 needs to communicate to other similar vlans. VLAN 300 is used on our network to manage all network switches. VLANS 400 and 401 are for workstations, etc.
Below, I have included a current config with the changes you have suggested on the previous post.
!Current Configuration:
!System Description "PowerConnect 6248, 3.3.1.10, VxWorks 6.5"
!System Software Version 3.3.1.10
!Cut-through mode is configured as disabled
!
configure
vlan database
vlan 30-31,40-41,300,400-401
vlan routing 30 1
vlan routing 31 2
vlan routing 40 3
vlan routing 41 4
exit
stack
member 1 2
member 2 2
exit
ip address 162.31.13.252 255.255.255.0
ip default-gateway 162.31.13.1
ip address vlan 300
interface vlan 30
routing
ip address 172.17.30.1 255.255.255.0
exit
interface vlan 31
routing
ip address 172.17.31.1 255.255.255.0
exit
interface vlan 40
routing
ip address 172.17.40.1 255.255.255.0
exit
interface vlan 41
routing
ip address 172.17.41.1 255.255.255.0
exit
!
interface ethernet 1/g1
switchport access vlan 30
exit
!
interface ethernet 1/g2
switchport access vlan 30
exit
!
interface ethernet 1/g3
switchport access vlan 30
exit
!
interface ethernet 1/g4
switchport access vlan 30
exit
!
interface ethernet 1/g5
switchport access vlan 30
exit
!
interface ethernet 1/g6
switchport access vlan 30
exit
!
interface ethernet 1/g7
switchport access vlan 31
exit
!
interface ethernet 1/g8
switchport access vlan 31
exit
!
interface ethernet 1/g9
switchport access vlan 31
exit
!
interface ethernet 1/g10
switchport access vlan 31
exit
!
interface ethernet 1/g11
switchport access vlan 31
exit
!
interface ethernet 1/g12
switchport access vlan 31
exit
!
interface ethernet 1/g13
switchport access vlan 40
exit
!
interface ethernet 1/g14
switchport access vlan 40
exit
!
interface ethernet 1/g15
switchport access vlan 40
exit
!
interface ethernet 1/g16
switchport access vlan 40
exit
!
interface ethernet 1/g17
switchport access vlan 41
exit
!
interface ethernet 1/g18
switchport access vlan 41
exit
!
interface ethernet 1/g19
switchport access vlan 41
exit
!
interface ethernet 1/g20
switchport access vlan 41
exit
!
interface ethernet 1/g21
switchport access vlan 401
exit
!
interface ethernet 1/g22
switchport access vlan 401
exit
!
interface ethernet 1/g23
switchport access vlan 401
exit
!
interface ethernet 1/g24
switchport access vlan 401
exit
!
interface ethernet 1/g25
switchport access vlan 400
exit
!
interface ethernet 1/g26
switchport access vlan 400
exit
!
interface ethernet 1/g27
switchport access vlan 400
exit
!
interface ethernet 1/g28
switchport access vlan 400
exit
!
interface ethernet 1/g48
switchport mode general
switchport general allowed vlan add 300,400-401 tagged
exit
exit
lions1855
11 Posts
0
September 21st, 2012 07:00
By the way, I forgot to mentioned the switch is using the fiber port 48 as the uplink communication channel.
DELL-Willy M
802 Posts
1
September 21st, 2012 08:00
I would recommend updating the firmware to the latest version. The current version 3.3.4.1 is available here for download.
www.dell.com/.../powerconnect-6248
Also since VLAN 300 is your native you probably want to add it as untagged on the fiber port 48.
console(config)# interface ethernet xxx
console(config-if)# switchport mode general
console(config-if)# switchport general allowed vlan add 300 untagged
You can run a specific command on port 48 also to exclude VLANs 30,31,40, and 41 like this.
console(config-if)# switchport general allowed vlan remove 30
console(config-if)# switchport general allowed vlan remove 31
console(config-if)# switchport general allowed vlan remove 40
console(config-if)# switchport general allowed vlan remove 41
Are you wanting VLAN 30,31,40, and 41 to be able to communicate with each other on the specific switch? If not then you would not need routing enabled for those VLANs.
What device is connected on the other end of your fiber port 48? You will need similar commands setting up a trunk/general mode allowing the same VLANs.
DELL-Willy M
802 Posts
1
September 21st, 2012 10:00
Once you run this command.
console(config)#ip address vlan 300
then you need to enter VLAN interface 300 to set the ip of VLAN 300
console(config)#interface vlan 300
console(config-if-vlan300)#ip address 162.31.13.252 255.255.255.0
lions1855
11 Posts
0
September 21st, 2012 10:00
Ok, I made some progress. The two most important VLANs 400 and 401 are working. However, no matter what I have tried, VLAN 300 does not wants to be the default one which it would be the Management VLAN.
I even tried entering the command on port 48 switchport general allowed vlan add 300 untagged, and it did not work. Then, I used another command switchport general allowed vlan add 300 tagged, and it did not work. But, as soon as I entered the command ip address vlan 1, the ip address to manage the switch started to work.
I noticed on the switch configuration it continues to show VLAN 1 as the default VLAN. Even if I have made ip address VLAN 300, the switch does not seem to believe that VLAN 300 is the management VLAN.
How can I convince the switch to change the default VLAN from 1 to 300?
Thanks
User:admin
Password:********
console>en
console#show run
!Current Configuration:
!System Description "PowerConnect 6248, 3.3.1.10, VxWorks 6.5"
!System Software Version 3.3.1.10
!Cut-through mode is configured as disabled
!
configure
vlan database
vlan 30-31,40-41,300,400-401
vlan routing 30 1
vlan routing 31 2
vlan routing 40 3
vlan routing 41 4
exit
stack
member 1 2
member 2 2
exit
ip address 162.31.13.252 255.255.255.0
ip default-gateway 162.31.13.1
interface vlan 30
routing
exit
interface vlan 31
routing
exit
interface vlan 40
routing
exit
interface vlan 41
routing
exit
interface vlan 400
name "Academic"
exit
!
interface ethernet 1/g1
switchport access vlan 30
exit
!
interface ethernet 1/g2
switchport access vlan 30
exit
!
interface ethernet 1/g3
switchport access vlan 30
exit
!
interface ethernet 1/g4
switchport access vlan 30
exit
!
interface ethernet 1/g5
switchport access vlan 30
exit
!
interface ethernet 1/g6
switchport access vlan 30
exit
!
interface ethernet 1/g7
switchport access vlan 31
exit
!
interface ethernet 1/g8
switchport access vlan 31
exit
!
interface ethernet 1/g9
switchport access vlan 31
exit
!
interface ethernet 1/g10
switchport access vlan 31
exit
!
interface ethernet 1/g11
switchport access vlan 31
exit
!
interface ethernet 1/g12
switchport access vlan 31
exit
!
interface ethernet 1/g13
switchport access vlan 40
exit
!
interface ethernet 1/g14
switchport access vlan 40
exit
!
interface ethernet 1/g15
switchport access vlan 40
exit
!
interface ethernet 1/g16
switchport access vlan 40
exit
!
interface ethernet 1/g17
switchport access vlan 41
exit
!
interface ethernet 1/g18
switchport access vlan 41
exit
!
interface ethernet 1/g19
switchport access vlan 41
exit
!
interface ethernet 1/g20
switchport access vlan 41
exit
!
interface ethernet 1/g21
switchport access vlan 401
exit
!
interface ethernet 1/g22
switchport access vlan 401
exit
!
interface ethernet 1/g23
switchport access vlan 401
exit
!
interface ethernet 1/g24
switchport access vlan 401
exit
!
interface ethernet 1/g25
switchport access vlan 400
exit
!
interface ethernet 1/g26
switchport access vlan 400
exit
!
interface ethernet 1/g27
switchport access vlan 400
exit
!
interface ethernet 1/g28
switchport access vlan 400
exit
!
interface ethernet 1/g48
switchport mode general
switchport general allowed vlan add 300,400-401 tagged
exit
exit
console#
lions1855
11 Posts
0
September 21st, 2012 12:00
On a side note, I have the two switches 6248 on stack mode. I am not sure if the cables are setup correctly. Right at the moment, the cables goes from the back port No 1 to second switch port No 1, and the same thing applies to port No 2 for both switches. is this a correct configuration, and do I have to do any additional steps in the software part?
For some reason, if I have a computer connected on switch number 2, the computer cannnot talk on the network. But, if the computer is connected to switch number 1, then everything works fine.
Why?
DELL-Willy M
802 Posts
1
September 21st, 2012 12:00
You would want a stacking cable connecting from XG1 port of switch 1 to XG2 port on switch 2. Then the second cable would connect from XG1 port of switch 2 to XG2 port of switch 1. The would create and "X" as they crossover each other.
lions1855
11 Posts
0
September 21st, 2012 12:00
ok, looking at the picture you have provided, and comparing to what I have done, I have two 6248 switches. On the first switch, bay 1 should be connected to bay 2 on the second switch. Then, on the second switch I should just leave alone.
At the time of buying the two switches and the stack modules, two cables were provided. I was under the impression that I had to use both cables.
DELL-Willy M
802 Posts
1
September 21st, 2012 12:00
Stacking
You can stack up to 12 PowerConnect 6224 and/or 6248 switches, supporting up to 576 front panel ports. Create a stack by connecting adjacent units using the stacking ports on the left side of the switch rear.
See Figure 4-13.
1. Connect one of the short stacking cables into either of the stacking ports of the top switch and the switch directly below it. Install a separately purchased stacking module in rear "Bay 1" of each of the switches in the stack.
2. For each switch in the stack, connect one of the short stacking cables from stacking port one on the switch to stacking port two on the next switch.
3. If necessary, use a separately purchased, long (3 meter) stacking cable to connect the switches. Repeat this process until all of the devices are connected.
4. Use the remaining stacking cable to connect the remaining free ports, one each on the top and bottom switches.
If you are using a stacking port module in “Bay 1” on both switches then no further software changes are needed. Stacking is discussed starting on page 62 of the User Guide.
<ADMIN NOTE: Broken link has been removed from this post by Dell>
lions1855
11 Posts
0
September 21st, 2012 13:00
One of the switches is showing "2/8" and the other switch is showing "1/8". How do I know which one is the master and so forth?
DELL-Willy M
802 Posts
0
September 21st, 2012 13:00
Are the Stacking LEDs showing the proper designation "Master" "2/8"?
lions1855
11 Posts
0
September 21st, 2012 13:00
Ok,
I have formed an 'X' shape with the cables. Do I have to configure something on the software side to get it working?
lions1855
11 Posts
0
September 21st, 2012 14:00
It seems that is working without an issue.
As far my other vlans, vlan 30, and 31, I added some ip addresses to handle local switch network routing. But, I can't seem to ping the address from the switch to the VLANs ip addresses.
DELL-Willy M
802 Posts
1
September 21st, 2012 16:00
You might take a look at the routing table. Make sure the subnets are listed as connected. Make sure you have routing enabled globally and on the specific VLAN.
console# show ip route
Can you ping the VLAN ip address from a PC connected to a port that is configured with switchport access. Don't forget the default gateway of the PC would be the IP address configured on the VLAN interface.