cancel
Showing results for 
Search instead for 
Did you mean: 

prod and bak NIC on master, media & client

Bharath_Achar
Level 6

We have 3 media and 1 master+media servers, all are having 2 NICs (prodution and backup) slamp1.aaa.com slamp2.aaa.com slamp3.aaa.com slamp4.aaa.com slamp1-bak.aaa.com slamp2-bak.aaa.com slamp3-bak.aaa.com slamp4-bak.aaa.com we installed a NBU client on windows and linux servers and these has only prod NIC, which are AWS hosted instances. 1. For these clients if we mention only below prod NIC entries as server list. slamp1-bak.aaa.com slamp2-bak.aaa.com slamp3-bak.aaa.com slamp4-bak.aaa.com then we are unable to connect NBU master/media and clients. we cannot see master/media client from NBU GUI under host properties. 2. if we mention only below prod NIC entries as server list. slamp1.aaa.com slamp2.aaa.com slamp3.aaa.com slamp4.aaa.com slamp1-bak.aaa.com slamp2-bak.aaa.com slamp3-bak.aaa.com slamp4-bak.aaa.com we can see master/media client connection from NBU GUI under host properties. Please tell me why the connection is not existing in case 1. what is the issue.

3 REPLIES 3

Luiz_Prina
Level 4
Employee

Hello Bharath,

 

 

Have you tried to use bpcoverage and bpcltncmd command?

 

It tells you what kind of issue you may find in your network.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

If clients only have access to prod network, it makes sense that they will only be able to communicate with master and media servers on prod hostnames.

Same as recommendations in your other post: https://www-secure.symantec.com/connect/forums/prod-bak-interface-usage-master-media-clients

Speak to network admins.
Get a network diagram as per my recommendation in above post...

Bharath_Achar
Level 6

 

Please ignore this question ,

 

there was some misconfiguration from network team and hence it was not routing.