Welcome, Guest. Please login or register.

Author Topic: Cisco RPS Discovery  (Read 4494 times)

pc_sg

  • Guest
Cisco RPS Discovery
« on: February 05, 2014, 03:33:54 PM »
Hi Remo,
today I had to find some infos about some Cisco RPS we have around connected to critical switches.
I know that some switches (3560 and 3750 afaik) communicate with RPS (at least 2300 models) and is possible to receive some infos, i.e. status, model or S/N.
The CLI command I know is "show env" declinations:
Code: [Select]
show env ?
  all          Show all environment status
  fan          Show fan status
  power        Show power supply status
  rps          Show RPS status
  stack        Show Stack-wide all environment status
  temperature  Show temperature status
  xps          Show XPS status



Do you think it's possible to identify and catalogue them in NeDi, for example as additional modules?


Not a real must, only a "nice to have" ... :)


Thanks in advance!

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2728
    • View Profile
    • NeDi
Re: Cisco RPS Discovery
« Reply #1 on: February 06, 2014, 07:04:53 PM »
It would be soo much easier, if the PS and its status would be in the entity mib (47.1.1.1 etc). Do you see it in there?
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

pc_sg

  • Guest
Re: Cisco RPS Discovery
« Reply #2 on: February 07, 2014, 08:32:30 AM »

Yes!


e.g. a stack of a couple of WS-C3750E-48TD wanlking 1.3.6.1.2.1.47.1.1.1.1.7 (Modules - Slot) gives a lot of information


