Veritas cluster MultiNICA, IP Conservation Mode (ICM), not recover corectly
Hi to all, I have a cluster 5.1 Redhat last version or parches. and I have two network interfaces, eth0 and eth4 that are MultiNICA IP Conservation Mode (this is because are external ips and don't want pay for more IP. This is with simulate ips machine1 eth0 has 192.168.1.10 (in the configuration of redhat /etc/networking this eth0 has 192.168.1.10) machine1 eth4 has 192.168.1.10 (in the configuration of redhat /etc/networking this eth4 not has any IP) machine2 eth0 has 192.168.1.11 (in the configuration of redhat /etc/networking this eth0 has 192.168.1.11) machine2 eth4 has 192.168.1.11 (in the configuration of redhat /etc/networking this eth4 not has any IP) Service has 192.168.1.12 Today I make some testing for running service, and pluging off the eth0 the sevice and the ip go to eth4.... OK (Machine1) pluging off the eth4 in machine1 the service fails and go to machine 2 OK.. pluging on eth0 and eth4 in machine 1 and the service allways said that are in fail. this is the message MultiNICA:nic205:monitor:On eth0 current statistics 0 are same as that of Previous statistics 0 I will go to the machine and see ifconfig -a and see that the machine don't have any ip configured in any interfaces (if make a network restart the system go to ok again but if use Performance Mode the system recovers good I don't need restart the network.. I don't want to use ip command to configure the ips, and for this I put Options "broadcast 192.168.1.255" Because I don't want to clean the default interfaces. Any idea why this are happeing? regards!!547Views3likes1CommentVeritas Operations Manager 6.1: Managing LUN classifications
Using Veritas Operations Manager Management Server, you can classify the LUNs created in your data center. You can classify them based on one or more parameters, such as: LUN name Vendor Product Array name Replication status of LUN: Whether or not the LUN is replicated LUN type: Thick or thin RAID group LUN RAID level When you define classifications for LUNs, Veritas Operations Manager stores these definitions as rules in theManagement Server. LUN classification is available only when theStorage Insight Add-on is installed and configuredon theManagement Server. To learn more about LUN classification, see: About LUN classification Using the storage perspective of theManagement Server console, you can create, modify, refresh, and delete LUN classifications. You must haveAdministrator privileges on the Storage perspectiveto perform this task. To learn more, see: Creating LUN classifications Modifying LUN classifications Deleting LUN classifications Refreshing LUN classifications Along with these operations, you can also modify the order in which the LUN classifications are applied to the LUNs. When multiple classifications are applicable to a LUN, Veritas Operations Manager uses the classification that appears first to classify the LUN. For more information about LUNclassification order, see: Modifying the order of the LUN classifications Storage Foundation and High Availability and Veritas Operations Manager documentation for other releases and platforms can be found on theSORT website.418Views2likes0Commentsneed a solution
we have 2 node cluster and with version 5.1 we experienced outage and I think it was due to below error messages can someone shed some light on these messages qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(1): Loop OFFLINE qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(1): Loop ONLINE fctl: [ID 999315 kern.warning] WARNING: fctl(4): AL_PA=0xe8 doesn't exist in LILP map scsi: [ID 107833 kern.warning] WARNING: /pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875f9d9,0 (ssd3): Command failed to complete...Device is gone scsi: [ID 107833 kern.warning] WARNING: /pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875f9d9,0 (ssd3): Command failed to complete...Device is gone scsi: [ID 107833 kern.warning] WARNING: /pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ssd@w203400a0b875f9d9,0 (ssd3): Command failed to complete...Device is gone scsi: [ID 243001 kern.info] /pci@0,600000/pci@0/pci@9/SUNW,qlc@0/fp@0,0 (fcp4): offlining lun=0 (trace=0), target=e8 (trace=2800004) vxdmp: [ID 631182 kern.notice] NOTICE: VxVM vxdmp V-5-0-0 removed disk array 600A0B800075F9D9000000004D2334F5, datype = ST2540- vxdmp: [ID 443116 kern.notice] NOTICE: VxVM vxdmp V-5-0-0 i/o error occured (errno=0x6) on dmpnode 334/0x2c last message repeated 59 times vxdmp: [ID 480808 kern.notice] NOTICE: VxVM vxdmp V-5-0-112 disabled path 118/0x18 belonging to the dmpnode 334/0x28 due to open failure vxdmp: [ID 824220 kern.notice] NOTICE: VxVM vxdmp V-5-0-111 disabled dmpnode 334/0x28 what is this dmpnode 334/0x28 signify, I forget how to map this to device as i only remember is tht its in hexadecimal. Also, what could be the cause of it ... is it due to HBA as issue starts with the message like below qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(1): Loop OFFLINE qlc: [ID 630585 kern.info] NOTICE: Qlogic qlc(1): Loop ONLINE fctl: [ID 999315 kern.warning] WARNING: fctl(4): AL_PA=0xe8 doesn't exist in LILP map1.8KViews2likes4CommentsVCS Error Codes for all platforms
Hello Gents, Do we have a list of all erro codes for VCS ? also if all the error codes are generic and are common for all platforms (including Linux,Solaris, Windows,AIX) Need this confirmation urgently, planning to design a common monitoring agent. Best Regards, NimishSolved6.3KViews2likes6CommentsBest practices for failover without heartbeat
I dont think there is a solution to this, becuse it would violate HA, butI need to ask the question. Prerequisite: HA Setup is up and running. Steps: 1). Unplug the heartbeat cable. (eth1) 2). Unplug/failover the primary system. Secondary system does not come up without manually enabling the autodisable on the faulted primary. They want the secondary system to come up. Automaticly. Is this possable? is it recomemned?968Views2likes2CommentsSFHA Solutions 6.0.1: Using Veritas Operations Manager Package Anomaly Add-on to find package installation anomalies
The Veritas Operations Manager Package Anomaly Add-on lets you generate the report that contains package installation anomalies across your datacenter. For information on Veritas Operations Manager Package Anomaly Add-on, see: About Veritas Operations Manager Package Anomaly Add-on 5.0 Features of Veritas Operations Manager Package Anomaly Add-on 5.0 Prerequisites for installing Veritas Operations Manager Package Anomaly Add-on 5.0 You can run the Veritas Operations Manager Package Anomaly Add-on on storage objects. The supported objects are business entities and hosts. A combination of these two parameters lets you further refine your selection criterion. For information on running the Veritas Operations Manager Package Anomaly Add-on, see: Running Veritas Operations Manager Package Anomaly Add-on 5.0 on the selected objects After you have executed the Veritas Operations Manager Package Anomaly Add-on on these objects, you can view the results in textual and graphical views on the Management Server console. For information on graphical and textual views using the Management Server console, see: Viewing the results of Veritas Operations Manager Package Anomaly Add-on run in the Graphical view Viewing the results of Veritas Operations Manager Package Anomaly Add-on run in the Textual view For more information on using Package Anomaly Add-on, see the Veritas Operations Manager Management Server Add-ons User's Guide. Veritas Operations Manager documentation for other releases can be found on the SORT website.342Views2likes0CommentsVeritas Risk Advisor: Working with tickets
Veritas Risk Advisor (VRA) is a data protection and downtime avoidance risk assessment solution. VRA lets you diagnose disaster recovery and high availability (clustering) problems (also called “gaps”) and optimize data protection and reduce risk of downtime. VRA scans your environment and alerts you to any potential gaps, best practice violations, or service level agreement (SLA) breaches. What is a ticket? When VRA detects a gap in your disaster recovery and/or high availability, it issues a ticket. The ticket specifies the problem and the environment entities associated with that problem. For example, VRA can identify: Critical data that is not protected properly. Standby hosts that do not have access to the replicated data. Service Level Agreements (SLAs) that are too strict or too lenient. Inconsistent access to storage by cluster nodes. Searching for tickets The VRA Tickets module lets you filter the list of tickets in your system to find a specific ticket or ticket type. After VRA displays your query search results, you can: Group the results by criteria that you specify. Drill down to see ticket details. View the network topology related to the ticket in the Topology module. Group the results by criteria that you specify. A full description of the ticket is provided, including an explanation of the problem and the items in your environment that are involved. The impact on your system is also shown with suggestions on how to resolve the ticket. Working with tickets You can perform a variety of operations on a ticket during its lifecycle. Mark the ticket as resolved. The next time VRA scans your system, it will consider this issue closed. Suppress a ticket. A suppressed ticket indicates that you are aware of this problem, but you do not want to be informed about it again during the next full system scan. Open the Topology module. You can open the topology module displaying the items relevant to the ticket. Add a note to a ticket. You can add a note to a ticket that describes it in more detail. You can filter by note text to make it easier to find a specific ticket(s). Add a star rating to indicate its level of important. (One star is the lowest ticket rating and five stars the highest.) You can then sort your tickets by rating to quickly see your most important issues. You can also perform operations on multiple tickets. Learning more For more information on working with tickets, see “Using the Tickets Module” in the Veritas Risk Advisor User’s Guide. You can access the User’s Guide and other VRA documentation in the Documents area of the SORT website.603Views1like0CommentsApplicationHA 6.1, ESXi 5.5 and SQL 2012 problems
Hi all, Just wondering if anyone out there might be able to throw a bit of advice my way. Currently evaluating AppHA on VMWare (AppHA 6.1 and ESXi 5.5 hosts) with the view to buying as on paper it does exactly what we want. I've installed the High Availability Console server which has plugged into vCenter nicely, installed the ApplicationHA agent onto a VM running Windows 2012 DC R2 and SQL 2012, again all going smoothly up to this point. Now I get around to testing the agent out. I'm doing this by stopping the sql server and sql agent services on the VM and waiting for AppHA to kick in and restart both services, this is when I'm getting into a little trouble. Firstly the services do not shut down as cleanly as when the agent is not configured on the VM, a message pops up saying that windows could not stop the SQL server and that the service did not return an error, helpful I know. This does not happen when the agent is not configured on the VM, the services shut down fine. Secondly when the agent is configured and the services finally shut down, the AppHA plugin for the VM in vCenter displays a faulted status and that the SQL server service is not running and that the SQL agent service could not started. AppHA just sits there and does nothing, it does not restart the services as it should do. Now it's probably something I've done during setup but being new to the product I cannot see what, I have followed all the install pdf's and have read them over many times, I just cannot see what I may have done wrong as the setup seems simple enough. Or am I testing the product in the wrong fashion? As I'm only in evaluation mode I have no technical support with Symantec so any help with this would be very much appreciated as we are looking at buying this product and at the moment this is the final piece of the test I need to get working (probably the most important part) before I can turn to the bean counters and ask for some cash. Many Thanks LeeSolved2.4KViews1like2Comments