說明xpon培訓(xùn)2018新功能3jl

1、This is a placeholder image only. Please select an image to reflect the content of your PPT presentation. Visit our approved corporate photography collection on the Store at: Philippe De BontridderJuly 20143JL-00100-0020-DFZZA5520 AMS Delta Training R9.2.30 / R9.3.10For internal use onlyAGENDAIntrod

2、uctionFunctional ImprovementsRobustness/Cluster/Security ImprovementsNE Specific Improvements1. INTRODUCTIONIntroductionThe main objectives of the 5520 AMS R9.3.10 release are:Features addressing AT&T TL9000/quality/platform migration to LinuxFull Linux support, including GUI, clustering and geo red

3、undancyFull next-generation SDC support (not covered here, see 3JL-06001-CAAA-WCZZA)Full HDM Lite supportPreliminary virtualization supportImproved support for the China marketSupport of new NE releases: ISAM FGN4.4General availability release (R9.3.0 was a LA)Migration path to R9.3.10:from 5520 AMS

4、 R9.3.0 (LA), R9.2.30, R9.2.10:Sparc to Sparc, Sparc tox86 toand x86 to x86Solaris to LinuxThe training has been recorded. It can be found here: 2. FUNCTIONAL IMPROVEMENTSThe purpose of this feature is to trigger actions or to alter the alarms (filtering/discarding alarms, severity changing, script

5、launch on alarm, auto-acknowledging alarms). For example:When DG alarm is reported to AMS, AMS will check if this alarm is MDU DG alarm, if not this alarm will be discardedWhen an INACT alarm is received on an ONT, append the content of the Current Reporting State to the Additional Info/Text field o

6、f the alarm. This helps discriminating a real fiber cut from other problemsSolution5520 AMS allows to define alarm rules that include the following:Active rules (max. 20) are evaluated one after the other for each alarmAlarm rules (1)What to do ? Discard the alarm Modify an alarm parameter Append in

7、formation to the Additional Text Call a scriptOn which alarms ? Filter based on alarm attributes Filter based on attributes of the object reporting the alarmAlarm rules are added via the Alarm Rules view (from the Administration perspective).Move the rules up/down to define in which order the rules

8、will be evaluatedTo help you detect performance hits, counters are added to the view. More detailed counters are available in the EMS Performance Monitoring viewClick on the icon to check if the rules are still valid after an AMS upgrade or new NE plug installedAlarm rules (2)Adding a new ruleOpen t

9、he Alarm Rules view Give it a nameSelect an actionBy default the rule is ActiveSelect a filter based on the alarm or on the source of the alarmClick on NextAlarm rules (3)And populate the parameters for the action you selectedClicking on Next will display a summary before you can click on FinishAlar

10、m rules (4)ProblemSome ANSI customers report all their alarms to OSSs in UTC. The ALU 7342 GPON NE is the only one that reports the alarms in local time since time zone management is enabled (needed to have the phones connected to ONTs displaying the local time)Solution7342 GPON NE R4.9 has an extra

11、 parameter5520 AMS can set it:New GPON R4.9 NE Plug Settings:and show UTC times:New Time Zone Setting: Alarm timestamps in UTC“GMT” or “NE Local Time”ProblemIn the AMS, the OSWP prefix name is always “OSWP” even if in the NE “L6GP” is used. This is confusing.SolutionYou can specify the OSWP prefixwh

12、en creating the NE SW Releaseby modifying the NE SW Package for already existing NE SW Releases Improvements to NE SW Management (1)ProblemThere is no limitation on number of NEs that can be included in a single NE SW Download operation. However there is a limitation for the NE SW Activation command

13、. The current limitation is 10.SolutionThis limit for the NE SW Activation is increased to 50 NEs. Improvements to NE SW Management (2)ProblemThe NE allows empty Planned Variant in the ONT SW Version Control Table, but the 5520 AMS always fill it in with “DO” when we right click on an ONT SW package

14、 and launch Align Version Control Table. If one uses the ONT migration scripts (delivered by the ISAM team) ontDownloadAndActivate.pl or stageont.pl, they same will happen.SolutionNew attribute Auto manage the ONT Planned Variant (always use one of DO, SIP, H248,.) in NE Plug Settings Improvements t

