Announcement

Collapse
No announcement yet.

Keeping the equipment going during a shutdown

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #61
    Originally posted by Leo Enticknap View Post
    With everything on their factory defaults, the two theater network NICs hooked directly to each other (either using a straight shot crossover cable or through a switch - I don't know if those NICs are modern enough to be able to deal with a straight shot patch cable), both servers running the same version of Show Manager, and the theater network designated as the management network on both servers, they should be able to see each other and transfer DCPs between each other. However, if one of them does have 192.168.1.2 set up as the NTP server, then someone has been changing settings from their factory defaults in the past; so all of the above needs checking out.
    Those ports are 1000Base-T. The 1000Base-T standard uses all 8 wires of the UTP cable and to "simplify" things, Auto-MDIX (auto-crossing) has been made a mandatory feature. So, yes, a "straight shot" cable should work. In practice, though, I've found many of the older generations of Gigabit Ethernet adapters, especially those without firmware updates, having trouble with Auto-MDIX, especially between vendors, but that shouldn't be the case here.

    Comment


    • #62
      I gave some incorrect information in my last post. The NTP Configured server on Server 1 is actually 192.168.241.2. No wonder Leo questioned it.

      I put a replacement drive in server 2 and after it booted up it rebuilt the array with four good drives (well..one still with 1 reallocated sector.)

      The time on server 2 was about a minute or more out after having set it correctly last week so today I went into the config screen and changed the NTP server address to Show player 1's IP address, 192.168.1.2.
      When it booted up and I logged into Show Manager, the Theatre time on Server 2 was now exactly the same as Server 1. The system screen in Server 2 now shows the NTP configured server as 192.168.1.2 and the NTP connected server as the same. After half an hour or so it was about 1 second out so I logged out and then back into Show Manager at which point the time was again synced to server 1.
      (I would have thought that the server clock would not drift so far out in such a short time).

      So there is certainly a connection there but I still can't get the two DSS100s to see each other's content.

      It appears that there is a setting incorrectly configured in Server 2 but I have no idea what it is. It would help if I knew exactly what all the address settings in the config screens actually related to.

      The other issue I have is with my Christie projector (CP2000 ZX) which comes up with a red error light when I power up the UPS. Last season it did the same but then one day the error just cleared itself. The last few weeks were OK in that the projector came on line each time I powered it up. Of course this means that I am currently unable to play any test content.

      I could leave the equipment on full time as I did during the season but the power bills tend to be astronomical.

      Comment


      • #63
        If, on the theater LANs, the two servers' addresses are 192.168.241.3 and 4 (i.e. their factory defaults) and they still won't see each other to transfer content, the only other things I can think of to check are that both are running the same version of Show Manager, and that both have the theater LAN designated as the management network.

        Comment


        • #64
          Like mentioned before, have you checked if the subnetmasks on both machines match each other? They absolutely need to be the same on both machines, or otherwise there will be trouble.

          Comment


          • #65
            If everything is default, the theatre network auditorium 1 should be 192.168.241.3, 255.255.255.0; Auditorium 2 should be 192.168.241.4, 255.255.255.0, Default gateway of 192.168.241.3 (which points it at auditorium #1). You would then run the config script on auditorium 1 and set it to be the TMS on the network. auditorium 2 should remain as SMS (you never want two TMS units on the same network). About 10 mins after booting up, you should see the units start talking to each other and able to share content between the two Show Stores. If both units are in SMS mode they won't ever connect to share content/cues/schedules/etc.

            Comment


            • #66
              Aah... that would seem to be the cause of the problem. Thanks for that. The main server has always been set to SMS which I guess didn't matter when it was the only Show Store. So setting Server 1 to TMS should fix the problem.

              When I last updated the config script in auditorium 2 I tried setting the addresses to 'auto'. When it booted up, the Show store address and Theatre link address had both changed to 192.168.241.100. It seems that whenever I save the script it changes the IP address. I gather that I should actually type in the addresses, which I had done originally but was clutching at straws when they still would not connect.

              I have always been reluctant to mess with any of the settings in the main cinema system as I have no technician available to assist if I stuff things up. Still, I have six months to fix it if I do.

              I'll have another crack at it next week.

              Comment


              • #67
                Sounds like a good plan.

                As to the second server being set to 192.168.241.100, that is probably because the default base address has been changed. Run the config script and move through until you get to the networking settings section.

                You should see that you are in AUTO for most of these settings. Scroll down to "13 Advanced configuration" and press enter. On the advanced page check the following to ensure they are at default:

                2 Internal base address [192.168.0.0] <this is where I think someone might have put an incorrect value>
                4 External base address [192.168.241.0] <this is where I think someone might have put an incorrect value of 192.168.241.100, which is why you are seeing that address>

                These two values tell the AUTO setting where to start. The number here would be the first value for auditorium 1, then auditorium 2's IP addresses would increment up by 1.

                If you have 2 and 4 correctly set as I've shown above, then you know what the IP addresses are going to be. You could also just change from AUTO to manually set addresses which would not use the base address info at all

                Our team is able to help if you need it. CinemaSupport@dolby.com or 1-415-645-4900.

                Mike

                Comment


                • #68
                  Thanks Mike.

                  I changed settings as per your advice and had them talking to each other in less than ten minutes.

                  I did get an NTP WARNING on Server 1 when I changed it to TMS. I previously set 192.168.1.2 as the configured NTP server on server two and it now syncs to Server one.

                  Server one has always shown the NTP configured server as 192.168.241.2 but I don't know what address that refers to. There is no NTP connected server. There is no external NTP server as I do not have a permanent internet connection. So I assume that I need to manually set the NTP server address to the Theatre interface address of server 1.

                  Prior to setting up the second DSS100, Server 1's current secure time display in the auditorium tab was accurate to the exact second and secure time update was enabled. I have no idea where it got the exact time from as I never set it or connected it to an external NTP server. it would be interesting to know where it got the time from. After connecting the second server the current secure time on server 1 became unavailable.

                  Comment

                  Working...
                  X