Skip to main content

Filter by idea status

Filter by features

835 Ideas

leadwestNew Participant

Collaboration portal (Function portal enhancement)Open

I aim to enhance the functionality of our function portal to facilitate easier network visibility for internal teams and vendors without compromising security or causing frustration during troubleshooting sessions.Our goal is to extend access to our function portal to internal ESS/SOC teams and federal staff, allowing them to observe our network without the need for account creation or modification privileges.During vendor calls, our organizational screen-sharing policies prevent us from granting control, resulting in inefficiencies and frustration. To streamline troubleshooting, I propose enabling vendor support teams to access a shared collaborative space within the portal. They would open affected site map or a custom map of just the chosen devices then vendor users could then:-Bring up a popup “console” to run Commands on the devices.-Execute show commands through netbrain- just how we do with the runbooks on our maps.-Execute diagnostic or live updating commands- Some commands periodically update live- would be nice for that to display on the screen.-Shared notepad that individuals can place notes on. We would also be able to log the actions of the vendor support. We could capture commands and logs in chronological order, identifying useful operational processes for specific issues. This data could then be transformed into a digital assistant or qapp to expedite troubleshooting.With this type of access- we would need heavier security:Example: Rather than a static passcode or user account. Make PKI,OTP, MFA, etc. available for authentication to the portal.Example: Adjustable data obfuscation for different levels of collaborators.Example: dropping the authentication settings and hashes out of the configuration,Example: No copy/paste 

gshaw550New Participant

NetBrain - Feature Request, Enhance Runbook exportOpen

Dear NetBrain, Regarding the Export feature of Runbooks. The export of Runbook information is really detailed “after” the Runbook has been executed, you can see the results of the commands run and the comparison. But we would like to export the Runbook details to Word before the Runbook is executed, so we can put the details into a Change Authorisation Form (part of the change management process outside of NetBrain which needs sign off before we can execute the Runbook) So as an example, in a Runbook you could create a step to run two show commands and then collect the standard set of “Built-in Live data” across a number of devices. At this stage we would like to see in the export what tables will be retrieved and commands are going to be run. But when you export a Runbook that has not yet been run you do not get this information, it focuses on the results (which have not been run at this stage) not the commands or tables you will be collecting. Would it be possible to include the commands and tables that will be run in the Runbook export, as a new feature?e.g in the export for that step in the Runbook something like this: Runbook StepDevices in Scope:Switch1 Switch2 Router3 Commands to be executed:show run show int status  Tables to be collected:MAC Table ARP TableThis would save us double keying this information into a separate Change Authorisation Form, we could export all of this and save a lot of time, this detail makes up 90% of the form. Many Thanks for your consideration, happy to discuss further