To have a better experience, please upgrade your IE browser.upgrade
Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
The customer had a topology consisting on ~200 x S5700 switches and eSight and due to this large environment he wanted to make his job easier by managing different processes on the switches through eSight. One of the handy features used by the customer on eSight is Backup&Restore which can save and restore the configuration of your device independent by your manual intervention on a server.
The problem appears when the customer would have the management addresses into a separate VPN instance, situation that make the feature not working.
If the NMS manages devices on the VPN network, you need to send the device information to the NMS using the VPN instance.
You can run the set net-manager vpn-instance command to configure the default VPN instance for the NMS to manage the device so that the device can use this VPN instance to communicate with the NMS. Having the VPN instance specified the feature can work and skip all the administrator’s job to manually backup configurations on a Server.
By default, if the VPN instance is not specified for NMS-NE communication the data will not be sent to the NMS using the instance.
Add the command that specifies the VPN instance on NEs devices (our case - S5700 switches):