课件参考成果rosa copernicus4v4.0nxpowerlite

1、ROSA NMS 4.0ContentRosa overviewClient server systemAdding unitsFolders and MapsMessagesTasksComponents and configurationsUpgradesSecurityTroubleshootingROSA NMSSIMNMSVSMDeviceServiceSI / EPGROSA VSM SuiteArchitectureROSA NMS and ROSA EMFoundation of our Management SolutionElement Management Network

2、 ElementsCisco + 3rd PTY gearNetwork & ElementManagement ROSA Device ManagementDevice OrientedNMS EMROSA NMS and ROSA EM is the Element Management layer of our Video Service Management Strategy ROSA NMS and EM facts Increased service uptime N+M “Seamless” encoder maintenance backup (nearly visible)T

3、ypical fault-triggered (alarm) encoder switchover-time 2.5 secondsBackup for local encoded programs and turnaround servicesFlexible 1+1 and N+M encoder, receiver, DCM (1+1), etc backup Supports industry-standard audio/video routing switchersReduced operational expenseConfiguration managementReducing

4、 complexity and reduction of configuration mistakesOpen standards (SNMP, HTTP, SQL, DVB, etc.) basedFlexible integration of 3rd party equipment through SNMP & dry contacts (I/O)ROSA Network and Element ManagementOf the shelf Video Management Solution for our different markets Main HeadendIP / ASI Ba

5、ckboneIP / ASI RegionalRegional HESatelliteFiberIPATMA/V.HFCIP / ASI RegionalSateliteTerrestrialHUBTelcoCableBroadcastNOCROSA NMS clientROSA Copernicus hostingROSA NMS server softwareMain HeadendN x ROSA Elemement ManagerROSA EM Regional Headend / HUBDistributed Client SoftwareStatus and controlAlar

6、m MessagingRedundancy ManagementAlarm CollectionConfiguration databaseDevice ManagementRedundancy ManagementLocal ControlAlarm CollectionIntegration of different types of management interfaces (SNMP; hardcontacts, )Client/ServerWhat is a client server system - Install/upgradeDifferent flavorsClient/

7、ServerArchitectureServer Hardware Connecting the client: ProtocolsChanging the networksettingsLicensingSingle UserDevice Configuration ShellWhat is a Client/Server systemServer The server gathers and stores the alarms/messages/data from various equipment The server can control equipment by running T

8、asks or components The server will provide the requested data to one or more atttached clients The server keeps the configuration and data in a Database The server notifies the clients if new messages arrive by sending NOTIFICATIONS The server is the Driver-side: DLLWhat is a Client/Server systemCli

9、ent The client represents the data gathered by the server in a user friendly way A client is necessary to configure the serverDefining what data to be gatheredDefining what devices to be controlledDeleting data on the server A client does not need a databaseThe client is the GUI-side (.exe)What is a

10、 Client/Server systemClient: RosaRCDS Open system architectureRCDS = proprietary protocol used to control serial equipmentSoftware: Rosa.exeServer: CopernicusSoftware: ELMA.exe : Element manager Service Copernicus Service to startup the ELMA automatically after a reboot.Communication between client

11、and server is done over an IP networkWhat is a Client/Server systemMessagesMessagesClient/ServerWhat is a client server systemDifferent flavorsClient/Server (Rosa CS)ArchitectureServer Hardware LicensingConnecting the client: ProtocolsChanging the networksettingsSingle User (Rosa SU)Device Configura

12、tion Shell (Rosa DCS)Rosa/Copernicus: Client / ServerRosa client computer and Copernicus serverCommunication through IP-based networkCopernicus MKVArchitectureSeperate computersMultiple clients are possible (Licensed)Be carefull: working with 2 clients applying simultanious settings on the copernicu

13、sRosa/Copernicus: Client / ServerArchitectureMultiple servers are possibleRosa/Copernicus: Client / ServerArchitectureROSAClientLAN / WANROSA EMHUBNetworkElementsROSAClientEngineering ROSA Clients provide the overall view of the video network Copernicus is the high reliability server that hosts the

14、ROSA software ROSA EM at the HUBs manage the local control/backup of the HUB ROSA EM at the Master Headend interfaces to proprietary protocol, contact closure and SNMP enabled devices Copernicus servers are located in Master Head end One Copernicus server dedicated to Master Headend Standby Copernic

