Tuesday, September 23, 2014

Migration



1) Boxes
2) JVMs on each boxes
3) Host Names
4) Firewall rules { All the rules  } Most important.
5) Install the binaries and federate one node at a time
6) After each federation - recyclel the DMGR
                           stop the nodeagent
                           Resync
                           Restart the Nodeagent

7) Setup the log4j scripts { check if in error or debug }
8) SEtup the application scripts { Take time but , be careful with hosts }
   i)   Deployment scripts
   ii)  SSH  Keys -  the key in id_rsa.pub on each server needs to be
        added to the authorized_keys.txt  file on the other server.
        -While doing so , make sure that the key is added correctly.
        -There is a possibility , of the key being split into two seperate lines
         which will corrupt the key.{ Please recheck and add as necessary }
9) Setup Cloudmark - for virus scan
10) setup sharedlib - JavaMailservice.jar
11) Setup WEbserver - and static content on it
12) If any node doesnt show up - check the firewall connectivity
    Work with the respective team and open the firewall ports
13) Setup log4j - diretories
    Setup log4j in classpath
    Setup shared libraries (icsJavaMailservice.jar )
    setup class paths
    setup - DB- JDBC drivers
    setup icscert.jck
    Setup SSL certs
    Setup certificates for ISPs.
    Setup Certificate for New-bay.

14) check the firewall ports to be open
15) Netscaler Rules
16) Grid XS - fp
17) /etc/hosts - check for ip addresses and correct hosts names
18) Check for keep alives
19) Revese proxy server setup } Not necesasry
20) Cloudmark - Virus scan
21) Comm suite - commsuite, MMP , SMTP
22) Web server
23) reverse - proxy on webserver
24) StaticContent.jar
25) docs
26) VIP - Probing - keepalive configuration
27) Change the log root in Environments -> Webspher Variables
28) check for the right versions of EAR files , shared lib jar files
    JavaMailservice.jar ,  static content
29) MQ - Configuration
30) LDAP HOST name in DB
31) Grid bootstrap port # in DB Property
32) If we are removing the node
      - Please do a full resync
      - Please recycle the DMGR and the respective node agents
      -
33) Database didnt provide the right username / password
    Check in the resources.xml  - Create this procedure and upload to Confluence
34)

==========
| ISSUES |
==========

1) LB priority issue
2) some certs missing
3) dB props { modify the props according to the requirement }
4) grid props for port #
5) F1 proxy issues
6) Device -name issues
7) LDAP issues
8) DB olumns - missing issue
9) MDN issue with Vision
10) Heap size requirement for JVMs - memory settings
11) JVM threads { web container threads }
12) Database connection pooling
13) PMI { monitoring }
14) High CPU - caputure thread dumps and check the threads , that are consuming high cpu
15) Continious Full GC - Increase the heap size
16) Opensso agents
17) Port conflicts - default host issues
18) Issue with keep alives
19) Keep alives probe , not configured on the Load balancer.
20) Connectivity to the database ,
21) Vision urls in DB { issue with DB connection url and port # }
22) Check the keep alives in http_access.log { load balancer configuration wrong }
23) The grid jvms boot strap port # needs to be updated in DB
24) Sync jvms , Web container custom props need to be updated
25) If issue with keep alives , then configuration on LB needs to be changed.
26) Issue with the request URL - if its a 404
27) Proxy settings with servers
28) Sync JVMS Web container props missing
29) JVM Parameters - missing
30) Props have wrong values
31) DB Updates are wrong
32) Please cross check the Db Port # Updates-
33) AM - Static content missing
34) AM Environment - not pointing to the correct Vision environment
35) Mailstore - configurations wrong - timing out on the mailstores - )( Accumulator s )
36) LDAP issue { ldap Host name }
37) Issue with MQ channel , as connections maxed out
38) Issue with LTPA token , resync , restart the DMGr and start the Application
39) Issue with firewall port - no connectivity exists
40) netstat -an | grep SYN
41) Continious high GC - increase the Heap size , and enable tracing using parameters , in Generic
    JVM args
42) Stale ips in /etc/hosts file
43) Issue with AM agents
44) Issues with hosts file - The names of the hosts specified
45) Issue with SSH keys - typos in Authorized_keys " twolines instead of one line "
46) Check the ssh keys both on the build server and the respective jvms. ( IMP )
47) Issue with JDBC provider ( are we using the correct version of he JDBC provider ? )
    The JDBC provider could be corrupt sometimes
