EXOS specifiy source interface for sntp, download image or download url
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-09-2016 03:23 PM
We have a X450-G2 with 16.1.3.6.
This switch is the router of a branch. Unfortunately the router-transfer nentwork is not part of VPN IPSec SA. So we have several problems with services which using the route-based source interface to reach some services.
For syslog, radius and snmp it is possible to define the correct source interface ip.
But sntp is current not possible.
Another problem is bringing firmware update to this switch - download image and download url NOR "tftp get" supports specifying a source interface.Last change to use a local PC for update. Maybe other or smarter suggestions ?
16.1.x Web interface does also not support a firmware update. (21.x. support that - but patch level is to low for me needs regarding system stability)
So any ideas to get sntp running or bringing a new firmware to that switch ?
Regards,
Matthias
This switch is the router of a branch. Unfortunately the router-transfer nentwork is not part of VPN IPSec SA. So we have several problems with services which using the route-based source interface to reach some services.
For syslog, radius and snmp it is possible to define the correct source interface ip.
But sntp is current not possible.
Another problem is bringing firmware update to this switch - download image and download url NOR "tftp get" supports specifying a source interface.Last change to use a local PC for update. Maybe other or smarter suggestions ?
16.1.x Web interface does also not support a firmware update. (21.x. support that - but patch level is to low for me needs regarding system stability)
So any ideas to get sntp running or bringing a new firmware to that switch ?
Regards,
Matthias
17 REPLIES 17
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-16-2016 09:01 AM
BTW the source IP feature is needed for the scp2 and ssh2 clients as well.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-14-2016 09:32 AM
Just to add a little background info...
The functionality requested by Matthias is available on the S-Series and similar EOS devices by specifying a default management interface. The SecureStacks variant of EOS received individual source interface configuration options after customer requests. If those customers would want to migrate to EXOS, they would need this feature.
Layer 3 switches of other vendors, e.g. Cisco, support setting the source interface for every management service.
The functionality requested by Matthias is available on the S-Series and similar EOS devices by specifying a default management interface. The SecureStacks variant of EOS received individual source interface configuration options after customer requests. If those customers would want to migrate to EXOS, they would need this feature.
Layer 3 switches of other vendors, e.g. Cisco, support setting the source interface for every management service.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-12-2016 09:20 AM
It would be nice to have the configuration options suggested by Matthias.
A way to specify a default management interface/IP used as default source address for every IP communication started by the switch (this excludes ICMP messages in reaction to incoming packets) would go a long way. Adding a mechanism to override this per service (e.g. SNTP) or command (e.g. download) would be appreciated as well.
Erik
A way to specify a default management interface/IP used as default source address for every IP communication started by the switch (this excludes ICMP messages in reaction to incoming packets) would go a long way. Adding a mechanism to override this per service (e.g. SNTP) or command (e.g. download) would be appreciated as well.
Erik
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-12-2016 08:21 AM
Hi Dave,
thanks for your reply.
The above described problem occuring again and again at some customer projects. In EOS i coulld address this with defining the host vlan.
Are there any plan to enhance EXOS with source-ip definition for sntp, firmware upload and configuration download services (within netsight).
Regards,
Matthias
thanks for your reply.
The above described problem occuring again and again at some customer projects. In EOS i coulld address this with defining the host vlan.
Are there any plan to enhance EXOS with source-ip definition for sntp, firmware upload and configuration download services (within netsight).
Regards,
Matthias
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎12-09-2016 06:28 PM
This doesn't address the networking problem but you can use the old school method of upgrading a switch via USB memory stick.
E.g.
Copy an EXOS .xos image on a FAT32 USB memory stick
download url file:///usr/local/ext/summitX-16.1.3.6.xos
E.g.
Copy an EXOS .xos image on a FAT32 USB memory stick
download url file:///usr/local/ext/summitX-16.1.3.6.xos
