Does the 3903x have a management port?
Hi Mitchell, I'm working on confirming the answer to your question, but in the meantime, you may find the information at: 3903x Service Delivery Switch and the data sheet helpful in learning more about 3903x. If you have any additional questions after reviewing it, please ask in the comments on this thread and we can help with them too.
Hi Mitchell Lewis. Thanks for your question.
Yes, the 3903X has Serial EIA-561 (RJ-45) console port that can be used to manage it via CLI locally.
Also, it has four service interfaces:
- 1 x RJ-45 combo port of 10/100/1000 Base-T copper Ethernet. This portis active when an optic is not installed in the corresponding SFP port(port 1).
- 1 x SFP port of 100 FX/1 Gig Ethernet using standard SFP modules.This port supports multiple SFP types to accommodate differentwavelengths and reach - 2 x ports of 100 FX/1 Gig Ethernet using standard SFP optics. Each portsupports multiple SFP types to accommodate different wavelengthsand reach. Copper or optical SFPs can be installed.
Hope it answered your question and let us know if we can help you clarify anything else
Hi Mitchell, Welcome to Ciena's Packet Networking forum.
I'm assuming you are probably referring to the local management port that hosts the local management interface seen on the majority of Ciena's Packet Networking devices. Some of the smaller Packet Networking devices, including the 3903x does not have this port, instead device management can be achieved as per what Vinicius described above, which is either through the console port, or via the remote management interface on any of the 3 front-panel ports on the device itself. Note that on the 3903x, the factory default configuration has all 3 front-panel ports assigned to the (remote interface) management VLAN 127.
That is what I was referring to. Does the remote management ip address have an ip address assigned to it by default?
Unlike the local interface, which does have a default IP address, the remote interface on the 3903x does not have a default IP address. The assignment of the IP address(es) for the remote interface would need to be configured or be assigned via DHCP/DHCPv6 (typically during the zero-touch provisioning (ZTP) phase).
Does the 3903x look for a dhcp lease by default?
Yes indeed, it is part of the zero-touch provisioning functionality of Packet Networking devices, including the 3903x. In a nutshell, the device by default will send out DHCP discovery frames out each NNI port of the device in an effort to handshake with a DHCP server to obtain an IP address for the remote interface, but is also utilised to obtain information to retrieve the initial configuration for the device. The retrieved initial configuration may or may not also contain the static configuration for the remote interface.
For more information, I recommend referencing the Zero Touch Provisioning section in 3903x Service Delivery Switch Installation and Startup guide
Feel free to ask further questions here if needed.
So this could be used in lieu of console for telnet/SSH access even without ZTP?
I'm not sure if I fully understand your question, but will provide an attempt to answer it.
As you are well aware, there are two mechanisms available to configure the device (console and remote interface), so technically you can configure the remote management interface (including the IP address) via the console port, and then have management (including telnet/SSH) access to the box via the remote interface.
Otherwise if you're depending on a DHCP server to provide the IP address, and you know the IP address that will be offered to the device by the server, I believe you should have access to the device via that IP address (and typically over default management VLAN 127) after the DHCP handshake has completed.
Thank you. That answers my question. I am having a bit of difficulty with my console cable to access the console of the box so I will try letting the remote interface get a dhcp lease & then login via ssh/telnet. I will report back.
I reset the 3903x to factory defaults. I connected my pc to port 1(Built in 10/100/1000 port) & opened wireshark to do a packet capture. I did not observe a DHCP request from the 3903x.
Am I missing something?
Fortunately I have a nice Ciena Lab. 5305's, 5140's 3960's, 3940's, 3930's,3920's, 3916's, 3911, 3903's 3902, 311V's. For the newer products with an RJ45 console port I connect to them through my Cisco 26xx Terminal Servers. Its the only way to rolll. I had to make all the cables but it works great.
Sorry to hear you're still having issues with the box. I'm surprised to hear that you're not seeing any DHCP requests/discovery messages being sent by the 3903x via port 1 after a factory reset. Are you receiving any frames from the 3903x, such as LLDP frames? I'm thinking we may be at a point that it may be best to get some dedicated expert assistance through Ciena technical support to help solve this issue more quickly for you.
I am seeing lldp frames. Perhaps the device is not reset properly. To reset the reset button is held for 10 seconds correct?
Looks like a hard reset is 3 seconds, here's a snippet on it from the same guide I mentioned earlier....
• Hard reset, which is accomplished by depressing the reset button for 3 seconds or more continuously. A hard reset is necessary when the quick reset does not work. When you press the reset button for more than 3 seconds, all the LEDs on the faceplate will be lit, then they will flash to indicate that the hard reset has been initiated. A hard reset erases the current configuration and restores the unit to the factory default settings.
I was able to get in. The DHCP lease request is sent out via a tagged ethernet frame with a vlan id of 127 so the far end port needs to have tagging enabled.
I was able to successfully telnet in after DHCP lease was obtained.
Retrieving data ...