Several products int he Cisco Unified Communications family of products contain a command execution vulnerability in the Disaster Recovery Framework (DRF) feature. The risk is HIGH. A remote, unauthenticated user could exploit this vulnerability to execute arbitrary commands that may allow full administration access to affected systems.
Hi,
I just want to throw something out there for opinions and viewpoints relating to a Disaster Recovery site.
Besides the live production environment, do you think a DR environment should include:
- pre-production environment
- QA Environment
......or would this be considered to be OTT... (3 Replies)
Recovering Solaris to an alternate server
I was just wondering if anyone could give me some points on restoring a Solaris 9 backup to an alternate server. Basically, we use netbackup 6 and I was wondering what the best procedures are for doing this? What things do we need to take into... (3 Replies)
I am looking into disaster recovery and I wanted to know what files and/or other information do I need to keep copies of to sucessfully restore my system from the ground up..... Any help is greatly appreciated. I am running Solaris 8 on an Ultra 60. (5 Replies)
Can anyone tell me of what to expect? I've been nominated to join a team of unix admins to do a DR testing. we already have the guys who are gono be doing the restores. besides the restore, anybody know what else to look forward to?? (2 Replies)
please tell me if this thinkin is correct, if not, please corret me:
disaster recovery means when something bad happens and you need to retrieved a backed up file, all you have to do is cd into the tape drive and then look for the file you want and extract it from the drive.
is this... (3 Replies)
Net::CLI::Interact::Manual::Phrasebook(3pm) User Contributed Perl Documentation Net::CLI::Interact::Manual::Phrasebook(3pm)NAME
Net::CLI::Interact::Manual::Phrasebook - List of Supported CLIs
INTRODUCTION
The bundled phrasebook includes support for a variety of network device CLIs. Many were contributed by users of the module. If you set up
a new CLI dictionary, please consider contributing it back! The phrasebook specification is given in Net::CLI::Interact::Phrasebook.
For each supported CLI, there is a name which must be passed in the "personality" option to Net::CLI::Interact's "new()" method. After
that, you can call the included Macros, and the module will use the included Prompt to match the current state of the CLI. More information
is available in the Tutorial and Cookbook.
Below is a list of all current bundled CLI dictionaries. Each lists its name, the available Prompts, Macros and Continuations, and from
which other CLI dictionaries it inherits.
IOS # Cisco IOS
CatOS # for older, pre-IOS Cisco devices
PIXOS # for PIX OS-based devices
PIXOS7 # Slightly different commands from other PIXOS versions
FWSM # currently the same as 'PIXOS'
FWSM3 # for FWSM Release 3.x devices (slightly different to FWSM 2.x)
JunOS # Juniper JUNOS support
HP # HP support
Nortel # Nortel support
ExtremeOS # Extreme Networks support
Foundry # Foundry/Brocade device support
PERSONALITIES
Cisco
This personality goes by the name of "cisco" and provides a basis for many other CLI dictionaries.
Prompts are "basic", "privileged", "configure", "user", and "pass".
Macros are "begin_privileged", "end_privileged", "begin_configure", "end_configure", and "disconnect".
CatOS
This personality goes by the name of "catos" and inherits from the "cisco" dictionary.
Additionally it provides the "privileged" Prompt.
Additionally it also provides the "paging" Macro to set the terminal page size.
ExtremeOS
This personality goes by the name of "extremeos" and inherits from the "cisco" dictionary.
Additional Prompts are "basic", "privileged", "configure", "user", and "pass".
Additional Macros are "begin_privileged", "end_privileged", and "disconnect".
Foundry / Brocade
This personality goes by the name of "foundry" and inherits from the "cisco" dictionary. Before connecting to the device you probably want
to set the output separator to be:
$nci->transport->ors("
");
For users of Net::Appliance::Session this should be:
$session_obj->nci->transport->ors("
");
IOS
This personality goes by the name of "ios" and inherits from the "cisco" dictionary.
Additionally it provides the "paging" Macro to set the terminal page size.
HP
This personality goes by the name of "hp" and inherits from the "cisco" dictionary.
Additionally it provides the "basic" and "user" Prompts.
JunOS
This personality goes by the name of "junos" and inherits from the "cisco" dictionary.
Additionally it provides the "privileged", "configure", and "user" Prompts.
Additionally it also provides the "begin_configure" and "paging" Macros.
Nortel
This personality goes by the name of "nortel" and inherits from the "cisco" dictionary.
Additionally it provides the "user" Prompt.
PIXOS
This personality goes by the name of "pixos" and inherits from the "cisco" dictionary.
Additionally it provides the "paging" Macro to set the terminal page size.
It can be used in its own right for Cisco PIX firewalls, but is also used as a base for other dictionaries.
PIXOS 7
This personality goes by the name of "pixos7" and inherits from the "pixos" dictionary.
Additionally it provides the "paging" Macro to set the terminal page size.
FWSM
This personality goes by the name of "fwsm" and inherits from the "pixos" dictionary.
It provides no further functionality, as Cisco FWSM software version 1 and 2 was the same as the PIX OS.
FWSM 3
This personality goes by the name of "fwsm3" and inherits from the "pixos" dictionary.
Additionally it provides the "paging" Macro to set the terminal page size.
perl v5.14.2 2012-06-12 Net::CLI::Interact::Manual::Phrasebook(3pm)