Difficulty recovering one of three servers after power outage
southcoast
50 Posts
November 1, 2018, 2:01 pmQuote from southcoast on November 1, 2018, 2:01 pmHello,
I need first to set the addressing to match the access desired. With two NIC's on the servers and the eth0 port set as management in the 10.0.20.0/24, the wget get commands work:
root@peta-san-01:~# wget 10.0.20.3:5000
--2018-11-01 21:21:50-- http://10.0.20.3:5000/
Connecting to 10.0.20.3:5000... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5902 (5.8K) [text/html]
Saving to: 'index.html.1'
index.html.1 100%[===================>] 5.76K --.-KB/s in 0s
2018-11-01 21:21:50 (24.2 MB/s) - 'index.html.1' saved [5902/5902]
root@peta-san-01:~#
And
Connecting to 10.0.20.2:5000... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5902 (5.8K) [text/html]
Saving to: 'index.html'
index.html 100%[===================>] 5.76K --.-KB/s in 0s
2018-11-01 21:15:33 (381 MB/s) - 'index.html' saved [5902/5902]
root@peta-san-02:~#
However, the backend scheme on eth1 is in the 10.250.251.0/24 scheme where the clients needed iSCSI access are in the 192.168.0.0/24 scheme.
Can the backend and iSCSI schemes be the same?
Hello,
I need first to set the addressing to match the access desired. With two NIC's on the servers and the eth0 port set as management in the 10.0.20.0/24, the wget get commands work:
root@peta-san-01:~# wget 10.0.20.3:5000
--2018-11-01 21:21:50-- http://10.0.20.3:5000/
Connecting to 10.0.20.3:5000... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5902 (5.8K) [text/html]
Saving to: 'index.html.1'
index.html.1 100%[===================>] 5.76K --.-KB/s in 0s
2018-11-01 21:21:50 (24.2 MB/s) - 'index.html.1' saved [5902/5902]
root@peta-san-01:~#
And
Connecting to 10.0.20.2:5000... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5902 (5.8K) [text/html]
Saving to: 'index.html'
index.html 100%[===================>] 5.76K --.-KB/s in 0s
2018-11-01 21:15:33 (381 MB/s) - 'index.html' saved [5902/5902]
root@peta-san-02:~#
However, the backend scheme on eth1 is in the 10.250.251.0/24 scheme where the clients needed iSCSI access are in the 192.168.0.0/24 scheme.
Can the backend and iSCSI schemes be the same?
southcoast
50 Posts
November 1, 2018, 2:12 pmQuote from southcoast on November 1, 2018, 2:12 pmSorry, to answer the questions from your last post, yes, these functions do work.
Sorry, to answer the questions from your last post, yes, these functions do work.
admin
2,930 Posts
November 1, 2018, 3:16 pmQuote from admin on November 1, 2018, 3:16 pmthe server went offline and no longer accessible either on UI access at port 5000 or ssh access on port 22
From the console I can ping the next hop..
if node 1 is offline/in-accessible from where you are located, yet node 1 is accessible to node 2 via the different subnets/ports..i would suggest to check your network connections / configuration beyond the switch connecting the PetaSAN nodes.
the server went offline and no longer accessible either on UI access at port 5000 or ssh access on port 22
From the console I can ping the next hop..
if node 1 is offline/in-accessible from where you are located, yet node 1 is accessible to node 2 via the different subnets/ports..i would suggest to check your network connections / configuration beyond the switch connecting the PetaSAN nodes.
southcoast
50 Posts
November 1, 2018, 5:46 pmQuote from southcoast on November 1, 2018, 5:46 pmThe server went offline when I set the iSCSI address to match the local subnet where the clients are located. To the question of the network, my switch was set as a single VLAN. With a separate management scheme 10.0.20.0/24 I created a separate VLAN. But I see in the quick start guide the management and iSCSI1 and Backend1 schemes share an interface. So, that would mean I should retain the single VLAN on my switch and allow 3 IP addressing schemes to share eth0, correct? If so, would the interface address on my local switch be configured with secondary addressing rather than the segmentation I am creating?
The server went offline when I set the iSCSI address to match the local subnet where the clients are located. To the question of the network, my switch was set as a single VLAN. With a separate management scheme 10.0.20.0/24 I created a separate VLAN. But I see in the quick start guide the management and iSCSI1 and Backend1 schemes share an interface. So, that would mean I should retain the single VLAN on my switch and allow 3 IP addressing schemes to share eth0, correct? If so, would the interface address on my local switch be configured with secondary addressing rather than the segmentation I am creating?
admin
2,930 Posts
November 1, 2018, 7:43 pmQuote from admin on November 1, 2018, 7:43 pmnode 1 is accessible by other nodes from within the PetaSAN cluster, so the network and switch setup at that layer is fine. At layers / hops beyond this, the node is not (or no longer) accessible. I would check configuration of switches/vlans/routers(?) beyond the PetaSAN switch.
node 1 is accessible by other nodes from within the PetaSAN cluster, so the network and switch setup at that layer is fine. At layers / hops beyond this, the node is not (or no longer) accessible. I would check configuration of switches/vlans/routers(?) beyond the PetaSAN switch.
southcoast
50 Posts
November 1, 2018, 11:09 pmQuote from southcoast on November 1, 2018, 11:09 pmOk, I am not sure how, but from my windows 10 PC following the directions, I am connected to my cluster. I am a bit uncertain of the packet flow. I am grateful it works, I jsut want to understand the how of it. There are two NICs and four schemes and with separate VLAN on the eth0 interface I could not see how the access works, but it does anyway. Anyway, I am connected as I intended and will next work on the VMware systems.
Thanks a bunch for your patience through this process!
Ok, I am not sure how, but from my windows 10 PC following the directions, I am connected to my cluster. I am a bit uncertain of the packet flow. I am grateful it works, I jsut want to understand the how of it. There are two NICs and four schemes and with separate VLAN on the eth0 interface I could not see how the access works, but it does anyway. Anyway, I am connected as I intended and will next work on the VMware systems.
Thanks a bunch for your patience through this process!
southcoast
50 Posts
November 1, 2018, 11:45 pmQuote from southcoast on November 1, 2018, 11:45 pmWhen I create a volume and another person does as well from their PC, how would files loaded to the SAN be shared among users?
On one of my nodes I have a 1tb volume, would that be available or available storage no larger than the smallest drive?
When I create a volume and another person does as well from their PC, how would files loaded to the SAN be shared among users?
On one of my nodes I have a 1tb volume, would that be available or available storage no larger than the smallest drive?
Difficulty recovering one of three servers after power outage
southcoast
50 Posts
Quote from southcoast on November 1, 2018, 2:01 pmHello,
I need first to set the addressing to match the access desired. With two NIC's on the servers and the eth0 port set as management in the 10.0.20.0/24, the wget get commands work:
root@peta-san-01:~# wget 10.0.20.3:5000
--2018-11-01 21:21:50-- http://10.0.20.3:5000/
Connecting to 10.0.20.3:5000... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5902 (5.8K) [text/html]
Saving to: 'index.html.1'index.html.1 100%[===================>] 5.76K --.-KB/s in 0s
2018-11-01 21:21:50 (24.2 MB/s) - 'index.html.1' saved [5902/5902]
root@peta-san-01:~#
And
Connecting to 10.0.20.2:5000... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5902 (5.8K) [text/html]
Saving to: 'index.html'index.html 100%[===================>] 5.76K --.-KB/s in 0s
2018-11-01 21:15:33 (381 MB/s) - 'index.html' saved [5902/5902]
root@peta-san-02:~#
However, the backend scheme on eth1 is in the 10.250.251.0/24 scheme where the clients needed iSCSI access are in the 192.168.0.0/24 scheme.
Can the backend and iSCSI schemes be the same?
Hello,
I need first to set the addressing to match the access desired. With two NIC's on the servers and the eth0 port set as management in the 10.0.20.0/24, the wget get commands work:
root@peta-san-01:~# wget 10.0.20.3:5000
--2018-11-01 21:21:50-- http://10.0.20.3:5000/
Connecting to 10.0.20.3:5000... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5902 (5.8K) [text/html]
Saving to: 'index.html.1'
index.html.1 100%[===================>] 5.76K --.-KB/s in 0s
2018-11-01 21:21:50 (24.2 MB/s) - 'index.html.1' saved [5902/5902]
root@peta-san-01:~#
And
Connecting to 10.0.20.2:5000... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5902 (5.8K) [text/html]
Saving to: 'index.html'
index.html 100%[===================>] 5.76K --.-KB/s in 0s
2018-11-01 21:15:33 (381 MB/s) - 'index.html' saved [5902/5902]
root@peta-san-02:~#
However, the backend scheme on eth1 is in the 10.250.251.0/24 scheme where the clients needed iSCSI access are in the 192.168.0.0/24 scheme.
Can the backend and iSCSI schemes be the same?
southcoast
50 Posts
Quote from southcoast on November 1, 2018, 2:12 pmSorry, to answer the questions from your last post, yes, these functions do work.
Sorry, to answer the questions from your last post, yes, these functions do work.
admin
2,930 Posts
Quote from admin on November 1, 2018, 3:16 pmthe server went offline and no longer accessible either on UI access at port 5000 or ssh access on port 22
From the console I can ping the next hop..if node 1 is offline/in-accessible from where you are located, yet node 1 is accessible to node 2 via the different subnets/ports..i would suggest to check your network connections / configuration beyond the switch connecting the PetaSAN nodes.
the server went offline and no longer accessible either on UI access at port 5000 or ssh access on port 22
From the console I can ping the next hop..
if node 1 is offline/in-accessible from where you are located, yet node 1 is accessible to node 2 via the different subnets/ports..i would suggest to check your network connections / configuration beyond the switch connecting the PetaSAN nodes.
southcoast
50 Posts
Quote from southcoast on November 1, 2018, 5:46 pmThe server went offline when I set the iSCSI address to match the local subnet where the clients are located. To the question of the network, my switch was set as a single VLAN. With a separate management scheme 10.0.20.0/24 I created a separate VLAN. But I see in the quick start guide the management and iSCSI1 and Backend1 schemes share an interface. So, that would mean I should retain the single VLAN on my switch and allow 3 IP addressing schemes to share eth0, correct? If so, would the interface address on my local switch be configured with secondary addressing rather than the segmentation I am creating?
The server went offline when I set the iSCSI address to match the local subnet where the clients are located. To the question of the network, my switch was set as a single VLAN. With a separate management scheme 10.0.20.0/24 I created a separate VLAN. But I see in the quick start guide the management and iSCSI1 and Backend1 schemes share an interface. So, that would mean I should retain the single VLAN on my switch and allow 3 IP addressing schemes to share eth0, correct? If so, would the interface address on my local switch be configured with secondary addressing rather than the segmentation I am creating?
admin
2,930 Posts
Quote from admin on November 1, 2018, 7:43 pmnode 1 is accessible by other nodes from within the PetaSAN cluster, so the network and switch setup at that layer is fine. At layers / hops beyond this, the node is not (or no longer) accessible. I would check configuration of switches/vlans/routers(?) beyond the PetaSAN switch.
node 1 is accessible by other nodes from within the PetaSAN cluster, so the network and switch setup at that layer is fine. At layers / hops beyond this, the node is not (or no longer) accessible. I would check configuration of switches/vlans/routers(?) beyond the PetaSAN switch.
southcoast
50 Posts
Quote from southcoast on November 1, 2018, 11:09 pmOk, I am not sure how, but from my windows 10 PC following the directions, I am connected to my cluster. I am a bit uncertain of the packet flow. I am grateful it works, I jsut want to understand the how of it. There are two NICs and four schemes and with separate VLAN on the eth0 interface I could not see how the access works, but it does anyway. Anyway, I am connected as I intended and will next work on the VMware systems.
Thanks a bunch for your patience through this process!
Ok, I am not sure how, but from my windows 10 PC following the directions, I am connected to my cluster. I am a bit uncertain of the packet flow. I am grateful it works, I jsut want to understand the how of it. There are two NICs and four schemes and with separate VLAN on the eth0 interface I could not see how the access works, but it does anyway. Anyway, I am connected as I intended and will next work on the VMware systems.
Thanks a bunch for your patience through this process!
southcoast
50 Posts
Quote from southcoast on November 1, 2018, 11:45 pmWhen I create a volume and another person does as well from their PC, how would files loaded to the SAN be shared among users?
On one of my nodes I have a 1tb volume, would that be available or available storage no larger than the smallest drive?
When I create a volume and another person does as well from their PC, how would files loaded to the SAN be shared among users?
On one of my nodes I have a 1tb volume, would that be available or available storage no larger than the smallest drive?