01 G06439

DOI-G06439
SpectralWave
UNIVERSAL NODE
BROAD BAND MANAGER
RELEASE 8.6
RELEASE NOTES
NEC Corporation
7-1, Shiba 5-Chome, Minato-Ku, Tokyo 108-8001, Japan

TEL: +81-3-3454-1111
FAX: +81-3-3798-1510
TELEX: NECTOK J22686
EMAIL: [email protected]
DOI-G06439
The information in this document was approved by the engineer(s) listed below
and was intended to be complete and accurate at the time of printing. However,
information is subject to change.
This document contains proprietary information of NEC Corporation,
and is not to be disclosed or used except in accordance with applicable
agreements. Please contact NEC Corporation or the project contractor.
1st Edition
July 2004, approved by H. Momiji of NEC-BBN-CNW
Copyright 2004 by NEC Corporation

All rights reserved.
Printed in Japan
DOI-G06439
U-NODE BBM RELEASE 8.6: RELEASE NOTES
SpectralWave U-Node BBM
Contents
1. SUMMARY
1-1
2. VERSION INFORMATION
2-1
2.1 Firmware Versions .............................................................................2-2

2.2 CID Application Software ..................................................................2-3
2.2.1 Version ................................................................................................ 2-3
2.2.2 Applicable Operation System .............................................................. 2-3
2.2.3 Available Functions ............................................................................. 2-3
3. FEATURES
3-1
3.1 Shelf Types .........................................................................................3-2

3.2 Interfaces ............................................................................................3-3
3.2.1 SINF64 Package ................................................................................. 3-3
3.2.2 SINF16 Package ................................................................................. 3-3
3.2.3 SINFM Package .................................................................................. 3-3
3.2.3.1 SINFM with OP0 ..................................................................... 3-3
3.2.3.2 SINFM with OP1 ..................................................................... 3-4
3.2.3.3 SINFM with OP4 ..................................................................... 3-4
3.2.4 GBE Package ...................................................................................... 3-4
3.2.5 GBEM Package ................................................................................... 3-4
3.2.6 FEH Package ...................................................................................... 3-5
3.2.7 STM1E Package .................................................................................. 3-5
3.2.8 DS3 Package ....................................................................................... 3-5
3.2.9 E12 Package ....................................................................................... 3-5
3.2.10 E31 Package ....................................................................................... 3-6
3.2.11 E32 Package ....................................................................................... 3-6
Contents
-i-
DOI-G06439
3.3 Configuration ......................................................................................3-7

3.3.1 Line Protections ................................................................................... 3-7
3.3.1.1 10G (STM-64 [OC-192]) ......................................................... 3-7
3.3.1.2 2.5G (STM-16 [OC-48]) .......................................................... 3-7
3.3.1.3 600M (STM-4 [OC-12]) ........................................................... 3-8
3.3.1.4 150M (STM-1 [OC-3]) ............................................................. 3-8
3.3.1.5 50M (STM-0) .......................................................................... 3-8
3.3.2 Package Protections ............................................................................ 3-9
3.3.2.1 STM1E Package ..................................................................... 3-9
3.3.2.2 DS3 Package .......................................................................... 3-9
3.3.2.3 E12 Package .......................................................................... 3-9
3.3.2.4 E31/E32 Package ................................................................. 3-10
3.3.2.5 PSW40/PSW80 Package ..................................................... 3-10
3.3.2.6 ESW Package ...................................................................... 3-10
3.3.2.7 PSW5WB/PSW10WB Package ............................................ 3-10
3.3.3 Path Protection .................................................................................. 3-11
3.3.3.1 Higher Order Path ................................................................ 3-11
3.3.3.2 Lower Order Path ................................................................. 3-11
3.3.4 Multiple-Ring Network ....................................................................... 3-12
3.3.5 Open Ring Network ........................................................................... 3-12
3.4 Operations ........................................................................................3-13

3.4.1 Upper OS (NMS) Access ................................................................... 3-13
3.4.2 CID Access ........................................................................................ 3-13
3.4.2.1 Available Connection Methods ............................................. 3-13
3.4.2.2 Restrictions ........................................................................... 3-13
3.4.3 Firmware Download ........................................................................... 3-13
3.4.3.1 Restrictions ........................................................................... 3-13
3.4.4 Data Backup/Restore ........................................................................ 3-14
3.4.5 Performance Monitoring (PM) ........................................................... 3-14
3.4.6 Timing Source Selection .................................................................... 3-14
3.4.7 Crossconnection ................................................................................ 3-15
3.4.7.1 Crossconnect Type ............................................................... 3-15
3.4.7.2 Higher Order Path ................................................................ 3-15
3.4.7.3 Lower Order Path ................................................................. 3-15
3.4.8 Laser Shutdown ................................................................................. 3-15
3.4.9 Path Test Access ............................................................................... 3-16
3.4.10 Overhead Access .............................................................................. 3-16
3.4.11 Loopback ........................................................................................... 3-16
3.4.12 In-Service Upgrade ............................................................................ 3-17
Contents
- ii -
DOI-G06439
4. PRECAUTIONS
4-1
4.1 Equipment/Shelves ............................................................................4-2

