ciena 3930 installation manual

File Name:ciena 3930 installation manual.pdf
Size:1376 KB
Type:PDF, ePub, eBook, fb2, mobi, txt, doc, rtf, djvu
Category:Book
Uploaded24 May 2019, 14:56 PM
InterfaceEnglish
Rating4.6/5 from 648 votes
StatusAVAILABLE
Last checked8 Minutes ago!

ciena 3930 installation manual

Another version is available. I understand I can unsubscribe at any time. I understand I can unsubscribe at any time. Learn about who we are and what we do. The site may not work properly if you don't update your browser. If you do not update your browser, we suggest you visit old reddit. Press J to jump to the feed. Press question mark to learn the rest of the keyboard shortcuts Log in sign up User account menu 42 Who's off their rocker.Our nice, big UPS won't do 120V outputs, so I'd have to get a second UPS for the fiber, rather than using the one that keeps our racks alive. It's exceedingly rare to see a switching power supply that can't handle 240V input these days. Even your tiny wall warts usually indicate they can go up that high. AC Input: 100V, 240V AC (nominal). Maximum Power Input: 75 to 95W, depends on variant. Maximum Power Input: 48 WSo I passed this information back, asked my contact to relay to their engineers. I get back: The Ciena 3930 can not accept 240v, we do not have a power supply capable of using this voltage. It has two separate 120v power supply's that require two separate 120v outlets. Or you can use a single 120v supply, or single or dual dv power -48vcd. OK, WTF? I point at the product specifications, and their engineers tell me I'm full of it. Who's off their rocker here? 48 comments share save hide report 83% Upvoted This thread is archived New comments cannot be posted and votes cannot be cast Sort by best level 1 packets. Ask them what the part number of the power supply is - they can get this information by running: chassis show power I expected someone here would have experience with the equipment. What you've told me just makes me confident I can supply them with 240V when they get here. I'm currently delivering 240V to it and this post is going through it. Translation: Our procurement department aint making a special case for you.

You are totally right almost ALL power supplies cover 100-240v, because it means the manufacture doesn't have to be concerned about that as a region specific detail. Do the units have a standard IEC plug. Just get the right IEC cable for your power source, and when the units show up double check the specs listed on the power supply unit and go for it. I figured it was process-bound, which is fine. But what I find unlikely is that the hardware itself doesn't support 100-240V like just about every other piece of electronic gear out there. I was also hoping that someone else who already has the 2930 could offer their own observations. If you do not have either of these, you are not ready to accept service. When they come to install, check out the Ciena power supply they give you. If it accepts 240 or 208V, plug it in. If you find that the power adapters truly don't accept anything other than 120V, you should be prepared to run the Ciena off wall power until you can get an electrician out to wire some 120V sockets to your UPS. It made me want to claw my eyes out. (I'm not an electrician, but I've done new-construction residential wiring that passed inspection. At least in my limited experience (four installs for two different companies). In the USA, 240 Volt is provided by two 120 V 'Legs' and a neutral. If you plug your Ciena 2930 into a US 240 V, then you will not have a good experience. In the UK, they have 240 volts on a single Leg, so a standard outlet has a 240 line, a neutral line, and a ground. Plugging a standard device into a UK 240 v line is not the same as US 240 volt. So, if you plug into a single leg of your 240 volt power strip, you'll get 120 volts. I'm sure there are 120v cables that will plug into a 240v system and get you what you need. There are also power strips that will connect into a 240v output and deliver 120v outlets.