15、o ONT SW Management (1)Note that 5520 AMS is aligned with the NE scripts, NE improvement is tracked by ALU00182286New attribute Planned Variant in ONT SW MONew attribute Planned Variant in Improvements to ONT SW Management (2)the Add ONT Release Mapping DialogParameters only available if Auto Manage

16、 is offCut-ThroughMuch faster than before Correct handling of the window width: tables do not wrap anymoreCorrect handling of the cursor: backspace, up/down left/right arrowsEMS Performance Monitoring graphs:A counter returns an integer that grows over time. For example, for a counter that tracks th

17、e number of ing alarms, the number in the counter will increment by 1 every time a new alarm reaches the AMS. The EMS Performance Graph polls a configured counter every 20 seconds, subtracts the last number it got, and divides it by the number of seconds (20). This gives us a number, in instances pe

18、r second, in which this event ( ing alarm) has occurred. Counter are displayed as “rates”A gauge integer will go up an down according the variable it tracks. For instance, the current number of logged in users is considered a gauge. There is no math done on a gauge object, it just takes the number p

19、olled and graphs that numberBug fixes related to counter/gauge usage + better help at the bottom of the graph + detailed explanation in Customer Doc (especially on aggregating values)Other improvements (1)Easier selection in big listsIf the list of items that can be selected in a list 15 then a sepa

20、rate dialog with inline text search is displayed instead of the standard drop-down widgetBetter coverage of keyboard acceleratorsDate/Time widget can be filled in without mouseCheckboxes and multiple selection lists selections are clarified in the User GuideOther improvements (2)3. ROBUSTNESS/CLUSTE

21、R/SECURITY IMPROVEMENTSNetwork Slot LT Edit split in:Network Slot LT XXX Troubleshoot: Allow to lock/unlock/reset the XXX LT boardsNetwork Slot LT XXX Edit: Allow all other operations like plan/unplan on the XXX LT boards (one need Network LT Other Edit to plan an empty slot)Network Troubleshoot spl

22、it per transmission technologySecurity functions split per transmission technologyFunctions build on top of each otherSome customers have a lot of setups (i.e. a lot of AMS clusters) and it is difficult to know if all the software is installed/activated on each machine.SolutionSave a reference SW co

23、nfig in a file (e.g. from a machine in the lab)Copy that file on all servers and launch the checkChecking that all AMS software is correctly installedThe 5520 AMS has been tested in the following environment:Linux (RedHat):VMWare ESX 5.1Simplex / Cluster / GeoSolaris (Sparc/x86):No virtualization su

24、pport !NotesAn AD configuration does not make sense in virtualized configurations. In fact they are contra-productive as smaller VM images can be moved to other servers with more flexibility. Also there is no extra cost by splitting AD in a A and a D part as RedHat licensing is based on physical soc

25、kets in the server.The cluster network can be a pure virtual network without any connection to a physical ethernet port.The shared Storage can be either a physical disk/volume/lun or something virtual (VDI)VirtualizationProblemThe NE is returning immediately an SNMP response even if the operation is

26、 notfinished yetin the NE.Subsequent SNMP requests will not succeed.Examples: when services involving an IGMP Channel or a VLAN association resources are deleted through APCSolution5520 AMS accepts a file per NE agenttype/release with a list of attributes and their corresponding delay value (in ms),

27、 per managed objects. If delivered by ALU R&D: in the NE plug itself (e.g. for IGMP Channel creation in GPON 4.8/4.9: 2000ms)ALU TEC Support: in $AMS_EXTERNAL_SHAREDDATA_HOME/ne/nedelaysconfigThe content of the file is loaded in the system via the JMX consoleFile format (per row): ,+ E.g. ont,bponOn

28、tSerialNumber,300 or vlanPortAssociation,create,200,delete,200File name: -attribute-delays-config.csvE.g. GPON.4.8-attribute-delays-config.csv, IHUB.4.5-attribute-delays-config.csvConfigurable SNMP latency (1)For internal use onlyOnly for 7342 GPON R4.7 or higher and ISAM R4.4 and aboveThis is a bet

29、ter alternative than the Latency parameter in APC that is applied to all requests of all NE type/releases. So, set it to 0Use Case: The TEC engineer contacts ALU R&D to have an analysis. Then, he:createsa -attribute-delays-config.csv file,adds a line for each Managed Object he wants to apply a delay

