Cisco LightStream 2020 Anleitung zur Fehlerbehebung

1Doc. No.Copyright  1995Cisco Systems, Inc.All rights reserved.The LightStream 2020 Release Notesfor Software Release 2.0.9These release notes descr

10Special ConsiderationsLSCle00509 PVCDeleting one PVC hangs up MMA when hundreds of PVCs are used.If hundreds of PVCs are created on a single port, t

11Special ConsiderationsLSCle00710 Checking SoftwareNo procedure is described for checking software on the standby NP.When you verify a software inst

12Special ConsiderationsLSCle00867 Disk SpaceYou may be unable to free up sufficient disk space for a new release.When attempting to install a new rele

13Special ConsiderationsLSCle00962 PVCThe deleted PVC cannot be added in again: “Waiting to be deleted from switch.”The current implementation restri

14Special Considerationsone download is in process, the downloads can be distinguished only by remembering the order inwhich they were invoked (one wi

15Software Upgrade ProceduresLSCle01318 OC3 PortOC-3 card continuously bounced when connected to SONET MUX.When connecting an OC3 portto a SONET mult

16Software Upgrade ProceduresNote The following procedure for software installation of Release 2.0.9 causes flash memory to bereloaded. The flash reload

17Software Upgrade ProceduresOutline of Upgrade ProceduresThe following procedures are used to upgrade a network to Release 2.0.9 software:• Procedur

18Software Upgrade ProceduresProcedure 1, Copy New Software to the Distribution NodeWith this procedure you copy the new software from the distributio

19Software Upgrade ProceduresStep 4 On a system with redundant NPs, verify that you are connected to the primary NP (theactive NP):• At the bash prom

2New Features and EnhancementsNew Features and EnhancementsRelease 2.0.9 contains improvements to existing functionality found in Release 2.0. Theimpr

20Software Upgrade ProceduresWhen the program prompts you for a diskette, insert the first diskette (of the diskette setthat you are currently installi

21Software Upgrade ProceduresEnter the name of the remote node in place of remote-node.Note If this is the first time you haveupgraded, then this step

22Software Upgrade ProceduresStep 2 Enter ‘. (backquote plus dot, that is, left single quote plus period).Step 3 At the TCS HUB prompt, use the connec

23Software Upgrade Procedures• Connect to the slot of the primary NP (the active NP) by typing the following command:TCS HUB<<A>> connect

24Software Upgrade ProceduresExample Output From a Successful UpgradeThe following is an example of output seen when this upgrade procedure is carried

25Software Upgrade Proceduresfsck /dev/sd0b(all sizes and block numbers in decimal)(file system creation time is Mon Apr 11 08:57:52 1994)checking us

26Software Upgrade ProceduresProcedure 4, Verify Switch Card FlashWith this procedure you verifythe version of flash memory in each node’sswitch cards,

27Software Upgrade ProceduresUpgrade FlashStep 3 If a new image is to be loaded into flash on a switch card, shutdown the node:bash# reboot -nThis tak

28Software Upgrade ProceduresStep 6 Load the switch card flash memory for Slot A.• For a Release 2 switch card in Slot A, enter the following command a

29Software Upgrade ProceduresTCS HUB<<A>>reset 1• Reconnect to the same NP (the NP in slot 1 in this example):TCS HUB<<A>> co

3Flash Memory Image Checksum ValuesSoftware releases 2.0.0 and above require a 32 MB network processor (NP).Software Release 2.0.5 is the minimum sof

30Software Upgrade ProceduresLoad StatisticsData bytes = 84898Overhead bytes = 42464Messages sent = 2654S-records = 5307System Monitor->•

31Special ProceduresReload Flash If NecessaryStep 12 If the switch card has an incorrect flash checksum, load the flash again by executing thepresent p

32Special ProceduresReturn to the section that referred you to this procedure (“Procedure 1, Copy New Software to theDistribution Node” or “Procedure

33Special ProceduresStep 3 If there is a redundant NP in this chassis, verify that the other NP is functioning as backup.Enter the following command:

34Special ProceduresStep 5 The following error message may be generated:Permission denied.If this message is displayed, the rsh permissions on the bac

35Special ProceduresSpecial Procedure D, Getting rsh to Work Successfully on a Remote NodeUse this procedure if the rsh command reports an error mess

36Special ProceduresNote Be sure you enter the redirect operator twice, with no space (>>). If you enter it only once(>), you will overwrite

37Resolved ProblemsNote Do not use the dir command to verify the contents of the diskette. There is no FAT (the DOSfileallocation table) onLightStream

38Resolved ProblemsThe platform bugs listed below have been fixed in Release 2.0.8a2 and are incorporated inRelease 2.0.9.LSCle02690 NP does not cut ov

4Special ConsiderationsSpecial Considerations for Release 2.0.9Setting and Detecting Baud Rate on the Console or Modem PortsThe TCS HUB for Release 2

5Special ConsiderationsThe arguments of the command are as follows:You can change the baud rate at any time. It takes effect on power-up or board res

6Special Considerations• If you do not have access to the local console, then use the modem port on the redundant switch.This method requires redundan

7Special ConsiderationsFrame Relay NNI Interface LimitedAlthough limited functionality for a frame relay NNI interface is present in the Release 2.0.

8Special ConsiderationsPlan the Network ConfigurationIdentify all OC-3 ports in your network that you want to run SDH.Step 1 List the SDH ports for eac

9Special ConsiderationsInstalling a CardEvery time you install a card in a slot of the system, use this procedure:Step 1 Log in to the active NP as r