My UPS offers hot-hot-ground, but no neutral, so there's no to-code way to hang off a single leg while providing hot-neutral-ground without risking a ground loop. I've looked into it before, because our security system's wall wart only takes 120V.Better yet, get a different ISP. Curiously, second-best fiber offer was from Comcast. Routers, switches, wireless, and firewalls. All rights reserved Back to top. Only the OOB port shows a link! Only the OOB port shows a link!I cannot get the connection from the Dell N3024P to come up on any ports except for the out-of-band management port. I'm using a standard CAT5 cable from the Ciena to the Dell. I've tried connecting the Ciena 3930 to the other ports on the N3024P, but none of them ever show a link light, except for the out-of-band management port. I can configure the out-of-band management port and set the gateway as the next-hop address and everything works fine. I can ping other hosts on my network from the switch itself by both host name and IP, I can ping remote subnets on my WAN, and I can ping Internet addresses by both IP and host name. I do not understand why this only works on the out-of-band management port and no other ports on the Dell N3024P. What am I doing wrong. It doesn't matter if I set the ports to access, general, or trunk. None of them ever come up when plugged into the Ciena, except the OOB port. We have other Ciena 3930 routers connected to Cisco layer 3 switches and the connection works fine, but I cannot get it to connect on the Dell N3024P unless I plug it into the out-of-band management port. Resetting the switch to factory default did nothing. Any suggestions? Thanks! Only the OOB port shows a link!I have seen some instances where the ports just don't negotiate properly, but manually setting the speed works. Try 100 and 1000. Here is a link to the most recent. Only the OOB port shows a link!

I have seen some instances where the ports just don't negotiate properly, but manually setting the speed works. Try 100 and 1000. Here is a link to the most recent. Discover everything Scribd has to offer, including books and audiobooks from major publishers. Start Free Trial Cancel anytime. Report this Document Download Now Save Save Manual 3930 For Later 0 ratings 0% found this document useful (0 votes) 18 views 104 pages Manual 3930 Uploaded by comtekaccounts Description: Hardware installation Full description Save Save Manual 3930 For Later 0% 0% found this document useful, Mark this document as useful 0% 0% found this document not useful, Mark this document as not useful Embed Share Print Download Now Jump to Page You are on page 1 of 104 Search inside document Browse Books Site Directory Site Language: English Change Language English Change Language. There’s essentially zero publiclyI’m not sure why it’s traditional for telco-oriented companies toCiena acquired WWP and built their packet Ethernet offerings onJuniper or Mikrotik device. For example you can enterThere’s three options: You’ll need a null modem cableThe local access part is important. You can plug your laptop into it. You can’t put a default gateway or other route on it and hook it upGLC-T SFP that identifies as Cisco SFP. The 3911 shows a difference. Learn more - opens in a new window or tab This amount is subject to change until you make payment. For additional information, see the Global Shipping Programme terms and conditions - opens in a new window or tab This amount is subject to change until you make payment. If you reside in an EU member state besides UK, import VAT on this purchase is not recoverable.

For additional information, see the Global Shipping Programme terms and conditions - opens in a new window or tab Learn More - opens in a new window or tab Learn More - opens in a new window or tab Learn More - opens in a new window or tab Learn More - opens in a new window or tab Learn More - opens in a new window or tab The item may have some signs of cosmetic wear, but is fully This item may be a floor model or an item that has been returned to the seller after a period of use. See the seller’s listing for full details and description of any imperfections. Contact the seller - opens in a new window or tab and request post to your location. Please enter a valid postcode. Please enter a number less than or equal to 1. You're covered by the eBay Money Back Guarantee if you receive an item that is not as described in the listing. Find out more about your rights as a buyer - opens in a new window or tab and exceptions - opens in a new window or tab. All Rights Reserved. User Agreement, Privacy, Cookies and AdChoice Norton Secured - powered by Verisign. Highly recommend. We have been striving to provide professional and timely services for our customers. We also set up a professional test center to guarantee the quality of our products. In the future, we will devote to providing more qualified products at good values. The staff at FS.COM is also very friendly and helpful. It's a win win! The prices are amazing. That is, the command code in each application may be shared across multiple command interfaces. Thus, the network device may provide the increased flexibility of having multiple command interfaces while minimizing the complexity required to maintain commands across those interfaces. In addition, a community command interface may be used to connect the common command interfaces of multiple network devices. AtiMe-3E Data Sheet, 1-17 (Mar. 8, 2000). Black, D., “Building Switched Networks,” pp. 85-267. Black, D.

