Missing Interfaces in

2000px-Former_Ubuntu_logo.svg

Have you have ever been in a situation (typically in a virtualised environment) where you have added another network adapter & it didn’t seem to appear in Ubuntu? In the following example, I added a second interface, however it didn’t just simply appear. The following is this issue was resolved.

~$ ifconfig
ens160: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.115.199 netmask 255.255.255.0 broadcast 192.168.115.255
inet6 fe80::250:56ff:fe9c:a2df prefixlen 64 scopeid 0x20<link>
ether 00:50:56:9c:a2:df txqueuelen 1000 (Ethernet)
RX packets 2846 bytes 359600 (359.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 159 bytes 18009 (18.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 358 bytes 26926 (26.9 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 358 bytes 26926 (26.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

As you can see in the ‘ifconfig’ output, there is no additional ethernet interface. So lets use the command ‘ip link’

~$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 00:50:56:9c:a2:df brd ff:ff:ff:ff:ff:ff
3: ens192: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:50:56:9c:56:c4 brd ff:ff:ff:ff:ff:ff

You can see that there is in fact an additional interface, however it hasn’t been configured yet. So lets use nano to edit the interfaces file and add it.

~$ sudo nano /etc/network/interfaces

 

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto ens160
iface ens160 inet static
address xxx.xxx.xxx.xxx
netmask 255.255.255.0
network xxx.xxx.xxx.xxx
broadcast xxx.xxx.xxx.xxx
gateway xxx.xxx.xxx.xxx
auto ens192
iface ens192 inet dhcp

We add the additional information underlined in this example, exit & save, then we need to restart the network service

~$ sudo systemctl restart networking

Be warned, if you are logged into the server via SSH, your connection will drop, as you’re restarting the whole networking service. Run the ‘ifconfig’ command again to verify that you have your new interface.

~$ ifconfig
ens160: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.115.199 netmask 255.255.255.0 broadcast 192.168.115.255
inet6 fe80::250:56ff:fe9c:a2df prefixlen 64 scopeid 0x20<link>
ether 00:50:56:9c:a2:df txqueuelen 1000 (Ethernet)
RX packets 622 bytes 74509 (74.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 79 bytes 10801 (10.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

ens192: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::250:56ff:fe9c:56c4 prefixlen 64 scopeid 0x20<link>
ether 00:50:56:9c:56:c4 txqueuelen 1000 (Ethernet)
RX packets 25 bytes 4043 (4.0 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 19 bytes 2897 (2.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 367 bytes 27739 (27.7 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 367 bytes 27739 (27.7 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

As we can see by the output, we now have the new interface.

 

Advertisements

Avaya ACE-Fx

url

This week I took the Avaya ACE-Fx 5 day course & exam (7501C). The course is made up of 4 days with two exams, a lab (7582X) & a theory / written exam (7590X) both on the 5th day. Simply passing the theory exam will earn you an Avaya ‘ACIS’ certification. In addition to passing theory, once you successfully complete the lab exam you have completed ACE-Fx Part 1 & are then ACE-Fx certified. But only for 2 years, then you will need to re-certify or complete Part 2 (7502C). What do I mean by Part 2 you may be asking.. Well I was asking the same question. It seems that Part 1 covers the basics of Fabric Connect, Fabric Attach & a bit of Fabric Extend. Part 2 goes for a deeper dive on those topics, along with specialised topics, such as complex multicast deployments.

All that to say that I passed & was quite pleased with the result. 100% on the lab & 88% on the theory.

 

Packet Pushers Show 210 – SPB Implementation Fundamentals

imgres

Back in October 2014, Dominik & myself spoke on an episode of the Packet Pushers podcast about Shortest Path Bridging & Avaya’s implementation of SPBm.

I had almost forgot about this until I was looking around for some information & discovered that Michael McNamara had mentioned it on his blog too.

https://blog.michaelfmcnamara.com/2014/11/avaya-spb-implementations-packet-pushers/

http://packetpushers.net/podcast/podcasts/show-210-spb-implementation-fundamentals/

VLANS & port modes on Juniper EX series

ex4300-48

root> configure

CREATE THE VLAN

root# set vlans MYVLAN vlan-id 100

ADD THE VLAN TO AN ACCESS PORT

root# set interfaces xe-0/0/0 unit 0 family ethernet-switching port-mode access vlan members MYVLAN

root# commit

ADD THE VLAN TO A TRUNK (TAGGED) PORT

root# set interfaces xe-0/0/0 unit 0 family ethernet-switching port-mode trunk vlan members MYVLAN

root# commit

 

Setting the management interface IP address on Palo Alto Networks Firewalls via CLI

imgresimgres

>configure

# set deviceconfig system ip-address 10.0.0.2 netmask 255.255.255.0 default-gateway 10.0.0.1 dns-setting servers primary 8.8.8.8

# commit

Password Recovery on Cisco 1800 series

1841800px-Cisco_logo.svg

Every now & then I have to reset or reconfigure an older Cisco device that I come across in my day to day. This is just for me personally to remember. If it helps you too, then your welcome! 😉

Please see the regular process to reset the password on 1841 Router below,

  • Use the console to connect to the 1841
  • Use the power switch in order to turn off the router, and then turn the router back on
  • SEND BREAK within 60 seconds of power up in order to put the router into ROMMON
  • Type confreg 0x2142 at the rommon 1> prompt in order to boot from Flash

This step bypasses the startup configuration where the passwords are stored

  • Type reset at the rommon 2> reset

The router reboots, but ignores the saved configuration.

  • Type no after each setup question, or press Ctrl-C in order to skip the initial setup procedure.
  • Type enable at the Router> prompt.
  • You are in enable mode and should see the Router# prompt.
  • Type copy startup-config running-config in order to copy the nonvolatile RAM (NVRAM) into memory.

Important:

Do not type copy running-config startup-config or write. These commands erase your startup           configuration.

  • Type configure terminal
  • Type #enable secret <password> in order to change the enable secret password.
  • Type config-register #config-register 0x2102
  • Type write memory or #copy running-config startup-config in order to commit the changes
  • RELOAD

Refer:

http://www.cisco.com/en/US/products/hw/routers/ps221/products_password_recovery09186a0080094773.shtml

Avaya Fabric Connect !!!

imgresurl

Anyone who knows me will know I’m pretty excited about what Avaya are doing with the IEEE 802.1aq standard “Shortest Path Bridging”. Avaya’s implementation is called “Fabric Connect”. I’ll be discussing my real world use case of Fabric Connect while I work through my next project, which is an all Avaya deployment in a high definition broadcast environment. Essentially Avaya is replacing an existing all Cisco infrastructure as the business needs for high bandwidth multicast rises well above email, web & SQL traffic. For now, please check out the Packet Pushers podcasts & view these videos from previous Network Field Day’s during their visit to Avaya for briefings on SPB & Fabric Connect.

Show 136: Avaya – Considerations for Turning your Network into an Ethernet Fabric

Show 147 – Avaya Fabric Connect Makes Multicast Simple (Really)

Show 158 – Avaya – Software Defined Data Centre & Fabric Connect

Show 179 – Avaya Efficient Data Center Design at Fujitsu & the Sochi 2014 Winter Games

Show 202 – Avaya & The Critical Importance of the SDN Underlay

Show 204 – Reducing Your Attack Surface with Avaya Stealth Networks