Network Device Configuration Behaviour (Static vs. DHCP)

5. RE: Network Device Configuration Behaviour (Static vs. DHCP)

Recommend

Session

Posted 01-12-2020 08:55

Patrick,

Certainly, it is below (I couldn't figure out how to copy-and-paste it in while maintaining formatting using the editor).

My question is prompted by the vendor of the vnf infrastructure I'm trying to run the router within. The issue I'm trying to resolve is once the IP, Gateway and netmask are configured using the Conductor, the router is no longer accessible via. ssh and it cannot 'phone home' to the conductor. The vnf manager behaves differently depending on how IPs are being configured (static vs. dynamic). The configuration I'm using is a static one but there is enough 'it looks enough like DHCP we need to ask questions' on the vendors side which prompted this question about the behaviour of the system.

----------------------------------------------
BEGIN ROUTER CONFIGURATION
----------------------------------------------
show config running authority router cmc-dv-eneaucpe-1

config

authority

router cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
inter-node-security internal

node cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
asset-id cmc-dv-enenaucpe-1-3
role combo

device-interface wan-pri
name wan-pri
pci-address 0000:00:03.0

network-interface eth1
name eth1
global-id 38
conductor true
inter-router-security internal
source-nat true

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164
exit
exit
exit
exit

service-route _conductor_1_route_1
name _conductor_1_route_1
service-name _conductor_1
generated true

next-hop cmc-dv-eneaucpe-1 eth1
node-name cmc-dv-eneaucpe-1
interface eth1
gateway-ip 102.177.116.164
exit
exit
exit
exit
exit
----------------------------------------------
END ROUTER CONFIGURATION
----------------------------------------------

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ
------------------------------

Original Message

8. RE: Network Device Configuration Behaviour (Static vs. DHCP)

Recommend

Session

Posted 01-13-2020 07:16

Hello Patrick,

It's not off by one. The KNI has two IP addresses, one in Linux's interface table and one in 128T's interface table. They are .127 and .126, respectively. Is this the 169. address you've been referring to?

Yes, it is. Is the 'ip a s' output I posted correct then?

The device type defaulted to Ethernet, so I did not change it. Screenshot below:

I have added a 'ssh' host service to the device interface configuration. The distributor I have been speaking with had indicated it was not required for our scenario.

I changed the ssh-host configuration to this (snipped from show config running authority router cmc-dv-eneaucpe-1). As mentioned the device type was defaulted to Ethernet and remains unchanged.

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164

host-service ssh
service-type ssh

access-policy cmc-dv-lab
source cmc-dv-lab
exit

access-policy /cmc-dv-inet
source /cmc-dv-inet

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ
------------------------------

Original Message

9. RE: Network Device Configuration Behaviour (Static vs. DHCP)

Recommend

peetee

Posted 01-13-2020 07:53

Hi Robert, please change it to type=ethernet in the PCLI. There is a UI bug that makes it look like your interface type is ethernet when it is not.

------------------------------
pt.
------------------------------

Original Message

10. RE: Network Device Configuration Behaviour (Static vs. DHCP)

Recommend

Session

Posted 01-13-2020 08:20

Hello Patrick,

I have made the change. The system still does not contact the Conductor afterwards.

<x-row>show config running authority router cmc-dv-eneaucpe-1

config

authority

router cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
inter-node-security internal

node cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
asset-id cmc-dv-enenaucpe-1-4
role combo

device-interface wan-pri
name wan-pri
type ethernet
pci-address 0000:00:03.0

network-interface eth1
name eth1
global-id 38
conductor true
inter-router-security internal
source-nat true

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164
host-service ssh
service-type ssh
access-policy cmc-dv-lab
source cmc-dv-lab
exit
access-policy /cmc-dv-inet
source /cmc-dv-inet
exit
exit
exit
exit
exit
exit
service-route _conductor_1_route_1
name _conductor_1_route_1
service-name _conductor_1
generated true
next-hop cmc-dv-eneaucpe-1 eth1
node-name cmc-dv-eneaucpe-1
interface eth1
gateway-ip 102.177.116.164
exit
exit
exit
exit
exit</x-row>

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ
------------------------------

Original Message

11. RE: Network Device Configuration Behaviour (Static vs. DHCP)

Recommend

peetee

Posted 01-13-2020 08:33

Please attach the output of "show device summary" and "show network-interface"?

------------------------------
pt.
------------------------------

Original Message

12. RE: Network Device Configuration Behaviour (Static vs. DHCP)

Recommend

Session

Posted 01-13-2020 08:45

From the Router:

[centos@vnfi_128t_router_h7mvmq_1 ~]$ sudo su - admin
Last failed login: Mon Jan 13 12:46:47 UTC 2020 on ttyS0
There were 3 failed login attempts since the last successful login.
Starting the PCLI...
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show network-interface
Mon 2020-01-13 13:41:33 UTC
<Send CTRL+C>
Completed in 30.86 seconds
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1#

No output was produced. So I let it run until timeout:

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ
------------------------------

Original Message

13. RE: Network Device Configuration Behaviour (Static vs. DHCP)

Recommend

peetee

Posted 01-13-2020 09:45

I'm afraid that troubleshooting this may be beyond the scope of our back-and-forth in the community. There's something more fundamental wrong with this installation that will require deeper investigation. Can you please open a ticket with our support team?

------------------------------
pt.
------------------------------

Original Message

Original Message:
Sent: 01-13-2020 08:45
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

From the Router:

[centos@vnfi_128t_router_h7mvmq_1 ~]$ sudo su - admin
Last failed login: Mon Jan 13 12:46:47 UTC 2020 on ttyS0
There were 3 failed login attempts since the last successful login.
Starting the PCLI...
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show network-interface
Mon 2020-01-13 13:41:33 UTC
<Send CTRL+C>
Completed in 30.86 seconds
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1#

No output was produced. So I let it run until timeout:

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 08:32
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Please attach the output of "show device summary" and "show network-interface"?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 08:20
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hello Patrick,

I have made the change. The system still does not contact the Conductor afterwards.

<x-row>show config running authority router cmc-dv-eneaucpe-1

config

authority

router cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
inter-node-security internal

node cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
asset-id cmc-dv-enenaucpe-1-4
role combo

device-interface wan-pri
name wan-pri
type ethernet
pci-address 0000:00:03.0

network-interface eth1
name eth1
global-id 38
conductor true
inter-router-security internal
source-nat true

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164
host-service ssh
service-type ssh
access-policy cmc-dv-lab
source cmc-dv-lab
exit
access-policy /cmc-dv-inet
source /cmc-dv-inet
exit
exit
exit
exit
exit
exit
service-route _conductor_1_route_1
name _conductor_1_route_1
service-name _conductor_1
generated true
next-hop cmc-dv-eneaucpe-1 eth1
node-name cmc-dv-eneaucpe-1
interface eth1
gateway-ip 102.177.116.164
exit
exit
exit
exit
exit</x-row>

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 07:52
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hi Robert, please change it to type=ethernet in the PCLI. There is a UI bug that makes it look like your interface type is ethernet when it is not.

------------------------------
pt.

Original Message:
Sent: 01-13-2020 07:16
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hello Patrick,

It's not off by one. The KNI has two IP addresses, one in Linux's interface table and one in 128T's interface table. They are .127 and .126, respectively. Is this the 169. address you've been referring to?

Yes, it is. Is the 'ip a s' output I posted correct then?

The device type defaulted to Ethernet, so I did not change it. Screenshot below:

I have added a 'ssh' host service to the device interface configuration. The distributor I have been speaking with had indicated it was not required for our scenario.

I changed the ssh-host configuration to this (snipped from show config running authority router cmc-dv-eneaucpe-1). As mentioned the device type was defaulted to Ethernet and remains unchanged.

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164

host-service ssh
service-type ssh

access-policy cmc-dv-lab
source cmc-dv-lab
exit

access-policy /cmc-dv-inet
source /cmc-dv-inet

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 06:39
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

It's not off by one. The KNI has two IP addresses, one in Linux's interface table and one in 128T's interface table. They are .127 and .126, respectively. Is this the 169. address you've been referring to?

In your device-interface configuration you're missing type=ethernet. (You also don't have any host-service configured to allow inbound SSH, so you'll need to add that in order to SSH back into that address, too.)

Please add type=ethernet to your device-interface configuration and let us know the results. Include with them a copy of the output of "show device summary" and "show network-interface" from the router, if you have access to its console after the 128T system starts up.

------------------------------
pt.

Original Message:
Sent: 01-12-2020 21:53
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

This is the 128T Router VM's network interface configuration after the config has been applied. The kni network interface is different than what you listed, but it's only 'off by one'. Was it a typo or significant?

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:c5:b8:41 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.2/24 brd 10.0.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fec5:b841/64 scope link
valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:05:26:d9 brd ff:ff:ff:ff:ff:ff
inet 192.168.64.1/24 brd 192.168.64.255 scope global eth2
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe05:26d9/64 scope link
valid_lft forever preferred_lft forever
5: kni254: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether ae:54:29:70:05:12 brd ff:ff:ff:ff:ff:ff
inet 169.254.127.127/31 brd 255.255.255.255 scope global kni254
valid_lft forever preferred_lft forever

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-11-2020 07:49
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

I don't quite follow the question... what type of interface are you creating?

Note that the 128T will create (at least) one interface, known as a "KNI" or kernel network interface, to shuttle packets between the Linux host operating system and the 128T's forwarding plane. This interface has a 169.254.127.126/31 address, and may be what you're seeing?

If you post an excerpt of your configuration here and let us know what you're trying to get working, we'll be happy to help out.

------------------------------
pt.

Original Message:
Sent: 01-10-2020 17:38
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Should be a simple question, after I configure an IP address in the Conductor, when I look at the network configuration of the running system it is creating the 169.* addresses like I would expect in an dhcp-system, but I configured the IP address in the normal way using the Conductor.

Where can I find more information about how the behaviour works?

Thanks!

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ
------------------------------

14. RE: Network Device Configuration Behaviour (Static vs. DHCP)

Recommend

Session

Posted 01-13-2020 09:50

How would I do so?

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ
------------------------------

Original Message

Original Message:
Sent: 01-13-2020 09:45
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

I'm afraid that troubleshooting this may be beyond the scope of our back-and-forth in the community. There's something more fundamental wrong with this installation that will require deeper investigation. Can you please open a ticket with our support team?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 08:45
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

From the Router:

[centos@vnfi_128t_router_h7mvmq_1 ~]$ sudo su - admin
Last failed login: Mon Jan 13 12:46:47 UTC 2020 on ttyS0
There were 3 failed login attempts since the last successful login.
Starting the PCLI...
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show network-interface
Mon 2020-01-13 13:41:33 UTC
<Send CTRL+C>
Completed in 30.86 seconds
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1#

No output was produced. So I let it run until timeout:

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 08:32
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Please attach the output of "show device summary" and "show network-interface"?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 08:20
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hello Patrick,

I have made the change. The system still does not contact the Conductor afterwards.

<x-row>show config running authority router cmc-dv-eneaucpe-1

config

authority

router cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
inter-node-security internal

node cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
asset-id cmc-dv-enenaucpe-1-4
role combo

device-interface wan-pri
name wan-pri
type ethernet
pci-address 0000:00:03.0

network-interface eth1
name eth1
global-id 38
conductor true
inter-router-security internal
source-nat true

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164
host-service ssh
service-type ssh
access-policy cmc-dv-lab
source cmc-dv-lab
exit
access-policy /cmc-dv-inet
source /cmc-dv-inet
exit
exit
exit
exit
exit
exit
service-route _conductor_1_route_1
name _conductor_1_route_1
service-name _conductor_1
generated true
next-hop cmc-dv-eneaucpe-1 eth1
node-name cmc-dv-eneaucpe-1
interface eth1
gateway-ip 102.177.116.164
exit
exit
exit
exit
exit</x-row>

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 07:52
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hi Robert, please change it to type=ethernet in the PCLI. There is a UI bug that makes it look like your interface type is ethernet when it is not.

------------------------------
pt.

Original Message:
Sent: 01-13-2020 07:16
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hello Patrick,

It's not off by one. The KNI has two IP addresses, one in Linux's interface table and one in 128T's interface table. They are .127 and .126, respectively. Is this the 169. address you've been referring to?

Yes, it is. Is the 'ip a s' output I posted correct then?

The device type defaulted to Ethernet, so I did not change it. Screenshot below:

I have added a 'ssh' host service to the device interface configuration. The distributor I have been speaking with had indicated it was not required for our scenario.

I changed the ssh-host configuration to this (snipped from show config running authority router cmc-dv-eneaucpe-1). As mentioned the device type was defaulted to Ethernet and remains unchanged.

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164

host-service ssh
service-type ssh

access-policy cmc-dv-lab
source cmc-dv-lab
exit

access-policy /cmc-dv-inet
source /cmc-dv-inet

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 06:39
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

It's not off by one. The KNI has two IP addresses, one in Linux's interface table and one in 128T's interface table. They are .127 and .126, respectively. Is this the 169. address you've been referring to?

In your device-interface configuration you're missing type=ethernet. (You also don't have any host-service configured to allow inbound SSH, so you'll need to add that in order to SSH back into that address, too.)

Please add type=ethernet to your device-interface configuration and let us know the results. Include with them a copy of the output of "show device summary" and "show network-interface" from the router, if you have access to its console after the 128T system starts up.

------------------------------
pt.

Original Message:
Sent: 01-12-2020 21:53
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

This is the 128T Router VM's network interface configuration after the config has been applied. The kni network interface is different than what you listed, but it's only 'off by one'. Was it a typo or significant?

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:c5:b8:41 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.2/24 brd 10.0.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fec5:b841/64 scope link
valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:05:26:d9 brd ff:ff:ff:ff:ff:ff
inet 192.168.64.1/24 brd 192.168.64.255 scope global eth2
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe05:26d9/64 scope link
valid_lft forever preferred_lft forever
5: kni254: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether ae:54:29:70:05:12 brd ff:ff:ff:ff:ff:ff
inet 169.254.127.127/31 brd 255.255.255.255 scope global kni254
valid_lft forever preferred_lft forever

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-11-2020 07:49
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

I don't quite follow the question... what type of interface are you creating?

Note that the 128T will create (at least) one interface, known as a "KNI" or kernel network interface, to shuttle packets between the Linux host operating system and the 128T's forwarding plane. This interface has a 169.254.127.126/31 address, and may be what you're seeing?

If you post an excerpt of your configuration here and let us know what you're trying to get working, we'll be happy to help out.

------------------------------
pt.

Original Message:
Sent: 01-10-2020 17:38
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Should be a simple question, after I configure an IP address in the Conductor, when I look at the network configuration of the running system it is creating the 169.* addresses like I would expect in an dhcp-system, but I configured the IP address in the normal way using the Conductor.

Where can I find more information about how the behaviour works?

Thanks!

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ
------------------------------

15. RE: Network Device Configuration Behaviour (Static vs. DHCP)

Recommend

peetee

Posted 01-13-2020 10:03

Do you have a support contract with 128 Technology?

------------------------------
pt.
------------------------------

Original Message

Original Message:
Sent: 01-13-2020 09:49
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

How would I do so?

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 09:45
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

I'm afraid that troubleshooting this may be beyond the scope of our back-and-forth in the community. There's something more fundamental wrong with this installation that will require deeper investigation. Can you please open a ticket with our support team?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 08:45
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

From the Router:

[centos@vnfi_128t_router_h7mvmq_1 ~]$ sudo su - admin
Last failed login: Mon Jan 13 12:46:47 UTC 2020 on ttyS0
There were 3 failed login attempts since the last successful login.
Starting the PCLI...
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show network-interface
Mon 2020-01-13 13:41:33 UTC
<Send CTRL+C>
Completed in 30.86 seconds
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1#

No output was produced. So I let it run until timeout:

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 08:32
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Please attach the output of "show device summary" and "show network-interface"?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 08:20
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hello Patrick,

I have made the change. The system still does not contact the Conductor afterwards.

<x-row>show config running authority router cmc-dv-eneaucpe-1

config

authority

router cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
inter-node-security internal

node cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
asset-id cmc-dv-enenaucpe-1-4
role combo

device-interface wan-pri
name wan-pri
type ethernet
pci-address 0000:00:03.0

network-interface eth1
name eth1
global-id 38
conductor true
inter-router-security internal
source-nat true

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164
host-service ssh
service-type ssh
access-policy cmc-dv-lab
source cmc-dv-lab
exit
access-policy /cmc-dv-inet
source /cmc-dv-inet
exit
exit
exit
exit
exit
exit
service-route _conductor_1_route_1
name _conductor_1_route_1
service-name _conductor_1
generated true
next-hop cmc-dv-eneaucpe-1 eth1
node-name cmc-dv-eneaucpe-1
interface eth1
gateway-ip 102.177.116.164
exit
exit
exit
exit
exit</x-row>

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 07:52
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hi Robert, please change it to type=ethernet in the PCLI. There is a UI bug that makes it look like your interface type is ethernet when it is not.

------------------------------
pt.

Original Message:
Sent: 01-13-2020 07:16
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hello Patrick,

It's not off by one. The KNI has two IP addresses, one in Linux's interface table and one in 128T's interface table. They are .127 and .126, respectively. Is this the 169. address you've been referring to?

Yes, it is. Is the 'ip a s' output I posted correct then?

The device type defaulted to Ethernet, so I did not change it. Screenshot below:

I have added a 'ssh' host service to the device interface configuration. The distributor I have been speaking with had indicated it was not required for our scenario.

I changed the ssh-host configuration to this (snipped from show config running authority router cmc-dv-eneaucpe-1). As mentioned the device type was defaulted to Ethernet and remains unchanged.

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164

host-service ssh
service-type ssh

access-policy cmc-dv-lab
source cmc-dv-lab
exit

access-policy /cmc-dv-inet
source /cmc-dv-inet

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 06:39
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

It's not off by one. The KNI has two IP addresses, one in Linux's interface table and one in 128T's interface table. They are .127 and .126, respectively. Is this the 169. address you've been referring to?

In your device-interface configuration you're missing type=ethernet. (You also don't have any host-service configured to allow inbound SSH, so you'll need to add that in order to SSH back into that address, too.)

Please add type=ethernet to your device-interface configuration and let us know the results. Include with them a copy of the output of "show device summary" and "show network-interface" from the router, if you have access to its console after the 128T system starts up.

------------------------------
pt.

Original Message:
Sent: 01-12-2020 21:53
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

This is the 128T Router VM's network interface configuration after the config has been applied. The kni network interface is different than what you listed, but it's only 'off by one'. Was it a typo or significant?

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:c5:b8:41 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.2/24 brd 10.0.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fec5:b841/64 scope link
valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:05:26:d9 brd ff:ff:ff:ff:ff:ff
inet 192.168.64.1/24 brd 192.168.64.255 scope global eth2
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe05:26d9/64 scope link
valid_lft forever preferred_lft forever
5: kni254: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether ae:54:29:70:05:12 brd ff:ff:ff:ff:ff:ff
inet 169.254.127.127/31 brd 255.255.255.255 scope global kni254
valid_lft forever preferred_lft forever

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-11-2020 07:49
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

I don't quite follow the question... what type of interface are you creating?

Note that the 128T will create (at least) one interface, known as a "KNI" or kernel network interface, to shuttle packets between the Linux host operating system and the 128T's forwarding plane. This interface has a 169.254.127.126/31 address, and may be what you're seeing?

If you post an excerpt of your configuration here and let us know what you're trying to get working, we'll be happy to help out.

------------------------------
pt.

Original Message:
Sent: 01-10-2020 17:38
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Should be a simple question, after I configure an IP address in the Conductor, when I look at the network configuration of the running system it is creating the 169.* addresses like I would expect in an dhcp-system, but I configured the IP address in the normal way using the Conductor.

Where can I find more information about how the behaviour works?

Thanks!

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ
------------------------------

16. RE: Network Device Configuration Behaviour (Static vs. DHCP)

Recommend

Session

Posted 01-13-2020 10:06

My contact is Lane Shields. Previously he directed me to the community when I have had questions of this sort.

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ
------------------------------

Original Message

Original Message:
Sent: 01-13-2020 10:02
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Do you have a support contract with 128 Technology?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 09:49
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

How would I do so?

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 09:45
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

I'm afraid that troubleshooting this may be beyond the scope of our back-and-forth in the community. There's something more fundamental wrong with this installation that will require deeper investigation. Can you please open a ticket with our support team?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 08:45
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

From the Router:

[centos@vnfi_128t_router_h7mvmq_1 ~]$ sudo su - admin
Last failed login: Mon Jan 13 12:46:47 UTC 2020 on ttyS0
There were 3 failed login attempts since the last successful login.
Starting the PCLI...
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show network-interface
Mon 2020-01-13 13:41:33 UTC
<Send CTRL+C>
Completed in 30.86 seconds
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1#

No output was produced. So I let it run until timeout:

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 08:32
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Please attach the output of "show device summary" and "show network-interface"?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 08:20
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hello Patrick,

I have made the change. The system still does not contact the Conductor afterwards.

<x-row>show config running authority router cmc-dv-eneaucpe-1

config

authority

router cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
inter-node-security internal

node cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
asset-id cmc-dv-enenaucpe-1-4
role combo

device-interface wan-pri
name wan-pri
type ethernet
pci-address 0000:00:03.0

network-interface eth1
name eth1
global-id 38
conductor true
inter-router-security internal
source-nat true

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164
host-service ssh
service-type ssh
access-policy cmc-dv-lab
source cmc-dv-lab
exit
access-policy /cmc-dv-inet
source /cmc-dv-inet
exit
exit
exit
exit
exit
exit
service-route _conductor_1_route_1
name _conductor_1_route_1
service-name _conductor_1
generated true
next-hop cmc-dv-eneaucpe-1 eth1
node-name cmc-dv-eneaucpe-1
interface eth1
gateway-ip 102.177.116.164
exit
exit
exit
exit
exit</x-row>

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 07:52
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hi Robert, please change it to type=ethernet in the PCLI. There is a UI bug that makes it look like your interface type is ethernet when it is not.

------------------------------
pt.

Original Message:
Sent: 01-13-2020 07:16
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hello Patrick,

It's not off by one. The KNI has two IP addresses, one in Linux's interface table and one in 128T's interface table. They are .127 and .126, respectively. Is this the 169. address you've been referring to?

Yes, it is. Is the 'ip a s' output I posted correct then?

The device type defaulted to Ethernet, so I did not change it. Screenshot below:

I have added a 'ssh' host service to the device interface configuration. The distributor I have been speaking with had indicated it was not required for our scenario.

I changed the ssh-host configuration to this (snipped from show config running authority router cmc-dv-eneaucpe-1). As mentioned the device type was defaulted to Ethernet and remains unchanged.

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164

host-service ssh
service-type ssh

access-policy cmc-dv-lab
source cmc-dv-lab
exit

access-policy /cmc-dv-inet
source /cmc-dv-inet

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 06:39
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

It's not off by one. The KNI has two IP addresses, one in Linux's interface table and one in 128T's interface table. They are .127 and .126, respectively. Is this the 169. address you've been referring to?

In your device-interface configuration you're missing type=ethernet. (You also don't have any host-service configured to allow inbound SSH, so you'll need to add that in order to SSH back into that address, too.)

Please add type=ethernet to your device-interface configuration and let us know the results. Include with them a copy of the output of "show device summary" and "show network-interface" from the router, if you have access to its console after the 128T system starts up.

------------------------------
pt.

Original Message:
Sent: 01-12-2020 21:53
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

This is the 128T Router VM's network interface configuration after the config has been applied. The kni network interface is different than what you listed, but it's only 'off by one'. Was it a typo or significant?

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:c5:b8:41 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.2/24 brd 10.0.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fec5:b841/64 scope link
valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:05:26:d9 brd ff:ff:ff:ff:ff:ff
inet 192.168.64.1/24 brd 192.168.64.255 scope global eth2
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe05:26d9/64 scope link
valid_lft forever preferred_lft forever
5: kni254: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether ae:54:29:70:05:12 brd ff:ff:ff:ff:ff:ff
inet 169.254.127.127/31 brd 255.255.255.255 scope global kni254
valid_lft forever preferred_lft forever

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-11-2020 07:49
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

I don't quite follow the question... what type of interface are you creating?

Note that the 128T will create (at least) one interface, known as a "KNI" or kernel network interface, to shuttle packets between the Linux host operating system and the 128T's forwarding plane. This interface has a 169.254.127.126/31 address, and may be what you're seeing?

If you post an excerpt of your configuration here and let us know what you're trying to get working, we'll be happy to help out.

------------------------------
pt.

Original Message:
Sent: 01-10-2020 17:38
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Should be a simple question, after I configure an IP address in the Conductor, when I look at the network configuration of the running system it is creating the 169.* addresses like I would expect in an dhcp-system, but I configured the IP address in the normal way using the Conductor.

Where can I find more information about how the behaviour works?

Thanks!

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ
------------------------------

17. RE: Network Device Configuration Behaviour (Static vs. DHCP)

Recommend

peetee

Posted 01-13-2020 10:18

If you don't have a support contract, the options will be a bit limited. Have you signed a EULA or Evaluation Agreement? Are you working on behalf of a 128 Technology customer or partner? If so, work with them to submit a ticket.

------------------------------
pt.
------------------------------

Original Message

Original Message:
Sent: 01-13-2020 10:06
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

My contact is Lane Shields. Previously he directed me to the community when I have had questions of this sort.

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 10:02
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Do you have a support contract with 128 Technology?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 09:49
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

How would I do so?

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 09:45
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

I'm afraid that troubleshooting this may be beyond the scope of our back-and-forth in the community. There's something more fundamental wrong with this installation that will require deeper investigation. Can you please open a ticket with our support team?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 08:45
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

From the Router:

[centos@vnfi_128t_router_h7mvmq_1 ~]$ sudo su - admin
Last failed login: Mon Jan 13 12:46:47 UTC 2020 on ttyS0
There were 3 failed login attempts since the last successful login.
Starting the PCLI...
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show network-interface
Mon 2020-01-13 13:41:33 UTC
<Send CTRL+C>
Completed in 30.86 seconds
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1#

No output was produced. So I let it run until timeout:

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 08:32
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Please attach the output of "show device summary" and "show network-interface"?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 08:20
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hello Patrick,

I have made the change. The system still does not contact the Conductor afterwards.

<x-row>show config running authority router cmc-dv-eneaucpe-1

config

authority

router cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
inter-node-security internal

node cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
asset-id cmc-dv-enenaucpe-1-4
role combo

device-interface wan-pri
name wan-pri
type ethernet
pci-address 0000:00:03.0

network-interface eth1
name eth1
global-id 38
conductor true
inter-router-security internal
source-nat true

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164
host-service ssh
service-type ssh
access-policy cmc-dv-lab
source cmc-dv-lab
exit
access-policy /cmc-dv-inet
source /cmc-dv-inet
exit
exit
exit
exit
exit
exit
service-route _conductor_1_route_1
name _conductor_1_route_1
service-name _conductor_1
generated true
next-hop cmc-dv-eneaucpe-1 eth1
node-name cmc-dv-eneaucpe-1
interface eth1
gateway-ip 102.177.116.164
exit
exit
exit
exit
exit</x-row>

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 07:52
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hi Robert, please change it to type=ethernet in the PCLI. There is a UI bug that makes it look like your interface type is ethernet when it is not.

------------------------------
pt.

Original Message:
Sent: 01-13-2020 07:16
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hello Patrick,

It's not off by one. The KNI has two IP addresses, one in Linux's interface table and one in 128T's interface table. They are .127 and .126, respectively. Is this the 169. address you've been referring to?

Yes, it is. Is the 'ip a s' output I posted correct then?

The device type defaulted to Ethernet, so I did not change it. Screenshot below:

I have added a 'ssh' host service to the device interface configuration. The distributor I have been speaking with had indicated it was not required for our scenario.

I changed the ssh-host configuration to this (snipped from show config running authority router cmc-dv-eneaucpe-1). As mentioned the device type was defaulted to Ethernet and remains unchanged.

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164

host-service ssh
service-type ssh

access-policy cmc-dv-lab
source cmc-dv-lab
exit

access-policy /cmc-dv-inet
source /cmc-dv-inet

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 06:39
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

It's not off by one. The KNI has two IP addresses, one in Linux's interface table and one in 128T's interface table. They are .127 and .126, respectively. Is this the 169. address you've been referring to?

In your device-interface configuration you're missing type=ethernet. (You also don't have any host-service configured to allow inbound SSH, so you'll need to add that in order to SSH back into that address, too.)

Please add type=ethernet to your device-interface configuration and let us know the results. Include with them a copy of the output of "show device summary" and "show network-interface" from the router, if you have access to its console after the 128T system starts up.

------------------------------
pt.

Original Message:
Sent: 01-12-2020 21:53
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

This is the 128T Router VM's network interface configuration after the config has been applied. The kni network interface is different than what you listed, but it's only 'off by one'. Was it a typo or significant?

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:c5:b8:41 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.2/24 brd 10.0.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fec5:b841/64 scope link
valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:05:26:d9 brd ff:ff:ff:ff:ff:ff
inet 192.168.64.1/24 brd 192.168.64.255 scope global eth2
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe05:26d9/64 scope link
valid_lft forever preferred_lft forever
5: kni254: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether ae:54:29:70:05:12 brd ff:ff:ff:ff:ff:ff
inet 169.254.127.127/31 brd 255.255.255.255 scope global kni254
valid_lft forever preferred_lft forever

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-11-2020 07:49
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

I don't quite follow the question... what type of interface are you creating?

Note that the 128T will create (at least) one interface, known as a "KNI" or kernel network interface, to shuttle packets between the Linux host operating system and the 128T's forwarding plane. This interface has a 169.254.127.126/31 address, and may be what you're seeing?

If you post an excerpt of your configuration here and let us know what you're trying to get working, we'll be happy to help out.

------------------------------
pt.

Original Message:
Sent: 01-10-2020 17:38
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Should be a simple question, after I configure an IP address in the Conductor, when I look at the network configuration of the running system it is creating the 169.* addresses like I would expect in an dhcp-system, but I configured the IP address in the normal way using the Conductor.

Where can I find more information about how the behaviour works?

Thanks!

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ
------------------------------

18. RE: Network Device Configuration Behaviour (Static vs. DHCP)

Recommend

Session

Posted 01-13-2020 10:22

I'm with an integration firm, I can get in touch with the distributor through the client.

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ
------------------------------

Original Message

Original Message:
Sent: 01-13-2020 10:18
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

If you don't have a support contract, the options will be a bit limited. Have you signed a EULA or Evaluation Agreement? Are you working on behalf of a 128 Technology customer or partner? If so, work with them to submit a ticket.

------------------------------
pt.

Original Message:
Sent: 01-13-2020 10:06
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

My contact is Lane Shields. Previously he directed me to the community when I have had questions of this sort.

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 10:02
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Do you have a support contract with 128 Technology?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 09:49
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

How would I do so?

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 09:45
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

I'm afraid that troubleshooting this may be beyond the scope of our back-and-forth in the community. There's something more fundamental wrong with this installation that will require deeper investigation. Can you please open a ticket with our support team?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 08:45
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

From the Router:

[centos@vnfi_128t_router_h7mvmq_1 ~]$ sudo su - admin
Last failed login: Mon Jan 13 12:46:47 UTC 2020 on ttyS0
There were 3 failed login attempts since the last successful login.
Starting the PCLI...
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show network-interface
Mon 2020-01-13 13:41:33 UTC
<Send CTRL+C>
Completed in 30.86 seconds
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1#

No output was produced. So I let it run until timeout:

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 08:32
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Please attach the output of "show device summary" and "show network-interface"?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 08:20
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hello Patrick,

I have made the change. The system still does not contact the Conductor afterwards.

<x-row>show config running authority router cmc-dv-eneaucpe-1

config

authority

router cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
inter-node-security internal

node cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
asset-id cmc-dv-enenaucpe-1-4
role combo

device-interface wan-pri
name wan-pri
type ethernet
pci-address 0000:00:03.0

network-interface eth1
name eth1
global-id 38
conductor true
inter-router-security internal
source-nat true

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164
host-service ssh
service-type ssh
access-policy cmc-dv-lab
source cmc-dv-lab
exit
access-policy /cmc-dv-inet
source /cmc-dv-inet
exit
exit
exit
exit
exit
exit
service-route _conductor_1_route_1
name _conductor_1_route_1
service-name _conductor_1
generated true
next-hop cmc-dv-eneaucpe-1 eth1
node-name cmc-dv-eneaucpe-1
interface eth1
gateway-ip 102.177.116.164
exit
exit
exit
exit
exit</x-row>

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 07:52
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hi Robert, please change it to type=ethernet in the PCLI. There is a UI bug that makes it look like your interface type is ethernet when it is not.

------------------------------
pt.

Original Message:
Sent: 01-13-2020 07:16
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hello Patrick,

It's not off by one. The KNI has two IP addresses, one in Linux's interface table and one in 128T's interface table. They are .127 and .126, respectively. Is this the 169. address you've been referring to?

Yes, it is. Is the 'ip a s' output I posted correct then?

The device type defaulted to Ethernet, so I did not change it. Screenshot below:

I have added a 'ssh' host service to the device interface configuration. The distributor I have been speaking with had indicated it was not required for our scenario.

I changed the ssh-host configuration to this (snipped from show config running authority router cmc-dv-eneaucpe-1). As mentioned the device type was defaulted to Ethernet and remains unchanged.

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164

host-service ssh
service-type ssh

access-policy cmc-dv-lab
source cmc-dv-lab
exit

access-policy /cmc-dv-inet
source /cmc-dv-inet

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 06:39
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

It's not off by one. The KNI has two IP addresses, one in Linux's interface table and one in 128T's interface table. They are .127 and .126, respectively. Is this the 169. address you've been referring to?

In your device-interface configuration you're missing type=ethernet. (You also don't have any host-service configured to allow inbound SSH, so you'll need to add that in order to SSH back into that address, too.)

Please add type=ethernet to your device-interface configuration and let us know the results. Include with them a copy of the output of "show device summary" and "show network-interface" from the router, if you have access to its console after the 128T system starts up.

------------------------------
pt.

Original Message:
Sent: 01-12-2020 21:53
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

This is the 128T Router VM's network interface configuration after the config has been applied. The kni network interface is different than what you listed, but it's only 'off by one'. Was it a typo or significant?

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:c5:b8:41 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.2/24 brd 10.0.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fec5:b841/64 scope link
valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:05:26:d9 brd ff:ff:ff:ff:ff:ff
inet 192.168.64.1/24 brd 192.168.64.255 scope global eth2
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe05:26d9/64 scope link
valid_lft forever preferred_lft forever
5: kni254: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether ae:54:29:70:05:12 brd ff:ff:ff:ff:ff:ff
inet 169.254.127.127/31 brd 255.255.255.255 scope global kni254
valid_lft forever preferred_lft forever

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-11-2020 07:49
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

I don't quite follow the question... what type of interface are you creating?

Note that the 128T will create (at least) one interface, known as a "KNI" or kernel network interface, to shuttle packets between the Linux host operating system and the 128T's forwarding plane. This interface has a 169.254.127.126/31 address, and may be what you're seeing?

If you post an excerpt of your configuration here and let us know what you're trying to get working, we'll be happy to help out.

------------------------------
pt.

Original Message:
Sent: 01-10-2020 17:38
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Should be a simple question, after I configure an IP address in the Conductor, when I look at the network configuration of the running system it is creating the 169.* addresses like I would expect in an dhcp-system, but I configured the IP address in the normal way using the Conductor.

Where can I find more information about how the behaviour works?

Thanks!

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ
------------------------------

19. RE: Network Device Configuration Behaviour (Static vs. DHCP)

Recommend

Session

Posted 01-13-2020 10:36

Patrick,

Thank's for your timely and responsive help over the weekend.

Robert

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ
------------------------------

Original Message

Original Message:
Sent: 01-13-2020 09:45
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

I'm afraid that troubleshooting this may be beyond the scope of our back-and-forth in the community. There's something more fundamental wrong with this installation that will require deeper investigation. Can you please open a ticket with our support team?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 08:45
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

From the Router:

[centos@vnfi_128t_router_h7mvmq_1 ~]$ sudo su - admin
Last failed login: Mon Jan 13 12:46:47 UTC 2020 on ttyS0
There were 3 failed login attempts since the last successful login.
Starting the PCLI...
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show network-interface
Mon 2020-01-13 13:41:33 UTC
<Send CTRL+C>
Completed in 30.86 seconds
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1#

No output was produced. So I let it run until timeout:

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 08:32
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Please attach the output of "show device summary" and "show network-interface"?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 08:20
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hello Patrick,

I have made the change. The system still does not contact the Conductor afterwards.

<x-row>show config running authority router cmc-dv-eneaucpe-1

config

authority

router cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
inter-node-security internal

node cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
asset-id cmc-dv-enenaucpe-1-4
role combo

device-interface wan-pri
name wan-pri
type ethernet
pci-address 0000:00:03.0

network-interface eth1
name eth1
global-id 38
conductor true
inter-router-security internal
source-nat true

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164
host-service ssh
service-type ssh
access-policy cmc-dv-lab
source cmc-dv-lab
exit
access-policy /cmc-dv-inet
source /cmc-dv-inet
exit
exit
exit
exit
exit
exit
service-route _conductor_1_route_1
name _conductor_1_route_1
service-name _conductor_1
generated true
next-hop cmc-dv-eneaucpe-1 eth1
node-name cmc-dv-eneaucpe-1
interface eth1
gateway-ip 102.177.116.164
exit
exit
exit
exit
exit</x-row>

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 07:52
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hi Robert, please change it to type=ethernet in the PCLI. There is a UI bug that makes it look like your interface type is ethernet when it is not.

------------------------------
pt.

Original Message:
Sent: 01-13-2020 07:16
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hello Patrick,

It's not off by one. The KNI has two IP addresses, one in Linux's interface table and one in 128T's interface table. They are .127 and .126, respectively. Is this the 169. address you've been referring to?

Yes, it is. Is the 'ip a s' output I posted correct then?

The device type defaulted to Ethernet, so I did not change it. Screenshot below:

I have added a 'ssh' host service to the device interface configuration. The distributor I have been speaking with had indicated it was not required for our scenario.

I changed the ssh-host configuration to this (snipped from show config running authority router cmc-dv-eneaucpe-1). As mentioned the device type was defaulted to Ethernet and remains unchanged.

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164

host-service ssh
service-type ssh

access-policy cmc-dv-lab
source cmc-dv-lab
exit

access-policy /cmc-dv-inet
source /cmc-dv-inet

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 06:39
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

It's not off by one. The KNI has two IP addresses, one in Linux's interface table and one in 128T's interface table. They are .127 and .126, respectively. Is this the 169. address you've been referring to?

In your device-interface configuration you're missing type=ethernet. (You also don't have any host-service configured to allow inbound SSH, so you'll need to add that in order to SSH back into that address, too.)

Please add type=ethernet to your device-interface configuration and let us know the results. Include with them a copy of the output of "show device summary" and "show network-interface" from the router, if you have access to its console after the 128T system starts up.

------------------------------
pt.

Original Message:
Sent: 01-12-2020 21:53
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

This is the 128T Router VM's network interface configuration after the config has been applied. The kni network interface is different than what you listed, but it's only 'off by one'. Was it a typo or significant?

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:c5:b8:41 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.2/24 brd 10.0.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fec5:b841/64 scope link
valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:05:26:d9 brd ff:ff:ff:ff:ff:ff
inet 192.168.64.1/24 brd 192.168.64.255 scope global eth2
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe05:26d9/64 scope link
valid_lft forever preferred_lft forever
5: kni254: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether ae:54:29:70:05:12 brd ff:ff:ff:ff:ff:ff
inet 169.254.127.127/31 brd 255.255.255.255 scope global kni254
valid_lft forever preferred_lft forever

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-11-2020 07:49
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

I don't quite follow the question... what type of interface are you creating?

Note that the 128T will create (at least) one interface, known as a "KNI" or kernel network interface, to shuttle packets between the Linux host operating system and the 128T's forwarding plane. This interface has a 169.254.127.126/31 address, and may be what you're seeing?

If you post an excerpt of your configuration here and let us know what you're trying to get working, we'll be happy to help out.

------------------------------
pt.

Original Message:
Sent: 01-10-2020 17:38
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Should be a simple question, after I configure an IP address in the Conductor, when I look at the network configuration of the running system it is creating the 169.* addresses like I would expect in an dhcp-system, but I configured the IP address in the normal way using the Conductor.

Where can I find more information about how the behaviour works?

Thanks!

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ
------------------------------

20. RE: Network Device Configuration Behaviour (Static vs. DHCP)

Recommend

Session

Posted 01-13-2020 17:08

Hello Patrick,

Quick update. We tracked down the issue, the 'grains' property in the /etc/salt/minion file was set to the device's IP address instead of 127.0.0.1 as it should have been. So the global.init file had the wrong 'control' IP and it wouldn't work. Thanks for your help.

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ
------------------------------

Original Message

Original Message:
Sent: 01-13-2020 09:45
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

I'm afraid that troubleshooting this may be beyond the scope of our back-and-forth in the community. There's something more fundamental wrong with this installation that will require deeper investigation. Can you please open a ticket with our support team?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 08:45
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

From the Router:

[centos@vnfi_128t_router_h7mvmq_1 ~]$ sudo su - admin
Last failed login: Mon Jan 13 12:46:47 UTC 2020 on ttyS0
There were 3 failed login attempts since the last successful login.
Starting the PCLI...
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show network-interface
Mon 2020-01-13 13:41:33 UTC
<Send CTRL+C>
Completed in 30.86 seconds
admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1#

No output was produced. So I let it run until timeout:

admin@cmc-dv-eneaucpe-1.cmc-dv-eneaucpe-1# show device summary
Mon 2020-01-13 13:37:59 UTC
<Send CTRL+C>
Completed in 196.43 seconds

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 08:32
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Please attach the output of "show device summary" and "show network-interface"?

------------------------------
pt.

Original Message:
Sent: 01-13-2020 08:20
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hello Patrick,

I have made the change. The system still does not contact the Conductor afterwards.

<x-row>show config running authority router cmc-dv-eneaucpe-1

config

authority

router cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
inter-node-security internal

node cmc-dv-eneaucpe-1
name cmc-dv-eneaucpe-1
asset-id cmc-dv-enenaucpe-1-4
role combo

device-interface wan-pri
name wan-pri
type ethernet
pci-address 0000:00:03.0

network-interface eth1
name eth1
global-id 38
conductor true
inter-router-security internal
source-nat true

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164
host-service ssh
service-type ssh
access-policy cmc-dv-lab
source cmc-dv-lab
exit
access-policy /cmc-dv-inet
source /cmc-dv-inet
exit
exit
exit
exit
exit
exit
service-route _conductor_1_route_1
name _conductor_1_route_1
service-name _conductor_1
generated true
next-hop cmc-dv-eneaucpe-1 eth1
node-name cmc-dv-eneaucpe-1
interface eth1
gateway-ip 102.177.116.164
exit
exit
exit
exit
exit</x-row>

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 07:52
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hi Robert, please change it to type=ethernet in the PCLI. There is a UI bug that makes it look like your interface type is ethernet when it is not.

------------------------------
pt.

Original Message:
Sent: 01-13-2020 07:16
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Hello Patrick,

It's not off by one. The KNI has two IP addresses, one in Linux's interface table and one in 128T's interface table. They are .127 and .126, respectively. Is this the 169. address you've been referring to?

Yes, it is. Is the 'ip a s' output I posted correct then?

The device type defaulted to Ethernet, so I did not change it. Screenshot below:

I have added a 'ssh' host service to the device interface configuration. The distributor I have been speaking with had indicated it was not required for our scenario.

I changed the ssh-host configuration to this (snipped from show config running authority router cmc-dv-eneaucpe-1). As mentioned the device type was defaulted to Ethernet and remains unchanged.

address 102.177.116.165
ip-address 102.177.116.165
prefix-length 31
gateway 102.177.116.164

host-service ssh
service-type ssh

access-policy cmc-dv-lab
source cmc-dv-lab
exit

access-policy /cmc-dv-inet
source /cmc-dv-inet

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-13-2020 06:39
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

It's not off by one. The KNI has two IP addresses, one in Linux's interface table and one in 128T's interface table. They are .127 and .126, respectively. Is this the 169. address you've been referring to?

In your device-interface configuration you're missing type=ethernet. (You also don't have any host-service configured to allow inbound SSH, so you'll need to add that in order to SSH back into that address, too.)

Please add type=ethernet to your device-interface configuration and let us know the results. Include with them a copy of the output of "show device summary" and "show network-interface" from the router, if you have access to its console after the 128T system starts up.

------------------------------
pt.

Original Message:
Sent: 01-12-2020 21:53
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

This is the 128T Router VM's network interface configuration after the config has been applied. The kni network interface is different than what you listed, but it's only 'off by one'. Was it a typo or significant?

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:c5:b8:41 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.2/24 brd 10.0.0.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fec5:b841/64 scope link
valid_lft forever preferred_lft forever
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 52:54:00:05:26:d9 brd ff:ff:ff:ff:ff:ff
inet 192.168.64.1/24 brd 192.168.64.255 scope global eth2
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe05:26d9/64 scope link
valid_lft forever preferred_lft forever
5: kni254: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether ae:54:29:70:05:12 brd ff:ff:ff:ff:ff:ff
inet 169.254.127.127/31 brd 255.255.255.255 scope global kni254
valid_lft forever preferred_lft forever

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ

Original Message:
Sent: 01-11-2020 07:49
From: Patrick A Timmons
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

I don't quite follow the question... what type of interface are you creating?

Note that the 128T will create (at least) one interface, known as a "KNI" or kernel network interface, to shuttle packets between the Linux host operating system and the 128T's forwarding plane. This interface has a 169.254.127.126/31 address, and may be what you're seeing?

If you post an excerpt of your configuration here and let us know what you're trying to get working, we'll be happy to help out.

------------------------------
pt.

Original Message:
Sent: 01-10-2020 17:38
From: Robert Mazzatto
Subject: Network Device Configuration Behaviour (Static vs. DHCP)

Should be a simple question, after I configure an IP address in the Conductor, when I look at the network configuration of the running system it is creating the 169.* addresses like I would expect in an dhcp-system, but I configured the IP address in the normal way using the Conductor.

Where can I find more information about how the behaviour works?

Thanks!

------------------------------
Robert Mazzatto
Software Developer
Frenchtown NJ
------------------------------

SD-WAN