Table of Contents
Advertisement
JUNOSe 10.2.2 Release Notes
Service Manager
SNMP
SONET
SRC Software and SDX Software
48
Known Problems and Limitations
The CLI fails to display any output when you include the optional
service-session serviceName keyword and variable in the show
service-management owner-session command. [Defect ID 181269]
Work-around: Do not include this optional argument. The service session
information is displayed properly when you issue the show
service-management owner-session command without including the optional
service-session serviceName keyword and variable.
After you activate an independent IPv6 service and issue either of the following
commands on the default virtual router or any other virtual router, except the
one on which the subscriber session is active, no output is displayed in the CLI
interface: [Defect ID 181929]
show service-management subscriber-session subscriberName interface
interfaceType interfaceSpecifier
show service-management subscriber-session subscriberName interface
interfaceType interfaceSpecifier service-session serviceName
This problem also occurs when a subscriber is authenticated using a RADIUS
server for a combined IPv4 and IPv6 service in a dual stack.
When you configure the router with an address pool that has two IP address
ranges, only the range that you configured first is available via the MIB. [Defect
ID 61232]
You cannot use the highest sensitivity bit-error rate setting (a value of 9)
associated with APS/MSP alarm when you issue the threshold sd-ber
command to configure a cOCx/STMx line module with cOC12-APS-capable
IOAs. [Defect ID 72861]
Work-around: Use only a value in the range 5–8 when you issue the threshold
sd-ber command for this module combination, as in the following example:
host1(config)#controller sonet 2/1
host1(config-controll)#aps group boston
host1(config-controll)#aps protect
host1(config-controller)#threshold sd-ber 6
The SRC client does not prevent you from changing the name of the router
while the client is connected to the SAE, resulting in SAE issues such as lost IP
addresses and stale users. [Defect ID 77102]
Work-around: To change the router name while the SRC client is connected to
the SAE, shut down the SRC client, change the name, then re-enable the SRC
client.
Advertisement
Table of Contents