Code: [Select]
iso.3.6.1.2.1.47.1.1.1.1.7.1 = STRING: "Cat37xx Stacking"
iso.3.6.1.2.1.47.1.1.1.1.7.1001 = STRING: "1"
iso.3.6.1.2.1.47.1.1.1.1.7.1002 = STRING: "Switch 1 - WS-C3750E-48TD - Fixed Module 0"
iso.3.6.1.2.1.47.1.1.1.1.7.1003 = STRING: "Switch 1 - Fan Container"
iso.3.6.1.2.1.47.1.1.1.1.7.1004 = STRING: "Switch 1 - Power Supply Container"
iso.3.6.1.2.1.47.1.1.1.1.7.1005 = STRING: "Switch 1 - RPS Container"
iso.3.6.1.2.1.47.1.1.1.1.7.1006 = STRING: "Switch 1 - WS-C3750E-48TD - Sensor 0"
iso.3.6.1.2.1.47.1.1.1.1.7.1007 = STRING: "StackPort1"
iso.3.6.1.2.1.47.1.1.1.1.7.1008 = STRING: "GigabitEthernet1/0/1"
iso.3.6.1.2.1.47.1.1.1.1.7.1009 = STRING: "GigabitEthernet1/0/2"
iso.3.6.1.2.1.47.1.1.1.1.7.1010 = STRING: "GigabitEthernet1/0/3"
iso.3.6.1.2.1.47.1.1.1.1.7.1011 = STRING: "GigabitEthernet1/0/4"
iso.3.6.1.2.1.47.1.1.1.1.7.1012 = STRING: "GigabitEthernet1/0/5"
iso.3.6.1.2.1.47.1.1.1.1.7.1013 = STRING: "GigabitEthernet1/0/6"
iso.3.6.1.2.1.47.1.1.1.1.7.1014 = STRING: "GigabitEthernet1/0/7"
iso.3.6.1.2.1.47.1.1.1.1.7.1015 = STRING: "GigabitEthernet1/0/8"
iso.3.6.1.2.1.47.1.1.1.1.7.1016 = STRING: "GigabitEthernet1/0/9"
iso.3.6.1.2.1.47.1.1.1.1.7.1017 = STRING: "GigabitEthernet1/0/10"
iso.3.6.1.2.1.47.1.1.1.1.7.1018 = STRING: "GigabitEthernet1/0/11"
iso.3.6.1.2.1.47.1.1.1.1.7.1019 = STRING: "GigabitEthernet1/0/12"
iso.3.6.1.2.1.47.1.1.1.1.7.1020 = STRING: "GigabitEthernet1/0/13"
iso.3.6.1.2.1.47.1.1.1.1.7.1021 = STRING: "GigabitEthernet1/0/14"
iso.3.6.1.2.1.47.1.1.1.1.7.1022 = STRING: "GigabitEthernet1/0/15"
iso.3.6.1.2.1.47.1.1.1.1.7.1023 = STRING: "GigabitEthernet1/0/16"
iso.3.6.1.2.1.47.1.1.1.1.7.1024 = STRING: "GigabitEthernet1/0/17"
iso.3.6.1.2.1.47.1.1.1.1.7.1025 = STRING: "GigabitEthernet1/0/18"
iso.3.6.1.2.1.47.1.1.1.1.7.1026 = STRING: "GigabitEthernet1/0/19"
iso.3.6.1.2.1.47.1.1.1.1.7.1027 = STRING: "GigabitEthernet1/0/20"
iso.3.6.1.2.1.47.1.1.1.1.7.1028 = STRING: "GigabitEthernet1/0/21"
iso.3.6.1.2.1.47.1.1.1.1.7.1029 = STRING: "GigabitEthernet1/0/22"
iso.3.6.1.2.1.47.1.1.1.1.7.1030 = STRING: "GigabitEthernet1/0/23"
iso.3.6.1.2.1.47.1.1.1.1.7.1031 = STRING: "GigabitEthernet1/0/24"
iso.3.6.1.2.1.47.1.1.1.1.7.1032 = STRING: "GigabitEthernet1/0/25"
iso.3.6.1.2.1.47.1.1.1.1.7.1033 = STRING: "GigabitEthernet1/0/26"
iso.3.6.1.2.1.47.1.1.1.1.7.1034 = STRING: "GigabitEthernet1/0/27"
iso.3.6.1.2.1.47.1.1.1.1.7.1035 = STRING: "GigabitEthernet1/0/28"
iso.3.6.1.2.1.47.1.1.1.1.7.1036 = STRING: "GigabitEthernet1/0/29"
iso.3.6.1.2.1.47.1.1.1.1.7.1037 = STRING: "GigabitEthernet1/0/30"
iso.3.6.1.2.1.47.1.1.1.1.7.1038 = STRING: "GigabitEthernet1/0/31"
iso.3.6.1.2.1.47.1.1.1.1.7.1039 = STRING: "GigabitEthernet1/0/32"
iso.3.6.1.2.1.47.1.1.1.1.7.1040 = STRING: "GigabitEthernet1/0/33"
iso.3.6.1.2.1.47.1.1.1.1.7.1041 = STRING: "GigabitEthernet1/0/34"
iso.3.6.1.2.1.47.1.1.1.1.7.1042 = STRING: "GigabitEthernet1/0/35"
iso.3.6.1.2.1.47.1.1.1.1.7.1043 = STRING: "GigabitEthernet1/0/36"
iso.3.6.1.2.1.47.1.1.1.1.7.1044 = STRING: "GigabitEthernet1/0/37"
iso.3.6.1.2.1.47.1.1.1.1.7.1045 = STRING: "GigabitEthernet1/0/38"
iso.3.6.1.2.1.47.1.1.1.1.7.1046 = STRING: "GigabitEthernet1/0/39"
iso.3.6.1.2.1.47.1.1.1.1.7.1047 = STRING: "GigabitEthernet1/0/40"
iso.3.6.1.2.1.47.1.1.1.1.7.1048 = STRING: "GigabitEthernet1/0/41"
iso.3.6.1.2.1.47.1.1.1.1.7.1049 = STRING: "GigabitEthernet1/0/42"
iso.3.6.1.2.1.47.1.1.1.1.7.1050 = STRING: "GigabitEthernet1/0/43"
iso.3.6.1.2.1.47.1.1.1.1.7.1051 = STRING: "GigabitEthernet1/0/44"
iso.3.6.1.2.1.47.1.1.1.1.7.1052 = STRING: "GigabitEthernet1/0/45"
iso.3.6.1.2.1.47.1.1.1.1.7.1053 = STRING: "GigabitEthernet1/0/46"
iso.3.6.1.2.1.47.1.1.1.1.7.1054 = STRING: "GigabitEthernet1/0/47"
iso.3.6.1.2.1.47.1.1.1.1.7.1055 = STRING: "GigabitEthernet1/0/48"
iso.3.6.1.2.1.47.1.1.1.1.7.1056 = STRING: "TenGigabitEthernet1/0/1 Container"
iso.3.6.1.2.1.47.1.1.1.1.7.1057 = STRING: "TenGigabitEthernet1/0/2 Container"
iso.3.6.1.2.1.47.1.1.1.1.7.1058 = STRING: "Switch 1 - FastEthernet0"
iso.3.6.1.2.1.47.1.1.1.1.7.1059 = STRING: "Switch 1 - Fan 0"
iso.3.6.1.2.1.47.1.1.1.1.7.1060 = STRING: "Switch 1 - Power Supply 0"
iso.3.6.1.2.1.47.1.1.1.1.7.1061 = STRING: "Switch 1 - RPS"
iso.3.6.1.2.1.47.1.1.1.1.7.1062 = STRING: "Switch 1 - RPS Power Supply A Container"
iso.3.6.1.2.1.47.1.1.1.1.7.1063 = STRING: "Switch 1 - RPS Power Supply B Container"
iso.3.6.1.2.1.47.1.1.1.1.7.1064 = STRING: "Switch 1 - RPS FRU Fan Container"
iso.3.6.1.2.1.47.1.1.1.1.7.1065 = STRING: "Switch 1 - RPS Power Supply A"
iso.3.6.1.2.1.47.1.1.1.1.7.1066 = STRING: "Switch 1 - RPS Power Supply B"
iso.3.6.1.2.1.47.1.1.1.1.7.1067 = ""
iso.3.6.1.2.1.47.1.1.1.1.7.1068 = STRING: "TenGigabitEthernet1/0/1"
iso.3.6.1.2.1.47.1.1.1.1.7.1069 = STRING: "Te1/0/1 Module Temperature Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.1070 = STRING: "Te1/0/1 Supply Voltage Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.1071 = STRING: "Te1/0/1 Bias Current Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.1072 = STRING: "Te1/0/1 Transmit Power Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.1073 = STRING: "Te1/0/1 Receive Power Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.1074 = STRING: "TenGigabitEthernet1/0/2"
iso.3.6.1.2.1.47.1.1.1.1.7.1075 = STRING: "Te1/0/2 Module Temperature Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.1076 = STRING: "Te1/0/2 Supply Voltage Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.1077 = STRING: "Te1/0/2 Bias Current Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.1078 = STRING: "Te1/0/2 Transmit Power Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.1079 = STRING: "Te1/0/2 Receive Power Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.2001 = STRING: "2"
iso.3.6.1.2.1.47.1.1.1.1.7.2002 = STRING: "Switch 2 - WS-C3750E-48TD - Fixed Module 0"
iso.3.6.1.2.1.47.1.1.1.1.7.2003 = STRING: "Switch 2 - Fan Container"
iso.3.6.1.2.1.47.1.1.1.1.7.2004 = STRING: "Switch 2 - Power Supply Container"
iso.3.6.1.2.1.47.1.1.1.1.7.2005 = STRING: "Switch 2 - RPS Container"
iso.3.6.1.2.1.47.1.1.1.1.7.2006 = STRING: "Switch 2 - WS-C3750E-48TD - Sensor 0"
iso.3.6.1.2.1.47.1.1.1.1.7.2007 = STRING: "StackPort2"
iso.3.6.1.2.1.47.1.1.1.1.7.2008 = STRING: "GigabitEthernet2/0/1"
iso.3.6.1.2.1.47.1.1.1.1.7.2009 = STRING: "GigabitEthernet2/0/2"
iso.3.6.1.2.1.47.1.1.1.1.7.2010 = STRING: "GigabitEthernet2/0/3"
iso.3.6.1.2.1.47.1.1.1.1.7.2011 = STRING: "GigabitEthernet2/0/4"
iso.3.6.1.2.1.47.1.1.1.1.7.2012 = STRING: "GigabitEthernet2/0/5"
iso.3.6.1.2.1.47.1.1.1.1.7.2013 = STRING: "GigabitEthernet2/0/6"
iso.3.6.1.2.1.47.1.1.1.1.7.2014 = STRING: "GigabitEthernet2/0/7"
iso.3.6.1.2.1.47.1.1.1.1.7.2015 = STRING: "GigabitEthernet2/0/8"
iso.3.6.1.2.1.47.1.1.1.1.7.2016 = STRING: "GigabitEthernet2/0/9"
iso.3.6.1.2.1.47.1.1.1.1.7.2017 = STRING: "GigabitEthernet2/0/10"
iso.3.6.1.2.1.47.1.1.1.1.7.2018 = STRING: "GigabitEthernet2/0/11"
iso.3.6.1.2.1.47.1.1.1.1.7.2019 = STRING: "GigabitEthernet2/0/12"
iso.3.6.1.2.1.47.1.1.1.1.7.2020 = STRING: "GigabitEthernet2/0/13"
iso.3.6.1.2.1.47.1.1.1.1.7.2021 = STRING: "GigabitEthernet2/0/14"
iso.3.6.1.2.1.47.1.1.1.1.7.2022 = STRING: "GigabitEthernet2/0/15"
iso.3.6.1.2.1.47.1.1.1.1.7.2023 = STRING: "GigabitEthernet2/0/16"
iso.3.6.1.2.1.47.1.1.1.1.7.2024 = STRING: "GigabitEthernet2/0/17"
iso.3.6.1.2.1.47.1.1.1.1.7.2025 = STRING: "GigabitEthernet2/0/18"
iso.3.6.1.2.1.47.1.1.1.1.7.2026 = STRING: "GigabitEthernet2/0/19"
iso.3.6.1.2.1.47.1.1.1.1.7.2027 = STRING: "GigabitEthernet2/0/20"
iso.3.6.1.2.1.47.1.1.1.1.7.2028 = STRING: "GigabitEthernet2/0/21"
iso.3.6.1.2.1.47.1.1.1.1.7.2029 = STRING: "GigabitEthernet2/0/22"
iso.3.6.1.2.1.47.1.1.1.1.7.2030 = STRING: "GigabitEthernet2/0/23"
iso.3.6.1.2.1.47.1.1.1.1.7.2031 = STRING: "GigabitEthernet2/0/24"
iso.3.6.1.2.1.47.1.1.1.1.7.2032 = STRING: "GigabitEthernet2/0/25"
iso.3.6.1.2.1.47.1.1.1.1.7.2033 = STRING: "GigabitEthernet2/0/26"
iso.3.6.1.2.1.47.1.1.1.1.7.2034 = STRING: "GigabitEthernet2/0/27"
iso.3.6.1.2.1.47.1.1.1.1.7.2035 = STRING: "GigabitEthernet2/0/28"
iso.3.6.1.2.1.47.1.1.1.1.7.2036 = STRING: "GigabitEthernet2/0/29"
iso.3.6.1.2.1.47.1.1.1.1.7.2037 = STRING: "GigabitEthernet2/0/30"
iso.3.6.1.2.1.47.1.1.1.1.7.2038 = STRING: "GigabitEthernet2/0/31"
iso.3.6.1.2.1.47.1.1.1.1.7.2039 = STRING: "GigabitEthernet2/0/32"
iso.3.6.1.2.1.47.1.1.1.1.7.2040 = STRING: "GigabitEthernet2/0/33"
iso.3.6.1.2.1.47.1.1.1.1.7.2041 = STRING: "GigabitEthernet2/0/34"
iso.3.6.1.2.1.47.1.1.1.1.7.2042 = STRING: "GigabitEthernet2/0/35"
iso.3.6.1.2.1.47.1.1.1.1.7.2043 = STRING: "GigabitEthernet2/0/36"
iso.3.6.1.2.1.47.1.1.1.1.7.2044 = STRING: "GigabitEthernet2/0/37"
iso.3.6.1.2.1.47.1.1.1.1.7.2045 = STRING: "GigabitEthernet2/0/38"
iso.3.6.1.2.1.47.1.1.1.1.7.2046 = STRING: "GigabitEthernet2/0/39"
iso.3.6.1.2.1.47.1.1.1.1.7.2047 = STRING: "GigabitEthernet2/0/40"
iso.3.6.1.2.1.47.1.1.1.1.7.2048 = STRING: "GigabitEthernet2/0/41"
iso.3.6.1.2.1.47.1.1.1.1.7.2049 = STRING: "GigabitEthernet2/0/42"
iso.3.6.1.2.1.47.1.1.1.1.7.2050 = STRING: "GigabitEthernet2/0/43"
iso.3.6.1.2.1.47.1.1.1.1.7.2051 = STRING: "GigabitEthernet2/0/44"
iso.3.6.1.2.1.47.1.1.1.1.7.2052 = STRING: "GigabitEthernet2/0/45"
iso.3.6.1.2.1.47.1.1.1.1.7.2053 = STRING: "GigabitEthernet2/0/46"
iso.3.6.1.2.1.47.1.1.1.1.7.2054 = STRING: "GigabitEthernet2/0/47"
iso.3.6.1.2.1.47.1.1.1.1.7.2055 = STRING: "GigabitEthernet2/0/48"
iso.3.6.1.2.1.47.1.1.1.1.7.2056 = STRING: "TenGigabitEthernet2/0/1 Container"
iso.3.6.1.2.1.47.1.1.1.1.7.2057 = STRING: "TenGigabitEthernet2/0/2 Container"
iso.3.6.1.2.1.47.1.1.1.1.7.2058 = STRING: "Switch 2 - FastEthernet0"
iso.3.6.1.2.1.47.1.1.1.1.7.2059 = STRING: "Switch 2 - Fan 0"
iso.3.6.1.2.1.47.1.1.1.1.7.2069 = STRING: "Switch 2 - RPS Power Supply A"
iso.3.6.1.2.1.47.1.1.1.1.7.2070 = STRING: "Switch 2 - RPS Power Supply B"
iso.3.6.1.2.1.47.1.1.1.1.7.2071 = STRING: "Switch 2 - RPS"
iso.3.6.1.2.1.47.1.1.1.1.7.2072 = STRING: "Switch 2 - RPS Power Supply A Container"
iso.3.6.1.2.1.47.1.1.1.1.7.2073 = STRING: "Switch 2 - RPS Power Supply B Container"
iso.3.6.1.2.1.47.1.1.1.1.7.2074 = STRING: "Switch 2 - RPS FRU Fan Container"
iso.3.6.1.2.1.47.1.1.1.1.7.2079 = ""
iso.3.6.1.2.1.47.1.1.1.1.7.2082 = STRING: "TenGigabitEthernet2/0/1"
iso.3.6.1.2.1.47.1.1.1.1.7.2083 = STRING: "Te2/0/1 Module Temperature Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.2084 = STRING: "Te2/0/1 Supply Voltage Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.2085 = STRING: "Te2/0/1 Bias Current Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.2086 = STRING: "Te2/0/1 Transmit Power Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.2087 = STRING: "Te2/0/1 Receive Power Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.2088 = STRING: "TenGigabitEthernet2/0/2"
iso.3.6.1.2.1.47.1.1.1.1.7.2089 = STRING: "Te2/0/2 Module Temperature Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.2090 = STRING: "Te2/0/2 Supply Voltage Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.2091 = STRING: "Te2/0/2 Bias Current Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.2092 = STRING: "Te2/0/2 Transmit Power Sensor"
iso.3.6.1.2.1.47.1.1.1.1.7.2093 = STRING: "Te2/0/2 Receive Power Sensor"
And .11 really returns S/N
How can I help you to add this information in NeDi ?