15、us server is located in Master HeadendROSAClientsROSAClientROSAClientROSA EMHUBNetworkElementsROSA EMHUBNetworkElementsROSA EMHUBNetworkElementsROSA EMHUBNetworkElementsROSA EMMain HeadendNetworkElementsROSA Copernicus(Standby)ROSA Copernicus(Main Headend)(x N)NOCROSA ManagementIn Large NetworksCope

16、rnicus Backup SupportOverviewCopernicus Server Backup Component Standard Package for Copernicus Backup/Restore since V3.0 B4 Automatic Backup of System data on central storage Manual Restore of data required to bring system back on-line.Copernicus High-Availability Solution Licensed Package for Cope

17、rnicus Standard and Large Systems Collocated and Non-Collocated (disaster recovery) Solution Automatic or On-Demand full system “take-over”ROSA NMS “High-Availability” SolutionSummaryKey Requirements:High Availability for Service Critical Operation (24:7 Monitoring, Backup Operation, Scheduling, Sta

18、tmux Control, Service Management, )Quick Recovery Easy RecoveryDisaster RecoveryMainStand-byManagement IPNo intervention to activate Hot Stand-by ROSA NMS server:Automatic or Manual Take-overAdditional Software component to synchronize both serversStandard Copernicus Servers, No Specific HardwareHig

19、h-Availabilitybased on Neverfail Partner Software Integration and SupportHeart-BeatNetwork ElementsEasy setup (no Shared Storage, no Windows Domain required, )Servers connected to LAN/WANFast failure detection using Heart-Beat connection between serversHigh-AvailabilitySummaryIP NetworkHeartbeatHear

20、tbeatCopernicus software is pre-installedMSDE (until MKIV)Standard SQL 2005 express edition on MK VElement manager software (elma)Rosa (client) software must be installed by the customer from the Rosa installation CDRosa/Copernicus: Client / ServerArchitectureInstalling Rosa on your PCRead ROSAInsta

21、ll.htm on the CDHave also a look in ReleaseNotes.htmRun setup.exe from ROSA directory! Do not install Rosa SU !Supported platformsWindows 2000 Professional/ServerWindows XP Professional SP1Windows XP Professional SP2 Firewall disabledWindows 2003 Server (since build 11)ROSA client, ROSA DCS, ROSA SU

22、, ROSA CSFROM BUILD 17Windows Vista is supported for the rosa client and a selected set of drivers (see release notes on CD)Supported platformsRosa client has been tested with IP security (INFO ON CD1)FTP_user account created since build 16Rosa :At regular intervals (every 30 seconds) a COM call to

23、the Copernicus is performed. If the COM call fails, ROSA will reconnect with the Copernicus. Server Availability Checking must be enabled in the ROSA Preferences dialog to use this functionalityClient/ServerWhat is a client server systemDifferent flavorsClient/ServerArchitectureServer Hardware Conne

24、cting the client: ProtocolsChanging the networksettingsLicensingSingle UserDevice Configuration ShellCopernicus MKIV hardwareMonitoring HWExample from remote PC or on the Copernicus Copernicus MKIV G3 hardwareDefault password: hpadminCopernicus hardware MK IV G4/G4pDefault password: same as windows

25、passwdCopernicus hardwareMonitor Copernicus hardware via RosaInstall driver ML350_G3Remote management solutionHardware Copernicus MKVML380: Hardware FrontROSA Copernicus MKV ServerHardware19” 2RU HP DL380 rack serverDual Core Intel Xeon Processor2GB RAMSlim line DVD-ROM Drive (8x/24x)2 x 72GB 10K rp

26、m SFF SAS hot plug Hard Drive (2.5)3 x RJ-45 Ethernet connectors (1 dedicated to iLO)Mixed Riser Cage (PCI-E/PCI-X) SoftwareOS = Windows Server 2003Pre-installed ROSA NMS Network Management Software PackageStandard System = SQL Server 2005 Express EditionLarge System = SQL Server 2005 Standard Editi

27、onOptions: Optional Redundancy Power Supply Kit Multi-port serial adapter kit 4xRS-232 / 4xRS-485 Multi-port serial adapter kit 8xRS-485Hardware Copernicus MKVML380: LED statusHardware Copernicus MKVML380: Hardware rearCopernicus Hardware: Options Copernicus MKV Standard Configuration:(2 GB RAM, Win

28、dows 2003 server R2 and SQL 2005 express edition)0 x Serial cards0 x Hot Spare0 x Redundant Power SupplyCopernicus Hardware: Options mended to use ROSA EM in case of serial connectionsROSA Element ManagerVersatile I/O interface108 digital inputs12 galvanic isolated digital inputs24 contact closure o

