MSL4048 Tape Library cannot be detected in device manager on Backup Server
Back Story
I am one of the system administrators for a customer network for approx. 100 users. The network (rack, components and cables, etc.) was shutdown a couple weeks ago and packed up in prep for a scheduled work location move that occurred a couple weekends ago. The network was reconfigured and it is now back up and running. We are using a new Blade Chassis with fiber channel.
The problem
The network is back up for the most part but we ran into a problem where the Backup Server (HP G1 Blade Server) is now not detecting the HP MSL4048 Tape Library. I have done some of my own troubleshooting:
- Check the Onboard Administrator to make sure all is good with the blade server (backup server)
- I can ping the MSL4048 Tape Library from the backup server
- I can ping the backup server
- I check the fiber connections on the new Blade Chassis (module 3 & module 4 using Fiber channel gbits) and on the MSL 4048 Tape Library (there are 2 fiber connections top and bottom of the tape library). I get a connection light on both.
- I checked the event logs on the backup server. nothing useful found.
- I have shutdown both the MSL 4048 Tape library and backup server and brought them back up one at a time (Tape Library first).
- I have rebooted both MSL4048 Tape Library and backup server and the backup server still cannot detect the Tape Library
Any other troubleshooting suggestions would be greatly appreciated.
I am one of the system administrators for a customer network for approx. 100 users. The network (rack, components and cables, etc.) was shutdown a couple weeks ago and packed up in prep for a scheduled work location move that occurred a couple weekends ago. The network was reconfigured and it is now back up and running. We are using a new Blade Chassis with fiber channel.
The problem
The network is back up for the most part but we ran into a problem where the Backup Server (HP G1 Blade Server) is now not detecting the HP MSL4048 Tape Library. I have done some of my own troubleshooting:
- Check the Onboard Administrator to make sure all is good with the blade server (backup server)
- I can ping the MSL4048 Tape Library from the backup server
- I can ping the backup server
- I check the fiber connections on the new Blade Chassis (module 3 & module 4 using Fiber channel gbits) and on the MSL 4048 Tape Library (there are 2 fiber connections top and bottom of the tape library). I get a connection light on both.
- I checked the event logs on the backup server. nothing useful found.
- I have shutdown both the MSL 4048 Tape library and backup server and brought them back up one at a time (Tape Library first).
- I have rebooted both MSL4048 Tape Library and backup server and the backup server still cannot detect the Tape Library
Any other troubleshooting suggestions would be greatly appreciated.
Gerald Connolly
What about zoning in the fabric? Is that setup OK?
ASKER
we don't do zoning.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes we had a working configuration before the move and it was reconfigured back to the same configuration after the move. The only differences are that we are using a new cisco switch with 10 gb fiber uplinks and connections and a new EVA Blade chassis (fiber channel). Our research has not gotten us anywhere with resolving this issue so far.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for jslaught's comment #a39911046
for the following reason:
None of the expert suggestions were helpful so with continous troubleshooting on this issue, it turned out that the Symantec Backup Exec blade server was not placed back in the right slot in the EVA Blade Chassis when we reconfigured the EVA after our location move. After putting this blade server in the right slot according to our documentation, it finally recognized the Tape Library (medium changer) and tape drives in server device manager. Did some test backups successfully so everything pertaining to this is back online and working properly.
Accepted answer: 0 points for jslaught's comment #a39911046
for the following reason:
None of the expert suggestions were helpful so with continous troubleshooting on this issue, it turned out that the Symantec Backup Exec blade server was not placed back in the right slot in the EVA Blade Chassis when we reconfigured the EVA after our location move. After putting this blade server in the right slot according to our documentation, it finally recognized the Tape Library (medium changer) and tape drives in server device manager. Did some test backups successfully so everything pertaining to this is back online and working properly.
Expert queried config before and after, solution found with config how is that not helpful?
Expert queried config before and after, solution found with config how is that not helpful?
ASKER
The suggestion was made by the expert to check the configuration. My comment provides the details of checking the configuration.