TIA!

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2728
    • View Profile
    • NeDi
Re: Cisco RPS Discovery
« Reply #3 on: February 07, 2014, 07:01:39 PM »
Check the RPS class with 1.3.6.1.2.1.47.1.1.1.1.5 and add the value to the existing as regexp (e.g. 9|6)
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

pc_sg

  • Guest
Re: Cisco RPS Discovery
« Reply #4 on: February 10, 2014, 08:09:04 AM »
Thank you so much!


Seems that adding 6 is enough (at least with 3750, for other I need to do some more check)


Do you need a dump of a walk on 1.3.6.1.2.1.47.1.1.1.1.5  for some other switches?

Edit: Cisco says that only Cisco Catalyst 2960-X, 2960-S, 3750-E, and 3560-E Series Switches are able to handle (i.e. communicate) with Cisco RPS 2300.
I've checked this walking in the same way you've adviced on two 3550 connected to a RPS2300, and seems unaware of being supplied by a RPS at all.
Since 3750 are handled by a single .def, adding 6 seems enough.
« Last Edit: February 10, 2014, 09:10:02 AM by pc_sg »

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2728
    • View Profile
    • NeDi
Re: Cisco RPS Discovery
« Reply #5 on: February 10, 2014, 05:53:14 PM »
I've adjusted 1.3.6.1.4.1.9.1.516.def. My strategy is, if a it's field-replacable and a SN can be read, it should be added. Everything else doesn't make sense to me...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

