NE, Version Issue Title Issue Description Action Raise Date

Wavekeys are unique within a keyspace.

At present in OMS, we use a global
namespace for the wavekeys. Do we have
to manage multiple namespaces? How do
they map with OSPF Areas? Which
WavekeySpace customers have more than one
All: (Srini/Bala) namespace? what does PhM do?
Pedja/Dat to open up when multi-
domain will be needed at
customers or when scaling needs
arise. 12 Aug, 2010

Network application and how framing is

done. what the conditions are. (Mobile
Backhaul )> This will help map the
usecases, user flows to OMS objects,
commands. Particular importance to
packets tagged as 8100 incoming or 9100
incoming on the 10Gbe port. In addition
need to understand the back-back config
through the backplane. (also working with
All, PSS4 Q-in-Q (Srini) Song/Bin Zhang on this). Closed. 12 Aug, 2010

Does webUI support traffic classification

based Q-in-Q provisioning? when that is
supported, is the classification done at
the individual flow level or at the port
level for all flows? For port level tagging,
is it done at the client port level or per- Closed. Need few bits of
All, PSS4 Q-inQ flow? [Srini, Linda] information. See status. 17-Aug-10

If two rings are connected with either a

10G or 10x1Gb interworking, where are
all the STags pushed and popped? Or can
the S-Tag proceed un-popped to the
Q-in-Q Network second ring and popped at the far end?
PSS4, PSS32 configuration. [Srini, Linda] Closed. 17-Aug-10

Releases (Tom Is there a release 1.5? or just 1.0.5? if

PSS4 Thomas) 1.5? what additional features. Closed. 12 Aug, 2010
 Are there traps to indicate commissioning
has started? can this be added if it is not?
This will aid user/OMS in knowing when
the commands can be sent and when not
and help explain to the user why some
tasks have to wait. Also to know whether
CommissionedStat a testLambda is being set up in a linear
All us (Srini/Bala) chain. On going. 12 Aug, 2010

The NE can support 88 channels if ITL

88 channel card is installed. Can an attribute be
support. added to the NE or the LD ports to
(Srini/Tom indicate that the NE can now support 88
2DFOADMs Thomas) channels? Closed 13 Aug, 2010

Can there be E-SNCP between 3 line ports

Q-in-Q E-SNCP on PSS-4, PSS-32 in the 10GbE Lan mode? Closed 18 Aug, 2010

BackPlane What are the constraints for connecting Closed. Kathie will send updated
connectivity 11DPE12 cards to the backplane> list for PSS36. 18 Aug, 2010

BackPlane what connectivity maps to XAUI1 and

connectivity 11DPE12 XAUI2? Open. Kathie 23 aug 2010.

7750
interworking 7750 interworking Do we deploy SVAC/1830 interworking? Open. pedja 23 aug 2010.

Discrepency between FM document and

webUI/Protection group document
indicating whether the QinQ mode
Q-in-Q ESNCP ESNCP supports SNCP Open. kathie/shangai 24 aug, 2010

How can we differentiate SVLANID setting

where packet is manipulated as opposed
where the SVLANID is used to classifu (in
Q-in-Q SVLANId setting the transit node). Closed. 24, Aug, 2010

FE is PSS4 and not in PSS32 is that

correct?
11DPE12 Client side FC800 - similar discrepancy Closed. 25, Aug, 2010

confirm that URU and propagated alarms

URU alarm Alarms are supported. Closed. Further work.(indu/ray) 25, Aug 2010

Dat - determine if further

information is necessary from
BT Mib Issue BT Requested a MIB comparison WDM or NE perspective. 10/27/2010
 PSS Nes: We always get a generic error
message that says “Commit failed”. This
SNMP Error does not give user any indication of what Look into improving SNMP
Messages failed and why it failed. provisioning error messages. 10/27/2010

Status of There are 3 features listed for the

11DPE12E 11DPE12E card. Are all these features
3.5/3.6 features supported in 3.5 and 3.6. Dat Answered 1/6/2011

Backplane back-to-back support. Is there

a parameter to specify whether or not
this backplane support can be used or
not? Also, does 11DPE12 support this
3.6 11DPE12E configuration. Dat will answer 1/6/2011

Is the cross-connect on the MVAC

3.5 MVAC unidirectional or bidirectional? Dat will answer 1/6/2011

To what extent is 1830 implementing TCM

3.6 TCM functionality. Dat will answer 1/6/2011

Are there upgrade proceedures necessary

3.5 WTOCM upgrade for WTOCM? Dat will answer 1/6/2011

Retrieve path OCH. Need equivalent in

3.6 Retrieve Path SNMP. Dat will answer 1/10/2011
 ResolutionDate Status

OMS not supporting in MNT4. At present

this is OK (confirmed with pedja). When
the domains need scaling or is
partitioned, A request has been made to
be able to retrieve the key-namespace
25 Aug, 2010 from the NE.

25, Aug 2010 Mail thread describing the feature.

