In OMS 6500 we intermittently observed backup failure alarm. What could be the possible cause for the same?
Intermittent database save failure can be cause by factors such as bad communication link between the affected node and the server, a faulty SP card or a pre-existing alarm on the node. I extracted the following from the 6500 R12.0 Fault management guide:
check the network element to determine whether a condition exists that can prevent a save. These conditions include:
• a “Software Upgrade in Progress” alarm is active
• a database save is already in progress
• a “Software Mismatch” alarm is active
• the software version on the shelf processor is different from the other circuit packs
• a “Disk Full” alarm is active
• an unsaved SAOS CLI config
— Save SAOS CLI configurations from the primary PKT/OTN cross-connect/eMOTR circuit packs and then re-issue the restore operation
• a corruption in the network element database is detected (indicated by a Transport Data Recovery Failed, a Database Recovery Incomplete, or a Switch Shelf ID Mismatch detected alarm)
• active alarms are present unless you specify the backup to ignore active alarms
• the NE mode is “Unknown”
I hope this answer helps.
Hello all -- can you tell me what ports are in use for backups? All of a sudden every 100+ nodes are failing on backups from 1C. This sounds like a transport problem and someone in my company made firewall changes. Need to know ports though : SFTP ?
Hi James, I just wanted to check in and see if you still need help with your question or have resolved the issue? Look forward to hearing from you.
In the future, a new question may be a better way to ask the community, or you're welcome to mention me to get my attention. I unfortunately missed it as a comment to this question, sorry.
Retrieving data ...