, “Managing Switched Local Area Networks A Practical Guide” pp. 324-329. “Configuration,” Cisco Systems Inc.NavisXtend Fault Server, Ascend Communications, Inc.NavisXtend Provisioning Server, Ascend Communications, Inc.PMC-Sierra, Inc. website (Mar. 24, 2000). Raddalgoda, M., “Failure-proof Telecommunications Products: Changing Expectations About Networking Reliability with Microkernel RTOS Technology,” QNX Software Systems Ltd.Syndesis Limited product literature, 1999. “Using Polyhedra for a Wireless Roaming Call Management System,” Polyhedra, Inc., (prior to May 20, 2000). Veritas Software Corporation webpage, 2000. Suite 350, Charlotte, NC, 28211, US) With the growth of the Internet, web interfaces were also created to allow administrators to remotely control network devices through web pages. In general, web interfaces provide easier access with a more visually rich format through Hypertext Markup Language (HTML). For example, commands may be grouped and displayed according to particular categories and hyperlinks may be used to allow the administrator to jump between different web pages. To accommodate the preferences of a large number of users and because both interfaces have advantages, often, both a CLI interface and a web interface are provided to a network device. Additional interfaces may also be provided. This flexibility, however, can be costly to maintain because although many of the commands provided on the interfaces are the same, the applications corresponding to the commands must include separate code for each interface. Thus, within, for example, an Asynchronous Transfer Mode (ATM) application, a command such as “Show ATM Stats” is essentially multiple commands: a different one for each interface. Thus, if a command needs to be changed or upgraded, each set of code must be modified. Similarly, to add a single, new command, the application writer must develop a set of code for each interface.

In addition, applications running on the network device must maintain an Application Programming Interface (API) for each external interface and must be knowledgeable about the source of each received command so that responses will be provided in the appropriate format, for example, HTML for a web interface or ASCII for a CLI. If an interface is modified or the interaction between the interface and the command within the application changes, the application will likely need to be changed. For certain software architectures, this may require a new release of the software running the network device, and the network device may need to be brought down while the software is re-installed. Thus, providing different types of interfaces increases flexibility but also increases the complexity of maintaining consistent commands across each interface and the complexity of responding to commands. SUMMARY A common command interface (CCI) provides an interface abstraction allowing network device applications to maintain one set of code for each command regardless of which command interface (e.g., web, CLI, NMS, etc.) initiates the command. In addition, a community command interface may be used to connect the common command interfaces of multiple network devices. In one aspect, the present invention provides a method of managing a telecommunications network device including registering at least one command executable by an application with a command interface, receiving the command at the command interface from a user interface, forwarding the command to the application, and completing execution of the command.

In another aspect, the present invention provides a method of managing a telecommunications network device including registering at least one command executable by an application with a first command proxy, wherein the first command proxy is local to the application, registering the command through the first command proxy with a central command daemon, receiving the command at a user interface, forwarding the command to a second command proxy, wherein the second command proxy is local to the user interface, forwarding the command through the second command proxy to the central command daemon, forwarding the command through the central command daemon to the first command proxy, forwarding the command through the first command proxy to the application, and completing execution of the command. In yet another aspect, the present invention provides a method of managing a telecommunications network including a first network device and a second network device including executing a community command daemon on one of the first or second network devices, executing a first application on the first network device, executing a second application on the second network device, registering a first command executable by the first application with a first command interface on the first network device, registering a second command executable by the second application with a second command interface on the second network device and registering the first and second commands with the community command daemon. In still another aspect, the present invention provides a telecommunications network device including an application capable of executing a command and a common command interface, wherein the application is capable of registering the command with the common command interface and the common command interface is capable of receiving the command from a user interface and forwarding the received command to the application.

In another aspect, the present invention provides a telecommunications network device including a common command interface and an application capable of executing a command, wherein the application includes a command application programming interface (API) for registering the command with the common command interface. In yet another aspect, the present invention provides a telecommunications network including a first network device, a second network device connected to the first network device, a community command daemon executing on the first or second network device, and a first common command interface executing on the first network device and capable of registering a first command with the community command daemon, and a second common command interface executing on the second network device and capable of registering a second command with the community command daemon. DETAILED DESCRIPTION Modular Software: A modular software architecture solves some of the more common scenarios seen in existing architectures when software is upgraded or new features are deployed. Software modularity involves functionally dividing a software system into individual modules or processes, which are then designed and implemented independently. Inter-process communication (IPC) between the processes is carried out through message passing in accordance with well-defined application programming interfaces (APIs) generated from the same logical system model using the same code generation system. A protected memory feature also helps enforce the separation of modules. Modules are compiled and linked as separate programs, and each program runs in its own protected memory space. In addition, each program is addressed with an abstract communication handle, or logical name. The logical name is location-independent; it can live on any card in the system. Once complete, the processes continue to communicate with the same logical name, unaware of the fact that a switchover just occurred.

