Pentium3NL

updated

13 years ago

P

Pentium3NL

11 Posts

0

82094

April 7th, 2014 05:00

FW 7.0.2 - Synrep Issues and Errors

Dear Everyone,

After our upgrade from v6.0.4 to v7.0.2, we are getting strange errors by email and logging. These errors started after the upgrade.

Strangest thing is that when we are receiving an error and are logging in, the error is gone already.

Severity  Date and Time      Member       ID              Message                                                                                                                                                                                                                                                                  --------  -----------------  -----------  --------------  -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------   Error    7-4-2014 11:44:20  san4-shared  7.4.3 | 7.4.23  iSCSI login to target '10.x.x.x:3260, iqn.2001-05.com.equallogic:xxxx'from initiator '10.x.x.x:55898, eqlinitiatorsyncrep' failed for the following reason: | Initiator disconnected from target during login. 

 

 

Why is this error coming up so often since the upgrade? Is this a Hardware or Software failure? The reason i'm asking is that our other clusters are not showing this error.

With regards,

Andreas van der Linden.

  • Pentium3NL

    11 Posts

    2249

    0

    Posted April 23rd, 2014 06:00

    Dear Everyone,

    Because of your discussion I have taken over the function of our network engineer and did some exploring myself. We don't know why, but someone enabled spanning tree on these interfaces. We are planning a maintenance window shortly to turn this off.

    Thank you very much for your suggestions.

  • Pentium3NL

    11 Posts

    1334

    0

    Posted April 8th, 2014 01:00

    The connection between the SAN's is configured as followed:

    - Single Cisco Redundant stacked switch between the SAN's

    - MTU 9000

    - 1-4 Gb/s

    Type: 2x PS4000 and 2x PS6100 where the sync rep is only on the same type (4000 -> 4000 and 6100 -> 6100)

  • Pentium3NL

    11 Posts

    1334

    0

    Posted April 8th, 2014 13:00

    depending on the type of equallogic, it has 2x1Gb/s interfaces or 4x1Gb/s interfaces to the switch.

  • Pentium3NL

    11 Posts

    1334

    0

    Posted April 9th, 2014 01:00

    Cisco C3750E

  • Pentium3NL

    11 Posts

    1334

    0

    Posted April 14th, 2014 06:00

    no one?

  • joergriether

    127 Posts

    1334

    0

    Posted April 18th, 2014 05:00

    Please check if the upgrade to v7 somehow enabled DCB if it was disabled before the upgrade. If you find it enabled, please diable it (only possible via CLI, not via GUI with v7).

    Let us know if that helped.

    Best regards, Joerg

  • joergriether

    127 Posts

    1227

    0

    Posted April 19th, 2014 04:00

    Don: Please clarify.

    Many switches will turn off any flow control if you disable dcb on the switch side. Thus - please explain.

    Why am i not to disable DCB on the array side, ever? That does not make any sense to me, because a) it was possible for a long time from within the gui and b) maybe you don´t want to disable it on the switch side for several reasons but you need to disable it on the array because the initiator don´t supports it. Also, i often spoke to EQL techs who told me where to disable it on the cli side for exatly that reason. Also, it is clearly explained in the cli guide. So i am concerned now: Is there *anything* we should know about that and why do you explicitly mention it?

    I had a coincidental chat about that with EQL techs in frankfurt/germany last week during the dell enterprise forum and it was exactly about dcb and how dcb is not widely supported by initiators, especially s/w initiators and how to disable it on the array level.

    Don maybe you remember this we had a conversation in this forum about a year ago on exactly the same topic - but you never told me why it is so important to you to explicitly not disable it an the array level?

    I really want to know the reason because if there is something important i should know about that i´d like to understand that and disable it on the switch side instead of the array side. But as far as i know and also as far as my friends and colleagues in frankfurt are telling me, disabling dcb on the array side does no harm at all. Please clarify.

    Best regards,

    Joerg

  • joergriether

    127 Posts

    1227

    0

    Posted April 22nd, 2014 02:00

    Hi Don,

    OK, thanks. Could you talk to engineering for the reason for telling you this? Please do me the favor because the enginners i myself talked to, told me otherwise.

    Second, please give exact advise how to disable DCB on a DELL 8164 (now N4064) so that it´s really disabled while in parallel keep link layer flow control *fully* intact. Because i don´t know how to realize that.

    Best regards,

    Joerg

  • joergriether

    127 Posts

    1227

    0

    Posted April 23rd, 2014 14:00

    @Pentium3nl:

    I don´t think STP/RSTP is your *real* problem. If it helps to disable STP on these ports you are either confronted with a) many global (r)stp recalculations or b) a flappy connection which goes online and offline from time to time. Both things are not good and the real reason should be your target. So i suggest to keep looking for possible causers of a) or b).

    @ Don:

    Thanks, Don.

    I still see absolutely no advantage in turning DCB globally off on switch side. On the array, however, i can do it "on the fly" without the slightest kind of disruption. Again, i am wondering why you removed it from the GUI with V7. I would change that back if i could. But then again, sadly i can´t ;-) I can only suggest.

    Best regards,

    Joerg

    PS by the way, am i the only one who finds these lines at least a little bit scary ->

    ---- from the official docs 8164 switch side ----

    4 Reverting from DCB to non-DCB configuration (Optional)

    One method to revert from a DCB configured switch to a non-DCB configured switch is to delete the current configuration (startup-config) and follow the steps in Section 2. If deleting the current configuration is not an option, then use the following procedure to unconfigure DCB and enable standard flow control.

    Note: This is a disruptive operation that requires down time. The arrays will temporarily lose communication with each other. Power off all arrays and hosts connected to the SAN before proceeding with these steps. 

    Disable DCB and the DCB policies console#configure

    console(config)#no dcb enable
    console(config)# no traffic-class-group weight
    console(config)#no classofservice dot1p-mapping
    console(config)#no classofservice traffic-class-group
    console(config)#no iscsi cos
    console(config)#interface range tengigabitethernet all
    console(config-if)#datacenter-bridging
    console(config-if-dcb)#no priority-flow-control mode
    console(config-if-dcb)#no priority-flow-control priority
    console(config-if-dcb)#exit
    console(config-if)#exit
    console(config)#interface range fortygigabitethernet all
    console(config-if)#datacenter-bridging
    console(config-if-dcb)#no priority-flow-control mode
    console(config-if-dcb)#no priority-flow-control priority
    console(config-if-dcb)#exit
    console(config-if)#exit 

     

  • joergriether

    127 Posts

    1227

    0

    Posted April 24th, 2014 01:00

    Hi Don,

    i am completely with you on that point. BUT to use DCB in real world, you have to make sure, that a) EVERY switch in the line of traffic EQL-to-initiator carries and supports DCB, b) every target can use DCB and c) every initiator can use DCB. Now let´s say a fresh EQL Version 7 comes to the network, it is attached to a fresh n4064 and thus automatically enables DCB and thus, uses PFC. After the N4064 there are other switches, let´s say some 8024s and others WITHOUT DCB enabled. What will happen? The EQL will enable DCB because it talks to the N4064, but the afterlying switches don´t and the initiatitor don´t, too. So - we find ourselfes in a bad scenario because what i (the user) want is at least flow control. Yes, i agree, pfc would be nice -  but let´s be honest - there are not many initiators in real world at this point which do fully support it.

    So - what now? Either I am forced to do a *very* hard modification to my N4064s (which will break network connectivity by the way, just read the intructions i posted earlier) OR i can set DCB off on the CLI of the EQL with Version 7.

    Again, i would set this off on the EQL array. At least while DCB is let´s say *in the beginning* state, especially when it comes to the *whole* ecosystem, in detail the initiators.

    Best regards,

    Joerg