Unsolved
This post is more than 5 years old
4 Posts
0
1502
June 28th, 2013 03:00
NS20FC Integrated
Can anyone tell me what the default IP address is for the host side of the fiber connection between the SPs and the Blades on a Celerra NS20FC Integrated?
No Events found!
dynamox
9 Legend
•
20.4K Posts
0
June 28th, 2013 04:00
it depends if arp-proxy was enabled, if you have access to the control station you can look in /etc/hosts
NickRob1
4 Posts
0
June 28th, 2013 07:00
Yes system was powered up correctly and the san side is working correctly. I get this message on the control station "IRCMEMC01 EMCServer: ReportEvent: NBS device(s) unavailable" a few minutes after it has booted.
NickRob1
4 Posts
0
June 28th, 2013 07:00
I have waited several hours but no luck. I thought it may be something to do with the registered connections between the DMs and the SPs henc my question on ip addresses.
dynamox
9 Legend
•
20.4K Posts
0
June 28th, 2013 07:00
try again in 10-15 minutes
NickRob1
4 Posts
0
June 28th, 2013 07:00
/etc/hosts listed below. Still not sure what should be used, I’ve tried 128.221.252.1 and 128.221.252.2 but can’t get /nbsnas to mount and nas services do not start when cs is booted.
# Do not remove the following line, or various programs
# that require network functionality will fail.
# Internal DART Server Primary Network
# Internal Management Switch Primary Network
# Internal UPS Primary Network
# Internal DART Server Backup Network
# Internal Management Switch Backup Network
# Internal UPS Backup Network
dynamox
9 Legend
•
20.4K Posts
0
June 28th, 2013 07:00
looks like SPA and SPB can be reached on your external network: 10.73.21.40 and 10.73.21.41. NAS service typically starts in 10-15 minutes after power up. Was the proper power up procedure followed ?
Rainer_EMC
4 Operator
•
8.6K Posts
0
June 28th, 2013 08:00
No – I don’t think it has anything to do with the SP
The NBS service is running on the data movers and providing config data to the control station via the internal network.
I would power cycle the data movers, wait a while and then reboot the control station
If the problem still persists open a service request