29、utputs8 analog inputs2 analog outputsAirco UnitPower Supply UnitTransmitterKits COP MKV:Multi-Port Serial Adapter (max. 2 installed in Copernicus MKV)The cable harness with 8 DB-9 connectors is connected to the 78 pins connector on the rear of the Copernicus.8 RS-485 ports4 RS-232 and 4 RS-485 ports

30、 Hot Spare DiskRedundant Power SupplyCopernicus MKIVG4p/G5 iLO interface* iLO Standard provides basic system board management functions, diagnostics and essential Lights-Out functionalityDefault : DHCP enabledRemote management solutionCopernicus MKIVG4p/G5 iLO interfaceILO2 interface Virtual text re

31、mote console (pre-OS only) Virtual Power Button Control Virtual Unit ID control OS independent hardware health status Integrated Management Log (IML) and iLO event loggingiLO interfaceiLO2 interface is always accessible, even if server is switched offHow to access: http:/ iLO interfaceAdd user name

32、and passwordCOP MKV:Using remote desktop on Copernicus MKVControlling remotely your serverHP has SW license for virtual KVM remote graphical console where you also see the whole boot up sequenceCOP MKV:Using remote desktop on copernicus MKVType in RUN: mstsc.exeFILL in the IP address of the copUse A

33、dmininstrator login en password of CopernicusCopernicus hardwareEach RS-485 port on the Copernicus has a pin adapter installedallowing for 1-to-1 connection to the devices e.g. flat cableImportant! Removing these pin adapters does not make these ports RS-232 ports. Do not connect the pin adapters tu

34、rned around. There is a black line on the Copernicus sideSerial connectionsCopernicus HW- Disk mirroring or disk shadowingsame data is written to both drivesRAID 1 is data redundancy. If one of the drives fails, the system can continue to run- Speedno increase or decrease -Disk Usage disadvantage: h

35、alf of disk capacity lostHarddisc BackupCopernicus configuration uses RAID 1Client/ServerWhat is a client server systemDifferent flavorsClient/ServerArchitectureServer Hardware Connecting the clientChanging the networksettingsLicensingSingle UserDevice Configuration ShellProtocolsUnderstand how the

36、client communicates with the Server.Following protocols are usedTCP/IPFTP Necessary to understand Connection problems- Notification problems (sending messages to the clients) Firewall issuesConnecting the client All communication between PCs will be done based on the IP addressesHostnames: Each PC a

37、lso has an unique (in the network) hostnameHostnames are easier to remember than IP addresses communication between client and Copernicus is based on Hostnames A hostname is a name given to the PCConnecting the client TCP/IP: Hostname When 2 computers want to communicate, by using the hostnames, the

38、se names have to be translated into IP Addresses2 Ways to translate hostnames into IP addresses (ex Client1 want to communicate with Client2)Connecting the client TCP/IP: Hostname Possibility 1 Using a DNS serverOne server will translate all hostnames into IP addressesWhen a computer want to communi

39、cate, it first asks the DNS server the IP Address of this hostnamePC_Darwin ?PC_darwin = 00Connecting the client TCP/IP: Hostname Possibility 2Using the hosts fileOn each PC 2 files containing IP address and hostnames are storedThese files can be found at: c:windowssystem32driversetcConnecting the c

40、lient TCP/IP: Hostname Communication Tips and tricksUse the command prompt - ipconfig: shows current IP address - Hostname: shows pc hostname - Ping : check communication to other PCPing IP address Ping hostnamePing a : retrieve the hostname Connecting the client TCP/IP: troubleshooting FTP: File tr

41、ansfer protocol (port 21)Used for Connection, license checkUpgrading and installing driversUpgrading Rosa/copernicus systemSynchronisation between client and serverBuild 14 provides possibility to choose between passive and active FTP (to avoid firewall issues)Can also be used to remotly connect to

42、the copernicus directory (transfert of traces)Connecting the client Protocols: FTP Check the ftp connection by using the internet explorer:ftp:/Administrator:Connecting the client Protocols: FTP : Distributed COM uses hostname ! has launching rights of administratorConnecting the client Protocols: F

43、irewalls can block ports that are used for communication between client and server or between server and devicesRead FAQ on CD to check used portsDiscribtion of used ports between client and server and the ports used between copernicus and devicesPossible to limit the ports in the registryTest port

44、communicationtelnet from client to server or server to client to a specific portNetstat an shows the ports that are connected or listeningConnecting the client Firewalls When a Copernicus is shipped it has the following default settings:Hostname: COP00000 (until cop MK V) RS + HP serial number on co

