Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
1.First confirm with customer, check the working state of the both server. Before issue happened, APP working in secondary. And permiary not ok. So we should focus on the standby server.
2.As server cannot ping or telnet, so in that case, we should login through com port which in the back side of the server as follows: To connect the laptop to the server over the console port on the ALOM board, perform the following steps:Connect the COM port on the ALOM board of SUN server and the COM port of the laptop by using the appropriate serial port cable.
Step 1Start any of the terminal management software, such as hypertrm.exe in the Windows OS, SecureCRT, netterm, teraterm, or CRT, on the laptop.
Step 2Retain the default values of Port, Baud Rate, Data Bits, Parity and Stop Bits, as shown in the Communications Setup dialog box, and then click OK.
Step 3Check whether information is displayed in the terminal management software window. If no information is displayed, check the server, serial port cable, terminal management software, and laptop.
Step 4Enable the telnet through below commands
1. Remove # in front of below line
# vi /etc/inetd.conf
#telnet stream tcp6 nowait root /usr/sbin/in.telnetd in.telnetd
Change to :
telnet stream tcp6 nowait root /usr/sbin/in.telnetd in.telnetd
2. then reboot the inetd daemon, with the command below :
# pkill inetd
# /usr/sbin/inetd –s
3. Secondary system working fine after reboot the same, and can telnet also. This means system no issue that time.
4. Telnet to the secondary server, checks the logs, found:
DCN interrupted and server running in the double-working state. And the secondary cannot start after the DCN restore. Logs as follows:
2011/02/25 22:51:43 VCS NOTICE V-16-1-50983 Resource NMSServer is offline on system Primary in cluster primaryCluster
2011/02/26 00:16:25 VCS NOTICE V-16-1-50983 Resource NMSServer is offline on system Primary in cluster primaryCluster
2011/02/26 00:38:41 VCS ERROR V-16-3-18313 (Secondary) TCP/IP connection via connector from cluster secondaryCluster to cluster primaryCluster is hung; intentionally disconnecting. Auto-reconnect will occur however you may wish to examine the wac resource on system 192.168.202.1
2011/02/26 00:38:41 VCS ERROR V-16-3-18311 (Secondary) secondaryCluster lost connection to cluster primaryCluster
2011/02/26 03:19:00 VCS ERROR V-16-2-13027 (Secondary) Resource(csgnic) - monitor procedure did not complete within the expected time.
2011/02/27 16:12:52 VCS NOTICE V-16-20013-16 (Secondary) SybaseBk:BackupServer:monitor:Setting cookie for proc = /opt/sybase/ASE-12_5/bin/backupserver -SDBSVR_back -e/opt/sybase/ASE-12_5/insta, PID = /proc/18880
2011/02/27 16:12:52 VCS INFO V-16-1-10299 Resource BackupServer (Owner: unknown, Group: AppService) is online on Secondary (Not initiated by VCS)
2011/02/27 16:12:52 VCS NOTICE V-16-1-10233 Clearing Restart attribute for group AppService on all nodes
2011/02/27 16:12:52 VCS ERROR V-16-1-50921 CONCURRENCY VIOLATION:Group AppService is online on the following clusters [primaryCluster, secondaryCluster]
5. After the DCN restore, VERITAS will change to recovered state. Locked the secondary server, App offline also, and try to start the primary server. As the faulty already exist in the Primary, so Veritas will keep in recovered state.
6. 2011/02/27 16:12:52，disable the MAC port in the Secondary and start the APP in Secondary also, monitor restore.
7. Check the primary server found the OS abnormal , reinstall the server and synchronization fully. Then VERITAS restore.