Sign in or 

| Started By | Thread Subject | Replies | Last Post | ||||
|---|---|---|---|---|---|---|---|
| nillsl | CLI PowerConnect... | 2 | Jun 23 2010, 11:43 AM EDT by nillsl | ||||
|
Thread started: Jun 23 2010, 10:43 AM EDT
Watch
Good day to everyone, im looking of CLI commands Manual, something like:
example: configure: this command gives you access to global cofiguration of the switch interface: this command gives access to configuration interfaces etc, etc...
out of
found this valuable.
Do you find this valuable?
Keyword tags:
CLI
iSCSI
POWERCONNECT
Show Last Reply
|
|||||||
| dunxd | Connecting the serial port | 7 | Mar 30 2010, 5:04 PM EDT by burtino | ||||
|
Thread started: Aug 27 2009, 11:19 AM EDT
Watch
I'm struggling to get connected using the RS-232 to USB cable supplied by Dell. I open up HyperTerminal - now which COM port do I use? None of them seem to work. So I can't connect to the switch via the serial port. My laptop has no serial port on it. Scratching my head because there is no documentation relating to this cable Dell supplied, but it isn't really plug and play...
Can anyone help me here?
Show Last Reply
|
|||||||
| aseniuk | Setting up 2 VLANs | 0 | Jan 25 2010, 9:47 AM EST by aseniuk | ||||
|
Thread started: Jan 25 2010, 9:47 AM EST
Watch
I really like to say that write up is quite good for us new to the iSCSI game.
I have 1x 5448 swtich that we would like to setup as the iSCSI (VLAN'd) and the rest of the switch to be used for network traffic for the servers we have. Is there any thing special I would need to change to get that going?
out of
found this valuable.
Do you find this valuable?
Keyword tags:
iSCSI VLAN
|
|||||||
| steve_o2 | iSCSI configuration | 2 | Nov 10 2009, 4:13 AM EST by DylanGoh | ||||
|
Thread started: Aug 27 2009, 10:14 PM EDT
Watch
Great write-up. My performance over two dedicated Intel NICs went from 22mb/sec to 73mb/sec after these changes.
I also will now setup a 4 port LAG between 2 5424 switches for redundant paths to my Equallogic PS5000. What performance is everyone else seeing over iSCSI?
Show Last Reply
|
|||||||
| holografique | need more details | 3 | Oct 29 2009, 8:30 PM EDT by nebdude | ||||
|
Thread started: Sep 9 2009, 2:54 PM EDT
Watch
this is a good start. but we need more details around:
- best practice for configuration 2x 5424 to act as a primary and secondary switch and the use of LAG or LACP groups (either via copper or fiber ports) - how to configure VLAN routing for when it comes time to have your iSCSI array replicate it's data to another site (subnet). - how to configure STP to ensure management uplinks from each switch back to a single core switch My typical configuration invovles creating the dedicated iSCSI VLAN on the core switch, then setting up an access port uplink on the primary and secondary 5424 on that iSCSI VLAN. I then use the other 3 fiber ports as the LAG/LACP group for the ISL trunk (per Equallogic Guidelines). This essentially gives me a dedicated iSCSI VLAN on the core and the iSCSI switches, and it's routable through the core to be able to route out to external sites for array replication. I can also access the array and other iSCSI devices management from your user networks for day-to-day management, email alerting, etc. etc. the problem I have is that if the uplink on the primary switch goes doen (or it fails) I lose complete management access to the secondary switch, even though it has it's own dedicated fiber uplink to the core on the iSCSI VLAN.
Show Last Reply
|
|||||||
| dunxd | no iscsi enable? | 1 | Sep 1 2009, 5:22 PM EDT by ChaseHansen | ||||
|
Thread started: Aug 28 2009, 7:37 AM EDT
Watch
Is this a good idea if there is any monitoring going on via the iscsi network? For example, I might be running snmp traffic, and accessing the switch web interface via the iscsi network. In my case I will also be running ESX servers on this network - ESX 3 requires that iscsi and management traffic are on the same network.
The reason I say this is because after putting in the settings you mention, I find the web interface is running extremely slowly - even timing out. I hadn't tried before configuring iscsi though.
Show Last Reply
|
|||||||
| dunxd | Configure Telnet | 0 | Aug 28 2009, 7:14 AM EDT by dunxd | ||||
|
Thread started: Aug 28 2009, 7:14 AM EDT
Watch
To get telnet working I entered the following commands otherwise I got the following error message when connecting via telnet:
bad/missing configuration, inaccessible server, user low privileges. Config as follows: cosole(config)# aaa authentication login default line console(config)# aaa authentication enable default line console(config)# line telnet console(config-line)# login authentication default console(config-line)# login enable default console(config-line)# password whatever Look under Starting and Configuring the Device in the User guide for more |
|||||||
| tonyhgras | iSCSI network configuration | 1 | Jun 29 2009, 2:44 PM EDT by SeanO'Brien | ||||
|
Thread started: Jun 23 2009, 1:40 PM EDT
Watch
Hi Jeff,
Are you considering that there's only one switch sitting between the server and the MD3000i? If that's true, how the configuration would change if there were two switches in two different networks connecting the servers to the storage array (eg: MD3000i, AX4-5i)? What about the two switches connected together to form a single network (LAGs between them, as some arrays require this setup)? And finally, I'd like to see an example of the configuration commands for a pair of switches stacked together for iSCSI traffic (eg: PowerConnect M6220, PowerConnect 6224) connected to teamed adapters on the servers (eg: ESX). Too much to ask? I'm sure a few DELL users will find it helpful, as there's not too much information about the optimal configuration for the iSCSI network using DELL switches. Thanks in advance, Tony
Show Last Reply
|
|||||||