45、p MKVWindows login:Username: AdministratorPassword: copadminRosa loginUsername: AdministratorPassword: wGb0DvcLdMWarning: Do not change the hostname in Windows (After connecting with a client) Connecting the client Copernicus Default settings Connecting the client Adding a copernicus to a Rosa clien

46、t Local serverAdding a copernicus to your ROSA systemConnecting the client Adding a copernicus Name to be displayedHostname of Copernicus(not IP!)Connecting with Copernicus serverConnecting the client Copernicus Default settings Fill in username. and passwordPassword: - first time connection = the d

47、efaultAdministrator user password (see CD)- Login with Rosa account:Security settings are applyed to the rosa User logged inConnecting the client Connection example Unit overviewMaps overviewMap DetailAutomatic connect possible after restarting Rosa clientCheck for unreachable serversConnecting the

48、client Copernicus Default settings Connecting the client Copernicus Default settings Since build 15 there is the possibility to use Passive FTPClient/ServerWhat is a client server systemDifferent flavorsClient/ServerArchitectureServer Hardware Connecting the client: ProtocolsChanging the networksett

49、ingsLicensingSingle UserDevice Configuration ShellChanging the Network settings Network settings should be configured by using ROSADo not configure computername and administrator Password directly on the copernicus serverTCP/IP settings can be changed For copernicus MKV: using the rosa client For co

50、pernicus MKV: using the Remote DesktopSelect the Copernicus you want to work on, and go to “server”Changing the Network settings Always change the Copernicus network settings via Rosa ClientChanging the Network settings Change the IP address of the COPERNICUSChange the computer name of the COPERNICU

51、SChange the WINDOWS password of the Administrator on the COPERNICUSSynchronize the clock of the Copernicus with the clock of the Rosa client, or visa versaClient/ServerWhat is a client server systemDifferent flavorsClient/ServerArchitectureServer Hardware Connecting the client: ProtocolsChanging the

52、 networksettingsLicensingSingle UserDevice Configuration ShellLicensingLicense file protects “software products”Device driversTask driversAdditional componentsLicense file is needed for each CopernicusEncryption with unique HostID on each CopernicusHostID changes when network card is replaced!Rosa c

53、lients do not need license file but limited on license agreementRosa SU and DCS do also need a license fileLicense file is needed for each driverEven free drivers need a license, license must be activatedLicensingIf additional or new licenses are neededGet HostID from connected CopernicusPurchase ne

54、w licenses related to this HostIDProvide ordernumber and Hostid to the EUTACAfter reception of new license file, install itLicensingDriver status is OK if license is available.Can be verified in Installed Drivers (control D)STATUS = OKCheck if licenses are OK or in errorClient/ServerWhat is a client

55、 server systemDifferent flavorsClient/ServerArchitectureServer Hardware Connecting the client: ProtocolsChanging the networksettingsLicensingSingle UserDevice Configuration ShellRosa/copernicus is running on one machineNo connection to other clients or higher management systems Used for field instal

56、lation, field troubleshooting or demoTo be used on personal Computer, no special HW requiredSingle User ! No SNMP agent task !Client/ServerWhat is a client server systemDifferent flavorsClient/ServerArchitectureServer Hardware Connecting the client: ProtocolsChanging the networksettingsLicensingSing

57、le UserDevice Configuration ShellStripped Rosa/copernicus configuration toolOnly to configure equipmentNo maps, no message loggingFree license for equipment that can only be configured through Rosa/copernicus (example: Ilynx;polaris)Default license delivered on Rosa/copernicus installation CDDevice

58、Configuration ShellContentClient serverAdding unitsFolders and MapsMessagesTasksComponents and configurationsUpgradesSecurityTroubleshootingRosa CopernicusAdding UnitsAdding UnitsUnits needs to be mapped on the copernicus before they can sent messages or be controlled by the copernicus serverDiffere

59、nt Protocols for equipment is availableDrivers needs to be installed before a device can be mappend on the copernicus serverThe protocol Driver (RCDS,SNMP,IIOP .)The device Driver (Titan MKII, XDQA, DCM .)ProtocolsAdding UnitsA protocol is a “language” that the Copernicus will use to communicate wit

60、h the different devicesA protocol driver is the “definition” of this “language”Installing a protocol driver in the Copernicus enables the Copernicus to talk that “language”8 serial portsRCDSProtocolsAdding UnitsOpen the drivers window, by clicking the drivers button (or press control D)Select instal