Visit Open-E website
Results 1 to 9 of 9

Thread: cannot connect to SAN

  1. #1

    Default cannot connect to SAN

    Hello I canno connect to the SAN, no ACL is setup, I have other 4 hypervisors connected to the SAN without problems:

    [root@hypervisor7 ~]# telnet 10.62.24.40 3260
    Trying 10.62.24.40...
    telnet: connect to address 10.62.24.40: Connection refused
    telnet: Unable to connect to remote host: Connection refused
    [root@hypervisor7 ~]# iscsiadm -m discovery -t sendtargets -p 10.62.24.40
    iscsiadm: cannot make connection to 10.62.24.40: Connection refused
    iscsiadm: cannot make connection to 10.62.24.40: Connection refused
    iscsiadm: cannot make connection to 10.62.24.40: Connection refused
    iscsiadm: cannot make connection to 10.62.24.40: Connection refused
    iscsiadm: cannot make connection to 10.62.24.40: Connection refused
    iscsiadm: cannot make connection to 10.62.24.40: Connection refused
    iscsiadm: connection login retries (reopen_max) 5 exceeded
    iscsiadm: Could not perform SendTargets discovery: encountered connection failure

    We have one license but not in this SAN, we are doing some tests. Is trial license limited in someway that explains this?

    Regards

  2. #2
    Join Date
    Oct 2010
    Location
    GA
    Posts
    935

    Default

    the trial has no limits on connections.

    check your routing to the storage IP.

  3. #3

    Default

    Sorry, I forgot to mention I can ping the SAN:

    [root@hypervisor7 ~]# ping 10.62.24.40
    PING 10.62.24.40 (10.62.24.40) 56(84) bytes of data.
    64 bytes from 10.62.24.40: icmp_seq=1 ttl=64 time=3.11 ms
    64 bytes from 10.62.24.40: icmp_seq=2 ttl=64 time=0.085 ms
    64 bytes from 10.62.24.40: icmp_seq=3 ttl=64 time=0.062 ms

    Regards

  4. #4

    Default

    I also checked SAN logs and the only thing I can find about ip I try to connect from is I can see ip in arp -nv output. No other log show anything about this ip. Even tried to add to de ACL, without success.

    Regards

  5. #5
    Join Date
    Oct 2010
    Location
    GA
    Posts
    935

    Default

    is this a virtual IP assignment? If so, make sure failover service is running.

    Any bonds, vlans ?

  6. #6

    Default

    Hello, no bonds, vlan yes, but access mode, same config than the other Hypervisors and switch ports that are currently running ok.

    Regards

  7. #7
    Join Date
    Oct 2010
    Location
    GA
    Posts
    935

    Default

    make sure nothing is in the way on port 3260.

  8. #8

    Default

    [root@hypervisor7 ~]# service iptables stop
    Expurgar reglas del cortafuegos: [ OK ]
    Configuración de cadenas a la política ACCEPT: filter [ OK ]
    Descargando módulos iptables: [ OK ]
    [root@hypervisor7 ~]# telnet 10.62.24.40 3260
    Trying 10.62.24.40...
    telnet: connect to address 10.62.24.40: Connection refused
    telnet: Unable to connect to remote host: Connection refused

    Regards

  9. #9
    Join Date
    Oct 2010
    Location
    GA
    Posts
    935

    Default

    [root@hypervisor7 ~]# telnet 10.62.24.40 3260
    Trying 10.62.24.40...
    telnet: connect to address 10.62.24.40: Connection refused
    telnet: Unable to connect to remote host: Connection refused
    Something is blocking the connection. Can you try it without the VLAN?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •