View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 627 | RackTables | default | public | 2012-10-06 11:43 | 2012-10-07 15:50 |
| Reporter | afabrizio72 | Assigned To | infrastation | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 0.20.1 | ||||
| Summary | 627: Live Ports and Live CDP are blank | ||||
| Description | It is the same problem as 489. When I use Live Ports and Live CDP, the page remain blank. Live vlans works well It is an authentication problem: when I make "live CDP" I don't see in the telnet connection the authentication credential, I just see "Terminal lenght 0" and "show cdp..." (With Live ports I see that the connection authenticate with username and password) Just to try, I modified the "remote.php" file in the "function translateDeviceCommands" and in "($settings['protocol'])" section. I modified: case 'ios12': $commands = "terminal length 0\n" . $commands; break; in: case 'ios12': $commands = "cisco\ncisco\nenable\ncisco\nterminal length 0\n" . $commands; break; (<username>\n<password>\nenable\n<enable password>) and it works (both live cdp and live ports) The "live vlans" feature use the switchvlans.php under the gateway directory and read the authentication in "switch.secrets.php". It is not clear where the "live cdp" and "live ports" read the credential. I have the gateway directory in : /usr/bin/Racktables/gateways and I added to secret.php: $racktables_gwdir = ‘/usr/bin/RackTables/gateways’; $racktables_plugins_dir = ‘/usr/bin/RackTables/plugins’; The switchvlans works well so I think the configuration is correct. | ||||
| Tags | No tags attached. | ||||
|
The deprecated "Live VLANs" feature uses the "switchvlans" gateway as a backend. Both "Live CDP" and "Live ports" use the new gateways API as described on http://wiki.racktables.org/index.php/Gateways . The new API does not require hardcoding any credentials in the source code, please see how credentials are configured with the terminal_settings() custom function (same page). To my understanding, there is no fix required here. |
|
|
Ok I confirm: no fix required. Now I understood the difference. I created the terminal_settings function with the required parameters, and now is working. For many reason I need to have different username and password for various switch, so I have to specify the hostname(and related parameter) both in the terminal_settings file and the cisco.secret.php file (for the VLANS): thats the only unconfortable thing. Anyway I will try to create a smarter terminal_setting function. Thanks |
|
|
Fine. Considering VLAN management, the "802.1Q" feature is a better choice for the job, and it uses the same infrastructure terminal_settings() is a part of. The "Live VLANs" consists of legacy code and may be removed really soon. Inside terminal_settings() it's possible to retrieve any required information about the current object and pick username and password respectively. I can confirm this to work. |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-10-06 11:43 | afabrizio72 | New Issue | |
| 2012-10-06 14:19 | infrastation | Note Added: 0000855 | |
| 2012-10-06 14:19 | infrastation | Assigned To | => infrastation |
| 2012-10-06 14:19 | infrastation | Status | new => assigned |
| 2012-10-06 20:30 | afabrizio72 | Note Added: 0000857 | |
| 2012-10-06 21:33 | infrastation | Note Added: 0000859 | |
| 2012-10-07 15:50 | infrastation | Status | assigned => closed |
| 2012-10-07 15:50 | infrastation | Resolution | open => no change required |