4.1.1 Equipment Version .............................................................................. 4-2
4.1.2 Main/EXT16/EXT64/EXTWB Shelves ................................................. 4-2
4.1.2.1 EXT64 Shelf ........................................................................... 4-2
4.1.2.2 EXT16 Shelf ........................................................................... 4-3
4.1.2.3 EXTWB Shelf .......................................................................... 4-3
4.2 Packages .............................................................................................4-4

4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
Memory Card ....................................................................................... 4-4

MSC Package ...................................................................................... 4-4
PSW/ESW/PSWWB ............................................................................ 4-4
SC16 .................................................................................................... 4-5
GBE/GBEM/FEH ................................................................................. 4-5
4.2.5.1 GBEM and FEH ...................................................................... 4-5
4.2.5.2 GBEM ..................................................................................... 4-6
4.2.5.3 FEH ........................................................................................ 4-6
4.2.5.4 GBE ........................................................................................ 4-6
4.2.6 E32 ...................................................................................................... 4-6
4.3 CID, CID Operations ...........................................................................4-7

4.4 Other Possible Conditions ................................................................4-8
Contents
- iii -
DOI-G06439
This page is intentionally left blank.
Contents
- iv E
DOI-G06439
1. SUMMARY
This document provides information regarding the SpectralWave Universal Node Broad
Band Manager (U-Node BBM) Release 8.6.x.
The information includes some restrictions that should be considered, in order to avoid
causing failures while U-Node BBM is in service.
SUMMARY
1-1
DOI-G06439
SUMMARY
1-2
E
DOI-G06439
2. VERSION INFORMATION
This section provides version information for firmware and CID application software used in
U-Node BBM Release 8.6.x.
Each version should be confirmed prior to equipment installation.
VERSION INFORMATION
2-1
DOI-G06439
2.1 FIRMWARE VERSIONS