pc_sg

  • Guest
Re: Cisco RPS Discovery
« Reply #6 on: February 11, 2014, 08:12:56 AM »
Let see (attached) what NeDi (1.0.8, I haven't yet upgraded all my NeDi instances, until a real stable and debugged version comes out) detect with 6 added on a stack of 3750 powered by a RPS.
Not only RPS, but also internal power supply. That is correct, particularly with new X series Cisco switches that, in stacks, can uses every internal power supply as a part of a RPS.


Anyway, I don't understand exactly your strategy to choose what is useful to collect. Do you look for presence of S/N (PhysicalSerialNum), and then pair them with other related infos?



rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2728
    • View Profile
    • NeDi
Re: Cisco RPS Discovery
« Reply #7 on: February 11, 2014, 06:14:53 PM »
Yes, SN should be readable. Some internal PS report SN as well, but what's the point, if it can't be replaced officially?

What do you mean by real stable and debugged? 109 is much closer to that than 108 :-)
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

pc_sg

  • Guest
Re: Cisco RPS Discovery
« Reply #8 on: February 13, 2014, 08:31:54 AM »
I'm unable to reply to your post.


Every time this returns:


Code: [Select]
Access denied by security policyYour request is blocked by a security policy rule.
Please contact the support team, support@hoststar.ch and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.Please provide the following information to our support team: forum.nedi.ch | 85.47.141.186 | 13.02.2014 08:29:50

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2728
    • View Profile
    • NeDi