Like certain existing architectures, the modular software architecture dynamically loads applications as needed. Beyond prior architectures, however, the modular software architecture removes significant application dependent data from the kernel and minimizes the link between software and hardware. Instead, under the modular software architecture, the applications themselves gather necessary information (i.e., metadata and instance data) from a variety of sources, for example, text files, JAVA class files and database views, which may be provided at run time or through the logical system model. Metadata facilitates customization of the execution behavior of software processes without modifying the operating system software image. A modular software architecture makes writing applications—especially distributed applications—more difficult, but metadata provides seamless extensibility allowing new software processes to be added and existing software processes to be upgraded or downgraded while the operating system is running (hot upgrades and downgrades). In one embodiment, the kernel includes operating system software, standard system services software and modular system services software. Even portions of the kernel may be hot upgraded under certain circumstances. Examples of metadata include, customization text files used by software device drivers; JAVA class files that are dynamically instantiated using reflection; registration and deregistration protocols that enable the addition and deletion of software services without system disruption; and database view definitions that provide many varied views of the logical system model. Each of these and other examples are described below. The embodiment described below includes a network computer system with a loosely coupled distributed processing system.

It should be understood, however, that the computer system could also be a central processing system or a combination of distributed and central processing and either loosely or tightly coupled. In addition, the computer system described below is a network switch for use in, for example, the Internet, wide area networks (WAN) or local area networks (LAN). It should be understood, however, that the modular software architecture can be implemented on any network device (including routers) or other types of computer systems and is not restricted to a network switch. A distributed processing system is a collection of independent computers that appear to the user of the system as a single computer. Referring to FIG. 1, computer system 10 includes a centralized processor 12 with a control processor subsystem 14 that executes an instance of the kernel 20 including master control programs and server programs to actively control system operation by performing a major portion of the control functions (e.g., booting and system management) for the system. A backup or redundant Ethernet switch may also be connected to each board such that if the primary Ethernet switch fails, the boards can fail-over to the backup Ethernet switch. External network control data is passed from the line cards to the central processor over Ethernet 32. This external network control data is also assigned a high priority when passed over the Ethernet to ensure that it is not dropped during periods of heavy traffic on the Ethernet. In addition, another bus 33 is provided for low level system service operations, including, for example, the detection of newly installed (or removed) hardware, reset and interrupt control and real time clock (RTC) synchronization across the system. In one embodiment, this is an Inter-IC communications (I 2 C) bus. Alternatively, the control and data may be passed over one common path (in-band).

The present invention provides a massively scalable, highly reliable comprehensive network management system, intended to scale up (and down) to meet varied customer needs. Hereinafter, the term “NMS” will be used for both element and network management systems unless otherwise noted. To configure a network device, the network administrator uses the NMS to provision services. For example, the administrator may connect a cable to a port of a network device and then use the NMS to enable the port. If the network device supports multiple protocols and services, then the administrator uses the NMS to provision these as well. To manage a network device, the NMS interprets data gathered by programs running on each network device relevant to network configuration, security, accounting, statistics, and fault logging and presents the interpretation of this data to the network administrator. Preferably, NMS programs and programs executing on network devices perform in expected ways (i.e., synchronously) and use the same data in the same way. Further, to ensure that the NMS and network device programs for managing and operating the network device use the same data, the programs, including the NMS programs, access a single data repository for configuration information, for example, a configuration database within the network device. In addition, the NMS servers provide the NMS clients with network device management information, which the clients then make available to the administrators. “Pushing” data from a server to multiple clients synchronizes the clients with minimal polling. Reduced polling means less management traffic on the network and more device CPU cycles available for other management tasks. Communication between the NMS client and server is done via Remote Method Invocation (RMI) over Transmission Control Protocol (TCP), a reliable protocol that ensures no data loss.