30、,copies the .csv file to the $AMS_EXTERNAL_SHAREDDATA_HOME/ne/nedelaysconfiglaunches the JMX console using the http:/:8080/jmx-console URL, and enters the admin credentialsclicks on the service=MObjectSnmpAttributeDelaysCacheService in the application.snmp.runtime.support sectionenters the NE Family

31、/release in the correspondingparameters of the reloadNePlugAttributeDelays operationclicks on the Invoke button of the loadNePlugAttributeDelays operationresumes its normal operations to see the effect of the configuration changesConfigurable SNMP latency (2)For internal use onlyProblemNE is shown w

32、rongly as isolated in 5520 AMS. This usually occurs when NE is busy on long operation (5520 AMS has sent SNMP request but the NE is taking time to respond, e.g. retrieving ONT data via the OMCI channel) and AMS polling happens during that long operation. Since the timeout settings for polling (defau

33、lt timeout = 12s) are much lower than for normal SNMP requests (default timeout = 56s), when this occurs we are wrongly considering that the NE is isolated, while it is not.SolutionWhen the NE is not isolated, polling uses the regular timeout (56s by default), when the NE is isolated, polling uses t

34、he short timeout (12s by default)Supervision Settings wording is adapted to reflect the above behaviorLess NE isolation alarmsProblemIf the AMS is slow, we would like to see the EMS Performance Monitoring graphs. But they consume GUI resources and may even not work if the system is loaded.SolutionEx

35、port the applicationStatistics_ files to .csv so that they can be imported in MS-Excell (or alike) to draw the graphs.EMS Performance Monitoring graphs in .csvFor internal use onlyProblemWhen using the NBI, too many actions pollute the Action viewsSolutionA new value for the action “Type” is added:

36、“NBI”By default, the view is filtered to hide the “NBI” actionsIf one clears the filter, too many actions would be present in the action view degrading its performance. Consequently, paging is added (page size = 1000 rows)Action Manager4. NE SPECIFIC IMPROVEMENTSProblemThere is a need to have a sing

37、le screen containing all the ONTs of a PON and also a need to manage these multiple ONTs with minimal number of clicks. Customer wants to compare all the ONTs in a single viewSolutionThe PON Port table view shows 2 tables: one with all ONTs, one with the services on the selected ONTGPON/EPON Port: M

38、ultiple ONT displayProblemWhen using a G6-GPON link, the 5520 AMS computes the VoIP Client IP address depending on the ONT and PON port. This algorithm cannot cope with more than:4 PON ports/board.64 ONTs/port2048 NEsSolutionNew IP address scheme: 2 subnets (i.e. IP Addresses) per G6-GPON associatio

39、n, each subnet with its own IP Prefix OR parameter to use 1 subnet per G6-GPON association if the number of ONTs/PON port is limited to 32.In the “Admin” tree, the “NE plug settings” for the GPON R4.9 allows 2 schemes for computing these IP addresses. The parameter “VoIP Client Address Allocation St

40、rategy (For G6 Only)” in the “Miscellaneous” section has 2 possible values:“Max. 4 PON Ports/Board” - 1 subnet“Max. 8 PON Ports/Board” - 2 subnetsGPON: 7342 R4.9 - GLT8-A, a 8 PON boardOnly relevant if Nr of ONTs/port is not limited to 32When creating an ONT in a 7342 GPON NE R4.6 or R4.9, there is

41、now an option to create cards for the M-300-A MDU ONT.GPON: Create ONT cards for MDU (M-300-A)ProblemWhen the SLID is used in HEX mode, TL1 always returns a 20 digit string, padding the entered value with 0s. On the 5520 AMS these padded 0s are not shown. So, the 5520 AMS does not find any matching

42、SLID when a 20 digit SLID is searched for. SolutionAlways display 20 digits when the SLID is used in HEX.GPON: Align SLID display between TL1 and AMSProblemCustomer finds the ONT column in the New ONTs table and tree confusing. End users are assigning new ONTs to the ONT position based on this New O

43、NT ID when they should not be doing that.SolutionThe friendly name of the New ONT“ object is changed in the Network Tree: the ID is replaced byONT: the serial number of the ONTEPON ONT: the MAC address of the ONTThe ID column is removed from Table viewGPON: New ONTs should not have an IDAMS supports GSIP R4.7 and R4.8 on the GPON and ISAM plugsNote that