The mapping is supported implicitly by

setting the CEVLAN on client port,
VTSXC and SVLANs on Line port. To map
entire port to SVLAN, no CEVLANs are
provisioned on client side (need to
complete this sentence with correct
25, Aug 2010 answer.).

The tagsa are pushed at the ingress line

side and popped at the client side
before egress. At the 10GbE LAN mode,
it behjaves as a client port. Can be set
to be transparent.

they are both the same. two new OTs,

11DPM12, 11DPE12E (from R3.5) and Y
Cable protection. (Date availability for
testing )
 Need to continue working on operator
use cases and how it can be improved.
Will be looked at after the immediate
requirements are looked at and
completed.

18 Aug, 2010 1350OMS solution.

25 Aug, 2010 No, they cannot.

2-3, 4-5, 6-7,8-9, 10-11,12-13, 14-15, 16-

17, 20-21, 22-23, 24-25, 26-27, 28-29,
30-31, 32-33, 34-35
XAUI1 to XAUI1, XAUI2-XAUI2 in each
23 Aug , 2010 pair.

Need to understand whether there are

any constraints in cross-connecting
between ports of the card or are there
any restrictions (or is it entirely internal
to the NE).

According to pedja, the SVLAN 1-32 can

be SNCPed. Srini's recollection - that
was only for OAM/Losprop. Hence the
need to confirm.

Based on connectivity to a client side or

a line side (OTU)

FE in PSS32 R3.5
FC800 not in either

URU supported. But details of what is

sent and what is propagated need
further clarification
 QinQ feature is supported in R3.5 and all
1/6/2011 3 features are supported in 3.6.
 18-Aug-10
WavekeySpace:
Dat to work with PhM to undrestand support and provide
answers.
Q-in-Q issues:
Srini to make a list of questions for Song and Minho and get
answers.

Dat to confirm that the 'traffic classification' based STag

assignment - in FM document but not in WebUI requirement is or
is not a management requirement (need some answers for the
MIB and SNMP commands as well).
PSS4 Release Numbering:
Resolved.
CommissioningFlag:
ongoing interworking work item on what OMS can support to the
operators and what we may need to enhance in the operations
between 1350 and NE and the interfaces.
2DFOADMS:
1350 to do homework.

Q-in-Q questions:
taggingProtocolId:

if this is used to setup the acceptable tag on an incoming frame,

should this be done at a port level and not a card level? Lets
imagine that Timewarner is using the same aggregation ring for
both VzW and AT&T, then do we expect them to connect the
customer traffic to different cards or different ports of the same
card? If same card, then each port could have to accept different
incoming tags based on the customer networks.
STag Setting choices:

Port based versus Traffic Based. As requirements stand (from

webUI), I understand that the port based is used, where the S-
VLANID is configured on a line port vts (based on connectivity to
the client side (or line side) GbE Port. For line-line connectivity, it
is clearly a transit node and shouldn't the S-VLAN ID have been
set already at the ingress node? Or do we expect the user to
keep setting this on all line ports along the EVC? For E-SNCP,
as things stand now, we need to set up the Tag on both line
sides separately. (more chances for user error). I think it may be
better to set this at the client port (which is ingress into the
network) and can be used by the different line ports to manage
the flow.
Do we need to support Traffic based tagging of SVLANID? (it is
present on the FM requirements, but not in WebUI
requirements).

If we do support Traffic based Tagging: Is the table (A set of rules

to map CVLAN to S-VLAN), one per Line-VTS? In real life
operations, will there be a set of such tables attached to different
flows. (i.e multiple flows share the same rules?). How do you
envision operators using this?
Push/Pop of SVLANID:
 Lets consider an aggregation ring connected to a Core WDM
Ring. These two can be connected in two ways: (a) with a 10GbE
LAN connectivity, (b) wth 10*1GB. My understanding (from a
previous mail from song) is that with a 10Gbe, we do not have to
pop the SVLANID. Do we need to do anything on the card to
prevent that from doing this or to accept a 9100 frame? for the
1GB interconnectivity, we will have to pop as it exits one ring and
ingresses another. Do we use the same scheme in the second
ring as well. (keeping in mind that the fibering may not be
symmetric).
Ring interworking:

In the previous two-subnetwork example, can the Core Metro

ring be a full ethernet ring (instead of a WDM ring?) In that case,
will the 10GbE still be transparent and not pop the SVLANID?

Will we expect the Core Metro Ring to be a non-bridging network

as well (where we have a full EVC transparency).

On the MSC side, do we still need the E-SNCP to be closed? (2*

10GB LAN from the metro ring and 1*10GBE through to the
Router connected to RNC). Can we create E-SNCP between 3
Line ports VTS in such a case? (kathie?)
PSS-32 Backplane connectivity (kathie?)

When the two 11DPE12 cards are connecting through

backplane, I understand there are rules on which slotId the cards
should be to be paired. is that available via the MIB or is it pre-
defined.