The NMS client and server relationship prevents the network administrator from directly accessing the network device. Since several network administrators may be managing the network, this mitigates errors that may result if two administrators attempt to configure the same network device at the same time. The present invention also includes a configuration relational database 42 within each network device and an NMS relational database 61 external to the network device. By using JDBC and a relational database, the NMS server is able to leverage database transactions, database views, database journaling and database backup technologies that help provide unprecedented system availability. Relational database technology also scales well as it has matured over many years. An active query is a mechanism that enables a client to post a blocked SQL query for asynchronous notification by the database when data changes are made after the blocked SQL query was made. Similarly, any configuration changes made by the network administrator directly through console interface 852 are made to the configuration database and, through active queries, automatically replicated to the NMS database. Maintaining a primary or master repository of data within each network device ensures that the NMS and network device are always synchronized with respect to the state of the configuration. Replicating changes made to the primary database within the network device to any secondary data repositories, for example, NMS database 61, ensures that all secondary data sources are quickly updated and remain in lockstep synchronization. Instead of automatically replicating changes to the NMS database through active queries, only certain data, as configured by the network administrator, may be replicated. Similarly, instead of immediate replication, the network administrator may configure periodic replication. For example, data from the master embedded database (i.e.

, the configuration database) can be uploaded daily or hourly. In addition to the periodic, scheduled uploads, backup may be done anytime at the request of the network administrator. Referring again to FIG. 2 a, for increased availability, the network device may include a backup configuration database 42.In addition, any changes to configuration database 42 may be written immediately to flash persistent memory 853 which may also be located on the primary centralized processor card or on another card, and similarly, any changes to backup configuration database 42.These flash-based configuration files protect against loss of data during power failures. In the unlikely event that all copies of the database within the network device are unusable, the data stored in the NMS database may be downloaded to the network device. As shown in FIGS. 41 a and 41 b, the chassis may support internal control (IC) processor cards 542 a and 543 a and external control (EC) processor cards 542 b and 543 b. In this embodiment, configuration database 42 may be maintained by a processor on internal control processor card 542 a and configuration database 42.The file transfer protocol (FTP) may provide an efficient, reliable transport out of the network device for data intensive operations. Bulk data applications include accounting, historical statistics and logging. An FTP push (to reduce polling) may be used to send accounting, historical statistics and logging data to a data collector server 857, which may be a UNIX server. NMS servers may also access network device statistics and status information stored within the network device using SNMP (multiple versions) traps and standard Management Information Bases (MIBs and MIB-2). The NMS server augments SNMP traps by providing them over the conventional User Datagram Protocol (UDP) as well as over Transmission Control Protocol (TCP), which provides reliable traps.

Each event is generated with a sequence number and logged by the data collector server in a system log database for in place context with system log data. These measures significantly improve the likelihood of responding to all events in a timely manner reducing the chance of service disruption. The various NMS programs—clients, servers, NMS databases, data collector servers and remote NMS databases—are distributed programs and may be executed on the same computer or different computers. The computers may be within the same LAN or WAN or accessible through the Internet. Distribution and hierarchy are fundamental to making any software system scale to meet larger needs over time. Distribution reduces resource locality constraints and facilitates flexible deployment. Since day-to-day management is done in a distributed fashion, it makes sense that the management software should be distributed. Hierarchy provides natural boundaries of management responsibility and minimizes the number of entities that a management tool must be aware of. Both distribution and hierarchy are fundamental to any long-term management solution. The client server model allows for increased scalability as servers and clients may be added as the number of network managers increase and as the network grows. In fact the code for both platforms may be the same allowing consistent graphical interfaces to be displayed to the network administrator. In addition to being native to JAVA, RMI is attractive as the RMI architecture includes (RMI) over Internet Inter-Orb Protocol (IIOP) which delivers Common Object Request Broker Architecture (CORBA) compliant distributed computing capabilities to JAVA. Like CORBA, RMI over IIOP uses IIOP as its communication protocol. For “manage anywhere” purposes and web technology integration, the various NMS programs may also run within a web browser. From HP NNM a context-sensitive launch into an NMS server may be executed.