PACKAGE
ID (NEC Code)
APPLICATION
VERSION
MOUNTING LOCATION
UB273-****
8.62
Main Shelf
AGENT68040 [AGCPU]
UB273-*A**/*B**
1.45
AGENTPPC [AGCPU]
UB273-*C**/*D**
2.25
AGENTTCP/IP [AGCPU]
UB273-*E**/*F**
3.12
SC16 [SC16CPU]
UB278-****
8.62
EXT16 Shelf
SSC [SWCPU]
UB274-****
8.07
Main/EXT16 Shelf
OHC [OHCPU]
UB275-****
8.06
Main Shelf
OHCEXT [OHCPU]
UB478-****
8.06
EXT16 Shelf
PSW40 [PW40CPU]
UB276-****
8.11
Main Shelf
PSW80 [PW80CPU]
UB277-****
8.11
ESW [EWCPU]
UB279-****
8.12
EXT16 Shelf
SINF16 [IFCPU]
UB282-****
8.22
Main/EXT16 Shelf
SINFM [IFCPU]
UB283-****
8.22
FEH [FEHCPU]
UB290-****
8.30
GBEM [GEMUCPU]
UB986-****
8.11
GBE [GBECPU]
UB289-****
8.00
STM1E [IFCPU]
UB287-****
8.22
DS3 [IFT3CPU]
UB288-****
8.01
COM [OHCPU]
UB280-****
8.06
SINF64 [IF64CPU]
UB281-****
8.30
SCWB [SCWBCPU]
UB558-****
8.61
SSCWB [SSCWBCPU]
UB560-****
5.01
PSW5WB [PSWWBCPU]
UB561-****
8.01
PSW10WB [PSWWBCPU]
UB562-****
8.01
E12 [E12CPU]
UB563-****
8.09
E31 [E31CPU]
UB564-****
8.02
E32 [E32CPU]
UB565-****
8.02
NAME
MSC
MSC2
SC [SCCPU]
VERSION INFORMATION Firmware Versions

2-2
EXT64 shelf
EXTWB shelf
DOI-G06439
2.2 CID APPLICATION SOFTWARE
2.2.1 Version
The applicable CID version for U-Node BBM Release 8.6.x is:
CID Application Software (FA919-*H05), Version 9.7.52,
or later version for equipment Release 8.6.x.
This CID application software provided for U-Node BBM cannot log into U-Node WBM.
2.2.2 Applicable Operation System

CID application software runs on the following operating systems:
! Microsoft Windows 95
! Microsoft Windows 98/98 Second Edition
! Microsoft Windows NT
! Microsoft Windows 2000 Professional (best recommended)
! Microsoft Windows XP Professional (best recommended)
2.2.3 Available Functions

The full range of functions on the CID application software are available.
NOTE: Information in the CID Help window is displayed in Japanese on a Japanese-version
Windows operating system, or in English on other language version Windows. CID
Help window for EXTWB shelf is not provided on the Japanese-version Windows
operating system.
VERSION INFORMATION CID Application Software

2-3
DOI-G06439
VERSION INFORMATION
2-4
E
DOI-G06439
3. FEATURES
This section provides information regarding operational setups/configurations, modes, and
functions supported by U-Node BBM Release 8.6.x. Some operations may require certain
conditions.
FEATURES
3-1
DOI-G06439
3.1 SHELF TYPES

This release of U-Node BBM provides the following types of shelves:
! Main shelf
! EXT16 shelf (extension shelf adding another 2.5G interface to the system)
! EXT64 shelf (extension shelf adding 10G interface to the system)
! EXTWB shelf (extension shelf adding PDH interface to the system)
FEATURES Shelf Types

3-2
DOI-G06439
3.2 INTERFACES
This release of U-Node BBM supports the following interfaces. However, the use of these
interfaces may be restricted by the configuration. See 3.3 Configuration for the interfaces
available for the configuration.
NOTE: SDH-J (SDH-Japan mode) has been renamed SDH-H (SDH-Hybrid mode) from
Release 6.2.
3.2.1 SINF64 Package

SINF64 package is installed in EXT64 shelf. Colored interface is also available.
! STM-64; for SDH
! OC-192; for SONET
! STM-64H; for SDH-Hybrid
3.2.2 SINF16 Package

SINF16 package is installed in the Main shelf and/or EXT16 shelf. Colored interface is also
available.
! STM-16; for SDH
! OC-48; for SONET
3.2.3 SINFM Package

SINFM package is installed in the Main shelf and/or EXT16 shelf. This package is a base
package to support OP0, OP1 and OP4 optical sticks. SINFM package can simultaneously
accommodate these optical sticks.
3.2.3.1 SINFM with OP0

! STM-0H; for SDH-Hybrid only
FEATURES Interfaces
3-3
DOI-G06439

! STM-1; for SDH
! OC-3; for SONET

! STM-4; for SDH
! OC-12; for SONET
3.2.4 GBE Package

GBE package is installed in the Main shelf and/or EXT16 shelf. This package requires GBIC
module for its operation.
! Giga Bit Ethernet: 1000BASE-SX, 1000BASE-LX
NOTE: SNC/P and UPSR are not available.
3.2.5 GBEM Package

GBEM package is installed in the Main shelf and/or EXT16 shelf. This package requires SFP
module for its operation.
! Giga Bit Ethernet: 1000BASE-SX, 1000BASE-LX
NOTES
1: Port-Multiplex operation is available.
2: Null-extension mapping for GFP frameis available; operation can be specified by CID
on non-Japanese operating system only. When using function with null-extension, the
port-multiplex operation is not available. One GBEM package cannot have both nullextension and linear frame mapping methods.
3: For GBEM virtual concatenation, distance gap between each path within a network
must not exceed 1200 km.
FEATURES Interfaces
3-4
DOI-G06439
3.2.6 FEH Package

FEH package is installed in the Main shelf and/or EXT16 shelf.
! Fast Ethernet: 100BASE-TX
! Ethernet: 10BASE-T
NOTE: For FEH virtual concatenation, distance gap between each path within a network must
not exceed 1200 km.
3.2.7 STM1E Package

STM1E package is installed in Main shelf and/or EXT16 shelf. This package requires
STM1TRM shelf and STM1TRM package, or E4TRM shelf and E4TRM package for its
operation.
! 150M Electric (with STM1TRM package)
! STM1E; for SDH
! STM1EH; for SDH-Hybrid
! 140M Electric (with E4TRM package)
! E4; for SDH
3.2.8 DS3 Package

DS3 package is installed in the Main shelf and/or EXT16 shelf; either must be Group C type
that is designated for the use of DS3 package. This package requires DS3TRM shelf.
! DS3; for SONET only
3.2.9 E12 Package

E12 package is installed in EXTWB shelf. This package requires E1 THR package (for NonProtection) or E1 TRM package (for either Protection/Non-Protection configuration).
! E12 (2M); for SDH only
FEATURES Interfaces
3-5
DOI-G06439
3.2.10 E31 Package

E31 package is installed in EXTWB shelf. This package requires E3 THR package (for NonProtection) or E3 TRM package (for Protection configuration).
3.2.11 E32 Package

E32 package is installed in EXTWB shelf. This package required E3 THR package (for NonProtection) or E3 TRM package (for Protection Configuration).
FEATURES Interfaces
3-6
DOI-G06439
3.3 CONFIGURATION
For this release of U-Node BBM, the following configurations are available:
3.3.1 Line Protections

3.3.1.1 10G (STM-64 [OC-192])
! Non-Protection
! Linear Protection: 1+1 Unidirectional, Non-revertive
NOTE: APS-Japan mode is not supported.
! Linear Protection: 1+1 Bidirectional, Non-revertive
! Linear Protection: 1:1 Bidirectional, Revertive (SLA supported)
! 2F MS-SPRing [BLSR] (SLA, Multi-Ring supported)
NOTE: Available when using PSW80 package.
3.3.1.2 2.5G (STM-16 [OC-48])

! Non-Protection
FEATURES Configuration
3-7
DOI-G06439
3.3.1.3 600M (STM-4 [OC-12])

! Non-Protection
3.3.1.4 150M (STM-1 [OC-3])

! Non-Protection
3.3.1.5 50M (STM-0)

! Non-protection
! Linear Protection: 1+1 Bidirectional
3-8
DOI-G06439
3.3.2 Package Protections
NOTE: U-Node BBM does not support protection configuration for GBE, GBEM and FEH
packages.
3.3.2.1 STM1E Package

! Non-Protection
! 1+1 Package Protection
NOTE: Protection configuration cannot be assigned if the protection-side
STM1E package has registered line facilities.
3.3.2.2 DS3 Package

! Non-Protection
NOTES
1: Protection configuration is assigned when DS3 packages are registered
for both Working slot and Protection slot.
2: Non-Protection mode and single use of a DS3 package are available
only when the package is installed in Working side slot (Slots #4, #6,
#10, and/or #12).
3.3.2.3 E12 Package

! Non-Protection
! 1:N Package Protection
NOTES
1: N = up to 8; number of work packages assigned for a protection group.
2: E12 package must be installed and registered for Slot #7 when
configuring protection switch group. Slot #7 is a slot reserved for the
E12 protection package.
3-9
DOI-G06439
3.3.2.4 E31/E32 Package

! Non-Protection
! 1:1 Package Protection, Revertive
! 1:1 Package Protection, Non-Revertive
NOTES
1: Protection configuration cannot be assigned if the protection-side
package has registered line facilities.
2: Operation for the 1:1 package protection Non-Revertive runs in the
way of that for 1+1 package protection.
3: See also 4. PRECAUTIONS: 4.2.6 E32.
3.3.2.5 PSW40/PSW80 Package

NOTE: Protection configuration is assigned when PSW packages are
registered for both slots. For this reason, when registration is made for
both slots, PSW single package operation is not available.
3.3.2.6 ESW Package

NOTES
1: ESW package configuration (single operation or 1+1 package
protection) must follow that of the PSW package in the Main shelf.
ESW protection switching is carried out in conjunction with that for the
PSW packages.
2: Protection configuration is assigned when ESW packages are
registered for both slots.
3.3.2.7 PSW5WB/PSW10WB Package

! 1+1 package protection
NOTES
1: PSWWB package configuration (single operation or 1+1 package
protection) must follow that of the PSW package in the Main shelf.
PSWWB protection switching is carried out in conjunction with that for
the PSW packages.
2: Protection configuration is assigned when PSWWB packages are
registered for both slots.
3-10
DOI-G06439
3.3.3 Path Protection

This release of U-Node BBM supports the path protection function (PPS) for the following
levels (! indicates for available):
3.3.3.1 Higher Order Path

10G:
2.5G:
600M:
150M:
50M:
45M:
STM-64
[OC-192]
STM-16
[OC-48]
STM-4
[OC-12]
STM-1
[OC-3]
STM-0
DS3
VC-4-16c [STS-48c]
VC-4-4c [STS-12c]
VC-4 [STS-3c]
VC-3 [STS-1]
CROSSCONNECT
LEVELS
GBE/GBEM:
FEH:
1000BASE-SX 10BASE-T
1000BASE-LX 100BASE-TX
NOTES
1: SNC/P for the higher order path, which is added/dropped at EXT16/
EXTWB shelf, is not available.
2: SNC/P for the higher order path, which is added/dropped using GBE
facilities of GBE package, is not available; use GBE facilities of GBEM
package that is available for SNC/P setups.
3: VC-4-64C concatenation using AU-4 termination allows FIX mode
only.
3.3.3.2 Lower Order Path

CROSSCONNECT
LEVELS
45M:
34M:
2M:
E32
E31
E12
VC-12
VC-3
NOTE: This function is not available if the version of installed PSW5WB or

PSW10WB package (group 0*00) is V01AX.
3-11
DOI-G06439
3.3.4 Multiple-Ring Network

One U-Node BBM can be the network elements for multiple Ring networks, configuring
Multiple-Ring network. Using a combination of Path Protection and MS-SPRing [BLSR],
ILR (Interlocked Ring) can be configured as well.
3.3.5 Open Ring Network

U-Node BBM does not support Open Ring configuration.
3-12
DOI-G06439
3.4 OPERATIONS
This release of U-Node BBM supports the following functions and setups:
3.4.1 Upper OS (NMS) Access

! OSI Protocol
! TCP/IP Protocol
3.4.2 CID Access

3.4.2.1 Available Connection Methods
! Direct Line: using CID port (RS-232C serial interface) on MSC package
! TCP/IP: using CID port (LAN interface) on top of the Main shelf
! Modem: using CID port (RS-232C serial interface) on MSC package
3.4.2.2 Restrictions
! Maximum number of users who can remotely log in to the same NE is four.
3.4.3 Firmware Download

! By CID operation
NOTE: Firmware cannot be downloaded to a remote node whose connection is
made by/through line facilities of EXT16 shelf or of U-Node
Regenerator.
! By NMS operation
3.4.3.1 Restrictions
For EXTWB, firmware download is available only when CID has local access via TCP/IP, or
from NMS by remote access.
FEATURES Operations
3-13
DOI-G06439
3.4.4 Data Backup/Restore

! By CID operation
Local operation (to/from a memory within the equipment)
! By CID operation
Remote operation (to/from remote server)
3.4.5 Performance Monitoring (PM)

This release of U-Node BBM supports the Intermediate Path Performance Monitoring
(IPPM) function for both higher and lower paths.
3.4.6 Timing Source Selection

This release of U-Node BBM supports the following timing source selections:
! Line Selection
! External Selection
2M PDH line timing output (when EXTWB with E12 package(s)NOTE is installed) is
available as well.
NOTE: E12 package that belongs to group 0A00/0B00 of version V01AX does
not support this function.
In addition to the automatic switching of selected timing sources, the following operations
are available:
! FSW: forced switching operation for the use of timing source
! MSW: manual switching operation for the use of timing source
! Lockout: inhibits switching to particular timing sources among selections
NOTE: This release of U-Node BBM supports free-running accuracy of Stratum 3E compliant
(added to 64K interface).
FEATURES Operations
3-14
DOI-G06439
3.4.7 Crossconnection
This release of U-Node BBM supports the following crossconnect types and the levels:
3.4.7.1 Crossconnect Type

! 1-Way
! 2-Way
! 1-Way PPS
! 2-Way PPS
Using CID, specified crossconnection type can be modified by adding/deleting PPS setup
without re-registering the crossconnection.
3.4.7.2 Higher Order Path

! AU-3 [STS-1]
! AU-4 [STS-3c]
! AU-4-4C [STS-12c]
! AU-4-16C [STS-48c]
! AU-4-64C [STS-192c]
NOTE: Including SLA path as well.
3.4.7.3 Lower Order Path

This performance is enabled by using EXTWB shelf.
! TU-12 (VC-12)
! TU-3 (VC-3)
3.4.8 Laser Shutdown

This release of U-Node BBM supports automatic/forced laser shutdown for terminating
optical outputs if the signal is lost. Optical output can be restarted by specifying either
automatic or manual.
FEATURES Operations
3-15
DOI-G06439
3.4.9 Path Test Access

This release of U-Node BBM supports path test access function for higher order path.
NOTES
1: Path Test Access is not operative by INC-100MS.
2: When using DS3, FEH and GBE (GBEM) interfaces, the path test access is restricted in
the direction: available access is to/from PSW only.
3: For the concatenation level of VC-3 [STS-1], error counts on Path Test Access between
facilities that belong to different standards may not result properly since the data
mapping system of SDH (ITU-T) and SONET (Telcordia) differ. This problem does not
occur among facilities with the concatenation levels of VC-4 [STS-3] or higher.
4: This operation is not available on VC-4-64c.
3.4.10 Overhead Access

This release of U-Node BBM supports the following types of OH access:
! DCC connection
! Orderwire access (head set and hand set)
! User channels
! OH Through
3.4.11 Loopback
This release of U-Node BBM can perform the following types of loopbacks:
! Terminal loopback
! Facility loopback
! Remote terminal loopback NOTE
NOTE: Available for E12, E31, and E32 facilities only.
FEATURES Operations
3-16
DOI-G06439
3.4.12 In-Service Upgrade

This release of U-Node BBM supports in-service upgrade operation for the following
configurations:
! 2F MS-SPRing [BLSR] to 4F MS-SPRing [BLSR]
! PSW40 packages to PSW80 packages
These in-service upgrades require CID operation to keep traffic operative. The
implementation must follow the in-service upgrade procedures provided in the Operation
and Maintenance manual.
FEATURES Operations
3-17
DOI-G06439
FEATURES
3-18
E
DOI-G06439
4. PRECAUTIONS
This section provides information, guidelines, and restrictions regarding U-Node BBM
operation. Improper equipment operation may cause damage to the traffic, equipment and/or
packages.
In order to run U-Node BBM at its top performance, all information provided here must be
read through and fully understood.
PRECAUTIONS
4-1
DOI-G06439
4.1 EQUIPMENT/SHELVES
4.1.1 Equipment Version

! Do not downgrade equipment to the prior releases.
! When upgrading, cutovers for all upgrading package firmware within the equipment
should be scheduled to take place at the same time.
! U-Node BBM requires its power off then on after starting up in the Cold Start mode.
4.1.2 Main/EXT16/EXT64/EXTWB Shelves

! If initialization (reset in the Cold Start mode) is required, it must take place on all shelves
within the system before starting CID operation:
EXT16 shelf and EXT64 shelf, if connected and registered, will be initialized when
Main shelf is initialized.
EXTWB shelf, if connected and registered, must be initialized when the Main shelf
is initialized.
An EXTWB shelf alone must not be initialized after the connection to the Main shelf
and the registrations are completed. If an EXTWB shelf needs to be initialized, all
the connected EXTWB shelves and the Main shelf must be initialized as well.
! When adding extension shelves, complete all the hardware and cable installations before
turning on the power of the newly added shelf.
! For a newly added extension shelf, turn off and on the power of the shelf before starting
registration, or an alarm may be issued by a package registration.
4.1.2.1 EXT64 Shelf

! For 10G 4F MS-SPRing [BLSR], available ports on PSW80 package are Ports #1, #2, #3
and #4 only.
PRECAUTIONS Equipment/Shelves
4-2
DOI-G06439
4.1.2.2 EXT16 Shelf

! U-Node BBM supports maximum number (three) of EXT16 shelves within the system.
! The use of ports on PSW package for connecting EXT16 shelves are determined by their
shelf IDs (detailed information is provided in the Cable Installation manual):
EXT16 SHELF ID
AVAILABLE PORTS
1, 2
3, 4
5, 6
! If shelf ID needs to be changed, registrations for the target EXT16 should be deleted, then
re-registered with new information. Be sure to confirm that the shelf and cables are
properly connected before re-registering the shelf.
! If registrations for EXT16 shelf need to be deleted, all objects registered under the EXT16
shelf must be deleted prior to shelf deletion.
! If the system is powered or reset, do not attempt to change the registered information of
EXT16 shelf before all the shelves are completely up and running.
! When adding EXT16 shelf to the system in service, do not turn on the power of or register
setup information of the EXT16 shelf before completing all the hardware (packages,
cables, and all physical connections and setups) installation.
4.1.2.3 EXTWB Shelf

! U-Node BBM supports up to 4 EXTWB shelves within the system.
! For EXTWB shelf, the use of PSW ports and SHELF INTF terminals on the Main shelf
are correlated:
PSW PORT TO BE
CONNECTED W/ SHELF #6
SHELF INTF (on Main Shelf)

TERMINAL DESIGNATION
WHEN CONNECTING
IN PARALLEL
PORT 1 (IN 1, OUT 1)
CN3 (EXT16 INTF 1-1), and

CN4 (EXT16 INTF 1-2)
One of EXTWB #7 thru #9 can use

PORT 2 (IN/OUT 2) on PSW only.


IN/OUT 4 on PSW only.


IN/OUT 6 on PSW only.
! Firmware download must be executed by NMS except when the MSC/MSC2 supports the
use of LAN port where the firmware download can be executed by CID.
NOTE: MSC/MSC2 provided for the use of LAN port is Group 0B00, AB00,
0D00, 0F00, AF00.
PRECAUTIONS Equipment/Shelves
4-3
DOI-G06439
4.2 PACKAGES
! Whether by accident or not, if an installed package is disengaged and re-engaged rapidly,
the MSC package within the equipment may not be able to detect the changes. This
results in the provisioning process not being applied to the re-installed package. See also
paragraph 4.2.3 PSW/ESW/PSWWB.
When replacing a package, remove the installed package, and wait for at least a few
seconds (confirm that IMPROPRMVL alarm is issued) before installing the replacement.
If LEDs on the newly installed package do not stop blinking, it means that the changes
have not been detected by the MSC package, and the provisioning process has not taken
place. The package should be re-installed so that the MSC package detects it.
! CPU reset must take place for one package at a time. If CPU resets take place in quick
succession, the target package(s) may not be started up. If a package is not started up,
remove the package from the shelf, and reinstall it.
4.2.1 Memory Card

! Memory card replacement must take place by following the instructions provided in the
Operation and Maintenance manual. Improper replacement may damage the memory
card. Replacing memory cards and MSC packages require special precautions.
4.2.2 MSC Package

! If MSC package with its firmware for the Release prior to 4 is installed in the shelf where
other packages for unmatched releases are installed, SFT_VER is not detected and the
condition will not be reported. The problem has already been cleared for the Release 4 or
later.
4.2.3 PSW/ESW/PSWWB
! Protection switching for ESW packages in the EXT16 shelf and PSW5WB/10WB
packages in the EXTWB shelf within the system are carried out in conjunction with that
for PSW40/80 packages in the Main shelf.
! Even a slight movement of ejectors on these packages can cause their protection
switching to be carried out. If this movement is attempted between ejectors on both
Working and Protection packages by turns consecutively, CID may not reflect the
changes, and may remain an online indication onto the offline package. (Actual Online
LED indications light on the proper package.)
! When performing the in-service upgrade from PSW40 to PSW80, traffic may be
momentarily interrupted.
PRECAUTIONS Packages
4-4
DOI-G06439
4.2.4 SC16
! Do not swap SC16 packages among EXT16 shelves with their EMEM card mounted; an
EMEM card should always be installed on the same EXT16 shelf. If SC16 packages need
to be swapped, remove EMEM cards, replace SC16 packages, then install EMEM cards
into the SC16 package on the original EXT16 shelf.
! When an SC16 package is reset by a command via CID, IMPROPRMVL condition may
be issued. If issued, this pseudo-alarm will automatically be cleared.
! If a SFT_VER alarm (firmware version mismatch) is reported on an SC16 package, the
SC16 package needs to be upgraded, then be reset along with MSC/MSC2 package.
4.2.5 GBE/GBEM/FEH
NOTE: The production of GBE package has been discontinued.
! While the link is not established, following alarms will be indicated depending on the
Auto Negotiation setups:
Auto Negotiation ON:
AUTONEGOERR
Auto Negotiation OFF:
LINKDOWN (GBEM/FEH)
no response (GBE)
! Ethernet interface should be used in the network where the equipment clocks are
synchronized, or a packet error may occur.
! UPSR and SNC/P should be operated in a network where the distance gap between a
Work path and the Protection path is 1200 km or less.
4.2.5.1 GBEM and FEH

! When crossconnecting GBEM/FEH virtual concatenation path, ensure to specify Higher
Order paths (AU paths) in the same sequence at both Add and Drop sides.
! CSF (Client Signal Failure) is issued by the link failure, such as LOS (for GBEM only),
AUTONEGOERR, and LINKDOWN. For GBEM, if ALS (Automatic Laser Shutdown)
has suspended optical outputs, CSF is not forwarded to the opposing node.
! Setup of an Extra Concatenation path (GBEM/FEH) is available for 2F MS-SPRing [2FBSLR] only.
! If the traffic is not in the normal condition under LOA (Loss of Alignment) alarm, LOM
(Loss of Multiframe) alarm, if occurs, may not be cleared by establishing multiframe
synchronization.
4-5
DOI-G06439
! Reported LOM alarm may change to LOA indication if the equipment is powered off/on
or the target package is removed while the LOM alarm is issued.
! While the Extra Concatenation is functioning, CSF (Client Signal Failure) may not be
properly forwarded.
! GBEM/FEH path cannot be terminated in PDH facility.
! While in the overflow status at the receive side, restoration involving bandwidth changes
may cause PKG_FAIL.
4.2.5.2 GBEM
! When connecting to Marvell equipment providing MAC and PHY, data communication
may be disabled.
4.2.5.3 FEH
! Some combinations of MDI setups are not supported. Check MDI setup of the opposing
node.
4.2.5.4 GBE
! Changing the Auto Negotiation setup for a device (router, etc.) connected to the GBE
package may cause link down. Once the connections are established, do not change their
settings.
! GBE interface on GBE package and that on GBEM package do not communicate.
! For the PPS setup, GBE facility cannot be specified for the path source: Primary/
Secondary.
4.2.6 E32
! E32 package group 0A00 must use E32 TRM package (UB568) for the Protection
configuration. This package cannot be configured with E3 TRM (UB567) or E3 THR
(UB570) package.
! E32 package group BA00 must use E3 TRM (UB567) package when configuring
Protection, or E3 THR (UB570) package when configuring Non-Protection.
4-6
DOI-G06439
4.3 CID, CID OPERATIONS

! If CID application software prior to version 3.2.04 (for equipment release 3.2.2) has been
installed, uninstall it before installing the new one. For upgrading from version 4.1.16
(for equipment release 4.1.2) or later, CID can be installed by overwriting onto them.
! Do not remove the CID connection cable while CID is in operation, or CID may be
terminated forcibly and another session may be rejected at login when connection is
established again. If this problem happens, clear it by starting up CID again, or by
restarting your PC.
! Depending on the combination of PC type and operating system, CID display may not
display characters or status information properly when starting up. The display will be
corrected by pressing the Update button or exiting/re-starting CID.
! The Update button should be used occasionally to retrieve the latest information from
NE where a remote user can also make an access. Also, depending on the installed
operating system or the PC, the CID display may not reflect changes made by usual CID
operation. Click the Update button in dialog boxes or restart CID application software to
retrieve the latest information.
! When a connection to a remote node is made by facilities of EXT16, CID cannot log in to
the remote node. Firmware download to the node cannot take place either.
! When CPU reset/cutover is executed via CID, a LINK_FAIL or IMPROPRMVL alarm
may be issued. If issued, this pseudo-alarm will automatically be cleared.
! If a BACKUPMEMP or BACKUP_MIS alarm is issued, clear the memory card failure
before starting CID operation; operating CID where the memory card has an error may
forcibly terminate the session.
! Start button of Error Detection in the Path Test Access dialog box may not work
after other tasks. If this condition occur, exit CID, and start it up again. (Just logging off
the CID may not work.)
! Terminal Emulator should be opened only for viewing command sequence issued on the
background. Do not enter TL1 commands directly. Entering TL1 commands via Terminal
Emulator may cause failure to communication between NE and CID.
! For CID release 6.1 or later, indication for (SDH)-J (Japan) line facilities has been
changed to (SDH)-H (Hybrid) on CID display.
PRECAUTIONS CID, CID Operations

4-7
DOI-G06439
4.4 OTHER POSSIBLE CONDITIONS

! If the traffic using normal PPS is in the status causing LOP, path-switch reports may
issued continuously.
! MS-AIS will not mask DCC_LINK_FAIL, if occurs, for DCC access using MSDCC.
! If a package is in the OOS-MA-AS or UNEQ&AINS state, DCC_LINK_FAIL is not
masked.
PRECAUTIONS Other Possible Conditions

4-8
E

01 G06439

Uploaded by

Copyright:

Available Formats

01 G06439

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

01 G06439

Uploaded by

Copyright:

Available Formats

DOI-G06439

7-1, Shiba 5-Chome, Minato-Ku, Tokyo 108-8001, Japan

July 2004, approved by H. Momiji of NEC-BBN-CNW

Copyright 2004 by NEC Corporation

SpectralWave U-Node BBM

2.1 Firmware Versions .............................................................................2-2

3.1 Shelf Types .........................................................................................3-2

3.3 Configuration ......................................................................................3-7

3.4 Operations ........................................................................................3-13

4.1 Equipment/Shelves ............................................................................4-2

4.2 Packages .............................................................................................4-4

Memory Card ....................................................................................... 4-4

4.3 CID, CID Operations ...........................................................................4-7

This page is intentionally left blank.

This page is intentionally left blank.

2.1 FIRMWARE VERSIONS

VERSION INFORMATION Firmware Versions

2.2 CID APPLICATION SOFTWARE

2.2.2 Applicable Operation System

2.2.3 Available Functions

VERSION INFORMATION CID Application Software

This page is intentionally left blank.

3.1 SHELF TYPES

FEATURES Shelf Types

3.2.1 SINF64 Package

3.2.2 SINF16 Package

3.2.3 SINFM Package

3.2.3.1 SINFM with OP0

3.2.3.2 SINFM with OP1

3.2.3.3 SINFM with OP4

3.2.4 GBE Package

3.2.5 GBEM Package

3.2.6 FEH Package

3.2.7 STM1E Package

3.2.8 DS3 Package

3.2.9 E12 Package

3.2.10 E31 Package

3.2.11 E32 Package

3.3.1 Line Protections

3.3.1.2 2.5G (STM-16 [OC-48])

3.3.1.3 600M (STM-4 [OC-12])

3.3.1.4 150M (STM-1 [OC-3])

3.3.1.5 50M (STM-0)

3.3.2 Package Protections

3.3.2.1 STM1E Package

3.3.2.2 DS3 Package

3.3.2.3 E12 Package

3.3.2.4 E31/E32 Package

3.3.2.5 PSW40/PSW80 Package

3.3.2.6 ESW Package

3.3.2.7 PSW5WB/PSW10WB Package

3.3.3 Path Protection

3.3.3.1 Higher Order Path

3.3.3.2 Lower Order Path

NOTE: This function is not available if the version of installed PSW5WB or

3.3.4 Multiple-Ring Network

3.3.5 Open Ring Network

3.4.1 Upper OS (NMS) Access

3.4.2 CID Access