48) Issue with Shared lib ( IcsJavaMaiilservice.jar  file  is it the right version )
    Please change it.
49) The database could be down
    The listeners need to be restarted some times
    The auth alias needs to be confirmed , before assocaiting it with a database
    The
50) Cloudmark log setup
    /app/cloudmark   -- > This needs to be setup on all the Presentation Boxes
    /log/cloudmark   -- > This needs to be setup on all the Presentation Boxes
51) ics.jck  -- > Make sure , we have the right version of this file
    /app/conf/certs  -- This is the lcoation where the cert needs to be placed.
    The location is specified on the the name space bindings -- In the console
     Environment --> Naming -->  Name space bindings -- > Key file location.
     The scope is cell and the binding type is string
             -->  KEY_FILE_LOC
             --> The string is  /app/conf/certs/  or  /app/certs  --> according
                 to the environment specifications.
                 Myverizon has it on /app/conf/certs {For BUA }

52) Events issue with Mq.
    The MQ needs to be restarted. ( On Toyota  AMQM2QA )
    The process associated with Router need to be restarted
53) The siteminder policies
54) The http header methods , sometimes , the PUT , GET , DELETE
    one of the above methods , might have not been defined and a
    particular operation fails, { we may need to check , if this method is defined }
     

55)  mail host in ICS_MESSAGING_QUOTA table was incorrect
     updated to icsqa2ms2.sdc.vzwcorp.com
     now delete endpoints is successful
56) CPU Starvation on Vison simulator - leads to socket timeout exceptions
    on pgw
57) Events issue , we have to check weather the profiles exists in the AM LDAP
    get the names of LDAP hosts for each environment { have a list }
58) Issue with Mail store
    The conf file on the mail store was not good and it had to be updated
    The issue was during installation. The files were , conf file and .dat file
    If copying the file from other environment , we need to have the ldap updated.
59) The value for the vision simulato rURL -
60) The vision simulator up or down
61) The URL for Fusion one
62) The URL for Cloudmark
63) The vip for media mixer { are they using the correct url }
64) The respective flags on AM side { if we are not getting events }
    Compare the configuration with Pre-prod
65) SMS binds { We may need to increase the number of binds on the smsc gateway }
    We need to call " Hong, ki " and ask him to increase the number or threads
66) Firewall issues , check the connectivity

    Telnet test  -  Mailstore       143
                    RSA             443
                    Mailstore host  143
                    LDAP            10389
                    AOl             8519
                    SMTP            25    265  587
                    IMAP            143   993
                    HTTP            80
                    HTTPs           443
                    RTMP            1935 { used by adobe FMS - Flash media server }
                                    for Media recording

                    RTMP - changed to RTMPS
                   

67) BUA+ Media see timeouts to the WIP
    Make sure the URL of the Media server , in the db is right
    For preprod , we use a vip { Load balancer } which has been configured
68) Issue with Static Content
69) Issue with Database , properties , check how many firewalls are involved
    Check the firewall ports on the right servers and the right flows.
70) Check the ICSJavamail service.jar  , the entry in the console respectively
71) Check the ics.jck and the corresponding Namespace binding in Console
72) Check the JDBC driver and the corresponding entries in the console - and class path entries
73) Shared library mappings and the CLASS path entries
74) setup Vision simulator and the firewall rule needed for it on port # 5999
75) Check the connectivity between the server on which the vision simulator is being setup and
    PG, Presentation
76) Issues with ISP certificates.
77) Issues with Device names
    Device names not present in Vision , not able to add the MDN
78) Device testing } -->
79) Issue with the JVM - custom properties
80) Issue with the JVMs not having correct app id in  JVM system properties
    JVM system properties , meaning - JVM custom properties , Generic properties
81) FMS servers , make sure all the PORTS are open up to the MMSC gateway
82) Issue with missing tables in Database
83) Issue with missing JVM web container props
84) Issue with additional firewall and db issues pop up
85) Issue with wrong JVM names
86) Issues with MDNs, Mon existent inbox on mailstore.

=============================================================================================

*******
For setting up an environment ,
On the load balancer , we set up the keep alives probe.
The load balancer or the VIP will constantly keep probing the  JVMs, to check if they are up or not.
So , the configuration is set up on the Load balancer.
For the http headers , we do the following.

============================================================================================

Shut down the Traffic in the EAST
Make the DB changes in the EAST { Be clear about the respective changes that are being made }
Once the media ear has been deployed , there is another code , that is being tested
What ever the content , we see the content , we need to see all that content on that web portal

=============================================================================================












No comments: