OSAM must make an API or a set of APIs available to users that can access diagnostic information from all parts of the pod.  It must be possible to search these APIs by date, time of day, customer ID, and other distinguishing attributes.

Alarms from the POD

 

Case 1 - Fiber connecting the Ethernet switch to the PON unit fails

 

 

 

 

1. Ethernet switch reports: Loss of signal, port #

 

1. PON device reports: Loss of signal, port #, through out of band connection since the in-band connection would be out of service in this case

 

1. OSAM reports: Loss of signal on switch port #, PON hardware feeder port #, service-affecting, and a list of customers affected by this condition

 

1. OSAM information: Retrieve historical alarms from the previous hour, day, etc. to look for telltale signs of failure

 

1. OSAM information: Retrieve historical syslogs from the previous hour, day, etc. to look for telltale signs of failure

 

1. OSAM information: Retrieve configuration of the Ethernet switch port and also the PON hardware uplink port

 

 

 

 

 

 

 

 

Case 2 - Feeder from the internet to the Ethernet switch fails

 

 

 

 

1. OSAM reports: Loss of signal on the Ethernet switch Internet feeder interface, port #, service-affecting

 

1. OSAM information: Retrieve Ethernet switch port configuration that is facing the internet switch

 

1. OSAM information: Retrieve historical alarms related to the Ethernet switch port facing the internet switch

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Case 3 - PON signal fails between the OLT port and the customer’s ONT

 

 

 

 

1. OSAM reports: Loss of signal on PON hardware port #, ONT ID, customer ID

 

1. OSAM reports: Signal power (light) levels on the affected OLT port.

 

1. OSAM reports: Be able to distinguish a single customer powering-down their ONT from a fiber cut.  Also, if multiple customers suddenly become disconnected, then we can assume that it is the fiber feeding the outside plant splitter.

 

1. OSAM information: Retrieve customer configuration from the PON hardware, including software release and customer ONT software release

 

1. OSAM information: Retrieve historical syslogs and alarms from the PON hardware to look for telltale signs of failure

 

 

 

 

 

 

 

 

Case 4 – Application Server Fails

 

The server hosting the voltha and onos applications fails.  In this case full service continues for existing customers, however; no new provisioning is possible and no maintenance information is available until the server is restored.

 

 

 

 

1. OSAM reports: voltha application down, onos application down

 

1. OSAM reports: Failover in process

 

1. OSAM reports: Failover completed, network operator services available

 

1. OSAM information: Retrieve status of the failover process – this should include the status of key programs shifting to the standby server and whether they have come up yet.

 

 

 

 

 

 

 

 

 

 

 

 

Case 5 - Common OLT hardware Fails

 

 

 

 

1. OSAM reports: Fan alarms.  If the box has more than one fan then the condition is not service-affecting.

 

1. OSAM reports: Power feeds.  If the box supports A and B feeds, and one feed remains up, then the condition is not service-affecting.

 

1. OSAM reports: If only one customer (or all customers on a split PON) is affected then OSAM reports the affected customers.  If common electronics fail taking out chunks of customers or all customers, then report a service-affecting condition.

 

1. OSAM information: Retrieve historical syslogs and alarms from Ethernet switch and PON hardware to look for telltale signs of failure

 

1. OSAM information: Console interface through which a user can bounce processes, ports, and or the entire PON box if necessary (during an evening maintenance window)

 

 

 

 

 

 

 

Case 6 – Internet Service Fails

 

The internet feeder facility is up, but internet service is down.  This is an insidious case because it usually involves another carrier’s facilities.  We need adequate tools to get the exact status of our equipment and how we see the internet signal to best work with the carriers to fix the problem.

 

 

 

 

1. OSAM reports: Valid internet signal not detected.  Do not generate alarms on behalf of the physical ports connecting the Internet serving switch and the POD switch if the hardware is up.

 

1. OSAM information: Interface through which the user can retrieve internet-related parameters like DHCP, DNS, and IP address configuration on the Ethernet switch