There are times when we need to access a hardware device via out-of-band management to troubleshoot an issue or perform activities like staging. The most common method of out-of-band management is to access a device via “Console”. This document talks about the other method of out-of-band management, which is via Eth0 (also called the “management port”)

All hardware devices have a management port which is Eth0 (hardware port), below is a screenshot of the rear-view of CSG355 hardware – highlighted is the location of the management port. Different hardware models have different locations for the management port – please study the installation guide, or product guide, for an understanding of the location of the Eth0 on your respective hardware model

The default address assigned to Eth0 is 10.10.10.10/8

So, in order to access a hardware via Eth0 you would need a laptop which is “statically” configured with the address in the above subnet range – for ex, 10.10.10.9/8. You can set it up on the laptop as below

<you can configure the subnet mask as 255.0.0.0 or 255.255.255.0 – it doesn’t matter>

Once you’ve configured the above address on the laptop, you can connect the laptop to Eth0 port of the hardware

First try pinging 10.10.10.10 from the command prompt

If the ping succeeds, you can open a putty terminal (or any other application that you use for terminal access) and ssh to 10.10.10.10 using credentials admin/versa123

You can modify the eth0 address as below. 

Note: These changes should either be made via console access or via ssh access to the device from the director (say Director "shell in box" access to the device or from Director shell you can ssh to the device's tvi addresss)

Since it's basically a ubuntu/linux interface and not part of VOS, you can modify it by changing the address configured in /etc/network/interfaces file

post which you will need to flap the interface once for the new address to take effect

 In /etc/network/interfaces file you can modify the address and subnet mask

 Save the file, and execute "sudo ifdown eth0" followed by "sudo ifup eth0" (ignore if any error is printed at this point)

Execute "ip addr | less" and verify if eth0 status is UP and if the new address has taken effect

You can also verify "show interfaces brief" on the cli

Please not that you are managing reachability to eth0 in your infra through an underlay of routers/switches, you will need to ensure reachability to the new address in your infra so that it's reachable from your jump server