Cisco Nexus Emulator
Aug 06, 2013 Hi all, I am looking for an emulator, not unlike GNS, for Nexus devices. Anything out there? Thanks Sebastian South Africa 37487.
Cisco Nexus Features
Titanium is Cisco Nexus Operating System emulator made by Cisco. A copy of Titanium 5.1.(2) installed on image has recently leaked to the Internet and now we can use it for our studies. The tutorial shows how to do connect Titanium VMware image to using emulator. As GNS3 has built-in support for Qemu and Qemu can work with VMware vmdk images no cloud connection is needed for connection to external devices. Used Software GNS3 0.8.3.1 installed on Fedora 17 Linux NxOS Emulator Titanium 5.1(2) VMware image Qemu 1.3.0 1.
Configure Qemu Guest Settings Assuming that you have Qemu emulator installed and working set Qemu Guest settings as following. Edit- Preferences- Qemu- Qemu Guest Picture 1 GNS3 - Qemu Guest settings 2. Create a new GNS3 project File- New blank project Picture 2 GNS3 - New Project 3. Create your topology Two Titanium instances are connected to 3725 router occupied with NM-16SW module. Titanium ports eth2/1 and mgmt0 are routed L3 ports connecting instances each other. There are also switched trunk ports eth2/2 on both Titanium instances connecting instances to the router 3725.
For layer3 connectivity interfaces vlan1 are created on both instances. Picture 3 GNS3 - Topology Ports f1/0 and f1/1 are interfaces located on NM-16SW module that is inserted in the router 3725. Both ports are L2 trunk ports connected to Titanium instances.
For L3 connectivity interface vlan 1 is created on the router. Titanium configuration Use console (Right click on device) to connect to device serial port. Username/password for Titanium is admin/cisco. Picture 4 Titanium login Now, check Titanium version.
Picture 5 Titanium version Check presented modules. Picture 6 Presented modules From what we see, one management port mgmt0 and one Ethernet module with 9 interfaces are presented in Titanium1. To ping IP address of management interface just issue command: Picture 7 Pinging management interface As interface mgmt0 is up on both Titanium instances by default instances should see each other using CDP protocol. Picture 8 L2 connection is working on routed eth2/1 ports of Titanium Now configure particular IP addresses for eth2/1 interfaces on both Titanium instances. Once IP addresses are assigned to the interfaces we should ping instances each other. Picture 9 L3 connection is working on routed ports of Titanium Create VLAN 10 and configure ethernet 2/2 as a L2 trunk port. In order to create layer3 vlan interface, following command has to be issued.
Picture 10 Titanium1 Vlan, trunk a vlan interface configuration Once vlan1 interface has been brought up a warning message 'crashed service netstack' has appeared as it is captured at the picture. However we can still ping vlan1 inetrface IP address 192.168.3.1 as it is shown at the picture. Picture 11 Pinging vlan1 interface IP address We have finished Titanium1 configuration. Configure router 3725 as following. Picture 12 Router 3725 configuration Test if we can ping vlan10 IP address 192.168.3.3 locally from CLI of router 3725. Picture 13 Pinging local interface vlan10 on router 3725 Router 3725 Vlan1 interface seems to be up and reachable. The other task is to ping vlan10 interface of Titanium1.
As you can see at the picture, once we issue ping to 192.168.3.1 from router 3725, Titanium instance completly crashed and reboot itself. Picture 14 Titanium1 crash Conclusion I've tested this scenario several times and every time I issued ping either from the remote end device, Titanium emulator crashed and rebooted. My conclusion is that Titanium is not ready for use in home lab and the real world scenario testing is impossible. As one guy said on the forum it is just feeling of NX-OS. Hoping for the best, everything may be changed with the next version of Titanium. Dear thanks for the amazing guide!
I have a problem to start titanium in quemu. With vmware it's work. My settings are: - win7 - i5 2,67 Ghz - 8 GB - Titanium-VM-5.1(2)-flat.vmdk - gns3 0.8.3.1.Problem with Quemu. a) it's necessary to set (in quemu option) 1.024 MB otherwise the quemu host does'nt start b) the quemu start, the console start but after several messages the system hangs How can fix this problem?.Problem with Virtualbox. I have tried to install titanium on virtualbox but i failed to convert the.vmdk image in.vdi for virtualbox with 'VBoxManage clonehd source.vmdk target.vdi -format VDI'.
And seem related to RAW format. How can fix this problems? Thanks giuseppe. Just installed 6.1.1 and tried the exact same thing that was crashing 5.2(1) - defining a few vlans, allowing them in a switchport (that goes to a NX1KV trunk port), defined a few SVIs for these VLANs and trying to ping the SVI of a L3 switch connected to the same vlans. As expected was a success,- it crashed just as before: N7K-2# sh ver Cisco Nexus Operating System (NX-OS) Software. Etc etc etc Software loader: version N/A kickstart: version 6.1(1) gdb system: version 6.1(1) gdb kickstart image file is: bootflash:/titanium-d1-kickstart.6.1.1.gbin kickstart compile time: 12:00:00 05:54:16 system image file is: bootflash:/titanium-d1.6.1.1.gbin system compile time: 7/1/2012 0:00:00 06:26:13. N7K-2# ping 10.100.2.1 PING 10.100.2.1 (10.100.2.1): 56 data bytes 36 bytes from 10.100.2.10: Destination Host Unreachable INIT: Sending processes the TERM signal.
Etc, etc, etc Sending all processes the TERM signal. Sending all processes the KILL signal. Unmounting filesystems. Restarting system.
Auto booting bootflash:/titanium-d1-kickstart.6.1.1.gbin bootflash:/titanium-d1.6.1.1.gbin. Booting kickstart image: bootflash:/titanium-d1-kickstart.6.1.1.gbin.Image verification OK. Hi, got this to run on virtualbox on Windows and Linux but I have the same problem on both. I can connect 2 Titanium instances together, ping each other but I can't do any L2 bridging. My specific goal was to set up OTV. I successfully create the OTV sites, get the overlays into an UP state but since L2 doesn't seem to be functioning, I can't connect the 2 sites subnets together. I never see any packets entering the switchport on Titianium that I assigned to teh vlan that I am extending.
I have tried both directly connecting the host to the titanium port as well as tried running both connections to a GNS3 ethernet switch. Anyone else have any luck with getting interesing scenarios constructed? Anyone have any ideas on how to get L2 working? I am a Mac user and did not have a windows 7 work station readily available to run VMware Workstation on to get into titanium. So naturally I wanted to run titanium in VMware fusion. After a lot of wasted time and fumbling. I could not access the pipe at.pipecom1 from OS X with titanium running in fusion.
Cisco Nexus 5000
I found another version of titanium 5.1.2 on the internet and found these lines of code in the vmx file: serial0.present = 'TRUE' serial0.yieldOnMsrRead = 'TRUE' serial0.fileType = 'network' serial0.fileName = 'telnet://127.0.0.1:9001' And then a simple telnet localhost 9001 and boom! I am in a virtual nexus 7k, titanium. If your getting this. System is coming up. System is coming up. System is coming up. System is coming up.
System is coming up. System is coming up. System is coming up. System is coming up. System is coming up. System is coming up.
System is coming up. Then ctrl c and it will say Exiting the basic config setup. Then login with username and password it will then let you into the system.:).