Re: Cisco RPS Discovery
« Reply #9 on: February 13, 2014, 08:36:53 PM »
Sorry about that, try posting half of it and see if the error disappears. If so add half of the remaining half and so forth...

I'm not sure what exactly causes it, but it's got something to do with the .htacces. Let me know, if you can identify the exact characters causing this...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

pc_sg

  • Guest
Re: Cisco RPS Discovery
« Reply #10 on: February 14, 2014, 08:30:26 AM »
OK.
First reply: yes, there are also internal power supply, but the description may help to distinguish which get and which discard.
If you want/like, I can send you privately a full snmpwalk dump.




pc_sg

  • Guest
Re: Cisco RPS Discovery
« Reply #11 on: February 14, 2014, 08:57:54 AM »
Second reply:
About stable, we've a bunch of NeDi 1.0.8-116 "in production",  and I know that I must modify databases. I'm afraid of losting collected information (my colleagues rely on it) and/or needs of a complete reinitialization. In the past, I wasn't able to backup data, reinitialize database and reimport data.
So, I'm waiting for a more debugged version. Maybe that current one is stable enough to guarantee no more database modifications ?

pc_sg

  • Guest
Re: Cisco RPS Discovery
« Reply #12 on: February 14, 2014, 09:10:08 AM »
Third reply:
About NeDi Update. In the past I never was able to use the internal update procedure, i.e. through Sytem - Files - Task - Update NeDi. I was forced to extract all files and overwrite the installed ones, keeping away configurations ad modded defs and reconfiguring/modding new ones if needed.


How can I determine cause of failing Update ?


Thanks!


P.S. the cause of error posting reply was the use of angle brackets inside text, exactely the right pointing one (to create an arrow). So not every printable character is usable in this forum...