IPMI does not work
Hi, we are helping a customer to configure a NetApp 5230 appliance which is upgraded from 2.5.4 to 2.6.0.3. Previously we did not configure IPMI. After the upgrade, we decide to configure IPMI. However, I followed the guidelines in NetBackup doc but it does not work. I cannot ping the IPMI port no matter what IP address I set. How to troubleshoot this? Thanks in advance.Solved8.3KViews7likes6CommentsFirmware & BIOS levels NBU 5230 Appliances
Hi, We are running several NBU 5230 Appliances (Current version 2.6.1.1) From support we have heard that our (RAID) firmware and BIOS levels are not current. My questions: What RAID firmware should we be running? What BIOS level should the 5230 units have? Do disk firmware levels also need updating and what level should they have? If RAID firmware is updated, should drivers be running a certain version as well? If yes, what version is best? Where can we obtain these updates? If we would go to 2.6.1.2, will any firmware/BIOS levels be updated during the upgrade process? (Probably not, I suspect) Has anybody performed these upgrades and encountered any issues? Thanks for any help! FredSolved7.6KViews0likes8CommentsNetbackup Licensing Guide
Hi everyone, I have 26 clients windows physicals, 2 VMware and 16 BD SQL inside of this VMware, with 20 TB for backup.....just that dont find a guide full licencing of Netbackup, i need know the difference of Agent vs Capacity, and know how the appliance 5230 is licensed. The appliance 5230 is licensed for agent or capacity? Anybody here can i help me please...? Also need a list of price of appliance and the agents...Solved6.7KViews0likes3CommentsNetbackup Appliance - Login Issue
Hi, I'm setting up a new appliance...straight out of the box. I put in IP address, DNS, gateway, SMTP and email address details...then my browser hang. On restart, I can't log into the appliance at all. I get the error 'Login failed. Please contact your System Administrator.' My set up is that I've connected my laptop to the appliance. I've tried using different browsers, cleared cache, etc....still giving me the same error. Please help.Solved6.4KViews0likes11Comments5230 Appliance - BIOS Warning
I have just installed a new 5230 appliance which shipped with 2603 installed. After initial configuration I upgraded the appliance to 261 which completed successfully in approximately 1 hour (MSDP pool only contained a couple of test backups). During the boot following upgrade I noticed a message as follows: "The installed version of the BIOS firmware is not correct. Contact your administrator to update the BIOS firmware" I was under the impression that the upgrade rpm packages updated all required firmware, O/S and NBU code ? I cannot locate any details regarding BIOS upgrades for the 5230 appliance. I don't know if this is specific to 261 (first 261 Iinstall I have completed) - has anyone come accross this ? Thanks, AJSolved4.9KViews1like6CommentsNetBackup Appliance 2.7.3 reimage ISO download
The 2.7.3 upgrade rpm has been available for download for a little over a week now. Anyone managed to get the 2.7.3 reimage ISO "NetBackup_Appliance_2.7.3_ML.iso" from Symantec FileConnect yet? Or are you supposed to get them from elsewhere now? I'm so out of touch. Thanks all, RLeon4.6KViews0likes6CommentsNBU appliance 2.6.1.2 can't pass the host configuration
Hi Please advise is there any workaround to pass the host configuration Error "Failed to resolve the host name" The appliance can pass the nalookup of it's name and it has been added in host file Please see the attachment Many thx in advance T.W.Solved4.5KViews0likes9CommentsNIC Bonding
Hello, Having a little trouble getting 802.3ad nic teaming working on two 5230 appliances. I've configured teaming before on Windows 2008 servers and it seems to work fine. The network team configures LACP on the switch side, and on the server side, I create the team in 802.3ad mode. On the appliance however, I create the bond, and on cli as well as through the web interface of the appliance, it looks to be created and functional, but on the switch side it doesn't look to be active. The bond has been created with eth1,2 and 3 ports (1 Gb/s). The web interface shows them all as up, and the network configuration shows the correct IP on bond0(eth1,eth2,eth3) with bond mode at 802.3ad. On the switch side, for some reason, the bond automatically splits into 2 separate bonds, 1 bond with eth1 and the other with eth2 and eth3. Both bonds show with LACP configured. We have two identical appliances, and we have tried configuring bonding on both appliances and the exact same thing happens. Has anyone come across this, or have any suggestions of what else to check? Thanks!Solved4.3KViews2likes8Comments